I went out and confirmed that the console was reading the correct temperature, -20°C.
I've been using a Davis Vantage Pro2 for weather monitoring out in the field and I've noticed some interesting readings.
Winter is starting to show its teeth here in Minnesota and things have gotten quite cold. The Davis system, that I'm running through INDI, is starting to show values around 3600°C!
After reviewing the logged data it seems that temperature is still being tracked properly, just at a massive offset. It seems to roll over at temps below -17.78°C to 3623°C.
I haven't had a chance to go out and see if the console is giving the same readings, however.
Ultimately, this isn't a major issue, for myself, but I figured it was worth noting.
Here is a directory with the needed python files from the PlaneWave website.
There is a zip file labeled pwi4_python.zip which should have everything you need.
Keep in mind that PWI4 must be running while using the scrips provided.
That sounds fantastic! Any idea where I should start digging? I looked through the QHY driver properties and could not find anything resembling a rapid capture mode.
I've been attempting to get an automated observatory up and running which would take images extremely quickly. I have been using a QHY 183M CMOS camera and have noticed that if I take a rapid sequence of exposures the vast majority of them will not be saved. I suspect that this is a file write speed issue but have been unable to verify this. I've attempted to save the FITS files to an external drive (HDD) thinking that the external drive would be able to dedicate all its write speed to the incoming FITS files but I did not notice increased performance.
Before I invest in getting an external SSD or some other more exotic solution, I was hoping someone on here may have some experience in this area. Any advice or guidance would be greatly appreciated.
For those who may run into the same issue I did in the future...
If you enable debug and see that a script is returning 512 you need to add "#!/usr/bin/python" to the beginning of your script.
I've been working on bridging the gap between Ekos and a telescope mount with no INDI drivers. I figured using the Telescope Scripting Gateway would be a straightforward way to do this as the mount has a Python API. Unfortunately, I can't seem to get the connect script to work. Despite ending the script in "sys.exit(0)" Ekos continues to return that it failed to connect.
I can't seem to find any documentation on the scripting gateway outside of the text file "telescope_script.txt"
If someone could point me in the right direction that would be greatly appreciated.
I did the same and the QHY camera is now detected!
After a fresh installation of Ubuntu MATE (20.04) the problem seemed to persist.
After installing Raspberry Pi OS, Ekos had no issue finding the camera. And everything seems to work as it should.
Considering Ubuntu MATE for the Pi 4 is still in beta I'm not sure who's end this issue is coming from.
At any rate, its worth noting that other devices (Celestron SCT focuser and Celestron CGX mount) had no issue connecting under Ubuntu MATE.
I've run into an issue where Ekos will not detect a QHY 183M camera. When Ekos is started I receive the message "No QHY cameras detected. Power On?"
I am running a Raspberry Pi 4 with Ubuntu MATE as it's OS (with the latest QHY INDI drivers). I have been able to connect to the same camera using a laptop running Ubuntu 18.04.
I did try connecting to the camera directly though INDI using "indiserver indi_qhy_ccd" but, again, it was not detected.
The camera is listed under the list of devices outputted by "lsusb"
Any advice would be greatly appreciated!
Yes, Planewave Interface 4 starts up a local server that can receive commands via typing them into the url.
Planewave has written a class in python that does all the url inputs for you.
I've been working with a Planewave L-350 mount for the past few months with the goal of automating its use. Unfortunately, Planewave has yet to develop any ASCOM drivers.
I had the idea to use the INDI telescope simulator as a bridge between Ekos and Planewave Interface 4. I've managed to write a script that will update the position of the simulated telescope (using sync) after the L-350 has settled on a target but the coordinates of said target have to entered manually. Ideally I would like to have Ekos only read the telescope sim info rather than submit new positions for it to go to and a way to communicate targets from the Ekos scheduler (preferably in python). I have looked over the DBus documentation and could not find anything resembling these two goals. Any advice would be greatly appreciated!