Introduction: Wireless All Sky Camera

Picture of Wireless All Sky Camera

An all sky camera is a device designed to take pictures of the entire sky over a certain amount of time, usually to monitor meteor showers or other astronomical phenomena.

I built mine to monitor the northern lights. I live in the Yukon and we sometimes get beautiful aurora displays during the night. However, I also have a day time job and I need my 8 hours of sleep. I created this camera to record a movie of the entire night. That way, I can replay the movie in the morning and never miss any aurora night.

Step 1: Requirements and Materials

Picture of Requirements and Materials

My requirements for this camera are the following:

  • needs to photograph most of the sky
  • needs high sensitivity to low light
  • should be weather proof
  • no wires should run to the house
  • needs to be autonomous
  • needs to create a movie from pictures and upload it to the internet
  • needs to start at dusk and stop at dawn

After thinking about it for a while, I decided that the device should include its own computer and send the pictures using wifi. As for the camera, I decided to use an astronomy camera that would be small enough and was powered over USB.

Here's the list of materials:

  • ASI224MC camera from ZWO (ASI120MC or MM works too and is cheaper)
  • wide angle lens Arecont 1.55 (It gives a wider field of view than the lens that comes with the camera)
  • Raspberry Pi 2 (or 3)
  • 64 GB micro SD card
  • Wifi module (no need if Raspberry Pi 3)
  • Short right angle USB cable
  • 4" ABS pipe with end caps
  • Acrylic dome

I thought about adding a dew heater but after a few month of testing, I never got any frost on the acrylic dome. This is possibly due to the heat produced by the raspberry pi itself.

Step 2: Wiring

Picture of Wiring

In this instructable, I will assume that you already have raspbian installed on the SD card.

The wiring is relatively easy. Plug the USB cable to the camera on one side and the raspberry pi on the other. Plug the wireless dongle into one of the 3 remaining USB ports of the pi. Insert the micro SD card in its slot and plug the raspberry pi to its 5V adapter.

In order to keep things tidy, you can fix your camera and computer onto a plywood board like I did on the picture.

Step 3: Build the Enclosure

Picture of Build the Enclosure

The enclosure is made of a 4" ABS pipe, a flat end cap and a threaded end cap with its lid.

The flat cap goes on top and is drilled to the diameter of the camera. The threaded cap goes at the bottom and a hole (for the extension cord) is drilled in the centre of the lid.

The acrylic dome can be fixed onto the top end using weather proof silicone. I used an acrylic ring but it makes things more complex than they need to be.

You can now fix the enclosure onto your deck, your roof or any other location with a good view of the sky.

Step 4: Software

Picture of Software

Update: If you need to change the way the capture works, you might have to make changes to the C++ source and compile it on your Raspberry PI. To do this, follow PeterD192's detailed instructions in the comments.

Update 2 (Nov 11th 2016): I have set up a GitHub page with an install script to make things easier for everyone: If you use it, you shouldn't have to use any of the following instructions.

Original Instructions:

In order to capture images with the camera, we need to run a program in the terminal. ZWO provides an SDK in order for developers to communicate with the camera. Using this SDK, I modified one of their C++ example and compiled it for the raspberry pi. Here's a list of dependencies that need to be installed in order to get the program running.

  • OpenCV to capture the image of the sky (You can get a compiled version here)
  • Sunwait to calculate the civil twilight of your location. There is a compiled version in the archive. Make sure you copy it to your path:
    sudo cp ~/allsky/sunwait /usr/local/bin
  • Required dependencies:
    sudo apt-get update && sudo apt-get install libusb-dev libav-tools gawk lftp entr imagemagik

To make things easy, I have attached an archive. Extract it at /home/pi/allsky.

From the lib folder, you will need to run this in order to use the camera without being root:
sudo install asi.rules /lib/udev/rules.d

You will also need to add to your library:
sudo cp ~/allsky/lib/armv7/libASICamera2* /usr/local/lib

Another thing you will need to do in order to automate everything is to run the main program on startup of the pi. You can open ~/.config/lxsession/LXDE-pi/autostart and add this line:
@xterm -hold -e ~/allsky/

Remember to set your wifi connection in order for the pi to upload videos. contains all the parameters you might want to play with: GPS coordinate, white balance, exposure and gain.

Step 5: Collect Images

Picture of Collect Images

Now that the raspberry pi is ready, you can plug your all sky camera. The startup script should call which in turn calls the binary file named "capture". It will determine if it's day time or night time. In case it's night time, the capture will start and take a picture every 5 seconds (or whatever value you set in At the end of the night, the capture will stop and avconv will stitch them together and upload a video to your website using FTP.

Step 6: Watch Your Time Lapse Videos

Picture of Watch Your Time Lapse Videos

The video produced by avconv should weigh between 30 and 50 mb depending on the length of the night (here in the Yukon, we can get from 18 hours to 0 hours of night time) and should be viewable on any web browser.

In the event that you find something interesting in the video, you can access the individual images on the raspberry pi. They will be in a folder named after yesterday's date.

Here's a page showing my own videos with almost all night archived starting January 18th 2016. Some have beautiful northern light, others have clouds, snow or rain.


PaulS627 (author)2018-01-18

Thought I wold put this in as separate comment from my previous ones.

I have now got it up and running with the dark frame subtraction and the difference in the image is amazing. No more random coloured pixels in the image.

Unbelievably it is a clear night out here tonight, so fingers crossed I should have a decentish video to post up tomorrow.

Very many thanks for all the effort and time you have put into getting this project up and running...and also improving too.

ThomasJ1 (author)PaulS6272018-01-18

Thanks a lot Paul. I'm really happy to hear about positive results because I could only test it on my own camera which, at -20C has only 3 or 4 hot pixels, so I wasn't sure if it would work well for others too.

PaulS627 (author)ThomasJ12018-01-18 worries. Very quick timplapse can be seen here

Is very clear to see how much of a difference the darkframe subtraction makes and you can also see this in effect when you get full cloud cover

PaulS627 (author)PaulS6272018-01-19

Looks like I have a smally error on the end of night actions.

When I went to look at it just now to move the files over to my NAS, the Allsky window was showing the following

'Posting next twilight time

Uploading data.json' and then looked like it was trying to connect to a default ftp server.

Can't say I have ever seen this before, but have never looked at this time. Have always left it alone to do it's thing.

What I dod notice is that when I was trying to copy the text in the window, when I hit Ctrl+C it stopped trying to do the upload and then went through the whole of the image rename and making of the timelapse.

Is this normal?

ThomasJ1 (author)PaulS6272018-01-19

Hi Paul,

I added in the last release. You don't really need it. It's just a helper if you have a website and you want to send the next twilight time to know when to resume live view.

You can add a # sign at the beginning of line 5 in Then it will stop trying to upload. I'll update the repo as well.

ThomasJ1 (author)ThomasJ12018-01-19

sorry I meant line 5 in

PaulS627 (author)ThomasJ12018-01-19

Have now hashed it out, many thanks

PaulS627 (author)PaulS6272018-01-19

Full video now available

RonaldS119 (author)2018-01-15

Thomas, I had success in modifying capture so that I could limit the number of images I take (just so I could practice transferring short movies). In generating the movie I see a lot of libraries in use, but I get som strange comments:

"using cpu capabilities; ARMv6 NEON (but the Rpi 3 is an ARM7 processor)?

Then I see:

deprecated pixel format used, make sure you did set range correctly?

past duration 0.9999992 too large - repeated 5 times

It does produce and upload the movie, but I am not sure how many frames actually got used.

The movie file is smaller (226 KiB) than the individual pictures (1280x960 - 279KiB)), I had display turned off, so none of the frames had segmentation.

Is it making the movie from the resized images?



RonaldS119 (author)RonaldS1192018-01-15

I guess I mis-spoke too early. I am still seeing some segmented images even though I am not displaying them as they are saved. I am still running inside so my exposures are long 30ms every 2 seconds. I will try it with normal setting outside soon.



RonaldS119 (author)RonaldS1192018-01-15

Alright, made my first night sky movie! I ran it for only an hour and a half (450 frames at my settings). I can definitely use dark subtraction, but I don't really know how much more it would reveal. I will have to try it on a couple of frames. I am running the camera the rest of the night, just for fun!

thanks again for this project.


ThomasJ1 (author)RonaldS1192018-01-16

Hi Ron,

I will release the dark subtraction code today if all goes well. I am also looking in a linux kernel patch that can fix the segmentation issue with ASI120 USB2 cameras. I'll keep you posted.

RonaldS119 (author)ThomasJ12018-01-17


It looks like you did some updating of the github site with additions for dark subtraction, great! what is the easiest way to upgrade my current allsky instillation on the Rpi? I am looking for a command like git sync (or update) allsky?

ThomasJ1 (author)RonaldS1192018-01-17

Until I make a fancy "update" button on the GUI, I believe the easiest is to copy settings.json and somewhere to keep track of your current settings, delete the allsky directory and clone the repo again.

Then edit both settings.json and to add your camera settings and FTP info back in.

I know it's a bit of work but that's the easiest until I figure out a 1-click solution.

RonaldS119 (author)ThomasJ12018-01-17


I looked for the kernal update on the ZWO user site, but it says "Moving to a new Server?"

ThomasJ1 (author)RonaldS1192018-01-17

It was live yesterday. Try a gain in a bit. It may take them a few hours if they are migrating their forum to a new place.

RonaldS119 (author)ThomasJ12018-01-17


Thank you for your work on the dark frame subtraction, it looks like it is working well. I have only been subtracting like frames (both dark and light) and have been getting pretty black images (as one would hope). This will really help those of us in warmer climates. Now to solve the dew and frost problems!

ThomasJ1 (author)RonaldS1192018-01-18

Here's the new location for ZWO forum:

Maybe a few resistors can keep the temperature above dew point.

picoranger (author)2018-01-14

Thomas, (or is it Tom?)
Thanks for all the work you've done on this project... Just completed some preliminary tests, and I can verify that the ZWO ASI libraries work with great with their ASI 1600MC camera.

I just had a quick question on the FTP process. I set up a FTP server on a local network PC via Filezilla. Instead of accruing an accumulation of pictures and videos, I only receive the latest captured image (named "image-resize.jpg"). Is there a file or script I can tweak regarding the FTP process to send all the captured pics? Or is this something I need to configure with the FTP server?

ThomasJ1 (author)picoranger2018-01-15

Hi Picoranger (or is it Pico?) :)

Thanks for confirming that the ASI1600MC works, I'll add it to the list in the README.

The file you want to modify is

By default, the only image being uploaded is the preview (smaller image) and the full images and video stay on the RPi SD Card. Then you have to delete the old one manually to make some space.

You can access all of this using filezilla.

So if I understand correctly, you want to save all the pictures and videos on your local server instead of the RPi ?


picoranger (author)ThomasJ12018-01-15

Thanks for the quick reply! One more question, I work for the National Park Service and I plan on deploying a couple of these setups in the Grand Canyon, to monitor Dark Sky levels against nearby urban centers. Is there an easy way to adjust the script directories for the on-board image and video storage, to a USB mounted drive on the RPi? The idea would be to easily retrieve the data...

ThomasJ1 (author)picoranger2018-01-16

Yes this is something that can be configured. I did this on a couple of cameras already. Basically, you add a line in fstab to mount the USB drive during boot and you create a symbolic link from /home/pi/allsky/images to /mnt/usb.
Then everything that was supposed to get saved in the /home/pi/allsky/images location, actually gets saved on the flash drive.
I may make a script to automate that later. I can give you the step by step instructions if you want.

picoranger (author)ThomasJ12018-01-16

Well, I gave it stab. I figured out the fstab part and mounted a drive on boot up... but botched the symbolic link part...

Any chance I can bother you with a step by step on mounting the USB for data storage? I'll just start from scratch to get it right. --Also, I'll be getting my hands on a ASI295MC, shortly... I'll let you know how it runs!

ThomasJ1 (author)picoranger2018-01-17

Alright, so if you have the fstab step figured out, you now need to create the symbolic link.

First, delete (or rename if you want to keep the content) the /home/pi/allsky/images directory because we will replace it with a symlink.

now, in the terminal:

ln -s /mnt/usb /home/pi/allsky/images

Make sure to replace "usb" by the directory you created earlier (the one listed in the line you added in fstab).

Also, make sure that your are the owner of that directory:

sudo chown -R pi:pi /mnt/usb

That should be all you need.

RonaldS119 made it! (author)2018-01-10


If I run the program with the "nodisplay" set to 0, so I get a display; my images come out in multiple segments. If I have "nodisplay" set to 1 they all come out fine. Sorry if this has been mentioned before, I have tried reading thru all the comments, but at my age I forget what I have read halfway thru! Any progress on the dark image subtraction update?

I built my inside like an old "erector" set, using metal wood joining strips as the structures. I made a collar, from 2" pvc pipe, for the camera to space it from the exterior pipe top so it sits approximately at the center of the dome. I used 4" White PVC for the exterior just because that was available in the local hardware store.



ThomasJ1 (author)RonaldS1192018-01-10

Hi Ronald, nice build. I like to see how builders come up with their own ideas based on the materials they can find.

I'm just back from vacation and I will be working on the dark frame subtraction in the coming days.

I'm not sure why you are getting segments in the image preview. I don't have an asi120 on hand to replicate the issue.

RonaldS119 (author)ThomasJ12018-01-10


Thanks, it is a fun project. The images that are stored are also in segments, but only when the display option is on. I thought it might have something to do with my screen resolution, but that does not seem to be the case. It is also not 100%, many images are segmented, but some are fine in the display on mode. I will keep playing with it. I set my location off so I could run it during the day (and adjust focus with the lens), so my exposure is running around 10 msec (short exposure) and I have a 10 second delay between images.

ThomasJ1 (author)RonaldS1192018-01-10

I think the 10 ms exposure may cause the segmentation. I have never tried to go that low so it hasn't really been tested with such short exposure.

Do you also get segmentation with longer exposure? 3 sec for example.

RonaldS119 (author)ThomasJ12018-01-10


I ran the program with exposures from 10 ms to 3 seconds both with and without the active display turned on. It always works when the display is off (at all even short exposures) but fails occasionally (4 out of 13 exposures) when the display is on (even 3 sec long exposures).

RonaldS119 (author)RonaldS1192018-01-10

both images are from the 3 second exposure run with the active display turned on. the first image came out ok, the second image is what I call segmented.

RonaldS119 (author)RonaldS1192018-01-10

I assume you are just issuing camera commands (from AISCamera2.h) to capture an image. How might I issue a command for the ASI_Exposure_Status to see if the exposure failed? I don't think this is an issue using SmartCap with the camera, but I will check. Also, do not spend too much time on this, as I really don't intend to monitor the images while the program is running. I was only doing it to try and adjust focus, but I did that thru smartcap on my PC.



ThomasJ1 (author)RonaldS1192018-01-10

You're not the only one with the segmented image problem. They seem to all come from an ASI120 camera. One user reported seeing the same issue using PHD Guiding so I think it may be related to the camera firmware.

In order to get a preview, you could install the GUI. It will do the same thing as the display option except that it will show in your browser instead so you shouldn't see any segmented image.

RonaldS119 (author)ThomasJ12018-01-10

Interesting, I don't see the segmentation running either PHD2 or SharpCap under various exposure settings and in preview mode. And recall I did update the camera firmware as you had suggested. I did not want to use the GUI as I am using this Rpi for other things at the moment. Eventually, I will have one dedicated to this project. Since it works in the mode I intend it to eventually, I am no too worried about this.

RonaldS119 (author)RonaldS1192018-01-11


I just noticed that all of the segmented images are larger than the normal images. For the 3 second exposure ones, any image larger than 296 KBs is segmented. I am not sure what that means?

What are your recommended specifications for the SD card? I know you suggested 64 GBs, probably to hold lots of images. (an image every 5 seconds for 10 hours x 300KBs < 3 Gbs so that seems overkill). More important might be write (to the card) speed. USB 2.0 speed is typically 40 to 60 MBps, so I suspect the card should at least support that speed. What are your thoughts?

ThomasJ1 (author)RonaldS1192018-01-11

It seems like it is writing the next image into the previous one. I use 64 GB because I use about 1 GB per night and the nights are 19 hrs long in winter. I use class 10 cards such as the Samsung Evo+.

Does the segmentation happen in the image at the root of the project or in the "images/current" directory or both? I'm trying to rule out a speed issue with

RonaldS119 (author)ThomasJ12018-01-11

If I have the "nodisplay" set to 0 ( so it shows the preview) the segmentation shows up both in the preview and in the image file.

I just noticed that you have a comment in to uncomment the following line if you get segmentation fault during timelapse on Pi3. the line reads "#cpulimit -e avconv -1 50 &" I assume this is only applies when creating the video.

I am trying to see if the segmentation happens with raw image files, but it is not writing consecutive image files to the image/current directory? It only writes one file to the allsky directory. type=2, quality=3

RonaldS119 (author)RonaldS1192018-01-11

strike the last part of that comment, I must have done something else wrong, because it is writing the files to the correct directory.

anismo (author)RonaldS1192018-01-14

I use ASI120MC and rPi2 (armv6) and here is what I encounter:

If I have delay very low (like 10ms which is default) I get segmented image issue. It works fine if the delay is like 4 second and exposure is 5 sec.

Curiously, If I set delay longer than exposure then I get black image . I also get black image if I mess with the USB speed (I have USB 2.0) and it gives me black image.

ThomasJ1 (author)anismo2018-01-16

I'm trying this fix and I'll let you know how it works.

poedman1 (author)2017-12-27

Hi Thomas,

Great project, I am building one at the moment. I am in manila, Philippies.

I have a raspberry 3, with an ASI 120MC.

I ran your script from your github page, changed my coordinates. At the moment I do not want to upload my photos/videos anywhere just get in runing...

I am getting an error which I dont understand (not a programmer)

pi@raspberrypi:~/allsky $ ./

Starting allsky camera...

Warning: no target process found. Waiting for it...


*** Allsky Camera Software v0.2 | 2017 ***


Capture images of the sky with a Raspberry Pi and an ASI Camera

Add -h or -help for available options

Author: Thomas Jacquin - <>


-Knut Olav Klo

-Daniel Johnsen

-Yang and Sam from ZWO

-Robert Wagner

Listing Attached Cameras:

- 0 ZWO ASI120MC

ZWO ASI120MC Information:

- Resolution:1280x960

- Color Camera: bayer pattern:GR

- Initialise Camera OK

- Sensor temperature:30.500000

Capture Settings:

Image Type: ASI_IMG_RGB24

Resolution: 1280x960

Quality: 95

Gain: 50

Exposure: 5000000µs

Brightness: 50

Gamma: 50

WB Red: 53

WB Blue: 90

Binning: 1

Delay: 10ms

USB Speed: 40

Text Overlay: text

Text Position: 15px left, 35px top

Font Name: 0

Font Color: 255 , 255, 255

Font Line Type: 16

Font Size: 0.7

Font Line: 1

Flip Image: 0

Filename: image.jpg

Latitude: 14.33N

Longitude: 121.6E

No Display: 1

Timelapse: 1

Time: 1

Saving 5s exposure images every 10 ms

Press Ctrl+C to stop

./ line 20: 1294 Segmentation fault ./capture $ARGUMENTS

So what can be the probelm with htis.

Thanks In advance

Per Edman

ThomasJ1 (author)poedman12017-12-27

Hi Per,

Can you try deleting the binary file called "capture" and recompile it by running "make capture"?

Then try to run again.

If it doesn't solve the issue, can you post the last few lines from log.txt? There may be a problem with one of the arguments.

poedman1 (author)ThomasJ12017-12-27

H Thomas,

Thanks for helping a newbie...deleted the capture file and did the "make capture". Same error

here is the whole log file

-bin 1 -brightness 50 -delay 10 -exposure 5000000 -filename image.jpg -flip 0 -fontcolor 255 255 255 -fontline 1 -fontname 0 -fontsize 0.7 -fonttype 0 -gain 50 -gamma 50 -height 0 -latitude 60.7N -longitude 135.05W -nodisplay 1 -quality 95 -text text -textx 15 -texty 35 -time 1 -timelapse 1 -type 1 -usb 40 -wbb 90 -wbr 53 -width 0

Reading configuration file

-bin 1 -brightness 50 -delay 10 -exposure 5000000 -filename image.jpg -flip 0 -fontcolor 255 255 255 -fontline 1 -fontname 0 -fontsize 0.7 -fonttype 0 -gain 50 -gamma 50 -height 0 -latitude 14.33N -longitude 121,6E -nodisplay 1 -quality 95 -text text -textx 15 -texty 35 -time 1 -timelapse 1 -type 1 -usb 40 -wbb 90 -wbr 53 -width 0

Reading configuration file

-bin 1 -brightness 50 -delay 10 -exposure 5000000 -filename image.jpg -flip 0 -fontcolor 255 255 255 -fontline 1 -fontname 0 -fontsize 0.7 -fonttype 0 -gain 50 -gamma 50 -height 0 -latitude 14.33N -longitude 121,6E -nodisplay 1 -quality 95 -text text -textx 15 -texty 35 -time 1 -timelapse 1 -type 1 -usb 40 -wbb 90 -wbr 53 -width 0

Reading configuration file

-bin 1 -brightness 50 -delay 10 -exposure 5000000 -filename image.jpg -flip 0 -fontcolor 255 255 255 -fontline 1 -fontname 0 -fontsize 0.7 -fonttype 0 -gain 50 -gamma 50 -height 0 -latitude 14.33N -longitude 121,6E -nodisplay 1 -quality 95 -text text -textx 15 -texty 35 -time 1 -timelapse 1 -type 1 -usb 40 -wbb 90 -wbr 53 -width 0

Reading configuration file

-bin 1 -brightness 50 -delay 10 -exposure 5000000 -filename image.jpg -flip 0 -fontcolor 255 255 255 -fontline 1 -fontname 0 -fontsize 0.7 -fonttype 0 -gain 50 -gamma 50 -height 0 -latitude 14.33N -longitude 121,6E -nodisplay 1 -quality 95 -text text -textx 15 -texty 35 -time 1 -timelapse 1 -type 1 -usb 40 -wbb 90 -wbr 53 -width 0

Reading configuration file

-bin 1 -brightness 50 -delay 10 -exposure 5000000 -filename image.jpg -flip 0 -fontcolor 255 255 255 -fontline 1 -fontname 0 -fontsize 0.7 -fonttype 0 -gain 50 -gamma 50 -height 0 -latitude 14.33N -longitude 121.6E -nodisplay 1 -quality 95 -text text -textx 15 -texty 35 -time 1 -timelapse 1 -type 1 -usb 40 -wbb 90 -wbr 53 -width 0

Reading configuration file

-bin 1 -brightness 50 -delay 10 -exposure 5000000 -filename image.jpg -flip 0 -fontcolor 255 255 255 -fontline 1 -fontname 0 -fontsize 0.7 -fonttype 0 -gain 50 -gamma 50 -height 0 -latitude 14.33N -longitude 121.6E -nodisplay 1 -quality 95 -text text -textx 15 -texty 35 -time 1 -timelapse 1 -type 1 -usb 40 -wbb 90 -wbr 53 -width 0

Reading configuration file

-bin 1 -brightness 50 -delay 10 -exposure 5000000 -filename image.jpg -flip 0 -fontcolor 255 255 255 -fontline 1 -fontname 0 -fontsize 0.7 -fonttype 0 -gain 50 -gamma 50 -height 0 -latitude 14.33N -longitude 121.6E -nodisplay 1 -quality 95 -text text -textx 15 -texty 35 -time 1 -timelapse 1 -type 1 -usb 40 -wbb 90 -wbr 53 -width 0

-bin 1 -brightness 50 -delay 10 -exposure 5000000 -filename image.jpg -flip 0 -fontcolor 255 255 255 -fontline 1 -fontname 0 -fontsize 0.7 -fonttype 0 -gain 50 -gamma 50 -height 0 -latitude 14.33N -longitude 121.6E -nodisplay 1 -quality 95 -text text -textx 15 -texty 35 -time 1 -timelapse 1 -type 1 -usb 40 -wbb 90 -wbr 53 -width 0

Reading configuration file

-bin 1 -brightness 50 -delay 10 -exposure 5000000 -filename image.jpg -flip 0 -fontcolor 255 255 255 -fontline 1 -fontname 0 -fontsize 0.7 -fonttype 0 -gain 50 -gamma 50 -height 0 -latitude 14.33N -longitude 121.6E -nodisplay 1 -quality 95 -text text -textx 15 -texty 35 -time 1 -timelapse 1 -type 1 -usb 40 -wbb 90 -wbr 53 -width 0

Reading configuration file

-bin 1 -brightness 50 -delay 10 -exposure 5000000 -filename image.jpg -flip 0 -fontcolor 255 255 255 -fontline 1 -fontname 0 -fontsize 0.7 -fonttype 0 -gain 50 -gamma 50 -height 0 -latitude 14.33N -longitude 121.6E -nodisplay 1 -quality 95 -text text -textx 15 -texty 35 -time 1 -timelapse 1 -type 1 -usb 40 -wbb 90 -wbr 53 -width 0

-bin 1 -brightness 50 -delay 10 -exposure 5000000 -filename image.jpg -flip 0 -fontcolor 255 255 255 -fontline 1 -fontname 0 -fontsize 0.7 -fonttype 0 -gain 50 -gamma 50 -height 0 -latitude 14.33N -longitude 121.6E -nodisplay 1 -quality 95 -text text -textx 15 -texty 35 -time 1 -timelapse 1 -type 1 -usb 40 -wbb 90 -wbr 53 -width 0

-bin 1 -brightness 50 -delay 10 -exposure 5000000 -filename image.jpg -flip 0 -fontcolor 255 255 255 -fontline 1 -fontname 0 -fontsize 0.7 -fonttype 0 -gain 50 -gamma 50 -height 0 -latitude 14.33N -longitude 121.6E -nodisplay 1 -quality 95 -text text -textx 15 -texty 35 -time 1 -timelapse 1 -type 1 -usb 40 -wbb 90 -wbr 53 -width 0

-bin 1 -brightness 50 -delay 10 -exposure 5000000 -filename image.jpg -flip 0 -fontcolor 255 255 255 -fontline 1 -fontname 0 -fontsize 0.7 -fonttype 0 -gain 50 -gamma 50 -height 0 -latitude 14.33N -longitude 121.6E -nodisplay 1 -quality 95 -text text -textx 15 -texty 35 -time 1 -timelapse 1 -type 1 -usb 40 -wbb 90 -wbr 53 -width 0

Reading configuration file

-bin 1 -brightness 50 -delay 10 -exposure 5000000 -filename image.jpg -flip 0 -fontcolor 255 255 255 -fontline 1 -fontname 0 -fontsize 0.7 -fonttype 0 -gain 50 -gamma 50 -height 0 -latitude 14.33N -longitude 121.6E -nodisplay 1 -quality 95 -text text -textx 15 -texty 35 -time 1 -timelapse 1 -type 1 -usb 40 -wbb 90 -wbr 53 -width 0



Per Edman

poedman1 (author)poedman12018-01-14

Hi Thomas,

Any idea what can cause my problem?

Best Regards


Per Edman

ThomasJ1 (author)poedman12018-01-15

Hi Per,

Sorry for the delay, I've been thinking about it and the log looks fine. The only thing I can think of is maybe a dependency issue that wasn't installed properly during the script.

Can you try deleting the allsky folder and got over the installation again? Look for any errors in the terminal.


poedman1 (author)ThomasJ12018-01-15

Hi Thomas,

I did what you recommended and when I booted up again it runs. But I get two copies of running. Both running. When I remove one copy as you instructed in the previous comments only one copy starts but I get the segmentation fault again.

if I change it back to two copies they both runs.. Strange?

Also my goal is to make the photos/videos end up on one of my NAS drives, the local address is How can I make this happen?

Great Job you're doing...


Per Edman

ThomasJ1 (author)poedman12018-01-16

Hi Per,

There's a thread on ZWO forum indicating that patching the linux kernel helps with the packet size. I'm trying it on someone's installation and I'll post the steps if it fixes the segmentation issue.

Here's the thread:

RonaldS119 (author)2018-01-14


How would I configure the Rpi if I want to use an ethernet connection to my house router to pass the movie? I can reach farther from my house with an ethernet cable than my wifi will reach.



RonaldS119 (author)RonaldS1192018-01-14


Never mind I figured it out. I am using FileZilla for my PC ftp server and with the proper setting and permissions I can ftp files to it from the Rpi



poedman1 (author)RonaldS1192018-01-15

Hey Ronald,

Please explain how you send your photos/video to another computer/NAS on your home network. That is want I want also, not a webpage.

I'm not a programmer...

Thanks in advance


Per Edman

RonaldS119 (author)poedman12018-01-15

I am using the free 'ftp server' program Filezilla. In that program you can set up a home directory, shared folders, an external user id to log in, a password and permissions to read, write and delete files on the server. Once you have set up those parameters you just start the server.
On the Rpi I make sure it is on the same network as the PC, either over WiFi or over Ethernet. If you look at the command in the file it is the 'lftp' command. you need to make sure that your variables match the protocal = ftp, the user you set up in Filezill and password, the name of the host computer (the PC). If you set up a home directory in Filezilla then you don't need an Image directory, it will already be the home one. Then it is just a matter of lots of trial and error to get all the parameters correct so that files transfer. You can execute the 'lftp' command from a terminal using a dummy image file to practice on until you get it working. You don't have to keep running the allsky program to get the transfer to the pc working.
hope this helps,

About This Instructable




Bio: Most of the things I build usually relate to either astronomy, physics or woodworking in general.
More by ThomasJ1:Planets Photography GuideNewspaper StandSee Through Star Map
Add instructable to: