There was a capacitor initially, but it worked flawlessly on windows with whatever program I used(SGP, NINA, firecapture, sharpcap), so I didn't install it on the new arduino board.
The capacitor should disable auto reset or something like that I think, is there any logic for it to work on windows and not work with indi?

I do not know the problem, but it is not related to the arduino code, or the moonlite driver. I have the same issue with myfocuser 2 pro, but i need to try with the capacitor. Other times it connects without problems

Oh you're experiencing the exact same problem?

Yes random. I think that isrelated ti Arduino that reset on serial connection and the code ti ger the motore position. Capacitior should evitate this.

That's very interesting, I'll surely give it a try when I have the chance, will you be able to let me know if you tried it too?

Thanks!

I tested it now with and without the capacitor. Without the capacitor some problem in the connection with or without unplug the usb port. With the capacitor no problem on connection in about 10 times

That is awesome! I'll give it a shot when I get the chance, I have some capacitors, but I'm not sure I have exactly 10uF capacitor, do you know if it makes much of a difference?

Thanks

I do not know if other capacitor works. With arduino nano 10uF works, you can do a simple search for arduino block autoreset with your specific board type

once that the code has been loaded you can connect the capacitor, if you need to reflash you have to disconnect it

Yes I'm aware of this, thanks a lot for all the help!

If, if, if your problem is that the mount and focuser switch /dev names randomly, write an udev rule to assign an explicit symlink to the device from its usb identifiers.

This is unfortunately not for the faint of heart, but an example can be found here: github.com/TallFurryMan/astro-slave/udev. Disclaimer: this is advanced system configuration, it is not an up-to-date representation of what I use and you will need to adapt the parameters to your own setup. This combined with driver configuration files enables deterministic device connection behavior.

-Eric

Just to add that many Ard Nano are clones which use CH340G /Prolific and other cheap chips which all have the same problem - They do not have a unique serial number so if you have 2 or more chips of the same type it is impossible (other than position) to write Udev rules for such devices. You can see this if you do a lsusb linux.die.net/man/8/lsusb . However as Eric has said this is something "not for the faint hearted" and i would suggest you the changes on a copy of your SD card (or take a backup first) and takes a little time to get your head around. Of course after doing the "udev by position" you will ALWAYS have to plug the device into the same port/hub.

Simpler way,if this is the problem, buy an genuine FDTI chiped device that has a unique serial number - for the Ard Nano the code will of course not need to be altered but most likely you will need the Autoreset /cap trick - I did and the problem went totally away