Vulisha

That is a limit induced by chip, but since mount is alt-az, longer do not have much sense.

It is not out yet, I have preordered it long time ago, there is a thread for it here:

I am using Ekos/Indi/Kstars on my. astroberry (Same thing basically, Kstars is a skymap, indi is driverbase like ascom, ekos is suite for capturing, plate solving and much more, but they are all in one app, you start it all from Kstars) I saw NINA and it is beautifull peace of code, but it is currently limited to windows due to. net framework. Hopefully it will be transfered to dotnet core and dotnet Maui so it will be usable on Linux as well.

Indeed result is not bad, but it has a lot of spherical aberation maybe some blend ti reduce f ratio will help with that.

And mind you, do not forget that you can always use binning, to increase size of your pixel. You can even use it in post-processing if you see tracking errors

Concider PlayerOne Uranus C, as it has passive cooling, and active can be bought as addon. Same sensor. 533 would probably be better due to bigger sensor, but regarding capability 585 has same chip performance as I investigated

Not my gallery unfortunately, but indeed very impressive. I do not own Redcat or iOptron. Not that I would mind owning it

I mean on guy in thread on forum, not HubblePi guy, I was aware of hubble pi since I started but it did not fit to my plans.

Hi Frostice I have it running. Even made RpiCamerax2 driver with hard-coded binning to make it useful for guiding. It is capable of capturing long exposures, and as guiding camera. Unfortunately it is not best choice for planetary imaging. You must be sure that you are not using it with dtoverlay=imx477, that will make camera use new libcamera api, and you are interested in legacy, mmal, implementation that is used in Rpi Camera driver in INDI. Can you share your /boot/config.txt and this command astroberry@astroberry:~ $ v4l2-ctl --list-devices bcm2835-codec-decode (platform:bcm2835-codec): /dev/video10 /dev/video11 /dev/video12 /dev/video18 /dev/video31 bcm2835-isp (platform:bcm2835-isp): /dev/video13 /dev/video14 /dev/video15 /dev/video16 /dev/video20 /dev/video21 /dev/video22 /dev/video23 mmal service 16.1 (platform:bcm2835-v4l2-0): /dev/video0 rpivid (platform:rpivid): /dev/video19 a stroberry@astroberry:~ $

Well firstly I would like to thank you on link to that thread I will do my best to help that person. Indeed while RPi HQCamera cannot match true Astrophotography cameras of new generation, it is not at all that bad, see samples below, I will upload a few. For long exposure is quite acceptable, unfortunately for planetary imaging you are limited with NDA. I was hoping my hands would be free but they are quite in chains. It is not that sensor(s) are not capable, opensource software ended being megaclosedsource under probably million dollar NDAs. IMX462 would preform brilliant, if I had options See rest of the images here: https://terramex.neocities.org/astro/index.html

I want to share my story with you how I decided to create my own astronomy camera. Disclaimer: typing on phone so expect typos! Disclaimer#2: big block of boring text, you can simply jump to conclusion on the end. How it started! It all started with me not liking to pay for a sensor and even more SoC that will be outdated when I can buy only sensor and plug it in my own SoC, and then change sensor as I please or need. Best cameras now have 256 or 512MB of ram, while RaspberryPi has 1GB up to 8GB. Jackpot isn't it? No, it is not! So my journey started with buying Rpi 3B+(~50usd) and V1 camera, just to test will it work, as that camera is few dolars. I was able to connect it to indi and get image. That was enough for starters and then I decided to order RPI High Quality camera with IMX477(50gbp+25%tax). RaspberryPi HQ Camera Initially Linux V4L2 for HQ Camera do not work as expected. There are no gain or shutter speed controls. Luckly there are dedicated INDI drivers for RPi HQ Camera. Unfortunately I spent days to decipher how to enable "long exposure mode" It is done by capturing first image of 10s and second of 15s. RpiHQCam can take 230s exposure and that is not half that bad and can capture decent astrophotography images. Cam has small pixels, has a lot of read noise, and too high resolution for guiding. So I had to modify drivers to add binning and for guiding, it is not bad, works, it has small delay(1-2s) for download but usable, and more than enough sensitive. Dead Rpi... Then my RPI died and I had to buy new one, during shortage, Pi 4b 1gb(60 eur + power 15 eur). Planet season! Then the planet season came, and problems came as well. Indi driver does not support streaming, so no luck in high speed imaging using INDI but never mind I can use console! There are two implementations of drivers for HQ Cam, legacy that is used by INDI and focuses on gpu, and Libcamera, that focuses on cpu. But bith of them use kernel driver that has only 4 modes fullress at 10fps, 2x binned at 40 and 50fps, and 4x binned at 120fps. 120fps is more than fine, but 4xbinned is not good. Driver does not support Analog crop, so changing region of interes and resolution does not effect FPS at all. So me being software developer I decided to rewrite kernel drivers. I am software developer! So I planned to add Analog crop and dynamic FPS that will increase based on resolution. I will not bore you with details at this part, but I failed miserably. Almost all of the registers are locked under Sony NDA, and I tried to reverse engineer thst stuff but it is a no, if you cannot get documents under NDA, just forget about it. You can be greatest developer, let alone me, no luck there. Rpi engineers have this in mind, but reluctant to confirm they will implement it. Arducam to the rescue I heard about Arducam and I saw they have IMX462, great little chip. So. I ordered that as well, 50USD+25%tax. And ended up limited there as well it has only single mode 60fps at fullhd. ROI is not implemented, neither are other modes. As Arducam can do something per request I asked them to add 720p at 120fps unbinned. They responded that minimum order quantity is 1000 chips for that change Then I discovered that IMX290 and IMX462 have same registers, but max implementation is again fixed 60fps. Settle as 60 fps OK fine, I will settle with 60FPS, not so bad right? Indeed not so bad. I decided to go with that. As Arducam supports only newest RPI OS Bullseye my Astroberry is not supported so I needed separate raspberry pi. So I bought another one, 8gb version(100 eur), shortage, only model available. Next issue I had was saving speed and my sd card was not fast enough. So I bought SSD(40eur) and USB 3.0 dock(10eur) that doesn't work at USB 3.0 port on Rpi if you use wifi. Something with cable and interference so I plugged it to usb 2.0. Start to record! There are two modes to record raw using console. Libcamera-raw, where you have to know bayer matrix, and libcamera-vid - -codec yuv420 where ffmpeg converts video to something usable. Unfortunately arducam has bug with yuv420 unable to convert it, while same procedure for imx477 works perfecy, and no one responds on my issue reported so first night of imaging can go to trash. Second day of imaging using raw, also can go to trash as I have failed to convert it to something usefull, no one from arducam responds. How about long exposure Arducam IMX462 is limited at 15s long exposure, so.... anyone wants to buy IMX462? Ending costs Rpi3b+, Rpi4b1gb, Rpi4b8gb, Imx477, Imx462, ssd and dock roughly sums up to 450 eur with taxes. Player One Mars II costs ~250 eur with taxes(there was a sale) , can take 2000s long exposure, goes over 200 fps, and I think it has passive cooling(or that is next one) . Additional hardware limitations Now even more boring part. You are not only limited with software. You are limited by hardware as well. Rapsberry Pi has two MIPI CSI-2 Lanes available for camera, that is roughly 2GBPS that limits max speed to raw resolution multiplied by bits of mode, all in all 2gbps cannot handle fullhd at 120FPS, USB3.0 cameras have 5GBPS. This can be worked around by buying RPi CM4, that has 4 lanes for camera so 4GBPS. Conclusion! Well it could all come just to this. Even if you have good technical knowledge, and you have good will, and time you are limited by NDAs, software and hardware limitations. Save your self a trouble and just buy what needs to be bought. Anyone wants to buy one rpi and Arducam 😂 Not to be only bearer of the bad news, these mages were captured with HQ Camera and Mak 127.

I saw it, and they only image without infrared filter, that kicks colors out bit it is good for low quality skies. I am interested in real color imaging for galaxies. Luckly they will add 1.55 filter adapter, so you can add any filter you want. Also neat trick will be putting it oj tripod so it acts partially as eq mount to reduce field rotation, hopefully

I have opened this thread while it was only kickstarter but thread was deleted for some reason... I backed this invention and I beleive it will be something if they make it properly. It is basically cheapest goto setup. Perfect for introduction to astronomy and perfect travel device. If results as bellow are possible it could be top item! Small lens does not mean bad performance, this has been imaged with Meopta Anaret 20/90mm, f4,5 @f5,6 which is effectively 16mm... with EOS500D https://flic.kr/p/2i7sSmr and

Thanks vlaiv, so basically higher fps is way to go! Unfortunately my camera (RpiHq camera) does not support ROI as it is. It has few modes 3040px@10 fps, 1520px@40 fps, 1080px@50fps all 12 bit and 990px@120fps and ROI is only helpfull for saving speed if disk is not fast enough, sensor is limited for some reason and cannot go above hard-coded values.

Just to jump in, for planetary imaging difference between 10bit and 12 bit. With my camera I can image 10bit at 120fps, and 12bit at 50fps. Which is the better option?

Dear friend it is perfectly possible to use Your DSLR - Eos 2000D Not so expensive lens - samyang 135 f2 EQ3 Mount - motorised And end up as NASA APOD winner! How do i know? Look at this APOD: https://apod.nasa.gov/apod/ap220405.html and now check the equipment: https://www.astrobin.com/id3tq9/ Indeed it is 22H of collection, and probably lot more of editing, but it is possible.

What is the setup?

It is pretty low for me as well it is at 23 degrees and it is pictured from very light poluted location, but luckly not a lot skyglow as sea is at south. Single frame attached, debayered, one is "raw", second is photometric color calibrated to remove green glow.

OnStep is a computerized goto system, usually for stepper motor equipped mounts though any step/dir interface motor driver (including servo) should work. There's a telescope hand controller App for Android (free in the Google Play Store,) an option to control through a website (Smart Web Server,) and a dedicated physical hand controller (Smart Hand Controller.) Or, on a PC there's ASCOM and INDI drivers for control. These options allow you to setup and control OnStep using a wide range of software including my Sky Planetarium, Cartes du Ciel, Stellarium, SkySafari, KStars, PHD2, etc So in short, buy a kit with board and stepper drivers. Buy Steppers, recommended from wiki are 400 step from omc-steppers, belts and gears and power supply. Also 3d printed motor mounts would be good. Then you need to do a hardest part, configure onstep per your mount specifications, and upload firmware using something like Arduino IDE, and you are set https://onstep.groups.io/g/main/wiki My full setup costed me ~100€ but before all this chip and similar crysis.

Indeed, you need a bit more integration time but field is flat, and optical quality is great, aberration free, only issue is bit off vignette on such a big sensor, fixed by flats and background extraction. Only prerequisite is good mount to handle big fl, which I do not have

Think about setting up OnStep, it requires a bit of work but you can get marvelous results!

Little of atypical imaging, deep space with Mak Edited with Siril and Lightroom I planed to get more exposures but ended up only with 29x300. 29x300s 127/1500 MAK EOS 550D 60/330 guidescope Rpi HQ Cam guidecam EQ5 Onstep

Manually set IP address and network mask on both devices. How would I set it up: Set your PC lan to 192.168.1.2 Set Astroberry to 192.168.1.3 Set both Network Masks to 255.255.255.0 (or /24 after ip) Ping using Cmd/Terminal devices to make sure it works.

Oh, so they probably are different makes sense if you think about it. Well ED80 is my dream scope but it is way out of my budget even without proper FF. When I saw this RC in 6" I would expect 5" to be even less expensive and somewhere upto 500 eur. And that would be my limit. So if I understand your calculations correctly mak 102/1250 would be ideal for 3x binning on 550D? lockquote widget

So I got a guy that I took telescope to for colimation as I was not able to get good resolution on planets, so I was sure I was doing bad colimation as I do not have laser, only camera, but he took a look through it and he said that miror is basically hyperbolic and not parabolic and that colimation is good but what i got is maximum I can get out of it as mirror is less than average. Regarding FoV I am aiming for roughly ~1-1.5° so I can fit M81, Sombrero, Leo triplet and planetary nebulas, small and large. 800mm FL was some "minimum" and 1200mm would be "maximum" I believe. @fireballxl5 I do have OVL FF for APO, would that be theoretically usable?