DV2 Network Master #11
Labels
No labels
Core
Fixed
Godot
HardwareIssue
LEDS
Networking
Problem
SoftwareIssue
duplicate
enhancement
good first issue
help wanted
invalid
on hold
question
reminder
todo 🗒️
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
squatnet/ArduinoStuff#11
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The master device will be responsible for accepting incoming messages via bluetooth or PJON and sending those messages out to the correct device. DV2 is using dynamic addressing. The master assings an ID # to the slave, and awaits the slave registering, Registered slaves are kept in an array of structs, as mentioned in #13
The master device will most likely need to be a mega 2560 and will need to be able to parse both bluetooth messages and PJON messages these messages will be transmitted to a number of other devices via PJON softwareBitBang
Recv bluetooth and parse json - done
Due to memory constraints the decision was made to drop JSON support from DV2. The master does in fact handle the Json well. However those devices which include fastLEDs do not have sufficient memory available to reliably parse JSON.
As a result a new syntax for messages has been created using comma separated values to acheive a very similar result.
PJON master-slave auto addressing has also been re-implemented.
#34 one more off the list
Pretty sure you can knock this one on the head no?
yeah, complete with #49 and #50 which add returning arrays of ids and specifying the type as all to return all device types.