I have been carrying out some tests of SafeSky when integrated with Skydemon.
When in “flying mode” I have noticed that Skydemon displays aircraft at altitudes of 200- 300 ft LOWER than they actually are.
This is not the case for when a SkyEcho 2 is used to detect aircraft instead of SafeSky.
I have reported the issue to Skydemon Tech Support and will report back.
It may be a Safesky issue or a Skydemon one.
Keep a very good lookout…
1 Like
Good information when talking about altitudes is to mention is how did you reference your altitude? Was that based on QNH or GPS Altitude?
Usually conspicuity devices are using GPS altitude, not taking into account local pressure and temperature and if you reference it to QNH then you might see altitude differences.
SkyEcho might compensate for this. With skydemon it depends if you connect over Bluetooth or AirConnect that uses NMEA and GDL90.
How does SkyEcho 2 connect to SkyDemon and do you happen to know if SkyEcho also has a barometer inside, and thus must be used inside NOT inside pressurised cabin?
Also, does the difference in day-to-day change the altitude differences?
All appropriate corrections were made for local QNH. The SafeSky radar display is correct; it is the display in Skydemon that is wrong (low) by 200 ft.
Skydemon with my SE2 works correctly (WIFI connection) and checked outside in fresh air and also in the cabin of my 1948 vintage aircraft (non-pressurised!). Yes, the SE2 contains a baro sensor.
I believe either SafeSky is sending wrong data or Skydemon is incorrectly applying some kind of offset.
I will report back when I hear back from Skydemon.