2 Commits

Author	SHA1	Message	Date
Lucas De Marchi	66a1e420cb	AP_HAL_Linux: RCInput_SoloLink: better name to first field ... Checking the time on the tcpdump capture, it matches the first fields from the data: $ tshark -n -c 4 -r ~/tmp/solo/rc.pcap 1 0.000000 10.1.1.1 → 10.1.1.10 UDP 68 5005 → 5005 Len=26 2 0.019976 10.1.1.1 → 10.1.1.10 UDP 68 5005 → 5005 Len=26 3 0.040046 10.1.1.1 → 10.1.1.10 UDP 68 5005 → 5005 Len=26 4 0.059961 10.1.1.1 → 10.1.1.10 UDP 68 5005 → 5005 Len=26 From the previous commit (first 2 packets): 5fa8 f441 3414 0500 73d7 dc05 dc05 dc05 db05 e803 e803 e803 f401 73f6 f441 3414 0500 74d7 dc05 dc05 dc05 db05 e803 e803 e803 f401 0x0005143441f45fa8 - 0x0005143441f4f673 = 0x4E14 = 19988 (usec) Which seems to approximately match for the other packets as well. We are not using the field since we rather get the time when we receive it, but at least use a better name.	2017-08-17 12:04:27 -07:00
Lucas De Marchi	79b004cf6a	AP_HAL_Linux: add prototype for handling SoloLink ... This allows to use a Solo controller to control Linux-based flight controllers. The protocol has been derived by analyzing a tcpdump trace: some fields are ignored. Example trace of RC data (obtained with `tshark -T fields -e data -n -c 5 -r rc.pcap` unkonwn seq ch1 ch2 ch3 ... ch8 5fa8 f441 3414 0500 73d7 dc05 dc05 dc05 db05 e803 e803 e803 f401 73f6 f441 3414 0500 74d7 dc05 dc05 dc05 db05 e803 e803 e803 f401 dc44 f541 3414 0500 75d7 dc05 dc05 dc05 db05 e803 e803 e803 f401 bc92 f541 3414 0500 76d7 dc05 dc05 dc05 db05 e803 e803 e803 f401 dfe0 f541 3414 0500 77d7 dc05 dc05 dc05 db05 e803 e803 e803 f401	2017-08-17 12:04:27 -07:00