I have been seeking help with some error messages from CCDap when using the TCC controlled PIR from RCOS. If I link the TCC to the sky I get the message "TheSky has rotated" "Rotate PIR to new TheSky Rotation" or "Cancel TheSky Rotation". I was told NOT to link the TCC to the Sky. OK...I did that and no longer get "that" message. Now a new message appears in the log file "TCC failed to report IsMoving as false after 120 sec"...I have included a sample log file showing the message. Now what am I doing wrong? HELP!

Norm

PIR.txt (4 KB, 52 downloads)

Norm,

Ignore that error message. That is the result of an incorrect watchdog timer entry in CCDAP and will be corrected in a future update, pending testing.

BTW, setting your minimum exposure to .11 sec will not give usable flats. In order to avoid shutter effects from biasing your flats, you should set the minimum exposure to no less than 2 sec.

Hi John
I have been seeing this error lately also..but I think it might be connected with something else..PIR Wrap Limits. I caught this error tonight and checked TCC, I could see that the rotator was sent to a position that exceeded the wrap limit, but of course, TCC would not drive the PIR beyond the wrap limit hence the error occurred. I do have "Automatically reverse PIR when wrap limit exceeded" checked in the PIR options tab, but it might be that CCDAP is timing out waiting for the PIR to unwrap.

What do you think?

cheers

Martin

Hi Martin,

Do you have the original TCC, or the newer TCC II? And what is the value of your wrap limit setting?

Hi Frank
I have the original TCC and my wrap limit is 370.

thanks
Martin

As was mentionned by John, there seems to be an error in the CCDAP code itself when it comes to measuring the timeout of a TCC response to a rotation command. CCDAP is not waiting for 120 seconds to report that "TCC failed to report IsMoving as false after 120 sec"...

I believe John has fixed this for future releases.
Emmanuel

Hi Martin,

Would that be a bit too high? I have my wrap limit set to +/- 190 and it has access to all 360 degree locations and and should never hit the 120 sec error. Maybe you are sending the PIR too far in one direction and it is taking too long to get back all the way around when the "limit" is being exceeded?

Hi Frank
yes, most definitely...and I like your idea there...I will set my limits to 190 and see what happens.

thanks for your advice.

Martin

I have my limit set at 190, and it works fine. But even with that setting, you can get the timeout message from CCDAP, for the reason explained in my previous post.

Emmanuel

If you update from the web to version 3.42.3 posted yesterday, you should no longer get the timeout.

I have upgraded to 3.42.3 and after several tests last night I was not able to replicate the timeout message.

Many thanks John.

Note that my wrap limit on the TCC is set at 190°

Emmanuel

Thanks for the feedback, Emmanuel. I normally have my wrap limit close to yours at 200.