In Satnogs client configuration I like to set the rotor type to -m 601 for the Yaesu G5500 rotor. My rotor covers 0 to 450 degrees, so that should be set, as well as a switch for flipping.
Before NETROTCTL was implemented I believe the rotor type was set in HAMLIB_UTILS_ROT_OPTS but that doesn’t seem to work with NETROTCTL. I never found the settings for flipping or 0 to 450 degrees.
satnogs_rot_flip = true
hamlib_utils_tor_opts: -m 201 (for Easycomm 1)
but no change in behavior. Still won’t track past 180 or 0/360. An example is observation
The sat AOS was at 176 degrees but the rotor commands stopped at 179.98 degrees. The satnogs_rot_flip had no effect even though this was a 77 deg elevation pass.
Another data point is pass https://network.satnogs.org/observations/2557530/
AOS az was 184 degrees but the rotor interface never sent any az/el commands, just the \dump_state at start followed by the “p” position queries.
And had a nice 83 max el pass with flip enabled but the ROTCTL wouldn’t let the elevation past 89 degrees, so it looks like ROTCTL doesn’t know it supposed to exceed 90 deg elevation, either. The pass was: https://network.satnogs.org/observations/2556528/
(good tracking since I was actually commanding the rotor from my tracking program while monitoring what ROTCTL was sending.