search

cmengler / pidflight-lap-firmware

PIDflight Lap Timing device firmware
GNU General Public License v3.0
14 stars 7 forks source link

API details for the serial? #2

Open eried opened 4 years ago

eried commented 4 years ago

I think a scanner would be awesome, like: turn drone off, press next, turn drone on, press next> drone found on: xx type of thing. Instead of reading the code, do you have some documentation on the serial commands?

cmengler commented 4 years ago

I had started this awhile ago -- https://wiki.pidflight.com/pidflightlap:protocol -- however I'm planning to move the effort to either GH wiki pages or version markdown files in the primary https://github.com/cmengler/pidflight-lap repo shortly :)

cmengler commented 4 years ago

I'll continue to effort on this page -- https://github.com/cmengler/pidflight-lap/wiki/Serial-Protocol

eried commented 4 years ago

Awesome! https://wiki.pidflight.com/pidflightlap:protocol I guess for VT the device just answers with more ids :P great!

I am not sure if I should make the ESP32 version as a PR here or as a separate fork, because the many differences I notice I will need to implement everything. What you think?

i.e. 1) The RSSI measurement needs to sample 2 analogs (the input battery) because 5V is actually 4.2 to 3.8 (depending on the lipo). I need to see how that will work with 4VT 2) The SD card "logger" 3) Wifi/BT will be implemented on the firmware, not as a module

cmengler commented 4 years ago

Correct! VT acts the same way as chained physical devices :)

Sweet, I'll take a look at your commits in your repo during the week and see if it can be merged. I still have a ESP32 dev board lying around which I'll test with too.

eried commented 4 years ago

It always could be merged :D maybe you should leave 2.7 as the final version for the "legacy" and move on to a cleaner solution. Drop support for all the other inferior boards an embrace the future of a super compact ESP32 based timer

image

cmengler commented 4 years ago

That's a very good point! Impressive build -- do you mind if I share this on the socials with credit to you of course! :)

eried commented 4 years ago

Sure! But I am waiting for 4VT still :P

dvmourik commented 3 years ago

Is there still progress on this project? I build a ESP version of Eried... but seems i don't have any RSSI signal. Can i debug this anyway?

Edit: Found solution. The resistor bridge is not working well. I removed the resistor to GND and it works. Probably not the best solution but i can now know the 5808 is working.

eried commented 3 years ago

We need to implement the 4VT on the ESP, which has enough power for switching super fast and doing all :)

tonarec commented 2 years ago

Hi! I really love the project and I would like to contribute to it! 😄 I'm currently looking to create an external module plugged into the radio-command to act like a device that just listen what's happening from the laptimer devices (for the moment), inspired by this Taranis ESP32 module. If I understand correctly the purpose of the MSP protocol, each device (chained on serial) have to process the MSP command or pass it to the next device. Is that correct ? In that case, what is the role of the WiFi/Bluetooth serial module ? I'm wondering what the Android app is doing, but I don't have find any code of it.

cmengler commented 2 years ago

Cheers @tonarec ! That idea sounds interesting.

A slightly modified version of the MSP protocol was adopted for this project to send/receive data from the lap timer and pass through a message to another timer in the chain.

This might be a good starting point to reference the available MSP commands and what the byte payloads are -- https://github.com/cmengler/pidflight-lap-gui/blob/master/src/js/pidflight/msp.js

I also started documenting the protocol sometime ago, however I never got to complete it -- https://github.com/cmengler/pidflight-lap/wiki/Serial-Protocol

Feel free to let me know if you have any questions:)