×

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

Bi-monthly release with minor bug fixes and improvements

ASI CCD Driver Issue

  • Posts: 158
  • Thank you received: 32

ASI CCD Driver Issue was created by Bill

Hey guys,

Went to connect up to do some testing, and I ran updates prior to doing so. After I updated and started INDI, my ASI CCD Cameras no longer connect, they just sit there in a yellow state trying to connect.

Here is the verbose output from the INDI Console:
bill@billpi:~$ indiserver -vv indi_asi_ccd indi_asi_wheel
2017-03-21T06:13:57: startup: indiserver -vv indi_asi_ccd indi_asi_wheel 
2017-03-21T06:13:57: Driver indi_asi_ccd: pid=4539 rfd=3 wfd=6 efd=7
2017-03-21T06:13:57: Driver indi_asi_wheel: pid=4540 rfd=4 wfd=9 efd=10
2017-03-21T06:13:57: listening to port 7624 on fd 5
2017-03-21T06:13:57: Driver indi_asi_wheel: sending <getProperties version='1.7'/>
 
2017-03-21T06:13:57: Driver indi_asi_ccd: sending <getProperties version='1.7'/>
 
2017-03-21T06:13:57: Driver indi_asi_wheel: read <defSwitchVector device='EFW' name='CONNECTION'>
2017-03-21T06:13:57: Driver indi_asi_wheel: read <defTextVector device='EFW' name='DRIVER_INFO'>
2017-03-21T06:13:57: Driver indi_asi_wheel: read <defSwitchVector device='EFW' name='DEBUG'>
2017-03-21T06:13:57: Driver indi_asi_wheel: read <defSwitchVector device='EFW' name='SIMULATION'>
2017-03-21T06:13:57: Driver indi_asi_wheel: read <defSwitchVector device='EFW' name='CONFIG_PROCESS'>
2017-03-21T06:13:57: Driver indi_asi_wheel: read <setSwitchVector device='EFW' name='DEBUG'>
2017-03-21T06:13:57: Driver indi_asi_ccd: read <getProperties device='Telescope Simulator' name='EQUATORIAL_EOD_COORD'>
2017-03-21T06:13:57: Driver indi_asi_ccd: snooping on Telescope Simulator.EQUATORIAL_EOD_COORD
2017-03-21T06:13:57: Driver indi_asi_ccd: read <getProperties device='Telescope Simulator' name='TELESCOPE_INFO'>
2017-03-21T06:13:57: Driver indi_asi_ccd: snooping on Telescope Simulator.TELESCOPE_INFO
2017-03-21T06:13:57: Driver indi_asi_ccd: read <getProperties device='CCD Simulator' name='FILTER_SLOT'>
2017-03-21T06:13:57: Driver indi_asi_ccd: snooping on CCD Simulator.FILTER_SLOT
2017-03-21T06:13:57: Driver indi_asi_ccd: read <getProperties device='CCD Simulator' name='FILTER_NAME'>
2017-03-21T06:13:57: Driver indi_asi_ccd: snooping on CCD Simulator.FILTER_NAME
2017-03-21T06:13:57: Driver indi_asi_ccd: read <getProperties device='SQM' name='SKY_QUALITY'>
2017-03-21T06:13:57: Driver indi_asi_ccd: snooping on SQM.SKY_QUALITY
2017-03-21T06:13:57: Driver indi_asi_ccd: read <message device='ZWO CCD ASI120MM-S' name=''>
2017-03-21T06:13:57: Driver indi_asi_ccd: read <defSwitchVector device='ZWO CCD ASI120MM-S' name='CONNECTION'>
2017-03-21T06:13:57: Driver indi_asi_ccd: read <defTextVector device='ZWO CCD ASI120MM-S' name='DRIVER_INFO'>
2017-03-21T06:13:57: Driver indi_asi_ccd: read <defSwitchVector device='ZWO CCD ASI120MM-S' name='DEBUG'>
2017-03-21T06:13:57: Driver indi_asi_ccd: read <defSwitchVector device='ZWO CCD ASI120MM-S' name='SIMULATION'>
2017-03-21T06:13:57: Driver indi_asi_ccd: read <defSwitchVector device='ZWO CCD ASI120MM-S' name='CONFIG_PROCESS'>
2017-03-21T06:13:57: Driver indi_asi_ccd: read <defTextVector device='ZWO CCD ASI120MM-S' name='ACTIVE_DEVICES'>
2017-03-21T06:13:57: Driver indi_asi_ccd: read <getProperties device='Telescope Simulator' name='EQUATORIAL_EOD_COORD'>
2017-03-21T06:13:57: Driver indi_asi_ccd: read <getProperties device='Telescope Simulator' name='TELESCOPE_INFO'>
2017-03-21T06:13:57: Driver indi_asi_ccd: read <getProperties device='CCD Simulator' name='FILTER_SLOT'>
2017-03-21T06:13:57: Driver indi_asi_ccd: read <getProperties device='CCD Simulator' name='FILTER_NAME'>
2017-03-21T06:13:57: Driver indi_asi_ccd: read <getProperties device='SQM' name='SKY_QUALITY'>
2017-03-21T06:13:57: Driver indi_asi_ccd: read <message device='ZWO CCD ASI1600MM-Cool' name=''>
2017-03-21T06:13:57: Driver indi_asi_ccd: read <defSwitchVector device='ZWO CCD ASI1600MM-Cool' name='CONNECTION'>
2017-03-21T06:13:57: Driver indi_asi_ccd: read <defTextVector device='ZWO CCD ASI1600MM-Cool' name='DRIVER_INFO'>
2017-03-21T06:13:57: Driver indi_asi_ccd: read <defSwitchVector device='ZWO CCD ASI1600MM-Cool' name='DEBUG'>
2017-03-21T06:13:57: Driver indi_asi_ccd: read <defSwitchVector device='ZWO CCD ASI1600MM-Cool' name='SIMULATION'>
2017-03-21T06:13:57: Driver indi_asi_ccd: read <defSwitchVector device='ZWO CCD ASI1600MM-Cool' name='CONFIG_PROCESS'>
2017-03-21T06:13:57: Driver indi_asi_ccd: read <defTextVector device='ZWO CCD ASI1600MM-Cool' name='ACTIVE_DEVICES'>
2017-03-21T06:14:00: Client 0: new arrival from 192.168.1.5:40200 - welcome!
2017-03-21T06:14:00: Client 0: read <getProperties device='' name=''>
2017-03-21T06:14:00: Driver indi_asi_wheel: queuing responsible for <getProperties device='' name=''>
2017-03-21T06:14:00: Driver indi_asi_ccd: queuing responsible for <getProperties device='' name=''>
2017-03-21T06:14:00: Driver indi_asi_wheel: sending <getProperties version="1.7"/>
 
2017-03-21T06:14:00: Driver indi_asi_ccd: sending <getProperties version="1.7"/>
 
2017-03-21T06:14:00: Driver indi_asi_wheel: read <defSwitchVector device='EFW' name='CONNECTION'>
2017-03-21T06:14:00: Client 0: queuing <defSwitchVector device='EFW' name='CONNECTION'>
2017-03-21T06:14:00: Driver indi_asi_ccd: read <defSwitchVector device='ZWO CCD ASI120MM-S' name='CONNECTION'>
2017-03-21T06:14:00: Client 0: queuing <defSwitchVector device='ZWO CCD ASI120MM-S' name='CONNECTION'>
2017-03-21T06:14:00: Driver indi_asi_ccd: read <defTextVector device='ZWO CCD ASI120MM-S' name='DRIVER_INFO'>
2017-03-21T06:14:00: Client 0: queuing <defTextVector device='ZWO CCD ASI120MM-S' name='DRIVER_INFO'>
2017-03-21T06:14:00: Driver indi_asi_ccd: read <defSwitchVector device='ZWO CCD ASI120MM-S' name='DEBUG'>
2017-03-21T06:14:00: Client 0: queuing <defSwitchVector device='ZWO CCD ASI120MM-S' name='DEBUG'>
2017-03-21T06:14:00: Driver indi_asi_ccd: read <defSwitchVector device='ZWO CCD ASI120MM-S' name='SIMULATION'>
2017-03-21T06:14:00: Client 0: queuing <defSwitchVector device='ZWO CCD ASI120MM-S' name='SIMULATION'>
2017-03-21T06:14:00: Driver indi_asi_ccd: read <defSwitchVector device='ZWO CCD ASI120MM-S' name='CONFIG_PROCESS'>
2017-03-21T06:14:00: Client 0: queuing <defSwitchVector device='ZWO CCD ASI120MM-S' name='CONFIG_PROCESS'>
2017-03-21T06:14:00: Driver indi_asi_ccd: read <defTextVector device='ZWO CCD ASI120MM-S' name='ACTIVE_DEVICES'>
2017-03-21T06:14:00: Client 0: queuing <defTextVector device='ZWO CCD ASI120MM-S' name='ACTIVE_DEVICES'>
2017-03-21T06:14:00: Driver indi_asi_ccd: read <defTextVector device='ZWO CCD ASI120MM-S' name='ACTIVE_DEVICES'>
2017-03-21T06:14:00: Client 0: queuing <defTextVector device='ZWO CCD ASI120MM-S' name='ACTIVE_DEVICES'>
2017-03-21T06:14:00: Client 0: sending <defSwitchVector device="EFW" name="CONNECTION" la
2017-03-21T06:14:00: Driver indi_asi_wheel: read <defTextVector device='EFW' name='DRIVER_INFO'>
2017-03-21T06:14:00: Client 0: queuing <defTextVector device='EFW' name='DRIVER_INFO'>
2017-03-21T06:14:00: Driver indi_asi_wheel: read <defSwitchVector device='EFW' name='DEBUG'>
2017-03-21T06:14:00: Client 0: queuing <defSwitchVector device='EFW' name='DEBUG'>
2017-03-21T06:14:00: Driver indi_asi_wheel: read <defSwitchVector device='EFW' name='SIMULATION'>
2017-03-21T06:14:00: Client 0: queuing <defSwitchVector device='EFW' name='SIMULATION'>
2017-03-21T06:14:00: Driver indi_asi_wheel: read <defSwitchVector device='EFW' name='CONFIG_PROCESS'>
2017-03-21T06:14:00: Client 0: queuing <defSwitchVector device='EFW' name='CONFIG_PROCESS'>
2017-03-21T06:14:00: Driver indi_asi_ccd: read <defSwitchVector device='ZWO CCD ASI1600MM-Cool' name='CONNECTION'>
2017-03-21T06:14:00: Client 0: queuing <defSwitchVector device='ZWO CCD ASI1600MM-Cool' name='CONNECTION'>
2017-03-21T06:14:00: Driver indi_asi_ccd: read <defTextVector device='ZWO CCD ASI1600MM-Cool' name='DRIVER_INFO'>
2017-03-21T06:14:00: Client 0: queuing <defTextVector device='ZWO CCD ASI1600MM-Cool' name='DRIVER_INFO'>
2017-03-21T06:14:00: Driver indi_asi_ccd: read <defSwitchVector device='ZWO CCD ASI1600MM-Cool' name='DEBUG'>
2017-03-21T06:14:00: Client 0: queuing <defSwitchVector device='ZWO CCD ASI1600MM-Cool' name='DEBUG'>
2017-03-21T06:14:00: Driver indi_asi_ccd: read <defSwitchVector device='ZWO CCD ASI1600MM-Cool' name='SIMULATION'>
2017-03-21T06:14:00: Client 0: queuing <defSwitchVector device='ZWO CCD ASI1600MM-Cool' name='SIMULATION'>
2017-03-21T06:14:00: Driver indi_asi_ccd: read <defSwitchVector device='ZWO CCD ASI1600MM-Cool' name='CONFIG_PROCESS'>
2017-03-21T06:14:00: Client 0: queuing <defSwitchVector device='ZWO CCD ASI1600MM-Cool' name='CONFIG_PROCESS'>
2017-03-21T06:14:00: Driver indi_asi_ccd: read <defTextVector device='ZWO CCD ASI1600MM-Cool' name='ACTIVE_DEVICES'>
2017-03-21T06:14:00: Client 0: queuing <defTextVector device='ZWO CCD ASI1600MM-Cool' name='ACTIVE_DEVICES'>
2017-03-21T06:14:00: Driver indi_asi_ccd: read <defTextVector device='ZWO CCD ASI1600MM-Cool' name='ACTIVE_DEVICES'>
2017-03-21T06:14:00: Client 0: queuing <defTextVector device='ZWO CCD ASI1600MM-Cool' name='ACTIVE_DEVICES'>
2017-03-21T06:14:00: Client 0: read <enableBLOB device='EFW' name=''>
2017-03-21T06:14:00: Client 0: sending <defSwitchVector device="ZWO CCD ASI120MM-S" name=
2017-03-21T06:14:00: Client 0: sending <defTextVector device="ZWO CCD ASI120MM-S" name="D
2017-03-21T06:14:00: Client 0: sending <defSwitchVector device="ZWO CCD ASI120MM-S" name=
2017-03-21T06:14:00: Client 0: sending <defSwitchVector device="ZWO CCD ASI120MM-S" name=
2017-03-21T06:14:00: Client 0: sending <defSwitchVector device="ZWO CCD ASI120MM-S" name=
2017-03-21T06:14:00: Client 0: sending <defTextVector device="ZWO CCD ASI120MM-S" name="A
2017-03-21T06:14:00: Client 0: sending <defTextVector device="ZWO CCD ASI120MM-S" name="A
2017-03-21T06:14:00: Client 0: sending <defTextVector device="EFW" name="DRIVER_INFO" lab
2017-03-21T06:14:01: Client 0: sending <defSwitchVector device="EFW" name="DEBUG" label="
2017-03-21T06:14:01: Client 0: sending <defSwitchVector device="EFW" name="SIMULATION" la
2017-03-21T06:14:01: Client 0: sending <defSwitchVector device="EFW" name="CONFIG_PROCESS
2017-03-21T06:14:01: Client 0: sending <defSwitchVector device="ZWO CCD ASI1600MM-Cool" n
2017-03-21T06:14:01: Client 0: sending <defTextVector device="ZWO CCD ASI1600MM-Cool" nam
2017-03-21T06:14:01: Client 0: sending <defSwitchVector device="ZWO CCD ASI1600MM-Cool" n
2017-03-21T06:14:01: Client 0: sending <defSwitchVector device="ZWO CCD ASI1600MM-Cool" n
2017-03-21T06:14:01: Client 0: sending <defSwitchVector device="ZWO CCD ASI1600MM-Cool" n
2017-03-21T06:14:01: Client 0: sending <defTextVector device="ZWO CCD ASI1600MM-Cool" nam
2017-03-21T06:14:01: Client 0: sending <defTextVector device="ZWO CCD ASI1600MM-Cool" nam
2017-03-21T06:14:01: Client 0: read <enableBLOB device='ZWO CCD ASI120MM-S' name=''>
2017-03-21T06:14:01: Client 0: read <enableBLOB device='ZWO CCD ASI1600MM-Cool' name=''>
2017-03-21T06:14:02: Client 0: read <newSwitchVector device='EFW' name='CONNECTION'>
2017-03-21T06:14:02: Driver indi_asi_wheel: queuing responsible for <newSwitchVector device='EFW' name='CONNECTION'>
2017-03-21T06:14:02: Driver indi_asi_wheel: sending <newSwitchVector device="EFW" name="CONNECTION">
 
2017-03-21T06:14:02: Client 0: read <newSwitchVector device='ZWO CCD ASI120MM-S' name='CONNECTION'>
2017-03-21T06:14:02: Driver indi_asi_ccd: queuing responsible for <newSwitchVector device='ZWO CCD ASI120MM-S' name='CONNECTION'>
2017-03-21T06:14:02: Client 0: read <newSwitchVector device='ZWO CCD ASI1600MM-Cool' name='CONNECTION'>
2017-03-21T06:14:02: Driver indi_asi_ccd: queuing responsible for <newSwitchVector device='ZWO CCD ASI1600MM-Cool' name='CONNECTION'>
2017-03-21T06:14:02: Driver indi_asi_ccd: sending <newSwitchVector device="ZWO CCD ASI120MM-S" name=
2017-03-21T06:14:02: Driver indi_asi_ccd: sending <newSwitchVector device="ZWO CCD ASI1600MM-Cool" n
2017-03-21T06:14:02: Driver indi_asi_wheel: read <setSwitchVector device='EFW' name='CONNECTION'>
2017-03-21T06:14:02: Client 0: queuing <setSwitchVector device='EFW' name='CONNECTION'>
2017-03-21T06:14:02: Client 0: sending <setSwitchVector device="EFW" name="CONNECTION" st
2017-03-21T06:14:02: Driver indi_asi_wheel: read <defNumberVector device='EFW' name='FILTER_SLOT'>
2017-03-21T06:14:02: Client 0: queuing <defNumberVector device='EFW' name='FILTER_SLOT'>
2017-03-21T06:14:02: Driver indi_asi_wheel: read <defTextVector device='EFW' name='FILTER_NAME'>
2017-03-21T06:14:02: Client 0: queuing <defTextVector device='EFW' name='FILTER_NAME'>
2017-03-21T06:14:02: Driver indi_asi_wheel: read <defSwitchVector device='EFW' name='USEJOYSTICK'>
2017-03-21T06:14:02: Client 0: queuing <defSwitchVector device='EFW' name='USEJOYSTICK'>
2017-03-21T06:14:02: Client 0: sending <defNumberVector device="EFW" name="FILTER_SLOT" l
2017-03-21T06:14:02: Driver indi_asi_wheel: read <setNumberVector device='EFW' name='FILTER_SLOT'>
2017-03-21T06:14:02: Client 0: queuing <setNumberVector device='EFW' name='FILTER_SLOT'>
2017-03-21T06:14:02: Client 0: sending <defTextVector device="EFW" name="FILTER_NAME" lab
2017-03-21T06:14:02: Client 0: sending <defSwitchVector device="EFW" name="USEJOYSTICK" l
2017-03-21T06:14:02: Client 0: sending <setNumberVector device="EFW" name="FILTER_SLOT" s
2017-03-21T06:14:02: Client 0: read <newSwitchVector device='EFW' name='CONFIG_PROCESS'>
2017-03-21T06:14:02: Driver indi_asi_wheel: queuing responsible for <newSwitchVector device='EFW' name='CONFIG_PROCESS'>
2017-03-21T06:14:02: Driver indi_asi_wheel: sending <newSwitchVector device="EFW" name="CONFIG_PROCESS
2017-03-21T06:14:02: Driver indi_asi_wheel: read <message device='EFW' name=''>
2017-03-21T06:14:02: Client 0: queuing <message device='EFW' name=''>
2017-03-21T06:14:02: Client 0: sending <message device="EFW" timestamp="2017-03-21T06:14:
2017-03-21T06:14:02: Driver indi_asi_wheel: read <setSwitchVector device='EFW' name='DEBUG'>
2017-03-21T06:14:02: Client 0: queuing <setSwitchVector device='EFW' name='DEBUG'>
2017-03-21T06:14:02: Driver indi_asi_wheel: read <message device='EFW' name=''>
2017-03-21T06:14:02: Client 0: queuing <message device='EFW' name=''>
2017-03-21T06:14:02: Client 0: sending <setSwitchVector device="EFW" name="DEBUG" state="
2017-03-21T06:14:02: Client 0: sending <message device="EFW" timestamp="2017-03-21T06:14:
2017-03-21T06:14:03: Driver indi_asi_wheel: read <setNumberVector device='EFW' name='FILTER_SLOT'>
2017-03-21T06:14:03: Client 0: queuing <setNumberVector device='EFW' name='FILTER_SLOT'>
2017-03-21T06:14:03: Client 0: sending <setNumberVector device="EFW" name="FILTER_SLOT" s
2017-03-21T06:14:03: Driver indi_asi_wheel: read <setTextVector device='EFW' name='FILTER_NAME'>
2017-03-21T06:14:03: Client 0: queuing <setTextVector device='EFW' name='FILTER_NAME'>
2017-03-21T06:14:03: Driver indi_asi_wheel: read <setSwitchVector device='EFW' name='USEJOYSTICK'>
2017-03-21T06:14:03: Client 0: queuing <setSwitchVector device='EFW' name='USEJOYSTICK'>
2017-03-21T06:14:03: Driver indi_asi_wheel: read <message device='EFW' name=''>
2017-03-21T06:14:03: Client 0: queuing <message device='EFW' name=''>
2017-03-21T06:14:03: Driver indi_asi_wheel: read <setSwitchVector device='EFW' name='CONFIG_PROCESS'>
2017-03-21T06:14:03: Client 0: queuing <setSwitchVector device='EFW' name='CONFIG_PROCESS'>
2017-03-21T06:14:03: Client 0: sending <setTextVector device="EFW" name="FILTER_NAME" sta
2017-03-21T06:14:03: Driver indi_asi_wheel: read <setNumberVector device='EFW' name='FILTER_SLOT'>
2017-03-21T06:14:03: Client 0: queuing <setNumberVector device='EFW' name='FILTER_SLOT'>
2017-03-21T06:14:03: Client 0: sending <setSwitchVector device="EFW" name="USEJOYSTICK" s
2017-03-21T06:14:03: Client 0: sending <message device="EFW" timestamp="2017-03-21T06:14:
2017-03-21T06:14:03: Client 0: sending <setSwitchVector device="EFW" name="CONFIG_PROCESS
2017-03-21T06:14:03: Client 0: sending <setNumberVector device="EFW" name="FILTER_SLOT" s
2017-03-21T06:14:04: Client 0: read <newSwitchVector device='ZWO CCD ASI120MM-S' name='CONNECTION'>
2017-03-21T06:14:04: Driver indi_asi_ccd: queuing responsible for <newSwitchVector device='ZWO CCD ASI120MM-S' name='CONNECTION'>
2017-03-21T06:14:04: Driver indi_asi_ccd: sending <newSwitchVector device="ZWO CCD ASI120MM-S" name=
2017-03-21T06:14:05: Client 0: read <newSwitchVector device='ZWO CCD ASI1600MM-Cool' name='CONNECTION'>
2017-03-21T06:14:05: Driver indi_asi_ccd: queuing responsible for <newSwitchVector device='ZWO CCD ASI1600MM-Cool' name='CONNECTION'>
2017-03-21T06:14:05: Driver indi_asi_ccd: sending <newSwitchVector device="ZWO CCD ASI1600MM-Cool" n

I connected them to Windows, and tested them in Sequence Generator Pro, and it seems to be working just fine. The funny thing is that the EFW is attached to a USB2.0 Hub that is on the ASI1600 camera, and it works just fine. The 120MM-S is on the same hub and it too doesn't work. Must be the camera driver?
Last edit: 7 years 1 week ago by Bill.
7 years 1 week ago #15444

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

Replied by Jasem Mutlaq on topic ASI CCD Driver Issue

ZWO just updated their driver SDK in INDI, could that be the reason? I will test soon ASI120M

EDIT: Tested and it works OK with latest SDK.
Last edit: 7 years 1 week ago by Jasem Mutlaq.
7 years 1 week ago #15462

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

  • Posts: 158
  • Thank you received: 32

Replied by Bill on topic ASI CCD Driver Issue

Interesting. I will have to do some more testing when I get home. I did not change anything on the Pi they are connected to, other than updating it to the latest code as usual. I tried a few different cables as well.

Hopefully my Pi isnt toasty.
7 years 1 week ago #15465

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

  • Posts: 298
  • Thank you received: 46

Replied by Markku on topic ASI CCD Driver Issue

Hi guys,
I just tried my SX cameras and none of them did connect, after downgrading to previous version it worked again..
So I think you can wait until next build or do a downgrade like this :
sudo dpkg -i /var/cache/apt/archives/indi-full_1.4~201703192003~ubuntu16.04.1_i386.deb
sudo dpkg -i /var/cache/apt/archives/libindi1_1.4.1+r2992~201703192155~ubuntu16.04.1_i386.deb
sudo dpkg -i /var/cache/apt/archives/libindi-data_1.4.1+r2992~201703192155~ubuntu16.04.1_all.deb
I'm not shure this is a correct way to do it but it worked..
Br
/Markku
The following user(s) said Thank You: Bill
7 years 1 week ago #15469

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

  • Posts: 158
  • Thank you received: 32

Replied by Bill on topic ASI CCD Driver Issue

Thanks for the test info. I do not have any pressing needs at the moment for using my gear, since I live in Washington state and we have had a grand total of six sunny days all year long. Perhaps it was just a bad daily build? I'll check in again this afternoon.
7 years 1 week ago #15470

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

  • Posts: 298
  • Thank you received: 46

Replied by Markku on topic ASI CCD Driver Issue

There is a new build ready now and my SX cameras work again ;) so it was just a bad build.
Br
/Markku
The following user(s) said Thank You: Ray Wells
7 years 1 week ago #15471

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

  • Posts: 158
  • Thank you received: 32

Replied by Bill on topic ASI CCD Driver Issue

Thanks for letting me know!

The interesting thing about ZWO updating the SDK recently, is that they just released a fix on Windows specific to the ASI120 camera on USB 2.0. Apparently some users were experiencing frame splits with the camera, and the fix they deployed solved it. Hopefully that same fix made it in here for Linux users too. That would be awesome.

Edit: Updated today and everything works fine now.
Last edit: 7 years 6 days ago by Bill.
7 years 1 week ago #15472

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

  • Posts: 81
  • Thank you received: 3

Replied by Brian Morgan on topic ASI CCD Driver Issue

Looking at the GitHub repo, I can tell that the INDI development team is using "Travis CI" where the "CI" stands for Continuous Integration. What happens is this: whenever anyone commits a change to the repo it kicks off Travis CI which runs a suite of "unit tests" programmed by the development team to test the validity of the code. If any of the unit tests fail then team members receive a notification to fix the bug.

It is a monumental challenge to ascertain with 100% confidence that a change to the code is valid and will run perfectly for end-users. The reason being that INDI interfaces with a multitude of hardware devices. It would be a fascinating feat of engineering if the unit tests included downloading the code automatically and run against every supported camera, mount, filter wheel, focuser, etc. I don't think that is what's happening. I think some basic testing is performed. The final up or down vote is ours to make. That is the symbiotic relationship we have with our INDI development team hosts! :)
7 years 6 days ago #15479

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

  • Posts: 158
  • Thank you received: 32

Replied by Bill on topic ASI CCD Driver Issue

Oh for sure, that is why I test the builds daily.
7 years 6 days ago #15480

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

  • Posts: 81
  • Thank you received: 3

Replied by Brian Morgan on topic ASI CCD Driver Issue

Rockstar, how do you manage the following scenario: You are packing up your equipment and traveling halfway around the world to witness a once-in-a-lifetime event. INDI is part of your setup. How do you ensure that your software is stable when it is time to record the event?

I ask this question because I have my laptop setup to automatically receive daily INDI builds. And as we've seen today things can sometimes become broken without warning. I would imagine that mission-critical equipment would not be setup to automatically receive daily builds. That would be performed on your test bed. At certain intervals you would make the final judgement that the software is stable given your requirements. Then you would download that specific INDI build to your mission-critical equipment.

A few days ago I posted a topic related to this but it was awkwardly written. How do you manage this process?

Thank you.
7 years 6 days ago #15482

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

  • Posts: 158
  • Thank you received: 32

Replied by Bill on topic ASI CCD Driver Issue

Here is how I would handle this:

1. Take an image of the Raspberry Pi in a known good state. Update this image only when you feel fully comfortable with a build. This shouldn't make it so you need to stop taking daily builds, since reimaging a Raspberry Pi takes minutes.
2. KStars doesn't update daily, so as long as you have a stable build of KStars installed, do not update until you return from your trip. You may want to save the stable package along with the Raspberry Pi image, just in case.
3. Take trip, enjoy imaging.
The following user(s) said Thank You: Brian Morgan
7 years 6 days ago #15484

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

  • Posts: 171
  • Thank you received: 41

Replied by Christian on topic ASI CCD Driver Issue

Same procedure here, in addition I have two laptops, one with latest stuff and one with stuff known to work. Never lost a good night due to software issues right now. Only due to mount issues and such things…
The following user(s) said Thank You: Brian Morgan
7 years 6 days ago #15504

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

Time to create page: 0.752 seconds