search

rbei-etas / busmaster

BUSMASTER is an Open Source Software tool to simulate, analyze and test data bus systems such as CAN. BUSMASTER was conceptualized, designed and implemented by Robert Bosch Engineering and Business Solutions (RBEI). Presently it is a joint project of RBEI and ETAS GmbH.
http://rbei-etas.github.com/busmaster/
GNU General Public License v3.0
951 stars 502 forks source link

Node simulation and Transport Protocol transfers #261

Closed mlowrie-seastar closed 12 years ago

mlowrie-seastar commented 12 years ago

Our J1939 product utilizes the transport protocol to send multi-byte data but Busmaster has strange behaviour with handling the transport protocol.

A manual attempt to retrieve proprietary PGN which will utilize transport protocol is shown below vs what occurs with node simulation

Manual attempt:

Our device claims address 0x44 14:27:01:6230 1 18eeff44 0x00EE00 ACL 44 FF 006 Rx 8 FF FF 5F E7 00 32 00 90

Busmaster J1939 brought online, claims address 00 14:27:04:4779 1 18eeff00 0x00EE00 ACL 00 FF 006 Tx 8 01 00 00 00 00 00 00 80

Busmaster transmit window used to claim address 26 14:27:18:8023 1 1ceeff26 0x00EE00 ACL 26 FF 007 Tx 8 01 00 00 00 00 00 00 80

Busmaster transmit window used to request a PGN: To 0x44 for PGN FEDA (proprietary PGN which utilizes transport protocol) 14:27:29:1083 1 1cea4426 0x00EA00 RQST 26 44 007 Tx 3 DA FE 00

Our device send RTS 14:27:29:1160 1 1cec2644 0x00EC00 RTS 44 26 007 Rx 8 10 21 00 05 03 DA FE 00

Busmaster does not respond with anything and our device aborts 14:27:30:3631 1 1cec2644 0x00EC00 CON_ABORT 44 26 007 Rx 8 FF 03 FF FF FF DA FE 00

Now, with node simulation: J1939->Configure->Simulated Systems Add Simulated system Add a node set to address 0x26 and whatever ECU name Save simulated system - no files, no code, no DLL, nothing active in node simulation

Our device claims address 0x44 14:32:55:5362 1 18eeff44 0x00EE00 ACL 44 FF 006 Rx 8 FF FF 5F E7 00 32 00 90

Busmaster J1939 brought online, claims address 00 then automatically claims address 26 - same address setup in node simulation 14:34:28:5647 1 18eeff00 0x00EE00 ACL 00 FF 006 Tx 8 01 00 00 00 00 00 00 80 14:34:28:5655 1 18eeff26 0x00EE00 ACL 26 FF 006 Tx 8 00 00 00 11 00 00 00 80

Busmaster transmit window used to request a PGN: To 0x44 for PGN FEDA (proprietary PGN which utlizes transport protocol) 14:34:35:6494 1 1cea4426 0x00EA00 RQST 26 44 007 Tx 3 DA FE 00

Our device send RTS 14:34:35:6543 1 1cec2644 0x00EC00 RTS 44 26 007 Rx 8 10 21 00 05 03 DA FE 00

Busmaster automatically send a CTS but incorrectly sends 11 03 00 instead of 11 03 01. 14:34:35:6556 1 1cec4426 0x00EC00 CTS 26 44 007 Tx 8 11 03 00 FF FF DA FE 00

Busmaster does not respond and our device aborts 14:34:36:1520 1 1cec2644 0x00EC00 CON_ABORT 44 26 007 Rx 8 FF 03 FF FF FF DA FE 00

So a few questions:

  1. Does Busmaster not handle transport protocol without node simulation?
  2. What is causing the incorrect CTS message to be sent?
  3. How can I utilize Busmaster with the transport protocol?

Thanks, Mike

RBEI-ArunKumar commented 12 years ago

The issue is addressed with ver 1.6.8 release.