×

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

Bi-monthly release with minor bug fixes and improvements

capture always aborted

  • Posts: 3
  • Thank you received: 0
StellarMate new user
Loaded StellaMate OS on a Raspberry Pi 5 and plugged USB cables into the ports. Have used app on ipad and Ekos and browser from Windows desktop.
I have:
Skywatcher EQ8 with EQMOD and USB cable
ASI183 mm cooled
Rigel N-step focus controller
ZWO 8 position filter wheel
ASI178 guide scope
Everything appears to be connected and I can slew the mount, change filters and move the focuser.
The camera appears to be connected, but when I try to capture a simple sequence, the sequence always fails with an "Aborted" message.
The INDI page is no help. It only says: [ERROR] Exposure failed after three tries.
I tried enabling debugging but it immediately disables itself leaving [INFO} enabled and disabled messages.

Any ideas how to fix this?

Bob
2 months 13 hours ago #99281

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

  • Posts: 1187
  • Thank you received: 370
Hi Bob,
first of all, the logging level is controlled by KStars/Ekos. Please use the logging button on the Manager tab, set the logging level to verbose and file based.

Then please post the log file here for further assistance.

Cheers
Wolfgang
2 months 9 hours ago #99292

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

Replied by Jasem Mutlaq on topic capture always aborted

There was an issue with ASI that was fixed just last week. Did you update the OS to the latest available updates?
The following user(s) said Thank You: Bob Benedict
Last edit: 2 months 8 hours ago by Jasem Mutlaq.
2 months 8 hours ago #99294

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

  • Posts: 3
  • Thank you received: 0

Replied by Bob Benedict on topic capture always aborted

Thanks - some little progress.
I updated stellarmate and managed to capture a few images from the main and guide cameras,. Then they mysteriously stopped working with aborts
I tried again tonight with zero success. The log is attached.
Bob
1 month 4 weeks ago #99362
Attachments:

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

  • Posts: 989
  • Thank you received: 161

Replied by Alfred on topic capture always aborted

I found my ASI cams sometimes "disappear" from the list in "lsusb". Just like they had never been connected.
When I get "exposure failed" messages, the first thing I do is check lsusb and 99% of the time both ASI cams have mysteriously disappeared from the list. Remarkably, they both show up again after a reboot even though nothing has changed (cables included).
1 month 3 weeks ago #99398

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

  • Posts: 3
  • Thank you received: 0

Replied by Bob Benedict on topic capture always aborted

Thanks for the reply.
Same story again tonight. The main and guide worked for a short while and then just stopped for no apparent reason.
looks like cameras are still there.
Bob

stellarmate@stellarmate:~ $ lsusb
Bus 004 Device 002: ID 2109:8110 VIA Labs, Inc. Hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 005: ID 04d8:fbb2 Microchip Technology, Inc. GCUSB-nStep stepper motor controller
Bus 003 Device 004: ID 03c3:1f01 ZWO ZWO EFW
Bus 003 Device 003: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC
Bus 003 Device 002: ID 2109:2811 VIA Labs, Inc. Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 004: ID 03c3:178a ZWO ASI178MC
Bus 002 Device 003: ID 03c3:183e ZWO ASI183MM Pro

Bus 002 Device 002: ID 2109:8110 VIA Labs, Inc. Hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 04b4:6572 Cypress Semiconductor Corp. Unprogrammed CY7C65642 hub
Bus 001 Device 002: ID 2109:2811 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
1 month 3 weeks ago #99453

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

Time to create page: 0.896 seconds