×

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

Bi-monthly release with minor bug fixes and improvements

Moravian G3-11000C1FW indi driver

  • Posts: 69
  • Thank you received: 12
I tested the G3-16200 with the 7-slot external filter wheel and found a few issues
1) the displayed cooling power stays unchanged at about 42% but the temperature changes to the commanded value correctly.
2) Fan On/Off causes the alert and error in the log:
miccd_fan error: Unknown error -1.
3) The external filter wheel has 7 slots but there are only 5 slots in the driver.
7 years 10 months ago #8546

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

  • Posts: 69
  • Thank you received: 12
I want to update. I installed the newer driver from INDI Github and the problems mentioned above were solved. After the end of the exposure, I got this error:
2016-05-30T18:12:03: Driver indi_mi_ccd: read setNumberVector MI CCD G3-16200 CCD_TEMPERATURE Busy
 CCD_TEMPERATURE_VALUE='-13.772273063659667969'
2016-05-30T18:12:03: Client 0: queuing <setNumberVector device='MI CCD G3-16200' name='CCD_TEMPERATURE'>
2016-05-30T18:12:03: Driver indi_mi_ccd: read setNumberVector MI CCD G3-16200 CCD_COOLER_POWER Ok
 CCD_COOLER_VALUE='77.20000147819519043'
2016-05-30T18:12:03: Client 0: queuing <setNumberVector device='MI CCD G3-16200' name='CCD_COOLER_POWER'>
2016-05-30T18:12:03: Client 0: sending msg copy 1 nq 2:
<setNumberVector device="MI CCD G3-16200" name="CCD_TEMPERATURE" state="Busy" timeout="60" timestamp="2016-05-30T18:12:03">
    <oneNumber name="CCD_TEMPERATURE_VALUE">
-13.772273063659667969
    </oneNumber>
</setNumberVector>
 
2016-05-30T18:12:03: Client 0: sending msg copy 1 nq 1:
<setNumberVector device="MI CCD G3-16200" name="CCD_COOLER_POWER" state="Ok" timeout="60" timestamp="2016-05-30T18:12:03">
    <oneNumber name="CCD_COOLER_VALUE">
77.20000147819519043
    </oneNumber>
</setNumberVector>
 
2016-05-30T18:12:03: Driver indi_mi_ccd: read message MI CCD G3-16200   'Exposure in progress: Time left 0'
2016-05-30T18:12:03: Client 0: queuing <message device='MI CCD G3-16200' name=''>
2016-05-30T18:12:03: Driver indi_mi_ccd: read setNumberVector MI CCD G3-16200 CCD_EXPOSURE Busy
 CCD_EXPOSURE_VALUE='0'
2016-05-30T18:12:03: Client 0: queuing <setNumberVector device='MI CCD G3-16200' name='CCD_EXPOSURE'>
2016-05-30T18:12:03: Client 0: sending msg copy 1 nq 2:
<message device="MI CCD G3-16200" timestamp="2016-05-30T18:12:03" message="Exposure in progress: Time left 0"/>
 
2016-05-30T18:12:03: Client 0: sending msg copy 1 nq 1:
<setNumberVector device="MI CCD G3-16200" name="CCD_EXPOSURE" state="Busy" timeout="60" timestamp="2016-05-30T18:12:03">
    <oneNumber name="CCD_EXPOSURE_VALUE">
0
    </oneNumber>
</setNumberVector>
 
 
2016-05-30T18:12:03: Driver indi_mi_ccd: [gxccd] error: read() failed: -1, LIBUSB_ERROR_IO, transferred: 0, errno: 11
2016-05-30T18:12:03: Driver indi_mi_ccd: [gxccd] error: read() failed: read only -1 bytes: Resource temporarily unavailable
2016-05-30T18:13:04: Driver indi_mi_ccd: [gxccd] error: cannot perform ioctl(): cmd: 0x11, LIBUSB_ERROR_TIMEOUT, ret: -7
2016-05-30T18:13:04: Driver indi_mi_ccd: read message MI CCD G3-16200   'Getting voltage failed: .'
 
 
 
2016-05-30T18:13:04: Client 0: queuing <message device='MI CCD G3-16200' name=''>
2016-05-30T18:13:04: Driver indi_mi_ccd: read setNumberVector MI CCD G3-16200 CCD_TEMPERATURE Busy
 CCD_TEMPERATURE_VALUE='-13.772273063659667969'
2016-05-30T18:13:04: Client 0: queuing <setNumberVector device='MI CCD G3-16200' name='CCD_TEMPERATURE'>
2016-05-30T18:13:04: Driver indi_mi_ccd: read setNumberVector MI CCD G3-16200 CCD_COOLER_POWER Alert
 CCD_COOLER_VALUE='0'
2016-05-30T18:13:04: Client 0: queuing <setNumberVector device='MI CCD G3-16200' name='CCD_COOLER_POWER'>
2016-05-30T18:13:04: Driver indi_mi_ccd: read setNumberVector MI CCD G3-16200 CCD_EXPOSURE Busy
 CCD_EXPOSURE_VALUE='0'
2016-05-30T18:13:04: Client 0: queuing <setNumberVector device='MI CCD G3-16200' name='CCD_EXPOSURE'>
2016-05-30T18:13:04: Client 0: sending msg copy 1 nq 4:
<message device="MI CCD G3-16200" timestamp="2016-05-30T18:13:04" message="Getting voltage failed: ."/>
 
2016-05-30T18:13:04: Client 0: sending msg copy 1 nq 3:
<setNumberVector device="MI CCD G3-16200" name="CCD_TEMPERATURE" state="Busy" timeout="60" timestamp="2016-05-30T18:13:04">
    <oneNumber name="CCD_TEMPERATURE_VALUE">
-13.772273063659667969
    </oneNumber>
</setNumberVector>
 
2016-05-30T18:13:04: Client 0: sending msg copy 1 nq 2:
<setNumberVector device="MI CCD G3-16200" name="CCD_COOLER_POWER" state="Alert" timeout="60" timestamp="2016-05-30T18:13:04">
    <oneNumber name="CCD_COOLER_VALUE">
0
    </oneNumber>
</setNumberVector>
 
2016-05-30T18:13:04: Client 0: sending msg copy 1 nq 1:
<setNumberVector device="MI CCD G3-16200" name="CCD_EXPOSURE" state="Busy" timeout="60" timestamp="2016-05-30T18:13:04">
    <oneNumber name="CCD_EXPOSURE_VALUE">
0
    </oneNumber>
</setNumberVector>

And the log file shows:

INFO    31.970367 sec   : Session log file /tmp/indi_mi_ccd_2016-05-30T18:00:26.log
INFO    41.449232 sec   : Connected to MI CCD G3-16200.
INFO    49.088450 sec   : Setting current filter to slot 1
DEBUG   49.088983 sec   : Filter changed to 1
INFO    54.974776 sec   : Setting current filter to slot 3
DEBUG   58.675901 sec   : Filter changed to 3
DEBUG   686.619289 sec  : Taking a 10 seconds frame...
DEBUG   686.620507 sec  : Exposure in progress: Time left 9
DEBUG   687.622184 sec  : Exposure in progress: Time left 8
DEBUG   688.623846 sec  : Exposure in progress: Time left 7
DEBUG   689.625479 sec  : Exposure in progress: Time left 6
DEBUG   690.627133 sec  : Exposure in progress: Time left 5
DEBUG   691.628763 sec  : Exposure in progress: Time left 4
DEBUG   692.632320 sec  : Exposure in progress: Time left 3
DEBUG   693.633043 sec  : Exposure in progress: Time left 2
DEBUG   694.634040 sec  : Exposure in progress: Time left 1
DEBUG   695.635697 sec  : Exposure in progress: Time left 0
DEBUG   696.851162 sec  : Exposure in progress: Time left 0
ERROR   757.852581 sec  : Getting voltage failed: .




What could be the cause of the problem? Thanks.
Last edit: 7 years 10 months ago by anat.
7 years 10 months ago #8559

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

Please communicate it to MI. Mr. Jakub is amazing at resolving these issues quickly.
7 years 10 months ago #8560

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

  • Posts: 69
  • Thank you received: 12
Thanks. I am in touch with Jakub now. He is fast :)
7 years 10 months ago #8571

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

Time to create page: 0.433 seconds