Agustin replied to the topic 'NanoPi M4' in the forum. 2 years ago

I saw your x with Zwo driver but I managed to configure indi-full, kstars-bleeding within NanoPi M4 running Lubuntu 32 bits and upgrading to Ubuntu 18.04.1 LTS. I can confirm that I'm able to use ASI-071C with a tele lens and a Nexstar mount as test gears with indiserver -v indi_celestron_gps indi_asi_ccd, and running kstars from pc using wifi. I tried also to install astrometry.net but got an error with guvcview "not going to be installed"..
I solved by uninstalling indi-full, and force the installations of libgslcblas0, libgsl23 and libguvcview-2.0-2. Later, guvcview was installed without problem and also astrometry.net installed without error. It is great to use USB3.0 with Zwo ccd and even using wifi, the downloading time is quite impresive.

Have fun,
Agustin

Read More...

Perhaps has been solved elsewhere, but I didn't find it. I have a SBIG STL11000 with an attached filterwheel FW8-STL. I did a test profile and the camera and filterwheel works, but presents only 5 filter positions. I tried to configure later the FW simulator to see if that open 8 room spaces on the configuration, but inside the camera windows, the filterwheel label presents still only 5 positions.
Anything that can be reconfigured?
Thanks,

Read More...

Agustin replied to the topic 'Starlight CCD Crash & AO Crash' in the forum. 3 years ago

HI, I also have a problem with indi_sx_ccd for my lodestar guider since this weekend (it was working ok previously), and there has been an indi update (don't know if included it). I see with dmesg that lodestar usb driver connect correctly, but kstars through this pop window:
"KStars detected INDI driver indi_sx_ccd crashed. Please check INDI server log in the Device Manager"
I did and this is the log:

2018-02-26T21:12:30: startup: /usr/bin/indiserver -v -p 7624 -m 100 -f /tmp/indififoc44397b2
2018-02-26T21:12:30: listening to port 7624 on fd 3
FIFO: start indi_sx_ccd
FIFO: Starting driver indi_sx_ccd
2018-02-26T21:12:30: Driver indi_sx_ccd: pid=6085 rfd=4 wfd=7 efd=8
2018-02-26T21:12:30: Client 5: new arrival from 127.0.0.1:42284 - welcome!
2018-02-26T21:12:30: Driver indi_sx_ccd: indi_sx_ccd: symbol lookup error: indi_sx_ccd: undefined symbol: _ZThn4360_N4INDI3CCD13GuideCompleteE12INDI_EQ_AXIS
2018-02-26T21:12:30: Driver indi_sx_ccd: stderr EOF
Child process 6085 died
2018-02-26T21:12:30: Driver indi_sx_ccd: restart #1
2018-02-26T21:12:30: Driver indi_sx_ccd: pid=6087 rfd=4 wfd=8 efd=9
Child process 6087 died
2018-02-26T21:12:30: Driver indi_sx_ccd: indi_sx_ccd: symbol lookup error: indi_sx_ccd: undefined symbol: _ZThn4360_N4INDI3CCD13GuideCompleteE12INDI_EQ_AXIS
2018-02-26T21:12:30: Driver indi_sx_ccd: stdin EOF
2018-02-26T21:12:30: Driver indi_sx_ccd: restart #2
2018-02-26T21:12:30: Driver indi_sx_ccd: pid=6088 rfd=4 wfd=8 efd=9
2018-02-26T21:12:30: Driver indi_sx_ccd: indi_sx_ccd: symbol lookup error: indi_sx_ccd: undefined symbol: _ZThn4360_N4INDI3CCD13GuideCompleteE12INDI_EQ_AXIS
2018-02-26T21:12:30: Driver indi_sx_ccd: stderr EOF
Child process 6088 died
2018-02-26T21:12:30: Driver indi_sx_ccd: restart #3
2018-02-26T21:12:30: Driver indi_sx_ccd: pid=6089 rfd=4 wfd=8 efd=9
2018-02-26T21:12:30: Driver indi_sx_ccd: indi_sx_ccd: symbol lookup error: indi_sx_ccd: undefined symbol: _ZThn4360_N4INDI3CCD13GuideCompleteE12INDI_EQ_AXIS
2018-02-26T21:12:30: Driver indi_sx_ccd: stderr EOF
Child process 6089 died
2018-02-26T21:12:30: Driver indi_sx_ccd: restart #4
2018-02-26T21:12:30: Driver indi_sx_ccd: pid=6090 rfd=4 wfd=8 efd=9
2018-02-26T21:12:30: Driver indi_sx_ccd: indi_sx_ccd: symbol lookup error: indi_sx_ccd: undefined symbol: _ZThn4360_N4INDI3CCD13GuideCompleteE12INDI_EQ_AXIS
2018-02-26T21:12:30: Driver indi_sx_ccd: stderr EOF
2018-02-26T21:12:30: Driver indi_sx_ccd: restart #5
2018-02-26T21:12:30: Driver indi_sx_ccd: pid=6091 rfd=4 wfd=8 efd=9
Child process 6090 died
2018-02-26T21:12:30: Driver indi_sx_ccd: indi_sx_ccd: symbol lookup error: indi_sx_ccd: undefined symbol: _ZThn4360_N4INDI3CCD13GuideCompleteE12INDI_EQ_AXIS
2018-02-26T21:12:30: Driver indi_sx_ccd: stderr EOF
2018-02-26T21:12:30: Driver indi_sx_ccd: restart #6
2018-02-26T21:12:30: Driver indi_sx_ccd: pid=6092 rfd=4 wfd=8 efd=9
Child process 6091 died
2018-02-26T21:12:30: Driver indi_sx_ccd: indi_sx_ccd: symbol lookup error: indi_sx_ccd: undefined symbol: _ZThn4360_N4INDI3CCD13GuideCompleteE12INDI_EQ_AXIS
2018-02-26T21:12:30: Driver indi_sx_ccd: stderr EOF
Child process 6092 died
2018-02-26T21:12:30: Driver indi_sx_ccd: restart #7
2018-02-26T21:12:30: Driver indi_sx_ccd: pid=6093 rfd=4 wfd=8 efd=9
2018-02-26T21:12:30: Driver indi_sx_ccd: indi_sx_ccd: symbol lookup error: indi_sx_ccd: undefined symbol: _ZThn4360_N4INDI3CCD13GuideCompleteE12INDI_EQ_AXIS
2018-02-26T21:12:30: Driver indi_sx_ccd: stderr EOF
Child process 6093 died
2018-02-26T21:12:30: Driver indi_sx_ccd: restart #8
2018-02-26T21:12:30: Driver indi_sx_ccd: pid=6094 rfd=4 wfd=8 efd=9
2018-02-26T21:12:30: Driver indi_sx_ccd: indi_sx_ccd: symbol lookup error: indi_sx_ccd: undefined symbol: _ZThn4360_N4INDI3CCD13GuideCompleteE12INDI_EQ_AXIS
Child process 6094 died
2018-02-26T21:12:30: Driver indi_sx_ccd: stderr EOF
2018-02-26T21:12:30: Driver indi_sx_ccd: restart #9
2018-02-26T21:12:30: Driver indi_sx_ccd: pid=6095 rfd=4 wfd=8 efd=9
2018-02-26T21:12:30: Driver indi_sx_ccd: indi_sx_ccd: symbol lookup error: indi_sx_ccd: undefined symbol: _ZThn4360_N4INDI3CCD13GuideCompleteE12INDI_EQ_AXIS
2018-02-26T21:12:30: Driver indi_sx_ccd: stderr EOF
Child process 6095 died
2018-02-26T21:12:30: Driver indi_sx_ccd: restart #10
2018-02-26T21:12:30: Driver indi_sx_ccd: pid=6096 rfd=4 wfd=8 efd=9
2018-02-26T21:12:30: Driver indi_sx_ccd: indi_sx_ccd: symbol lookup error: indi_sx_ccd: undefined symbol: _ZThn4360_N4INDI3CCD13GuideCompleteE12INDI_EQ_AXIS
2018-02-26T21:12:30: Driver indi_sx_ccd: stderr EOF
2018-02-26T21:12:30: Driver indi_sx_ccd: Terminated after #10 restarts.
Child process 6096 died

Any help?
Thanks

Read More...

It was in front of my nose. Sorry! Meanwhile, I solved the error by creating another clean configuration only with telescope and camera, and running meanwhile TSX as sudo. Since then, I don't have the error, nor the log to submits :-)
BTW, I didn't find the way to auto enable TSX TCP server socket. Anybody knows?
Thanks!

Read More...

I don't know how to get INDI logs (I tried to find how, but only found developers hints for debug mode in device code to generate a log in /tmp, but not how to get device protocols logs from a user pov).
I tried yesterday to put TSX TCP server script api logs and got this errors from their side.
Please, let me know how to generate debug logs in a Ekos device.
Thanks

Read More...

Hi, I am trying to control a Paramount Mount with TSX in ubuntu 16.04, with Ekos using TCP API of TSX. It does connect and read coordinates, but any slew fail. TSX stand-alone is capable, of course of slewing. Before connecting INDI, I prepare TSX with Find Home, that works, and leave the mount in tracking.
Any idea, how to debug the situacion? After any try to slew, or start tracking, or Park/Unpark.. etc, from INDI, the interface of TSX shows "Connection problems" and some time even bring COM popups. Later than this, I have to reboot the mountand TSX.
Thanks

Read More...

Thank you for the excellent work in INDI. I am using it with ZWO ASI017C and EQ6 without problem but I have an old Starlight Xpress MX7C that I could use for guiding. I've tried the SX driver without success. MX7C used the USB1.1 interface with this lsusb result:
Bus 002 Device 010: ID 0547:2131 Anchor Chips, Inc. AN2131 EZUSB Microcontroller
and dmesg:
[428913.339419] usb 2-1.4: new full-speed USB device number 10 using ehci-pci
[428913.432242] usb 2-1.4: New USB device found, idVendor=0547, idProduct=2131
[428913.432252] usb 2-1.4: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Is there any possibility to use it with IND anyhow? Thanks in advace.

Read More...