Unfortunately the driver currently only supports the older ScopeDome USB Card v2.1 which I have personally. The protocol has changed totally with the new Arduino card from a binary stream to text based so it would require new code. The driver is in theory structured with this in mind as there are also older versions which differ from the 2.1 too, but it would still need to be written and especially tested as I don't have the new card to work with.

Dear jpaana,

within the last 3 days I wrote the basic function for accessing and commanding the 2mScopeDome.
I did this via reverse engineering with help of an incompatible command list which I found in a Polish document.

Could this be helpful for programming the new interface driver?

---

Is there a INDI-client available which returns RA, DEC and Pierside of the actual telescope position via port access, stdio or file?
If yes then I could write a small utility which can control the dome by myself.

Best regads

Frank

Not sure exactly what you are trying to achieve but there are lots of INDI scope drivers which will return RA, DEC and Pier side.

And the base INDI dome driver, on which a driver for real dome hardware is built, has code to get this data from the scope driver and do the conversion to dome position.

The command set seems to be fairly well documented in scopedome.com/Doc/ScopeDomeArduinoCard/S...Arduino_Info_5.2.pdf and the commands correspond almost 1:1 to binary commands in the older controller so mapping them should be fairly straight forward. I originally tried to make the base ScopeDome driver generic and leave the communication details to card drivers, but unfortunately some implementation details specific to my own controller are still there so they would have to be abstracted away a bit more. Also there are a lot of features that aren't strictly necessary for basic operation, like sensor reading etc. (and some are still placeholders and actually don't do anything), so just mapping the shutter open/close, rotate dome, abort etc. commands would make it usable.

I'm quite used to reading Google translated Polish as I originally wrote the driver based on the Windows driver source which has comments in Polish, but fortunately variable names etc. were in English

In case you are willing to do some beta testing, I could start doing the basic implementation blind and hope for the best.

I am not skilled in writing INDI-drivers, or INDI-Clients.
But I have to finish a project here at our observatory.
Due to missing documentation by the Polish manufacturer and missing INDI-driver I programmed the basic routines for driving the dome (have a look to the ZIP-File of the last post please).
If there is a client which will send RA, DEC and Pier side periodically, then I can adapt my routines without to write an INDI driver within some minutes.

You can poll those values from INDI server with indi_getprop command, for example my EQ8 gives:
EQMod Mount.EQUATORIAL_EOD_COORD.RA=3.0200912594207576234
EQMod Mount.EQUATORIAL_EOD_COORD.DEC=89.684600000000003206
EQMod Mount.TELESCOPE_PIER_SIDE.PIER_WEST=On
EQMod Mount.TELESCOPE_PIER_SIDE.PIER_EAST=Off

Dear jpaana,
thank you very much!!!
Next evening I will try to do this.
I will send
indi_getprop
to port 7624
then I hope to get the desired information.
I will t4ransform these data into DomeAzimut and send this value to the dome via my tested shell scripts.
This was the help which is so important.
Best regards
Frank

Dear jpaana,

sorry for asking an additional question.
Have a look to the screen copy please:

* I did a test without open dome.
* I started ekos and the INDI server locally.
* Then I set a connection to the INDI server via netcat utility.
* I entered indi_getprop
* nothing happened
* I cut the connection via EKOS button on the right window
* I started the connection via EKOS button on the right window - and got the following result, but no coordinates

What is wrong in my doing?

Best regards

Frank

Thank you for the scopedome.com/Doc/ScopeDomeArduinoCard/S...Arduino_Info_5.2.pdf documentation link. I haven't read this but many others.m It seems to be better than the Polish original
I will accept your offer of doing the basic implementation blind, and I can do BetaTesting for you.
---
And I hope to bridge the time with the indi_getprop command method, if I will find the reason for blocking up to disconnect/connect of the EQ8

Oh, I meant shell command called indi_getprop which comes with INDI, it would do all the parsing for you and you can also give it just a subset of the properties to return.

Dear jpaana,
now it's working. The dome is tracking the telescope.
Unfortunately the shutter controller died But there is a manual emergency button for opening and closing the shutter without software.
Let me send a small astronomical gift to you.
Can I get your postal address for the small parcel please?
Best regards
Frank

Good to hear about tracking working, sorry about the shutter controller... I'm currently also waiting for a new PCB for my controller, so I know the feeling.