×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

asi_ccd driver troubles

  • Posts: 454
  • Thank you received: 51

Replied by Patrick on topic asi_ccd driver troubles

Checked the cam yesterday on the field. It works fine but I had a problem with binning 2 under shooting with EKOS. When I used it I try to get a preview the time counter make the countdown and a message "downloading" appears next to the counter with the clock turning in infinite loop. I had to stop it with stop button and didn't get any images.
8 years 4 months ago #5801
The topic has been locked.
  • Posts: 454
  • Thank you received: 51

Replied by Patrick on topic asi_ccd driver troubles

After having tested the ZWO120 on odroid with kstars all works fine. So I launched the indiserver on the odroid with the cam connected and tested the remote access from my notebook. I have got the following message:
2015-11-11T22:49:35 Unable to establish remote devices:
+ ZWO CCD
+ ZWO CCD
Please ensure remote device name corresponds to actual device name.
2015-11-11T22:49:19 INDI services started. Connection to remote INDI server is successful.
2015-11-11T22:49:19 Connecting to remote INDI server at 192.168.5.53 on port 7624 ...
The name of the cam that I gave is the same

I have used the name proposed by INDI/EKOS : "ZWO CCD" but the connection to the cam fail.

:blink:
8 years 4 months ago #5816
The topic has been locked.
  • Posts: 130
  • Thank you received: 11

Replied by Klaus on topic asi_ccd driver troubles

Try
ZWO CCD ASI120MM
as remote device name. I never tried this but have it in my settings and don't remember why. :whistle:

Klaus
8 years 4 months ago #5817
The topic has been locked.
  • Posts: 454
  • Thank you received: 51

Replied by Patrick on topic asi_ccd driver troubles

Thanks Klaus,
The "ZWO CCD" is the one proposed by EKOS on the client side in the EKOS main tab. I guessed the name was the same on the server side. Maybe it is different on the server side.
In the Kstars config -> EKOS configuration I think that the name to provide is the one of the device in the server side.
Unfortunately I don't find in INDI any way to know those names. I thought that the -vv option would give the default names of the devices supported by the driver, but no it doesn't.
This would help a lot.
All this is a little bit confused for me.
I will check the name you propose.
Pat
Last edit: 8 years 4 months ago by Patrick.
8 years 4 months ago #5820
The topic has been locked.
  • Posts: 454
  • Thank you received: 51

Replied by Patrick on topic asi_ccd driver troubles

:( No more success with ZWO CCD ASI120MM

2015-11-12T09:16:20 Unable to establish remote device:
+ ZWO CCD ASI120MM
Please ensure remote device name corresponds to actual device name.
2015-11-12T09:16:05 INDI services started. Connection to remote INDI server is successful.
2015-11-12T09:16:05 Connecting to remote INDI server at 192.168.5.52 on port 7624 ...

I guess I have troubles with the driver. If it works locally on the odroid and not in remote I think there is something wrong in the naming convention. But don't know what.
Last edit: 8 years 4 months ago by Patrick.
8 years 4 months ago #5821
The topic has been locked.
  • Posts: 454
  • Thank you received: 51

Replied by Patrick on topic asi_ccd driver troubles

I just tested now to launch indiserver in fifo mode. Starting the driver indi_asi_ccd after and forcing the name to "ZWO CCD" and got the same result.
I loose my Latin.
8 years 4 months ago #5824
The topic has been locked.
I just tested it here and Ekos have no problem connecting to the camera, I just selected "ZWO CCD" from the combo box under remote. What is the KStars version you're using?
8 years 4 months ago #5825
The topic has been locked.
  • Posts: 130
  • Thank you received: 11

Replied by Klaus on topic asi_ccd driver troubles

Just for my curiosity: Starting indi server in terminal I get this:
klaus@sirius:~$ indiserver -vvv indi_asi_ccd
2015-11-12T12:29:09: startup: indiserver -vvv indi_asi_ccd 
2015-11-12T12:29:09: Driver indi_asi_ccd: pid=3215 rfd=3 wfd=6 efd=7
2015-11-12T12:29:09: listening to port 7624 on fd 4
2015-11-12T12:29:09: Driver indi_asi_ccd: sending msg copy 1 nq 1:
<getProperties version='1.7'/>
 
2015-11-12T12:29:09: Driver indi_asi_ccd: read getProperties Telescope Simulator EQUATORIAL_EOD_COORD 
2015-11-12T12:29:09: Driver indi_asi_ccd: snooping on Telescope Simulator.EQUATORIAL_EOD_COORD
2015-11-12T12:29:09: Driver indi_asi_ccd: read getProperties Telescope Simulator TELESCOPE_INFO 
2015-11-12T12:29:09: Driver indi_asi_ccd: snooping on Telescope Simulator.TELESCOPE_INFO
2015-11-12T12:29:09: Driver indi_asi_ccd: read getProperties CCD Simulator FILTER_SLOT 
2015-11-12T12:29:09: Driver indi_asi_ccd: snooping on CCD Simulator.FILTER_SLOT
2015-11-12T12:29:09: Driver indi_asi_ccd: read getProperties CCD Simulator FILTER_NAME 
2015-11-12T12:29:09: Driver indi_asi_ccd: snooping on CCD Simulator.FILTER_NAME
2015-11-12T12:29:09: Driver indi_asi_ccd: read message ZWO CCD ASI120MM   'Using default recorder (SER File Recorder)'
2015-11-12T12:29:09: Driver indi_asi_ccd: read defSwitchVector ZWO CCD ASI120MM CONNECTION Idle rw
    CONNECT='Off'
 DISCONNECT='On'
2015-11-12T12:29:09: Driver indi_asi_ccd: read defTextVector ZWO CCD ASI120MM DRIVER_INFO Idle ro
 DRIVER_NAME='ZWO CCD ASI120MM'
 DRIVER_EXEC='indi_asi_ccd'
 DRIVER_VERSION='0.4'
 DRIVER_INTERFACE='2'
2015-11-12T12:29:09: Driver indi_asi_ccd: read defSwitchVector ZWO CCD ASI120MM DEBUG Idle rw
     ENABLE='Off'
    DISABLE='On'
2015-11-12T12:29:09: Driver indi_asi_ccd: read defSwitchVector ZWO CCD ASI120MM SIMULATION Idle rw
     ENABLE='Off'
    DISABLE='On'
2015-11-12T12:29:09: Driver indi_asi_ccd: read defSwitchVector ZWO CCD ASI120MM CONFIG_PROCESS Idle rw
 CONFIG_LOAD='Off'
 CONFIG_SAVE='Off'
 CONFIG_DEFAULT='Off'

The driver name is reported as 'ZWO CCD ASI120MM'. Isn't this what I should feed in EKOS' Remote device names?

Klaus
8 years 4 months ago #5831
The topic has been locked.
No need, just select ZWO CCD from the dropdown list.
The following user(s) said Thank You: Klaus
8 years 4 months ago #5833
The topic has been locked.
  • Posts: 454
  • Thank you received: 51

Replied by Patrick on topic asi_ccd driver troubles

@Jasem

The version of Kstars is 2.4.0.
Looks like this is when the driver send the device properties through network that the problem occurs.
Is it possible that it could be a network issue or a hardware one ?
The server is connected and the communication is opened with it so ...

CS
Pat
8 years 4 months ago #5834
The topic has been locked.
Unlikely, is the camera connected to the Raspberry PI _before_ you run the indiserver indi_asi_ccd command?
8 years 4 months ago #5835
The topic has been locked.
  • Posts: 454
  • Thank you received: 51

Replied by Patrick on topic asi_ccd driver troubles

:oops: You are right Jasem, the camera must be connected before starting the driver. Now it works fine.
Thank you so much.
This a little step for me but a huge step for humanity :silly:
Next step connecting a ST8300 to the Odroid. That will be a huge step for the universe :blink:

PS: I checked the binning 2x but it doesn't work. The counter countdown and the "downloading" message never disappear while the little clock run infinitely.

CS
Pat
Last edit: 8 years 4 months ago by Patrick.
8 years 4 months ago #5841
The topic has been locked.
Time to create page: 5.105 seconds