I am looking for a solution as to how to get a home-brewed analog sensor back through FRsky s.port telemetry at a reasonably quick refresh rate. Any thoughts?
I currently have it all setup and running on an x4r-sb going into the A2 port. It works well, but does not refresh as quick as I would like. I was hoping that by using the CELS value in the flight controller, but it refreshes just as slow as the A2 port and is controlled but the RX software (if I understood correctly).
If i look at some of the other sensors communicating through s.port, I feel there should be a solution as values like "hdg" and "accx" refresh fast enough.
In looking through the other ADC usages, hoping to find a faster telemetry path, I found that the airspeed can both read an ADC and in the FRsky s.port protocol seems to refresh much faster (as fast or faster than "hdg" and "accx".
With this in mind, I tried to just pass ADC2 through the ASPD module and it did not work.
tracernz was kind enough to look into it quickly (while they were trying to complete the "wired" release) and thought that the ASPD calibration might have been causing an issue with just getting the raw data from the sensor. He attempted a quick "hack" (PR2063 https://github.com/d-ronin/dRonin/pull/2063) which showed a very small sign of life but mostly returns zeroes.
1) Does anyone have any better thoughts how to get this to work?
Is there a way to "fake out" the airspeed calibration?
2) Is anyone willing to take a look at PR2063 and see if it works for you?
3) any other thoughts?
Thank you in advance!!!
TX: X9D+ or QX7
Sensor: Home built Analog output of 0-3.3V