Not sure if the OS is the root cause of the problem ... can you switch on the trace for the filter wheel driver? Actually I forgot how to do that but afaik it is possible, there are some trace output statements in the code

Will try that tomorrow. Never heard of "trace" though. Only logging in ekos/kstars, so I will have to look it up first.

New day, new attempt:
Started up the indi server with the -l argument to log events locally on the Rock64.
The log file has only one line:

INFO 0.005758 sec : Session log file /home/rock64/.indi/logs/2017-11-12/indi_asi_wheel/indi_asi_wheel_20:04:07.log

I also noted now that the indi_asi_wheel process dies every time the client tries to connect to it. I've tried Ekos and PixInsight as clients. Same result for both.
But still no clue as to why this happens.

Should I try to build the indi_asi_wheel driver on my rock?
(I don't want to build the entire indilib software, just the wheel driver. If this would help.)

I think this is the filter driver log file:
/home/rock64/.indi/logs/2017-11-12/indi_asi_wheel/indi_asi_wheel_20:04:07.log
Does this file contain some entries / info?

Only the line starting with "INFO":
INFO 0.005758 sec : Session log file /home/rock64/.indi/logs/2017-11-12/indi_asi_wheel/indi_asi_wheel_20:04:07.log

Nothing else.

Build libindi from source and then compile the driver and see if that makes a difference. The drivers contains a blob that was compiled for arm64 but I wonder if this is what causing the issue somehow?

Thanks, will do. But not tonight, because tonight is going to be clear. I'll use my trusty raspberry pi until I got this solved.
Will report back here when I have more to share.

Hi guys..
I don't have the Rock64 board but I found this looking around in the forums..
forum.pine64.org/showthread.php?tid=5137&pid=32215
Br
/Markku

Thanks for the link.
The board itself doedn't crash. Rather the indi filter wheel driver does. My ASI camera and az eq6 mount function very well.

Latest update:

Clouds tonight, so I cleared the sd-card of my Rock64.
Installed Ubuntu (xenial) pre-release 0.5.15 (not the latest, because that came with some stability warnings).

Compiled indilib as per this thread:

indilib.org/forum/general/210-howto-buil...st-libindi-ekos.html

started indiserver on the rock64, and ekos/kstars on windows
Connection to the simulators (telescope and ccd) worked well, so the build seems good.

Then compiled and installed eqmod and asi-ccd and asi-filter wheel.
No errors during compilation/build.

Started indiserver with indi_asi_ccd and indi_asi_wheel. Started ok and both devices are visible on lsusb

Tried connecting to ekos/kstars on windows:

2017-11-16T20:20:21: [ERROR] Connect(): EFWOpen() = 4

2017-11-16T20:21:20: [ERROR] Error connecting to the CCD (5)

Here's the log, showing the same error code:



Any ideas?

Btw, running indiserver with the -l switch to create a log didn't result in any more details.

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.

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