ok it's more clear now and it's quite an odd behavior that I didn't experienced when I was using sky flats.
But increasing the tolerance should lower the chance of hitting the threshold during a entire session of flats (at least for each of the filters).
I mean, if you set 16000 +/- 4000 the chance that all the 40 (maybe better to lower to 20) flats ADUs are in the 12000-20000 range is greater. So no need for 'cycling'.
And having flats with a wide range of ADUs is ok as long as they are normalized during integration.
I see that this is not a solution to your issue but more a workaround to avoid it.
Ferrante
Read More...
about the first issue, the 'Tolerance' allows to adjust the valid ADUs range. Have you tried to increase it?
Sky flat ADU values change rapidly so having an higher tolerance should help preventing the issue.
The log that you attached seems to show a correct behavior, it captured 3 out of 40 images and it's not in a infinite loop.
To me the double image in the log seems to be caused by a double logging of the same image but to be sure it should be looked into the source code.
Do you get 80 images instead of 40?
The log shows an interval of about 12s between a capture and the next, while the exposure is only 1s.
Did you set a 'delay' of 10s? if this is the case, I would decrease it, it will help to have ADUs in the correct range.
Ferrante
Read More...
hi Gunter,
in my case (it's a roll off roof, not a dome) abort.py is meant to immediately stop the roof motion.
About the state, what kind of communication you have from/to the device? I mean it's over http, local serial/usb port?
If it's http for example, status.py could be used to poll the device status as the protocol is asynchronous and to update the /tmp/indi-status file.
As these template scripts are executed outside of Ekos, any return value like the parking status (roof open or roof close) must be send to Ekos in some way.
In park.py, if parking is successful, the file 'indi-status' stores the value '1 0 0' ( '0 0 0' if roof open) then Ekos reads this value and so is aware of the parking status.
Btw if the protocol is http I found more efficient that status.py periodically read/write the /tmp/status-indi while park/unpark/abort just manage to issue commands to the device.
If you want a more stable integration of your device (roof or dome) with Ekos consider writing a new INDI driver and not to rely on these scripts only*. My approach (it's the third time so far) is to use the scripts at first and in the meantime write and test the INDI driver.
* one big issue with the scripts (in the roof case) is that only parked / unparked states are sent to Ekos. There's no way as far as I know to tell Ekos that the roof is moving opening or closing etc.
Ferrante
Read More...
it seems that Jasem already fixed this issue as part of another one.
github.com/indilib/indi/issues/1582
I will test and report here if it works fine with the scheduler as well. thanks again for your support.
ferrante
Read More...
Looking at the code seems that the park() method is not managing lights.
I will open an issue on github providing these informations. Probably Jasem should look into it because the bug could also be in the parent lx200 and I immediately got lost in the class hierachy.
Thanks a lot for your help.
Ferrante
Read More...
hi Wolfgang,
you're absolutely right: The parking light is always green, also during slewing and parking. But the messages in the log are reporting parking and parked correctly (see attachments).
So the scheduler rely on the status light been green/yellow to proceed to the next shutdown step? isn't there a 'parking status' variable in Ekos?
Thanks,
Ferrante
Read More...
hi Wolfgang,
sorry to bother you with this issue again, but I still struggle to understand the LX200 driver/Scheduler interaction when the shutdown procedure runs.
I see a different behavior when switching from LX200 mount driver to Simulators (Simulators has the expected behavior so the issue is likely on LX200 side), see logs below.
I'm not familiar with the scheduler code, what triggers the 'mount parked' status? It would help me to understand if the LX200 driver is issuing the wrong message.
LX200 logs:
[2021-12-26T21:00:40.086 CET INFO ][ org.kde.kstars.indi] - "FITS" file saved to "/home/ferrante/NGC2081/Light/Luminance/IC_4632_Light_Luminance_1.500_secs_2021-12-26T21-00-40_002.fits"
[2021-12-26T21:00:40.143 CET INFO ][ org.kde.kstars.ekos.capture] - "Download Time: 0.19 s, New Download Time Estimate: 0.20 s."
[2021-12-26T21:00:40.287 CET INFO ][ org.kde.kstars.ekos.capture] - "Received image 2 out of 2."
[2021-12-26T21:00:40.535 CET INFO ][ org.kde.kstars.ekos.scheduler] - "Job 'NGC2081' is complete."
[2021-12-26T21:00:40.700 CET INFO ][ org.kde.kstars.ekos.scheduler] - "No jobs left in the scheduler queue."
[2021-12-26T21:00:40.700 CET INFO ][ org.kde.kstars.ekos.scheduler] - Starting shutdown process...
[2021-12-26T21:00:41.690 CET INFO ][ org.kde.kstars.ekos.scheduler] - "Parking mount in progress..."
[2021-12-26T21:00:41.703 CET INFO ][ org.kde.kstars.indi] - LX200 10micron : "[INFO] Parking. "
[2021-12-26T21:00:41.729 CET INFO ][ org.kde.kstars.indi] - Hakos Roll Off Roof : "[INFO] Telescope status changed. Lock is set to: unlocked "
[2021-12-26T21:00:41.962 CET INFO ][ org.kde.kstars.indi] - LX200 10micron : "[INFO] Gstat changed from 0 to 2 "
[2021-12-26T21:00:42.699 CET INFO ][ org.kde.kstars.ekos.guide] - "Mount is moving. Resetting calibration..."
[2021-12-26T21:00:42.700 CET INFO ][ org.kde.kstars.ekos.guide] - "Calibration is cleared."
[2021-12-26T21:00:42.708 CET INFO ][ org.kde.kstars.ekos.scheduler] - "Mount parked."
[2021-12-26T21:00:43.694 CET INFO ][ org.kde.kstars.ekos.scheduler] - "Parking dome..."
[2021-12-26T21:00:43.696 CET INFO ][org.kde.kstars.ekos.observatory] - "Rolloff roof is closing..."
[2021-12-26T21:00:43.726 CET INFO ][ org.kde.kstars.indi] - Hakos Roll Off Roof : "[INFO] Roof is parking... "
[2021-12-26T21:00:44.724 CET INFO ][ org.kde.kstars.indi] - Hakos Roll Off Roof : "[INFO] Dome state PARKING. "
[2021-12-26T21:00:44.725 CET INFO ][org.kde.kstars.ekos.observatory] - "Rolloff roof stopped."
[2021-12-26T21:00:49.732 CET INFO ][ org.kde.kstars.indi] - Hakos Roll Off Roof : "[INFO] Dome state IDLE. "
[2021-12-26T21:01:04.720 CET INFO ][ org.kde.kstars.indi] - Hakos Roll Off Roof : "[INFO] Dome state IDLE. "
[2021-12-26T21:01:07.119 CET INFO ][ org.kde.kstars.indi] - LX200 10micron : "[INFO] Gstat changed from 2 to 5 "
[2021-12-26T21:01:07.129 CET INFO ][ org.kde.kstars.indi] - LX200 10micron : "[INFO] Mount is parked. "
[2021-12-26T21:01:10.118 CET INFO ][ org.kde.kstars.indi] - Hakos Roll Off Roof : "[INFO] Resuming Park command. "
[2021-12-26T21:01:10.119 CET INFO ][org.kde.kstars.ekos.observatory] - "Rolloff roof is closing..."
[2021-12-26T21:01:10.128 CET INFO ][ org.kde.kstars.indi] - Hakos Roll Off Roof : "[INFO] Roof is parking... "
...
It seems that the scheduler sets the mount as parked at 21:00:42.708 when the LX200 driver is still parking ('Gstat changed from 0 to 2'*).
But the LX200 driver issues the mount parked message ~25 sec later 21:01:07.119 ('Gstat changed from 2 to 5'*).
While with simulators, the driver and scheduler act as expected.
Simulators log:
[2021-12-28T12:31:26.689 CET INFO ][ org.kde.kstars.indi] - "FITS" file saved to "/home/ferrante/NGC_7242/Light/Luminance/IC_4632_Light_Luminance_1.500_secs_2021-12-28T12-31-26_004.fits"
[2021-12-28T12:31:26.753 CET INFO ][ org.kde.kstars.ekos.capture] - "Download Time: 0.20 s, New Download Time Estimate: 0.21 s."
[2021-12-28T12:31:26.890 CET INFO ][ org.kde.kstars.ekos.capture] - "Received image 2 out of 2."
[2021-12-28T12:31:27.026 CET INFO ][ org.kde.kstars.ekos.scheduler] - "Job 'NGC 7242' is complete."
[2021-12-28T12:31:27.360 CET INFO ][ org.kde.kstars.ekos.scheduler] - "No jobs left in the scheduler queue."
[2021-12-28T12:31:27.361 CET INFO ][ org.kde.kstars.ekos.scheduler] - Starting shutdown process...
[2021-12-28T12:31:28.328 CET INFO ][ org.kde.kstars.ekos.scheduler] - "Parking mount in progress..."
[2021-12-28T12:31:28.330 CET INFO ][ org.kde.kstars.indi] - Telescope Simulator : "[INFO] Parking to RA: 1:05:33 - DEC: 0:00:00 "
[2021-12-28T12:31:29.327 CET INFO ][ org.kde.kstars.ekos.scheduler] - Parking mount in progress...
[2021-12-28T12:31:29.336 CET INFO ][ org.kde.kstars.ekos.guide] - "Mount is moving. Resetting calibration..."
[2021-12-28T12:31:29.337 CET INFO ][ org.kde.kstars.ekos.guide] - "Calibration is cleared."
[2021-12-28T12:31:30.327 CET INFO ][ org.kde.kstars.ekos.scheduler] - Parking mount in progress...
[2021-12-28T12:31:31.327 CET INFO ][ org.kde.kstars.ekos.scheduler] - Parking mount in progress...
[2021-12-28T12:31:32.327 CET INFO ][ org.kde.kstars.ekos.scheduler] - Parking mount in progress...
[2021-12-28T12:31:33.327 CET INFO ][ org.kde.kstars.ekos.scheduler] - Parking mount in progress...
[2021-12-28T12:31:34.327 CET INFO ][ org.kde.kstars.ekos.scheduler] - Parking mount in progress...
[2021-12-28T12:31:35.327 CET INFO ][ org.kde.kstars.ekos.scheduler] - Parking mount in progress...
[2021-12-28T12:31:35.402 CET INFO ][ org.kde.kstars.indi] - Telescope Simulator : "[INFO] Mount is parked. "
[2021-12-28T12:31:35.403 CET INFO ][ org.kde.kstars.indi] - Dome Scripting Gateway : "[INFO] Telescope status changed. Lock is set to: unlocked "
[2021-12-28T12:31:35.404 CET INFO ][ org.kde.kstars.indi] - Telescope Simulator : "[INFO] Telescope slew is complete. Parked "
[2021-12-28T12:31:36.327 CET INFO ][ org.kde.kstars.ekos.scheduler] - "Mount parked."
[2021-12-28T12:31:37.327 CET INFO ][ org.kde.kstars.ekos.scheduler] - "Dome already parked."
[2021-12-28T12:31:39.327 CET INFO ][ org.kde.kstars.ekos.scheduler] - "Shutdown complete."
[2021-12-28T12:31:39.329 CET INFO ][ org.kde.kstars.ekos.scheduler] - Scheduler is stopping...
Thanks,
Ferrante
* As to the LX200 driver, the codes status are:
0, GSTAT_TRACKING: SCOPE_TRACKING;
1, GSTAT_STOPPED: SCOPE_IDLE;
2, GSTAT_PARKING: SCOPE_PARKING;
3, GSTAT_UNPARKING: SCOPE_TRACKING;
4, GSTAT_SLEWING_TO_HOME: SCOPE_SLEWING;
5, GSTAT_PARKED: SCOPE_PARKED;
Read More...
these template scripts are executed outside of Ekos, so any return value like the parking status (roof open or roof close) must be send to Ekos in some way.
In park.py, if parking is successful, the file 'indi-status' stores the value '1 0 0' ( '0 0 0' if roof open) then Ekos reads this value and so is aware of the parking status.
That's the meaning of the coordinates function.
Ferrante
Read More...