×

INDI Library v2.0.0 Released (01 Feb 2023)

Bi-monthly release with major changes to INDI properties and client API in addition to new drivers and improvements.

Problems connecting to ZWO efw (Rock64)

  • Posts: 125
  • Thank you received: 15

Thanks for the suggestion. I tried that (but without the telescope driver). I have the server on a different machine from the client, so my ip address isn't the localhost (127.0.0.1) Running the server as superuser makes no difference.
Wim

Skywatcher 190MN + 150PDS, AZ-EQ6 GT + EQ3-2 Goto, ZWO ASI294MM Pro + ZWO ASI174MM-Cool, Raspberry Pi4 with Astroberry + Rock64 x 2 with INDI & PHD2

www.astrobin.com/users/wimvb/
5 years 3 months ago #20688

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

  • Posts: 125
  • Thank you received: 15
Started the indiserver with the -vv switch, and got this back (attached screen grab from the terminal window)

File Attachment:

File Name: asi_efw_test.zip
File Size:5 KB


It seems to me that the server sends messages to the driver, but after a while they end up being queued. Does that mean that the driver is unresponsive? (time stamp 22:59:20)
The start up procedure was as follows:
- Kill any ongoing indi processes (as per Maudy's response)
- Start indiserver on Rock64 with switch -vv, drivers: CCD Simulator and ASI EFW
- Start Kstars on windows
- Start Ekos, connecting to server on Rock64
Wim

Skywatcher 190MN + 150PDS, AZ-EQ6 GT + EQ3-2 Goto, ZWO ASI294MM Pro + ZWO ASI174MM-Cool, Raspberry Pi4 with Astroberry + Rock64 x 2 with INDI & PHD2

www.astrobin.com/users/wimvb/
5 years 3 months ago #20689
Attachments:

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

  • Posts: 41
  • Thank you received: 7
The asi wheel driver crashed at 22;59;26
2017-11-04T22:59:26: Driver indi_asi_wheel: restart #1
after it has connected. When a driver at the server restarts, clients wont get noticed by those restarts, and cannot reconnect. That's the reason why the driver suddenly behaves unresponsive after initial connection.

@Jasem: We started to discuss how to handle driver restarts on the client side ... what do you think. I see this still as a major problem that clients an not automatically reconnect when a driver has restated. Or did you solve this problem in EKOS already?

Btw: The INDI CCD module of the new PixInsight 1,8.5 version is now able to control to external filter wheels ;)
5 years 2 months ago #20817

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

  • Posts: 125
  • Thank you received: 15
Thanks for your response. I tried the pixinsight indi client (1.8.5), without success. The question that remains is why the filter wheel crashes on the rock64.
An automatic reconnect to ekos would be a great feature.
Wim

Skywatcher 190MN + 150PDS, AZ-EQ6 GT + EQ3-2 Goto, ZWO ASI294MM Pro + ZWO ASI174MM-Cool, Raspberry Pi4 with Astroberry + Rock64 x 2 with INDI & PHD2

www.astrobin.com/users/wimvb/
5 years 2 months ago #20819

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

  • Posts: 41
  • Thank you received: 7
Yes, any client will show a similar behaviour ... the root cause of this problem is the crash of the asi filter driver on rock64. I run this driver on a raspberry pi 3 and it woks without problems.
5 years 2 months ago #20820

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

  • Posts: 125
  • Thank you received: 15
Same here. It works great on the Pi. The reason I'm testing this with the Rock64, is that it has a usb3 port. With shorter image transfer times, amp glow should be less of an issue with my ASI174.
Wim

Skywatcher 190MN + 150PDS, AZ-EQ6 GT + EQ3-2 Goto, ZWO ASI294MM Pro + ZWO ASI174MM-Cool, Raspberry Pi4 with Astroberry + Rock64 x 2 with INDI & PHD2

www.astrobin.com/users/wimvb/
5 years 2 months ago #20824

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

  • Posts: 125
  • Thank you received: 15
If it is the OS that is (part of) the problem, and causes the fw driver to crash, would it be better to install INDI under debian? At the moment I have it running under Ubuntu on the Rock64 and Raspberry Pi.
Wim

Skywatcher 190MN + 150PDS, AZ-EQ6 GT + EQ3-2 Goto, ZWO ASI294MM Pro + ZWO ASI174MM-Cool, Raspberry Pi4 with Astroberry + Rock64 x 2 with INDI & PHD2

www.astrobin.com/users/wimvb/
5 years 2 months ago #20826

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

  • Posts: 41
  • Thank you received: 7
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
5 years 2 months ago #20833

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

  • Posts: 125
  • Thank you received: 15
Will try that tomorrow. Never heard of "trace" though. Only logging in ekos/kstars, so I will have to look it up first.
Wim

Skywatcher 190MN + 150PDS, AZ-EQ6 GT + EQ3-2 Goto, ZWO ASI294MM Pro + ZWO ASI174MM-Cool, Raspberry Pi4 with Astroberry + Rock64 x 2 with INDI & PHD2

www.astrobin.com/users/wimvb/
5 years 2 months ago #20835

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

  • Posts: 125
  • Thank you received: 15
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.)
Wim

Skywatcher 190MN + 150PDS, AZ-EQ6 GT + EQ3-2 Goto, ZWO ASI294MM Pro + ZWO ASI174MM-Cool, Raspberry Pi4 with Astroberry + Rock64 x 2 with INDI & PHD2

www.astrobin.com/users/wimvb/
5 years 2 months ago #20858

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

  • Posts: 41
  • Thank you received: 7
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?
5 years 2 months ago #20860

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

  • Posts: 125
  • Thank you received: 15
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.
Wim

Skywatcher 190MN + 150PDS, AZ-EQ6 GT + EQ3-2 Goto, ZWO ASI294MM Pro + ZWO ASI174MM-Cool, Raspberry Pi4 with Astroberry + Rock64 x 2 with INDI & PHD2

www.astrobin.com/users/wimvb/
5 years 2 months ago #20861

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

Time to create page: 0.553 seconds