I have actually reported thé issue hère: github.com/indilib/indi-3rdparty/issues/822
Basically there seems to bé an initialization issue with thé camera, that fails tobstart properly quitte often depending on thé way it has been poweresld/unpowered.
I am actively looking for other users of this caméra to unferstand if thé issue I reported Can bé reproduced with other caméras of thé same model
If you have this caméra I would bé good to hère from you about thé behaviour of thé camera when powering 12V first for instance.
Thanks you in advance for your help.
Any update about driver for the GIOTTO ?
I am very much interested in this device as well, anyone has tested it ? In particular the "localized" cloud detection ?
This is not a direct answer to your question, but I am developing a robotic observatory management software in python (that includes an full python indi client), and broadcast some information on mqtt topics.
My full stack includes mosquitto, telegraf, influxdb, and grafana, I personally use grafana to monitor the observatory, but from what I know, HA can also query influxdb with flux query in a very similar way telegraf does.
That's a potential idea for you if used together with infi-mqtt from @rkaczorek
I recently came across this issue while trying an automation scenario.
The focuser simulator was not able to change the focus of the Guide Simulator camera, even if there was focuser simulator in the list of snoop device.
I was wondering if it was possible either to instanciate a guide simulator that would have a proper focusing curve, or to instanciate two ccd simulator on the same server.
Thank you in advance for your help
Nice, thank you very much for your answer, I didn't know the command "indi_setprop" existed, this is quite handy for debugging !
I am using a custom python implementation of indi client (not the official pyindi, that I stopped using a while ago because of poor maintenance status).
Actually I realized what was the issue, and it was not related to the lx200 mount driver implementation.
I was sending 2 TARGET_EOD_COORD set in a row, without waiting for the end of the goto.
What happened is that I was received a TELESCOPE_ABORT_MOTION switch, and the TARGET_EOD_COORD was set to IDLE value (instead of the BUSY I expected).
I fixed my script and now everything is working as expected
I used to go check the following documentation to undersand basic propoerties of cameras/telescope and write scripts for my equipments
Recently, I found myself in trouble while someone tried to used a piece of software I used, that contained a simple "goto".
In practice the goto amounts to do that:
set number 'EQUATORIAL_EOD_COORD' to specified value
wait until EQUATORIAL_EOD_COORD light goes from IPS_BUSY to something else (either IPS_ALERT or IPS_OK)
Usually, for instance in the simulator, the light goes to IPS_OK when the slew is over, and the telescope is at the desired psition.
Relevant code for this behaviour can be found there:
However, for lx 200 based driver, it looks like the behaviour might be different, but this is not 100% clear to me:
It looks like the IPS_BUSY has been commented out, and instead, the TrackState (from enum TelescopeStatus) is updated. Unfortunately, from what I know, the TelescopeStatus is not exposed as either a read-only switch or something else, making it impossible to synchronize properly on the end of the slew.
Am I understanding the issue correctly or not ?
Thank you in advance for your help.
Client is on a x86 laptop and server/driver on a 4GB SBC ~30% more powerful than a rasbperrypi4 (rock64pro from pine64). I tried with 8bit and lowest resolution but didn't get better results unfortunately. But the outcome seems more or less random, I will try to reduce the potential source of errors in my next attempt, IE, much better network, changing usb cable, etc...
I tried changing the auto-exposure (enabled by default ?) in the controls tab.
I have an Altair AA 183MM Pro, that I bought specifically to use with indi. Unfortunately, I haven't been able to use it properly, as I often need to reboot something (either the driver or the indiserver or the ekos indi client crash or become unusable).
Anyway, let start with a bug I can easily reproduce.
Whenever I launch indiserver with indi_altair_ccd driver alone:I get a very weird behaviour after I have launched an acquisition, on the client side, I basically end-up with a completely blank client (and of course never manage to get the nice image pop-up as it works with the asi driver for zwo ccd):
Sorry I don't have the 269 c, However I have the Altair AA183M Pro and I must say I am pretty disappointed by the driver. It keeps crashing, making ekos indi client completely buggy or unreliable. To me it is a pretty bad product/driver pair, and I will never invest again in Altair hardware.