Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Orion Starshoot autoguider connection #32

Closed
GoogleCodeExporter opened this issue Jun 25, 2015 · 24 comments
Closed

Orion Starshoot autoguider connection #32

GoogleCodeExporter opened this issue Jun 25, 2015 · 24 comments
Labels
Priority-Medium Type-Defect

Comments

@GoogleCodeExporter
Copy link 

What steps will reproduce the problem?
1. start PHD
2. try to connect camera
3. choose either INDI or 4vl

What is the expected output? What do you see instead?
Expect to see camera working but only get 
INDI: failed to connect to indi server and 
problem connecting to camera
V4L: the camera does not show up on the list of cameras

What version of the product are you using? On what operating system?
KDE with kubuntu operating system
 PHD v.1.12.4
Please provide any additional information below.
I am a total linux newbie. I tried to download and install v4l and INDI and may 
not have done so correctly. The make of PHD went through finding all v4l 
requirements and compiled and made no problem. I don't think I got INDI working 
OK yet.

Original issue reported on code.google.com by brucer...@gmail.com on 21 Jul 2012 at 2:29
@GoogleCodeExporter
Copy link
Author 

Hi,
thanks for reporting this problem.
Need a little bit more information to help You, though ;-)

Could You please provide as much details about the camera as possible?
Fire up a terminal (i think it's 'kterm', haven't used KDE for a while), type 
'tail -f /var/log/syslog', then connect the camera and please post the output - 
this will give us a first indication of the type of problem you're facing.
It would also be nice if You could provide the build log from compiling PHD - 
it's easy to miss warnings, maybe You accidentally did not install all relevant 
libraries.
BTW, which Kubuntu release are You using?
Cheers,

Steffen

p.s.: I'm on vacation next week, i'll try to keep up with my emails, but can't 
guarantee it.

Original comment by steffen....@gmail.com on 21 Jul 2012 at 8:29

@GoogleCodeExporter
Copy link
Author 

using Konsol fired up tail then connected then disconnected. Here is output

bruce@bruce-HP-620:~$ tail -f /var/log/syslog
Jul 21 17:35:13 bruce-HP-620 kernel: [   71.613634] process `skype' is using 
obsolete setsockopt SO_BSDCOMPAT
Jul 21 17:35:21 bruce-HP-620 ntpdate[2213]: step time server 91.189.94.4 offset 
1.295949 sec
Jul 21 17:35:35 bruce-HP-620 nmbd[2221]: [2012/07/21 17:35:35.738790,  0] 
nmbd/nmbd_become_lmb.c:395(become_local_master_stage2)
Jul 21 17:35:35 bruce-HP-620 nmbd[2221]:   *****
Jul 21 17:35:35 bruce-HP-620 nmbd[2221]:   
Jul 21 17:35:35 bruce-HP-620 nmbd[2221]:   Samba name server BRUCE-HP-620 is 
now a local master browser for workgroup WORKGROUP on subnet 192.168.122.1
Jul 21 17:35:35 bruce-HP-620 nmbd[2221]:   
Jul 21 17:35:35 bruce-HP-620 nmbd[2221]:   *****
Jul 21 17:36:14 bruce-HP-620 dnsmasq[1309]: reading /etc/resolv.conf
Jul 21 17:36:14 bruce-HP-620 dnsmasq[1309]: using nameserver 192.168.0.1#53
Jul 21 17:36:55 bruce-HP-620 kernel: [  172.128118] usb 2-1: new high speed USB 
device number 3 using ehci_hcd
Jul 21 17:36:55 bruce-HP-620 mtp-probe: checking bus 2, device 3: 
"/sys/devices/pci0000:00/0000:00:1d.7/usb2/2-1"
Jul 21 17:36:55 bruce-HP-620 mtp-probe: bus: 2, device: 3 was not an MTP device
Jul 21 17:37:31 bruce-HP-620 kernel: [  208.359461] usb 2-1: USB disconnect, 
device number 3

Then hit ctl c then fired up tail again got:

^C
bruce@bruce-HP-620:~$ tail -f /var/log/syslog
Jul 21 17:35:35 bruce-HP-620 nmbd[2221]:   
Jul 21 17:35:35 bruce-HP-620 nmbd[2221]:   Samba name server BRUCE-HP-620 is 
now a local master browser for workgroup WORKGROUP on subnet 192.168.122.1
Jul 21 17:35:35 bruce-HP-620 nmbd[2221]:   
Jul 21 17:35:35 bruce-HP-620 nmbd[2221]:   *****
Jul 21 17:36:14 bruce-HP-620 dnsmasq[1309]: reading /etc/resolv.conf
Jul 21 17:36:14 bruce-HP-620 dnsmasq[1309]: using nameserver 192.168.0.1#53
Jul 21 17:36:55 bruce-HP-620 kernel: [  172.128118] usb 2-1: new high speed USB 
device number 3 using ehci_hcd
Jul 21 17:36:55 bruce-HP-620 mtp-probe: checking bus 2, device 3: 
"/sys/devices/pci0000:00/0000:00:1d.7/usb2/2-1"
Jul 21 17:36:55 bruce-HP-620 mtp-probe: bus: 2, device: 3 was not an MTP device
Jul 21 17:37:31 bruce-HP-620 kernel: [  208.359461] usb 2-1: USB disconnect, 
device number 3
Jul 21 17:39:27 bruce-HP-620 anacron[1085]: Job `cron.daily' started
Jul 21 17:39:27 bruce-HP-620 anacron[2558]: Updated timestamp for job 
`cron.daily' to 2012-07-21

then plugged in camera and got:

Jul 21 17:40:21 bruce-HP-620 kernel: [  377.860117] usb 2-1: new high speed USB 
device number 4 using ehci_hcd
Jul 21 17:40:21 bruce-HP-620 mtp-probe: checking bus 2, device 4: 
"/sys/devices/pci0000:00/0000:00:1d.7/usb2/2-1"
Jul 21 17:40:21 bruce-HP-620 mtp-probe: bus: 2, device: 4 was not an MTP device

then  disconnected camera:

Jul 21 17:41:08 bruce-HP-620 kernel: [  424.982058] usb 2-1: USB disconnect, 
device number 4


I don't know how to get a build log, so I recompiled with a redirect to output 
text files.

results of cmake . is:

-- Configuring done
-- Generating done
-- Build files have been written to: /home/bruce/open-phd-guiding-read-only

results of make is:

[100%] Built target PHD

results of make install:

[100%] Built target PHD
Install the project...
-- Install configuration: ""
-- Up-to-date: /usr/local/bin/PHD
-- Up-to-date: /usr/local/share/PHD/PHDGuideHelp.zip

Distributor ID: Ubuntu
Description:    Ubuntu 11.10
Release:        11.10
Codename:       oneiric


I have no idea if this helps. Really appreciate your time.

-Bruce

Original comment by brucer...@gmail.com on 21 Jul 2012 at 11:54

@GoogleCodeExporter
Copy link
Author 

I googled MTP devices and found I needed to install the following. So I did.

Commit Log for Sat Jul 21 18:09:06 2012

Installed the following packages:
gmtp (1.2.0-1)
libmtp-dbg (1.1.0-3ubuntu1)
libmtp-dev (1.1.0-3ubuntu1)
libmtp-doc (1.1.0-3ubuntu1)
mtp-tools (1.1.0-3ubuntu1)

after rebooting I ran tail as before. Lots of stuff upgraded. Then plugged in 
teh camera and got:


Jul 21 20:18:38 bruce-HP-620 kernel: [  751.272117] usb 2-1: new high speed USB 
device number 3 using ehci_hcd
Jul 21 20:18:38 bruce-HP-620 mtp-probe: checking bus 2, device 3: 
"/sys/devices/pci0000:00/0000:00:1d.7/usb2/2-1"
Jul 21 20:18:38 bruce-HP-620 mtp-probe: bus: 2, device: 3 was not an MTP device

then unplugged and got:


Jul 21 20:19:23 bruce-HP-620 kernel: [  796.630580] usb 2-1: USB disconnect, 
device number 3

Hope that helps.

-Bruce

Original comment by brucer...@gmail.com on 22 Jul 2012 at 2:23

@GoogleCodeExporter
Copy link
Author 

Hi Bruce,
thanks - yep, that helps a lot!
Ok, first of all - the installation of those 'libmtp' packages didn't hurt, but 
couldn't fix this issue either, sorry.
From the syslog outputs it's clear that the camera is not detected as a valid 
V4L device, otherwise there'd be output like this:

Jul 22 10:19:00 pangolin kernel: [ 1040.210591] gspca_sn9c20x: SOI968 sensor 
detected
Jul 22 10:19:00 pangolin kernel: [ 1040.210762] input: sn9c20x as 
/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/input/input14
Jul 22 10:19:00 pangolin kernel: [ 1040.211056] usbcore: registered new 
interface driver sn9c20x

It would be great if You'd simply plug in the camera, open a terminal, run 
'lsusb' and send the output (contains the Vendor and Product IDs of all USB 
devices)?!
Could be that the camera is a clone of a model that is already supported by 
Linux, then getting your camera to work isn't too hard.

Steffen

Original comment by steffen....@gmail.com on 22 Jul 2012 at 8:26

@GoogleCodeExporter
Copy link
Author 

lsusb with camera plugged in:
bruce@bruce-HP-620:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 05c8:0403 Cheng Uei Precision Industry Co., Ltd
(Foxlink)
Bus 008 Device 002: ID 1267:0210 Logic3 / SpectraVideo plc
Bus 002 Device 004: ID 1856:0011

lsusb without camera plugged in:
bruce@bruce-HP-620:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 05c8:0403 Cheng Uei Precision Industry Co., Ltd
(Foxlink)
Bus 008 Device 002: ID 1267:0210 Logic3 / SpectraVideo plc

If it helps, this is an Orion Starshoot Autoguider. Orion does not
have a linux driver for it. I got them to send me the source for their
Windows driver. I was thinking of hacking the Windows source for that
driver and creating a v4l driver out of it if things get desperate.
Thank you again for your time and trouble.

-Bruce

Original comment by brucer...@gmail.com on 22 Jul 2012 at 4:13

@GoogleCodeExporter
Copy link
Author 

Hi Steffen,

I know you are on holidays and it is summer. Any progress on this? A clone 
would be awesome if it is available.

Yours,

Bruce

Original comment by brucer...@gmail.com on 30 Jul 2012 at 11:27

@GoogleCodeExporter
Copy link
Author 

Hi Bruce,
thanks for providing the 'lsusb' output - haven't had time yet to dig into 
this, sorry; have only been back for two days and working through all the stuff 
...

You said that Orion sent You the Windows source code - would You mind emailing 
me a copy - could be a good starting point if there's a similar, already 
supported, chip available?
Cheers,

Steffen

Original comment by steffen....@gmail.com on 2 Aug 2012 at 8:41

@GoogleCodeExporter
Copy link
Author 

Bruce,
after spending some time on the net searching for Linux-related information 
regarding the Starshoot Autoguider it looks to me like there's only one option: 
implement a driver from scratch!
I think a good starting point on how to do that is the site 'Linux UVC driver 
and tools' (http://www.ideasonboard.org/uvc/#documentation), 'Linux Hardware 
Compatibility Lists & Linux Drivers' (http://www.linux-drivers.org) has some 
pointers, too.
Haven't done Kernel programming in ages ... i don't really know how steep the 
learning curve is dealing not only with the intricacies of USB but V4L2 as well 
(or UVC).
Since i don't own one of these cameras i can't help that much with developing a 
driver but i'd give a try!
Regards,

Steffen

Original comment by steffen....@gmail.com on 5 Aug 2012 at 9:32

@GoogleCodeExporter
Copy link
Author 

Yeah, sorry for taking so long to get back on this. However, your
conclusion is the same as mine. I haven't cut a driver in over 30
years. I think if I cut one, it will make a lot of people happy. I may
ask Orion for the op-codes to the chip, however, the masks on the
Windows code should match up as far as functionality goes. The problem
is knowing the right files to hack, copy and whatever. I have attached
a zip of the source of the driver as from Orion. I have other "stuff"
but I don't know what it is. If you don't mind, may I keep you in the
loop as I wander through this?

Yours,

Bruce

Original comment by brucer...@gmail.com on 7 Aug 2012 at 1:46

@GoogleCodeExporter
Copy link
Author 

Hi Bruce,
thanks - yeah, would be nice if You'd keep me in the loop; time permitting i'll 
try to help if at all possible.
I think something went wrong with the attachment - can't see it here?!
Would You mind sending it directly to me?

Steffen

Original comment by steffen....@gmail.com on 7 Aug 2012 at 2:41

@GoogleCodeExporter
Copy link
Author 

There are problems sending this zip because of Google. I have renamed
it again. If you cannot get it please let me know and I will send it
direct.

-Bruce

Original comment by brucer...@gmail.com on 7 Aug 2012 at 3:18

@GoogleCodeExporter
Copy link
Author 

Hi Bruce,
nope, can't see it - send it direct, please, that would be great.

Steffen

Original comment by steffen....@gmail.com on 8 Aug 2012 at 5:59

@GoogleCodeExporter
Copy link
Author 

done

Original comment by brucer...@gmail.com on 8 Aug 2012 at 6:16

@GoogleCodeExporter
Copy link
Author 

My OAG has failed, I believe that the serial EPROM is corrupted or erased.
If you have the firmware for the OAG, I could attempt to reprogram/replace the
EPROM. 

Thanks...

Original comment by AdamRosa...@gmail.com on 9 Aug 2012 at 7:02

@GoogleCodeExporter
Copy link
Author 

Gents I'm trying to,work out how to use an Orion StarShoot Autoguider with a 
Belkin Home Base - USB to wi-fi device. The Home Base is a linux device and 
Belkin publish the source code on their website. It already covers a wide range 
of USB devices and I've been trying to work out what I need to do add the 
StarShoot. I'd appreciate anything you have managed to work out about the Orion 
drivers. The Belkin source page is at 
http://en-us-support.belkin.com/app/answers/detail/a_id/7276 I don't know if 
there is any commonality between the way drivers are done for this project and 
in the Linux variant used there. I've been roughing up a stub based on an 
existing webcam's c and h files and tried to work with snooping the usb 
transfers under windows but have never written a driver so the learning curve 
is pretty big.

Would it be rude to ask for a copy of the windows source for the Orion 
StarShoot drivers or any suggestions on how to go about this? 

Bob

Original comment by BobSteph...@gmail.com on 1 Sep 2012 at 11:31

Attachments:

@GoogleCodeExporter
Copy link
Author 

I've realised that the SnoopyProLog file is not easily usable. I'll attach a 
text version of part of a run of the tool from this morning. I've not managed 
to export to xml and copy and paste formats badly so if it would help to search 
in the original for something specific please let me know.
The attached file will be the SnoopyPro output for the first 8 pairs of 
exchanges captured between my Win7 (32bit) laptop and the Orion StarShoot 
autoguider.

Bob

Original comment by BobSteph...@gmail.com on 1 Sep 2012 at 11:54

Attachments:

@GoogleCodeExporter
Copy link
Author 

Hi Bob,
thanks - i'll have a closer look at the code You sent; meanwhile i've emailed 
You some suggestions and the stuff that Bruce got from Orion - i hope he 
doesn't mind!
Cheers,

Steffen

Original comment by steffen....@gmail.com on 2 Sep 2012 at 4:47

@GoogleCodeExporter
Copy link
Author 

Don't mind at all. The more the merrier.

Original comment by brucer...@gmail.com on 3 Sep 2012 at 12:17

@GoogleCodeExporter
Copy link
Author 

Steffen and Bruce, thanks to you both for your efforts.
Hopefully I can add something to the mix.

Bob

Original comment by BobSteph...@gmail.com on 3 Sep 2012 at 8:44

@GoogleCodeExporter
Copy link
Author 

OK, so you got the code OK? I think I am going to have to call them
again and get the op codes of the chip.

Original comment by brucer...@gmail.com on 3 Sep 2012 at 11:27

@GoogleCodeExporter
Copy link
Author 

I've seen a number of posts which indicate that the StarShooter and the QHY5 
are the same under the covers with a firmware difference to return a different 
device id being the main difference.

One post mentioned hacking the firmware to make a QHY5 return a StarShooter 
device id as a workaround to some instability with the QHY5 drivers in windows.
Also what appears to be a view that the StarShooter is dumbed down and may 
actually be capable of a lot more than is in the official drivers. I known that 
approach is something that the CHDK project leveraged with Canon Powershot 
cameras, the lower end cameras often have capabilities which are locked out to 
differentiate from the high end cameras.

I've not worked out how far the QHY5 linux driver progress has gone.

Original comment by BobSteph...@gmail.com on 4 Sep 2012 at 5:34

@GoogleCodeExporter
Copy link
Author 

Chased a little more and found a reference to INDI support for QHY5 and Orion 
StarShoot guider at http://www.indilib.org/index.php?title=QHY

The discussion page reads as though its working for both but the source in the 
view source page does not look complete. I get the feeling I'm missing 
something with that, perhaps others may make better sense of it.

Bob

Original comment by BobSteph...@gmail.com on 4 Sep 2012 at 8:56

@GoogleCodeExporter
Copy link
Author 

Hi all,
there's a thread on Astrotreff (german astronomy-related forum) regarding 
Linux/Autoguiding where a working solution for the Starlight Xpress Lodestar 
was requested ... and a project on Sourceforge named 'lin_guider' is mentioned 
which provides QHY5 udn QHY6 support - maybe that's a suitable starting point?
Cheers,

Steffen

Original comment by steffen....@gmail.com on 14 Oct 2012 at 1:55

@GoogleCodeExporter
Copy link
Author 

Given all the changes for phd2, I'm marking all PHD1 unowned bugs as "WontFix". 
If somebody objects, I can undo it.

Original comment by br...@boneheads.us on 30 Aug 2013 at 12:47

  • Changed state: WontFix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Priority-Medium Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter