×

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

Bi-monthly release with minor bug fixes and improvements

Atik 1.6 Driver problem

  • Posts: 90
  • Thank you received: 12
Hi I'm running a Pi3 with ubuntu 16.04 and I've installed the Atik 1.6 driver from cloudmakers. Ekos was able to take an image but the FITS preview never pops up.
I've tried to run the atik ccd test and below shows... Can anyone help? Thanks..
If I rolled back the driver to 1.1 version. It's working fine atik ccd test shows complete and ok...

ubuntu@ubuntu-standard:~$ sudo atik_ccd_test

version 1.6

list

-> AtikCamera::list(...)
'Atik 490ex' [0x20e7, 0xdf3a] found...
-> AtikCameraImpl::AtikCameraImpl(..., Atik 490ex, 2)
maxPacketSize = 16777216
<- AtikCameraImpl::AtikCameraImpl
<- AtikCamera::list 1

open Atik 490ex

-> AtikCameraImpl::open()
libusb_claim_interface() -> LIBUSB_SUCCESS / LIBUSB_TRANSFER_COMPLETED
libusb_set_interface_alt_setting() -> LIBUSB_SUCCESS / LIBUSB_TRANSFER_COMPLETED
-> AtikCameraImpl::writeFW()
cpu stopped 1
cpu started 1
<- AtikCameraImpl::writeFW 1
-> AtikCameraImpl::setPortDirection(0, 0x9f)
<- AtikCameraImpl::setPortDirection 1
-> AtikCameraImpl::setPortState(0, 0x80)
<- AtikCameraImpl::setPortState 1
-> AtikCameraImpl::i2cSetTimeout(50)
<- AtikCameraImpl::i2cSetTimeout 1
-> AtikCameraImpl::setParTimeout(50)
<- AtikCameraImpl::setParTimeout 1
-> AtikCameraImpl::i2cSetSpeed(0)
<- AtikCameraImpl::i2cSetSpeed 1
-> AtikCameraImpl::flush()
libusb_bulk_transfer -> LIBUSB_ERROR_TIMEOUT
0 bytes flushed
<- AtikCameraImpl::flush
-> AtikCameraImpl::i2cSetTimeout(5000)
<- AtikCameraImpl::i2cSetTimeout 1
-> AtikCameraImpl::eepRead(3, ..., 2)
-> AtikCameraImpl::i2cWrite(81, [0x00 0x03], 2)
<- AtikCameraImpl::i2cWrite 1
-> AtikCameraImpl::i2cRead(81, ..., 2)
<- AtikCameraImpl::i2cRead 1 [0x3a 0xdf]
<- AtikCameraImpl::eepRead 1 [0x3a 0xdf]
-> AtikCameraImpl::eepRead(1000, ..., 5)
-> AtikCameraImpl::i2cWrite(81, [0x00 0xe8], 2)
<- AtikCameraImpl::i2cWrite 1
-> AtikCameraImpl::i2cRead(81, ..., 5)
<- AtikCameraImpl::i2cRead 1 [0xff 0xff 0xff 0xff...]
<- AtikCameraImpl::eepRead 1 [0xff 0xff 0xff 0xff...]
colour = 1, offsetX = 0, offsetY = 0
pid = df3a
-> AtikCameraImpl::i2cSetTimeout(100)
<- AtikCameraImpl::i2cSetTimeout 1
-> AtikCameraImpl::setParTimeout(1000)
<- AtikCameraImpl::setParTimeout 1
-> AtikCameraImpl::parInit(9)
-> AtikCameraImpl::parInit(...)
<- AtikCameraImpl::parInit 1
<- AtikCameraImpl::parInit 1
-> AtikCameraImpl::ping()
ping -> 100
-> AtikCameraImpl::sendCommand(80, [0x64], ..., 1, 0)
<- AtikCameraImpl::sendCommand 1 NULL
ping <- 148
ping -> 101
-> AtikCameraImpl::sendCommand(80, [0x65], ..., 1, 0)
<- AtikCameraImpl::sendCommand 1 NULL
ping <- 164
ping -> 102
-> AtikCameraImpl::sendCommand(80, [0x66], ..., 1, 0)
<- AtikCameraImpl::sendCommand 1 NULL
ping <- 120
ping -> 103
-> AtikCameraImpl::sendCommand(80, [0x67], ..., 1, 0)
<- AtikCameraImpl::sendCommand 1 NULL
ping <- 34
ping -> 104
-> AtikCameraImpl::sendCommand(80, [0x68], ..., 1, 0)
<- AtikCameraImpl::sendCommand 1 NULL
ping <- 144
<- AtikCameraImpl::ping 0
unlock()
failed to initialize device!!!
<- AtikCameraImpl::open 00
ubuntu@ubuntu-standard:~$
Last edit: 7 years 6 months ago by Stephen Wong.
7 years 6 months ago #10801

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

  • Posts: 105
  • Thank you received: 23
Hi,

I have the same problem. This problem is under investigation: check the subject 'Atik 4000 "dispatch error"' on the forum.
The following user(s) said Thank You: Stephen Wong
7 years 6 months ago #10807

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

  • Posts: 90
  • Thank you received: 12
ok thanks I will wait for the investigation results.. of course I'm happy to provide further logs
7 years 6 months ago #10808

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

  • Posts: 77
  • Thank you received: 10

Replied by NickK on topic Atik 1.6 Driver problem

Hi,
Although the ATIK drivers are peters (and I don't develop the drivers anymore and I don't work for ATIK/SB), I did work on competitive drivers (TheSkyX for OSX) a few years ago so I know the original code base behaviour.

Looking at the logs the camera does not fully initialise as the driver is waiting for the ping response in the initialisation code. I took the liberty to enhance the drivers so that they'd automatically attempt to re-initialise if this occurred.
ODROID C2 Ubuntu
Last edit: 7 years 6 months ago by NickK.
7 years 6 months ago #10818

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

  • Posts: 712
  • Thank you received: 174
Hi, as Nick said, ping is a part of initialisation code and this looks, that initialisation failed for some reason. Can you replug it before running atik_ccd_test (both USB and power)? Thank you, Peter
7 years 6 months ago #10821

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

  • Posts: 90
  • Thank you received: 12
Hi Peter,
Here's what I reinstalled 1.6 driver and then plug in the camera, power it up, and run atik_ccd_test. It shows failed to get image. and then when I run the test again, every time it would show unable to initialize. Please refer to the log below. (btw I just installed v1.7 and exact same problem happens). Thank you!

ubuntu@ubuntu-standard:~$ atik_ccd_test

version 1.6

list

-> AtikCamera::list(...)
'Atik 490ex' [0x20e7, 0xdf3a] found...
-> AtikCameraImpl::AtikCameraImpl(..., Atik 490ex, 2)
maxPacketSize = 16777216
<- AtikCameraImpl::AtikCameraImpl
<- AtikCamera::list 1

open Atik 490ex

-> AtikCameraImpl::open()
libusb_claim_interface() -> LIBUSB_SUCCESS / LIBUSB_TRANSFER_COMPLETED
libusb_set_interface_alt_setting() -> LIBUSB_SUCCESS / LIBUSB_TRANSFER_COMPLETED
-> AtikCameraImpl::writeFW()
cpu stopped 1
cpu started 1
<- AtikCameraImpl::writeFW 1
-> AtikCameraImpl::setPortDirection(0, 0x9f)
<- AtikCameraImpl::setPortDirection 1
-> AtikCameraImpl::setPortState(0, 0x80)
<- AtikCameraImpl::setPortState 1
-> AtikCameraImpl::i2cSetTimeout(50)
<- AtikCameraImpl::i2cSetTimeout 1
-> AtikCameraImpl::setParTimeout(50)
<- AtikCameraImpl::setParTimeout 1
-> AtikCameraImpl::i2cSetSpeed(0)
<- AtikCameraImpl::i2cSetSpeed 1
-> AtikCameraImpl::flush()
libusb_bulk_transfer -> LIBUSB_ERROR_TIMEOUT
0 bytes flushed
<- AtikCameraImpl::flush
-> AtikCameraImpl::i2cSetTimeout(5000)
<- AtikCameraImpl::i2cSetTimeout 1
-> AtikCameraImpl::eepRead(3, ..., 2)
-> AtikCameraImpl::i2cWrite(81, [0x00 0x03], 2)
<- AtikCameraImpl::i2cWrite 1
-> AtikCameraImpl::i2cRead(81, ..., 2)
<- AtikCameraImpl::i2cRead 1 [0x3a 0xdf]
<- AtikCameraImpl::eepRead 1 [0x3a 0xdf]
-> AtikCameraImpl::eepRead(1000, ..., 5)
-> AtikCameraImpl::i2cWrite(81, [0x00 0xe8], 2)
<- AtikCameraImpl::i2cWrite 1
-> AtikCameraImpl::i2cRead(81, ..., 5)
<- AtikCameraImpl::i2cRead 1 [0xff 0xff 0xff 0xff...]
<- AtikCameraImpl::eepRead 1 [0xff 0xff 0xff 0xff...]
colour = 1, offsetX = 0, offsetY = 0
pid = df3a
-> AtikCameraImpl::i2cSetTimeout(100)
<- AtikCameraImpl::i2cSetTimeout 1
-> AtikCameraImpl::setParTimeout(1000)
<- AtikCameraImpl::setParTimeout 1
-> AtikCameraImpl::parInit(9)
-> AtikCameraImpl::parInit(...)
<- AtikCameraImpl::parInit 1
<- AtikCameraImpl::parInit 1
-> AtikCameraImpl::ping()
ping -> 100
-> AtikCameraImpl::sendCommand(80, [0x64], ..., 1, 0)
<- AtikCameraImpl::sendCommand 1 NULL
ping <- 101
<- AtikCameraImpl::ping 1
-> AtikCameraImpl::sendCommand(1, NULL, ..., 0, 0)
<- AtikCameraImpl::sendCommand 1 NULL
version: 3.37
model: ATIK-490ex
manufacturer: ARTEMIS CCD
flags: 0x158 PREVIEW SUBSAMPLE OVERLAP
pixel count: 3380 x 2704
pixel size: 3.7 x 3.7
max bin: 255 x 255
well capacity: 60
-> AtikCameraImpl::appInit()
-> AtikCameraImpl::sendCommand(44, NULL, ..., 0, 0)
<- AtikCameraImpl::sendCommand 1 NULL
DEBUG OFF

DEBUG ON
APPINIT completed
<- AtikCameraImpl::appInit 1
-> AtikCameraImpl::sendCommand(54, NULL, ..., 0, 2)
<- AtikCameraImpl::sendCommand 1 [0x01 0x00]
temperature sensor count: 1
-> AtikCameraImpl::getTemperatureSensorStatus(1, ...)
lock()
-> AtikCameraImpl::sendCommand(55, [0x01 0x00], ..., 2, 6)
<- AtikCameraImpl::sendCommand 1 [0x02 0x00 0x00 0x00...]
unlock()
<- AtikCameraImpl::getTemperatureSensorStatus 1
temperature sensor type: 2
-> AtikCameraImpl::sendCommand(52, NULL, ..., 0, 6)
<- AtikCameraImpl::sendCommand 1 [0x1f 0x00 0xff 0x00...]
cooler: COOLER_SETPOINT
min cooler power: 0
max cooler power: 255
-> AtikCameraImpl::eepRead(5, ..., 2)
-> AtikCameraImpl::i2cWrite(81, [0x00 0x05], 2)
<- AtikCameraImpl::i2cWrite 1
-> AtikCameraImpl::i2cRead(81, ..., 2)
<- AtikCameraImpl::i2cRead 1 [0x93 0x7e]
<- AtikCameraImpl::eepRead 1 [0x93 0x7e]
-> AtikCameraImpl::eepRead(8, ..., 2)
-> AtikCameraImpl::i2cWrite(81, [0x00 0x08], 2)
<- AtikCameraImpl::i2cWrite 1
-> AtikCameraImpl::i2cRead(81, ..., 2)
<- AtikCameraImpl::i2cRead 1 [0x4f 0x5b]
<- AtikCameraImpl::eepRead 1 [0x4f 0x5b]
serial # 1531936403
-> AtikCameraImpl::i2cSetTimeout(200)
<- AtikCameraImpl::i2cSetTimeout 1
-> AtikCameraImpl::setParTimeout(2000)
<- AtikCameraImpl::setParTimeout 1
<- AtikCameraImpl::open 1

getCapabilities

-> AtikCameraImpl::getCapabilities(...)
<- AtikCameraImpl::getCapabilities 1

setPreviewMode

-> AtikCameraImpl::setPreviewMode(0)
not changed
<- AtikCameraImpl::setPreviewMode 1

set8BitMode

-> AtikCameraImpl::set8BitMode(0)
<- AtikCameraImpl::set8BitMode 1

getTemperatureSensorStatus

-> AtikCameraImpl::getTemperatureSensorStatus(1, ...)
lock()
-> AtikCameraImpl::sendCommand(55, [0x01 0x00], ..., 2, 6)
<- AtikCameraImpl::sendCommand 1 [0x02 0x00 0xff 0x03...]
current temperature: 22.4
unlock()
<- AtikCameraImpl::getTemperatureSensorStatus 1

getCoolingStatus

-> AtikCameraImpl::getCoolingStatus(...)
lock()
-> AtikCameraImpl::sendCommand(53, NULL, ..., 0, 6)
<- AtikCameraImpl::sendCommand 1 [0x00 0x00 0x1f 0x00...]
cooler state: COOLING_INACTIVE
target temperature: -60.0
power: 0%
unlock()
<- AtikCameraImpl::getCoolingStatus 1

setCooling

-> atikSetCooling(-10.0)
lock()
-> AtikCameraImpl::sendCommand(56, [0x6c 0x02], ..., 2, 2)
<- AtikCameraImpl::sendCommand 1 [0x01 0x00]
unlock()
<- AtikCameraImpl::setCooling 1

getCoolingStatus

-> AtikCameraImpl::getCoolingStatus(...)
lock()
-> AtikCameraImpl::sendCommand(53, NULL, ..., 0, 6)
<- AtikCameraImpl::sendCommand 1 [0x00 0x00 0xdf 0x00...]
cooler state: COOLING_SETPOINT
target temperature: -10.0
power: 0%
unlock()
<- AtikCameraImpl::getCoolingStatus 1

initiateWarmUp

-> AtikCameraImpl::initiateWarmUp()
lock()
-> AtikCameraImpl::sendCommand(57, NULL, ..., 0, 0)
<- AtikCameraImpl::sendCommand 1 NULL
unlock()
<- AtikCameraImpl::initiateWarmUp 1

getCoolingStatus

-> AtikCameraImpl::getCoolingStatus(...)
lock()
-> AtikCameraImpl::sendCommand(53, NULL, ..., 0, 6)
<- AtikCameraImpl::sendCommand 1 [0xf4 0x00 0x7f 0x00...]
cooler state: WARMING_UP
target temperature: -10.0
power: 95%
unlock()
<- AtikCameraImpl::getCoolingStatus 1

readCCD (short)


3380x2704 rounded to 3380x2704

-> AtikCameraImpl::readCCD(0, 0, 3380, 2704, 1, 1, 0.500000)
lock()
-> AtikCameraImpl::setParTimeout(30000)
<- AtikCameraImpl::setParTimeout 1
-> AtikCameraImpl::sendCommand(2, [0x00 0x00], ..., 2, 0)
<- AtikCameraImpl::sendCommand 1 NULL
-> AtikCameraImpl::sendCommand(4, NULL, ..., 0, 0)
<- AtikCameraImpl::sendCommand 1 NULL
-> AtikCameraImpl::sendCommand(5, NULL, ..., 0, 0)
<- AtikCameraImpl::sendCommand 1 NULL
-> AtikCameraImpl::sendCommand(6, [0xf4 0x01 0x01 0x00...], ..., 16, 0)
<- AtikCameraImpl::sendCommand 1 NULL
<- AtikCameraImpl::readCCD 1

getImage

-> AtikCameraImpl::getImage(..., 9139520)
libusb_bulk_transfer -> LIBUSB_ERROR_IO
elapsed 0.100948 s
-> AtikCameraImpl::setParTimeout(1000)
<- AtikCameraImpl::setParTimeout 1
unlock()
<- AtikCameraImpl::getImage 0 [0x00 0x00 0x00 0x00...]

close

-> AtikCameraImpl::close()
<- AtikCameraImpl::close

Atik 490ex test failed: Failed to get image
Last edit: 7 years 6 months ago by Stephen Wong.
7 years 6 months ago #10826

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

  • Posts: 712
  • Thank you received: 174
This time it initialise correctly and failed later. Is it connected directly to USB port and is it sufficiently powered (this apply also on hub if any, but I don't recommend to use hub for such device)? Peter
7 years 6 months ago #10832

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

  • Posts: 90
  • Thank you received: 12
Hi Peter,
No I didn't connect the camera via a hub, it directly goes to one of the pi3 USB connectors. Every connection is the same when I switch and test between 1.1 and 1.6/1.7 drivers.
I also tried v1.5 and same problem occurs: while what I read from OpenSkyImager, I aware since the atik driver 1.4 version was improved on the preview mode, with some sort of USB acceleration may be? would that be the reason? Cause I saw the error starts with: libusb_bulk_transfer -> LIBUSB_ERROR_IO... so.. just a guess

Let me know what else I can try. Thank you!
7 years 6 months ago #10844

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

  • Posts: 77
  • Thank you received: 10

Replied by NickK on topic Atik 1.6 Driver problem

Could be a couple of reasons
* power on the USB - this can cause things to be a bit unpredictable. I use a powered USB hub with my C2.
* changes in timings for the drivers or possibly the length of cable/system in use can cause timing changes too.
ODROID C2 Ubuntu
7 years 6 months ago #10847

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

  • Posts: 90
  • Thank you received: 12
Hi Nick,
Thank you - but unlikely for my case, as I don't use a hub, and the same cable I used: there's no problem on 1.1, but problem always repeatable on 1.5 onwards.
7 years 6 months ago #10848

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

  • Posts: 712
  • Thank you received: 174
OK, the only way is to find the difference between working driver version and current version. BTW, does it work with 1.4 (atikccd-1.4-v7-armhf.deb)? Peter
Last edit: 7 years 6 months ago by Peter Polakovic.
7 years 6 months ago #10855

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

  • Posts: 90
  • Thank you received: 12
Hi Peter,

I'll try that tonight and post the result. BTW - is the previous versions of the driver links available (and their changelogs) somewhere so I can test may be the 1.2 & 1.3 drivers and compare and posts the results also?

Stephen
7 years 6 months ago #10864

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

Time to create page: 1.461 seconds