×
INDI Library v2.0.7 is Released (01 Apr 2024)
Bi-monthly release with minor bug fixes and improvements
Raspberry Pi HQ Autoguiding?
- Marc Carrier
-
- Offline
- New Member
-
- Posts: 3
- Thank you received: 1
- Marc Carrier
-
- Offline
- New Member
-
- Posts: 3
- Thank you received: 1
- Kevin S Snedden
-
- Offline
- New Member
-
- Posts: 4
- Thank you received: 0
- David Dufres
-
Topic Author
- Offline
- New Member
-
- Posts: 11
- Thank you received: 1
Replied by David Dufres on topic Raspberry Pi HQ Autoguiding?
Am revisiting the idea this weekend - had dropped it as my RPi4 died and I had moved to another SBC (NanoPC T4) that is hardly drop-in compatible to the Rpi camera lineup.
However, am currently having worse and worse performance from my T7C, I found a solution to both the NanoPC compatibility and inconsistent pi cam support in INDI:
www.davidhunt.ie/raspberry-pi-zero-with-...amera-as-usb-webcam/
It’ll use a 10$ Pi Zero to turn the Pi Cam HQ into a USB UVC webcam. From there, it should JustWork (TM). I gain almost 100% sensor size, going from 1/3.2" to 1/2.3", smaller pixel size even with 2x2 binning and faster bandwidth. Down the road, also possibility of bluetooth connection if needed (although then still need to power the Pi Zero which is powered via usb otg anyway) and to add other pi-compatible sensors (thinking GPS/temp/humidity). Funnily, Arducam sells a picam-to-uvc board, for 100$. Here total cost will be 12-13$ (board + small SD card).
To be continued soon
However, am currently having worse and worse performance from my T7C, I found a solution to both the NanoPC compatibility and inconsistent pi cam support in INDI:
www.davidhunt.ie/raspberry-pi-zero-with-...amera-as-usb-webcam/
It’ll use a 10$ Pi Zero to turn the Pi Cam HQ into a USB UVC webcam. From there, it should JustWork (TM). I gain almost 100% sensor size, going from 1/3.2" to 1/2.3", smaller pixel size even with 2x2 binning and faster bandwidth. Down the road, also possibility of bluetooth connection if needed (although then still need to power the Pi Zero which is powered via usb otg anyway) and to add other pi-compatible sensors (thinking GPS/temp/humidity). Funnily, Arducam sells a picam-to-uvc board, for 100$. Here total cost will be 12-13$ (board + small SD card).
To be continued soon
Please Log in or Create an account to join the conversation.
Replied by Outta on topic Raspberry Pi HQ Autoguiding?
- Dash Black
-
- Offline
- New Member
-
- Posts: 5
- Thank you received: 0
- Dash Black
-
- Offline
- New Member
-
- Posts: 5
- Thank you received: 0
- Dash Black
-
- Offline
- New Member
-
- Posts: 5
- Thank you received: 0
Replied by Dash Black on topic Raspberry Pi HQ Autoguiding?
I went ahead and installed Astroberry, installed all 3rd party drivers, ran the code you suggested in the other thread and... still crashing 
I'm totally at a loss for what to do.
I'm totally at a loss for what to do. Please Log in or Create an account to join the conversation.
- Dash Black
-
- Offline
- New Member
-
- Posts: 5
- Thank you received: 0
Replied by Outta on topic Raspberry Pi HQ Autoguiding?
Hi Dash,
First of all please use EDIT button
you do not have to post a new post for every update if you are latest poster. It will be easier for other people to find helpful advice if there is not too much clump.
I know my guide is not the best in details but I wrote it on mobile phone not on PC so it is a bit harder to do it properly
For this either mkdir and upload my code to that folder, or change path in script to location where code is. If you are familiar with GIT github.com/indilib/indi-3rdparty there is guide how to clone it in repository, and then you can overwrite ~/Projects/indi-3rdparty/indi-rpicam with code you have in other thread. i linked above, or manually do changes from this thread.
That is good, from moment it started working for me it did not crash not once, except it lags for 15 seconds when downloading Full Res image from DSLR. I solved that by extending connection timeout in PHD2 to 30s but that is not related to driver it is due to DSLR, RPI bus and processing power.
You can confirm that edit of the driver is working if default resolution is 2028x1520 and not 4056x3040. Also pixel size should be 3.1x3.1
First of all please use EDIT button
you do not have to post a new post for every update if you are latest poster. It will be easier for other people to find helpful advice if there is not too much clump.I know my guide is not the best in details but I wrote it on mobile phone not on PC so it is a bit harder to do it properly
For this either mkdir and upload my code to that folder, or change path in script to location where code is. If you are familiar with GIT github.com/indilib/indi-3rdparty there is guide how to clone it in repository, and then you can overwrite ~/Projects/indi-3rdparty/indi-rpicam with code you have in other thread. i linked above, or manually do changes from this thread.
That is good, from moment it started working for me it did not crash not once, except it lags for 15 seconds when downloading Full Res image from DSLR. I solved that by extending connection timeout in PHD2 to 30s but that is not related to driver it is due to DSLR, RPI bus and processing power.
You can confirm that edit of the driver is working if default resolution is 2028x1520 and not 4056x3040. Also pixel size should be 3.1x3.1
Please Log in or Create an account to join the conversation.
Time to create page: 1.197 seconds
© 2003-2022 by INDI Library. All rights reserved.