PiAstroHub: RaspberryPi for Autoguiding+DSLR+GOTO
Posted 15 August 2013 - 11:27 PM
Posted 03 September 2013 - 08:36 AM
I finally managed to get lin_guider up and going but it seems to be over agressive in its adjustments
I am experiencing the same over-aggressiveness with lin_guider on my non-oc'd Pi.
Did you progress in any way on this issue?
Posted 16 September 2013 - 10:27 PM
Posted 26 September 2013 - 10:59 AM
I just learned about HitecAstro which prompted to look further into this.
Posted 27 September 2013 - 12:37 AM
Posted 30 September 2013 - 05:57 PM
and since the RaspberryPI has it's own GPIO onboard then this eliminates the requirement for the USB Breakout. Which appears (I'm NOT an EE) that I can go direct to a Darlington Array then RJ12 for the ST-4. Neat. (however I'm not sure where the ASCOM drivers will come into play then - can I use the ASCOM Drivers to own the GPIO's on the RPi?)
I'll check to see if the MK808 has GPIO pins later tonight.
I'll need to reread this thread to see if the RPi was ruled out mainly due to perf as I'd love to see your findings on that. Was it the web page side or the webcam side?
Posted 30 September 2013 - 10:32 PM
For USB-GPIO, this MCP2200 based can be a good solution, so long as astro programs would support the MCP2200 driver:
Posted 30 September 2013 - 10:51 PM
I will definitely put a real heatsink and active-fan to cool it. Little or no heatsink on them, IMO, is a joke.
Posted 01 October 2013 - 10:03 AM
So, MK808 with the original wifi (RK901) is the only one that would work as an access point. For the speed, the difference between RK3066 and RK3188 is not much. The plate-solving time is about 12 sec (RK3188) vs 15 sec (RK3066) while it takes more than 3 mins in Raspberry Pi.
Posted 02 October 2013 - 07:14 AM
MK808 (RK3066 dual-core) 91667
CX919 II (RK3188 quad-core) 161713
Re: use TV stick's WiFi in AP mode
Nowadays, most of them are using Broadcom based chipset (thus no AP, unless using an external WiFi USB dongle).
Posted 02 October 2013 - 10:06 PM
I believe Linpack only exercise the CPU portion of the RK3000 series SoC devcie, never exercise the GPU. Thus the result is in MFLOPS.
Of course, it's just a raw estimate of CPU capability when the program is assumed to be designed as multi-threaded and efficiently using the multi-core CPU. It does not consider memory optimization etc. in real-life calculation.
But since Linpack is for linear algebra, I think it could be a close approximation on RK3000 SoC's potential.
BTW, I've only tested the RK3066 Linux once but never on RK3188's. Don't know if the kernel has been optimized for its 4-core CPU.
BTW2: Antutu (most recent version) for Android benchmark score:
RK3066: (2x 1416MHz CPU): 13027
RK3188: (4x 1600MHz CPU): 18698
Posted 15 October 2013 - 08:37 AM
Can you tell us what is the minimum setup which is necessary to be able to auto-guide with a modified SPC900 webcam ?
And can you tell us why the new devices with RK3188 and new wifi chips can't create a reachable ad'hoc network ?
Is the problem on the linux side or the android (or IOS) side ?
Posted 15 October 2013 - 08:30 PM
To autoguide with a webcam, you will need
1) An Arm linux device (Raspberry Pi, MK808, ...)
3) GPUSB to send the correction signal
4) Linguider 2.9 which should be released soon.
I will need to slightly modify my codes to work with this new version. This version will support QHY5L-ii and GPUSB.
About the wifi connection, I tested only the AP mode (not the adhoc mode) because most of Android devices cannot make an adhoc connection with the stock ROM. So far, MK802iv (older version which uses RTL8188 wifi chip) works nicely but the wifi chip was changed to AP6210 after July 2013. I am not sure if AP6210 works in the adhoc mode or not.
The AP6210 hardware supports the AP mode because we can create a hotspot when the RK3188 device runs Android. It is definitely about the driver. So far, the source code for the wifi chip is not available.
I attach the photo showing my complete field setup.
Posted 15 October 2013 - 08:37 PM
You see the USB hub under the MK808. 4 USB cables are
1) Usb serial cable + serial cable to the mount
2) Cable to QHY6 for autoguiding
3) DSLR usb cable to download images
4) DSLR bulb shutter cable
The MK808 also works as the access point to accept connection from a mobile device. Then, an iOS or Android tablet can control all devices from a web browser. It is that simple
Posted 15 October 2013 - 11:09 PM
Ils there enougth debit on the unique USB socket for all the signals ?
Posted 15 October 2013 - 11:38 PM
Posted 15 October 2013 - 11:48 PM
Posted 16 October 2013 - 12:26 AM
Look for the file dslr_getphoto.sh in www.zip
You can put the upzipped folder as /home/pi/www. You will see the interface if opening the html file.
Posted 16 October 2013 - 01:33 AM
But you take only jpeg photos and not raw ones ?
Is the www folder content a server to run on raspberry or MK808 ?
Posted 16 October 2013 - 01:44 AM
You will need to follow the installation process in Readme. You can start with steps 1-7 if you want to use only the DSLR. Please recompile all .c files if you run it on RPi:
gcc xxx.c -o xxx
All C binaries were compiled for RK3066.
Posted 17 October 2013 - 10:29 PM
I am very impressed with your project.
I definitely would like to try iAstrohub but in my country, QHY5 and 6 are not available anymore. I understood I need new version of lin guider for QHY5-II. Do you have plan to release new version including new version of lin guider?