×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

Problems connecting to ZWO efw (Rock64)

  • Posts: 333
  • Thank you received: 24
This error (Error connecting to the CCD (5)) I used to have to resolve not he RPI3/Ubuntu-mate, by:

1. Running INDISERVER via command line and sudo
2. Connect Ekos to the remote server 127.0.0.1 (localhost)

The CCD (5) error was caused by my ASI224MC-C.

The Connect(): EFWOpen() = 4, was also resolved with this combination of sudo and 127.0.0.1.

In my case both ASI224 and EFW were connected to the ASI1600 USB hub.

I was running everything on RPI3, and using VNC to connect to the RPI3.

I know we covered some of this before, and just mention it in case it helps.
6 years 4 months ago #20950

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

  • Posts: 126
  • Thank you received: 16
Thanks, Maudy.

Running indiserver as root got me back to the original issue:
indiserver connects to the ASI174 camera, but the driver process for the wheel dies when trying to connect to it.

Here's a quick screen dump from the command console

Child process 2253 died
2017-11-16T22:12:10: Driver indi_asi_wheel: restart #1
2017-11-16T22:12:10: Driver indi_asi_wheel: pid=2398 rfd=4 wfd=10 efd=11
2017-11-16T22:12:16: Driver indi_asi_ccd: recorder: setpixelformat 1195528775
2017-11-16T22:12:23: Driver indi_asi_wheel: stderr EOF
Child process 2398 died
2017-11-16T22:12:23: Driver indi_asi_wheel: restart #2
2017-11-16T22:12:23: Driver indi_asi_wheel: pid=2470 rfd=4 wfd=10 efd=11
Child process 2470 died
6 years 4 months ago #20951

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

  • Posts: 126
  • Thank you received: 16
I opened a thread on the ZWO user forum regarding this.

zwoug.org/viewtopic.php?f=17&t=7552

Tonight I started from a fresh ubuntu install (xenial-mate). Installed INDI full & Kstars from the PPA, and tried running everything locally (even using Remote with server localhost:8624). Still no luck. But I did get a ubuntu crash report for the wheel driver.
I'm totally out of ideas, so if I don't get any more input here or on the ZWO forum, I'm writing this off and will wait for Raspberry Pi to come out with a usb3 device.
Btw, the issue is with the zwo mini filter wheel. The ASI174MM works with the Rock64. So, if anyone wants to use the Rock with an ASI osc, that should work just fine.

File Attachment:

File Name: _usr_bin_i...rash.zip
File Size:122 KB
6 years 4 months ago #21133
Attachments:

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

  • Posts: 126
  • Thank you received: 16
Tiny bit of progress. ZWO have identified the problem to be in the driver. From the crash report that I submitted, they could figure out where in the code the crash occurs. They just don't know yet how to fix it.
6 years 4 months ago #21144

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

  • Posts: 41
  • Thank you received: 7
The dump contains a stacktrace:

Stacktrace:
#0 0x00000055645b2528 in CEFW::clearError() ()
No symbol table info available.
#1 0x00000055645b2628 in CEFW::getSlotNum(int*) ()
No symbol table info available.
#2 0x00000055645b1550 in ASIWHEEL::Connect() ()
No symbol table info available.
#3 0x0000007faf2772ac in INDI::DefaultDevice::ISNewSwitch(char const*, char const*, ISState*, char**, int) () from /usr/lib/aarch64-linux-gnu/libindidriver.so.1
No symbol table info available.
#4 0x0000007faf2a91e8 in INDI::FilterWheel::ISNewSwitch(char const*, char const*, ISState*, char**, int) () from /usr/lib/aarch64-linux-gnu/libindidriver.so.1
No symbol table info available.
#5 0x00000055645b0990 in ISNewSwitch ()
No symbol table info available.
#6 0x0000007faf26a9f8 in dispatch () from /usr/lib/aarch64-linux-gnu/libindidriver.so.1
No symbol table info available.
#7 0x0000007faf26afe8 in clientMsgCB () from /usr/lib/aarch64-linux-gnu/libindidriver.so.1

So the problem is within the ZWO SDK which is called by the INDI driver. I think this can only be fixed by the zwo folks.
6 years 4 months ago #21231

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

  • Posts: 126
  • Thank you received: 16
I got the same info (just not as detailed as your reply) from the ZWO driver developer. They see that the cause is the driver, but they don't have a solution yet. I just hope they're working on one. From the reactions I have received, there are enough people interested to see it work. The Rock64 sbc is a viable alternative to the RPi, because of the usb3 port.
6 years 4 months ago #21236

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

  • Posts: 7
  • Thank you received: 3
It's bug of our EFW SDK, I've rebuilt one that can run on aarch64 platform:
astronomy-imaging-camera.com/software/EF...ac_SDK_V0.3.1205.tar
The following user(s) said Thank You: Jasem Mutlaq, Wim van Berlo
6 years 3 months ago #21464

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

Thanks, I've updated INDI ASI driver as well with the arm64 fix.
The following user(s) said Thank You: Wim van Berlo
6 years 3 months ago #21465

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

  • Posts: 126
  • Thank you received: 16
Thanks for posting here. I already saw the reply on the zwi user forum. Will test as soon as possible
6 years 3 months ago #21466

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

  • Posts: 126
  • Thank you received: 16
Great! Then I shouldn't need to recompile the driver separately. I guess that the fix is part of the standard package now.
6 years 3 months ago #21467

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

  • Posts: 281
  • Thank you received: 29
Dear Jasem,

I have been updating whatever I could think about (apt-get update, ...upgrade, updating ppa, indi-full). When updating the indi-asi driver, this is what happens

astroberry@astroberry:~$ sudo apt-get install indi-asi
[sudo] password for astroberry:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
asi-common
The following NEW packages will be installed:
asi-common
The following packages will be upgraded:
indi-asi
1 upgraded, 1 newly installed, 0 to remove and 400 not upgraded.
Need to get 241 kB of archives.
After this operation, 188 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 ppa.launchpad.net/mutlaqja/ppa/ubuntu xenial/main armhf asi-common all 0.8.0+r3461~201710091055~ubuntu16.04.1 [2,186 B]
Get:2 ppa.launchpad.net/mutlaqja/ppa/ubuntu xenial/main armhf indi-asi armhf 0.7~201712050918~ubuntu16.04.1 [239 kB]
Fetched 241 kB in 2s (93.8 kB/s)
Selecting previously unselected package asi-common.
(Reading database ... 206308 files and directories currently installed.)
Preparing to unpack .../asi-common_0.8.0+r3461~201710091055~ubuntu16.04.1_all.deb ...
Unpacking asi-common (0.8.0+r3461~201710091055~ubuntu16.04.1) ...
dpkg: error processing archive /var/cache/apt/archives/asi-common_0.8.0+r3461~201710091055~ubuntu16.04.1_all.deb (--unpack):
trying to overwrite '/lib/udev/rules.d/99-asi.rules', which is also in package indi-asi 0.5+r3077~201705151253~ubuntu16.04.1
Preparing to unpack .../indi-asi_0.7~201712050918~ubuntu16.04.1_armhf.deb ...
Unpacking indi-asi (0.7~201712050918~ubuntu16.04.1) over (0.5+r3077~201705151253~ubuntu16.04.1) ...
Errors were encountered while processing:
/var/cache/apt/archives/asi-common_0.8.0+r3461~201710091055~ubuntu16.04.1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
astroberry@astroberry:~$ sudo apt-get install indi-asi
Reading package lists... Done
Building dependency tree
Reading state information... Done
indi-asi is already the newest version (0.7~201712050918~ubuntu16.04.1).
You might want to run 'apt-get -f install' to correct these:
The following packages have unmet dependencies:
indi-asi : Depends: asi-common but it is not going to be installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).

Should I run apt-get -f install?

Many thanks,

Helge
6 years 3 months ago #21475

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

Yes run sudo apt-get -f install
6 years 3 months ago #21476

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

Time to create page: 0.953 seconds