Connecting to two boards

D2K

• July 31, 2024 21:30

Hi.

We are using two CAN@net boards to interface with two control units via canopen master api. The software works well when running each board/control separately. However it doesn't work when attempting to drive the two boards within the same software build. The second InitBoard call would override the first one even though the calls have different boards guids, the resulting boardhdl id is 1 in both calls.

Is it possible to connect to two CAN@Net ii boards simultaneously?

0

• Official comment

  

  Peter Wucherer

  • August 01, 2024 15:06

  Hi D2K,

  you mean open 2 CAN@net/II VCI in one application?
  Or the same application started 2 times and uses 2 different CAN@net II/VCI?

  I tested it and it works successful when using the board selection dialog.
  Using the defines GUID_CANATNET2_DEVICE, COP_1stBOARD and COP_2ndBOARD working ok.

  Do you use the VCI mode (COP_VCI3GENERIC)?

  
  In my got 2 different board handles:
  ---------
  Console test for IXXAT CANopen Master API!
  Open 2 CAN interfaces using the defines GUID_CANATNET2_DEVICE, COP_1stBOARD and COP_2ndBOARD !
  COP_InitBoard OK. Board handle: 1
  Board type: 10.41.24.201         Serial no: HW834641
  COP_InitBoard OK. Board handle: 2
  Board type: 10.41.24.202         Serial no: HW843648
  ---------
  If useful, I can add the source code, it's a Visual Studio 2022 C++ console demo.
  Or do you use .NET.

  Maybe you can create a support request. 
  There we can go deeper into.
  A request can made here:
  https://support.hms-networks.com/hc/en-us

  Best regards,
  Peter
• 

  D2K

  • August 01, 2024 21:00

  Hi Peter,

  It's the first, that's two CAN@net in one application. The latter (starting 2 times) works okay with some safeguards.

  We have tried GUID_CANATNET2_DEVICE, COP_1stBOARD, COP_2ndBOARD. Also VCI GENERIC in one of the tests although we don't use it normally. I've summitted a support request to discuss more.

  Thanks.

  0
• 

  Peter Wucherer

  • September 02, 2024 08:18

  Hi D2K,
  
  I'd like to add here a summary for all readers:
  
  The solution was an update to version V6.3.56.2 of the CANopen Master API.
  Also, the VCI V4 drivers are now used on Windows 11.
  
  Best regards,
  Peter
  
  

  0

Please sign in to leave a comment.