×
INDI Library v1.8.5 Released (19 Apr 2020)

April 2020 release of INDI Library v1.8.5 introduces new drivers while providing fixes and improvements to existing devices and core framework.

Has anyone used the new iOptron Firmware with the INDI drivers?

11 months 2 weeks ago
calberts
Expert Boarder
Expert Boarder
Posts: 106
More
Has anyone used the new iOptron Firmware with the INDI drivers? #42384
Yep i understand , i think, it doesn't save the parking position it wil go back to the zero position. (you dont see the current changing)
But wen moving de Dec change little) in some direction the current can be updated and will be updated and will be saved.

Do you mean this behavour, for me it works as i wanted. but if we need to test in this topic give shout ;-) have nice weekend


Chris

Please Log in or Create an account to join the conversation.

11 months 1 week ago
DerPit
Platinum Boarder
Platinum Boarder
Posts: 439
Karma: 1
More
Has anyone used the new iOptron Firmware with the INDI drivers? #42659

knro wrote: Thanks for the exhaustive testing! I emailed iOptron and waiting to see what they say about it.

If it turns out some issue with the firmware, I see almost set the azimuth to a small non-zero value to make it park with the CWB down.


Yes, an old post I'm answering to... I just had another glitch related to the parking issue. Last night, I just parked my scope as usual, but without going outside to cover it and check. This morning I saw it parked at some 45 degree position of the CWB.
I first thought the gears had lost steps or something, but everything worked fine, pointing, going to HOME etc.

It took me a while to realize that the site location reported by the GPS had changed, from 28:45:37 to 28:45:34.
And of course the stored parking position was for :37 altitude..... Of course the parking algorithm took 'properly' care of this by rotating RA to be able to reach that position :o

My personal conclusion for that dilemma would be to use the Zero/Home position for 'Default'. However, the park command will always go to the position stored in the mount, and that likely also would do a miss-pointing in that case(?).
So go to zero, take whatever coordinates you end up with, and store those, so you can park? Or use a placeholder for ALT that is always replaced by the sites latitude? Or don't park, but just switch off tracking?
How do other mount drivers park?

openSUSE Tumbleweed KStars git INDI git
GPDX+EQMOD, CEM60EC, ASI1600+EFW+EAF+ASI290 mini

Please Log in or Create an account to join the conversation.

Time to create page: 0.425 seconds