Guess I took the scenic route locating this. It was simply in the ParkData.xml that the status was set to false for both the simulator and the actual driver.
Thanks for the help.
Yes,, using the roof simulator works on my laptop but not on the observatory machine. Same OS and supposed to be the same KStar and INDI version. But they obviously differ in some way and I will try and track that down.
I'm on Fedora and run update most days - 3.3.7 just became available this morning. Installing it fixed the graph display.
root@chai tg]# dnf list --installed kstars-bleeding
kstars-bleeding.x86_64 3.3.6-2.18 @lupinix-indi-bleeding
[root@chai tg]# dnf update --best --allowerasing
Last metadata expiration check: 0:05:18 ago on Fri 08 Nov 2019 09:54:29 AM EST.
Package Arch Version Repository Size
kstars-bleeding x86_64 3.3.7-2.1 lupinix-indi-bleeding 32 M
On the Dome::isRolloffRoof() check it supposedly should succeed. The only call I find is capability being set as per the rolloff simulator.
SetDomeCapability(DOME_CAN_ABORT | DOME_CAN_PARK);
This log is from when it was raining.
I have lost track of when this was first noticed but at startup the observatory always shows the roof as open. The rolloff roof status and switches do not agree. Also the graph is no longer appearing.
Has there been any interface requirement change for a rolloff roof? I just did a rebuild of mine but it didn't help.
I'm not seeing anything wrong here in my setup after running it overnight. It is an interesting display the way it adjusts with time and temperature. The Observatory information is matching the values seen from the Vantage driver. It is responsive to the unsafe status returned from the Weather Safety Proxy driver's curl requests and external park/unpark requests to the roll off roof driver. Looks good.
What is the correct git command to fetch the modified source?
I tried variations of the git command using git clone git://github.com/sterne-jaeger/kstars/tree/observatory_sensor_graphs/ as the base without success. Then clicked on the code tab and used the link shown in the dialog or clone box which did fetch kstars.
git clone git://github.com/sterne-jaeger/kstars.git.
After the build I am not seeing the graph so assume I fetched the wrong code.
Just a thank you. I used your cloud and rain sensor code to add the same to my obs. I did not use a Raspberry Pi, just the Arduino and ran the web server on the Ekos machine. Then instead of the driver, polled the web server from the Weather Safety Proxy driver as suggested here. The Observatory module took it from there detecting the unsafe condition when raining.
I use the daily build. KStars 3.3.6, INDI 1.8.1-2.6. Guide camera ASI 174.
Cable drag and balance might be a factor although neither were adjusted going from bad to good guiding.
Did the same image again last night with similar results, started badly and gradually became stable. In my
case I'm thinking it might be associated with the location in the sky which was directly overhead. Started
settup right after a meridian flip, combined perhaps with balance or cabling. As the target moved a little
westward things calmed down, just a thought.
I was having a hard time with guiding last night, took about 1.5 hours to get it going.
The swings were very high, going off scale and needing a restart. This was using settings
untouched from earlier nights when guiding was acceptable. Seeing was average and a nice
clear night better than most here. The last few things changed were:
- Disable dithering, didn't seem to be related but left it disabled
- Reduce pulse
- Algorithm changed from SMART
- Use of subframe (since this was the last thing changed before guiding worked for more than a few minutes)
After these changes the RMS error averaged 0.4 for the remaining 2 hours of time.
I do not know when the FOV became 5.6x5.6 but did not touch it since things were working.
Star: Manual select
FOV: 84x53 (5.6x5.6)
Guide Rate: x1 (Mach1)
Exposure: 3 seconds
Max pulse: 900ms
Min pulse: 30ms
Same here, commented on it in
Think restarting KStars was my way of getting going again.