×

INDI Library v1.9.2 Released (14 Sep 2021)

Bimonthly Stable INDI Library release introduces new drivers and fixes for existing ones.

Driver crashes when connecting HEQ5 and indi_eqmod_telescope

  • Posts: 3
  • Thank you received: 0
Hi,
I searched a lot but could not find the answer about this issue:

I have a HEQ5
A direct cable 
www.pierro-astro.com/materiel-astronomiq...il#tab-product-desc3

and latest astroberry.

The cable is recognized:
 $ lsusb 
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
[b]Bus 001 Device 005: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC[/b]
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

but running 
indiserver -v indi_eqmod_telescope
or starting from ekos, gives me this error
2021-08-24T14:36:18: startup: indiserver -v indi_eqmod_telescope 
2021-08-24T14:36:18: Driver indi_eqmod_telescope: pid=1911 rfd=3 wfd=6 efd=7
2021-08-24T14:36:18: listening to port 7624 on fd 4
2021-08-24T14:36:18: Driver indi_eqmod_telescope: indi_eqmod_telescope: symbol lookup error: /usr/lib/arm-linux-gnueabihf/libindidriver.so.1: undefined symbol: ISSnoopDevice
2021-08-24T14:36:18: Driver indi_eqmod_telescope: stderr EOF
2021-08-24T14:36:18: Driver indi_eqmod_telescope: restart #1
Child process 1911 died
 

I am not sure what this means and how to solve it, any hints?
1 month 3 weeks ago #74807

Please Log in or Create an account to join the conversation.

  • Posts: 382
  • Thank you received: 140
Your EQMod driver has been built against newer base INDI library than what you have installed in the system. So either you can try to update them both or build from source yourself so that they match.
Remote observatory running Ubuntu 21.04 x64 with ScopeDome 2M, Skywatcher EQ8, TS 8" RC, Atik 383L+, ASI178MC, ASI120MM-S, SX Lodestar X2, SX USB wheel with OAG, ZWO EAF, Gemini SnapCap, USB_DewPoint, KomaHub
The following user(s) said Thank You: LordPader
1 month 3 weeks ago #74814

Please Log in or Create an account to join the conversation.

  • Posts: 3
  • Thank you received: 0
Thanks,
looks like an upgrade wasn't upgrading everything as it should. A newly full upgrade solved the problem.
1 month 2 weeks ago #74841

Please Log in or Create an account to join the conversation.

Moderators: Radek Kaczorek
Time to create page: 0.553 seconds