After 4 years, my SHUTTER went wonky? help

Lately - the shutter has been hit or miss. Often closing part way and stopping. I have to use the serial communication to set @PWS,10000 then @CLS It seems to hit PRS0 on it's own to soon> so I've delt with this. Last night it didn't close and today it's really wacked. I click OPEN and it tried to close. I hit close and it just makes a jump. I rebooted all - no help. I used NINA, DeviceHub and Arduino serial commands. (btw WHAT IS THE OPEN COMMEND VIA SERIAL? ) like @CLS to close. I want to send open and can't seem to get it to go.

2 comments

2 Comments

Rodolphe

Oct 22, 2022

•

The open command is @OPS (OPen Shuter)

As for the other problems, there might be some mechanical issue. Can you check the the plastic tab behind the track is applying enough pressure on the track so that the sprocket doesn't jump ?

Also check the connection for the open and close sensor as some of the thing you see could be related to the controller not "seeing" the limit magnets, or seeing them when it shouldn't.

You could try to reset to factory default and power cycle both controllers : @ZDR and then @ZWR (to save)

You can find all the commands there : https://bitbucket.org/tigra-astronomy/nexdome-ascom-driver/wiki/Protocol

This is only for the NexDome V3 (not the new Beaver controller or previous version of the NexDome controller).

cauchy

Nov 29, 2022

Replying to

Interesting, my shutter started doing the same thing about a month ago (coincidence?). Never was an issue before and is not mechanical.

I wrote a python script that resets the position and closes using the serial protocols, when voyager detects the shutter is not close (voltage detector).

It is odd. If I power off the shutter (and rotator), then re-establish connection, it seems to be fine for a few nights, then has problems again.

Going to try a factory reset. Did that work for you Ron?