I've tested your parameters, except pan0, pan90, p,i,d. In telemetry_protocol I use 8 (GPS_TELEMETRY) because I don't have FRSKY X telemetry data (I only can test with the file you shared some days ago, and with this capture data it seems like the drone wasn't flying, it was static. Could you provide a new capture?). With your parmas and using GPS_TELEMETRY everything seems to work.
There a case in which something like you describe could hapens:
I guess that you are using some NMEA packets simulation software, and are converting the packets into FRSKY X telemetry packets, and are sending them to the antenna tracker. I also guess that you have enabled the estimation position system (eps).
If you set home position manually, or from the local gps, and you start the virtual flight and tracking starts, if the virtual drone has been flying longer than 1000 m away from the home position (distance > 1000), if you restart the antenna tracker, for example, because you want to adjust some parameter, and after that the system reboots you set home position again, and you try to start the tracking without returining the dron to a distance below the 1000 meters, the position of the drone is filtered and is not taken into account, the antenna tracker doesn't track it.
This is becaus I introduced a filter to discards corrupted positions when using FrSky D, and this filter is affecting all protocols.
The solution could be one of these:
- every time you simulate the flight you must return the drone to the home position
- set home position from telemetry
- disable eps
Please if is your case, try it...
There a case in which something like you describe could hapens:
I guess that you are using some NMEA packets simulation software, and are converting the packets into FRSKY X telemetry packets, and are sending them to the antenna tracker. I also guess that you have enabled the estimation position system (eps).
If you set home position manually, or from the local gps, and you start the virtual flight and tracking starts, if the virtual drone has been flying longer than 1000 m away from the home position (distance > 1000), if you restart the antenna tracker, for example, because you want to adjust some parameter, and after that the system reboots you set home position again, and you try to start the tracking without returining the dron to a distance below the 1000 meters, the position of the drone is filtered and is not taken into account, the antenna tracker doesn't track it.
This is becaus I introduced a filter to discards corrupted positions when using FrSky D, and this filter is affecting all protocols.
The solution could be one of these:
- every time you simulate the flight you must return the drone to the home position
- set home position from telemetry
- disable eps
Please if is your case, try it...