Satnogs Rotator stops tracking after initial position

Hi,
The rotator goes to start position during the scheduled time but stops tracking thenafter.
Here is the output from support tool:

{
“versions”: {
“satnogs-client”: “1.6”,
“satnogs-client-ansible”: “202109022142”,
“satnogs-flowgraphs”: “1.4-1”,
“gr-satnogs”: “2.3.1.1-1”,
“gr-soapy”: “2.1.3-1”,
“gnuradio”: “3.8.2.0-2”,
“satnogs-config”: “0.12”
},
“state”: {
“is-applied”: true,
“pending-tags”: null
},
“system”: {
“date”: “2022-01-03T07:17:25.417644+00:00”,
“distribution”: {
“DESCRIPTION”: “Raspbian GNU/Linux 10 (buster)”,
“RELEASE”: “10”,
“CODENAME”: “buster”,
“ID”: “Raspbian”
},
“pending-updates”: true,
“platform”: {
“system”: “Linux”,
“node”: “raspberrypi”,
“release”: “5.10.63-v7l+”,
“version”: “#1496 SMP Wed Dec 1 15:58:56 GMT 2021”,
“machine”: “armv7l”,
“processor”: “”
},
“memory”: {
“total”: 4025200640,
“available”: 3776045056,
“percent”: 6.2,
“used”: 109699072,
“free”: 3617120256,
“active”: 108253184,
“inactive”: 241164288,
“buffers”: 24641536,
“cached”: 273739776,
“shared”: 8839168,
“slab”: 32960512
},
“disk”: {
“total”: 30280855552,
“used”: 3909795840,
“free”: 25086332928,
“percent”: 13.5
}
},
“configuration”: {
“hamlib_utils_rot_enabled”: true,
“hamlib_utils_rot_opts”: “-m 204 -s 19200 -r /dev/ttyUSB0 -C timeout=200”,
“satnogs_antenna”: “RX”,
“satnogs_api_token”: “[redacted]”,
“satnogs_log_level”: “DEBUG”,
“satnogs_rot_model”: “ROT_MODEL_EASYCOMM3”,
“satnogs_rx_samp_rate”: “2.048e6”,
“satnogs_soapy_rx_device”: “driver=rtlsdr”,
“satnogs_station_elev”: “1300”,
“satnogs_station_id”: “757”,
“satnogs_station_lat”: “27.679”,
“satnogs_station_lon”: “85.409”,
“sentry_enabled”: true
}
}

Also works fine with: rotctl -m 204 -s 19200 -r /dev/ttyUSB0 -vvvvv command

Works fine when hamlib_utils_rot_enabled is set to False

We had a similar issue. It ended up being that our SDR had gone bad. SATNOGS would command the rotator to move to the initial position, then try to detect the SDR. When detecting the SDR failed, the observation was canceled, and the rotator didn’t move anymore. I’m not sure if this will fix your issue, but it’s something to check!