Parcourir les catégories
Explorer
Fiverr Pro
Français
$
USD
I will develop can bus firmware for industrial embedded systems
Embedded Systems Engineer Specializing in Firmware and PCB Design
Hi, I’m Prageeth, I develop embedded firmware and design custom MCU PCBs for industrial, robotics and electronic projects. My work includes C/C++ firmware, STM32 peripherals, CAN bus communication, Ki...
À propos de ce service
Need CAN communication for an industrial controller, machine, robot or embedded product?
I develop focused CAN firmware for engineers, hardware startups and product teams.
I can implement:
- CAN configuration, bit rate and acceptance filters
- TX/RX handling and message parsing from your specification
- Periodic and event-driven messages
- Timeout, node-status and basic error handling
- Integration into existing C, STM32 or RTOS projects
- Source code, build notes and verification checklist
Best fit: A defined MCU/board, CAN transceiver, toolchain, message IDs and expected behavior. Provide a DBC or protocol document if available.
Before ordering, message me your MCU, CAN hardware, bit rate, ID format, message count, project files and acceptance criteria.
Packages cover standard CAN 2.0. CAN FD, CANopen, J1939, ISO-TP/UDS, bootloaders and safety-critical or certified systems require separate review and quotation. Physical testing requires suitable hardware access or reliable logs.
PCB design and mobile/desktop apps are excluded.
Mon portfolio
Autres services de Ingénierie électronique I Offre
FAQ
What types of CAN bus firmware do you develop?
I develop standard CAN 2.0 firmware for supported embedded microcontrollers, including message transmission and reception, message parsing, periodic messages, and basic timeout or communication-error handling.
Which microcontrollers do you support?
This Gig is primarily focused on STM32. Please send your exact MCU or development board, toolchain, and existing project details before ordering so I can confirm compatibility.
Do I need to provide a CAN message matrix or DBC file?
Please provide your message matrix, DBC file, or a written specification with CAN IDs, standard or extended identifiers, message lengths, signal layouts, byte order, scaling, and transmission periods. If you do not have one, contact me before ordering.
What is included in each package?
Basic covers up to 3 CAN message IDs, Standard covers up to 8, and Premium covers up to 15 for one CAN node. The exact deliverables and testing depend on the selected package and the information you provide.
Do you support CAN FD, CANopen, J1939, or UDS?
These are not included in the standard packages. They require separate technical review and a custom offer because their protocol requirements and testing scope differ from basic CAN 2.0 messaging.
Do you need my existing firmware project?
For integration into existing firmware, yes. Please provide the relevant source files, project configuration, MCU details, and build instructions. If you need a new standalone project, contact me first to confirm the scope.
Will you test the firmware on physical hardware?
Physical hardware testing is not automatically included. I can perform appropriate source-level, build, and software-based checks when the project supports them. Hardware validation required remote testing and agreed test scope.
What files will I receive?
Depending on the package, you will receive the agreed firmware source code, relevant project changes, setup or build instructions, and documentation. I will state clearly which checks were completed and which were not.
What counts as a revision?
A revision covers reasonable changes to the agreed deliverables within the original scope. New features, additional CAN IDs beyond the package limit, a changed protocol, or a different hardware platform may require an extra or custom offer.
Can you guarantee production-ready or safety-certified firmware?
No blanket guarantee of production readiness or safety certification is included. I deliver work against the agreed requirements and report the checks performed. Formal certification, safety analysis, and production qualification require a separate scope.
