Closed triplanedave closed 6 years ago
FWIW, setting back to default values makes no difference. Using SharpCap with the camera, I am getting images, so not a broken camera.
Hi Dave, did you try to capture images when it was dark outside? The camera starts taking pictures at civil twilight so if you want to test it during the day, you'll have to set your lat/long to a place on earth where it's dark. Let me know how it goes, I'm trying to narrow the issue down by eliminating the common problems.
That happened to me when I first used Allsky which I consider a nice feature, easier than adding a RTC and programming. Bill
Sent from my iPhone
On Apr 25, 2018, at 19:46, Thomas Jacquin notifications@github.com wrote:
Hi Dave, did you try to capture images when it was dark outside? The camera starts taking pictures at civil twilight so if you want to test it during the day, you'll have to set your lat/long to a place on earth where it's dark. Let me know how it goes, I'm trying to narrow the issue down by eliminating the common problems.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
Yes, I left it running all night long. It finally logged that it was out of daytime, and should be capturing images, but they were always black.
Shouldn't live view in the Admin Panel at least show the current image, even if it's not capturing?
Yes the live view shows image.jpg located at the root of the project. Have you tried starting the program manually?
./allsky.sh
This may give you a bit more info in the terminal.
No, hadn't thought of running it manually. I'll give that a shot. Also thinking about whether the metadata for the image might have some clue as to what the settings are for the capture. Do you know if the metadata is provided by the camera driver, or the capture app, or ? Would the image capture metatdata (exposure length, gain, etc) be of any value to know?
I believe the only info being written to the metadata is image type, width and height. If running the program manually still doesn't give you more info, try going back to the old firmware.
2018-04-27 10:58 GMT-07:00 Dave Randall notifications@github.com:
No, hadn't thought of running it manually. I'll give that a shot. Also thinking about whether the metadata for the image might have some clue as to what the settings are for the capture. Do you know if the metadata is provided by the camera driver, or the capture app, or ? Would the image capture metatdata (exposure length, gain, etc) be of any value to know?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/thomasjacquin/allsky/issues/16#issuecomment-385047533, or mute the thread https://github.com/notifications/unsubscribe-auth/AC6WJovNyNyNjC1Vyzx_8-5Wxuy9syXSks5ts1xJgaJpZM4TkXmm .
ran it manually. Got the following after it came out of waiting for night and tried 1st image capture: OpenCV Error: Incorrect size of input array (Non-positive cols or rows) in cvInitMatHeader, file /build/opencv-U1UwfN/opencv-2.4.9.1+dfsg1/modules/core/src/array.cpp line 146
Hey Dave, you don't need to wait for night, you can change your longitude for some place on earth where it's dark in order to test the camera. I have not seen this OpenCV error before. Could you try re-running the install.sh script and reboot in the end? I'm not sure why OpenCV would fail when trying to save the image.
Another method is to change the system date + dark hours with the command line date. After your test then reboot and enter date to check that the date has returned to normal.
Bill P.
Sent from my iPad
On May 3, 2018, at 11:05 AM, Thomas Jacquin notifications@github.com wrote:
Hey Dave, you don't need to wait for night, you can change your longitude for some place on earth where it's dark in order to test the camera. I have not seen this OpenCV error before. Could you try re-running the install.sh script and reboot in the end? I'm not sure why OpenCV would fail when trying to save the image.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.
ok, doing the longitude works. manually running the script still errors some times, but sudo .\allsky.sh will eventually work. But, still black images. wondering if we can coordinate a remote session with teamviewer? i have it running on the device. maybe something will be obvious to you
OK, problem solved.
1) Reinstall Raspian
2) Update Raspian
3) Reinstall allsky
4) Use 2.4a power supply
All good!
Great! The power supply may have been the issue here. The camera takes a bit of power so if the power supply is not strong enough, it will fail to work properly.
Love the project, 100% fits the bill for what I'm trying to accomplish. Only challenge is that I'm getting pure black images.
Log.txt is showing:
-bin 1 -brightness 50 -darkframe 0 - delay 20000 -exposure 5000000 -filename image.jpg -flip 0 -fontcolor 255 0 0-fontline 1 -fontname 0 -fontsize 0.7 -fonttype 0 -gain 50 - gamma 50 -height 960 -latitude 47.66N -longitude -122.12W -nodisplay 1 -quality 95 -text ThunderCreek -textx 15 -texty 35 -time 1 -type 1 -usb 80 -wbb 90 -wbr 53 -width 1280
Thoughts on what I might need to change to get it properly imaging? It's a ZWO120MC on a RPI 3 with the "compatible" firmware upgrade done on the camera.