Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Too many Sensor Lost Messages – Solution? #2684

Closed
capraf opened this issue Jun 12, 2023 · 20 comments
Closed

Too many Sensor Lost Messages – Solution? #2684

capraf opened this issue Jun 12, 2023 · 20 comments
Assignees
@bsongis-frsky
Labels
enhancement New feature or request
Milestone
1.5.0

Comments

@capraf
Copy link

capraf commented Jun 12, 2023

In order to find out the reason for the “Sensor Lost” messages, I tried the following: During the flights, I set a time stamp in my X20S at each time, the „Sensor Lost“ Message occurs. After that I checked the LOG-fieles at these times.

At each of these times, I found empty fields for a sensor which is of the reason for the Message. But surprisingly the time at which no sensor data is received, is in the range between 500ms and 3 seconds. As the „Sensor Lost Warning Delay“ (Telemetry Menu) was set to 10 seconds, there should be no “Sensor Lost” Message.

As far as I can see, the number in „Sensor Lost Warning Delay“ is not used correctly. Could this be the reason for the many „Sensor Lost“ Messages?
@yak-54
Copy link

yak-54 commented Jun 12, 2023 •
edited

are you using Archer R8Pro ?

@capraf
Copy link
Author

capraf commented Jun 12, 2023 via email

@dap35
Copy link

dap35 commented Jun 12, 2023

Which sensor is dropping data? For some, such as the GPS time, I would turn of the sensor lost notification.

@mawzthefinn
Copy link
Collaborator

Have you tried the latest Archer firmware? 2.1.12 is current

Andy what TD-ISRM firmware (2.2.2 or 2.2.4 would be current)

@capraf
Copy link
Author

capraf commented Jun 12, 2023

Thanks for the idea - but I know most of the discussions and I don't want to start a new one.
I just want to ask Bertrand and his team, if there could be an error in the programming of the "Sensor Lost Warning Delay" parameter.
E.g.: In a LOG file were 20 fields of an "UniSens E" Sensor missing - that is a timeframe of about 2.5 seconds. This is an error or a bug and should not happen.

@capraf
Copy link
Author

capraf commented Jun 12, 2023

I will try the 2.1.12 if I have time again.
But I think that the X20S has a problem. It should not send a "Sensor lost" massage, if there is gap of 2.2 seconds and the "Sensor Lost Warning Delay" is 10 seconds.

@mawzthefinn
Copy link
Collaborator

If you are using an Unisens-E there is a known issue with out of bounds values causing sensor lost warnings, which requires a firmware update on the Unisens-E to solve

@yak-54
Copy link

yak-54 commented Jun 13, 2023

does the rssi get low in the logs as well ?

@capraf
Copy link
Author

capraf commented Jun 13, 2023

@yak-54: rssi is ok. During that time it is between 48db and 51db.

@capraf
Copy link
Author

capraf commented Jun 13, 2023

@mawzthefinn: UniSens-E is up to date...

@bsongis-frsky
Copy link
Collaborator

Can you attach your logs please? I don't think there is an issue with the warning delay.

@capraf
Copy link
Author

capraf commented Jun 13, 2023 via email

@capraf
Copy link
Author

capraf commented Jun 13, 2023 •
edited

@bsongis-frsky
here is the log-file
Marabu-2023-06-11-09-52-40.csv

@capraf
Copy link
Author

capraf commented Jun 27, 2023

I checked this with a new model.
There are also empty fields which produced 2 "Sensor lost" messages at:

  1. time 11:47:04.950 (only one entry)
  2. time 11:53:46.920 to 11:53:48.830 (only about 2 seconds)
    Configuration:
    X20S, FW 1.4.9, HF-Modul-FW 2.2.4
    SR8 PRO, FW 2.1.12
    Sensor 1: YGE 95LVT (the error messages came from address 12 0601 and / or 12 600
    Sensor 2: GPS Modul 3 (nor Error from this sensor)
    I hope, this helps.
    Edge-2023-06-25-11-41-10.csv

@glipski50
Copy link

glipski50 commented Jul 25, 2023 •
edited

I can confirm capraf's / Friedhelms observation.

I did several tests today with different configurations:
X20, int. HF Module, Archer R6, Type ACCESS
X20, ext. HF Module TWIN Lite Pro, Archer R6, Type ACCESS
X20, ext. HF Module TWIN Lite Pro, TWIN R6, Type TWIN
X20 and receivers all with the most actual firmware

Sensor was a Unisense E (with most actual firmware with AppID offset) and GPSLogger 2. The sensor lost announcement delay was set to 5 sec.

I have received for all configurations the sensor lost error message. I did all those test on a bench outside (for GPS signal) and I stopped logging after the error message came up in order to make sure that this missing data i.e. sensor loss was triggering the error message. Here some examples of the AppID's

0E 0830 - GPS Geschwindigkeit
14 0101 - Flughöhe
0E 0700 - AccX

This screenshot with a TWIN R6 shows the missing data (i.e. sensor lost) that triggered the error message. The sensor was lost for about 1 - 1.4 sec and should not have triggered the error message since the sensor lost announcement delay was set to 5 sec.

Sensor verloren

The write intervall for the TWIN R6 is 250 ms.

The sensor data (i.e. sensor lost) is for about 1 - 1.5 sec. Since the delays for the individual sensore are set per default to 5 sec the error message should not had coma up at all.

Here are two short logfiles , the write intervall for the R6 ACCESS is 100 ms, the write intervall for the TWIN R6 was set to 250 ms, the fileds with the missing data are marked red.

Sensor lost.xlsx

I support Friedhelms question to Bertrand and his team to revisit the sensor lost settings for correct function.

@Target0815
Copy link
Contributor

@glipski50 : the time frame without value is short and does not reach the 5 seconds default setting, but no value changed for several seconds before the data was lost. IMHO this is taken into account in the timeout for the message.

@capraf
Copy link
Author

capraf commented Jul 26, 2023

@Target0815 : it will happen very often that no values will change for a long time.
e.g.

  • during Motor Stop the number of revolutions will be zero (glider with brake)
  • position of GAS signal
  • ESC Temp.

@github-actions github-actions bot added the Stale label Oct 25, 2023
@capraf
Copy link
Author

capraf commented Oct 30, 2023

Unfortunately I can't test this as the respective Airplane was sold.
I didn't find any entry in the release information of the last Ethos releases up to Ethos 1.4.13 - so I didn't know if there were changes regarding the "Lost Sensor" error message.

@github-actions github-actions bot removed the Stale label Oct 31, 2023
@github-actions github-actions bot added the Stale label Jan 30, 2024
@bsongis-frsky bsongis-frsky added enhancement New feature or request and removed Stale labels Jan 30, 2024
@bsongis-frsky bsongis-frsky self-assigned this Jan 30, 2024
@FrSkyRC FrSkyRC deleted a comment from github-actions bot Jan 30, 2024
@FrSkyRC FrSkyRC deleted a comment from github-actions bot Jan 30, 2024
@bsongis-frsky
Copy link
Collaborator

Improved in 1.5.0 in increasing the default delay before the Sensor Lost warning

@bsongis-frsky bsongis-frsky added this to the 1.5.0 milestone Jan 30, 2024
@yak-54
Copy link

yak-54 commented Jan 30, 2024

thanks

@glipski50 glipski50 mentioned this issue May 10, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bsongis-frsky bsongis-frsky

Labels
enhancement New feature or request
Projects
None yet
Milestone
1.5.0
Development

No branches or pull requests
7 participants
@yak-54 @dap35 @Target0815 @mawzthefinn @bsongis-frsky @capraf @glipski50