If you have the older 12V model of EAF, it requires 12V power connected to be visible to the computer. The newer 5V USB power only version does not need that, but probably requires a powered USB-hub instead as it powers the motor from USB as well.

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.

Ok, thank you !
I'll try to change my alimentation this week-end.
Wait and see

Hello,
Bad news... I've changed all my cables and test my power, all is fine.
I've updated the firmware of my EAF and test it on my computer. No problem.

But, on my RPI, with SM, I don't see the EAF
For testing, I've created a profile very simple : One CCD and the EAF


And the result is :

and


So, I don't understand why I see my two ASI (224 + 1600) and not my EAF if I indicate only one camera and the EAF.

If I keep my classic configuration :


I don't see my EAF and I haven't an error message



An idea ?
Thank you.

Did you also add in in the optical train?

Your profile and optical trains are OK. If you changed all the cables..etc then I suspect the only remaining issue is that the RPI is somehow bad. This happens very rarely but it does happen. I just tested ASI EAF with StellarMate and it's detected fine, so it's definitely not a driver issue. It could be a USB conflict issue as well, but I don't see if you tried connecting ONLY ASI EAF?

Create profile with this:
Telescope Simulator
CCD Simulator
ASI EAF

and physically, nothing connected to StellarMate BUT ASI EAF.

Ho yes, sorry but I've tried that.


But I don't see my EAF


So I suppose my EAF is dead... I'll buy the new EAF (5v instead 12v) and hope.

Thank you for your time !

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....

Yes, I've tried to connect only my EAF like Jasem said and with a separate alimentation.
Sometimes, I see my EAF but if I close Ekos and restart, I lose my EAF...
I think a lot of people use the new EAF with a RPI (I hope).
Sadly, I haven't another solution.

I use SM since two years and I'm very happy. I hope to solve my problem quickly.

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.

Hmmm, ok, maybe change the power of my RPI ?
Why not, I'll try that.
This morning, I try to start Ekos, plug and unplug my EAF on my RPI and... Ekos see the EAF.
If I close and restart Ekos, I lose my EAF. I need to go to my observatory to unplug/plug again.
So, I think it's a problem only with the EAF.
But I'll try to change my power of my RPI.
Thank you.

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? ()