Jump to content


Photo

PiAstroHub: RaspberryPi for Autoguiding+DSLR+GOTO

  • Please log in to reply
508 replies to this topic

#51 anat

anat

    Viking 1

  • -----
  • Posts: 686
  • Joined: 03 Jun 2004

Posted 09 April 2013 - 01:42 AM

Hello all,

I have tested my all new raspberrypi to drive my orion atlas mount using skysafari. It works very fine. But the 2 usb ports are occupied one by the usb wifi dongle the other by the Raspberry which handle the mount. To answer a question I have seen somewhere: the handle is needed to make it works.
So there is no other room to connect a cam.
The amount of the installation to drive an Orion Atlas mount is as follow:
raspberry B 42€
box for rpi 10€
wifi dongle 10€
usb/RS232 14€

for a total of 76€ (100$) which is the half price of the skyfi orion device (in Europe).

Unfortunately I have read somewhere that the usb inteface is unique and the 2 plugs share the same interface. So there is nothing to wait in term of performance. But maybe it is sufficient for autoguiding.

Anat you are true, the MK808 looks to be a better alternative, wifi, bluetooth are included in device. But unfortunately there is only one usb plug. It would have been fun to make acquisition with the same device as the one that autoguide and drive the mount. But it seems not to be done even with the MK808.


Congrats for the Skyfi setup !
Both Raspberry Pi and MK808 works with a powered usb hub. In my setup I use:
QHY6 for autoguiding
QHY8L or DSLR for image capturing
USB-serial adapter for mount control
USB sound adapter
connected to a hub without any problem.

#52 anat

anat

    Viking 1

  • -----
  • Posts: 686
  • Joined: 03 Jun 2004

Posted 09 April 2013 - 01:45 AM

Anat, I have a question for you, what you done to successfully compile GoQat on the raspberry.
Thanks for your answer.


These are steps to compile GoQat:
sudo apt-get install gawk
sudo apt-get install libgtk2.0-dev
sudo apt-get install libgoocanvas-dev
sudo apt-get install libxpa-dev
sudo apt-get install saods9
sudo apt-get install grace
sudo apt-get install libunicap2-dev
sudo apt-get install autoconf

>>> Install GoQat
tar -xvf goqat-0.9.8.tar.gz
cd goqat-0.9.8
./configure
make
sudo make install

#53 anat

anat

    Viking 1

  • -----
  • Posts: 686
  • Joined: 03 Jun 2004

Posted 10 April 2013 - 03:16 AM

I am ready to release the source codes. Thank all testers and developers for your support.

https://sourceforge....ects/iastrohub/

Now a tablet can control the autoguider, CCD, DSLR, and mount via a tiny hub :) I recommend MK808 (original with RK901 Wifi chip).

Best regards,
Anat

#54 pfile

pfile

    Gemini

  • -----
  • Posts: 3163
  • Joined: 14 Jun 2009

Posted 20 May 2013 - 10:56 PM

so have you tried openPHD again? it seems like they have made a lot of progress recently.

#55 anat

anat

    Viking 1

  • -----
  • Posts: 686
  • Joined: 03 Jun 2004

Posted 21 May 2013 - 04:14 AM

I have never tried openPHD after using Linguider. Linguider is super fast on Arm devices.

#56 pfile

pfile

    Gemini

  • -----
  • Posts: 3163
  • Joined: 14 Jun 2009

Posted 21 May 2013 - 07:29 PM

i'll check it out. just browsing thru the files you've uploaded, it seems like mount control is done thru CdC with the INDI interface, is that correct?

#57 Raginar

Raginar

    Fly Me to the Moon

  • *****
  • Posts: 6138
  • Joined: 19 Oct 2010
  • Loc: Rapid CIty, SD

Posted 24 May 2013 - 09:07 AM

Can it control an SBIG camera?

#58 pfile

pfile

    Gemini

  • -----
  • Posts: 3163
  • Joined: 14 Jun 2009

Posted 24 May 2013 - 12:28 PM

i have been looking into this - i don't think so. however, hacking in sbig http support might be "easy", but that only works on STT and STX cameras.

i think the main problem is that INDI is way behind ascom. maybe these little single-board computers will change that though.

#59 Raginar

Raginar

    Fly Me to the Moon

  • *****
  • Posts: 6138
  • Joined: 19 Oct 2010
  • Loc: Rapid CIty, SD

Posted 25 May 2013 - 09:48 AM

Darn. I'm sure hacking in an HTTP server wouldn't be too bad. I just find SBIG's lack of an ASCOM driver to be a real PITA.

#60 pfile

pfile

    Gemini

  • -----
  • Posts: 3163
  • Joined: 14 Jun 2009

Posted 25 May 2013 - 05:36 PM

well, it's easier because it's an http client. it could probably be done with a perl script, actually.

and libcurl is really good for getting http support into a program... like phd.

what does an ascom driver buy you for a camera? meaning, are there camera control packages out there that only interface with ascom-compatible cameras?

#61 pfile

pfile

    Gemini

  • -----
  • Posts: 3163
  • Joined: 14 Jun 2009

Posted 25 May 2013 - 05:36 PM

p.s. what i am hoping is that these cheap, single-board computers will spark new interest in INDI...

#62 Raginar

Raginar

    Fly Me to the Moon

  • *****
  • Posts: 6138
  • Joined: 19 Oct 2010
  • Loc: Rapid CIty, SD

Posted 26 May 2013 - 09:58 AM

It buys me access to the self-guider :). And hopefully would provide me a way around using $500+ software to guide and image.

I wish I could use the Http server with my St-10.

#63 anat

anat

    Viking 1

  • -----
  • Posts: 686
  • Joined: 03 Jun 2004

Posted 27 May 2013 - 12:38 AM

i'll check it out. just browsing thru the files you've uploaded, it seems like mount control is done thru CdC with the INDI interface, is that correct?


Yes. A mount is controlled via INDI/CdC in the background.

#64 anat

anat

    Viking 1

  • -----
  • Posts: 686
  • Joined: 03 Jun 2004

Posted 27 May 2013 - 12:40 AM

Can it control an SBIG camera?


No because SBIG doesn't release libraries for Arm Linux. QSI can be controlled using QSI open library and GoQat.

#65 smartc

smartc

    Lift Off

  • -----
  • Posts: 8
  • Joined: 08 Aug 2010

Posted 09 June 2013 - 12:01 PM

Can anyone confirm Orion SSAG is working with lin_guider? I am trying to implement on my RPi, but can't seem to get lin_guider to recognize the SSAG.

It appears to be recognized in lsusb:

Bus 001 Device 005: ID 1856:0011

However, I get the following error messages when starting lin_guider:
[1370797037:231] ERROR: Unable to find config file '/home/pi/.config/GM_software/devconf3.conf'
using defaults
[1370797037:239] lusb::initialize(): Success
[1370797037:249] ERROR: qhy5_core_shared::open_device(): Could not open the QHY5 device
[1370797037:252] ERROR: Error opening device: qhy5: code=1

Just noticed the "config" file error now, so will do some more research, but what settings are you using in lin_guider to get the SSAG working?

Cheers,
Corey

#66 groz

groz

    Surveyor 1

  • *****
  • Posts: 1954
  • Joined: 14 Mar 2007
  • Loc: Campbell River, BC

Posted 09 June 2013 - 02:16 PM

ssag and qhy5 have different vid/pid. I dont have notes handy offhand, but, you probably just need to make it search for a different vid/pid.

#67 smartc

smartc

    Lift Off

  • -----
  • Posts: 8
  • Joined: 08 Aug 2010

Posted 09 June 2013 - 02:19 PM

Thanks... That had occurred to me as well, but I'm not sure how to do that... Any ideas where to start?

#68 smartc

smartc

    Lift Off

  • -----
  • Posts: 8
  • Joined: 08 Aug 2010

Posted 09 June 2013 - 09:38 PM

No dice in getting the SSAG working under Linux. I found one thread on another forum suggesting that you could reflash the EEPROM to make it mimic a QHY5, but that requires (1) Win XP and (2) willingness to mess with the hardware, neither of which are in the cards for me.

Am giving up on this for tonight and will be guiding with PHD on my MacBook for now... Will post an update if I can get it working. Still open to any advice from others who might have got this to work.

Cheers,
Corey

#69 anat

anat

    Viking 1

  • -----
  • Posts: 686
  • Joined: 03 Jun 2004

Posted 10 June 2013 - 04:18 AM

The SSAG works out of the box for me. Please download firmware from

https://sourceforge....files/firmware/

Then,

sudo dpkg -i firmware-ccd_1.0_all.deb

#70 smartc

smartc

    Lift Off

  • -----
  • Posts: 8
  • Joined: 08 Aug 2010

Posted 10 June 2013 - 07:37 PM

Should have let you know that I tried that on the weekend with no luck.

All that being said, I fired things up tonight and everything worked on the first attempt. Although I tried every iteration I could think of earlier (or at least I think I did), it is more or less working tonight. I say more or less because I'm getting the occasional read error message and the Pi seems to lock up after a few minutes. Not sure if the two are connected...

For what it's worth, I made a point of:

(1) Ensuring all peripherals were connected to a powered USB hub, and
(2) Ensuring the SSAG was plugged in before I booted the Pi.

The USB cable has always been a bit loose fitting on my SSAG and I also made triple-sure I had a good connection. (I normally tape the cable in place to prevent it coming loose when it's on the telescope.)

Beyond those things, I can't say I have any sage advice... Just glad it's working so I can move on to the next trouble-shooting activity!

Cheers and thanks to all for the help,
Corey

#71 anat

anat

    Viking 1

  • -----
  • Posts: 686
  • Joined: 03 Jun 2004

Posted 11 June 2013 - 01:09 AM

Please make use that your powered usb hub is one of those in the working list.
http://elinux.org/RP...fiedPeripherals

#72 Kris Large

Kris Large

    Lift Off

  • -----
  • Posts: 2
  • Joined: 27 Oct 2012
  • Loc: Hermiston, OR, USA

Posted 30 June 2013 - 08:17 PM

Can anyone confirm Orion SSAG is working with lin_guider? I am trying to implement on my RPi, but can't seem to get lin_guider to recognize the SSAG.

It appears to be recognized in lsusb:

Bus 001 Device 005: ID 1856:0011

However, I get the following error messages when starting lin_guider:
[1370797037:231] ERROR: Unable to find config file '/home/pi/.config/GM_software/devconf3.conf'
using defaults
[1370797037:239] lusb::initialize(): Success
[1370797037:249] ERROR: qhy5_core_shared::open_device(): Could not open the QHY5 device
[1370797037:252] ERROR: Error opening device: qhy5: code=1

Just noticed the "config" file error now, so will do some more research, but what settings are you using in lin_guider to get the SSAG working?

Cheers,
Corey


I'm at the same point smartc was as of this post. Using a supported, powered USB hub, installed the ccd firmware package. Any other suggestions?

#73 anat

anat

    Viking 1

  • -----
  • Posts: 686
  • Joined: 03 Jun 2004

Posted 03 July 2013 - 10:38 PM

Please use the command "dmesg" and post here. The camera should be assigned as QHY5 in dmesg logs.

#74 Kris Large

Kris Large

    Lift Off

  • -----
  • Posts: 2
  • Joined: 27 Oct 2012
  • Loc: Hermiston, OR, USA

Posted 04 July 2013 - 02:58 PM

Thanks for the response. I'm away from my RPi, but the SSAG wasn't recognized as QHY5 in lsusb, just showed up as
"Bus 001 Device 005: ID 1856:0011"

As I played with it, I modified the qhy5 rules from lin_guider 26, changed any vid/pid that said 1618 to 1856 and 0901 to 0011. Then re-ran qhy5_lg_install.sh. After that the device shows up as QHY VOTI in dmesg, QHY5 in /dev and appears to be working nicely. However, I suspect this isn't the best approach.

If you had a clean install of raspbian and installed "firmware-ccd_1.0_all.deb", your SSAG would be detected properly?

#75 groz

groz

    Surveyor 1

  • *****
  • Posts: 1954
  • Joined: 14 Mar 2007
  • Loc: Campbell River, BC

Posted 05 July 2013 - 09:00 AM

Your approach is ok. The qhy5 and ssag are indeed the same hardware, but, programmed with different vid/pid numbers. If you want your system to correctly recognize either variant, then adding more rules for the alternate id's would be the approach you need.






Cloudy Nights LLC
Cloudy Nights Sponsor: Astronomics