Visibility of 'Vibes' in DataExplorer

[beko]

Hello,

I like to log Flightdata in my DS-14 and visualize/save it afterwords with 'DataExplorer'.
But I missed a Graph for the 'Vibes'-Parameter, that the Spirit offers. Looking in the
Logfile with an Editor, it shows a 'Vibes'-Entry in the Header also as continous 'Vibes'
Values in the log.
I figured out, when I add a Line (red marked in Pic. 1) manually in the Header

(like the one from Unilog2), DataExplorer will offer the possibility to show the 'Vibes'
Graph (gray in Pic. 2).

Is it possible to change the Jeti .bin-file in a way, that the Log File will include the
Line that i manually added? Or am I completely wrong??

Greetings from Germany

Bernd

[ZeXx86]

You have to refresh Telemetry data in the transmitter.
When updating from 1.1.0 to newer versions, this issue can happen.
Deleting Vibes and refreshing the data will fix the problem.

[beko]

Hi ZeXx86,

thank you for your quick reply, I (once more) did a Telemetry/Sensor-refresh but in the Jeti-log
(attached) I just generated, the red-marked line from first picture still not appeares. The Vibes-
Sensor was also visible in Tx before, I put the Value on Telemetrie-Display. Perhaps it is an Issue
of DataExplorer?

Greetings from Germany

Bernd

23-07-47.log

(46.64 KiB) Downloaded 656 times

Edit: I use FW 2.02 in Spirit

[beko]

... updated from 2.02 EX to 2.02, took the new spirit.bin and
refreshed Telemetry/Sensors in my DS-14 (V4.0). Still no change,
the red marked Line must be added manually to see the Vibes-
Parameter in DataExplorer.
Is there anything I can try out ?? I am helpless ...

Greets Bernd

[ZeXx86]

Hello,

now I understand your problem. It looks like DataExplorer is not able to determine data from the log, because there is missing parameter with ID 0 from unit.
Adding empty parameter with ID 0 will solve this.

Well, this could be fixed in the DataExplorer but also in our firmware. From my point of view it should be fixed rather in DataExplorer, but I guess this can take a long time.
We will fix it with upcoming version. Then all will be OK.

In the transmitter log viewer there is no problem, so you can view it without modification.

[buell47]

Well, this could be fixed in the DataExplorer but also in our firmware. From my point of view it should be fixed rather in DataExplorer, but I guess this can take a long time.
We will fix it with upcoming version. Then all will be OK.

Fantastic, thx Tomas [emoji106] [emoji4]

[beko]

Tomas, thank you very much!!

Greets Bernd

[beko]

Hello,

now I understand your problem. It looks like DataExplorer is not able to determine data from the log, because there is missing parameter with ID 0 from unit.
Adding empty parameter with ID 0 will solve this.

Well, this could be fixed in the DataExplorer but also in our firmware. From my point of view it should be fixed rather in DataExplorer, but I guess this can take a long time.
We will fix it with upcoming version. Then all will be OK.

In the transmitter log viewer there is no problem, so you can view it without modification.

Hello Tomas,
for the last 5 Years I edit the logfiles to see the Vibes-Graph in Data-Explorer. Do you see the possibility to fix it in one of the next Versions of the Spirit Integration-file? This would be great!

Greetings from Germany

Bernd

[beko]

Hi Thomas,
thanks for the new 4.0, it works great for me!
But for Years now I have to put the Sprit-Label
> 000000000;4202849569;0;Spirit; < manually
into the Jeti logfile to make the Vibes-Parameter
visible in Data-Explorer, as mentioned above.
I am dreamin' of a fix
Best Regards Bernd