Register    Login    Forum    Search    FAQ

Board index » Software » Linux




Post new topic Reply to topic  [ 10 posts ] 
Author Message
 Post Posted: Thu Nov 09, 2017 4:54 pm 
Offline

Joined: Thu Oct 26, 2017 10:12 pm
Posts: 10
Location: Sweden
Recently I've purchased a Rock64 single board computer with USB3 port to control my ASI 174MM-Cool and filter wheel.

https://www.pine64.org/?page_id=7147

I use Ubuntu Mate (latest community pre-release) as operating system and have the latest INDI software installed. The camera connects fine, but the filter wheel is completely unresponsive. I tried the following combinations, all without success:
1. ASI on USB3, efw on ASI hub
2. ASI on USB2, efw on ASI hub
3. ASI on USB3, efw on USB2
4. INDI CCD simulator, efw on USB2

5. ASI & efw on Raspberry Pi, running the same setup (this works flawlessly)

Both the camera and the filter wheel are visible in the usb list, and indiserver can see the filter wheel. It can send commands to the filter wheel, but these get queued. The connection indicator in Ekos/Kstars lights yellow, meaning that connection is in progress, but never finishes.

I've posted this problem on the INDI forum, but it seems that nobody else is using this hardware combination.

http://indilib.org/forum/focusers-filte ... ock64.html

The reason I test this combination is that the Rock64 has a fast USB3 port, so faster image download, and possibly less amp glow (?), than the Raspberry Pi.

Does anyone have experience with this computer? What can I do to test what's going on?
Or can I recompile the efw driver for this system?

Any suggestions to come to grips with this issue are appreciated.

TIA,

_________________
Wim

cameras: ASI 174MM-Cool, ASI 120MM (guiding)
telescope: Skywatcher 150PDS, SW ST80 (guiding)
mount: Skywatcher AZ EQ6 GT
software: INDI Ekos/Kstars, PixInsight


Top 
 Profile  
Reply with quote  
 Post Posted: Thu Nov 16, 2017 1:33 am 
Offline

Joined: Thu Feb 09, 2017 4:58 am
Posts: 81
Hi Wim,
Don't worry.
Although I don't have Rock64(RK3328), but we have another motherboard, which is running RK3399 and should be able to reproduce your problem. So I'll try to get back to you.
Thanks
chad

_________________
ZWO Driver Engineer
Location:lon=120.6 lat=31.3
SuZhou China


Top 
 Profile  
Reply with quote  
 Post Posted: Fri Nov 17, 2017 6:16 am 
Offline

Joined: Thu Feb 09, 2017 4:58 am
Posts: 81
Hi Wim,
I am very sorry for the trouble caused to you.
I have repeated the issue. But I didn't know anything about the INDI protocol before. So it might take some time to solve it. Hope it won't affect your using.
Thanks
chad

_________________
ZWO Driver Engineer
Location:lon=120.6 lat=31.3
SuZhou China


Top 
 Profile  
Reply with quote  
 Post Posted: Sat Nov 18, 2017 2:49 pm 
Offline

Joined: Thu Oct 26, 2017 10:12 pm
Posts: 10
Location: Sweden
Thanks for the reply. It isn't critical for me, as everything works fine on the raspberry pi that I normally use. But I would like to get it working on the Rock64 because of the faster usb3 port.
If it's of any help, I have posted my problem on the indi forum as well.

http://indilib.org/forum/focusers-filte ... ock64.html

This thread contains everything I have tried so far.
It seems that any messages to the efw get queued, and the driver process dies when trying to connect to the fw from a client. Building from source doesn't solve the problem.

_________________
Wim

cameras: ASI 174MM-Cool, ASI 120MM (guiding)
telescope: Skywatcher 150PDS, SW ST80 (guiding)
mount: Skywatcher AZ EQ6 GT
software: INDI Ekos/Kstars, PixInsight


Top 
 Profile  
Reply with quote  
 Post Posted: Mon Nov 20, 2017 2:11 am 
Offline

Joined: Thu Feb 09, 2017 4:58 am
Posts: 81
Hi Wim,
yes, I noticed that.
I also noticed the other one :
http://indilib.org/forum/focusers-filte ... wheel.html
You can have a try。
Thanks
chad

_________________
ZWO Driver Engineer
Location:lon=120.6 lat=31.3
SuZhou China


Top 
 Profile  
Reply with quote  
 Post Posted: Mon Nov 20, 2017 9:48 am 
Offline

Joined: Thu Oct 26, 2017 10:12 pm
Posts: 10
Location: Sweden
Thanks. I've seen that topic too. I'll try this tonight. So far, I've only used the configuration with indiserver on the Rock64 and ekos/kstars on windows.
I'll also try linux Jessie as operating system.

_________________
Wim

cameras: ASI 174MM-Cool, ASI 120MM (guiding)
telescope: Skywatcher 150PDS, SW ST80 (guiding)
mount: Skywatcher AZ EQ6 GT
software: INDI Ekos/Kstars, PixInsight


Top 
 Profile  
Reply with quote  
 Post Posted: Mon Nov 20, 2017 11:07 pm 
Offline

Joined: Thu Oct 26, 2017 10:12 pm
Posts: 10
Location: Sweden
Tonight I tested from a fresh Ubuntu setup:

Rock64 with xenial-mate-rock64-0.5.15-136-arm64 image
installed INDI full and Kstars bleeding according to instructions on indilib.org
installed python & tools
installed indi web manager

Connected efw mini to ASI 174MM-Cool usb hub
Connected camera to rock64 usb3 port

Tested with everything running on rock64, even Ekos/Kstars.
Tested indi-web local and remote (localhost:8624)
indi_asi_wheel crashes as soon as I try to connect to it.

Managed to get a crash report from ubuntu, which I attach here (zipped)

Incidentally: using the command lsusb -t shows the camera connected as usb 3 (speed 5000M), but the wheel as usb1 (speed 12M). Is this relevant?

I also tried installing Debian (Jessie), but got a bunch of errors when trying to install the indilib dependencies, so I gave up on this.


Attachments:
File comment: crash report indi_asi_wheel
_usr_bin_indi_asi_wheel.0.crash.zip [122.14 KiB]
Downloaded 1 time

_________________
Wim

cameras: ASI 174MM-Cool, ASI 120MM (guiding)
telescope: Skywatcher 150PDS, SW ST80 (guiding)
mount: Skywatcher AZ EQ6 GT
software: INDI Ekos/Kstars, PixInsight
Top 
 Profile  
Reply with quote  
 Post Posted: Tue Nov 21, 2017 5:44 am 
Offline

Joined: Thu Feb 09, 2017 4:58 am
Posts: 81
for USB3.0 and USB1.0, I don't think they are relevant.
As you know, EFW has a very small amount of data, So USB1.0 is enough. When connecting, device speed only meet the requirements of USB1.0, So it will be identified as USB1.0。
Beside,I checked your log and the crash was caused by the indi_asi_wheel drive. I have found the place where the crash occurred in the source Code, but how it happened and how to solve it is not clear to me.
Thanks
chad

_________________
ZWO Driver Engineer
Location:lon=120.6 lat=31.3
SuZhou China


Top 
 Profile  
Reply with quote  
 Post Posted: Tue Nov 21, 2017 6:25 am 
Offline

Joined: Thu Oct 26, 2017 10:12 pm
Posts: 10
Location: Sweden
Yes, I thought so too, regarding usb1. But I just wanted that confirmed.
As for the driver crash, do you think that Jasem Mutlaq or someone from the indi group might be able to help with that? Or is the driver developed by ZWO?

_________________
Wim

cameras: ASI 174MM-Cool, ASI 120MM (guiding)
telescope: Skywatcher 150PDS, SW ST80 (guiding)
mount: Skywatcher AZ EQ6 GT
software: INDI Ekos/Kstars, PixInsight


Top 
 Profile  
Reply with quote  
 Post Posted: Tue Nov 21, 2017 7:16 am 
Offline

Joined: Thu Feb 09, 2017 4:58 am
Posts: 81
I am not sure。I think we need more information。Now we don't know the root cause, even if he helps us, they don't know how to do it.
Thanks
chad

_________________
ZWO Driver Engineer
Location:lon=120.6 lat=31.3
SuZhou China


Top 
 Profile  
Reply with quote  
Display posts from previous:  Sort by  
 
Post new topic Reply to topic  [ 10 posts ] 

Board index » Software » Linux


Who is online

Users browsing this forum: No registered users and 1 guest

 
 

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to: