ASCOM-Talk : Messages : 21714-21743 of 29969

I just tried to uninstall ASCOM but it encountered an unexpected error. The
error code 2869.

--- In ASCOM-Talk@yahoogroups.com, "mikael_johannesen" <dsl29721@...> wrote:
>
> Vista Home Premium 32 bit.
>
> --- In ASCOM-Talk@yahoogroups.com, "dc3dreamer" <rdenny@> wrote:
> >
> > 0x5 is also "access denied" in Microsoft gobbledegook speak. What OS are you
running (Vista or 7)? Is there anything "special" about it? You've already done
the right things.
> >
> >   --- Bob
> >
> > --- In ASCOM-Talk@yahoogroups.com, "mikael_johannesen" <dsl29721@> wrote:
> > >
> > > Hi
> > >
> > > I too have gotten the dreaded error
> > >
> > > C:\Program Files\Common Files\ASCOM\Helper.dll
> > > Unable to register DLL/OCX: RegSvr32 failed with exit code 0x5
> > >
> > > I have UAC turned off and running installation as admin doesn't help
either. I can't register the dll manually either it comes back with another
error code - access denied.
> > >
> > > Has this issue been resolved or does anyone have a clue how to fix it?
> > >
> >
>

#21715

From: "Tim Long" <Tim@...>
Date: Wed Sep 1, 2010 11:07 am
Subject: RE: [ASCOM] Re: ASCOM 5.5 install and RegSvr32 error

t_p_long

At this point, you seem to be stuck in the quicksand. You can't complete
the install and you can't uninstall. The cause is unknown but it looks
like you have a permissions problem, either in your filesystem on in the
registry. The ASCOM installer is known to work on a correctly configured
system with standard permissions, so this must be something peculiar to
your system.

The best suggestion I have at this point is to use System Restore to
back out all of the failed installs/uninstalls, then try to double-check
your file and registry permissions against another computer.

--Tim Long

> -----Original Message-----
> From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-
> Talk@yahoogroups.com] On Behalf Of mikael_johannesen
> Sent: 01 September 2010 06:35
> To: ASCOM-Talk@yahoogroups.com
> Subject: [ASCOM] Re: ASCOM 5.5 install and RegSvr32 error
>
> I just tried to uninstall ASCOM but it encountered an unexpected
error. The
> error code 2869.
>
> --- In ASCOM-Talk@yahoogroups.com, "mikael_johannesen" <dsl29721@...>
> wrote:
> >
> > Vista Home Premium 32 bit.
> >
> > --- In ASCOM-Talk@yahoogroups.com, "dc3dreamer" <rdenny@> wrote:
> > >
> > > 0x5 is also "access denied" in Microsoft gobbledegook speak. What
OS are
> you running (Vista or 7)? Is there anything "special" about it? You've
already
> done the right things.
> > >
> > >   --- Bob
> > >
> > > --- In ASCOM-Talk@yahoogroups.com, "mikael_johannesen" <dsl29721@>
> wrote:
> > > >
> > > > Hi
> > > >
> > > > I too have gotten the dreaded error
> > > >
> > > > C:\Program Files\Common Files\ASCOM\Helper.dll Unable to
register
> > > > DLL/OCX: RegSvr32 failed with exit code 0x5
> > > >
> > > > I have UAC turned off and running installation as admin doesn't
help
> either. I can't register the dll manually either it comes back with
another error
> code - access denied.
> > > >
> > > > Has this issue been resolved or does anyone have a clue how to
fix it?
> > > >
> > >
> >
>
>
>
>
> ------------------------------------
>
> For more information see http://ASCOM-Standards.org/.
>
> To unsubscribe from this group, send an email FROM THE ACCOUNT YOU
USED
> TO SUBSCRIBE(!) to:
> ASCOM-Talk-unsubscribe@yahoogroups.com
>
> Yahoo! Groups Links
>
>
>

--
ExchangeDefender Message Security: Click below to verify authenticity
http://www.exchangedefender.com/verify.asp?id=o81B7e0o002678&from=tim@tigranetwo\
rks.co.uk
Complete email hygeine and business continuity solution available from
http://www.tigranetworks.co.uk

#21716

From: "Franklin" <frank@...>
Date: Wed Sep 1, 2010 3:23 pm
Subject: Temperature Casting Workarounds???

f_holub

I'm just getting my feet wet with some ASCOM programming and have run into a bug. I know from this thread that this is a known issue. Basically the Lacey EasyFocus driver seems to cast Temperature as a float instead of a double. VS C# seems to really hate this. The above thread mentions some speculation on some workarounds but no real solutions. I have a note in to James Lacey but I see the driver hasn't been updated since 2006 so I'm not getting my hopes up.
I have tried some of the conjectured at solutions but still get errors...

using InvokeMember gets me...

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.InvalidCastException: Specified cast is not valid. at ASCOM.DriverAccess.Focuser.get_Temperature()

I get cast exceptions with pretty much everything.

Did anyone actually come up with a solution and have a nice code example?

Frank

BTW - I know the driver CAN work... The following VBS script works fine...

Set Focuser = CreateObject("EasyFocus.Focuser")
Focuser.Link = True
WScript.Echo Focuser.Temperature

#21717

From: "dc3dreamer" <rdenny@...>
Date: Wed Sep 1, 2010 6:11 pm
Subject: Re: Matlab example

dc3dreamer

Hello --

> I'd like to control my scope from Matlab, but I've no experience in programming with Ascom.

> Isn't there a simple example in Matlab that shows how to connect the scope and to send move commands?

No, but I made one up for you:

% Search MATLAB help for "COM"... I am running R2007b by the way

% Use the ASCOM Helper docs for the Chooser and Util API

% Displaying the Chooser lets you open the driver's setup dialog

C = actxserver('DriverHelper.Chooser');

U = actxserver('DriverHelper.Util');

% Remember last selected telescope or initialize to no selection

try

ScopeID = C.Choose(ScopeID);

catch ME

ScopeID = 'ScopeSim.Telescope'; %Default to simulator

end

fprintf(1, '\nChosen scope has ID %s\n', ScopeID);

if ScopeID == 'ScopeSim.Telescope'

input('Restore the Scope Simulator window so you can see it, then press enter:');

end

% Use the ASCOM Telescope V3 Reference for the API

T = actxserver(ScopeID);

T.Connected = true;

RASexa = U.HoursToHMS(T.RightAscension);

DESexa = U.DegreesToDMS(T.Declination);

fprintf(1, 'Initial RA=%s DE=%s\n', RASexa, DESexa);

T.Tracking = true;

% Slew to 1 hour east of meridian

fprintf(1, 'Slewing...\n');

T.SlewToCoordinatesAsync(T.SiderealTime + 1, T.Declination);

while T.Slewing

fprintf(1, '.');

U.WaitForMilliseconds(500);

end

fprintf(1, '\nSlew complete, look at scope\n');

T.Tracking = false;

T.Connected = false;

Reply | Messages in this Topic (6)

#21718

From: "dc3dreamer" <rdenny@...>
Date: Wed Sep 1, 2010 6:15 pm
Subject: Re: Matlab example

dc3dreamer

PS: If you selected Simulator for the Telescope, and you didn't hand-start the
ASCOM Telescope Simulator, then deleting the T variable from your workspace will
cause the simulator to auto-release and exit.

Reply | Messages in this Topic (6)

#21719

From: "dc3dreamer" <rdenny@...>
Date: Wed Sep 1, 2010 6:24 pm
Subject: Re: Temperature Casting Workarounds???

dc3dreamer

I assume your code works with the Focuser Simulator. If so, then the problem is
the broken Lacy driver,  not your code or the Client Toolkit wrapper.

If you decide that your application will contain a hack for the broken Lacey
driver, you could lift the code from the Client Toolkit and modify it to work
with the Lacey driver. Once you get that code working, then put your app's
normal call in a try block, and add a catch for the invoke error, and instead
execute your hack.

I can't think of another solution short of fixing the driver. Would you like to
try that? Is the source available?

   -- Bob

--- In ASCOM-Talk@yahoogroups.com, "Franklin" <frank@...> wrote:
>
> I'm just getting my feet wet with some ASCOM programming and have run
> into a bug. [...]

#21720

From: "dc3dreamer" <rdenny@...>
Date: Wed Sep 1, 2010 6:31 pm
Subject: Re: [ASCOM] 12" LX200 Classic Issues with 5.x?

dc3dreamer

Ok, I understand now. I'm afraid I am in no position to fix it. Seemingly, with
the later driver, PHD's calls to the driver and their timing does something that
triggers a problem in the driver/controller combination. I am confident that the
commands being sent to the scope are correct for the driver calls being made by
PHD, but I don't know if the combination of commands and their timing is causing
the scope to misbehave. The difference between the  old driver and the new one
is a clue.

With that said, there is an open "issue" on the ASCOM developer list that
describes something similar - something about asking for the RA/Dec while a
"small" slew is in progress. Perhaps some else can amplify? I am not in a
position to do this research now, maybe someone is already plugged in and can
help?

   -- Bob

--- In ASCOM-Talk@yahoogroups.com, "lecza" <lecza@...> wrote:
>
> With the 5.x platform/drivers installed PHD guiding was having trouble getting
through the calibration phase.  When calibrating West the star would move a
little then drift back the other way.  I cannot tell if the scope is not getting
the commands at all (and the "drifting" is just PE) or if they are just not
right.  I've tried listening to the mount but its very quiet when guiding anyway
so I cannot tell if 5.x is actually guiding at all.
>
> Slewing in TheSky6 works fine with 5.x.
>
> With the 4.1 platform/drivers I see the proper start movement in PHD during
the calibration step and once calibration is complete it appears to guide
properly.
>
> I have uninstalled/reinstalled 4.1 and 5.x several times to ensure consistent
behavior.  Its always the same.  4.1 works fine for guiding and 5.x does not.
>
> Let me know is there is anymore information that you need.  This week looks
like its going to be very clear and I have left my scope outside setup and ready
to go.
>
> Thanks!
>
> --- In ASCOM-Talk@yahoogroups.com, "dc3dreamer" <rdenny@> wrote:
> >
> > Here I am... But I'm not the author of the driver, and I don't know what
"doesn't work" means :-)) I suspect (with no foundation) that the driver that
got installed as part of the ancient ASCOM 4 platform (which includes some very
old drivers) is somehow working for you., while the current driver had some
problem?
> >
> > Can you describe what problem you had initially?
> >
>

Reply | Messages in this Topic (8)

#21721

From: "mikael_johannesen" <dsl29721@...>
Date: Wed Sep 1, 2010 8:52 pm
Subject: [ASCOM] Re: ASCOM 5.5 install and RegSvr32 error

mikael_johan...

Your proposal to alter registry permissions promoted me to google for that and
found this:
http://www.windowsreference.com/security/reset-the-entire-registry-permissions-t\
o-defaults/

That fixed my problem and ASCOM installed without a problem.

Mikael

--- In ASCOM-Talk@yahoogroups.com, "Tim Long" <Tim@...> wrote:
>
> At this point, you seem to be stuck in the quicksand. You can't complete
> the install and you can't uninstall. The cause is unknown but it looks
> like you have a permissions problem, either in your filesystem on in the
> registry. The ASCOM installer is known to work on a correctly configured
> system with standard permissions, so this must be something peculiar to
> your system.
>
> The best suggestion I have at this point is to use System Restore to
> back out all of the failed installs/uninstalls, then try to double-check
> your file and registry permissions against another computer.
>
> --Tim Long
>
> > -----Original Message-----
> > From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-
> > Talk@yahoogroups.com] On Behalf Of mikael_johannesen
> > Sent: 01 September 2010 06:35
> > To: ASCOM-Talk@yahoogroups.com
> > Subject: [ASCOM] Re: ASCOM 5.5 install and RegSvr32 error
> >
> > I just tried to uninstall ASCOM but it encountered an unexpected
> error. The
> > error code 2869.
> >
> > --- In ASCOM-Talk@yahoogroups.com, "mikael_johannesen" <dsl29721@>
> > wrote:
> > >
> > > Vista Home Premium 32 bit.
> > >
> > > --- In ASCOM-Talk@yahoogroups.com, "dc3dreamer" <rdenny@> wrote:
> > > >
> > > > 0x5 is also "access denied" in Microsoft gobbledegook speak. What
> OS are
> > you running (Vista or 7)? Is there anything "special" about it? You've
> already
> > done the right things.
> > > >
> > > >   --- Bob
> > > >
> > > > --- In ASCOM-Talk@yahoogroups.com, "mikael_johannesen" <dsl29721@>
> > wrote:
> > > > >
> > > > > Hi
> > > > >
> > > > > I too have gotten the dreaded error
> > > > >
> > > > > C:\Program Files\Common Files\ASCOM\Helper.dll Unable to
> register
> > > > > DLL/OCX: RegSvr32 failed with exit code 0x5
> > > > >
> > > > > I have UAC turned off and running installation as admin doesn't
> help
> > either. I can't register the dll manually either it comes back with
> another error
> > code - access denied.
> > > > >
> > > > > Has this issue been resolved or does anyone have a clue how to
> fix it?
> > > > >
> > > >
> > >
> >
> >
> >
> >
> > ------------------------------------
> >
> > For more information see http://ASCOM-Standards.org/.
> >
> > To unsubscribe from this group, send an email FROM THE ACCOUNT YOU
> USED
> > TO SUBSCRIBE(!) to:
> > ASCOM-Talk-unsubscribe@yahoogroups.com
> >
> > Yahoo! Groups Links
> >
> >
> >
>
> --
> ExchangeDefender Message Security: Click below to verify authenticity
> http://www.exchangedefender.com/verify.asp?id=o81B7e0o002678&from=tim@...
> Complete email hygeine and business continuity solution available from
http://www.tigranetworks.co.uk
>

#21722

From: "Franklin" <frank@...>
Date: Wed Sep 1, 2010 7:00 pm
Subject: Re: Temperature Casting Workarounds???

f_holub

Thanks for the reply! Yes, the "normal" code works perfectly with the
simulator. The invoke code was just an attempt to get around this cast
issue.  Right now I would be happy if I simply had a code snippet that
can actually read the Temperature value from the EasyFocuser driver in
C#. If I get there I will definitely do as you suggest and catch the
exception.

Frank

--- In ASCOM-Talk@yahoogroups.com, "dc3dreamer" <rdenny@...> wrote:
>
> I assume your code works with the Focuser Simulator. If so, then the
problem is the broken Lacy driver,  not your code or the Client Toolkit
wrapper.
>
> If you decide that your application will contain a hack for the broken
Lacey driver, you could lift the code from the Client Toolkit and modify
it to work with the Lacey driver. Once you get that code working, then
put your app's normal call in a try block, and add a catch for the
invoke error, and instead execute your hack.
>
> I can't think of another solution short of fixing the driver. Would
you like to try that? Is the source available?
>
>   -- Bob
>
> --- In ASCOM-Talk@yahoogroups.com, "Franklin" frank@ wrote:
> >
> > I'm just getting my feet wet with some ASCOM programming and have
run
> > into a bug. [...]
>

#21723

From: "Tim Long" <Tim@...>
Date: Thu Sep 2, 2010 1:53 am
Subject: RE: [ASCOM] Re: ASCOM 5.5 install and RegSvr32 error

t_p_long

Glad that helped. That's a really useful link, too.
--Tim

> -----Original Message-----
> From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-
> Talk@yahoogroups.com] On Behalf Of mikael_johannesen
> Sent: 01 September 2010 21:53
> To: ASCOM-Talk@yahoogroups.com
> Subject: [ASCOM] Re: ASCOM 5.5 install and RegSvr32 error
>
> Your proposal to alter registry permissions promoted me to google for
that and
> found this:
> http://www.windowsreference.com/security/reset-the-entire-registry-
> permissions-to-defaults/
>
> That fixed my problem and ASCOM installed without a problem.
>
> Mikael
>
> --- In ASCOM-Talk@yahoogroups.com, "Tim Long" <Tim@...> wrote:
> >
> > At this point, you seem to be stuck in the quicksand. You can't
> > complete the install and you can't uninstall. The cause is unknown
but
> > it looks like you have a permissions problem, either in your
> > filesystem on in the registry. The ASCOM installer is known to work
on
> > a correctly configured system with standard permissions, so this
must
> > be something peculiar to your system.
> >
> > The best suggestion I have at this point is to use System Restore to
> > back out all of the failed installs/uninstalls, then try to
> > double-check your file and registry permissions against another
computer.
> >
> > --Tim Long
> >
> > > -----Original Message-----
> > > From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-
> > > Talk@yahoogroups.com] On Behalf Of mikael_johannesen
> > > Sent: 01 September 2010 06:35
> > > To: ASCOM-Talk@yahoogroups.com
> > > Subject: [ASCOM] Re: ASCOM 5.5 install and RegSvr32 error
> > >
> > > I just tried to uninstall ASCOM but it encountered an unexpected
> > error. The
> > > error code 2869.
> > >
> > > --- In ASCOM-Talk@yahoogroups.com, "mikael_johannesen" <dsl29721@>
> > > wrote:
> > > >
> > > > Vista Home Premium 32 bit.
> > > >
> > > > --- In ASCOM-Talk@yahoogroups.com, "dc3dreamer" <rdenny@> wrote:
> > > > >
> > > > > 0x5 is also "access denied" in Microsoft gobbledegook speak.
> > > > > What
> > OS are
> > > you running (Vista or 7)? Is there anything "special" about it?
> > > You've
> > already
> > > done the right things.
> > > > >
> > > > >   --- Bob
> > > > >
> > > > > --- In ASCOM-Talk@yahoogroups.com, "mikael_johannesen"
> > > > > <dsl29721@>
> > > wrote:
> > > > > >
> > > > > > Hi
> > > > > >
> > > > > > I too have gotten the dreaded error
> > > > > >
> > > > > > C:\Program Files\Common Files\ASCOM\Helper.dll Unable to
> > register
> > > > > > DLL/OCX: RegSvr32 failed with exit code 0x5
> > > > > >
> > > > > > I have UAC turned off and running installation as admin
> > > > > > doesn't
> > help
> > > either. I can't register the dll manually either it comes back
with
> > another error
> > > code - access denied.
> > > > > >
> > > > > > Has this issue been resolved or does anyone have a clue how
to
> > fix it?
> > > > > >
> > > > >
> > > >
> > >
> > >
> > >
> > >
> > > ------------------------------------
> > >
> > > For more information see http://ASCOM-Standards.org/.
> > >
> > > To unsubscribe from this group, send an email FROM THE ACCOUNT YOU
> > USED
> > > TO SUBSCRIBE(!) to:
> > > ASCOM-Talk-unsubscribe@yahoogroups.com
> > >
> > > Yahoo! Groups Links
> > >
> > >
> > >
> >
> > --
> > ExchangeDefender Message Security: Click below to verify
authenticity
> >
> http://www.exchangedefender.com/verify.asp?id=o81B7e0o002678&from=tim
> @...
> > Complete email hygeine and business continuity solution available
from
> > http://www.tigranetworks.co.uk
> >
>
>
>
>
> ------------------------------------
>
> For more information see http://ASCOM-Standards.org/.
>
> To unsubscribe from this group, send an email FROM THE ACCOUNT YOU
USED
> TO SUBSCRIBE(!) to:
> ASCOM-Talk-unsubscribe@yahoogroups.com
>
> Yahoo! Groups Links
>
>
>

--
ExchangeDefender Message Security: Click below to verify authenticity
http://www.exchangedefender.com/verify.asp?id=o821rUD8006799&from=tim@tigranetwo\
rks.co.uk
Complete email hygeine and business continuity solution available from
http://www.tigranetworks.co.uk

#21724

From: "dc3dreamer" <rdenny@...>
Date: Thu Sep 2, 2010 5:25 am
Subject: [ASCOM] Re: ASCOM 5.5 install and RegSvr32 error

dc3dreamer

I'm curious how the registry permissions got altered in a way that prevented the
install from succeeding. It might help others in the future.

#21725

From: "mikael_johannesen" <dsl29721@...>
Date: Thu Sep 2, 2010 6:19 am
Subject: [ASCOM] Re: ASCOM 5.5 install and RegSvr32 error

mikael_johan...

I have no idea.

--- In ASCOM-Talk@yahoogroups.com, "dc3dreamer" <rdenny@...> wrote:
>
> I'm curious how the registry permissions got altered in a way that prevented
the install from succeeding. It might help others in the future.
>

#21726

From: Chris Rowland <chris_group_mail@...>
Date: Thu Sep 2, 2010 8:11 am
Subject: Re: [ASCOM] Re: Temperature Casting Workarounds???

scope_sapiens

The problem with the EasyFocus driver means that the driver toolkit
can't be used, but there's no reason why an application shouldn't
replicate what the driver toolkit does.

I've just posted a new version (5.5.3) of the temperature compensated
focuser driver that works with the easyfocus driver. The source code
shows one way to handle this, it takes the driver toolkit code and
replaces the casts with Convert calls. These are less fussy about the
return type so copes with this problem.

Chris

Franklin wrote:
> Thanks for the reply! Yes, the "normal" code works perfectly with the
> simulator. The invoke code was just an attempt to get around this cast
> issue.  Right now I would be happy if I simply had a code snippet that
> can actually read the Temperature value from the EasyFocuser driver in
> C#. If I get there I will definitely do as you suggest and catch the
> exception.
>
> Frank
>
> --- In ASCOM-Talk@yahoogroups.com, "dc3dreamer" <rdenny@...> wrote:
>> I assume your code works with the Focuser Simulator. If so, then the
> problem is the broken Lacy driver,  not your code or the Client Toolkit
> wrapper.
>> If you decide that your application will contain a hack for the broken
> Lacey driver, you could lift the code from the Client Toolkit and modify
> it to work with the Lacey driver. Once you get that code working, then
> put your app's normal call in a try block, and add a catch for the
> invoke error, and instead execute your hack.
>> I can't think of another solution short of fixing the driver. Would
> you like to try that? Is the source available?
>>   -- Bob
>>
>> --- In ASCOM-Talk@yahoogroups.com, "Franklin" frank@ wrote:
>>> I'm just getting my feet wet with some ASCOM programming and have
> run
>>> into a bug. [...]
>
>
>
>
> ------------------------------------
>
> For more information see http://ASCOM-Standards.org/.
>
> To unsubscribe from this group, send an email FROM THE ACCOUNT YOU USED TO
SUBSCRIBE(!) to:
> ASCOM-Talk-unsubscribe@yahoogroups.com
>
> Yahoo! Groups Links
>
>
>
>
> ------------------------------------------------------------------------
>
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 9.0.851 / Virus Database: 271.1.1/3105 - Release Date: 08/31/10
19:34:00
>

#21727

From: "Tim Long" <Tim@...>
Date: Thu Sep 2, 2010 9:49 am
Subject: RE: [ASCOM] Re: ASCOM 5.5 install and RegSvr32 error

t_p_long

Bob, Mikael:

I don't know how it's happening but this registry permissions thing is
something I've seen a few times now in relation to ASCOM. It could be
malware, group policy, or some kind of security hardening tool, or a
registry cleaner. Do any of these apply in this situation? It would be
very helpful to narrow this down...

--Tim Long

> -----Original Message-----
> From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-
> Talk@yahoogroups.com] On Behalf Of dc3dreamer
> Sent: 02 September 2010 06:26
> To: ASCOM-Talk@yahoogroups.com
> Subject: [ASCOM] Re: ASCOM 5.5 install and RegSvr32 error
>
> I'm curious how the registry permissions got altered in a way that
prevented
> the install from succeeding. It might help others in the future.
>
>
>
> ------------------------------------
>
> For more information see http://ASCOM-Standards.org/.
>
> To unsubscribe from this group, send an email FROM THE ACCOUNT YOU
USED
> TO SUBSCRIBE(!) to:
> ASCOM-Talk-unsubscribe@yahoogroups.com
>
> Yahoo! Groups Links
>
>
>

--
ExchangeDefender Message Security: Click below to verify authenticity
http://www.exchangedefender.com/verify.asp?id=o829nMgT016765&from=tim@tigranetwo\
rks.co.uk
Complete email hygeine and business continuity solution available from
http://www.tigranetworks.co.uk

#21728

From: "loreastro" <comolli@...>
Date: Thu Sep 2, 2010 9:08 am
Subject: Re: Matlab example

loreastro

Dear Rob,
I'd like to thank you very much for your extremely detailed reply! I'll try to
implement in my sw asap.

Regards,
Lorenzo

Reply | Messages in this Topic (6)

#21729

From: "Franklin" <frank@...>
Date: Thu Sep 2, 2010 5:01 pm
Subject: [ASCOM] Re: Temperature Casting Workarounds???

f_holub

Hi Chris,

I looked at your code and tried as best I could to replicate the Convert calls,
but I still get a cast exception and/or a System.NullReferenceException. I guess
I'm not setting up the types and objects correctly for the invoke.
Anyway, Right now everything works great going through the POTH.Hub or your
CompensatedFocuser driver. I think I might just disable Temp when using
EasyFocus until I get good enough to figure this one out.

Frank

--- In ASCOM-Talk@yahoogroups.com, Chris Rowland <chris_group_mail@...> wrote:
>
> The problem with the EasyFocus driver means that the driver toolkit
> can't be used, but there's no reason why an application shouldn't
> replicate what the driver toolkit does.
>
> I've just posted a new version (5.5.3) of the temperature compensated
> focuser driver that works with the easyfocus driver. The source code
> shows one way to handle this, it takes the driver toolkit code and
> replaces the casts with Convert calls. These are less fussy about the
> return type so copes with this problem.
>
> Chris
>
> Franklin wrote:
> > Thanks for the reply! Yes, the "normal" code works perfectly with the
> > simulator. The invoke code was just an attempt to get around this cast
> > issue.  Right now I would be happy if I simply had a code snippet that
> > can actually read the Temperature value from the EasyFocuser driver in
> > C#. If I get there I will definitely do as you suggest and catch the
> > exception.
> >
> > Frank
> >
> > --- In ASCOM-Talk@yahoogroups.com, "dc3dreamer" <rdenny@> wrote:
> >> I assume your code works with the Focuser Simulator. If so, then the
> > problem is the broken Lacy driver,  not your code or the Client Toolkit
> > wrapper.
> >> If you decide that your application will contain a hack for the broken
> > Lacey driver, you could lift the code from the Client Toolkit and modify
> > it to work with the Lacey driver. Once you get that code working, then
> > put your app's normal call in a try block, and add a catch for the
> > invoke error, and instead execute your hack.
> >> I can't think of another solution short of fixing the driver. Would
> > you like to try that? Is the source available?
> >>   -- Bob
> >>
> >> --- In ASCOM-Talk@yahoogroups.com, "Franklin" frank@ wrote:
> >>> I'm just getting my feet wet with some ASCOM programming and have
> > run
> >>> into a bug. [...]
> >
> >
> >
> >
> > ------------------------------------
> >
> > For more information see http://ASCOM-Standards.org/.
> >
> > To unsubscribe from this group, send an email FROM THE ACCOUNT YOU USED TO
SUBSCRIBE(!) to:
> > ASCOM-Talk-unsubscribe@yahoogroups.com
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
> > ------------------------------------------------------------------------
> >
> >
> > No virus found in this incoming message.
> > Checked by AVG - www.avg.com
> > Version: 9.0.851 / Virus Database: 271.1.1/3105 - Release Date: 08/31/10
19:34:00
> >
>

#21730

From: "Tom" <tom_krajci@...>
Date: Thu Sep 2, 2010 6:50 pm
Subject: [ASCOM] Re: Temperature Casting Workarounds???

tom_krajci

--- In ASCOM-Talk@yahoogroups.com, "Franklin" <frank@...> wrote:

>...I think I might just disable Temp when using EasyFocus until I
> get good enough to figure this one out.

Will you disable temp. comp. in the EasyFocus driver, or in the Temperature
Compensated Focuser shim that Chris is developing?

--
-------------------------------------------
Tom Krajci
Cloudcroft, New Mexico
http://picasaweb.google.com/tom.krajci

Center for Backyard Astrophysics (CBA)
http://cbastro.org/ CBA New Mexico

American Association of Variable Star
Observers (AAVSO): KTC http://www.aavso.org/
-------------------------------------------

#21731

From: "Tom" <tom_krajci@...>
Date: Thu Sep 2, 2010 7:59 pm
Subject: Temperature compensated focuser 'shim' 5.5.3 - initial test findings

tom_krajci

Here are some initial findings based on indoor testing of the temp. compensated
focuser shim 5.5.3 and FocusMax 3.5.24Beta...coupled to my MoonLite/EasyFocus
ASCOM focuser driver and MoonLite focuser.

This 'shim' will adjust the focuser's physical position as temperature
changes...but is supposed to keep the focuser step value constant.  In other
words you'll see the focuser move in/out as temperature changes, but it sends a
temp. compensated focus position value to FocusMax.  If you don't move the
focuser for filter offsets, or any other reason...then the reported focus
position should remain constant.

Here's output from the FocusMax temperature log:

12:04:53  Position = 1505  Temp = 25.5
12:05:11  Position = 1510  Temp = 25.0
12:05:30  Position = 1511  Temp = 25.0
12:05:47  Position = 1510  Temp = 25.5
12:06:09  Position = 1505  Temp = 25.5
12:06:29  Position = 1506  Temp = 25.0
12:06:48  Position = 1510  Temp = 25.0
12:07:12  Position = 1505  Temp = 25.5
12:07:38  Position = 1511  Temp = 25.5
12:07:55  Position = 1511  Temp = 25.5
12:08:15  Position = 1505  Temp = 25.5
12:08:34  Position = 1505  Temp = 25.5
12:08:59  Position = 1505  Temp = 25.0
12:09:18  Position = 1511  Temp = 25.0
12:09:43  Position = 1505  Temp = 25.0
12:10:08  Position = 1506  Temp = 25.5
12:10:32  Position = 1506  Temp = 25.5
12:11:17  Position = 1511  Temp = 25.5
12:11:54  Position = 1511  Temp = 25.5
12:12:33  Position = 1505  Temp = 25.5
12:13:06  Position = 1506  Temp = 25.5
12:13:36  Position = 1505  Temp = 25.5
12:18:41  Position = 1505  Temp = 25.5

I had the temperature reading rate set fast...but note that there is still some
'jitter' in reported focuser position...even when temperature remains constant
for some time interval.

FocusMax 3.5.24Beta is awful sluggish when connected to this focuser shim, and
here is the probable reason:

12:11:19   Position: 1508
12:11:20   Temperature: 25.50
12:11:25   IsMoving: True
12:11:25   Position: 1505
12:11:26   Temperature: 25.50
12:11:51   IsMoving: True
12:11:52   Temperature: 25.50
12:11:54   Position: 1508
12:11:55   Temperature: 25.50
12:11:59   IsMoving: True
12:11:59   Position: 1506
12:12:01   Temperature: 25.50
12:12:07   IsMoving: True
12:12:07   Position: 1505
12:12:08   Temperature: 25.50
12:12:26   IsMoving: True
12:12:27   Temperature: 25.50
12:12:33   Position: 1508
12:12:34   Temperature: 25.50
12:12:59   IsMoving: True
12:13:00   Temperature: 25.50
12:13:06   Position: 1508
12:13:07   Temperature: 25.50
12:13:30   IsMoving: True
12:13:31   Temperature: 25.50
12:13:37   Position: 1508
12:13:38   Temperature: 25.50
12:18:34   IsMoving: True
12:18:35   Temperature: 25.50
12:18:41   Position: 1508
12:18:42   Temperature: 25.50

The temp. compensated focuser shim is always reporting that it's moving...even
when it's not.  If I try and use the FocusMax jog feature...it takes a very long
time for the system to respond...or the software simply hangs.

If I try and click on the Setup button in FocusMax (to adjust some ASCOM driver
parameters)...FocusMax 3.5.24beta either hangs, or reports an error that the
port is closed, crashes and disappears.

All for now.

--
-------------------------------------------
Tom Krajci
Cloudcroft, New Mexico
http://picasaweb.google.com/tom.krajci

Center for Backyard Astrophysics (CBA)
http://cbastro.org/ CBA New Mexico

American Association of Variable Star
Observers (AAVSO): KTC http://www.aavso.org/
-------------------------------------------

#21732

From: Chris Rowland <chris_group_mail@...>
Date: Thu Sep 2, 2010 11:07 pm
Subject: Re: [ASCOM] Temperature compensated focuser 'shim' 5.5.3 - initial test findings

scope_sapiens

What values did you set for temperature coefficient and Offset?

Can you note what the display on the moonlite focuser box says?

Did you have temperature compensation turned on or off?

It may be worth setting the min move parameter to avoid continual small
moves.

What I found using my test focuser driver was that the reported focus
position would jitter by a small amount - 5 steps with a coefficient of
100 steps per degree - but would not drift. The position reported on the
box did change as you would expect. That was with a 10 second moving
average.

The focuser would report moving when the focuser was doing a
compensation move but not when it wasn't. Your focusmax log shows it
moving all the time so it might be correctly reporting moving because it is.

The focuser shim isn't expecting that the setup dialog will be called
when it's connected. It could easily not be trapping errors, this was
developed quickly in order to determine if the principle of this style
of temperature compensation works rather than make it bullet proof.

What seems to happen with the EasyFocus driver is that it reports the
temperature to the nearest 0.1 deg and the value read is jittering by
0.1 or 0.2 deg.  If you want to stop jitter then the number of samples
must be enough that a 0.2 deg change divided by the number of samples
and multiplied by the temperature coefficient must give less than one step.

If a min step is set then the reported position will change until the
min step is reached, then there will be a single larger movement and the
value will return to close to the target position.

The various errors in temperature measurement and position will tend to
mean that values will not be exact to the step. There may be rounding
errors getting in the way. I would not expect drift though.

What's important is that once a temperature coefficient for the scope
and focuser has been determined the scope stays in focus as the
temperature changes. It will need changes of 5 or 10 degrees to
determine this and experiments made to demonstrate that the image stays
in focus as the temperature changes.

If changes of 0.1 deg in temperature are enough to put the image out of
focus then I doubt that any amount of software will help.  Was it Doug
who pointed out that a scope he did some tests on seemed actually to be
sensitive to the rate of change of temperature, not the actual value?
If that's the case then this will not help.

You have enough to be able to do these experiments and I think we need
to determine if this compensation method will help in practice.

Chris

Tom wrote:
> Here are some initial findings based on indoor testing of the temp.
compensated focuser shim 5.5.3 and FocusMax 3.5.24Beta...coupled to my
MoonLite/EasyFocus ASCOM focuser driver and MoonLite focuser.
>
> This 'shim' will adjust the focuser's physical position as temperature
changes...but is supposed to keep the focuser step value constant.  In other
words you'll see the focuser move in/out as temperature changes, but it sends a
temp. compensated focus position value to FocusMax.  If you don't move the
focuser for filter offsets, or any other reason...then the reported focus
position should remain constant.
>
> Here's output from the FocusMax temperature log:
>
> 12:04:53  Position = 1505  Temp = 25.5
> 12:05:11  Position = 1510  Temp = 25.0
> 12:05:30  Position = 1511  Temp = 25.0
> 12:05:47  Position = 1510  Temp = 25.5
> 12:06:09  Position = 1505  Temp = 25.5
> 12:06:29  Position = 1506  Temp = 25.0
> 12:06:48  Position = 1510  Temp = 25.0
> 12:07:12  Position = 1505  Temp = 25.5
> 12:07:38  Position = 1511  Temp = 25.5
> 12:07:55  Position = 1511  Temp = 25.5
> 12:08:15  Position = 1505  Temp = 25.5
> 12:08:34  Position = 1505  Temp = 25.5
> 12:08:59  Position = 1505  Temp = 25.0
> 12:09:18  Position = 1511  Temp = 25.0
> 12:09:43  Position = 1505  Temp = 25.0
> 12:10:08  Position = 1506  Temp = 25.5
> 12:10:32  Position = 1506  Temp = 25.5
> 12:11:17  Position = 1511  Temp = 25.5
> 12:11:54  Position = 1511  Temp = 25.5
> 12:12:33  Position = 1505  Temp = 25.5
> 12:13:06  Position = 1506  Temp = 25.5
> 12:13:36  Position = 1505  Temp = 25.5
> 12:18:41  Position = 1505  Temp = 25.5
>
> I had the temperature reading rate set fast...but note that there is still
some 'jitter' in reported focuser position...even when temperature remains
constant for some time interval.
>
> FocusMax 3.5.24Beta is awful sluggish when connected to this focuser shim, and
here is the probable reason:
>
> 12:11:19   Position: 1508
> 12:11:20   Temperature: 25.50
> 12:11:25   IsMoving: True
> 12:11:25   Position: 1505
> 12:11:26   Temperature: 25.50
> 12:11:51   IsMoving: True
> 12:11:52   Temperature: 25.50
> 12:11:54   Position: 1508
> 12:11:55   Temperature: 25.50
> 12:11:59   IsMoving: True
> 12:11:59   Position: 1506
> 12:12:01   Temperature: 25.50
> 12:12:07   IsMoving: True
> 12:12:07   Position: 1505
> 12:12:08   Temperature: 25.50
> 12:12:26   IsMoving: True
> 12:12:27   Temperature: 25.50
> 12:12:33   Position: 1508
> 12:12:34   Temperature: 25.50
> 12:12:59   IsMoving: True
> 12:13:00   Temperature: 25.50
> 12:13:06   Position: 1508
> 12:13:07   Temperature: 25.50
> 12:13:30   IsMoving: True
> 12:13:31   Temperature: 25.50
> 12:13:37   Position: 1508
> 12:13:38   Temperature: 25.50
> 12:18:34   IsMoving: True
> 12:18:35   Temperature: 25.50
> 12:18:41   Position: 1508
> 12:18:42   Temperature: 25.50
>
> The temp. compensated focuser shim is always reporting that it's moving...even
when it's not.  If I try and use the FocusMax jog feature...it takes a very long
time for the system to respond...or the software simply hangs.
>
> If I try and click on the Setup button in FocusMax (to adjust some ASCOM
driver parameters)...FocusMax 3.5.24beta either hangs, or reports an error that
the port is closed, crashes and disappears.
>
> All for now.
>
>
>
> ------------------------------------------------------------------------
>
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 9.0.851 / Virus Database: 271.1.1/3107 - Release Date: 09/01/10
19:34:00
>

#21733

From: "Franklin" <frank@...>
Date: Thu Sep 2, 2010 10:53 pm
Subject: [ASCOM] Re: Temperature Casting Workarounds???

f_holub

I'm disabling the temp reading in my little application when directly using the
EasyFocus driver - If I use POTH or Chris' Temperature Compensated Focuser shim
as a go between then my little app is happy...

Frank

--- In ASCOM-Talk@yahoogroups.com, "Tom" <tom_krajci@...> wrote:
>
>
>
> --- In ASCOM-Talk@yahoogroups.com, "Franklin" <frank@> wrote:
>
> >...I think I might just disable Temp when using EasyFocus until I
> > get good enough to figure this one out.
>
> Will you disable temp. comp. in the EasyFocus driver, or in the Temperature
Compensated Focuser shim that Chris is developing?
>
> --
> -------------------------------------------
> Tom Krajci
> Cloudcroft, New Mexico
> http://picasaweb.google.com/tom.krajci
>
> Center for Backyard Astrophysics (CBA)
> http://cbastro.org/ CBA New Mexico
>
> American Association of Variable Star
> Observers (AAVSO): KTC http://www.aavso.org/
> -------------------------------------------
>

#21734

From: "Tom" <tom_krajci@...>
Date: Fri Sep 3, 2010 12:03 am
Subject: Re: Temperature compensated focuser 'shim' 5.5.3 - initial test findings

tom_krajci

--- In ASCOM-Talk@yahoogroups.com, Chris Rowland <chris_group_mail@...> wrote:
>
> What values did you set for temperature coefficient and Offset?

Coeff = 100 per degree...which was arbitrary

Offset was 2250.

> Can you note what the display on the moonlite focuser box says?

Since I use the MoonLite mini-controller...no built-in display.  Only displays
of focuser position are the various windows in FocusMax...Jog window, main
window, temperature log, main log, and ASCOM traffic log.

> Did you have temperature compensation turned on or off?

The MoonLite/EasyFocus ASCOM driver's temp. compensation was off.

FocusMax 3.5.24beta was automatically turning on temp. compensation in its main
window (I would try and uncheck the checkbox in FocusMax...one second later it
would be checked again.)

> It may be worth setting the min move parameter to avoid continual small
> moves.

I intentionally kept it at one (min value) this time to see what sort of jitter
or other weird move patterns I would see.

I have not yet tested this with FocusMax backlash compensation turned on.  That
might prove interesting....

> What I found using my test focuser driver was that the reported focus
> position would jitter by a small amount - 5 steps with a coefficient of
> 100 steps per degree - but would not drift. The position reported on the
> box did change as you would expect. That was with a 10 second moving
> average.

I was using a 5 second moving average, but in real operation I'd probably use a
much longer interval...5 - 20 minutes perhaps?

> The focuser would report moving when the focuser was doing a
> compensation move but not when it wasn't. Your focusmax log shows it
> moving all the time so it might be correctly reporting moving because it is.

I don't know if that's because my moving average was so short, or other causes. 
I'll keep experimenting with different settings and reporting it here.

> The focuser shim isn't expecting that the setup dialog will be called
> when it's connected. It could easily not be trapping errors, this was
> developed quickly in order to determine if the principle of this style
> of temperature compensation works rather than make it bullet proof.

Understood, thanks.

I find that if I exit FocusMax, remove power from the focuser, restart
FocusMax...then I can invoke the setup dialog without a crash.

> What seems to happen with the EasyFocus driver is that it reports the
> temperature to the nearest 0.1 deg and the value read is jittering by
> 0.1 or 0.2 deg.  If you want to stop jitter then the number of samples
> must be enough that a 0.2 deg change divided by the number of samples
> and multiplied by the temperature coefficient must give less than one step.

Hmmm, FocusMax only displays to the nearest 1/2 deg C.  I hate when temperature
measurements are 'dumbed down' for the display, but internally they are at
higher precision.

> The various errors in temperature measurement and position will tend to
> mean that values will not be exact to the step. There may be rounding
> errors getting in the way. I would not expect drift though.

Rounding errors of a step or two is fine by me.  But yes, drift is unacceptable.

> What's important is that once a temperature coefficient for the scope
> and focuser has been determined the scope stays in focus as the
> temperature changes. It will need changes of 5 or 10 degrees to
> determine this and experiments made to demonstrate that the image stays
> in focus as the temperature changes.

I intend to do an entire night of occasional focus runs so that I can analyze
the logs for temperature and focus position...and get a pretty confident measure
of temperature coefficient.

> If changes of 0.1 deg in temperature are enough to put the image out of
> focus then I doubt that any amount of software will help.  Was it Doug
> who pointed out that a scope he did some tests on seemed actually to be
> sensitive to the rate of change of temperature, not the actual value?
> If that's the case then this will not help.

That's why I cut holes in rear castings of all SCT's up here, add fans, and cut
more vent holes up near the corrector plate (with filter material)...and run the
fans all night.  That cuts back on tube currents, and the OTA tracks ambient air
temperature better.

Also, most SCT's use high-expansion aluminum tubes.  I've replaced that with
either steel or carbon fiber...much less focus shift as temperature changes.

> You have enough to be able to do these experiments and I think we need
> to determine if this compensation method will help in practice.

Still monsoon here...limited to indoor testing only for the next couple
weeks...then the big migration as I set up six or seven scopes in their
shelters.

Thanks!

--
-------------------------------------------
Tom Krajci
Cloudcroft, New Mexico
http://picasaweb.google.com/tom.krajci

Center for Backyard Astrophysics (CBA)
http://cbastro.org/ CBA New Mexico

American Association of Variable Star
Observers (AAVSO): KTC http://www.aavso.org/
-------------------------------------------

#21735

From: "Tom" <tom_krajci@...>
Date: Fri Sep 3, 2010 2:28 am
Subject: Re: [ASCOM] Temperature compensated focuser 'shim' 5.5.3 - initial test findings

tom_krajci

--- In ASCOM-Talk@yahoogroups.com, Chris Rowland <chris_group_mail@...> wrote:
>
>
> What I found using my test focuser driver was that the reported focus
> position would jitter by a small amount - 5 steps with a coefficient of
> 100 steps per degree - but would not drift. The position reported on the
> box did change as you would expect. That was with a 10 second moving
> average.

I tried a moving average of 120 seconds.  Reported focuser position no longer
shows jitter.

Hmmmm, moving average for calculating temperature to apply for temperature
compensation.

Part of the temperature measure/math may need to take into account the
resolution/fineness of the raw temperature output from the focuser/controller. 
FocusMax displays the temperature from my MoonLite/EasyFocus driver/MoonLite
stepper controller....to the nearest 1/2 deg C.  It's 22.0    22.5    23.0   
23.5    etc....but never    22.1   22.2

But I'm just an un-empowered, dumb user.  I don't know what the raw values are
coming from the temp sensor/focuser controller.  It's a digital output...but
does each digit correspond to 1/2 C, or 1/10thC, or 1/7th C?  I don't know.  But
knowing, and properly using that temperature resolution is probably important.

Moving average - that allows you to have calculated temp's such as 22.05C.  Is
that necessary?  Is that false precision?  Perhaps a median function, or some
other algorithm that produces an output that is similar to the temperature
resolution/fineness of the raw temperature output?  If that raw value is
quantized by every 1/2C...then perhaps the output of the algorithm needs to be
quantized in  the same 1/2C steps.

Maybe keep track of the last 21 measures.  Take the median of them as the
output?  Or bin them according to raw temperature resolution...and select the
bin with the most instances?

Am I on the right track?

> The focuser would report moving when the focuser was doing a
> compensation move but not when it wasn't. Your focusmax log shows it
> moving all the time so it might be correctly reporting moving because it is.

When my moving average was 5 seconds...the focuser would report it was moving
about every 2 - 3 seconds.  I touched the motor with my hands...yes...the
stepper motor was moving every 2 - 3 seconds.

When my moving average was 120 seconds...the focuser would report it was moving
about every 15 - 30 seconds.  I touched the motor with my hands...yes...the
stepper motor was moving every 15 - 30 seconds.

> What seems to happen with the EasyFocus driver is that it reports the
> temperature to the nearest 0.1 deg and the value read is jittering by
> 0.1 or 0.2 deg.

Or perhaps the moving average is taking the average of:  20 20 20 20 20 20 20 20
20 20.5    and calculating a moving average temperature of 20.05?  Maybe it
should take the median and say that the temperature is 20?

> If a min step is set then the reported position will change until the
> min step is reached, then there will be a single larger movement and the
> value will return to close to the target position.

I'll test that tomorrow with different min step values....

--
-------------------------------------------
Tom Krajci
Cloudcroft, New Mexico
http://picasaweb.google.com/tom.krajci

Center for Backyard Astrophysics (CBA)
http://cbastro.org/ CBA New Mexico

American Association of Variable Star
Observers (AAVSO): KTC http://www.aavso.org/
-------------------------------------------

#21736

From: "Tom" <tom_krajci@...>
Date: Fri Sep 3, 2010 3:45 am
Subject: Re: [ASCOM] Temperature compensated focuser 'shim' 5.5.3 - initial test findings

tom_krajci

--- In ASCOM-Talk@yahoogroups.com, Chris Rowland <chris_group_mail@...> wrote:
>
> The various errors in temperature measurement and position will tend to
> mean that values will not be exact to the step. There may be rounding
> errors getting in the way. I would not expect drift though.

Here's something interesting I noticed when I jogged the focuser out by 100
steps...did it more than once.

19:32:17   TempCompAvailable: True
19:33:41   IsMoving: False
19:33:42   Temperature: 25.50
19:33:52   Position: 2273
19:33:53   Temperature: 25.50
19:34:06   IsMoving: True
19:34:06   Position: 2273
19:34:07   Temperature: 25.50
19:34:23   IsMoving: True
19:34:24   Temperature: 25.50
19:34:43   Position: 2273
19:34:44   Temperature: 25.50
19:34:54   IsMoving: True
19:34:54   Position: 2273
19:34:55   Temperature: 26.00
19:35:03   MaxStep: 9400
19:35:08   IsMoving: True
19:35:08   IsMoving: False
19:35:09   IsMoving: False
19:35:10   Temperature: 26.00
19:35:16   Position: 2308
19:35:18   Temperature: 26.00
19:35:24   IsMoving: True
19:35:24   Position: 2308
19:35:25   Temperature: 26.00
19:35:32   IsMoving: True
19:35:33   Temperature: 26.00
19:35:40   MaxStep: 9400
19:35:45   IsMoving: True
19:35:45   IsMoving: False
19:35:46   Position: 2364
19:35:47   Temperature: 26.00
19:35:53   IsMoving: True
19:35:54   Position: 2364
19:35:55   Temperature: 26.00
19:36:01   IsMoving: True
19:36:02   Temperature: 26.00
19:36:10   Position: 2364
19:36:11   Temperature: 26.00
19:36:22   IsMoving: True
19:36:22   Position: 2364
19:36:24   Temperature: 26.00
19:36:37   IsMoving: True
19:36:38   Temperature: 26.00
19:36:51   Position: 2364
19:36:52   Temperature: 26.00
19:37:05   IsMoving: True
19:37:06   Position: 2364
19:37:07   Temperature: 26.00
19:37:20   IsMoving: True
19:37:21   Temperature: 26.00
19:42:51   Position: 2364
19:42:52   Temperature: 26.00
19:44:04   IsMoving: True
19:44:05   Temperature: 26.50
19:44:26   MaxStep: 9400
19:44:30   IsMoving: True
19:44:48   IsMoving: False
19:45:04   Position: 2426
19:45:05   Temperature: 26.50
19:45:24   IsMoving: True
19:45:25   Temperature: 26.50
19:45:42   Position: 2426
19:45:43   Temperature: 26.50
19:45:44   Temperature: 26.50
19:46:02   TempComp: True
19:46:21   IsMoving: True
19:46:22   Temperature: 26.50
19:46:50   Position: 2426
19:46:51   Temperature: 26.50

Note that reported focuser position moved out from 2273 to 2308, to 2364, and
then out to 2426.  (Each move was the result of a jog of 100 steps.)  (Temp.
coeff. was 100 steps/degC)

I also noticed that when I jogged out 100 steps, the focuser appeared to move
out 100 steps, but then immediately reversed direction and moved back somewhat. 
(Backlash compensation is not enabled in FocusMax, or in the focuser driver.)

--
-------------------------------------------
Tom Krajci
Cloudcroft, New Mexico
http://picasaweb.google.com/tom.krajci

Center for Backyard Astrophysics (CBA)
http://cbastro.org/ CBA New Mexico

American Association of Variable Star
Observers (AAVSO): KTC http://www.aavso.org/
-------------------------------------------

#21737

From: "brokengeiger" <anatase@...>
Date: Fri Sep 3, 2010 5:43 am
Subject: CG5 GT

brokengeiger

setting up the ascom generic celestron drivers to work within WWT (world wide
telescope).

My telescope setup isn't on the list. I put a newt orion 6" on my CG5 GT.

1. press choose in WWT (which launches "celestron driver.exe")
2. ascom telescope chooser
     a. drop down to Celestron scope driver
     b. click properties
     c. celestron driver setup
         i. drop down scope type

Only one I see that would match is the Advanced C5-SGT?

Reply | Messages in this Topic (2)

#21738

From: "brokengeiger" <anatase@...>
Date: Fri Sep 3, 2010 5:51 am
Subject: Re: ASCOM 5.5 install and RegSvr32 error

brokengeiger

For kicks you can regsvr32 the C:\Program Files\Common Files\ASCOM\Helper.dll
yourself in an command prompt and see if that's the only one failing. Then if it
fails try again in an elevated command prompt. This could mean you don't have
UAC truely off - just muffled the allows.

Otherwise for the setup:
Right click the setup process
choose properties
click the compatibility tab
select "run this program as an admin" in priv level (even though you have UAC
off)

if that fails go back to that dialogue
select "run this program in compat mod for:"
select windows XP sp3

I doubt ascom did any version checks at this level but doesn't hurt to try and
report back.




--- In ASCOM-Talk@yahoogroups.com, "mikael_johannesen" <dsl29721@...> wrote:
>
> Vista Home Premium 32 bit.
>
> --- In ASCOM-Talk@yahoogroups.com, "dc3dreamer" <rdenny@> wrote:
> >
> > 0x5 is also "access denied" in Microsoft gobbledegook speak. What OS are you
running (Vista or 7)? Is there anything "special" about it? You've already done
the right things.
> >
> >   --- Bob
> >
> > --- In ASCOM-Talk@yahoogroups.com, "mikael_johannesen" <dsl29721@> wrote:
> > >
> > > Hi
> > >
> > > I too have gotten the dreaded error
> > >
> > > C:\Program Files\Common Files\ASCOM\Helper.dll
> > > Unable to register DLL/OCX: RegSvr32 failed with exit code 0x5
> > >
> > > I have UAC turned off and running installation as admin doesn't help
either. I can't register the dll manually either it comes back with another
error code - access denied.
> > >
> > > Has this issue been resolved or does anyone have a clue how to fix it?
> > >
> >
>

#21739

From: Chris Rowland <chris_group_mail@...>
Date: Fri Sep 3, 2010 6:43 am
Subject: Re: [ASCOM] CG5 GT

scope_sapiens

Yes, choose any of the AS-GT choices - that's the mount you have.  You
can set the telescope parameters (aperture, focal length and
obstruction) if you like but very few programs use this so it won't
matter if you don't.

Chris

brokengeiger wrote:
> setting up the ascom generic celestron drivers to work within WWT (world wide
telescope).
>
> My telescope setup isn't on the list. I put a newt orion 6" on my CG5 GT.
>
> 1. press choose in WWT (which launches "celestron driver.exe")
> 2. ascom telescope chooser
>     a. drop down to Celestron scope driver
>     b. click properties
>     c. celestron driver setup
>         i. drop down scope type
>
> Only one I see that would match is the Advanced C5-SGT?
>
>
>
>
> ------------------------------------
>
> For more information see http://ASCOM-Standards.org/.
>
> To unsubscribe from this group, send an email FROM THE ACCOUNT YOU USED TO
SUBSCRIBE(!) to:
> ASCOM-Talk-unsubscribe@yahoogroups.com
>
> Yahoo! Groups Links
>
>
>
>
> ------------------------------------------------------------------------
>
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 9.0.851 / Virus Database: 271.1.1/3107 - Release Date: 09/01/10
19:34:00
>

Reply | Messages in this Topic (2)

#21740

From: Chris Rowland <chris_group_mail@...>
Date: Fri Sep 3, 2010 7:07 am
Subject: Re: [ASCOM] Temperature compensated focuser 'shim' 5.5.3 - initial test findings

scope_sapiens

sigh - it looks as if I'm going to have to add some logging to the shim.

We need to know what's really happening; what values it's reading, what
messages it's sending to the real focuser, what commands it's getting
and values returned to the controlling application.

I'm not going to modify the shim to account for the idiosyncrasies of
one driver, nor am I going to implement a median filter. We don't need
sophisticated data processing for this and a moving average will be less
vulnerable to pathological data examples.

I think you are right Tom, the moonlite focuser reports the temperature
with a precision of 0.1 degree but to the nearest 0.5 degree, so 22.0,
22.5, 23.0, 23.5. That's a feature of the implementation but internally
the temperature is a double so has about a dozen significant figures.

With a coefficient of 100 a change of 0.01 degree will cause a change of
1 step so to prevent a single value with a difference of 0.5 deg from
affecting things at least 50 samples need to be averaged.

Backlash is not implemented in any of this, nor in the ASCOM protocol.
I'm going to stay out of that can of worms.

Chris

Tom wrote:
>
> --- In ASCOM-Talk@yahoogroups.com, Chris Rowland <chris_group_mail@...> wrote:
>> The various errors in temperature measurement and position will tend to
>> mean that values will not be exact to the step. There may be rounding
>> errors getting in the way. I would not expect drift though.
>
> Here's something interesting I noticed when I jogged the focuser out by 100
steps...did it more than once.
>
> 19:32:17   TempCompAvailable: True
> 19:33:41   IsMoving: False
> 19:33:42   Temperature: 25.50
> 19:33:52   Position: 2273
> 19:33:53   Temperature: 25.50
> 19:34:06   IsMoving: True
> 19:34:06   Position: 2273
> 19:34:07   Temperature: 25.50
> 19:34:23   IsMoving: True
> 19:34:24   Temperature: 25.50
> 19:34:43   Position: 2273
> 19:34:44   Temperature: 25.50
> 19:34:54   IsMoving: True
> 19:34:54   Position: 2273
> 19:34:55   Temperature: 26.00
> 19:35:03   MaxStep: 9400
> 19:35:08   IsMoving: True
> 19:35:08   IsMoving: False
> 19:35:09   IsMoving: False
> 19:35:10   Temperature: 26.00
> 19:35:16   Position: 2308
> 19:35:18   Temperature: 26.00
> 19:35:24   IsMoving: True
> 19:35:24   Position: 2308
> 19:35:25   Temperature: 26.00
> 19:35:32   IsMoving: True
> 19:35:33   Temperature: 26.00
> 19:35:40   MaxStep: 9400
> 19:35:45   IsMoving: True
> 19:35:45   IsMoving: False
> 19:35:46   Position: 2364
> 19:35:47   Temperature: 26.00
> 19:35:53   IsMoving: True
> 19:35:54   Position: 2364
> 19:35:55   Temperature: 26.00
> 19:36:01   IsMoving: True
> 19:36:02   Temperature: 26.00
> 19:36:10   Position: 2364
> 19:36:11   Temperature: 26.00
> 19:36:22   IsMoving: True
> 19:36:22   Position: 2364
> 19:36:24   Temperature: 26.00
> 19:36:37   IsMoving: True
> 19:36:38   Temperature: 26.00
> 19:36:51   Position: 2364
> 19:36:52   Temperature: 26.00
> 19:37:05   IsMoving: True
> 19:37:06   Position: 2364
> 19:37:07   Temperature: 26.00
> 19:37:20   IsMoving: True
> 19:37:21   Temperature: 26.00
> 19:42:51   Position: 2364
> 19:42:52   Temperature: 26.00
> 19:44:04   IsMoving: True
> 19:44:05   Temperature: 26.50
> 19:44:26   MaxStep: 9400
> 19:44:30   IsMoving: True
> 19:44:48   IsMoving: False
> 19:45:04   Position: 2426
> 19:45:05   Temperature: 26.50
> 19:45:24   IsMoving: True
> 19:45:25   Temperature: 26.50
> 19:45:42   Position: 2426
> 19:45:43   Temperature: 26.50
> 19:45:44   Temperature: 26.50
> 19:46:02   TempComp: True
> 19:46:21   IsMoving: True
> 19:46:22   Temperature: 26.50
> 19:46:50   Position: 2426
> 19:46:51   Temperature: 26.50
>
> Note that reported focuser position moved out from 2273 to 2308, to 2364, and
then out to 2426.  (Each move was the result of a jog of 100 steps.)  (Temp.
coeff. was 100 steps/degC)
>
> I also noticed that when I jogged out 100 steps, the focuser appeared to move
out 100 steps, but then immediately reversed direction and moved back somewhat. 
(Backlash compensation is not enabled in FocusMax, or in the focuser driver.)
>
>
>
> ------------------------------------------------------------------------
>
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 9.0.851 / Virus Database: 271.1.1/3107 - Release Date: 09/01/10
19:34:00
>

#21741

From: Chris Rowland <chris_group_mail@...>
Date: Fri Sep 3, 2010 8:14 am
Subject: Re: [ASCOM] Temperature compensated focuser 'shim' 5.5.3 - initial test findings

scope_sapiens

Two other things:

The temperature reported to the application is read directly from the
real focuser, it's not the averaged value.

There is no jog command for an absolute focuser, just a move to a
position. Jog will be implemented in the application by determining an
offset from a previous position. Better to try a move to a defined
position. When I do this the compensated focuser moves to the exact
position.

Chris

#21742

From: "Tom" <tom_krajci@...>
Date: Fri Sep 3, 2010 3:01 pm
Subject: Re: [ASCOM] Temperature compensated focuser 'shim' 5.5.3 - initial test findings

tom_krajci

--- In ASCOM-Talk@yahoogroups.com, Chris Rowland <chris_group_mail@...> wrote:
>
> ...it looks as if I'm going to have to add some logging to the shim.
>
> We need to know what's really happening; what values it's reading, what
> messages it's sending to the real focuser, what commands it's getting
> and values returned to the controlling application.

Roger that.  Here's an example of why more logging is good.  This is from
FocusMax (traffic log):

08:26:28   TempCompAvailable: True
08:26:40   IsMoving: True
08:26:41   Temperature: 21.00
08:26:45   Position: 2487
08:26:46   Temperature: 21.50
08:26:49   IsMoving: True
08:26:49   Position: 2487
08:26:50   Temperature: 21.50
08:26:53   IsMoving: True
08:26:53   Position: 2487
08:26:54   Temperature: 21.50
08:26:59   IsMoving: True
08:26:59   Position: 2487
08:27:00   Temperature: 21.50
08:27:06   IsMoving: True
08:27:07   Temperature: 22.00
08:27:10   Position: 2487
08:27:11   Temperature: 22.00
08:27:15   IsMoving: True
08:27:15   Position: 2487
08:27:16   Temperature: 22.00
08:27:20   IsMoving: True
08:27:20   Position: 2487
08:27:21   Temperature: 22.00
08:27:25   IsMoving: True
08:27:26   Temperature: 22.00
08:27:30   Position: 2488
08:27:31   Temperature: 22.50
08:27:35   IsMoving: True
08:27:35   Position: 2487
08:27:36   Temperature: 22.50
08:27:39   IsMoving: True
08:27:39   Position: 2487
08:27:40   Temperature: 22.50
08:27:44   IsMoving: True
08:27:44   Position: 2487
08:27:45   Temperature: 22.50
08:27:50   IsMoving: True
08:27:51   Temperature: 22.50
08:27:55   Position: 2487
08:27:56   Temperature: 22.50
08:28:02   IsMoving: True
08:28:02   Position: 2487
08:28:03   Temperature: 22.50
08:28:08   IsMoving: True
08:28:08   Position: 2487
08:28:09   Temperature: 23.00
08:28:14   IsMoving: True
08:28:15   Temperature: 23.00
08:28:19   Position: 2487
08:28:20   Temperature: 23.00
08:28:21   Temperature: 23.00
08:28:27   TempComp: True
08:28:33   IsMoving: True
08:28:33   Position: 2487
08:28:34   Temperature: 23.00
08:28:40   IsMoving: True
08:28:41   Temperature: 23.00
08:28:46   Position: 2487
08:28:47   Temperature: 23.50
08:28:51   IsMoving: True
08:28:51   Position: 2487
08:28:53   Temperature: 23.50
08:28:58   IsMoving: True
08:28:58   Position: 2487
08:28:59   Temperature: 23.50
08:29:05   IsMoving: True
08:29:06   Temperature: 23.50
08:29:12   Position: 2487
08:29:13   Temperature: 23.50
08:29:20   IsMoving: True
08:29:20   Position: 2487
08:29:21   Temperature: 23.50
08:29:29   IsMoving: True
08:29:30   Temperature: 23.50
08:29:38   Position: 2487
08:29:39   Temperature: 23.50
08:29:48   IsMoving: True
08:29:48   Position: 2487
08:29:49   Temperature: 24.00
08:29:57   IsMoving: True
08:29:58   Temperature: 24.00
08:30:04   Position: 2487
08:30:05   Temperature: 24.00
08:30:13   IsMoving: True
08:30:13   Position: 2487
08:30:14   Temperature: 24.00
08:30:22   IsMoving: True
08:30:23   Temperature: 24.00
08:30:32   Position: 2487
08:30:33   Temperature: 24.00
08:30:41   IsMoving: True
08:30:41   Position: 2487
08:30:42   Temperature: 24.00
08:30:46   IsMoving: True
08:30:46   Position: 2487
08:30:47   Temperature: 24.00
08:30:51   IsMoving: True
08:30:52   Temperature: 24.00
08:30:56   Position: 2487
08:30:57   Temperature: 24.00
08:31:02   IsMoving: True
08:31:02   Position: 2487
08:31:03   Temperature: 24.00
08:31:04   Temperature: 24.00
08:31:09   TempComp: True
08:31:14   IsMoving: True
08:31:15   Temperature: 24.00
08:31:21   Position: 2487
08:31:22   Temperature: 24.00
08:31:27   IsMoving: True
08:31:27   Position: 2487
08:31:28   Temperature: 24.00
08:31:33   IsMoving: True
08:31:33   Position: 2487
08:31:34   Temperature: 24.00
08:31:40   IsMoving: True
08:31:41   Temperature: 24.00
08:31:48   Position: 2487
08:31:49   Temperature: 24.00
08:31:56   IsMoving: True
08:31:56   Position: 2487
08:31:57   Temperature: 24.00
08:32:04   IsMoving: True
08:32:05   Temperature: 24.00
08:32:14   Position: 2487
08:32:15   Temperature: 24.00
08:32:25   IsMoving: True
08:32:25   Position: 2487
08:32:26   Temperature: 24.00
08:32:36   IsMoving: True
08:32:37   Temperature: 24.00
08:32:52   Position: 2487
08:32:54   Temperature: 24.00
08:33:10   IsMoving: True
08:33:11   Temperature: 24.50
08:33:24   Position: 2487
08:33:25   Temperature: 24.00
08:33:38   IsMoving: True
08:33:38   Position: 2487
08:33:39   Temperature: 24.50
08:33:53   IsMoving: True
08:33:54   Temperature: 24.50
08:34:15   Position: 2487
08:34:16   Temperature: 24.50
08:34:36   IsMoving: True
08:34:37   Temperature: 24.50
08:34:56   Position: 2487
08:34:58   Temperature: 24.50
08:35:17   IsMoving: True
08:35:18   Temperature: 24.50
08:35:38   Position: 2487
08:35:39   Temperature: 24.50
08:35:59   IsMoving: True
08:36:00   Temperature: 24.50
08:36:20   Position: 2487
08:36:21   Temperature: 24.50
08:36:50   IsMoving: True
08:36:51   Temperature: 24.50
08:45:00   Position: 2487
08:45:01   Temperature: 24.50
08:45:02   Temperature: 24.50
08:46:02   TempComp: True
08:46:07   TempCompAvailable: True

Note the irregular time interval of updates/info written to the log...especially
the 8-minute gap near the very end.

It's tough to troubleshoot and analyze without good log info.

> Backlash is not implemented in any of this, nor in the ASCOM protocol.
> I'm going to stay out of that can of worms.

I've got my fingers crossed that FocusMax backlash compensation can help here.

After all, it's a dirty, nasty astro-world out there.  Just about every focuser
(and mount drive, and SCT main mirror focusing scheme, etc....) has some
combination of backlash, slippage, flexure, and lord knows what else.  And for
better or worse, I gotta get my hands dirty dealing with stuff like backlash so
that I can keep on taking more and better science data.

--
-------------------------------------------
Tom Krajci
Cloudcroft, New Mexico
http://picasaweb.google.com/tom.krajci

Center for Backyard Astrophysics (CBA)
http://cbastro.org/ CBA New Mexico

American Association of Variable Star
Observers (AAVSO): KTC http://www.aavso.org/
-------------------------------------------

#21743

From: "Tom" <tom_krajci@...>
Date: Fri Sep 3, 2010 3:21 pm
Subject: Re: [ASCOM] Temperature compensated focuser 'shim' 5.5.3 - initial test findings

tom_krajci

--- In ASCOM-Talk@yahoogroups.com, Chris Rowland <chris_group_mail@...> wrote:
>
>
> We need to know what's really happening; what values it's reading, what
> messages it's sending to the real focuser, what commands it's getting
> and values returned to the controlling application.

When I call up Windows Task Manager, I find that FocusMax.exe is using all
available CPU resources when it's connected to the temperature compensated shim.

--
-------------------------------------------
Tom Krajci
Cloudcroft, New Mexico
http://picasaweb.google.com/tom.krajci

Center for Backyard Astrophysics (CBA)
http://cbastro.org/ CBA New Mexico

American Association of Variable Star
Observers (AAVSO): KTC http://www.aavso.org/
-------------------------------------------