Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Loop of All Sky Starting then failing #461

Closed
DamoclesSword opened this issue Sep 8, 2021 · 17 comments
Closed

Loop of All Sky Starting then failing #461

DamoclesSword opened this issue Sep 8, 2021 · 17 comments
Assignees
Labels
bug Needs software change

Comments

@DamoclesSword
Copy link

It seems that me, and Patriot Astro, have ran into a new issue where everything works, but in the GUI it will say "starting up" then give a "not running" error and do that cycle a few times.

@EricClaeys
Copy link
Collaborator

@DamoclesSword, please check in the log file /var/log/allsky.log. AllSky is starting, getting an error of some type, exiting, then restarting, getting the error, etc.
If you see ASI_ERROR_TIMEOUT messages in the log file, please make sure you have the latest capture.cpp and camera_options_ZWO.json files, and in the GUI, go to the bottom, click on "Show advanced options", and make sure "Version 0.8 Exposure" is UNchecked.

@ckuethe
Copy link
Collaborator

ckuethe commented Sep 12, 2021

Try applying the patch from #469. It won't fix your problem, but maybe it'll tell you what's failing.

@DamoclesSword
Copy link
Author

@DamoclesSword, please check in the log file /var/log/allsky.log. AllSky is starting, getting an error of some type, exiting, then restarting, getting the error, etc.
If you see ASI_ERROR_TIMEOUT messages in the log file, please make sure you have the latest capture.cpp and camera_options_ZWO.json files, and in the GUI, go to the bottom, click on "Show advanced options", and make sure "Version 0.8 Exposure" is UNchecked.

I finally got time to check. Here is the log:
Sep 7 20:08:26 allsky allsky.sh[2377]: ***** Starting AllSky *****
Sep 7 20:08:26 allsky allsky.sh[2377]: Making sure allsky.sh is not already running...
Sep 7 20:08:26 allsky allsky.sh[2377]: Trying to automatically choose between ZWO and RPI camera
Sep 7 20:08:26 allsky allsky.sh[2377]: CAMERA: ZWO
Sep 7 20:08:26 allsky allsky.sh[2377]: CAMERA_SETTINGS: /home/pi/allsky/settings_ZWO.json
Sep 7 20:08:27 allsky allsky.sh[2377]: Starting allsky camera...
Sep 7 20:08:43 allsky allsky.sh[498]: ***** Starting AllSky *****
Sep 7 20:08:43 allsky allsky.sh[498]: Making sure allsky.sh is not already running...
Sep 7 20:08:44 allsky allsky.sh[498]: Trying to automatically choose between ZWO and RPI camera
Sep 7 20:08:44 allsky allsky.sh[498]: None of RPI or ZWO Cameras were found. Exiting.

I dont see any clear error.

As for Ckuethe, I am not sure how to do what you suggest. I am new to all of this.

@ckuethe
Copy link
Collaborator

ckuethe commented Sep 12, 2021

"None of RPI or ZWO Cameras were found. Exiting." You haven't said what kind of camera you're using.

If you are using a ZWO camera, does it show up when you run lsusb, eg. ID 03c3:120d ZWO ASI120MM-S? If you're using the rpi camera, does vcgencmd get_camera say supported=1 detected=1

@DamoclesSword
Copy link
Author

Ive tried it with a 120MC-S and 178MM

@DamoclesSword
Copy link
Author

Sorry didnt see the other half. As for that "run lsusb, eg. ID 03c3:120d ZWO ASI120MM-S? If you're using the rpi camera, does vcgencmd get_camera say supported=1 detected=1" I have no idea how to do that

@ckuethe
Copy link
Collaborator

ckuethe commented Sep 12, 2021

In the same way that you installed the allsky software, you'll need to open up a shell to run those commands. Just type lsusb or vcgencmd get_camera and see what happens.

@DamoclesSword
Copy link
Author

When running lsusb, I get:
Bus 001 Device 002: ID 03c3:178c
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

and with the get_camera it says zero for both. Granted, this is using my 178MM and not my 120MC-S

@DamoclesSword
Copy link
Author

The new error log shows:

Sep 12 16:50:19 allsky allsky.sh[2265]: Stop the allsky service to end this process.
Sep 12 16:50:19 allsky allsky.sh[2265]: ==========
Sep 12 16:50:19 allsky allsky.sh[2265]: === Starting daytime capture ===
Sep 12 16:50:19 allsky allsky.sh[2265]: ==========
Sep 12 16:50:19 allsky allsky.sh[2265]: Saving images with delay of 5,000 ms (5 sec)
Sep 12 16:50:19 allsky allsky.sh[2265]: > ERROR: Failed getting image, status = 11 (ASI_ERROR_TIMEOUT)
Sep 12 16:50:22 allsky allsky.sh[2265]: > ERROR: Failed getting image, status = 11 (ASI_ERROR_TIMEOUT)
Sep 12 16:50:24 allsky allsky.sh[2265]: > ERROR: Failed getting image, status = 11 (ASI_ERROR_TIMEOUT)
Sep 12 16:50:30 allsky allsky.sh[2265]: ***** Stopping AllSky *****
Sep 12 16:50:30 allsky allsky.sh[2265]: capture exited with retcode=2

@ckuethe
Copy link
Collaborator

ckuethe commented Sep 12, 2021

Progress, then. Your camera is detected. Now try Eric's suggestion and see if changing the 0.8 Exposure makes any difference.

@DamoclesSword
Copy link
Author

It was already turned off. So no change besides the new error log

@EricClaeys
Copy link
Collaborator

@DamoclesSword,
Please try the attached file. It's the version 0.7 capture.cpp that knows about the new option names (e.g., "daybrightness" instead of "brightness") that were added in version 0.8. It does not use the "Version 0.8 exposure" mode.

Unpack the file, rename the .cpp file to "capture.cpp", put in ~/allsky, then "cd allsky ; make capture" and restart AllSky. It won't give any errors in the log file but you'll know it's working if you get images.

Let me know how it goes.
Eric
capture0.7with0.8arguments.zip

@EricClaeys
Copy link
Collaborator

@DamoclesSword,
what did you do to have the Pi recognize your camera? Your first attempt didn't even find the camera but the second attempt did.
Eric

@linuxkidd linuxkidd added the bug Needs software change label Oct 4, 2021
@EricClaeys
Copy link
Collaborator

@DamoclesSword,
any update? If you have things working with the newest code, please close this issue.

@DamoclesSword
Copy link
Author

I still have not found a solution, but I can try again soon!

@EricClaeys
Copy link
Collaborator

@DamoclesSword, try the file I attached on Sept 12 and see if that works.

@EricClaeys
Copy link
Collaborator

Closing issue, never heard back from user.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Needs software change
Projects
None yet
Development

No branches or pull requests

4 participants