ASCOM - SafetyMonitor


#4

Viking doesn’t support this I/O Card at now … if i receive the specification on protocol used for a particular Card i can add if license was purchased.

All the best


#5

Leonardo

Please tell me what I need to send you to look into the DigiLoggers switch. I know many observatories use it in the US. There’s no license necessary; it is controlled over https. I have written a few batch files to switch on and off specific relays and there is actually an ASCOM driver for it:

https://ascom-standards.org/Downloads/SwitchDrivers.htm

Roberto


#6

Ok Roberto,

i can import in Voyager like switch ASCOM. Like i do for Lunatico DragonFly, Tecnosky or PegasusAstro Ultimate Powerbox. But just for the user with license … like i tell you on the previous message.

All the best
LO


#7

Hi Leo

Just to check that the ASCOM SafetyMonitor did not make it to the latest best release? Thank you for the AltAz/RADEC update!

Roberto


#8

NO Roberto, I hope to do soon on the next daily build


#9

Hi Leo
Any chance of incorporating this feature in the next daily build? It’s the last piece of the puzzle for me to be able to fully automate with Voyager.
Thank you
Roberto


#10

Dear Roberto,

i have a lot of requests and a long to-do list … have faith on me !

All the best
LO


#11

Of course Leo - always! :wink:


#12

I’m just adding now what you ask but i want to be sure you understand working with it is a limitation of what Voyager can do in a normal way for Emergency management. You will lost one grade of security with SafetyMonitor.

All the best
LO


#13

Hi Leo

Thanks! :sunglasses:

What do you mean by losing a grade of security? :thinking: I am aware that by not using a full fledged cloudwatcher like device I can only get an IsSafe/NotSafe flag but that is sufficient for me.
All my Emergency Exits are driven by this flag and are all temporary. Permanent Exits for me only occur at the end of astronomical twilight.
Am I missing something else here?
Roberto


#14

Safe or not safe is only one grade … Voyager have a suspend and resume system event on plus.
With safe and not safe you can only decide if exit or no from Script or just suspend and resume. One only decision. Emergency exit in Voyager mean finish of all activities.

You found explanation here:
https://voyager.tourstar.net/index.php?title=DragScript_Flow_of_Control#Manage_2

All the best
LO


#15

Leo

It will have to be a Suspend/Resume for me. I assume I can run it in a loop with Voyager checking for an IsSafe flag to trigger Resume? That was my intention at least…

Roberto


#16

When you setting up in Voyager the SafetyMonitor you must choose if unsafe condition is Emergency exit or Suspend conditions … if you choose Emergency exit DragScript finish after do event blocks. If you choose suspend Voyager go in suspend event do block ad wait for resume (Is Safe in this case) to restart doing code in resume and continue script where is suspended or where you choose.

Now that is clear i can continue… thanks for your time.

LO


#17

Clear! Thank you!
Roberto


#18

Have your safety monitor driver an integration time before send Safe and Unsafe events ?
Because voyager have an integration time for I/O card events, wheater controls inside have integration time … if your driver doesn’t have it mean Voyager could bumping over decision.

LO


#19

Hi Leo
Yes, it can be set to wait a certain time before reporting Safe/NotSafe.
Thanks
Roberto


#20

My safety monitor is in fact a cloud/rain watcher IR based device. It has a “Clarity” measure just like Boltwood but the only ASCOM compliant driver for it is a SafetyMonitor one.
Internally it can be graduated to report safe/not safe conditions depending on different levels of clarity/clouds and/or rain.
Roberto


#21

OK thanks.

But this system can release a oneline file like the AAG or Booltwood or SkyAlert ?

LO


#22

Leo
No, it creates a log but not in the same format unfortunately.
Roberto


#23