The OS is Ubuntu 18.04
My camera will run to a dead loop when "Dark" in enabled, and works good when "Light" is enabled.
There is an option in the INDI control panel of a camera which is "Dark", and also "Flat", "Bias"
So what is the meaning of these options?
I assume that this will drive the mechanical shutter to close to capture "Dark".
While some cameras do not have a mechanical shutter to do "Dark".
But the option is still available.
When the "Dark" is set, the camera will work strangely.
ap-i.net has just released the 64-bit version of skychart, ccdciel, libpasastro, indistarter and eqmodgui
Lin_guider does not need a 'driver' to run the qhy camera, but the firmwares. So these firmwares could make Lin_guider work, on qhy cameras - ex. my qhy5L-II
T-Studio wrote: Mr. Ecloud
Thank you for information.
Certainly Skychart could not install from deb file.
On Rpi 3 or Intel 64 bit machines it worked with firmware, but it was not available on this machine.
Did you work in your environment?
Products of Chinese vendors (QHY and ZWO) feel that support of LINUX is not good.
(Although expensive, Lodestar works better.)
ASI cameras have not been tested yet. But ASI do work with Indi nightly.
1. ASI driver is broken with the stable build, so the nightly is needed.
2. By now I did not find any crash of the nightly kstars and ekos.
3. Skysafari driver will run to full of cpu sometimes.
4. CCDCiel is stable, Munipack is stable, Siril is stable.
5. Skychart can not be installed with the deb. Need to compile from the source.
For both 32-bit and 64-bit and even X86
The Lin_guider could not work without QHY firmware. But there is conflict between the deb package from the sourceforge and Indi-qhy driver. It's very easy to fix this issue. Download the attachment and extract to /lib/firmware/qhy
I'm wondering why the firmwares are not installed into this dir by indi...
File Attachment:File Name: qhy_firmware.tar.gz
File Size: 51 KB
I'm writing email to the support to query this, and also I'm planning to install tigervnc which can support Display:0 and also a virtual display.
PK wrote: Yes, it stops on my T4 with Lubuntu too. I have not yet tried another VNC server install yet.
And also I'm thinking about to purchase a 13 inch LCD for focusing (I have no auto focuser) and for flat captures.
I found an app - fim , which can display a true full screen picture in console without any task/tool/status bars. So this could be as a flat plate.
Did you find that x11vnc very unstable?
I have the NanoPC T4 with FriendlyDesktop installed.
The x11vnc always crashes.
Is there anyone that has got this issue?
Sometimes the app will run full of cpu at 200% (two threads?) with no skysafari connection.
I just start the server, do nothing with skysafari, capture in ekos, and this could happen.
root@AstroT4:~# indiserver indi_asi_ccd
2018-10-05T10:10:32: startup: indiserver indi_asi_ccd
2018-10-05T10:10:55: Driver indi_asi_ccd: stderr EOF
2018-10-05T10:10:55: Driver indi_asi_ccd: restart #1
Child process 1549 died
So should I try to Nightly Builds or change to 32-bit OS?
I'm planning to install INDI and other astro apps on NanoPC T4
Which OS type is preferred to run these apps on ARM, 32-bit or 64-bit?
According to my experience on X86, the 64-bit linux is better.
I can see the SDK is already ver 0.7 on ZWO official web.
But it shows 0.6 in INDI v1.7.0, Mac.
Why not update to the latest SDK?
I found the 16bit mod is not working properly on ASI294MC with the INDI1.7.0 Mac.
thank you Jasem for your quickly reply.
knro wrote: Yes it's a bug in the INDI Stable build and is already fixed in GIT. So it will be in the next release of INDI Stable, or you can compile from GIT.
When will you plan to release the new stable?
I want this feature because there is a Robofocus clone here. I can nearly make it work.
Only one issue is, there is a TTY timeout error after it moved (no issue of the moving). So the position is not refreshed. And the error always shows with "Bogus position:(00 00 00 00 00 00 00 00 00) - Bytes read: -1
I guess this device does not response any query command when it is moving. Maybe to increase the query period could help.
And also, I think the logic of querying position could be bug. It seems to jump into a dead loop after it failed a TTY connection.
It reads out -1 bytes every 1 sec (to the end of the world). This means some resources are not released and it does not do a clean reconnection. And there is no global timeout.
It should release the port and sleep for several seconds to reconnect to the port after a failure.
I'm sure it's a logic dead loop but not a hardware deadlock, because the device can still move after this 'timeout. Moving always works but position readout is dead.
In the 'Options' panel of INDI client, there is 'Polling' - Period (ms)
The default value is 1000.
On my understanding this means every 1000ms the driver does query the position of the focuser.
After I set this to 50000 and save the configuration, the value changed but from the log I can see the driver kept querying position every 1 sec.
Did I misunderstand or this is a bug?