Jump to content

sgl_imaging_challenge_banner_31.thumb.jpg.b7a41d6a0fa4e315f57ea3e240acf140.jpg

Pete6

Members
  • Content Count

    36
  • Joined

  • Last visited

Community Reputation

25 Excellent

About Pete6

Profile Information

  • Location
    Charlotte NC

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I am not sure if this is the right thread. If it is not then please move it. I have a Pi 4 with 4GB memory. It boots from a 1TB SSD and has no microSD car in the device. I run the latest downloadable of astroberry and have done all the updates/upgrades. I also have a QHYCCD PoleMaster on the mount. If this is connected to a USB port neither oaLive or oaCapture will run. Clicking them does nothing. Running them in terminal gives the errors shown in the image. Cutting the USB power to the port with the PoleMaster allows oaCapture to run. I am running oaCapture 1.8.0 and oaLive 1.9.
  2. webcam uses Civil Dawn and Dusk times to switch modes. The camera seemed happier with this. You can select whichever Dawn / Dusk set you wish in lines 218 - 230 in the webcam file. Currently this is set to Civil but it can be changed to Nautical or Astronomical. I display these last two Dawn . Duck times only for information. They do not do anything inside the code. It's an astronomer's tool so I display all the Dawn / Dusk daily timings. Only the Civil times are currently used to switch camera modes and videos.. Hence the Midnight sun text is just informational. I changed one
  3. Jason, None of this should be happening. Could you please either post here or PM me the /home/pi/webcam file. I have no idea what has happened but I will find out. Actually if you need to post it on Dropbox or Google Drive let me have the link. Thanks
  4. Hi Sam, This sounds pretty exciting to me. I have no experience using the HQ camera although I have read all about it. It seems a mighty camera. It should work with AllSky Camera but given the foregoing, I ain't tested it so you are a (the?) pioneer here. I will give you all the help I can which may turn out to be worth exactly what you pay for it... One thing has emerged from testing and that is the Pi (even a 4) seems to take a fair while to completely clear itself after processing an image. This is why we have had so much discussion about how often a Pi Zero can take an image at
  5. No this is not doing narrow band. In fact I only just got the Raspberry Pi Cam V2 with its Sony IMX 219 sensor to gather enough light down the M12 mount to its 1/4 (I think()" sensor. There us also not IR filter so in fact this is about as wide a band as I can make it. My goal was to make a very cheap but usable AllSky Camera. Using a Pi Zero W you can make a working setup for well under £40 not including the case. Jiberjaber has used a drinks bottle for that. So not too expensive. If you skip using the temperature prob you can assemble the whole device with zero soldering and stand
  6. If you want to run a job every 2 minutes, open up webcam and find the part where I write out the crontab file and stick a line or two in there. There are plenty of examples in that code . echo "*/2 * * * * $HOME/myjob> /dev/null 2>&1">>$HOME/webcamcron should do the trick. That way it will get written to the crontab file each day when webcam runs itself and writes a new crontab file.
  7. Good. I am glad it is working now. I thought you would have done the mods but I really wanted to publish my findings so that in the future people do not have to go down the same hole. It is clear that the Pi Zero W has a lot less computing power than the Pi 4 but it also generates a lot less heat and is far, far cheaper so you can build my little box for less than £40. Of course it has to work and perhaps I was a little premature in publishing. I thought it worked. Mine did, well pretty much... It was just a few tweaks to the Pi Zero W version that were needed. I shall update the
  8. @Jason, I am going to try Install UV4L and WebRTC when I get some free time. That was a nice find. Thanks. I like the weather station integration. Editing the webcam.php is just fiddly, not hard and it looks perfect. It looks as if you are making real progress here. I too have been testing. As I said a few days ago, I have increased the gap between switching the camera from night to day and the start of the night video to 6 minutes. Combined with a 5 minute shot interval this has performed flawlessly the last 3 nights. I reccomend that you try these timing as well.
  9. root@0W-AllSky:/home/allsky/pics# ls -l total 10808 drwxr-xr-x 2 root root 4096 Apr 29 18:16 b -rwxr-xr-x 1 root root 1329 Apr 19 20:47 concatday.sh -rwxr-xr-x 1 root root 1341 Apr 19 20:47 concatnight.sh -rwxr-xr-x 1 root root 299 Apr 30 08:24 copypic.sh drwxr-xr-x 2 root root 20480 May 18 20:50 day -rw-r--r-- 1 root root 9476568 May 18 21:05 movieday.mp4 -rw-r--r-- 1 root root 624245 May 18 21:35 movienight.mp4 -rwxr-xr-x 1 root root 150 Apr 4 19:52 movie.sh -rwxr-xr-x 1 root root 2528 May 14 22:54 newdaymovie.sh -rwxr-xr-x 1 root root 2515 May 15 21:04 newnightmov
  10. Well maybe your camera is delivering images of a different size to mine. As downloaded and with a Pi Cam V2 it should work. The 110Kb file limit was set up for and is stopping all white image files on my Pi Zero W system. Could it be that your system is producing files that are smaller? If so the 110Kb limit certainly needs to be changed. Here is a ls - l dump from my Pi Zero W system
  11. What you are experiencing is exactly what happened to me. Once it works, it just goes on ticking. I am seeing about 22 second night videos and over a minute for daytime. This agrees with the other 3 Pi 3 and 4 systems running alongside.
  12. Thank you. You are right it is err, voluble. I am pretty sure after testing this device for some months that the problem is that raspistill does not clean up after itself very well. SInce I am launching a new instance every 4-5 minutes and I know the image takes approx 1m 40s from prompt to prompt I am forced to conclude tha it is doing other things that take longer after the image is complete. What I do not know but htop shows numerous instances of raspistill if I reduce the shot time. On a Pi 3 or 4 a safe [removed word] time is 4 minutes but it seems that on a Pi Zero W, 5 minute interv
  13. My Pi Zero W system just switched flawlessly from day to night. I have a 6 minute difference between the camera switching modes and the night video starting. This has worked two days in a row. The 3 Pi 3 and 4 systems have never had a problem with this change so It is like most things with my little project here, just a question of tweaking it until it does what you want. I am going to leave this running like this for another couple of days until I change newnightmovie.sh and remove the comment I referred to earlier. This is really getting close now to where I think it is reliable
  14. Love the pics. This is the way to do it on the cheap. I have seen one AllSKy Cam https://interactiveastronomy.com/skyeye.html that costs over a 1000 quid.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. By using this site, you agree to our Terms of Use.