Well here comes the MoonLite driver log.... I filtered the relevant infos to shorten the file.
It appears every serial Timeout occurs after a :GT# command (Get temperature). Sometimes the response seems to fit, and sometimes, it generates a Timeout.
One time, there is an incomplete answer (chars lost) without Timeout and not after a :GT# command. ( see ??????????? )
The response to the :GI# command (Is the motor moving ?) should have been “01” if the motor is moving, otherwise “00”
To be honest, I must say there is no physical temp probe so far, as I didn't receive the componant yet. The question now is why the Timeout only occurs sometimes?
And why did older versions did not lose chars (See my previous message), when this one does ?

- Marc

What files exactly do I need to flash to Arduino UNO? I have one over here.

git clone github.com/jbrazio/ardufocus.git

Thanks

- Marc

Thank you. I just finished testing this:

1. GT# command sometimes times out. I tried changed polling period to 1 second, which makes this timeout appear less, but it still happens at random times. Maybe the Arduino is looking for the sensor and taking quite a bit of time there? Not sure.
2. The board returns NOT MOVING even though when it is moving. It happens randomly, maybe 5-10% of the time, but it's definitely there. See screenshot below, I was at 13,000 steps and commanded it to 20,000 and at 14956, it decided to return 00# for the :GI# command. Why? beats me.

The reason you don't see these errors is because you're not running in a loop. Most of the time, these things work OK, but because the drivers continuous reads the value, you see them. The timeout error is not critical and can probably be improved with increasing the polling period. I even stopped reading temperature completely while in motion, but I still kept getting random time out commands.

Thanks a lot Jasem. So I guess I need to find a better firmware for my focuser
if someone has a good plan for this ...

Anyway, thanks again for your time and kindness.

- Marc

The Moonlite hardware works well with the Moonlite driver. Better than leeching off other people's work.

Looking at that repository it's typcal linux. Precious about it's own copyright, with messages plastered over everything, while being completely contemptous of other peoples copyright, including part of MY ASCOM driver documentation.

Chris,

I'm sorry to hear this thing infringes some of your own copyrights.How would have I known ? At least, now everybody here knows it is faulty Thanks, Jasem !
You're not talking about the Linux world (remember, this thing runs under an Arduino, not under Linux, Windows or Mac.) You're talking about people who do not respect the work of others.
And this kind of people, you can find them on both side, Copyrights and Copylefts Also, remember your beloved Mac runs under Darwin which is ... Free Software deriving from NextStep (Copyright) and BSD (Free Software). Only the GUI is Copyright. I guess things are never binary in the real world

Now, you've made your point and you were right to do so. Let's end this, this is not the place for that kind of discussion..

- Marc

I'm not blaming you, you weren't to know of course. OTOH you were perfectly aware that this driver was built using MoonLite's proprierty work.It's the way that the whole open software scene seems to be, the most importand thing - frequently the only documentation - is a copyright message.Beloved Mac? You mut be thinking of someone else. I have an iPad which runs SkyDemon when I'm flying but for development Windows C#, RaspPi, occasionally Arduino or more likely Teensy, and PicAxe.Some of your points needed a reply but don't see a need to continue.

The sad thing is that it's easier to do this using a protocol that suits the Arduino and is more resilient.

Chris wrote :

"Beloved Mac? You must be thinking of someone else."

Right, my mistake. Sorry.

Marc

Chris wrote :

"The sad thing is that it's easier to do this using a protocol that suits the Arduino and is more resilient. "

You have something in mind ? Any suggestion ? I'm starting to think I'd better write it myself. I'm not a lazy man and I have some experience on the subject. ( But not with the Arduino .)
Any advice welcome as long as I can write it in C.

- Marc

This is my Focuser.ino Arduino file that controls two focusers, one stepper and one dc, a light box and a dew heater. Can't have unused pins.

And temperature using an LM355.

Close enough to C not to matter, the protocol is defined in the file.

It's designed to work with a ULN 3008 for stepper control.

It looks as if it can use a couple of buttons to run the focuser in and out.

I last touched this in 2014, glancing through it you should have few problems.

No indi code, there will be an ASCOM driver arond somewhere but that will be in C#.

Have fun!

Previous issue with MacOS Catalina 10.15.3/10.15.4 and Moonlite FTDI Driver signing not being recognised by MacOS and not loading
===========================================
I've today received an updated driver from FTDI version 2.4.4 which is signed and recognised by Apple so it now loads whereas version 2.4.2 didn't.
I can't give it a full test yet but bench testing a basic config it does now seem to work ok and the focuser moves in and out when requested. It is too early to say it is fixed until I can test in its proper configuration, but the signs look encouraging. I'd be interested if it works for others who have this specific issue. The driver doesn't seem to be on their website yet, but there support people are very proactive and helpful if you log a support call via email.