Deneb-l replied to the topic 'INDI Driver for SVBONY cameras' in the forum. 3 days ago

Rebuilding the3rd party made the trick.
Anyway, I had previously installed the Ubuntu package (apt install indi-sv305), so, had to make my first 3rd party install.
For those who are in the same situation:

  • Remove previous package:
    sudo apt remove indi-sv305
  • Clean previous packages:
    sudo apt autoremove
  • Download or pull the code from: github.com/indilib/indi-3rdparty
  • Install packages requested for the build:
    sudo apt-get -y install libnova-dev libcfitsio-dev libusb-1.0-0-dev zlib1g-dev libgsl-dev build-essential cmake git libjpeg-dev libcurl4-gnutls-dev libtiff-dev libfftw3-dev libftdi-dev libgps-dev libraw-dev libdc1394-22-dev libgphoto2-dev libboost-dev libboost-regex-dev librtlsdr-dev liblimesuite-dev libftdi1-dev libavcodec-dev libavdevice-dev
  • in my case, I had to remove and reinstall libraw19 (???)
  • From the folder whre you pulled indi-3rdparty-master, follow the README instructions
    $ cmake -DCMAKE_INSTALL_PREFIX=/usr .
    $ make
    $ sudo make install
Now, the drivers does not crash anymore (haven't test yest with the Camera though)
Hope it helps

Read More...

Deneb-l replied to the topic 'INDI Driver for SVBONY cameras' in the forum. 3 days ago

Rebuilding the3rd party made the trick.
Anyway, I had previously installed the Ubuntu package (apt install indi-sv305), so, had to make my first 3rd party install.
For those who are in the same situation:

  • Remove previous package:
    sudo apt remove indi-sv305
  • Clean previous packages:
    sudo apt autoremove
  • Download or pull the code from: github.com/indilib/indi-3rdparty
  • Install packages requested for the build:
    sudo apt-get -y install libnova-dev libcfitsio-dev libusb-1.0-0-dev zlib1g-dev libgsl-dev build-essential cmake git libjpeg-dev libcurl4-gnutls-dev libtiff-dev libfftw3-dev libftdi-dev libgps-dev libraw-dev libdc1394-22-dev libgphoto2-dev libboost-dev libboost-regex-dev librtlsdr-dev liblimesuite-dev libftdi1-dev libavcodec-dev libavdevice-dev
  • in my case, I had to remove and reinstall libraw19 (???)
  • From the folder whre you pulled indi-3rdparty-master, follow the README instructions
    $ cmake -DCMAKE_INSTALL_PREFIX=/usr .
    $ make
    $ sudo make install
Now, the drivers does not crash anymore (haven't test yest with the Camera though)
Hope it helps

Read More...

Deneb-l replied to the topic 'INDI Driver for SVBONY cameras' in the forum. 4 days ago

Don't know if this is related to your change but now, the indi_sv305_ccd crashes with or without any camera plugged-in:
Driver indi_sv305_ccd: indi_sv305_ccd: symbol lookup error: indi_sv305_ccd: undefined symbol: _ZN4INDI3CCD15addFITSKeywordsEP8fitsfilePNS_7CCDChipE

Ubuntu 20.04.4 LTS
Linux XXXXXXXX 5.13.0-51-generic #58~20.04.1-Ubuntu SMP Tue Jun 14 11:29:12 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

KStars
Version 3.6.0 Beta

indiserver --version
[...]
INDI Library: 1.9.7
Code 1.9.7-tgz. Protocol 1.7.

Read More...

Ok, so far, this is what I have understood from the lx200 structure (there is actually 22 different classes to address):
Any lx200 component class heritates from LX200Generic which derives from LX200Telescope.
LX200Telescope derives from 3 classes:
             public INDI::Telescope, public INDI::GuiderInterface, public INDI::FocuserInterface
The comment in source code says that there is "One binary for all lx200 drivers but each binary is renamed to the device name"
I have not found how this actually works but as a matter of fact, haven't found a specific binary for each lx200 class (lx200gps, lx200autostar...)

I think I will stop here for my investigation with lx200 and follow the initial suggestion from James and knro to derives from FocuserInterface and FilterInterface (took me some time to understand that FocuserWheelInterface is names FilterInterface...)
Will keep posted if this can be, and how it can be done. 

Read More...

Wouhaou, yes, I haven't thought about the Interface. I will analyze the lx200 code, try to understand how they have dealt with that and key posted.
During the nigth, I also had a new idea. I reminded that the way I wrote the interface from the controller side is a fork of a classic Telnet server, which leads to the capacity to accept multiple incoming tcp "clients". I could have two separate INDI drivers which would, both, open a telnet socket and keep the socket purpose in the Microcontroller code (one for communicating FilterWheel events, the other one for focuser events) but I find this workaround pretty inelegant.
Thanks again James.
 

Read More...

Hello,
I have searched in many Forum topics and documentation but cannot seem to find an answer.
I started to create and build a custom focuser and FilterWheel combined device, driven by a single ESP32-32S NodeMCU controller.
My main objective is to create a super-lightweight configuration so I can keep my loved EQ5...
When I started my project, I would have swear I could find a documentation about having a single driver for different purposes (in my case, a focuser and a filterwheel).
My hardware is ready and sending "manual commands" to my controller works.
I am now starting to write the driver, the first step was to build the Focuser commands. I copied from an example and found how-to compile and test in Ekos. But I am stuck on this "multi-purpose" question. The more I read and understand the INDI driver library architecture, the more I have doubts about the possibility to build a single driver and provide both, a Focuser and a FilterWheel capability with a single communication channel and a single driver. Trying to derive a class from both device creates too many compilation dead end (class myCombinedDevice : public INDI::Focuser , INDI::FilterWheel)
Do you know if what I try to do is actually feasible? In that case, can you drive me to an example or documentation?
Many thanks.

Deneb-L.

Read More...