Wait Altitude Behaving Strangely - firing too soon

Just to play with it I set up this script based on Betelgeuse rising past 30 degrees then 33 degree. It was at 27 degrees at the time. It recognizes the correct current altitude when both the Wait statements run as shown below, but then immediately fires the next action showing a much higher altitude. Anyu suggestions? I tried to make sure my current location was correctly set in the ASCOM driver and in TSX. I know I said I wouldn’t ask a question today but this is just puzzling me too much!

13:18:58 388 - Run Action => Wait Altitude: >= 30 [°] - ( RA 05 56 11 - DEC 07 24 25 ) - Timeout 00:00:00 [hh:mm:ss]
13:18:58 581 - Waiting Altitude Target 27 10 07.91 vs. Request 30 00 00.00 *
13:19:09 679 - Waiting Altitude done … Target 49 47 22.52 vs. Request 30 00 00.00
13:19:09 691 - Instruction [5]=> Expose: Filter [0] [Filter Slot 0] - 10 [s] - Bin 1 - Full Frame - Light - Exp - None
13:19:09 707 - Run Action => Expose: Filter [0] [Filter Slot 0] - 10 [s] - Bin 1 - Full Frame - Light - Exp - None
13:19:09 999 - Camera Expose : D:\ASI20494\Test\Exp_LIGHT__No_Filter__20190421_131909_994_W.FIT
13:19:10 019 - Dome Slave Manager : Dome Object is Null
13:19:10 457 - Exposing 10 [s] ; Filter=
* No Filter ** ; Type=LIGHT ; Binning=1 ; ReadoutMode=Default
13:19:22 977 - Expose finished
13:19:22 997 - Download started
13:19:23 326 - Download finished
13:19:25 668 - File FIT Saved (Exp_LIGHT__No_Filter__20190421_131909_994_W)
13:19:25 680 - Camera Expose Done
13:19:25 689 - Action Time [ATOMIC_CAMERA_SHOT] => 0 [m] 15 [s]
13:19:25 706 - Action Time Mobile Mean [ATOMIC_CAMERA_SHOT] => 0 [m] 10 [s]
13:19:25 724 - Instruction [6]=> Wait Altitude: >= 33 [°] - ( RA 05 56 11 - DEC 07 24 25 ) - Timeout 00:00:00 [hh:mm:ss]
13:19:25 745 - Run Action => Wait Altitude: >= 33 [°] - ( RA 05 56 11 - DEC 07 24 25 ) - Timeout 00:00:00 [hh:mm:ss]
13:19:25 904 - Waiting Altitude Target 27 14 27.58 vs. Request 33 00 00.00
13:19:41 023 - Waiting Altitude done … Target 49 47 22.52 vs. Request 33 00 00.00
13:19:41 055 - Instruction [7]=> Goto End

I cannot help you in this way, log is not complete and i cant see script.
Send script and complete log file to support mail and i’ll try to check, write version of voyager and timing about problem. Wait altitude work from a lot of years … if i touched something in the last daily build i need to understand. General post in a public forum without complete information can cause problems in support, i dont agree on this way. If something coming from a bug I’ll be the first to pubblish.

All the best
LO

Sorry Leo! I decided to try again with the Beehive Cluster and it’s an Easter miracle :wink:this time it worked like a charm. I’ll run again but looks like it was maybe just a glitch. Will let you know my results.

I sent you a report with logs and script.