u360gts 11.2.0 RC2

New features

Telemetry Forwarding function added. All telemetry input will be forwarded through the output telemetry port without any limit, all protocols are supported and no translation is applied, it works as a transparent bridge. That means if the tracker recieves FrSky X telemetry (e.g.), it should forward it as it is to the output port. Not tested yet in real flight.

In order to use this new function, features softserial and telemetry relaying has to be enabled, and the new protocol called FORWARD, that has been added to list of available protocols for telemetry relaying, has to be selected (use 8192 protocol number in serial commands from CLI in order to configure it).

Demo video 1: https://www.youtube.com/watch?v=-t9i9cyD3Hc.
Demo video 2: https://www.youtube.com/watch?v=HTbRv6JHI98.

Restore Last Known Home Position function added. This is one of the more demanded features by users since quite time ago. If enabled, the antenna tracker will store the home position in the non volatile memory once it has been established. If durin tracking a power reset ocurrs (e.g the users replaces the battery), the home position will restored (HOME SET LAST will be shown on display) and tracking will continue normally without the need of landing.

This functionality may be enabled by setting restore_last_home parameter to ON. After enabled, home_lat, home_lon and home_alt provide 0 values by default. Once home position is set, either from telemetry, gps or by pressing the home button, the antenna tracker will store the home position values on those parameters. After a power reset, the antenna tracker will read the stored values and restore the home position.

Note: stored lat/lon/alt values may be changed if desired before flying from a different location, the user may press home button for more than 3 seconds in order to get a new home position from the incoming telemetry stream or from local gps.

Improvements

Protocol Autodetection feature has been reworkded. In order to improve acuracy for this functionallity, now it scans during 3 seconds each protocol, and once it get at least two 3D fixes, it will consider that protocol as the protocol used in incoming telemetry stream. This new way of auto detection is slower than before, but should be more acurate. In order to improve speed it is recommended to select as preferred telemetry protocol as default (e.g. whichever is used in the greatest number of your aircrafts).

Bugfixes

CRC calculation for FrSky X telemetry (smartport). The continous FCS error is caused by the method used for cyclic redundancy checksum calculation. It depends on the way telemetry is extracted, directly from TX module, or from internal BLE module. This fix checks CRC using both methods.

Configurator

Firmware v11.2.0 is full supported by u360gts-configurator v4.2.0