It seems to have the same symptoms as with our driver Wait one more day, I'll try to invite Nick (AOSX) to this discussion if he has any idea what can be wrong. I don't believe this camera is actually faulty, just somehow different

Hi Peter, Nick,

This afternoon I've called the guys at Atik and explained the situation in details.
I have been advised to test the camera under Windows first as they only support Windows.

The camera works fine on Windows XP, no issues what-so-ever, used the Artemis capture software or whatever it's called.
I can expose for 1sec to 60sec without any issues (I have not tried higher than 60 as there is no point really right now).

I then tried OpenPHD2 from Nick over at the SGL forum, I can connect to the camera fine, this is the same as if I was using Indi on Mac/RasPi/Odroid.
It connects fine.
But, when I tried to loop pictures for let's say 9s exposure.... well, that it did not work.
The camera froze, the end picture was just garbage, same output as the ones off the atik_test_ccd on Linux.



Stephane

That's bad, I have no more idea what to do

I'm sure this camera is different somehow, the firmware maybe? Who knows.
What annoys me if that it worked before on RasPI, not it doesn't anymore.

Is there a way I can check which firmware I'm running on the board?
Do you want me to open up the Titan and take a picture of it?

I do appreciate the help.
Might even consider send it to you for you to test it.

It probably make no sense to open it. Firmware is uploaded on camera connection and it is the same as used by window driver.
Are you using the same power supply for RasPI as before? Or maybe some temperature dependency...

My original PI is gone, gave it to a friend at work.
I have two B+ and one model A

I'm going to format my SD card and test it on a fresh install on the A model.

edit:
scrap that idea, I remember how much of a pain it is on a Model a with a single USB port....

Hi,

running atik_ccd_test just after connecting my Atik Titan gives the same timeout error and the test fails (see test.txt).
At this state ekos can't capture images from the camera, it hangs on downloading the image.
But after taking a long exposure (5 minutes) with Ekos, all works fine. Closing ekos and running
atik_ccd_test again now gives 'Atik Titan test OK' (see test2.txt).

So the procedure to get my Titan working is:

1. Connect the camera to USB
2. start indiserver
3. connect ekos to the camera
4. take a 5 minute exposure

After that I can also take short exposures.
This behaviour occurs on PC with 32 and 64 bit Kubuntu 15.04, 32 Bit Lubuntu 14.10 and rasbian & fedora on bananaPi.

Best regards

Strange, but good to know. Peter

hi guys,

---

So the procedure to get my Titan working is:

Connect the camera to USB
start indiserver
connect ekos to the camera
take a 5 minute exposure

---

I will try this.

JB

BTW, how long are your short exposures? The hardcoded threshold for using short (camera timed) a long (computer timed) exposure is 0.5s so from software point of view there is no difference between 1s, 1 minute or 5 minute exposure. Peter

Hi,
sorry for my late reply.

Last night I found the reason for the strange behavior of my Titan. It is the temperature. Yesterday I setup my scope on daylight and all works like a charm. After dusk I polar align the mount. Ready to start to get pretty pictures. But the Titan says no. No chance to get a single image from the Titan. I wonder why the Titan works in the afternoon but not in the night. And then I've got it: the temperature changed. So I heaten the camera's body with a hair dryer and the Titan works again.

Under room temperatur condition the 5 minute exposure seems to suffices to warm up the camera electronics. Maybe the frequency change in respond to the crystal oscillator's temperature coefficient is big enough to break the timing of the atik driver. My Titan works normal with windows.

With short exposures I mean everything shorter than a minute or so (0.01 s to 60 s).