PhoenixPilot/PhoenixPilot — pull request #26 by elafargue (2012-11-27 02:36:25+00:00)
Title: UAVTalk: put all transaction tracking inside the "telemetry" layer

Uavtalk now just sends ACK/NACK to telemetry without tracking transactions, and Telemetry.cpp follows its own transactions. Very reliable on my machine, removed a lot of crashes linked
to transMap in uavtalk. No loss of functionality.

Let me know how this works on your machines. I have tested on:
- USB with CC3D
- USB to PipX - Radio - PipX-CC3D with good and bad link (further testing ongoing)
- Objects requests, updates
- Multiple connect/disconnect
- USB plug/unplug

Transactions are still tracked and multiple transactions are still possible, but all managed by the telemetry layer, not the protocol layer. removes quite a lot of complexity from the uavtalk layer.

Please test & report!