Flysky Vario Support

The datalog can be confusing but without ftdi it's the best chance to get more debugging data. I uploaded a test build with some code to put the raw sensor data in telemetry that can be logged by datalog ( 772b430 ). I don't have a t8sg_v2 but tested logging with the emulator and it worked fine. Here's how to set it up for this test build. If this still doesn't get you there I can make a screen cap:

1. In Model Menu select your model in Model Setup, and then navigate to Datalog.

2. Set the enable to None while making the rest of the changes.

3. Scroll down one to Reset and select to clear out any current saved data.

4. Scroll down to Select, change to None, select to turn all logged values to Off.

5. Scroll down to TelemT1 and select to change to On.

6. Scroll down to Alt and select to change to On.

7. Scroll back up to Enable, select a switch not used in your model, and enable it. You can do this by just moving the switch you want to use.

Observe the "bytes left" number going down. Check the Telemetry Monitor to ensure values are showing in the Temp and Alt fields. The numbers will be meaningless but will confirm telemetry data is being logged.

After 10 seconds or so of receiving telemetry data, disable the logging. Copy the datalog.bin file from the tx and post it here please.

Thanks!

Could you have a look on my previous message?

For this test shoul only the altitude sensor be connected, or both together with voltage sensor?

I hadn't seen that. The CP2102 should work. Though the datalog might be easier and is worth a try.

A cable to connect to the trainer port is needed. It's a 3-conductor audio jack but a two conductor plug will work. Connect tip from the trainer port to the RX pin on the CP2102. Connect the outer ring to the ground pin.

The CP2102 will show up as a serial port on the PC where you plug it in. You'll need some serial interface program to capture the data coming in. Which program depends on your operating system. On Windows I use an old program called Realterm but other options are out there.

ballbear wrote: For this test shoul only the altitude sensor be connected, or both together with voltage sensor?

Only the altitude sensor should be connected.

OOOPs, I did it with both , so I will repeat it again.
The datalog with both connected is here ....

Second test with only Altitude sensor connected. About 5 sec after start I lifted the sensor 40cm up and than back down and after that it was at least ten second in one level ...

One question - can I use this test build for flying with the plane or would be better to go back ?

Couldn´t the FTDI adapter be connected directly to the altitude sensor?

ballbear wrote: One question - can I use this test build for flying with the plane or would be better to go back ?

It's fine to use, just the altitude and telemetry numbers won't be correct.

ballbear wrote: Couldn´t the FTDI adapter be connected directly to the altitude sensor?

The sensor has to be polled for data, and runs half duplex. You'd need circuit and software to talk to it with the ftdi.

The datalog data is good. The telemetry values look reasonable. The t8sg is accurately displaying the data received. I wrote some separate code on a pc to interpret the datalog data and got the same results as the t8sg code. Files attached.

It's interesting the altitude values are so different when the voltage sensor is also attached. I don't think there should be any interaction. Do the sensors get enough power?

The reported altitudes in both cases are not close to the real value of 230m. Is there any calibration procedure for the sensors?

I've uploaded a new test build with the normal telemetry restored ( 9776608 ). I did change so no ground level is set - the altitude is reported as ASL. That may make it easier to figure out what's going on.

At about 5:45 there is how the altitude setting is made
About calibration of the sensor I didn´t found nothing yet.

I made new tests with the previous TestBuild, same like you get the datalogs, but this time with BEC switched to 6 Volts.
I am curious, if there will be some difference.
Like last time, the first test is done with both sensors connected, ( datalog6V ) and the second with only altimeter ( datalog6V2 )

I am going to try next thing : I try to get the pressure info from my SUUNTO watches
Have a nice day
Pavel

I was not allowed to add the zip files, so next trial now
Six mean six volts

Now we have here 983 mBar air pressure.

Here is datalog made with the last version, at beginning both sensors connected, after twenty sec the voltage sensor was disconnected ...Actual pressure 981 mBar,

The last file doesn't seem to contain valid data.

The two 6V files are interesting. The air pressure shows a lot of variation. In the 6V file the minimum pressure is 960.64 mBar and maximum 964.37, corresponding to altitudes of 415m and 447m. The pressure somewhat trends higher over the duration of the file.

The 6V2 data looks better. Minimum mBar 962.99 (435m) to maximum 981.26 (270m). Also the pressure steadily increases over the duration.

Everything looks fine as far as receiving and processing the data from the sensor. The reported pressure isn't very stable. Do you have a way to try this sensor with a non-Deviation tx to compare?

I tried to make another datalog with the last Test Build.
It started before binding the receiver and with only altitude sensor connected.
The air pressure according Suunto watches was 977mBar, temperature according this watches 21 Celsius.
Test was done with 6V from BEC. The sensor wasnť moved.
Unfortunatelly I don´t have possibility to test the sensor with FlySky transmitter. I will ask coleagues from club if somebody is using usefull transmitter.
Next way is to order second sensor. ...

Interesting the altitude kept decreasing the whole time, right through the correct value.

Could there be influence from the receiver?
I can make test with second receiver ...