RaspberryPi Camera for Astrophotography

[gordon77]

Update:

- Save and Reload configs now includes more items eg DecN/S on/off, nr, 2x2 etc
- You can set it to load a pre-saved config at startup, set use_config in the program to = 1,2 or 3. Remember to save them first!

I'm working on a cheaper interface using cheap opto-couplers, I need some clear nights to test it !.
It can fit in a case and leave enough space for a RTC.

[gordon77]

Finally a clear night and I got some testing done, the new 'cheaper' interface worked well with my NEQ6.

The output of the opto-couplers doesn't go to 0 ohms like the opto-relays but worked fine.

If you are in the UK then Maplin have the ILQ74 as part number YY63T, and an alternative to the IL74 is a 4N25, part number AY44X.

As usual all at your own risk but I have tested it on my equipment.

Gordon

[blueridgedog]

Is there a git repository for this? I would like to get the current version. Gordon mentioned that it has full resolution capture and that is what I am looking to find with a preview window. The target user has an expensive guiding mount that is permanently setup in an observatory and is not looking for guiding, but wants the Pi for simple astro photography using image stacking post processing.

Thanks.

[gordon77]

I will be uploading the latest version very soon, just a few minor updates / bug fixes. Sorry no git yet.
To capture full res just set as required eg exp time, iso etc and click 'pic cap' button, for multiple shots click on 'con cap' and will save every frame at the size of the screen view. The screen view by default is 640 X 480, you can increase it ( if using a HD display try setting 'Display = 2' and 'Image_window = 5' at the start of the program) , and it can be a reduced res or upto a cropped full res dependent on the zoom setting.

If you have any suggestions for changes / additions let me know.

Gordon

[gordon77]

Version l.

- added a countdown timer to show the PHOTO (DSLR) progress
- various adjustments to make it run smoother if using long Exp Times, upto 6 seconds.
- added an 'Esc' button, if using long Exp Times if doesn't appear to always detect you trying to close the window.

Updated to Version m.
I found an error when testing, setting Threshold by clicking on graph didn't work, and put large black box on keys when exiting Graph if using Display = 2.

Gordon

[Hummer]

Hi All,

Has anyone using this autoguider had success using a monochrome camera instead of the PiCamera?
I am looking to improve my setup which currently uses a Pi2 and the PiCamera. Hoping someone can suggest a monochrome camera that is more sensitive to faint light?

Daniel
dpollit@rogers.com

[gordon77]

I can get my Philips SFC 900 webcam to connect on USB, a popular webcam with astronomers, but I haven't managed to work out how to control it except for Brightness.

Anyone know how to ? Maybe Opencv ?

I will be limited to 640x480 (zoom level 2).

Gordon

[MikeDunn]

Hi Gordon,

I'm expecting a new RasPi + the Touchscreen in a few days (tomorrow with luck), and was wondering if you've been able to test/verify your app etc with this config ?

Mike

[gordon77]

Hi Mike,

I don't have one of the new Pi screens, only a 800x480 HDMI screen (non touch) which is the default setting.

I'd be interested to know if it works OK.

Gordon

[MikeDunn]

Well,

Assuming it turns up tomorrow, will give it a try over the week-end !

Mike

[gordon77]

PCB (veroboard) layout

[MikeDunn]

OK, it arrived while I was out, and I did the assembly yesterday; have tried the app this evening, with mixed results ...

First, let me say that I'm doing this in Testing mode only, as I haven't got a camera yet (trying to find some guidance on whether to get the classic camera or the Noir version ... anyone here got any recommendations, or can point me to a thread on what's best ?)

So - the good bits

• Well - it works So that's a good start !

The bad bits

• Half the settings are 'lost' off the side of the screen
• App resolution - the official screen doesn't follow the default config in the app, nor any of the other defined sizes, so no easy change
• Can't resize the window 'on the fly' by grabbing a side & pulling

Now, the first & last are likely of no consequence if the middle can be easily addressed. While I see that I can change the display settings, it's not so clear what needs to be modified. I am assuming that

Code: Select all

Display = 0

should change to

Code: Select all

Display = 2

Now ... given that change, I assume that

Code: Select all

Image_window = 5

also needs to be modified - but to what ? The official screen is 800x480, which doesn't appear in any of the options, and I am unsure I see where I can define such a size ? Is it in the

Code: Select all

if Display > 1:

then that seems to put the screen to 1280x960 ? Or am I misreading this part of the code ? The default is 840x480, so it's (frustratingly) close

So I don't know what needs the change or where ... Given that this screen is now out, and likely others will be interested in using it in this fashion, how easy is it to define a new mode for it, maybe as a new Display or Image_window option that can be quickly & easily selected in the code ?

Mike

[gordon77]

Try display =2 and image_window = 0 or 1 to see what you get.

Display 0 should give 640 + 192 = 832 which suits my screen. Is the pi screen exactly 800 WIDE?

[MikeDunn]

That's what all the blurb says ...
Pimoroni
Amazon
and of course RasPi themselves

Re the screen change; Image_window = 0 gives the smaller window, but has a black bar down the right side before the buttons, about the width of the bottom two buttons (maybe a little wider) but also loses everything under the text "scale E" and "P-Count", those buttons seem to be half-depth; using 1 gives the same bump-in and black bar, but gives buttons to "scale W", "plc cap" and "scr cap" - nothing under them.

Reverting back allows the entire set on the VNC session, but can't be seen properly on the Pi

[gordon77]

What does display=1 show?

[MikeDunn]

With Image_width = 0, I get the buttons at the bottom - depth of 5 via VNC but I lose the bottom 2 rows on the screen

Image_width = 1 gives the same No discernible difference

[gordon77]

All a bit baffling.

So the best is display =0 but at present you lose 1/2 of the right hand buttons eg 32 pixels?

[MikeDunn]

Pretty much !

Will see if I can take a photo & post tomorrow ...

Cheers for your help !

[gordon77]

That will be good, and l'll see what l can try.

[gordon77]

Try this , will hopefully fix the Pi display.

You can change the picture width in the section starting with 'if display == 0', I have set 'width = 608' to lose 32 pixels.

I am not sure about VNC I have never used it.

Gordon

[MikeDunn]

Cheers for that ... we're getting somewhere ...

The good news is - I get more icons; the bad news - not them all. However ... I modified the width parameter to 560 and it all fits in Now, how does that add up to an 800 wide display ...

Checked vs the VNC session - and I'm not getting the bottom set of icons Didn't notice that originally, it was the right-hand side that grabbed my attention At the default setting I don't get any icons under the "Dec S S Stop S" row ... changing to 400 made it worse

So ... what can I modify now

[gordon77]

On my display I remove the pygame top banner, right click on the banner and choose 'un-decorate'.

Does that help ?

I also modify the GUI task bar...
Right click on the task bar..
Choose Panel Settings
Under Geometry: set Bottom, Left, Width 100%, Height 25 pixels, Icon Size 25 pixels
Under Advanced: tick Minimise when not in use, and set size when not in use to 2

Note the bottom half of the R1,R2,R3,S1,S2 and S3 keys will always be off the screen when using a 480 height screen, but I think its usable..

Gordon

[MikeDunn]

Well ... that was an interesting few minutes !

A little earlier today, while browsing the touchscreen forum, I cam across someone having the same problem I was on the touch aspect being offset a bit; added a post there, & moved on. Checked the reported screen res & noticed that it wasn't showing 800x480 as it should be Did a post on that too ... Turns out ... overscan was (somehow) on So turned it off, rebooted & lo and behold - proper resolution. Not only that, but the touch was now at the right point

That brings me back here ... Have done the task bar (that saves a little real estate ) and have also removed the top banner (had to plug my keyboard in, before remembering a post on forcing a right-click - now enabled ). So now I get the full set of buttons to the side and to the bottom (just !) - top banana ! And just to be awkward - I get a little real estate either side I need to fix Now ... what was that width again ? Oh yes ... 600

Mike

[gordon77]

I'm pleased you've solved it.

Was it 608?

[MikeDunn]

Settled on 600 but I can add another 8 & see

Got the plumber in atm (don't ask ... ), will see if I can when he leaves ...