×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

Read More...

Driver for older Orion Starshoot Deep Space Imager

  • Posts: 4
  • Thank you received: 1

Replied by Michael Dewitte on topic Driver for older Orion Starshoot Deep Space Imager

I know this topic is quite old, but I'm looking for the same thing, since it's the only thing preventing me to switch my setup to Ini / Linux / Raspberry PI....

Has anyone news about this ? Or about spec or where I could find stuff to be able to write my own drivers (beeing a developper) ?

Thx in advance for any help / reaction !
7 years 9 months ago #8946

Please Log in or Create an account to join the conversation.

  • Posts: 314
  • Thank you received: 95

Replied by Oleg on topic Driver for older Orion Starshoot Deep Space Imager

Look at this page about Meade DSI Pro (I/II) INDI driver
and this page Raspberry PI .
You can try my open project Astronomy Linux
Last edit: 7 years 9 months ago by Oleg.
7 years 9 months ago #8947

Please Log in or Create an account to join the conversation.

Replied by Jasem Mutlaq on topic Driver for older Orion Starshoot Deep Space Imager

Isn't that just a branded QHY5? If so, just use the INDI QHY driver.
7 years 9 months ago #8948

Please Log in or Create an account to join the conversation.

  • Posts: 173
  • Thank you received: 19

Replied by Jon on topic Driver for older Orion Starshoot Deep Space Imager

Here is some info from the Windows debugger about it if it's helpful.....
[Port2]  :  Orion StarShoot Deep Space Imager 2
 
 
Is Port User Connectable:         yes
Is Port Debug Capable:            no
Companion Port Number:            2
Companion Hub Symbolic Link Name: USB#VID_2109&PID_0812#5&2301df1d&0&5#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
Protocols Supported:
 USB 1.1:                         yes
 USB 2.0:                         yes
 USB 3.0:                         no
 
Device Power State:               PowerDeviceD0
 
       ---===>Device Information<===---
English product name: "StarShoot Camera"
 
ConnectionStatus:                  
Current Config Value:              0x01  -> Device Bus Speed: High (is not SuperSpeed or higher capable)
Device Address:                    0x1F
Open Pipes:                           2
 
          ===>Device Descriptor<===
bLength:                           0x12
bDescriptorType:                   0x01
bcdUSB:                          0x0200
bDeviceClass:                      0x00  -> This is an Interface Class Defined Device
bDeviceSubClass:                   0x00
bDeviceProtocol:                   0x00
bMaxPacketSize0:                   0x40 = (64) Bytes
idVendor:                        0x1856 = Imaginova
idProduct:                       0x0003
bcdDevice:                       0x0000
iManufacturer:                     0x01
     English (United States)  "Orion"
iProduct:                          0x02
     English (United States)  "StarShoot Camera"
iSerialNumber:                     0x00
bNumConfigurations:                0x01
 
          ---===>Open Pipes<===---
 
          ===>Endpoint Descriptor<===
bLength:                           0x07
bDescriptorType:                   0x05
bEndpointAddress:                  0x82  -> Direction: IN - EndpointID: 2
bmAttributes:                      0x02  -> Bulk Transfer Type
wMaxPacketSize:                  0x0200 = 0x200 max bytes
bInterval:                         0x00
 
          ===>Endpoint Descriptor<===
bLength:                           0x07
bDescriptorType:                   0x05
bEndpointAddress:                  0x08  -> Direction: OUT - EndpointID: 8
bmAttributes:                      0x02  -> Bulk Transfer Type
wMaxPacketSize:                  0x0200 = 0x200 max bytes
bInterval:                         0x00
 
       ---===>Full Configuration Descriptor<===---
 
          ===>Configuration Descriptor<===
bLength:                           0x09
bDescriptorType:                   0x02
wTotalLength:                    0x0020  -> Validated
bNumInterfaces:                    0x01
bConfigurationValue:               0x01
iConfiguration:                    0x00
bmAttributes:                      0xE0  -> Self Powered
  -> Remote Wakeup
MaxPower:                          0xC8 = 400 mA
 
          ===>Interface Descriptor<===
bLength:                           0x09
bDescriptorType:                   0x04
bInterfaceNumber:                  0x00
bAlternateSetting:                 0x00
bNumEndpoints:                     0x02
bInterfaceClass:                   0xFF  -> Interface Class Unknown to USBView
bInterfaceSubClass:                0x00
bInterfaceProtocol:                0x00
iInterface:                        0x00
 
          ===>Endpoint Descriptor<===
bLength:                           0x07
bDescriptorType:                   0x05
bEndpointAddress:                  0x82  -> Direction: IN - EndpointID: 2
bmAttributes:                      0x02  -> Bulk Transfer Type
wMaxPacketSize:                  0x0200 = 0x200 max bytes
bInterval:                         0x00
 
          ===>Endpoint Descriptor<===
bLength:                           0x07
bDescriptorType:                   0x05
bEndpointAddress:                  0x08  -> Direction: OUT - EndpointID: 8
bmAttributes:                      0x02  -> Bulk Transfer Type
wMaxPacketSize:                  0x0200 = 0x200 max bytes
bInterval:                         0x00
7 years 9 months ago #8949

Please Log in or Create an account to join the conversation.

  • Posts: 173
  • Thank you received: 19

Replied by Jon on topic Driver for older Orion Starshoot Deep Space Imager

Unable to establish:
+ QHY CCD
7 years 9 months ago #8950

Please Log in or Create an account to join the conversation.

  • Posts: 173
  • Thank you received: 19

Replied by Jon on topic Driver for older Orion Starshoot Deep Space Imager

I attempted to capture some packets for this camera but I really don't know what I'm doing. I followed the advice given in this thread: www.indilib.org/forum/general/878-suppor...oot-g3-ccd.html#5448

There doesn't seem to be a firmware requirement if I followed the thread instructions correctly. In this capture, I just took a one second exposure. I don't know what I am looking for in the capture log. Any help is appreciated and I don't mind plugging away at this.....

EDIT* I re-uploaded the correct file

--Jon

File Attachment:

File Name: Orion_DSCI...g.tar.gz
File Size:61 KB
Last edit: 7 years 9 months ago by Jon.
7 years 9 months ago #9071
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 4
  • Thank you received: 1

Replied by Michael Dewitte on topic Driver for older Orion Starshoot Deep Space Imager

I just opened up my Orion Stashoot DeppSapce II (SSDSI II) and I found a CY7C68001 chip in it, that's a Cypress SX2. Datsheet is easely found, in which we can find commands and all the necessary stuff. I'll try to decode capture with this help, if possible...
The following user(s) said Thank You: Jasem Mutlaq
7 years 9 months ago #9084

Please Log in or Create an account to join the conversation.

  • Posts: 173
  • Thank you received: 19

Replied by Jon on topic Driver for older Orion Starshoot Deep Space Imager

Thanks for checking that. Interestingly, the thread I referred to mentions that the device ID will most likely change after giving the vm access to the camera if there is firmware loading. I'm not picking up a new/different device ID when running lsusb the second time......

--Jon
7 years 9 months ago #9086

Please Log in or Create an account to join the conversation.

  • Posts: 173
  • Thank you received: 19

Replied by Jon on topic Driver for older Orion Starshoot Deep Space Imager

Based on your information about the chip, I have dumped the firmware for it....Am I allowed to upload it?
Because the id's didn't change, does this mean the firmware is stored on the camera and not needing to be loaded?


Also,please note my earlier post with the capture has been re-uploaded as I attached the incorrect capture file......

--Jon
Last edit: 7 years 9 months ago by Jon.
7 years 9 months ago #9087

Please Log in or Create an account to join the conversation.

  • Posts: 4
  • Thank you received: 1

Replied by Michael Dewitte on topic Driver for older Orion Starshoot Deep Space Imager

I'm not sure you can upload this kind of stuff here. For what I understand in the doc of the SX2, the SX2 only manage the USB thing for the processor. And the eprom can be linked to the SX2, so I imagine that the firmware is in fact the config of the SX2, not the firmware of the camera itself... Am I right ?

I'll take a look at your capture as soon as I get some time. I think that the set of commands that the host can send to the camera is very simple... We don't have that many parameters when we request a capture and I don't see other commands I could issue to the camera. It's really a simple stuff. The most complicated step is probably to understand what are the parameters and how they are sent to the camera (the coding, the order, etc)
7 years 9 months ago #9105

Please Log in or Create an account to join the conversation.

  • Posts: 173
  • Thank you received: 19

Replied by Jon on topic Driver for older Orion Starshoot Deep Space Imager

I've been doing some more USB sniffing to try and understand more about this camera. I wanted to just try some simple tests to connect to it but I have failed miserably. My first approach was in thinking that since the Meade DSI cameras have the same Cypress chip, that I could just swap out the firmware files and change the vid/pid info and at least get a connection. That simply doesn't/won't/can't work. I decided it might be best to try and build from the generic-ccd drive, since it seems less complicated, to at least get a simple connection. I am not able to get the code snippet referenced in generic-ccd.cpp to compile after using and #include<usb.h>. The snippet below gives an error: undefined reference to `usb_get_busses'
cameraCount = 0;
     for (struct usb_bus *bus = usb_get_busses(); bus && cameraCount < MAX_DEVICES; bus = bus->next) {
       for (struct usb_device *dev = bus->devices; dev && cameraCount < MAX_DEVICES; dev = dev->next) {
         int vid = dev->descriptor.idVendor;
         int pid = dev->descriptor.idProduct;
         for (int i = 0; deviceTypes[i].pid; i++) {
           if (vid == deviceTypes[i].vid && pid == deviceTypes[i].pid) {
             cameras[i] = new GenericCCD(dev, deviceTypes[i].name);
             break;
           }
         }
       }
     }
I am very much a novice with c++ development and also developing in Linux in general. I think that perhaps I am missing something with regards to linking usb.h to the compiler but don't understand what or how to do that using make files.......

--Jon
7 years 9 months ago #9204

Please Log in or Create an account to join the conversation.

  • Posts: 7
  • Thank you received: 0

Replied by Louis McCarthy on topic Driver for older Orion Starshoot Deep Space Imager

Great timing, I just started looking into this too....

I think we can split the research into two sections:
1) Plug in and enumeration
2) Image capture

Plug in and enumeration would be where firmware upload, if it does it, would occur. I'm not sure if the USB sniffing tools I have can do this. Can anyone else get a dump during this phase?

I've created a dump, of image capture, using Wireshark Version 2.2.0 (v2.2.0-0-g5368c50 from master-2.2) and the bundled version of USBPcapCMD (1.1.0.0-g794bf26-5).
It consists of starting MaximDL, capturing a 5 second frame, and then closing MaximDL.

I've configured the fan speed to be low. When the camera is plugged into USB, the fan stays high until the MaximDL software is started. It's a nice indicator of important USB activity.

I've attached the dump here, but if that doesn't work you can download from Dropbox: www.dropbox.com/s/tj2l2m873sf6e1g/sspro-...photo.pcapng.xz?dl=0
7 years 7 months ago #10229
Attachments:

Please Log in or Create an account to join the conversation.

Time to create page: 0.965 seconds