×

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

Bi-monthly release with minor bug fixes and improvements

Read More...

Failure to take exposure with Starlight SXVR-M25C

  • Posts: 33
  • Thank you received: 0

Failure to take exposure with Starlight SXVR-M25C was created by Russell Valentine

I've really enjoyed using INDI, well done!

The astronomy club I'm in recently got a used Starlight Express camera. The SXVR-M25C. However I am never able to get an exposure. When I try to take a 1 second exposure for example it just hangs there forever.

I seems to connect and it looks like it gets info from the camera. But when I expose I just never get the image. I see a lot of these in the logs

INDI Server: "2019-09-24T03:02:57: Driver indi_sx_ccd: sxReadPixels: libusb_control_transfer -> LIBUSB_ERROR_TIMEOUT"

I have it externally power, I've tried replacing the USB cable and also tried with the cooler on and off in the configuration.

Any help would be appreciated.

File Attachment:

File Name: log_21-59-40.txt
File Size:50 KB
4 years 6 months ago #43810
Attachments:

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

  • Posts: 33
  • Thank you received: 0

Replied by Russell Valentine on topic Failure to take exposure with Starlight SXVR-M25C

Sorry forgot some key information:

1) INDI Library version 1.8.1

2) KStars/Ekos 3.3.6 ubuntu ppa kstars-bleeding

3) INDI Source - Ubuntu ppa:mutlaqja/ppa

4) Kernel - Linux pendragon 5.0.0-29-generic #31~18.04.1-Ubuntu SMP Thu Sep 12 18:29:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
4 years 6 months ago #43811

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

  • Posts: 301
  • Thank you received: 46

Replied by Markku on topic Failure to take exposure with Starlight SXVR-M25C

Hi,

From the logfile I found this..
[2019-09-23T22:02:28.050 CDT DEBG ][ org.kde.kstars.indi] - SX CCD SXVR-M25C : "[DEBUG] Requested CCD Frame is (0,0) (21946 x 39648) "
[2019-09-23T22:02:28.052 CDT INFO ][ org.kde.kstars.indi] - SX CCD SXVR-M25C : "[ERROR] Error: Requested image out of bounds (21946, 39648) "
[2019-09-23T22:02:28.057 CDT INFO ][ org.kde.kstars.indi] - SX CCD SXVR-M25C : "[INFO] Device configuration applied. "
[2019-09-23T22:02:28.057 CDT DEBG ][ org.kde.kstars.indi] - SX CCD SXVR-M25C : "[DEBUG] Configuration successfully loaded. "

But according to the manual for the camera : www.sxccd.com/handbooks/SXVR-M25C%20handbook.pdf
It should be : 3032 x 2016 pixel array. Each pixel is 7.4 x 7.4uM
So maybe the problem is there ??

Cs,
/Markku
4 years 6 months ago #43828

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

  • Posts: 33
  • Thank you received: 0

Replied by Russell Valentine on topic Failure to take exposure with Starlight SXVR-M25C

Thanks for taking a look.

I agree that might be part of the problem. I noticed that also. However when I start INDI the frame set is set to 3032x2016. So I don't know where it is getting 21946x39648 from.
4 years 6 months ago #43830

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

  • Posts: 33
  • Thank you received: 0

Replied by Russell Valentine on topic Failure to take exposure with Starlight SXVR-M25C

A club member pointed out to me that the camera is a SXV-M25C (no R). I can double check the USB ID. Maybe that makes a difference. Maybe INDI treating it as the newer SXVR-M25C and not the older SXV-M25C.
4 years 6 months ago #43832

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

  • Posts: 33
  • Thank you received: 0

Replied by Russell Valentine on topic Failure to take exposure with Starlight SXVR-M25C

More information:



kern.log
============================================================

Sep 24 13:34:12 pendragon kernel: [ 195.296703] usb 1-5: new high-speed USB device number 4 using xhci_hcd
Sep 24 13:34:13 pendragon kernel: [ 196.964164] usb 1-5: new high-speed USB device number 5 using xhci_hcd
Sep 24 13:34:14 pendragon kernel: [ 197.716388] usb 1-5: config 1 has an invalid interface number: 1 but max is 0
Sep 24 13:34:14 pendragon kernel: [ 197.716392] usb 1-5: config 1 has no interface number 0
Sep 24 13:34:14 pendragon kernel: [ 197.716797] usb 1-5: New USB device found, idVendor=1278, idProduct=0325, bcdDevice= 0.00
Sep 24 13:34:14 pendragon kernel: [ 197.716802] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Sep 24 13:34:14 pendragon kernel: [ 197.716805] usb 1-5: Product: ECHO2
Sep 24 13:34:14 pendragon kernel: [ 197.716808] usb 1-5: Manufacturer: Starlight Xpress


lsusb
===============================================================
Bus 001 Device 005: ID 1278:0325 Starlight Xpress SXV-M25C



usb-devices
===============================================================
T: Bus=01 Lev=01 Prnt=01 Port=04 Cnt=02 Dev#= 5 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=1278 ProdID=0325 Rev=00.00
S: Manufacturer=Starlight Xpress
S: Product=ECHO2
C: #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA
I: If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none)
4 years 6 months ago #43837
Attachments:

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

  • Posts: 301
  • Thank you received: 46

Replied by Markku on topic Failure to take exposure with Starlight SXVR-M25C

Ok, so the resolution is a bit different then..
www.sxccd.com/handbooks/SXV-M25C%20handbook.pdf

I guess you already tried setting the resolution manually in INDI Controlpanel CCD Image settings ??
It could be something else too that messes up things, maybe you could try the cam on Windows and the software from sxccd.com and see if it works.

Cs,
/Markku
4 years 6 months ago #43841

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

  • Posts: 33
  • Thank you received: 0

Replied by Russell Valentine on topic Failure to take exposure with Starlight SXVR-M25C

Someone else in the astronomy club has already used it on windows using the SXR-M25C software from Starlight Express's website.

INDI thinks it is 3000x2000 I guess, from log:
"2019-09-24T03:02:26: Driver indi_sx_ccd: sxGetCameraParams: chip size: 3000 x 2000 x 16, pixel size: 7.80 x 7.80, matrix type: fff"

I would have thought INDI would handle a slightly wrong set frame, but maybe not. I will have to try 3040x2016 instead of 3032x2016. Of course in the manual you linked it lists multiple resolutions 3044x2016 is also mentioned. I suppose I can try the resolution given in the image from the windows software. It can't take it off the observatory grounds and it is a 1.25 hr drive one way, so will likely be a few days until I can try the different resolutions in the config.
4 years 6 months ago #43845

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

  • Posts: 301
  • Thank you received: 46

Replied by Markku on topic Failure to take exposure with Starlight SXVR-M25C

There is a small utility in INDI called : sx_ccd_test run in a terminal and see what it says.. when running that with my cams I get correct results.

I guess it doesn't hurt to try the resolutions..
I wish my obsy would be that far away from the city, I have about 20 minutes drive and the city lights can be a bit disturbing some nights.
4 years 6 months ago #43869

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

  • Posts: 33
  • Thank you received: 0

Replied by Russell Valentine on topic Failure to take exposure with Starlight SXVR-M25C

On windows with the Starlight software says the resolution of the camera is 3000x2000, however the fits images it saves are 3040x2024
  • 3000x2000 - Nope
  • 3032x2016 - Nope
  • 3046x2016 - Nope, does not let me says it is out of bounds.
  • 3040x2024 - Nope, does not let me says it is out of bounds.

sx_ccd_test output:
sx_ccd_test version 1.13
 
sxList: 'SXVR-M25C' #1 [0x1278, 0x325] found
sxList() -> 1
 
testing SXVR-M25C -----------------------------------
 
sxOpen: libusb_open -> OK
sxOpen: libusb_get_config_descriptor -> OK
sxOpen: libusb_claim_interface(1) -> OK
sxOpen() -> 1
 
sxGetCameraModel: libusb_control_transfer -> OK
sxGetCameraModel: libusb_control_transfer -> OK
sxGetCameraModel: NON-INTERLACED MONO model 25
sxGetCameraModel() -> 89
 
sxGetCameraParams: libusb_control_transfer -> OK
sxGetCameraParams: libusb_control_transfer -> OK
sxGetCameraParams: chip size: 3000 x 2000 x 16, pixel size: 7.80 x 7.80, matrix type: fff
sxGetCameraParams: capabilities: STAR2K
sxGetCameraParams: serial ports: 2
sxGetCameraParams(..., 0,...) -> 1
 
sxSetTimer: libusb_control_transfer -> OK
sxSetTimer(900) -> 1
 
sxGetTimer: libusb_control_transfer -> OK
sxGetTimer: libusb_control_transfer -> OK
sxGetTimer() -> 900
 
sxGetTimer: libusb_control_transfer -> OK
sxGetTimer: libusb_control_transfer -> OK
sxGetTimer() -> 0
 
sxClearPixels: libusb_control_transfer -> OK
sxClearPixels(..., 0) -> 1
 
sxLatchPixels: libusb_control_transfer -> OK
sxLatchPixels(..., 0, ...) -> 1
 
sxReadPixels: libusb_control_transfer -> OK
sxReadPixels() -> 1
 
1787 1795 1819 1834 1802 1788 1833 1798 1822 1799 
1815 1805 1787 1829 1802 1821 1811 1795 1810 1849 
1829 1789 1855 1813 1829 1807 1795 1827 1831 1823 
1837 1810 1819 1823 1819 1808 1815 1790 1841 1807 
1793 1807 1832 1811 1797 1839 1818 1813 1821 1810 
1812 1821 1843 1791 1825 1831 1850 1830 1817 1819 
1841 1826 1817 1818 1807 1795 1829 1830 1803 1819 
1789 1791 1795 1807 1835 1838 1801 1811 1828 1815 
1820 1819 1831 1823 1815 1817 1807 1790 1787 1797 
1815 1808 1838 1791 1795 1789 1827 1806 1803 1779 
 
sxClose: libusb_close
sxClose() 
 
4 years 6 months ago #44551

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

  • Posts: 301
  • Thank you received: 46

Replied by Markku on topic Failure to take exposure with Starlight SXVR-M25C

Now we get somewhere.. sx_ccd_test recognizes the camera as a "SXVR-M25C" but seems to read the CCD as a "SXV-M25C" and that makes some confusion I guess.. or maybe the error from your first post "Driver indi_sx_ccd: sxReadPixels: libusb_control_transfer -> LIBUSB_ERROR_TIMEOUT" is the cause of this ?
I think Jasem is the guy for this little problem, so I hope he will chime in here and take a look..

/Markku
4 years 6 months ago #44599

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

  • Posts: 301
  • Thank you received: 46

Replied by Markku on topic Failure to take exposure with Starlight SXVR-M25C

I checked the driver source and found this.. your cam have usbid the same as the SXVR-M25C so that is a problem, but I don't know how to make a difference between two cams with the same usbid, and that's why it's recognized wrong.

File : sxccdusb.cpp
static struct
{
    int pid;
    const char *name;
    int seq;
} SX_PIDS[] = { { 0x105, "SXVF-M5", 0 },
                { 0x305, "SXVF-M5C", 0 },
                { 0x107, "SXVF-M7", 0 },
                { 0x307, "SXVF-M7C", 0 },
                { 0x308, "SXVF-M8C", 0 },
                { 0x109, "SXVF-M9", 0 },
                { 0x325, "SXVR-M25C", 0 },
                { 0x326, "SXVR-M26C", 0 },
                { 0x115, "SXVR-H5", 0 },
                { 0x119, "SXVR-H9", 0 },  (The list continues to cover rest of the SX cameras..)

The other thing is in the file : sxccd.cpp
Because of this line "else if (isICX453)" the driver reads the cam a wrong way ?? Well, I'm just guessing but Jasem is probably the right guy to sort this out.
void SXCCD::SetupParms()
{
    struct t_sxccd_params params;
    model             = sxGetCameraModel(handle);
    bool isInterlaced = sxIsInterlaced(model);
    bool isICX453     = sxIsICX453(model);
    PrimaryCCD.setInterlaced(isInterlaced);
    sxGetCameraParams(handle, 0, &params);
    if (isInterlaced)
    {
        params.pix_height /= 2;
        params.height *= 2;
        wipeDelay = 130000;
    }
    else if (isICX453)
    {
        params.width = 3032;
        params.height = 2016;
    }
    SetCCDParams(params.width, params.height, params.bits_per_pixel, params.pix_width, params.pix_height);

/Markku
The following user(s) said Thank You: Russell Valentine
4 years 6 months ago #44642

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

Time to create page: 1.353 seconds