Custom CAN Bus Data Decoding Software
Budget: ₹12,500 – ₹37,500 INR
I need robust software that listens to a custom CAN bus, decodes every frame, and pushes three data classes—sensor readings, control commands, and diagnostic messages—into a database layer. The twist is that I already have part of a schema in place for legacy data, yet several new tables (or a small time-series store) will be required to house the fresh payloads you decode.
You are free to choose the stack—Python with python-can, C/C++ over SocketCAN, or even a .NET route—as long as it can sniff the bus reliably at 1 Mbit/s, map the IDs and byte offsets I’ll provide, and expose the parsed values through a clean API or direct SQL inserts.
Key milestones
• Build a translator that subscribes to the custom CAN stream and converts raw frames to human-readable JSON objects.
• Write an integration layer that inserts the JSON into my existing Postgres tables and spins up any new tables you design for the additional fields.
• Provide a straightforward configuration file so I can tweak signal scaling or add new message IDs later without recompiling.
I will supply a DBC-style mapping sheet, sample capture logs, and credentials to a staging Postgres instance. Delivery is complete when I can:
1. Plug the translator into our test bench and see live sensor, command, and diagnostic rows appearing in the database.
2. Run a simple SELECT that returns correctly scaled values identical to the reference CSV I’ll share.
Clean, well-commented code and a brief README are all I ask beyond that. If this sounds up your alley, let’s get rolling.
You are free to choose the stack—Python with python-can, C/C++ over SocketCAN, or even a .NET route—as long as it can sniff the bus reliably at 1 Mbit/s, map the IDs and byte offsets I’ll provide, and expose the parsed values through a clean API or direct SQL inserts.
Key milestones
• Build a translator that subscribes to the custom CAN stream and converts raw frames to human-readable JSON objects.
• Write an integration layer that inserts the JSON into my existing Postgres tables and spins up any new tables you design for the additional fields.
• Provide a straightforward configuration file so I can tweak signal scaling or add new message IDs later without recompiling.
I will supply a DBC-style mapping sheet, sample capture logs, and credentials to a staging Postgres instance. Delivery is complete when I can:
1. Plug the translator into our test bench and see live sensor, command, and diagnostic rows appearing in the database.
2. Run a simple SELECT that returns correctly scaled values identical to the reference CSV I’ll share.
Clean, well-commented code and a brief README are all I ask beyond that. If this sounds up your alley, let’s get rolling.