Backlash and possible driver protocol conversion of my arduino DIY focuser.
If I change to a different protocol which one would be the easiest to match with an indi driver that does have backlash compensation?
and if so, can I get a copy of the protocol used?
Also, does anyone have arduino focuser code that emulates a different protocol from moonlite and that has working backlash controls via the indidriver?
All the ones I've found in searches are using moonlite, but it never hurts to ask.
I did a text search of the indi-focus drivers code and found several that have it mentioned and am going through looking at indi code to try to decide which one to switch to but many of them are very complicated.
I think it's better to define your own protocol, that way you have control over what is defined and implemented.
I've always defined a protocol as follows:
Every command starts with a single character, followed by a parameter if required and a terminator character.
This always causes a response consisting of the same command character with optional data and a terminator.
The terminator character must never appear in the data.
This works well with a Arduino, the library functions provide all the support needed.
Backlash would be:
send 'b#' return 'b500#' current backlash is 500.
send B600#'' return 'B600#' set backlash to 600.
To reiterate the OP...
What I'm after is to see if anyone has already made an arduino focuser serial using a different protocol with a backlash feature that already has a working driver in the system.
ar2star2 wrote: Ray, have you tried the MyFocuserPro2 driver it uses Arduino, has backlash compensation a recent Indi driver was written by Alan. I’ve tried it on an MyFocuserPro2 I built a while back for use on ASCOM I just updated the firmware to version v291 and it works I believe there may be a version v292 by now there’s a long thread on here about it
Thanks I'll check that out. I looked at it once long a go but found the code difficult to follow and went a different route. I'm a bit more experienced now so maybe I can bend it to my hardware needs now. Sounds like they continued development as well so if nothing else that new driver might have the protocol I can use. Jasem also mentions another full opensource driver in that thread I'll check out too.
[update: ] I thought that sounded familiar. I started with a very early version of that same code originally. Looks like mr. Brown also needed a few more commands so this might be just what I'm looking for.