
Manually convert CAN-bus specification documents to JSON
- or -
Post a project like this£1.5k(approx. $2.0k)
- Posted:
- Proposals: 14
- Remote
- #3697906
- OPPORTUNITY
- Expired
Delivering High-Quality IT Services at Competitive Prices |Experienced Full Stack Web and App Developer |Android and IOS App Development|

489978448908865041591205060613646021557692841151650441410973147372467643949632917
Description
Experience Level: Expert
I'm looking for a technical person that can understand a highly technical CAN-bus protocol documents and extract technical details that need to be written down in JSON. Because these documents are textual, like a technical manual, creating the JSON is a manual and very tedious job.
The CAN-bus protocol documents I have specify about 500 different messages. Messages are binary and the specification defines where the data values are, how many bits/bytes they use, and which format they have.
Each message has a number of general values (e.g. message ID number, size, type, ...), followed by a variable number so called 'fields'. Examples of what type of value a field carries: voltage, speed, switch on/off, latitude, longitude, tank level, ... Also, a field can be an enumeration (like in many programming languages) that give meaning to each of the integer values of the field.
The resulting JSON file must contain an entry per CAN-bus message that specifies the message in detail. Enumerations (see above) must be specified in a separate JSON array. Field formats (e.g. integer, floating point, ...) must also be specified in a separate JSON array.
The JSON must be similar to: https://github.com/canboat/canboat/blob/master/analyzer/pgns-v2.json
It is extremely important that no mistakes are made in the conversion between CAN-bus documents and JSON file. I'd like to know how you will keep the number of errors to a minimum.
The CAN-bus protocol documents I have specify about 500 different messages. Messages are binary and the specification defines where the data values are, how many bits/bytes they use, and which format they have.
Each message has a number of general values (e.g. message ID number, size, type, ...), followed by a variable number so called 'fields'. Examples of what type of value a field carries: voltage, speed, switch on/off, latitude, longitude, tank level, ... Also, a field can be an enumeration (like in many programming languages) that give meaning to each of the integer values of the field.
The resulting JSON file must contain an entry per CAN-bus message that specifies the message in detail. Enumerations (see above) must be specified in a separate JSON array. Field formats (e.g. integer, floating point, ...) must also be specified in a separate JSON array.
The JSON must be similar to: https://github.com/canboat/canboat/blob/master/analyzer/pgns-v2.json
It is extremely important that no mistakes are made in the conversion between CAN-bus documents and JSON file. I'd like to know how you will keep the number of errors to a minimum.
Cornelis V.
100% (6)Projects Completed
6
Freelancers worked with
6
Projects awarded
44%
Last project
10 Nov 2025
Spain
New Proposal
Login to your account and send a proposal now to get this project.
Log inClarification Board Ask a Question
-
There are no clarification messages.
We collect cookies to enable the proper functioning and security of our website, and to enhance your experience. By clicking on 'Accept All Cookies', you consent to the use of these cookies. You can change your 'Cookies Settings' at any time. For more information, please read ourCookie Policy
Cookie Settings
Accept All Cookies