01-24-2024, 12:21 PM
The binding is interrupted constantly due to an oversight in the firmware (discovered right after the very first release). There has to be 100 frames in a row that are successfully sent to the receiver where the receiver also ACK's the reception of the packet. If all 100 in a row occur without a single error then the binding completes. If there is a retry then the process is started over. The bug is that the transmitter module's PPM interrupt is still left in place, so that interrupts the transmission of the data and depending on many factors can cause a retry. The interrupt was left enabled to give some actual time to see the LED flicker indicating a bind was occurring. This worked but also allowed for interruption in the ACK portion of the response packet. Eventually it goes through.
The transmitter's ID, frame rate, and number channels are stored in the receiver during the binding process.
The transmitter's ID, frame rate, and number channels are stored in the receiver during the binding process.

