AUBRIX.SYSTEMS
Back to engineering archive

Record 095 / Connected systems

Stored CAN-frame sender draft

An archived application parses stored CAN-frame text, attempts sends through MCP_CAN and toggles a single NeoPixel indicator.

Incomplete archived draft
CAN transmissionMCP_CAN APINeoPixel indicator

Archived source flow

Selected stored-frame path: skip empty lines, parse a non-empty stored line, attempt CAN send and toggle one indicator pixel. End-of-data returns to the main loop delay before restarting. No received-CAN effects, applied per-frame timing or successful delivery is established.
Stored-text send path reconstructed from archived source. The status pixel does not confirm delivery. Required frame data is absent, and build and bus operation are unverified. View diagram at full size

Technical notes

Stored frame parsing

SendCanMessage() walks the stored data text. processCanData() parses a non-empty line into an identifier, DLC and payload, then calls sendMsgBuf(). It is not a received-CAN command handler.

Indicator and repetition

One NeoPixel alternates between red and off after a send attempt. The return status is not checked. After the stored text ends, the loop delays 50 ms and starts the stored sequence again; parsed per-line dataDelay is not applied.

Incomplete and unchecked inputs

The referenced data.h is absent from the matched source folder. DLC is not bounded before filling an eight-byte buffer. The draft does not establish LED-effect commands, preserved frame timing or successful CAN delivery.

Engineering archiveArchive record

Project enquiries

Discuss your project.

Tell us what you’re developing and where you need engineering support.

Discuss your project