We “inherited” an older telescope and building. The “clamshell” roof is controlled via an Opto22 SNAP-B3000-Enet interface and Digital and Analog IO units. To protect the equipment from adverse weather the roof controller has a Watchdog that checks values from the Aanlog inputs. The digital pins are used to switch relay’s on and off for the roof motors and to check the limit switches.
See attached images of the roof control circuits and screenshots of the read values from the Enet unit. I am able to interact with the IO unit using ioManager R7.1c from a windows PC. The unit is on a private network and is not connected to the Internet/WWW
The instruments/sensors feeding the Analog are no longer there, and is causing problems to open and close the roof as the Watchdog engages. I need to remove/bypass the watchdog in order to test the roof control from a new Python script to control the roof.
I have tried to download the config/logic file from the unit, but it just states that it cannot access the FTP site, and I also do not have the required RS232 connector to try that way.
How can I remove/deprogramme the Aanlog sections in order to gain access to safely operate the roof.
Appreciate the assistance/advise
Hendrik van Heerden
I was able to access the digital and analog bits as well which can be turned on or off, but it is still a bit confusing. Is there a how to guide that i can figure out how the wiring works with setting bits?
I also see there is a PPP communication section. Is this where I can set stuff like where ir downloads the files to and communicates?
Event/Reactions can be quite challenging to figure out. The analog and digital parts are connected through the Scratch Pad Bits. So there can be several layers to figure out.
If you can connect with ioManager, then PPP probably won’t add anything more.
You should consider contacting Product Support for further help.
Remove the analog input connector, this will set all those to zero, perhaps bypassing some of the interlock event reactions.
Inject specific analog voltages from an external power supply, thus fooling the event reactions into thinking everything is Ok to operate.
Delete the event reactions and use the new Python script to do all control sequencing.
Backup the B3000 using I/O Manger, reset it to factory defaults and reconfigure the I/O with your Python script
Hopefully, the last person to program the unit did the unthinkable and documented it. Event reactions can be tricky to reverse engineer; having some notes from the person who did it will be a huge help.
