I’m trying to use this feature so I’ve set up a simple test to familiarise myself:
NGC281 - RA: 00 52 59.300 and DEC: 56 37 19.00 currently the transit time for this is 21:31 GMT which is in about 1 hours time. I want to set this up so that it will start imaging if the object is between 3 hours before and till 2 hours after transit - I would expect the before and after values to be set to -3 and +2 (relative to the meridian).
This is what’s shown on the monitor after widening the values:
20:42:09 166 - Run Condition => DO IF HA BETWEEN: Between -7 and 7 [Hours] - ( RA 00 52 59.300 - DEC 56 37 19.00 )
20:42:09 171 - Check HourAngle … OUT OF RANGE ! Target HA 07:15:47 vs. Request Interval [-07:00:00 <-> 07:00:00
It could be my understanding is incorrect or I’ve done something wrong but I can only get this to work if I increase the start value to -8 hours. I haven’t checked the Sequence editor.
Am I using this correctly ?
i dont understand exactly your request. Your setting are an interval of HA -7 and +7 , 7.15 are out of +7.
So i dont found anything wrong in what reported from monitor.
About coords i cant thelp if are right and also about your setting in latitude and longitude are right in your system.
Anyway forum is not the right way if you need support, please collect log and dragscript (remove personal info) and send to support mail you found in your license mail. If there is a bug in this function we’ll try to understand how to fix, or if there are something wrong in your setting we can help to fix.
All the best
Sorry Leo, I will respond as requested.
Shall I delete this post ?
No problem Robert, no delete. We use this post for solution and info about when we receive mail.
If HA is “-” then HA is how long before the star will transit the meridian. For example, -3 HA means the star will transit the meridian in 3 hours. NOTE: -6 HA means the star is located on the Eastern horizon and will transit the Meridian in 6 hours.
If HA is “+” then HA is how many hours earlier the star passed the meridian. For example, +2 HA means the star passed the meridian 2 hours earlier. NOTE: +6 HA means the star is now located on the Western horizon and passed the meridian 6 hours earlier.
Therefore, when you put -7HA to +7HA you asked Voyager to begin the sessions when the star is 1 hour BELOW the eastern horizon (meaning it will take 7 hours to transit the meridian) and to stop when it is 7 hours past the meridian, or 1 hour below the western horizon.
Given that you want to begin the session when the star is within 3 hours before the meridian and no later than 2 hours past the meridian then you would use:
DO IF HA BETWEEN: -3 and +2.
Another way to look at this is,
“-” HA means the star is in the Eastern sky and is rising,
“+” HA means the star is in the Western sky and is setting.
Hi Craig thanks,
i think Robert talk about he expect object to be 1 hour before meridian and in monitor read 7h 15m before.
I need log to understand if there is something set up wrong … or there is a bug in block code.
All the best
i just do some test with a simple script … i cannot found any problem for NGC281. Transit is correct and HA check also:
For your info
Sorry, just got to the computer. Thanks very much for the example, I’ll double check everything - there can’t be much wrong but there’s obviously something I’ve missed.
Craig, thanks for your input. the -7/+7 were just settings to fool the IF HA condition, originally I was using -3/+2.
I’ve got to understand where the 7h 15m came from when it should have been one hour.
Calculation data coming from mount and PC, so something wrong in latitude, longitude, date and time.
Log will help to understand.
All the best
I think there’s something up with my PC as I can’t even open voyager help. What did run though correctly was the simple example you provided but even though my dragscript is set with the same values it jumps through the IF statement.
I can’t do much more now but I’m going to run some memory diagnostics tomorrow evening as chkdsk is clean.
Many Thanks for your help
Yes you were right about the telescope setup. I was using the ASCOM Mount simulator (due to the weather) and the time was incorrect. Once set via the GPS option it all started working correctly. Some of my confusion was based on an Emergency Suspend being initiated as the end of Astronomical Night had been reached - of course it had based on the Mount simulator time !
Thanks very much for your pointers, all’s well now.