You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is currently used to track a set of features and improvements for using the ExpressLRS backpack ecosystem in a racing environment. Discussions and/or suggestions are welcome and encouraged.
Reduce the distance required between the timer backpack and the pilots' backpack
ELRS Netpack allows for a backpack connection over ethernet instead of a serial connection
Address OSD over backpack stalling
OSD generated from the backpack is known to freeze after extended use occasionally. The root bug(s) of this could be in either the backpack ecosystem or the HDZero goggle firmware
Separate addressing based on device type (change last octet of generated UID to match device type)
Move each backpack device to their own address so the ESPNOW message sent callback returns an accurate send success status. Currently, the Tx backpack can report successfully receiving an OSD message from Timer backpack
Potentially assign the timer backpack to a single mac address and allow the Tx and VRx to bypass filtering packets that address. This would the timer backpack to send a message to each peer without having to adjust its own address. Also enable simultaneously sending messages to multiple peers from the timer backpack at once.
Without the change, 5-10% of packets have been lost in a bench test with multiple devices with the same receiving uid powered on. Drops down to 0% with only one device with the receiving uid powered on. The test uses the ELRS netpack as the sending device (packet transmitted up to 5 times or until send successful).
Add a menu to the VRx backpack web page to allow for customizing their race OSD
Send race data packets from the Timer backpack to be assembled into full OSD packets by the VRx backpack. The full packet would then be sent to the goggles.
Pilot Ready Status
Add another switch like the one used for DVR Rec for pilots to indicate if they are ready to race. The change in status would be captured by the timer backpack
Currently expecting that this message would be broadcasted over espnow instead of using unicast like other messages typically do. This would allow for timer backpacks to receive the message without having to be registered as a peer.
Channel Control from Timer (Controversial/Lowest Priority)
Set pilot's video channels from the backpack. Issues could arise with unexpected video loss if this is implemented. This will likely only be pursued if there is enough demand and users understand the risks this could cause.
This issue is currently used to track a set of features and improvements for using the ExpressLRS backpack ecosystem in a racing environment. Discussions and/or suggestions are welcome and encouraged.
Reduce the distance required between the timer backpack and the pilots' backpack
Address OSD over backpack stalling
Separate addressing based on device type (change last octet of generated UID to match device type)
Customizable Race OSD
Pilot Ready Status
Channel Control from Timer (Controversial/Lowest Priority)