Rotator / Station is going crazy


Since many day, I realized that my station is sometime following a satellite (the rotator is moving) while there are no observations scheduled. Sometimes also a real observation is planned and then it follows 2 satellites at the same time, which doesn’t work very well.

This seems to me to be a serious problem

Hello @Yohan_Hadji

Can you please post the results of satnogs-setup > Advanced > Support ?

Sure, there it is

------------[ copy here ]------------
    "versions": {
        "satnogs-client": "1.3.4",
        "satnogs-client-ansible": "202007160921",
        "satnogs-flowgraphs": "1.2.2-1",
        "gr-satnogs": "",
        "gr-soapy": "2.1.3-1",
        "gnuradio": "",
        "satnogs-config": "0.10.2"
    "state": {
        "is-applied": true,
        "pending-tags": null
    "system": {
        "date": "2020-08-08T06:36:05.730575+00:00",
        "distribution": {
            "DESCRIPTION": "Raspbian GNU/Linux 10 (buster)",
            "RELEASE": "10",
            "CODENAME": "buster",
            "ID": "Raspbian"
        "pending-updates": true,
        "platform": {
            "system": "Linux",
            "node": "SuperAntennaz",
            "release": "5.4.51-v7l+",
            "version": "#1327 SMP Thu Jul 23 11:04:39 BST 2020",
            "machine": "armv7l",
            "processor": ""
        "memory": {
            "total": 896733184,
            "available": 443043840,
            "percent": 50.6,
            "used": 365322240,
            "free": 241659904,
            "active": 291049472,
            "inactive": 299155456,
            "buffers": 13058048,
            "cached": 276692992,
            "shared": 28770304,
            "slab": 32612352
        "disk": {
            "total": 14915805184,
            "used": 5276454912,
            "free": 8985894912,
            "percent": 37.0
    "configuration": {
        "hamlib_utils_rot_enabled": true,
        "hamlib_utils_rot_opts": "-m 202 -s 19200 -r /dev/ttyACM0 -C timeout=200",
        "satnogs_antenna": "RX",
        "satnogs_api_token": "[redacted]",
        "satnogs_ppm_error": "1",
        "satnogs_rf_gain": "48.0",
        "satnogs_rot_flip_angle": "30",
        "satnogs_rot_model": "ROT_MODEL_EASYCOMM2",
        "satnogs_rot_port": "/dev/ttyACM0",
        "satnogs_rot_threshold": "5",
        "satnogs_rx_samp_rate": "2.048e6",
        "satnogs_soapy_rx_device": "driver=rtlsdr",
        "satnogs_station_elev": "216",
        "satnogs_station_id": "762",
        "satnogs_station_lat": "45.195995",
        "satnogs_station_lon": "5.684243"
------------[ copy end ]-------------

Can you point to an observation on the Network that did that?

I would have to guess 2647033… and the behavior he describes is indicative of the zombie gr process issue we’ve been hunting down in my client. /cc @Acinonyx

Hi @pierros @cshields
Unfortunately I hadn’t noted the time and the day it happened and so I can’t find the observation(s). That’s not this one
The whole series of failures on my station comes from a problem with the usb cable that doesn’t hold well on my rtlsdr.

I’m going to restart scheduling observations on my station and try to reproduce the double-observation problem

Well, that was quick

It happened on two obs, the two ops are failed

Seems like a stuck observation issue. Try rebooting and updating fully your station please.