RA velocity of 0.15"/s added

[TRAPPIST]

Hello,

Since a couple of months I have noticed that our mount gets from time to time a velocity in RA of exactly 0.15041068619..."/s without any raison (no moving target). We then loose the data of course because the filed is drifting a lot. It looks like sideral velocities but 100x smaller !

From the driver of our NTM mount we can see that we get nearly at the same time 2 commands (see below) one setting the RA vel to to 0.01" of RA and then right after puts it to 0. But our driver is not able to make this second command because both arrive at the same time ! So sometimes this velocity reach the mount.

Do you know why ACP is sending is such a velocity (sideral/100) to the mount ? I dont see any obvious raison.
Could it come from focusMAx ?

Thank you!
Emmanuel




Log:
>2011-02-16 08:10:14.752 I =>
>execution(Telescope.setRightAscensionRate(..)) arguments('0.01')
>(external source )
>2011-02-16 08:10:14.752 I <=
>execution(Telescope.setRightAscensionRate(..)) arguments('0.01')
>return() (external source )
>2011-02-16 08:10:14.752 I =>
>execution(Telescope.setRightAscensionRate(..)) arguments('0.0')
>(external source )
>2011-02-16 08:10:14.752 I <=
>execution(Telescope.setRightAscensionRate(..)) arguments('0.0') return()
>(external source )

[Bob Denny]

Amazing. A few days ago I got another question on this and I answered it here:

http://forums.dc3.com/showthread.php?p=28094#post28094

This has been in the code for a very long time (years). It seems that we now have two drivers which don't do what they are asked to do and yet do not report an error. I have had an email from Mario at Astelco in my inbox for two weeks... I need to call him about the J2000/LocalTopo issue and point him to the ASCOM developer resources he may not have seen yet. At that time I will talk to him about this, and in general about how vital it is that the driver always do what it is asked, or report an error if it cannot.

[TRAPPIST]

Hello

this has been fixed on the level of the driver of the NTM. It now wait first command is completed before doing next one. The bug has bee fixed a week agao and since then no more problem of this kind.

Emmanuel

[Bob Denny]

Excellent.

By the way, I talked with ASTELCO on the phone and we will talk again when their developer comes back from holiday.