Closed ckuethe closed 5 years ago
Regarding the message reset high-speed USB device number 6 using dwc_otg
, this is basically saying that the connection to the camera was reset because of some issue (low voltage could be causing it).
I had this kind of issue happen to me on a RPi4 using the USB3 and powered with the RPi3 power supply (2.5V instead of 3V).
This could also happen because of a long or low quality USB cable.
I'm using the USB cable that came with my ZWO ASI120MM-S, but I'll see about swapping it for a shorter cable.
Was just checking into the power supply; I made sure to get a good 3A, 5.2V supply (to account for cable loss), and neither dmesg
nor vcgencmd get_throttled
give any indication of undervoltage events.
FYI, for long power runs I've used https://www.amazon.com/gp/product/B018X0BAYS.. so I'm actually sending 48V about 500ft and using that to convert it to 5V.
My power run is only 5ft. But thanks for the pointer to that buck converter, it might be useful for some other outdoor projects I'm working on.
TL;DR - need a way to detect and delete images with corrupt jpeg data to prevent them from messing up startrails and keograms.
For reasons not clear to me, some of the jpgs written to disk are corrupt, causing startrails to complain like this:
and:
which leads to strange startrail images like this.
The only possibly weird thing in dmesg is a few of these:
but nothing in the allsky capture log indicating a capture error or failure to compress.
If I delete all the images with corrupt jpeg data and rerun
startrail
I get a much better looking image.