Messages with DLC = 0 and no data in the payload (but no flags) were not being published. These messages are valid and were being passed by kvaser_interface up to ROS, then silently dropped. This is undesired behavior. The CAN bridge now passes these messages but drops CAN FD (not supported by can_msgs/Frame), TX ACK, TX RQ, Message Delay notifications, and TX NACK messages. These are informational-only messages and cannot be correctly represented by can_msgs/Frame anyway.
Messages with DLC = 0 and no data in the payload (but no flags) were not being published. These messages are valid and were being passed by kvaser_interface up to ROS, then silently dropped. This is undesired behavior. The CAN bridge now passes these messages but drops CAN FD (not supported by
can_msgs/Frame), TX ACK, TX RQ, Message Delay notifications, and TX NACK messages. These are informational-only messages and cannot be correctly represented bycan_msgs/Frameanyway.