Excellent, thanks for the controller responses, I'll double check that parsing of the fields is correct. Unfortunately the log file didn't contain any more information as the previous one, but I think this is enough for me to progress for now. I think I'll ask ScopeDome guys if there is anything that can be done software wise with the connection breaks, I don't have any problems with my controllers, but I power them directly and they are fairly close to each other so that's expected. Unfortunately not much I can do about the shutter if there isn't connection to control it...

i've started to identify the different field in the status frame on my side
i think there is an issue around the parsing or just after , as before doing anything just after connection, shutter is seen open by the frame (but it is closed)

i patch the code to show cmdstatus frames received on indi from the arduino
just after connection (without pressing any button)
i see that the frame is correctly received, (shutter is see off in the frame )
but not updated in the GUI (seen as open)
if it can help you ......

The fields are described in the protocol documentation that can be downloaded from www.scopedome.com/wp-content/uploads/202...uino_Info_5.2SDK.pdf but it's possible I've made a mistake assigning them to variables in the code and then to shutter status. So I'll override the responses from my controller with those you sent and check how the code behaves and there the error comes from.

Long overdue status update after I've finally had a few evenings to work on the driver. Biggest new thing is that ethernet connection now works for me at least. Set connection mode to Ethernet / TCP and fill in the host name and username/password (port number isn't actually used, but doesn't hurt either) before connecting.

Quite a lot of small and larger fixes included too, namely I found from the Windows driver source that digital input and buttons are actually inverted in the status reply, so that caused shutter open/close status confusion among other things. I also added option to set home sensor polarity as it seems to be active low for Arduino cards where as USB Card 2.1 uses active high. So if find home command finds the sensor almost immediately without actually being near the sensor, that is most probably caused by wrong polarity setting.

Hopefully someone has time to test this and report if/when things don't work

good news !!, will test it ASAP
keep you update
Rgds

I've tested the home sensor functionality as well as the shutter successfully last night. Board firmware was 5.7, Scopedome 3M.
Thank you, Jarno for your restless support.

Best,
Gorden

Hi did few test (Ethernet connection - 2m dome - firm 5.4)

CCW/CW works fine
Open / close shutter works fine
find home works fine
relays command works fine


the save configuration in option's tab does not works (may be not implemented yet)

will continue to play with

Regards
Eric

Thanks for testing, sounds promising!

Saving configuration should work (it's mostly handled by the base INDI classes, I just save a few specific items in addition), definitely does for me. Does it create/update "~/.indi/ScopeDome Dome_config.xml" file and if it does, do the contents look valid?

Eric,

how about movements to absolute positions? Is that working for you? And how about parking and slaving to the mount?

Cheers,
Gorden

HI

just checked , in fact configuration is correctly saved in the file "~/.indi/ScopeDome Dome_config.xml"
(i did the test with "close on park" and "open on unpark"
but when i restart i need to manually load it, it is not automatically done, looks like the default config is loaded instead.

for the slaving i have an issue the dome is trying to find the position but turn in an endless loop, the same with absolute position
(this is working with network and scopdome windows drivers) .

Eric

Hi,

I have the same behavior when trying to enable slaving or moving to an absolute position. Jarno is working on it already.

Sometimes (not every time) after updating the INDI server I had the same with saving the config. Once I got the message that there was no config even though saving the config was reported to be successful.
What worked for me in these cases:
- disconnect everything and stop the server
- delete (or rename) the config (not the default config) from .indi folder
- start the INDI server, the driver config file is created from the default config.
- connect and repeat the settings, save the config file

Next time the driver is connecting the settings should be applied correctly.

Cheers.

Gorden