×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

Baader-Planetarium Dome

If you're using the PPA, the latest Ekos is only available for Ubuntu 14.10 and above due to its dependency of KDE 5.

You can find more info in the INDI::Dome API.
9 years 4 months ago #2231

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

  • Posts: 158
  • Thank you received: 2
That's not good at all... 14.04 is LTS and honestly I am not planning upgrading to 14.10 :dry:
9 years 4 months ago #2236

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

Then you can compile INDI & KStars from source, I'll see if I can compile a HOWTO at some point for 14.04 systems.
9 years 4 months ago #2237

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

  • Posts: 158
  • Thank you received: 2
If there are KDE 5 dependencies (why?!) how can I compile on 14.04? Please, no KDE 5 compiling! :blink:
9 years 4 months ago #2239

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

I just installed latest Mint on a VM, so once I figure out the steps exactly, I'll post them here. KStars was migrated to KDE 5 and so bleeding-edge Ekos relies on that as well.
9 years 4 months ago #2243

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

  • Posts: 158
  • Thank you received: 2
I understand the difficulty, but isn't it possible to keep KDE 4 and KDE 5 alongside? Really, I am sure I am not the only one looking at non-LTS Ubuntu releases with lack of trust (my experience allows me to say that)...
9 years 4 months ago #2245

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

  • Posts: 158
  • Thank you received: 2
Argh... C++ confuses me :( Can I just give the command set? It will be much faster than expecting me to learn a little bit of C++ in a adequate time :lol: I can take care of the azimuth correction math (once I find it out I will describe it here) and you will translate it into your code :) Is it OK?
9 years 4 months ago #2272

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

Ok, we can give it a try. Ask Baader to send me a trophy after this :D
Last edit: 9 years 4 months ago by Jasem Mutlaq.
9 years 4 months ago #2274

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

  • Posts: 158
  • Thank you received: 2
Nah, Baader won't send any trophy :lol: Just come to Moldova, I will give you the access to the observatory I work for ;)

Ok, here is the command set. It's much simpler than in the case of Baader focusers :lol:

1. Request:
d#getshut
Replies: a)
d#shutope
Shutter is fully opened
b)
d#shutclo
Shutter is fully closed
c)
d#shutrun
Shutter is in the process of opening/closing

2. Request:
d#getflap
Replies: a)
d#flapope
Flap is fully opened
b)
d#flapclo
Flap is fully closed
c)
d#flaprun
Flap is in the process of opening/closing

3. Request:
d#getazim
Reply:
d#azr0000
Current position of the dome (after calibration. Before calibration the reply is
d#azi0000
).
d#azr0000
represents South,
d#azr0900
represents West and
d#azr1800
represents North. Resolution is 1/10 of a degree

4. Request:
d#closhut
Reply:
d#gotmess
Close the shutter with confirmation of receiving the command. If flap is opened it will be automatically closed before closing the shutter

5. Request:
d#opeshut
Reply:
d#gotmess
Open the shutter with confirmation of receiving the command

6. Request:
d#cloflap
Reply:
d#gotmess
Close the flap with confirmation of receiving the command

7. Request:
d#opeflap
Reply:
d#gotmess
Open the flap with confirmation of receiving the command. If shutter is closed it will be automatically opened before opening the flap

8. Request:
d#azi0000
Reply:
d#gotmess
Move the dome to the desired position. Numbers are the same as for reading the current position. Note: if I remember it right dome can arrive at the desired position with small error

9. Request:
d#azi
Reply:
d#azierro
There must be a value (valid one) or you will receive such a message

10. Request:
d#encsave
Reply:
d#gotmess
Save to EEPROM current azimuth position (useful in case of planned power off)

In case of unknown command the reply will be
d#comerro
In case of general dome failure it will send
d#domerro
Thank you for your support!
The following user(s) said Thank You: Schreiber
Last edit: 9 years 3 months ago by Alexandru Barbovschi. Reason: Added 10
9 years 4 months ago #2275

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

Any command to stop the azimuth motion? You connect to it via ttyUSB same as the focuser? 9600 8N1? Also, what kind of "small error" are we talking about? 1 degree? 30 minutes? 5 degrees?

Just to confirm, they use ZERO azimuth to indicate NORTH? 90 EAST...etc?

Also closhut must be d#closhut I presume?

Btw, the dome driver can also receive the mount's Az position, do you want the dome to sync to the mount's Az ?
Last edit: 9 years 4 months ago by Jasem Mutlaq.
9 years 4 months ago #2286

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

  • Posts: 158
  • Thank you received: 2
Oops! Forgot to mention - focuser is assigned ttyACM0 :) The dome is connected right now by serial port, so it is ttyS0 at the moment. But when Banana Pi is going to arrive it will become ttyUSB0. The speed is as you wrote. Regarding zero azimuth... If I remember it right it represents south point, have to recheck it. Yes, d#closhut :blush: Yes, slaving is mandatory, but correction is necessary - the telescope is not at the center of the dome. I have to describe the math... Need to sit with pen and paper :)
9 years 4 months ago #2287

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

Ok, we need to be sure what zero azimuth means as it means NORTH in INDI and we have to covert it to INDI standard. It would make sense if 0 to 1799 corresponds to 0 to 179.9 degrees then. Regarding the slaving, is the correction static? That is, a specific offset from the dome az? Right now, the sync moves the dome to the mount's Az as is.
Last edit: 9 years 4 months ago by Jasem Mutlaq.
9 years 4 months ago #2288

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

Time to create page: 0.786 seconds