Details
-
Bug
-
Resolution: Done
-
P1: Critical
-
Some future release
-
None
Description
Yes, really. It only sends and receives CANFD frames. If connected to a device talking CAN it rejects all packets as invalid because it receives packets of CAN_MTU (i.e. 16), but expects CANFD_MTU (i.e. 72). The "canbusutil" tool pretends to be able to send CAN messages, but the information if the message is CAN or CANFD is only used to check the payload length, but it is not passed down to any backend.
While at it: the CAN_RAW_FD_FRAMES setting should not be hardcoded to 1, this should be a user option.
Attachments
| For Gerrit Dashboard: QTBUG-49675 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 143506,3 | Linux/SocketCAN: Permit the reading of 16 byte and 72 byte can frame MTUs | 5.6 | qt/qtserialbus | Status: MERGED | +2 | 0 |
| 143507,6 | Linux/SocketCan: Fix writing of simple and extended can frames | 5.6 | qt/qtserialbus | Status: MERGED | +2 | 0 |
| 144137,6 | QCanBusFrame: add flag to identify CANFD frames | 5.6 | qt/qtserialbus | Status: ABANDONED | -1 | 0 |
| 144240,6 | QCanDevice: add CanFdKey configuration option | 5.6 | qt/qtserialbus | Status: MERGED | +2 | 0 |
| 176504,6 | QCanBusFrame: add flag to identify CAN FD frames | 5.8 | qt/qtserialbus | Status: MERGED | +2 | 0 |