Skip to content

Validate XBee serial --> backend --> React dashboard live data path #73

@ethancoon

Description

@ethancoon

What we need before race day is proof that live XBee serial output can make it all the way into the React race dashboard.

Add a simple end-to-end test path for the radio pipeline using the existing XBee serial format, so we can confirm that when lines like

DEBUG ... Sent CAN message with ID 0x406 Length 6 Data 0x204e040100c0

come in over serial, they are parsed, pushed through the backend queue/consumer flow, and result in visible updates on the race dashboard.

  • Reuse radio_producer.listen_to_radio() and parse_radio_line() as the entry point for live serial radio data
  • Confirm the parsed (id, data) frames are reaching consumer.add_to_queue(...)
  • Trace where those queued frames get processed into whatever Socket.IO event the race dashboard is listening for
  • React dashboard received update
  • If needed, create a small “fake radio input” mode that feeds sample lines in the exact XBee text format, so we can test without depending on live hardware every time
  • Keep this focused on proving the current pipeline works, not on refactoring the whole dashboard/backend architecture

In English: LTE is probably not going to happen before the race, so we're going to use the serial XBEE RF modules instead. I believe the way Embedded has it set up is that it just straight up sends the log message, but the radios are not currently working so just effectively hijack the script with valid debug statements to see if it propogates to the React dashboard.

IF YOU NEED DEBUG STATEMENTS, CHECK HERE IN THE DRIVE

Metadata

Metadata

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions