Ok. This time I set it up with a CCD Simulator, Telescope Simulator, Guider simulator, and the Moonlite. I Rebooted, unplugged all devices, and rest the Moonlite motor by unplugging it from everything and plugging it back in. When I booted up went into EKOS and started INDI, the focuser would not start. I logged this session. Stopped INDI, and I tried to clear out the USB port connection information on the Moonlite connection tab. Then I quit EKOS, reset the focuser again, and then loaded up EKOS, started INDI, and it worked this time. I copied the USB settings from Device Profile, and took another log, moved the focuser a bit, then exited EKOS. All the information is attached.

I did previously install a driver for the USB-Serial cable I use to connect to my mount and control it. I believe I installed the Prolific driver from www.prolific.com.tw/US/ShowProduct.aspx?p_id=229&pcid=41 , but it has been a while. The USB Serial cable I'm using with the mount is from Sabrent .

Thanks, Let me know if I need to provide anything else.

You're getting resource busy error, so perhaps something in MacOS is using this port? I'm not sure what do suggest otherwise.

I don’t have any other devices plugged in, so how would I test it?

I’m wondering since I have a Serial to USB cable and driver installed for my NexStar hand controller if getting a USB version of the hand controller would eliminate this issue? I think the only way to test it would be to erase OSX and do a clean install with no USB serial driver installed to test the focuser before I make a purchase.

Also, one other thing.

I have both my serial-USB cable for my mount plugged in now, and the focuser, and they're both working. By themselves. I still get the timeout errors, but I can send commands to the focuser.

The FT232R is the focuser. FTDI makes the chip, and they have a webpage here where you can see the specs. It looks like their might be a driver from FTDI, I'm wondering if this would help, but I don't know which to download.

A little more digging and what I can find on their website is that the VCP driver is for this:

VCP creates a virtual com port on the MAC and allows applications that use the POSIX programming interface to communicate with the device. This is effectively the same us using a legacy com port.

And the D2XX drivers are for:

D2xx uses FTDI’s programming interface to access advanced features of the chips.

Sounds like maybe I should try the VCP drivers?

Try to this command, what do you get:

I get this:

This is with both serial USB devices connected.

I've loaded up all devices again (Mount, cameras, etc) and the Moonlite is working this time. I have it plugged into the Laptop directly, and I have the others plugged into a USB Hub. I'm wondering if one of the issues when I previously had everything plugged into the hub was that there might not have been enough power for everything.

I'm still getting the same timeout issues. So there still appears to be a communication issue with just receiving information from the Moonlite controller regarding temp and position. However that said, the Moonlite overview tab shows the correct absolute position.

This is how it all looks connected in profiler:

Still wondering if the driver I listed above might alleviate the communication issue, or if there is a bug in the INDI driver. Here's a log from the last time with everything working.

It might be nothing, but I observe that the first error message reported by the driver is from updatePosition. As it happens, it is the only function that uses a hard-coded timeout equal to 2 seconds, while other functions of indi_moonlite are using MOONLITE_TIMEOUT, equal to 3 seconds. That might also start to explain the similar timeouts I experienced with my custom arduino firmware under this driver, but well, maybe not.

-Eric

Ok I fixed that, but even 2 seconds should be enough. I increased POLLMS from 250 to 500ms, I think twice-a-second frequency is more than enough for a focuser.

In my own experience when the focuser is working, I noticed if it has received a command, moved to the position, then I issue a new command, it sometimes does not move if I do this too quickly. It requires some longer delay before you can give it a new command.

Am I able to adjust the timing settings you indicated or do I need to wait for an update to EKOS or the Moonlite plugin?