×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

Read More...

Failed to start profile ASI EFW indiwebmanger issue

  • Posts: 50
  • Thank you received: 6

Replied by Konstantin Baranov on topic Failed to start profile ASI EFW indiwebmanger issue

I have similar problem. I use EKOS with local profile. After latest upgrade, it silently does not connect the EFW device, even though it starts the driver. I changed EKOS profile to use INDI 'remotely' and start INDI server manually. Now it works again. Didn't have time to dig anything out of the logs yet.
3 months 5 days ago #98740

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

Replied by Jasem Mutlaq on topic Failed to start profile ASI EFW indiwebmanger issue

All the ASI prefixes have been removed, it's all now ZWO
3 months 5 days ago #98742

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

  • Posts: 208
  • Thank you received: 14

Replied by Nick Birkett on topic Failed to start profile ASI EFW indiwebmanger issue

Jasem, I guess that's a ZWO thing since they do the drivers.
I was completely thrown by that one especially as ASI EFW was the first item in the dropdown box in the profile editor and ZWO EFW is the last one and I had been using ASI EFW for years (the driver is also called indi_asi_wheel)
Using kstars v 3.6.8 presently presumably this will change for next release ?
What about the driver names ?
nick@plum:~$ ls /usr/bin/indi*asi*
/usr/bin/indi_asi_ccd /usr/bin/indi_asi_wheel
/usr/bin/indi_asi_focuser /usr/bin/indi_lx200basic
/usr/bin/indi_asi_single_ccd /usr/bin/indi_oasis_focuser
/usr/bin/indi_asi_st4

ls /usr/bin/*zwo*
No such file or directory

Thanks for that.
Nick
3 months 5 days ago #98743

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

  • Posts: 208
  • Thank you received: 14

Replied by Nick Birkett on topic Failed to start profile ASI EFW indiwebmanger issue

Ok I also had to move my filter list from old profile
ASI EFW_config.xml'
to new profile
'ZWO EFW_config.xml'

Nick
3 months 5 days ago #98744

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

  • Posts: 208
  • Thank you received: 14

Replied by Nick Birkett on topic Failed to start profile ASI EFW indiwebmanger issue

FYI It all works on my set correctly now.
I use a single board PC indi server and connect using a Linux client (my desktop workstation in my office), so almost always use the remote
profiles. The remote server does have a vnc desktop running but I only use this for starting phd2.
I've always used the indiwebmanager to start the remote drivers. Now I changed to use ZWO EFW this is back to working as expected.
I had to reset my filter wheel profiles and filters from using ASI EFW to ZWO EFW profiles.
Nick
3 months 4 days ago #98752

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

  • Posts: 208
  • Thank you received: 14

Replied by Nick Birkett on topic Failed to start profile ASI EFW indiwebmanger issue

I just upgraded to 3.6.9 .
The ASI EFW option in the profile editor has now gone so no confusion as ther is only ZWO EFW for ZWO filter wheel.
3 months 4 days ago #98759

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

  • Posts: 249
  • Thank you received: 62

Replied by Ferrante Enriques on topic Failed to start profile ASI EFW indiwebmanger issue

I followed the advice in this thread but no success so far: When indiserver is manually started with indi_asi_wheel and the client connects from remote everything works fine. But if it's Ekos to start the server it doesn't work.
I then tried to:
- Replace the config file name from 'ASI' to 'ZWO'
- Delete the config file and the default config. It then doesn't get recreated by Ekos because the driver is not connected.
- Reset all the tables in the sqlite database
- Upgrade to nightly

In all cases it seems to be Ekos failing to start the driver.
The log only reports a generic failure where the device is referred as 'ASI EFW' by the server but then the client cannot find 'ZWO EFW':
[2024-02-06T14:30:04.785 CET DEBG ][           org.kde.kstars.indi] - Starting INDI Driver "indi_asi_wheel"
....
[2024-02-06T14:30:05.005 CET DEBG ][           org.kde.kstars.indi] - Received new device ASI EFW
[2024-02-06T14:30:05.019 CET DEBG ][           org.kde.kstars.indi] - < ASI EFW >: < CONNECTION >
[2024-02-06T14:30:05.019 CET DEBG ][           org.kde.kstars.indi] - < ASI EFW >: < DRIVER_INFO >
[2024-02-06T14:30:05.019 CET DEBG ][           org.kde.kstars.indi] - < ASI EFW >: < DEBUG >
[2024-02-06T14:30:05.019 CET DEBG ][           org.kde.kstars.indi] - < ASI EFW >: < SIMULATION >
[2024-02-06T14:30:05.046 CET DEBG ][           org.kde.kstars.indi] - < ASI EFW >: < CONFIG_PROCESS >
[2024-02-06T14:30:05.046 CET DEBG ][           org.kde.kstars.indi] - < ASI EFW >: < POLLING_PERIOD >
[2024-02-06T14:30:05.111 CET INFO ][           org.kde.kstars.ekos] - Connecting to "Telescope Simulator"
....
[2024-02-06T14:55:10.898 CET INFO ][           org.kde.kstars.ekos] - "Unable to establish:\n+ ZWO EFW\nPlease ensure the device is connected and powered on."

Attached the full log.
Any idea?
Ferrante
3 months 2 days ago #98842
Attachments:

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

  • Posts: 208
  • Thank you received: 14

Replied by Nick Birkett on topic Failed to start profile ASI EFW indiwebmanger issue

Hi Ferrante.
I renamed the ASI EFW files to XXX.saved and then re-ran the profile editor created a brand new profile where I selected ZWO EFW
in the drop down box and saved it. I used the saved ASI files to remind me the order of the filter names as I have several wheels, otherwise these files are no longer needed.
On EKOS start up it wont start the profile because there is another box than then pops up asking to connect all the equipment (with the usb id's), then it connects and then pops up the optical train box to select the camera, telescope guider etc. Sometimes the usb connect box is hidden behind other windows and if you dont select it and check "connect all" then it won't work.
Hope that helps.
Nick
The following user(s) said Thank You: Ferrante Enriques
3 months 2 days ago #98849

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

  • Posts: 249
  • Thank you received: 62

Replied by Ferrante Enriques on topic Failed to start profile ASI EFW indiwebmanger issue

hi Nick,
thanks for your help.
I followed step by step what you described above. Unfortunately I get the same error: after starting Ekos and before the USB selector pops up I get the 'unable to connect' error.
I downgraded to 3.6.9 stable for this test, did you use nightly?

Ferrante
3 months 2 days ago #98852

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

  • Posts: 208
  • Thank you received: 14

Replied by Nick Birkett on topic Failed to start profile ASI EFW indiwebmanger issue

Ferrante, I am just using 3.6.9 from the mutlaqja-ppa. This just got installed when I did an apt upgrade on server and client.
I have enough problems without trying to run "nightly" versions !
Currently trying to solve phd2 camera timeouts...........
One thing I find i need to do with my system is once the server is booted, disconnect and reconnect all the usb devices
one at a time (unlpug and replug). Same issue in NINA on a completely different system. Maybe cable issue, who knows, too many variables ?
Nick
The following user(s) said Thank You: Ferrante Enriques
3 months 2 days ago #98853

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

  • Posts: 249
  • Thank you received: 62

Replied by Ferrante Enriques on topic Failed to start profile ASI EFW indiwebmanger issue

hi Nick,
I'll keep trying. thanks,

I doubt it is cable issue: It works fine if I start it as standalone server. Plus, it's 10.000km from home...although I can ask people there.
ferrante
3 months 2 days ago #98854

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

  • Posts: 208
  • Thank you received: 14

Replied by Nick Birkett on topic Failed to start profile ASI EFW indiwebmanger issue

If you run a client locally, you can use an older version of kstars, it should run as it used to.
This is the biggest problem of kstars, that upgrades can completely break your setup.
I sometimes end up using another local machine with the standard distribution kstars (v 3.5.7 in ubuntu jammy)
as the client even though the remote server is up to the latest kstars-bleeding stable. Obviously all out of date stuff, but
gives you a result if desperate.
Good luck. Nick
3 months 2 days ago #98855

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

Time to create page: 0.983 seconds