HyTech's CAN network definition. Every push builds a release with the generated CAN library that the firmware uses.
json_lib/messages.json— messages: name, CAN ID, DLC, and which signals they containjson_lib/signals.json— signal definitions: length, scale, offset, signedness, unitsjson_lib/enums.json— enum values referenced by signalsimported_dbcs/— third-party DBC files merged into the release as-isconversion_scripts/— scripts CI uses to turn the JSON into a DBC, proto, and C library
- Add the signals to
json_lib/signals.json. - Add the message to
json_lib/messages.json, referencing those signals by name. CAN IDs must be unique. - Check it locally:
pip install cantools==40.2.2 python conversion_scripts/json_to_dbc.py - Push. CI creates a release named
<branch>-<run number>.
Each release includes can_lib.tar.gz (C library), ht_can.dbc, ht_can.proto, and python_proto_lib.tar.gz.
To use it in firmware, point the HT_CAN entry in platformio.ini at the release:
https://github.com/hytech-racing/HT_CAN/releases/download/<release-name>/can_lib.tar.gz