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...

Read More...

I tried changing the auto-exposure (enabled by default ?) in the controls tab.
 


I also played with the resolution option, but I guess weird behaviour ranging from, getting an image after a very long time, to driver disconnection + getting the client interface reseted for the camera.
Nothing more than the previous logs are shown in those cases unfortunately... It is really a shame that the driver is that bad with regard to the consistent behaviour I have with ZWO ASi cameras.

Read More...

Dear all,

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):
FYMqP8V 



Here are some logs from the driver logs:and from the driver verbose output:

pastebin.com/mKpb71j5

If someone can help, I have no idea where to start, I use plenty of different driver, but Altair is really the one always causing me troubles I haven't seen with any other driver.

Read More...

dolguldur replied to the topic 'Altair 26C' in the forum. 4 weeks ago

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.

Read More...

dolguldur replied to the topic 'Altair Hypercam 183M crash' in the forum. 4 weeks ago

Thank you for the feedback. It is an option indeed. I power the camera with a powerful source (upbv2 from pegasus astro), but I might have a weak cable, will do some tests later one. For now, it seems more like a software issue.

Read More...

dolguldur replied to the topic 'Altair Hypercam 183M crash' in the forum. 4 weeks ago

Did you eventually managed to fix that issue ?
It is quite annoying, as I cannot reliably get this camera to work, and for now I didn't managed to find out what parameter was influencing this behaviour....
I get:
[WARNING] Failed to snap exposure. Error: Unexpected failure. Switching to regular exposure...

Read More...

dolguldur replied to the topic 'Problem importing PyIndi' in the forum. 4 months ago

Even if the swig build itself is not failing, I guess we ended up more or less back to the same state: github.com/indilib/pyindi-client/issues/2
Anyone with good knowledge about swig able to help ?

If I have time this week, I'll check what I can do with pybind11, see if the methods/attributes can be retrieved from python, or if it is not swig related.

Read More...

dolguldur replied to the topic 'Problem importing PyIndi' in the forum. 10 months ago

Ok thank you for the feedback, and I apologize for mentionning the wrong problem. I was simply not able to determine what was the issue by myself.
I just realized that the macro I suspected to be the initial source of the problem was more or less an equivalent of Q_DECLARE_PRIVATE one can also find in QT source code that is apparently meant to bypass some compiler limitation with RTTI and dynamic_cast.

In my humble opinion it would be a good idea to have pyindi client tested at least as part of indi releases, as I think this project really makes indi extremely powerful, and some opensource projects with growing popularity are relying on it (hinking here at the fantastic work done by Gulinux). However it is definitely not my call, as I am not doing any significant maintenance of either indi or pyindi-client.

Thank you pawel-soja for your work on the project !

Read More...

dolguldur replied to the topic 'Re:Problem importing PyIndi' in the forum. 10 months ago
dolguldur replied to the topic 'Problem importing PyIndi' in the forum. 12 months ago

There seems to be other things that are not right with 1.8.8 and 1.8.9:
Here is what I get trying to install pyindi with version older than 0.2.6 ie 0.2.5 and earlier :

pip install pyindi-client==0.2.5; python -c "import PyIndi"
:

/usr/include/libindi/indiproperty.h:42: Error: Syntax error in input(3).
error: command 'swig' failed with exit status 1


At this line, there is a macro:
class Property
{
    DECLARE_PRIVATE(Property)
public:
    Property();

The macro is defined in indiutility.h
#define DECLARE_PRIVATE(Class) \
    inline Class##Private* d_func() { return reinterpret_cast<Class##Private *>(getPtrHelper(d_ptr)); } \
    inline const Class##Private* d_func() const { return reinterpret_cast<const Class##Private *>(getPtrHelper(d_ptr)); } \
    friend class Class##Private;

I think this is breaking swig

Read More...

dolguldur replied to the topic 'Problem importing PyIndi' in the forum. 12 months ago

I tried removing all the unstable stuff comming from the ppa's And then installed ubuntu 20.04 stock indi-dev package
Know I am left with this:

ldd /home/user/venv/lib/python3.7/site-packages/_PyIndi.cpython-37m-x86_64-linux-gnu.so
linux-vdso.so.1 (0x00007ffda918b000)
libz.so.1 => /opt/anaconda3/lib/libz.so.1 (0x00007fbfb55b9000)
libcfitsio.so.8 => /usr/lib/x86_64-linux-gnu/libcfitsio.so.8 (0x00007fbfb5285000)
libnova-0.16.so.0 => /usr/lib/x86_64-linux-gnu/libnova-0.16.so.0 (0x00007fbfb4f06000)
libstdc++.so.6 => /opt/anaconda3/lib/libstdc++.so.6 (0x00007fbfb4dc5000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fbfb4c76000)
libgcc_s.so.1 => /opt/anaconda3/lib/libgcc_s.so.1 (0x00007fbfb4c62000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fbfb4c3d000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fbfb4a4b000)
libcurl-gnutls.so.4 => /usr/lib/x86_64-linux-gnu/libcurl-gnutls.so.4 (0x00007fbfb49bc000)
libbz2.so.1.0 => /opt/anaconda3/lib/libbz2.so.1.0 (0x00007fbfb47aa000)
/lib64/ld-linux-x86-64.so.2 (0x00007fbfb56a2000)
libnghttp2.so.14 => /usr/lib/x86_64-linux-gnu/libnghttp2.so.14 (0x00007fbfb4781000)
libidn2.so.0 => /usr/lib/x86_64-linux-gnu/libidn2.so.0 (0x00007fbfb475e000)
librtmp.so.1 => /usr/lib/x86_64-linux-gnu/librtmp.so.1 (0x00007fbfb473e000)
libssh.so.4 => /usr/lib/x86_64-linux-gnu/libssh.so.4 (0x00007fbfb46d0000)
libpsl.so.5 => /usr/lib/x86_64-linux-gnu/libpsl.so.5 (0x00007fbfb46bd000)
libnettle.so.7 => /usr/lib/x86_64-linux-gnu/libnettle.so.7 (0x00007fbfb4683000)
libgnutls.so.30 => /usr/lib/x86_64-linux-gnu/libgnutls.so.30 (0x00007fbfb44ad000)
libgssapi_krb5.so.2 => /opt/anaconda3/lib/libgssapi_krb5.so.2 (0x00007fbfb445c000)
libldap_r-2.4.so.2 => /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 (0x00007fbfb4406000)
liblber-2.4.so.2 => /usr/lib/x86_64-linux-gnu/liblber-2.4.so.2 (0x00007fbfb43f5000)
libbrotlidec.so.1 => /usr/lib/x86_64-linux-gnu/libbrotlidec.so.1 (0x00007fbfb43e7000)
libunistring.so.2 => /usr/lib/x86_64-linux-gnu/libunistring.so.2 (0x00007fbfb4265000)
libhogweed.so.5 => /usr/lib/x86_64-linux-gnu/libhogweed.so.5 (0x00007fbfb422b000)
libgmp.so.10 => /opt/anaconda3/lib/libgmp.so.10 (0x00007fbfb3f97000)
libcrypto.so.1.1 => /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 (0x00007fbfb3cc1000)
libp11-kit.so.0 => /usr/lib/x86_64-linux-gnu/libp11-kit.so.0 (0x00007fbfb3b8b000)
libtasn1.so.6 => /usr/lib/x86_64-linux-gnu/libtasn1.so.6 (0x00007fbfb3b75000)
libkrb5.so.3 => /opt/anaconda3/lib/./libkrb5.so.3 (0x00007fbfb3a99000)
libk5crypto.so.3 => /opt/anaconda3/lib/./libk5crypto.so.3 (0x00007fbfb3a78000)
libcom_err.so.3 => /opt/anaconda3/lib/./libcom_err.so.3 (0x00007fbfb3a72000)
libkrb5support.so.0 => /opt/anaconda3/lib/./libkrb5support.so.0 (0x00007fbfb3a63000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fbfb3a5d000)
libcrypto.so.1.0.0 => /opt/anaconda3/lib/./libcrypto.so.1.0.0 (0x00007fbfb3814000)
libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x00007fbfb37f8000)
libsasl2.so.2 => /usr/lib/x86_64-linux-gnu/libsasl2.so.2 (0x00007fbfb37d9000)
libgssapi.so.3 => /usr/lib/x86_64-linux-gnu/libgssapi.so.3 (0x00007fbfb3794000)
libbrotlicommon.so.1 => /usr/lib/x86_64-linux-gnu/libbrotlicommon.so.1 (0x00007fbfb3771000)
libffi.so.7 => /usr/lib/x86_64-linux-gnu/libffi.so.7 (0x00007fbfb3765000)
libheimntlm.so.0 => /usr/lib/x86_64-linux-gnu/libheimntlm.so.0 (0x00007fbfb3759000)
libkrb5.so.26 => /usr/lib/x86_64-linux-gnu/libkrb5.so.26 (0x00007fbfb36c4000)
libasn1.so.8 => /usr/lib/x86_64-linux-gnu/libasn1.so.8 (0x00007fbfb361d000)
libcom_err.so.2 => /lib/x86_64-linux-gnu/libcom_err.so.2 (0x00007fbfb3616000)
libhcrypto.so.4 => /usr/lib/x86_64-linux-gnu/libhcrypto.so.4 (0x00007fbfb35de000)
libroken.so.18 => /usr/lib/x86_64-linux-gnu/libroken.so.18 (0x00007fbfb35c5000)
libwind.so.0 => /usr/lib/x86_64-linux-gnu/libwind.so.0 (0x00007fbfb359b000)
libheimbase.so.1 => /usr/lib/x86_64-linux-gnu/libheimbase.so.1 (0x00007fbfb3587000)
libhx509.so.5 => /usr/lib/x86_64-linux-gnu/libhx509.so.5 (0x00007fbfb3539000)
libsqlite3.so.0 => /opt/anaconda3/lib/libsqlite3.so.0 (0x00007fbfb3414000)
libcrypt.so.1 => /lib/x86_64-linux-gnu/libcrypt.so.1 (0x00007fbfb33d9000)

(no trace of libindi whatsoever)

nm -D /home/gnthibault/projects/RemoteObservatory/venv/lib/python3.7/site-packages/_PyIndi.cpython-37m-x86_64-linux-gnu.so | grep IUSaveConfigText
U IUSaveConfigText

The sybol seems undefined here. But you can find it in
nm -D /usr/lib/x86_64-linux-gnu/libindidriver.so | grep IUSaveConfigText
0000000000035dd3 T IUSaveConfigText

But not much in the static client library:
nm /usr/lib/x86_64-linux-gnu/libindiclient.a | grep Save
0000000000002821 T IUSaveText
U IUSaveText
U IUSaveText

Read More...