I changed the steps/degree on on a rotator setting but had to recompile all drivers. Installing and re installing doesn’t change anything at all.
By now my only chance is using a backup of my SD on Saturday to get anything working again.

If you (can) compile yourself it should be straightforward. You need to compile indi libraries, etc, install them, and then recompile the indi_eqmod (which is not part of main indi, but in indi-3rdparty) against the new indi library. At least here this works w/o issues.
Just make sure you do not have any old libraries or header files installed.

Read More...

Did you upgrade the whole INDI installation when adding your driver? If so, you also need to upgrade/recompile indi_eqmod (from the 3rd-party repo). The so version of the indi libs has changed...
(There's another thread here about that)

Read More...

The more interesting question would be whether saving stuff as FITS would use that GPS time of the camera. My strong suspicion there is 'NO'.

Read More...

Untested, but try unix.stackexchange.com/questions/234581/...ect-usb-port-via-cli
or askubuntu.com/questions/645/ddg#661

Read More...

So yes, it does properly terminate the indiserver and drivers, and restarts them. Thus, it isn't the issue that I do observe sometimes.

Read More...

Strange. Just to add a data point:
I had a computer that wasn't used for a long time, and it still had kstars 3.3.9 installed. That one always gave me errors when trying to update data files. I just updated that to 3.6.3 (recent git). Starting it, it would ask me if it should convert database files to new format, which I OK'ed.
After that KStars->Data->Updates->Update Comets Orbital Elements succeeded, and then I could search (and find) C/2022 E3 ZTF.

Read More...

At least that behavior I do see if I disconnect a ZWO device while the driver (indi_asi_*) is still running. Can you check that after closing EKOS/KStars, the driver is not running? (

ps aux | grep indi

Was just an idea. But it's not a general issue. At least my 12V EAF has no issues on a Pi4. But the Pi is powered by a high-current power supply.

Read More...

I had a similar error, and there the reason was that the meridian flip was not initiated by EKOS, but by the mount itself. What are your MF limits, both on the mount and in EKOS?

Read More...

Have you tried to only connect the EAF to the Pi? Or connect via an additional, powered USB hub? Could be the power supply of the Pi isn't strong enough to (reliably) power Pi plus several USB units. In that case, switching to the 5V version would/could make things worse....

Read More...

Not sure if that is an issue here. But in my experience the ZWO drivers have problems when a connected device disappears. In my case it was a bad power connection. After such an event, you have to restart the driver (indi_asi_focuser) before it will recognize the EAF again.

Read More...

I'm using eqmod cable and driver for my GP-DX, which has one of the EQ3/5 upgrade kits installed. Initially, before getting the eqmod cable, I had used the HC to connect, and ISTR that the HC has to be put into a special mode so it listens on the input port and translates it into proper commands for the motor controller. Did you do that?
Depending on what cable you ordered, if it is an eqmod cable (which includes AFAIK an USB-to-RS422 converter) it would have to be plugged to the motor control box instead of the HC.

Read More...