Reset dome position

Hardware Control
#1

Dear,

Prism V10 10.4.11.908.
I’m experiencing some troubles regarding closing the dome after an automated session with the LESVEDOME.NET drivers. But i think the problem is Prism related.
I have setup as : Perform Reset Dome position and then close.

So when the automated session is over, the program asks for dome resetting to home point, but just 0.005 seconds later it is already at home point. which of course is not. This causes the shutters relays to be activated and the closing time for the relays is running. (3 minutes closing time ). After 1.5 minutes, the dome is at the actual home point and the shutters are closing effectively. But after another 1.5 minutes the power to the shutter motors is again supressed and the dome is not fully closed.

Look at this copy out of the prism auto obs logs:

UTC 2021-02-25 01h21m18.541s : [Dome] Initiating reset/homing
UTC 2021-02-25 01h21m18.549s : [Dome] Reset/homing completed
UTC 2021-02-25 01h21m23.637s : [Dome] Close Dome/Shelter requested

UTC 2021-02-12 01h47m52.420s : [Dome] Initiating reset/homing
UTC 2021-02-12 01h47m52.427s : [Dome] Reset/homing completed
UTC 2021-02-12 01h47m57.469s : [Dome] Close Dome/Shelter requested

When i use the manual : " reset AZ" button in the Dome operating window, the dome actually goes to the home point.

Hope this bug can be solved soon.

Thank you.

#2

“but just 0.005 seconds later it is already at home point. which of course is not.”

That means Prism sees the dome controller in this state.
Is there an ASCOM driver log ?
Combined with Prism Log, this could help understanding where the issue lies.

`

#3

Dear all,

I had not enabled the prism log so i only go the auto obs log. There is the lesvedomenet driver log.
I copied a part of the actual finding home and closing:

The auto obs log :
UTC 2021-02-25 01h21m18.541s : [Dome] Initiating reset/homing
UTC 2021-02-25 01h21m18.549s : [Dome] Reset/homing completed
UTC 2021-02-25 01h21m23.637s : [Dome] Close Dome/Shelter requested

The Lesvedomedriver log:
2021-02-25 01 21 18.546 HW_FindHome - DomeAzimuth=57,0
2021-02-25 01 21 40.576 SlewHome complete, Dome Az was = 124,3
2021-02-25 01 21 40.851 HW_Move: 023,4
2021-02-25 01 21 40.860 HW_CloseShutter
2021-02-25 01 21 40.860 HW_FindHome - DomeAzimuth=123,6
2021-02-25 01 21 40.871 Position correct for shutter operation, starting to move it
2021-02-25 01 23 29.051 SlewHome complete, Dome Az was = 118,6
2021-02-25 01 24 40.918 Shutter timer has expired

As you can see: The lesvedome driver detects the actual home position 22 seconds later from : Find home position. But Prism does not and actually already activates the closing relays.

I can try and test tonight with automated observations. This can not run during daylight, right?

#4

can you please provide us with the entire logs. Please attach them here or upload to a service such as dropbox. It is important to know the “whole story” :smiley:

#5

Dear All,

thank you. This evening i did a test run with the automated observations:
Slewing to 3 points, grab one image and in the end : reset dome and then close dome.
Again the same error.

Here is the wetransfer link.
Closing sequence starting points:

LesveDomeNET file:
Rule 61: 2021-03-09 18 26 46.353 HW_FindHome - DomeAzimuth=8,1

Obsauto log:
Rule 98: UTC 2021-03-09 18h26m46.294s : [Dome] Initiating reset/homing

Prism big log (level 4)
Rule 61507: @[10656]: UTC 2021-03-09 18h26m46.294s {34.3 ms} : [ObsAuto] [Dome] Initiating reset/homing@

Again the same error: When the dome is actually at home point the shutter motors are already activated and the closing stopts half its way because the timing expires.

Also a problem at startup witch i don’t know why but every time this happens:
When i want to try opening the dome: the dome will automaticly start rotating, even when it is on its home point already and giving a O/I input signal on the velleman board. I don’t know what Prism does not “look” first to see if it is at home point, before start rotating.

Thank you.

#6

Is this problem been investigated? :slight_smile: