v9.3

New features

In this version the altitude data from local GPS and altitude data from Telemetry are treated as relative altitude regardless of the origin of the data (Barometer or GPS). It is intended to prevent undesirable behaviors when local GPS is used (absolute altitude) and the source of the altitude is the barometer of the aircraft (relative altitude). For example when using LTM telemetry with iNav we had to disable de local GPS and/or set the home position manually using the telemetry data only. With this new version it is solved and the pilot may use the local GPS always.

v9.2.4

Bugfix

SmartPort telemetry was losing the last decimal in the latitude and longitude, what was causing a big difference between the heading position of the tracker and the position of the aircraft. With this bugfix the precission will be higher.

v9.2.3

Bugfix

The number of satéllites was wrong when parsing telmetry protocol SmartPort (FRSKY_X) from iNav.

You can backup your settings for 9.2.2 version and restore them after installing 9.2.3. After that you have to use this command in CLI mode:

set telemetry_provider=INAV

This will cause to decode the number of satellites in the same way than iNav is packing and sending it.

Valid values for parameter telemetry_provider are:

NONE
DIY_GPS
INAV

Parameter telemetry_diy_gps is used no more.

9.2.2

Bugfix

Fixed a bug that causes the coordinates and the number of satellites not to be visualized when the Smart Port protocol of FrSky is used

9.2.1

Bugs

PITLAB protocol parser gets now absolute altitude from type K frames instead of the relative altitude got from type B frames. This would prevent problems in calculating the altitude of the aircraft when a local GPS is used in the tracker.

9.2.0

New features

• PITLAB telemetry supported.
• "AUTODETECT" option added to configuration menu (display).

9.1.0

New features

Buzzer is supported for the following purposes:

• Warning beeps when automatic home position is set by local GPS (must be present and enabled).
• Low and critical battery alarms (when battery monitoring enabled).

Notes
Home position warning can be disabled by user (it is enabled by default):

set gps_home_beeper = OFF

Battery alarms are always ON.

9.0.3

Bugfixes

• Fixed a bug that caused to not show on the display the minus sign for latitude and longitude data when the absolute value is between 0 and 1.

• Fixed a bug that caused to display wrong values of heading depending on the value of OFFSET parameter.

9.0.1

New features

Telemetry protocol autodetection system has been implemented: from now you it is no more needed to configure or to change the configuration to select a different protocol among supported. You just need to care of sending telemetry at the same baud rate, and the antenna tracker will try to detect it. Once the telemetry protocol has been detected, the tracking values will be reset, and it will be shown on the OLED display, as usualy.

This is an experimental feature, you should use it carefully, please don't fly your aircraft far from the line of sight in the first test flights. The detection system is activated every time the telemetry is lost for at least 3 seconds, during the detection might detect a different protocol by mistake.

A new version of the u360gts-configurator has been released for this version of the firmware. The configurator allow enable/disable this new feature.

8.1.0

New features

• FCS (Checksum valitadion fails) field on display OLED has been added for other protocols.

Bugfixes

• The ticker did not spin with a steady pace when it was receiving telemetry.