I will try to be a bit clearer.
For the moment I implemented a firmware on ESP32 to handle a focuser. On Ekos side the focuser driver connect the to the ESP32 via wifi. There is 2 servers running on ESP32. One that handle the focuser commands coming from EKOS and another that handle commands coming from a mobile device. I am not sure this is the best solution. This is why I wondered if it couldn't be better that the ESP32 could connect directly to the INDI server and act as a client.
Maybe it is a silly idea.
Hello to all,
This is a some time now that I play with ESP32. This little device has a lot of flexibility and allow lot of developments.
I wonder if it is possible to create a generic headless client of INDI on this device. The fact is, as I can understand, developing a client need to use the lib base of INDI. But there is no version to be used on ESP32.
The underlying idea is to make a Wifi network for high latencies devices as focusers, domes, mounts, etc...
So the question is, do I make a mistake when I want to create such client ?
In fact do I make an architecture mistake considering the INDI lib ecosystem ?
Thanks for your answer
I received two days ago my all new RisingCam IMX571.
Globally the camera works fine. But the beast is not easy to manage.
First, the gain value seems to be hard to handle as the slider in the control tab of the camera goes from 100 to 45000 (In the source of the INDI driver 0-->400 and there is a switch from LCG to HCG @900). I am not very confident in the value I can choose to shoot.
Another problem comes from temperature management. See joined screen capture.
And finally, I can't lock the debug option of the driver.
For the moment this is my first remarks on this cam.
I am waiting for clear skies and a less annoying moon to continue my tests.
Unfortunately it seems that the iOptron Legacy driver seems not to take in account the park position. If I store a park position in Ekos, the mount always go to a horizontal park position instead of the one that was stored.
The only position that is respected is the home position.
Returning to the starting pos is a better idea than going back to home or park. As my starting pos is "home" my problem might be solved.
I experiment this annoying situation which consist of being obliged to open the device manager to ask the mount to go to home. I know that all mounts doesn't have a home position. But would it be possible to add it if the "Home" option is available for the mount ?
For example in the polar align assistant when the process is finished it would be nice to have a button to click to ask the mount to go back home without having to open the device manager to do it.
Maybe the park button might also be present on same polar align panel.
This is an idea that crossed my mind. But I don't know how to do that. In fact, that will be an excellent option in the capture tab.
The SNR is computed with guiding camera, could it be possible to do it with the principal one, ans would it be a sufficient information to compute a capture time ?
A friend of mine has an EQ8. He controls it with a RPi on which I have installed a Kstars/Ekos/INDI version. This version is late of 2 version numb er I guess.
Last night we tested together the flip. In my case, with the latest version, it failed. In his case all worked fine.
Usually I shoot always from east to meridian or from meridian to west.
Yesterday as the weather wasn't really favourable for a good night of astrophotography.
So I decided to check how works the meridian flip.
My setup is compound with a Ioptron CEM60 and a Nikon D5300 as main camera.
I choose an object close to the meridian and start a capture session.
After having passed the meridian, the mount flipped. And ... nothing happened after that no more astrometry or calibration of the mount.
I suspected the camera to be responsible of it ... but the cam still worked fine.
I browse all configs but didn't find any reason to that behaviour.
If there is somebody using a setup close to mine do they notice such problem ?
To all the Kstars/Ekos/INDI users I wish an happy new year without any shitty Covid, with clear skies for many days.
See you next year.
I have a question about those cam that are very affordable.
I wonder if the toupcam are compatible with those risingcam that looks like clones of first one and maybe altair astro too.
I am very interested by the one that uses the IMX571 sony sensor.
If someone has informations about that...
Can somebody give me informations about using this camera used with INDI on PC and RPI4 ?
Is it as efficient and stable (firmware or sdk) as ZWO ASI ?
I tried to install Dragon on my laptop.
Hum, first it didn't worked for some missing libraries and second it crashed the indi server.
I had to get back compiling a indi server version with the previous SDK. The only positive thing I got is that now with lsusb command I see namely the QHY183M instead of an unknown usb device in the usb device list