Supporting Tx/Rx message direction for each interface #776

Activity

1. bessman commented on Feb 24, 2020

   

   bessman

   on Feb 24, 2020

   Contributor

   More actions

   How should receive_own_messages behave with this change? Should messages transmitted by other applications have is_rx=False?

   I'm looking at Kvaser's canlib, and I can see no obvious way to accomplish that.
2. tamenol commented on Feb 27, 2020

   

   tamenol

   on Feb 27, 2020

   Contributor

   More actions

   I was looking to implement this for the PCAN bus. However I can't seem to find a variable in the PCANbasic library I could use to check if it's RX or TX. Someone has an idea?

   TPCANMessageType only has these values:

   # PCAN message types
   PCAN_MESSAGE_STANDARD = TPCANMessageType(
       0x00
   )  # The PCAN message is a CAN Standard Frame (11-bit identifier)
   PCAN_MESSAGE_RTR = TPCANMessageType(
       0x01
   )  # The PCAN message is a CAN Remote-Transfer-Request Frame
   PCAN_MESSAGE_EXTENDED = TPCANMessageType(
       0x02
   )  # The PCAN message is a CAN Extended Frame (29-bit identifier)
   PCAN_MESSAGE_FD = TPCANMessageType(
       0x04
   )  # The PCAN message represents a FD frame in terms of CiA Specs
   PCAN_MESSAGE_BRS = TPCANMessageType(
       0x08
   )  # The PCAN message represents a FD bit rate switch (CAN data at a higher bit rate)
   PCAN_MESSAGE_ESI = TPCANMessageType(
       0x10
   )  # The PCAN message represents a FD error state indicator(CAN FD transmitter was error active)
   PCAN_MESSAGE_ERRFRAME = TPCANMessageType(
       0x40
   )  # The PCAN message represents an error frame
   PCAN_MESSAGE_STATUS = TPCANMessageType(
       0x80
   )  # The PCAN message represents a PCAN status message
3. chrisoro commented on Jun 22, 2020

   

   chrisoro

   on Jun 22, 2020

   Contributor

   More actions

   @hardbyte @pierreluctg
   any indication when you release a version based on the develop branch? this feature is really interesting for us (vector devices for now)
4. felixdivo

   added

   api

   enhancement

   on Apr 23, 2021