Scopedome forum - Ostatnie tematy

After driver update to 5.5.30, Shutter moves partially to open, then closes

Bill110366 — Mon, 20 Apr 2026 10:37:54 +0000

Hello,

I sent an Support ticket, but no answer so far.

Driver updated to 5.5.30 (reinstalled twice)

All functions ok, except Shutter opening: The shutter moves about 15 to 30 degrées, and then closes again.

Weather station: No difference by selecting either AAG SOLO, AAG CLOUDWATCHER, SCOPE DOME CLOUDSENSOR or NONE

A point of interrest: in the "About" Windows, the Driver seams still to be 5.5.27. Is this normal?

113 114

No way to open and use my Telescope at the moment.

Any idea of what's going on?

Thanks

Eric

The shutter can no longer be controlled – Bluetooth connection no longer possible.

Andreas_Roland — Sat, 28 Feb 2026 20:01:34 +0000

We are at a loss!

Problem:

In the driver software ‘ScopeDome Arduino Dome v10f13’:
The shutter can no longer be controlled on the ‘Shutters’ tab.
The lighting can no longer be switched on in the ‘Main’ tab.
The button in the ‘Relay Shutter’ frame changes status (dark red colour), but the light does not come on.

On the shutter box:
The ‘Open’, “Close” and ‘Light’ buttons on the shutter box itself also have no effect.

Status:

On the shutter box:
Only the ‘Encoder’ LED lights up red.
The shutter can be opened and closed using the yellow ‘Emergency Buttons’ “Open” and ‘Close’.

In the software:
Red ‘Bad Link’ note on the “Main” tab in the ‘Dome Commands and state info’ frame.
Green question mark on the ‘Main’ tab in the ‘Dome State’ frame on the dome sketch.

Arduino_Error_Log.txt:
26.02.2026 12:25:34 | slave=setTime=1772105134 | slave|ERROR|Bluetooth not connected | adruino_command_error
26.02.2026 12:25:34 | slave=getBootloaderVersion | slave|ERROR|Bluetooth not connected | adruino_command_error
26.02.2026 12:25:37 | slave=getFirmwareVersion | slave|ERROR|Bluetooth not connected | adruino_command_error
26.02.2026 13:00:31 | moveShutter=OPEN:50000:3000 | moveShutter|ERROR|Bluetooth not connected | adruino_command_error
26.02.2026 13:03:12 | moveShutter=OPEN:50000:3000 | moveShutter|ERROR|Bluetooth not connected | adruino_command_error
26.02.2026 13:04:59 | moveShutter=OPEN:50000:3000 | moveShutter|ERROR|Bluetooth not connected | adruino_command_error
26.02.2026 13:09:52 | moveShutter=OPEN:50000:3000 | moveShutter|ERROR|Bluetooth not connected | adruino_command_error
26.02.2026 13:12:48 | moveShutter=OPEN:50000:3000 | moveShutter|ERROR|Bluetooth not connected | adruino_command_error
26.02.2026 13:14:28 | Bad status format | board: master - section: relays
26.02.2026 13:14:28 | Bad status format | board: master - section: relays
26.02.2026 15:45:57 | getStatus | IP_command_error | IP_command_error

LEDs on the circuit boards:

Shutter box:
1) On the Bluetooth module: fast continuous flashing in blue.
2) To the right below the ‘Dome or shutter direction control relay’
(No. 23 in the circuit board description in ScopeDome_Arduino_Card_Manual_EN_PlugAnd_Play_2.0.pdf):
- Permanently lit LED in red.
- Below it, slowly flashing LED in blue; after flashing approximately 11 times ,
- a green LED flashes once between the two.

Dome box:
1) On the Bluetooth module: alternating fast and slow flashing in blue.
2) To the right below the ‘Dome or shutter direction control relay’
(No. 23 in the circuit board description in ScopeDome_Arduino_Card_Manual_EN_PlugAnd_Play_2.0.pdf):
LED continuously lit in blue.
3) To the right of the ‘Relay controlling camera power supply’ (No. 26 in the description):
LED continuously lit in red.

The dome is working without any problems.

Attempted solutions:

Switching all components off and on again was unsuccessful.
Bluetooth pairing by simultaneously pressing the Open + Close + Fan buttons (shutter box) and CCW + CW + CCD buttons (dome box) was unsuccessful!

Background:

In the log, we also find the entry ‘Bluetooth not connected’ from months ago. But the problem described has only occurred now.
In October, we updated the firmware and connected a new computer. After that, all components continued to function.
Since then, no further changes have been made to our knowledge.
The weather was cold and often wet for many weeks. Dew often formed inside the dome.

Please note the attachments regarding the flashing LEDs on the circuit boards!

104 103 105

How to set IP addres on scopedome arduino card

admin — Fri, 12 Dec 2025 10:47:09 +0000

- Connect the card to your computer via a USB connection.
- Open ScopeDome driver and conect it to the card via USB.
- Connect your computer and the card to the same IP network hub.
- Launch Command Prompt and enter the command “ipconfig”.
- Read the "IPV4 Address" value (in this example: 192.168.2.198).
- This means that your computer is operating on the 192.168.2.x network.
- Select a free IP address on your network, e.g., 192.168.2.120.
- Enter this address in the “IP address” field in the card's Config window and press the “Set IP” button.
- Press "Save Settings" button
- Restart card power
- Set "Connect by" value to "Ethernet"
- Press "Save Settings" button
- Close config window and restart the driver.

P.S.
Remember that the card's IP address can only be changed when it is connected to a computer via a USB port.

100 102

ScopeDome does not move centrally in front of the telescope

Andreas_Roland — Tue, 25 Nov 2025 12:04:38 +0000

We are using ScopeDome Arduino v10f13 software with driver 5.5.24. The telescope with the EQ8-Pro mount is controlled by N.I.N.A.

We have tried everything possible. Most recently, we tried to use the “DomMapPoints” dialog to ensure that the dome follows the telescope correctly. We defined four map points at intervals of approximately 90 degrees. But so far, the telescope always looks at the edge of the shutter instead of through the center. What are we doing wrong?

In the “DomMapPoints” dialog, the telescope could not be addressed with “slew to”; we always had to use Stellarium or N.I.N.A. for this.

We entered the offsets in the Config-> Dome dialog. We measured the values directly in the dome.

We also experimented with the SideOfPier parameter, but have not yet found a suitable solution.

It appears to us that there is some kind of offset that we have not yet been able to enter correctly. On the main dialog with the graphic for the telescope and shutter position (dome radar), the telescope always looks at the edge of the shutter, regardless of which position in the sky we have moved to. There were also hits in the north and south in exceptional cases, for example, when we entered a negative value for “Scope Position X (+S/-N)” instead of a positive one. However, according to the instructions and our checks at the observatory, this would be exactly the wrong way around. With this setting, targets in the east and west were still missed, i.e., the telescope looked at the edge of the shutter.

Thanks for help!

93 94

2m Scopedome rotation angle issue

jybeninger — Thu, 04 Sep 2025 08:33:12 +0000

Good day.

I have used a Scopedome 2m without much problems for 6 months - I just changed the controlling laptop and thought I entered exactly the same values as before - The old computer is dead ... I cannot check those values now.

An issue just appeared where the dome rotates more than it should: I visualise the rotation with a webcam to see what happens.

When just testing it, running with the ScopeDome Arduino Dome v10f13, shutter closed so as not to confuse it:

Goto 90 degrees, goes more than that

Goto 180 degrees, goes more than that

Goto 316 degrees will bring it approximately to the starting point (359 degrees is home)

Goto FindHome just moves slightly, 1 degree or less then Home reached and reading shows 359 degrees (Home).

I repeated exactly the same 3 times.
I switched off and on, same issue.

The values entered in Config/Card are: Encoder value for 360 degrees = 3681 clk (should I change this?) and in Config/Dome Home sensor set at 360 deg and Max rotate 360 deg.

Please advise.

Thank you very much

Jean-Yves

Dome randomly resetting encoder count and rotating dome

Chrosbahr — Fri, 29 Aug 2025 08:52:51 +0000

Hi

I am seeing 2 issues happening what seems to be at random.

Earlier this week I moved the dome to a position of 345 degrees. The encoder showed 135 steps.

A couple of days later, where there has been absolutely no activity in the observatory, the encoder shows 0 steps. I don't see anything in the logs - and the dome is still pointing at 345 degrees, but obviously reports as pointing north (encoder = 0).

Today, after yet a couple of days also without activity, the dome has physically rotated itself and now points at approx. 205 degrees. The encoder still shows 0. The logs show no sign of a "move" command.

The only suspicious thing I see in the log is an "Arduino command error" entry, which I don't know exactly what means.

What can cause this, and how do I troubleshoot it further? It is bad enough that the encoder resets itself, but I really don't like that it physically rotates the dome without any command to do so.

Thanks,

Christian

Power plug type

Chrosbahr — Thu, 14 Aug 2025 18:21:35 +0000

Hi
What kind of plugs are these, that are used to connect the 230V wires going from the dome box to the slip ring system?

Find Home position not working anymore

Bill110366 — Thu, 14 Aug 2025 10:26:36 +0000

After quite a few month with nearly no issues, I found my dome this morning open, and not in Park position.

NINA is set to close the Shutter, and park the dome to home position each morning after a shooting session. But today, it didn't work.

I tried to set "Find home", but the Dome is rotating with no stop at the park sensor. the Red "At Park" message never shows up as it physically passes though the sensor.

If I select "Go to home", It will slave the dome to Home position, and the Green "At Park" is showing up. That's ok. It knows the home position.

It looks like the home sensor is not working suddenly?

Any Tip or way to check if this sensor is out of service?

thanks

Eric

Cloudwatcher with SQM

Bill110366 — Fri, 06 Jun 2025 17:33:17 +0000

Hello everybody

I just received my new cloundwatcher including an SQM reader. System works really nice 👍 .

I like to use the SQM readout in the Dome Driver, and downloaded the ASCOM driver for the Cloudwatcher, but cannot find the correct driver in the SQM driver list of the dome driver?

Thanks

Eric

Manually moving shutter

Klaus Conrad — Mon, 19 May 2025 21:36:16 +0000

Hi - my site is remote, and i do not have physical access to it quickly. Tonight when shutter opened, it refused to close as the 'isclose' sensor seems to have gotten stuck in closed position. Thankfully i hope we will have good weather and no rain tonight, but if something like this happens, is there a low level override to run the motor directly and ignore 'isclose' or 'isopen' switches?