Closed pavel-kirienko closed 3 years ago
This feature is needed and missing. A possible approach is to save all CAN frames into a human-readable (yet easily parseable) text file, one frame at a line, additionally extended with parsed UAVCAN message representation. For example:
RX 20:13:41.360935 1E016EF8 67 47 gG 120 110 uavcan.protocol.GetNodeInfo # <human-readable message uavcan.protocol.GetNodeInfo (request) in YAML format goes here> RX 20:13:41.413945 1E01F881 C0 . 1 120 uavcan.protocol.GetNodeInfo RX 20:13:41.414946 1E0101F8 54 A7 32 00 00 00 00 80 T.2..... 120 1 uavcan.protocol.GetNodeInfo RX 20:13:41.415946 1E0101F8 00 00 01 06 03 65 52 20 .....eR 120 1 uavcan.protocol.GetNodeInfo RX 20:13:41.415946 1E0101F8 14 04 D3 18 A0 8F 59 00 ......Y. 120 1 uavcan.protocol.GetNodeInfo # <human-readable message uavcan.protocol.GetNodeInfo (response) in YAML format goes here>
No this is a stupid idea. We need something more space-efficient.
Superseded by https://github.com/UAVCAN/yakut/issues/1
This feature is needed and missing. A possible approach is to save all CAN frames into a human-readable (yet easily parseable) text file, one frame at a line, additionally extended with parsed UAVCAN message representation. For example: