×

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

Bi-monthly release with minor bug fixes and improvements

Read More...

Starlight Xpress Trius 825 Mono not detected

  • Posts: 33
  • Thank you received: 4

Replied by Krzysztof on topic Starlight Xpress Trius 825 Mono not detected

No one else has access to this and messages are silent about any other connections, i think it might be only some software which uses it for some reason. Still can't figure it out, what it might be is a true mystery.
I'll wait maybe giorgio will check his with rpi.
Last edit: 8 years 2 weeks ago by Krzysztof.
8 years 2 weeks ago #7526

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

  • Posts: 712
  • Thank you received: 174

Replied by Peter Polakovic on topic Starlight Xpress Trius 825 Mono not detected

Can you try to disconnect Lodestar and to use 825 only? Peter
8 years 2 weeks ago #7528

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

  • Posts: 33
  • Thank you received: 4

Replied by Krzysztof on topic Starlight Xpress Trius 825 Mono not detected

I've disconnected (physically) everything except SX-825 and run indiserver on rpi only with indi_sx_ccd. It still behaves the same - detected but not useful.
sx_ccd_test gives the same result
pi@pi:~ $ sx_ccd_test 
sx_ccd_test version 1.11
 
sxList: 'SX-825' #1 [0x1278, 0x189] found
sxList() -> 1
 
testing SX-825 -----------------------------------
 
sxOpen: libusb_open -> LIBUSB_ERROR_ACCESS
sxOpen() -> 0
 
Segmentation fault
pi@pi:~ $

It does have built-in usb hub. When I connect lodestar or filter wheel or both even to it they do work through indiserver. Maybe this hub interferes with something?
Last edit: 8 years 2 weeks ago by Krzysztof.
8 years 2 weeks ago #7531

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

  • Posts: 33
  • Thank you received: 4

Replied by Krzysztof on topic Starlight Xpress Trius 825 Mono not detected

I have just made test on "conventional" PC with kubuntu installed. After updating packages i started with sx_ccd_test which gave me exactly the same error (only SX-825 physically connected).
<code>sx_ccd_test version 1.11

sxList: 'SX-825' #1 [0x1278, 0x189] found
sxList() -> 1

testing SX-825

sxOpen: libusb_open -> LIBUSB_ERROR_ACCESS
sxOpen() -> 0

Segmentation fault (core dumped)</code>

This is how messages look like with -vv on indiserver after start:
2016-04-02T12:48:48: startup: indiserver -vv indi_sx_ccd 
2016-04-02T12:48:48: Driver indi_sx_ccd: pid=15716 rfd=3 wfd=6 efd=7
2016-04-02T12:48:48: listening to port 7624 on fd 4
2016-04-02T12:48:48: Driver indi_sx_ccd: sending <getProperties version='1.7'/>
 
2016-04-02T12:48:48: Driver indi_sx_ccd: read <getProperties device='Telescope Simulator' name='EQUATORIAL_EOD_COORD'>
2016-04-02T12:48:48: Driver indi_sx_ccd: snooping on Telescope Simulator.EQUATORIAL_EOD_COORD
2016-04-02T12:48:48: Driver indi_sx_ccd: read <getProperties device='Telescope Simulator' name='TELESCOPE_INFO'>
2016-04-02T12:48:48: Driver indi_sx_ccd: snooping on Telescope Simulator.TELESCOPE_INFO
2016-04-02T12:48:48: Driver indi_sx_ccd: read <getProperties device='CCD Simulator' name='FILTER_SLOT'>
2016-04-02T12:48:48: Driver indi_sx_ccd: snooping on CCD Simulator.FILTER_SLOT
2016-04-02T12:48:48: Driver indi_sx_ccd: read <getProperties device='CCD Simulator' name='FILTER_NAME'>
2016-04-02T12:48:48: Driver indi_sx_ccd: snooping on CCD Simulator.FILTER_NAME
2016-04-02T12:48:48: Driver indi_sx_ccd: read <setNumberVector device='SX CCD SX-825' name='CCD_EXPOSURE'>
2016-04-02T12:48:48: Driver indi_sx_ccd: read <defSwitchVector device='SX CCD SX-825' name='CONNECTION'>
2016-04-02T12:48:48: Driver indi_sx_ccd: read <defTextVector device='SX CCD SX-825' name='DRIVER_INFO'>
2016-04-02T12:48:48: Driver indi_sx_ccd: read <defSwitchVector device='SX CCD SX-825' name='DEBUG'>
2016-04-02T12:48:48: Driver indi_sx_ccd: read <defSwitchVector device='SX CCD SX-825' name='CONFIG_PROCESS'>
2016-04-02T12:48:48: Driver indi_sx_ccd: read <defTextVector device='SX CCD SX-825' name='ACTIVE_DEVICES'>

A this is how it looks like when i connect from a client and try to connect to camera:
2016-04-02T12:50:20: Client 0: new arrival from 192.168.99.72:52047 - welcome!
2016-04-02T12:50:20: Client 0: read <getProperties device='' name=''>
2016-04-02T12:50:20: Driver indi_sx_ccd: queuing responsible for <getProperties device='' name=''>
2016-04-02T12:50:20: Driver indi_sx_ccd: sending <getProperties version="1.0"/>
 
2016-04-02T12:50:20: Driver indi_sx_ccd: read <defSwitchVector device='SX CCD SX-825' name='CONNECTION'>
2016-04-02T12:50:20: Client 0: queuing <defSwitchVector device='SX CCD SX-825' name='CONNECTION'>
2016-04-02T12:50:20: Client 0: sending <defSwitchVector device="SX CCD SX-825" name="CONN
2016-04-02T12:50:20: Driver indi_sx_ccd: read <defTextVector device='SX CCD SX-825' name='DRIVER_INFO'>
2016-04-02T12:50:20: Client 0: queuing <defTextVector device='SX CCD SX-825' name='DRIVER_INFO'>
2016-04-02T12:50:20: Driver indi_sx_ccd: read <defSwitchVector device='SX CCD SX-825' name='DEBUG'>
2016-04-02T12:50:20: Client 0: queuing <defSwitchVector device='SX CCD SX-825' name='DEBUG'>
2016-04-02T12:50:20: Driver indi_sx_ccd: read <defSwitchVector device='SX CCD SX-825' name='CONFIG_PROCESS'>
2016-04-02T12:50:20: Client 0: queuing <defSwitchVector device='SX CCD SX-825' name='CONFIG_PROCESS'>
2016-04-02T12:50:20: Driver indi_sx_ccd: read <defTextVector device='SX CCD SX-825' name='ACTIVE_DEVICES'>
2016-04-02T12:50:20: Client 0: queuing <defTextVector device='SX CCD SX-825' name='ACTIVE_DEVICES'>
2016-04-02T12:50:20: Driver indi_sx_ccd: read <defTextVector device='SX CCD SX-825' name='ACTIVE_DEVICES'>
2016-04-02T12:50:20: Client 0: queuing <defTextVector device='SX CCD SX-825' name='ACTIVE_DEVICES'>
2016-04-02T12:50:20: Client 0: sending <defTextVector device="SX CCD SX-825" name="DRIVER
2016-04-02T12:50:20: Client 0: sending <defSwitchVector device="SX CCD SX-825" name="DEBU
2016-04-02T12:50:20: Client 0: sending <defSwitchVector device="SX CCD SX-825" name="CONF
2016-04-02T12:50:20: Client 0: sending <defTextVector device="SX CCD SX-825" name="ACTIVE
2016-04-02T12:50:20: Client 0: sending <defTextVector device="SX CCD SX-825" name="ACTIVE
2016-04-02T12:50:20: Client 0: read <enableBLOB device='SX CCD SX-825' name=''>
2016-04-02T12:50:20: Driver indi_sx_ccd: queuing responsible for <enableBLOB device='SX CCD SX-825' name=''>
2016-04-02T12:50:20: Driver indi_sx_ccd: sending <enableBLOB device="SX CCD SX-825">
Also
</enableB
2016-04-02T12:50:25: Client 0: read <newSwitchVector device='SX CCD SX-825' name='CONNECTION'>
2016-04-02T12:50:25: Driver indi_sx_ccd: queuing responsible for <newSwitchVector device='SX CCD SX-825' name='CONNECTION'>
2016-04-02T12:50:25: Driver indi_sx_ccd: sending <newSwitchVector device="SX CCD SX-825" name="CONN
2016-04-02T12:50:25: Driver indi_sx_ccd: stderr EOF
2016-04-02T12:50:25: Driver indi_sx_ccd: restart #1
2016-04-02T12:50:25: Driver indi_sx_ccd: pid=15748 rfd=3 wfd=7 efd=8
2016-04-02T12:50:25: Driver indi_sx_ccd: sending <getProperties version='1.7'/>
 
2016-04-02T12:50:25: Driver indi_sx_ccd: read <getProperties device='Telescope Simulator' name='EQUATORIAL_EOD_COORD'>
2016-04-02T12:50:25: Driver indi_sx_ccd: snooping on Telescope Simulator.EQUATORIAL_EOD_COORD
2016-04-02T12:50:25: Driver indi_sx_ccd: read <getProperties device='Telescope Simulator' name='TELESCOPE_INFO'>
2016-04-02T12:50:25: Driver indi_sx_ccd: snooping on Telescope Simulator.TELESCOPE_INFO
2016-04-02T12:50:25: Driver indi_sx_ccd: read <getProperties device='CCD Simulator' name='FILTER_SLOT'>
2016-04-02T12:50:25: Driver indi_sx_ccd: snooping on CCD Simulator.FILTER_SLOT
2016-04-02T12:50:25: Driver indi_sx_ccd: read <getProperties device='CCD Simulator' name='FILTER_NAME'>
2016-04-02T12:50:25: Driver indi_sx_ccd: snooping on CCD Simulator.FILTER_NAME
2016-04-02T12:50:25: Driver indi_sx_ccd: read <setNumberVector device='SX CCD SX-825' name='CCD_EXPOSURE'>
2016-04-02T12:50:25: Client 0: queuing <setNumberVector device='SX CCD SX-825' name='CCD_EXPOSURE'>
2016-04-02T12:50:25: Client 0: sending <setNumberVector device="SX CCD SX-825" name="CCD_
2016-04-02T12:50:25: Driver indi_sx_ccd: read <defSwitchVector device='SX CCD SX-825' name='CONNECTION'>
2016-04-02T12:50:25: Client 0: queuing <defSwitchVector device='SX CCD SX-825' name='CONNECTION'>
2016-04-02T12:50:25: Driver indi_sx_ccd: read <defTextVector device='SX CCD SX-825' name='DRIVER_INFO'>
2016-04-02T12:50:25: Client 0: queuing <defTextVector device='SX CCD SX-825' name='DRIVER_INFO'>
2016-04-02T12:50:25: Driver indi_sx_ccd: read <defSwitchVector device='SX CCD SX-825' name='DEBUG'>
2016-04-02T12:50:25: Client 0: queuing <defSwitchVector device='SX CCD SX-825' name='DEBUG'>
2016-04-02T12:50:25: Driver indi_sx_ccd: read <defSwitchVector device='SX CCD SX-825' name='CONFIG_PROCESS'>
2016-04-02T12:50:25: Client 0: queuing <defSwitchVector device='SX CCD SX-825' name='CONFIG_PROCESS'>
2016-04-02T12:50:25: Driver indi_sx_ccd: read <defTextVector device='SX CCD SX-825' name='ACTIVE_DEVICES'>
2016-04-02T12:50:25: Client 0: queuing <defTextVector device='SX CCD SX-825' name='ACTIVE_DEVICES'>
2016-04-02T12:50:25: Client 0: sending <defSwitchVector device="SX CCD SX-825" name="CONN
2016-04-02T12:50:25: Client 0: sending <defTextVector device="SX CCD SX-825" name="DRIVER
2016-04-02T12:50:25: Client 0: sending <defSwitchVector device="SX CCD SX-825" name="DEBU
2016-04-02T12:50:25: Client 0: sending <defSwitchVector device="SX CCD SX-825" name="CONF
2016-04-02T12:50:25: Client 0: sending <defTextVector device="SX CCD SX-825" name="ACTIVE
Last edit: 8 years 2 weeks ago by Krzysztof.
8 years 2 weeks ago #7539

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

  • Posts: 712
  • Thank you received: 174

Replied by Peter Polakovic on topic Starlight Xpress Trius 825 Mono not detected

It is actually the same problem, it crashed on connecting camera.

I'm surprised, that it happen only with this camera. Lodestar uses the same protocol as 825. I'll check it with vendor if there is some difference. Peter
8 years 2 weeks ago #7542

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

  • Posts: 712
  • Thank you received: 174

Replied by Peter Polakovic on topic Starlight Xpress Trius 825 Mono not detected

So the answer is, that there is no difference between 825 and older cameras. I have no idea what's wrong :( Can you try it under windows or OSX? Peter
8 years 2 weeks ago #7545

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

  • Posts: 33
  • Thank you received: 4

Replied by Krzysztof on topic Starlight Xpress Trius 825 Mono not detected

Peter
So far i have tested this camera with:
- indiserver on RPi2 (arm) - doesn't work
- indiserver on PC (x86) - doesn't work
- built-in AstroImager 2.0 drivers on OS X - doesn't work
- USBoverIP on RPi2 (arm) + windows client machine - does work
- INDI Server (2.2.5) on OS X (10.11) - does work

doesn't work = detected but not useful

I can make more tests if it might be helpful just let me know exactly what tests are needed.
8 years 2 weeks ago #7546

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

  • Posts: 712
  • Thank you received: 174

Replied by Peter Polakovic on topic Starlight Xpress Trius 825 Mono not detected

It is not supported by AstroImager 2.0, but should work with 2.1. Can you try this beta: download.cloudmakers.eu/AI2.1_90.dmg ?
The following user(s) said Thank You: Krzysztof
8 years 2 weeks ago #7547

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

  • Posts: 712
  • Thank you received: 174

Replied by Peter Polakovic on topic Starlight Xpress Trius 825 Mono not detected

Hm... and I forgot to add new PIDs to 99-sx.rules, that's why it does work on OSX and doesn't on Linux :( Fixed in rel. 2711. Peter
The following user(s) said Thank You: Krzysztof
8 years 2 weeks ago #7548

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

  • Posts: 33
  • Thank you received: 4

Replied by Krzysztof on topic Starlight Xpress Trius 825 Mono not detected

AI2.1_90 beta - works :)
I'll wait till Jasem black box will compile new release and hopefully try it tomorrow.
Thanks!
8 years 2 weeks ago #7550

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

  • Posts: 33
  • Thank you received: 4

Replied by Krzysztof on topic Starlight Xpress Trius 825 Mono not detected

I have updated indilib on my RPi2 today.
1. sx_ccd_test (1.12) doesn't show any errors now, only bunch of OK's and numbers (that's good I guess).
2. "indiserver -vv indi_sx_ccd" starts without problems
3. AI 2.0(59) and 2.1(90) connects to SX-825 on RPi2-indiserver without any issues and camera is fully operational
4. Test with lodestar x2 connected - also no problem, everything works

Thank You :)
8 years 2 weeks ago #7579

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

  • Posts: 712
  • Thank you received: 174

Replied by Peter Polakovic on topic Starlight Xpress Trius 825 Mono not detected

Great, thank you for cooperation :) Peter
8 years 1 week ago #7589

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

Time to create page: 0.859 seconds