On 06/20/12 7:48 AM, Felix Handte wrote:
>
> Ideally, I'd like to write a driver in TCL (using tcom) that presents
> the TCS as an ASCOM telescope to Maxim DL. How would I go about doing
> that? Have people written ASCOM-compatible drivers in TCL before? Can
> they send me their source code?

ASCOM drivers are Windows "COM" objects, written in VBasic or C#.   I
don't believe there's any way to connect TCL to the .NET world of COM
objects.   you might be able to write a shim in TCL that has a RPC
interface to your TCS stuff, and a C# ASCOM object that talks to that RPC.



--
john r pierce                            N 37, W 122
santa cruz ca                         mid-left coast

Bob,

Whilst we have your ear there is another potential issue.

When using an ASCOM implemented control program (CCDAutopilot, CCDCommander etc)
AND MAxim AND TheSkyX AND a Paramount AND the "no cable" (ie "telescope") method
of autoguiding there is a problem with guiding parameters after a flip.

It is possible to get Maxim to guide correctly after a flip (by altering the
advanced controls/auto pier flip etc) but this does not happen when Maxim is
externally controlled.

I have posted this (http://www.bisque.com/sc/forums/t/15513.aspx?PageIndex=2) on
the Bisque forum and the response leads me to believe I am not alone. Indeed
Matt Thomas of CCDCommander has acknowledged there is an issue.

Please note that this does not happen with a cable to the autoguider port (see
the Bisque post).

I have not had chance to test this aspect with the new driver but thought it
worthwhile to flag up whilst we are discussing the updated driver.

Paul
--- In ASCOM-Talk@yahoogroups.com, "dc3dreamer" <rdenny@...> wrote:
>
> Thanks to Chris for the fast reaponse and fixing this. Especially considering
that he does not have a Paramount!!!
>
> If this is OK, I'll update the ASCOM Download area with 5.1.10. Chris, let me
know when you consider it OK.
>
>   -- Bob
>
> --- In ASCOM-Talk@yahoogroups.com, "John" <stnoble@> wrote:
> >
> >
> > Chris
> > Many thanks for posting the file. I was also able to test it tonight here in
the UK with success. Installed without difficulty and using TheSkyX Pro,
Paramount ME, Maxim DL5.18 calibrated at once and very satisfactory tracking.
> > Is it correct that 'Enable Simultaneous RA and DEC corrections' should be
OFF. I tested it with this off.
> > John
> >
>

Was able to confirm last evening that the TheSky Controlled ASCOM driver ver
5.2.10 does resolve the pulse guide issue.  Actually duplicated the issue using
ver 5.2.7, installed 5.2.10, and issue resolved.  Setup, TheSkyX Pro ver 10.1.11
build 5745, MaxIm DL Ver 5.18, Paramount MX mount.

Rod Cook

--- In ASCOM-Talk@yahoogroups.com, "dc3dreamer" <rdenny@...> wrote:
>
> Thanks to Chris for the fast reaponse and fixing this. Especially considering
that he does not have a Paramount!!!
>
> If this is OK, I'll update the ASCOM Download area with 5.1.10. Chris, let me
know when you consider it OK.
>
>   -- Bob
>
> --- In ASCOM-Talk@yahoogroups.com, "John" <stnoble@> wrote:
> >
> >
> > Chris
> > Many thanks for posting the file. I was also able to test it tonight here in
the UK with success. Installed without difficulty and using TheSkyX Pro,
Paramount ME, Maxim DL5.18 calibrated at once and very satisfactory tracking.
> > Is it correct that 'Enable Simultaneous RA and DEC corrections' should be
OFF. I tested it with this off.
> > John
> >
>

On 06/19/12 3:40 PM, Tim Long wrote:
> I don't think we can give you guidance on this sort of decision - it
> depends on the characteristics of your drive system and how it is
> intended to be used. These are decisions for you, the designer, to make.

well, I have no idea what PhD Guiding or another autoguider package
actually uses out of the vast number of ASCOM APIs and methods, so I
guess my question was relative to that.

the drive system in question is a Vixen SuperPolaris mount with 2 MT-1
motors, which are 48 step/turn, 120:1 gear reduction stepper motors,
being half stepped, driving a 10 minute/turn wormgear.   the default
sidereal tracking rate is approximately 19.6 halfsteps per second.


--
john r pierce                            N 37, W 122
santa cruz ca                         mid-left coast

Felix,

The ASCOM interface is late bound, I think that means that it doesn't have a
MIDL file because it uses the IUnknown interface.

How this affects using tcom I don't know but from a very quick look it seems to
assume an early bound interface.

Is the control protocol the one specified by Tom Trebisky where the MMT is
controlled by ascii text strings sent over TCP/IP?

If so it shouldn't be too difficult to interface directly to this in an ASCOM
driver written in C# or VB.NET.  Or maybe to some other layer that takes text
strings - maybe TCL commands.

Chris

--- In ASCOM-Talk@yahoogroups.com, Felix Handte <fhandte@...> wrote:
>
> John,
>
> Thanks for your response.
>
> You can provide a COM interface to TCL code, actually, using the tcom
> library (documentation here <http://www.vex.net/~cthuang/tcom/> and
> here<http://www2.tcl.tk/1821>).
> Primarily, I think, I'm looking for an MIDL file to define the interface.
> Is that available?
>
> Thanks,
> Felix Handte
>
> On Thu, Jun 21, 2012 at 1:26 AM, John R Pierce <pierce@...> wrote:
>
> > **
> >
> >
> > On 06/20/12 7:48 AM, Felix Handte wrote:
> > >
> > > Ideally, I'd like to write a driver in TCL (using tcom) that presents
> > > the TCS as an ASCOM telescope to Maxim DL. How would I go about doing
> > > that? Have people written ASCOM-compatible drivers in TCL before? Can
> > > they send me their source code?
> >
> > ASCOM drivers are Windows "COM" objects, written in VBasic or C#. I
> > don't believe there's any way to connect TCL to the .NET world of COM
> > objects. you might be able to write a shim in TCL that has a RPC
> > interface to your TCS stuff, and a C# ASCOM object that talks to that RPC.
> >
> > --
> > john r pierce N 37, W 122
> > santa cruz ca mid-left coast
> >
> >
> >
>

Yes, please post the new version. We have enough evidence that it's OK.

Would you also be able to update the Celestron driver as well please. this is
now version 5.0.28 and is in the files area. There is a conform report as well.

Chris

--- In ASCOM-Talk@yahoogroups.com, "dc3dreamer" <rdenny@...> wrote:
>
> Thanks to Chris for the fast reaponse and fixing this. Especially considering
that he does not have a Paramount!!!
>
> If this is OK, I'll update the ASCOM Download area with 5.1.10. Chris, let me
know when you consider it OK.
>
>   -- Bob
>
> --- In ASCOM-Talk@yahoogroups.com, "John" <stnoble@> wrote:
> >
> >
> > Chris
> > Many thanks for posting the file. I was also able to test it tonight here in
the UK with success. Installed without difficulty and using TheSkyX Pro,
Paramount ME, Maxim DL5.18 calibrated at once and very satisfactory tracking.
> > Is it correct that 'Enable Simultaneous RA and DEC corrections' should be
OFF. I tested it with this off.
> > John
> >
>

I tested 5.2.10 last night with an MX and Maxim DL 5.18 using both the
Microguide and Telescope as the autoguider output selection and in both
instances the calibration was solid and the tracking was good. Previously under
5.2.07 when guiding was attempted The SkyX would turn off tracking. This
behavior was not seen. From my perspective it is good to go. Thanks

Jim
--- In ASCOM-Talk@yahoogroups.com, "dc3dreamer" <rdenny@...> wrote:
>
> Thanks to Chris for the fast reaponse and fixing this. Especially considering
that he does not have a Paramount!!!
>
> If this is OK, I'll update the ASCOM Download area with 5.1.10. Chris, let me
know when you consider it OK.
>
>   -- Bob
>
> --- In ASCOM-Talk@yahoogroups.com, "John" <stnoble@> wrote:
> >
> >
> > Chris
> > Many thanks for posting the file. I was also able to test it tonight here in
the UK with success. Installed without difficulty and using TheSkyX Pro,
Paramount ME, Maxim DL5.18 calibrated at once and very satisfactory tracking.
> > Is it correct that 'Enable Simultaneous RA and DEC corrections' should be
OFF. I tested it with this off.
> > John
> >
>

Maybe not so quick a question.

One application, Firestarter 2.1, can use ASCOM telescope chooser, select a
scope for pulse guide purposes and launch the driver for the selected scope.
Another application, PHD, kicks back an error "Failed to run Scope Chooser.
Something is wrong with ASCOM"

Any ideas what could let one program launch chooser and another not?
I have been told the user is always admin user.

Gene

Ok, the 5.1.10 update of the TheSky Controlled Telescope driver is online at the
ASCOM web site download center. Thanks again!!!!!

   -- Bob


On Jun 21, 2012, at 11:19, "Chris" <chris_group_mail@...> wrote:

> Yes, please post the new version. We have enough evidence that it's OK.
>
> Would you also be able to update the Celestron driver as well please. this is
now version 5.0.28 and is in the files area. There is a conform report as well.
>
> Chris
>
> --- In ASCOM-Talk@yahoogroups.com, "dc3dreamer" <rdenny@...> wrote:
>>
>> Thanks to Chris for the fast reaponse and fixing this. Especially considering
that he does not have a Paramount!!!
>>
>> If this is OK, I'll update the ASCOM Download area with 5.1.10. Chris, let me
know when you consider it OK.
>>
>>  -- Bob
>>
>> --- In ASCOM-Talk@yahoogroups.com, "John" <stnoble@> wrote:
>>>
>>>
>>> Chris
>>> Many thanks for posting the file. I was also able to test it tonight here in
the UK with success. Installed without difficulty and using TheSkyX Pro,
Paramount ME, Maxim DL5.18 calibrated at once and very satisfactory tracking.
>>> Is it correct that 'Enable Simultaneous RA and DEC corrections' should be
OFF. I tested it with this off.
>>> John
>>>
>>
>
>
>
>
> ------------------------------------
>
> 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
>
>
>
>

This can be tricky to diagnose. I cannot speak for CCDC or CCDAP, but at least
with my ACP automation engine, MaxIm must NOT be connected for any of its
telescope/observatory controls. Therefore the auto-pier-flip setting in MaxIm
will not affect things and cause confusion. ACP manages the guiding parameters
across flips once it has been calibrated looking east (mount on west side of
pier.

I would contact Matt or John for a procedure to run tests with their software to
isolate the guiding issue. I have one for ACP but it's probably not right for
those programs, and in any case they will have a way to work together to zero in
on the issue.

   -- Bob


On Jun 21, 2012, at 0:26, "Joe Bloggs" <yahoo@...> wrote:

> Bob,
>
> Whilst we have your ear there is another potential issue.
>
> When using an ASCOM implemented control program (CCDAutopilot, CCDCommander
etc) AND MAxim AND TheSkyX AND a Paramount AND the "no cable" (ie "telescope")
method of autoguiding there is a problem with guiding parameters after a flip.
>
> It is possible to get Maxim to guide correctly after a flip (by altering the
advanced controls/auto pier flip etc) but this does not happen when Maxim is
externally controlled.
>
> I have posted this (http://www.bisque.com/sc/forums/t/15513.aspx?PageIndex=2)
on the Bisque forum and the response leads me to believe I am not alone. Indeed
Matt Thomas of CCDCommander has acknowledged there is an issue.
>
> Please note that this does not happen with a cable to the autoguider port (see
the Bisque post).
>
> I have not had chance to test this aspect with the new driver but thought it
worthwhile to flag up whilst we are discussing the updated driver.
>
> Paul
> --- In ASCOM-Talk@yahoogroups.com, "dc3dreamer" <rdenny@...> wrote:
>>
>> Thanks to Chris for the fast reaponse and fixing this. Especially considering
that he does not have a Paramount!!!
>>
>> If this is OK, I'll update the ASCOM Download area with 5.1.10. Chris, let me
know when you consider it OK.
>>
>>  -- Bob
>>
>> --- In ASCOM-Talk@yahoogroups.com, "John" <stnoble@> wrote:
>>>
>>>
>>> Chris
>>> Many thanks for posting the file. I was also able to test it tonight here in
the UK with success. Installed without difficulty and using TheSkyX Pro,
Paramount ME, Maxim DL5.18 calibrated at once and very satisfactory tracking.
>>> Is it correct that 'Enable Simultaneous RA and DEC corrections' should be
OFF. I tested it with this off.
>>> John
>>>
>>
>
>
>
>
> ------------------------------------
>
> 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
>
>
>
>

It's hard to make any guesses with so little to go on. Does the chooser
'look right'? Can you compare it with a known-good ASCOM v6.0 chooser
and see if it looks the same? There have been cases of 'chooser hijack'
with certain software installing its own copy of some ASCOM components.
Depending on how the application accesses the chooser, this can lead to
different applications seeing different versions of the chooser or one
working and not the other. It's a long shot... but it's the best guess I
can make.

Have you run the ASCOM Diagnostics tool? Anything interesting in the
log?

Regards,
Tim Long


> -----Original Message-----
> From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-
> Talk@yahoogroups.com] On Behalf Of lynol1000
> Sent: 21 June 2012 23:24
> To: ASCOM-Talk@yahoogroups.com
> Subject: [ASCOM] Tale of two ASCOM's ?
>
> Maybe not so quick a question.
>
> One application, Firestarter 2.1, can use ASCOM telescope chooser,
select a
> scope for pulse guide purposes and launch the driver for the selected
scope.
> Another application, PHD, kicks back an error "Failed to run Scope
Chooser.
> Something is wrong with ASCOM"
>
> Any ideas what could let one program launch chooser and another not?
> I have been told the user is always admin user.
>
> Gene
>
>
>
>
>
> ------------------------------------
>
> 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=q5LN6VAG024954&from=tim@tigranetwo\
rks.co.uk
Complete email hygiene and business continuity solution available from
http://www.tigranetworks.co.uk

Hi Tim, The Chooser in Firestarter looks correct.

It is an ASCOM 5.5 install.

The diags show Windows (W7/64bit) registry entries for the scope driver the user
is trying to access yet the 5.5 profile.xml does not show entries for it.

The driver (mine) does nothing but ASCOM calls for initial registration and
entries, I have run it on everything from ASCOM 5.0 through the latest, Win XP
through W8 dev, all have worked on other systems.

Almost like some one or more components of ASCOM are not as expected.

The user reported initially when he installed Firestarter it reported ASCOM
5.0a, the profile diags show 5.5.

Running ASCOM Platform version kicks back an error
ShowplatformVersion.vbs cannot create object DriverHelper2.util

12:20:13.480 ScanRegistry              Start
12:20:13.480 Registry Profile          Profile Root
12:20:13.512 Registry Profile             PlatformVersion = 5

12:20:17.614 FileDetails               HELPER2.DLL C:\Program Files (x86)\Common
Files\ASCOM\HELPER2.DLL
12:20:17.630 FileDetails                  File Version:    5.1 0 0
12:20:17.630 FileDetails                  Product Version: 5.1 0 0

and
12:20:17.692 Helper2.DLL               C:\Program Files (x86)\Common
Files\ASCOM\Utilities\Helper2.dll
12:20:17.692 FileDetails               HELPER2.DLL C:\Program Files (x86)\Common
Files\ASCOM\Utilities\HELPER2.DLL
12:20:17.724 FileDetails                  File Version:    4.0 0 3

and
12:20:26.179 File                      C:\ProgramData\ASCOM\Profile\Profile.xml
12:20:26.179                             <?xml version="1.0" encoding="utf-8"?>
12:20:26.179                             <Profile>
12:20:26.179                               <DefaultElement Value="===== *****
UnsetValue ***** =====" />
12:20:26.179                               <Element Name="PlatformVersion"
Value="5.5" />

Gene

Gene

--- In ASCOM-Talk@yahoogroups.com, "Tim Long" <Tim@...> wrote:
>
> It's hard to make any guesses with so little to go on. Does the chooser
> 'look right'? Can you compare it with a known-good ASCOM v6.0 chooser
> and see if it looks the same? There have been cases of 'chooser hijack'
> with certain software installing its own copy of some ASCOM components.
> Depending on how the application accesses the chooser, this can lead to
> different applications seeing different versions of the chooser or one
> working and not the other. It's a long shot... but it's the best guess I
> can make.
>
> Have you run the ASCOM Diagnostics tool? Anything interesting in the
> log?
>
> Regards,
> Tim Long
>
>
> > -----Original Message-----
> > From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-
> > Talk@yahoogroups.com] On Behalf Of lynol1000
> > Sent: 21 June 2012 23:24
> > To: ASCOM-Talk@yahoogroups.com
> > Subject: [ASCOM] Tale of two ASCOM's ?
> >
> > Maybe not so quick a question.
> >
> > One application, Firestarter 2.1, can use ASCOM telescope chooser,
> select a
> > scope for pulse guide purposes and launch the driver for the selected
> scope.
> > Another application, PHD, kicks back an error "Failed to run Scope
> Chooser.
> > Something is wrong with ASCOM"
> >
> > Any ideas what could let one program launch chooser and another not?
> > I have been told the user is always admin user.
> >
> > Gene
> >
> >
> >
> >
> >
> > ------------------------------------
> >
> > 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=q5LN6VAG024954&from=tim@...
> Complete email hygiene and business continuity solution available from
http://www.tigranetworks.co.uk
>

The first thing to do is to remove ASCOM 5 and 5.5 and if needed (likely) run
the "cleanup" tool that really really removes them, than install the current
ASCOM Platform 6. I just looked for the cleanup tool in the group files area and
can't find it. I'm sorry. Maybe you won't need it. If you do, in other words if
there is a problem getting rid of the old Platform, ask here and someone will
point you to it.

   -- Bob


On Jun 21, 2012, at 16:46, "lynol1000" <lynol1000@...> wrote:

> Hi Tim, The Chooser in Firestarter looks correct.
>
> It is an ASCOM 5.5 install.
>
> The diags show Windows (W7/64bit) registry entries for the scope driver the
user is trying to access yet the 5.5 profile.xml does not show entries for it.
>
> The driver (mine) does nothing but ASCOM calls for initial registration and
entries, I have run it on everything from ASCOM 5.0 through the latest, Win XP
through W8 dev, all have worked on other systems.
>
> Almost like some one or more components of ASCOM are not as expected.
>
> The user reported initially when he installed Firestarter it reported ASCOM
5.0a, the profile diags show 5.5.
>
> Running ASCOM Platform version kicks back an error
> ShowplatformVersion.vbs cannot create object DriverHelper2.util
>
> 12:20:13.480 ScanRegistry              Start
> 12:20:13.480 Registry Profile          Profile Root
> 12:20:13.512 Registry Profile             PlatformVersion = 5
>
> 12:20:17.614 FileDetails               HELPER2.DLL C:\Program Files
(x86)\Common Files\ASCOM\HELPER2.DLL
> 12:20:17.630 FileDetails                  File Version:    5.1 0 0
> 12:20:17.630 FileDetails                  Product Version: 5.1 0 0
>
> and
> 12:20:17.692 Helper2.DLL               C:\Program Files (x86)\Common
Files\ASCOM\Utilities\Helper2.dll
> 12:20:17.692 FileDetails               HELPER2.DLL C:\Program Files
(x86)\Common Files\ASCOM\Utilities\HELPER2.DLL
> 12:20:17.724 FileDetails                  File Version:    4.0 0 3
>
> and
> 12:20:26.179 File                     
C:\ProgramData\ASCOM\Profile\Profile.xml
> 12:20:26.179                             <?xml version="1.0"
encoding="utf-8"?>
> 12:20:26.179                             <Profile>
> 12:20:26.179                               <DefaultElement Value="===== *****
UnsetValue ***** =====" />
> 12:20:26.179                               <Element Name="PlatformVersion"
Value="5.5" />
>
> Gene
>
> Gene
>
> --- In ASCOM-Talk@yahoogroups.com, "Tim Long" <Tim@...> wrote:
>>
>> It's hard to make any guesses with so little to go on. Does the chooser
>> 'look right'? Can you compare it with a known-good ASCOM v6.0 chooser
>> and see if it looks the same? There have been cases of 'chooser hijack'
>> with certain software installing its own copy of some ASCOM components.
>> Depending on how the application accesses the chooser, this can lead to
>> different applications seeing different versions of the chooser or one
>> working and not the other. It's a long shot... but it's the best guess I
>> can make.
>>
>> Have you run the ASCOM Diagnostics tool? Anything interesting in the
>> log?
>>
>> Regards,
>> Tim Long
>>
>>
>>> -----Original Message-----
>>> From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-
>>> Talk@yahoogroups.com] On Behalf Of lynol1000
>>> Sent: 21 June 2012 23:24
>>> To: ASCOM-Talk@yahoogroups.com
>>> Subject: [ASCOM] Tale of two ASCOM's ?
>>>
>>> Maybe not so quick a question.
>>>
>>> One application, Firestarter 2.1, can use ASCOM telescope chooser,
>> select a
>>> scope for pulse guide purposes and launch the driver for the selected
>> scope.
>>> Another application, PHD, kicks back an error "Failed to run Scope
>> Chooser.
>>> Something is wrong with ASCOM"
>>>
>>> Any ideas what could let one program launch chooser and another not?
>>> I have been told the user is always admin user.
>>>
>>> Gene
>>>
>>>
>>>
>>>
>>>
>>> ------------------------------------
>>>
>>> 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=q5LN6VAG024954&from=tim@...
>> Complete email hygiene 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
>
>
>
>

What's happened is that PHD has received some error which it interprets and
reports as an ASCOM problem.  It has not reported what the error was that it
got.

This hiding of the real error makes it very difficult to say what has happened.
If we had the real error we would be in a much better position to help.

Error reporting is an area where I believe that it is a mistake to modify the
information for the user.  Your audience in this case is the developer and they
need the detail of the error message in order to be able to help.

I suggest that you ask Craig for the details of exactly what error triggered
this message, including the full error message.

Chris

--- In ASCOM-Talk@yahoogroups.com, "Peter Simpson" <peter@...> wrote:
>
> Hi Gene,
> Its possible that the Chooser has been unintentionally hijacked by an
> application such as early versions of FocusMax (current versions don't
> do this). If this is the case then re-registering the helper DLLs may
> solve the issue:
>
>     1. Open an admin level command prompt
>     2. Change to directory  C:\Program Files\Common Files\ASCOM
>     3. Run the command: regsvr32 helper.dll
>     4. Then run the command: regsvr32 helper2.dll
>
> Regards, Peter
> --- In ASCOM-Talk@yahoogroups.com, "lynol1000" <lynol1000@> wrote:
> >
> > Maybe not so quick a question.
> >
> > One application, Firestarter 2.1, can use ASCOM telescope chooser,
> select a scope for pulse guide purposes and launch the driver for the
> selected scope.
> > Another application, PHD, kicks back an error "Failed to run Scope
> Chooser. Something is wrong with ASCOM"
> >
> > Any ideas what could let one program launch chooser and another not?
> > I have been told the user is always admin user.
> >
> > Gene
> >
>

The driver makes no allowances for the side of pier the scope is on, it issues
the same guide commands regardless.

Trying to modify this comes into the category of too difficult without hardware.

It's possible that MaxIm is compensating for the guide direction change, that
this is being done in theSky, or both, or neither.

I can't tackle this, sorry but life's too short.

Of course if someone were to give me a Paramount I might change my mind :-)

Chris

--- In ASCOM-Talk@yahoogroups.com, Bob Denny <rdenny@...> wrote:
>
> This can be tricky to diagnose. I cannot speak for CCDC or CCDAP, but at least
with my ACP automation engine, MaxIm must NOT be connected for any of its
telescope/observatory controls. Therefore the auto-pier-flip setting in MaxIm
will not affect things and cause confusion. ACP manages the guiding parameters
across flips once it has been calibrated looking east (mount on west side of
pier.
>
> I would contact Matt or John for a procedure to run tests with their software
to isolate the guiding issue. I have one for ACP but it's probably not right for
those programs, and in any case they will have a way to work together to zero in
on the issue.
>
>   -- Bob
>
>
> On Jun 21, 2012, at 0:26, "Joe Bloggs" <yahoo@...> wrote:
>
> > Bob,
> >
> > Whilst we have your ear there is another potential issue.
> >
> > When using an ASCOM implemented control program (CCDAutopilot, CCDCommander
etc) AND MAxim AND TheSkyX AND a Paramount AND the "no cable" (ie "telescope")
method of autoguiding there is a problem with guiding parameters after a flip.
> >
> > It is possible to get Maxim to guide correctly after a flip (by altering the
advanced controls/auto pier flip etc) but this does not happen when Maxim is
externally controlled.
> >
> > I have posted this
(http://www.bisque.com/sc/forums/t/15513.aspx?PageIndex=2) on the Bisque forum
and the response leads me to believe I am not alone. Indeed Matt Thomas of
CCDCommander has acknowledged there is an issue.
> >
> > Please note that this does not happen with a cable to the autoguider port
(see the Bisque post).
> >
> > I have not had chance to test this aspect with the new driver but thought it
worthwhile to flag up whilst we are discussing the updated driver.
> >
> > Paul
> > --- In ASCOM-Talk@yahoogroups.com, "dc3dreamer" <rdenny@> wrote:
> >>
> >> Thanks to Chris for the fast reaponse and fixing this. Especially
considering that he does not have a Paramount!!!
> >>
> >> If this is OK, I'll update the ASCOM Download area with 5.1.10. Chris, let
me know when you consider it OK.
> >>
> >>  -- Bob
> >>
> >> --- In ASCOM-Talk@yahoogroups.com, "John" <stnoble@> wrote:
> >>>
> >>>
> >>> Chris
> >>> Many thanks for posting the file. I was also able to test it tonight here
in the UK with success. Installed without difficulty and using TheSkyX Pro,
Paramount ME, Maxim DL5.18 calibrated at once and very satisfactory tracking.
> >>> Is it correct that 'Enable Simultaneous RA and DEC corrections' should be
OFF. I tested it with this off.
> >>> John
> >>>
> >>
> >
> >
> >
> >
> > ------------------------------------
> >
> > 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
> >
> >
> >
> >
>

Thanks all,

I'll pass the advice's on. The user runs a filter wheel and the firewire cam
through ASCOM and is more afraid of losing that capability then running the
telescope guider.

The system is for sure corrupted, hijack seems like a good possibility.

One question, if ASCOM 5.5 is installed first then ASCOM 5.0a is attempted
installed, could that cause something? The user is convinced there is no 5.5 on
his platform yet the ASCOM profile.xml says there is, and he is 'sure' is 5.0a
only.

Gene

--- In ASCOM-Talk@yahoogroups.com, "Chris" <chris_group_mail@...> wrote:
>
> What's happened is that PHD has received some error which it interprets and
reports as an ASCOM problem.  It has not reported what the error was that it
got.
>
> This hiding of the real error makes it very difficult to say what has
happened. If we had the real error we would be in a much better position to
help.
>
> Error reporting is an area where I believe that it is a mistake to modify the
information for the user.  Your audience in this case is the developer and they
need the detail of the error message in order to be able to help.
>
> I suggest that you ask Craig for the details of exactly what error triggered
this message, including the full error message.
>
> Chris
>
> --- In ASCOM-Talk@yahoogroups.com, "Peter Simpson" <peter@> wrote:
> >
> > Hi Gene,
> > Its possible that the Chooser has been unintentionally hijacked by an
> > application such as early versions of FocusMax (current versions don't
> > do this). If this is the case then re-registering the helper DLLs may
> > solve the issue:
> >
> >     1. Open an admin level command prompt
> >     2. Change to directory  C:\Program Files\Common Files\ASCOM
> >     3. Run the command: regsvr32 helper.dll
> >     4. Then run the command: regsvr32 helper2.dll
> >
> > Regards, Peter
> > --- In ASCOM-Talk@yahoogroups.com, "lynol1000" <lynol1000@> wrote:
> > >
> > > Maybe not so quick a question.
> > >
> > > One application, Firestarter 2.1, can use ASCOM telescope chooser,
> > select a scope for pulse guide purposes and launch the driver for the
> > selected scope.
> > > Another application, PHD, kicks back an error "Failed to run Scope
> > Chooser. Something is wrong with ASCOM"
> > >
> > > Any ideas what could let one program launch chooser and another not?
> > > I have been told the user is always admin user.
> > >
> > > Gene
> > >
> >
>

Thanks for the comments - I'll revisit this when I'm able to test.

regards,

Paul

--- In ASCOM-Talk@yahoogroups.com, Bob Denny <rdenny@...> wrote:
>
> This can be tricky to diagnose. I cannot speak for CCDC or CCDAP, but at least
with my ACP automation engine, MaxIm must NOT be connected for any of its
telescope/observatory controls. Therefore the auto-pier-flip setting in MaxIm
will not affect things and cause confusion. ACP manages the guiding parameters
across flips once it has been calibrated looking east (mount on west side of
pier.
>
> I would contact Matt or John for a procedure to run tests with their software
to isolate the guiding issue. I have one for ACP but it's probably not right for
those programs, and in any case they will have a way to work together to zero in
on the issue.
>
>   -- Bob
>
>
> On Jun 21, 2012, at 0:26, "Joe Bloggs" <yahoo@...> wrote:
>
> > Bob,
> >
> > Whilst we have your ear there is another potential issue.
> >
> > When using an ASCOM implemented control program (CCDAutopilot, CCDCommander
etc) AND MAxim AND TheSkyX AND a Paramount AND the "no cable" (ie "telescope")
method of autoguiding there is a problem with guiding parameters after a flip.
> >
> > It is possible to get Maxim to guide correctly after a flip (by altering the
advanced controls/auto pier flip etc) but this does not happen when Maxim is
externally controlled.
> >
> > I have posted this
(http://www.bisque.com/sc/forums/t/15513.aspx?PageIndex=2) on the Bisque forum
and the response leads me to believe I am not alone. Indeed Matt Thomas of
CCDCommander has acknowledged there is an issue.
> >
> > Please note that this does not happen with a cable to the autoguider port
(see the Bisque post).
> >
> > I have not had chance to test this aspect with the new driver but thought it
worthwhile to flag up whilst we are discussing the updated driver.
> >
> > Paul
> > --- In ASCOM-Talk@yahoogroups.com, "dc3dreamer" <rdenny@> wrote:
> >>
> >> Thanks to Chris for the fast reaponse and fixing this. Especially
considering that he does not have a Paramount!!!
> >>
> >> If this is OK, I'll update the ASCOM Download area with 5.1.10. Chris, let
me know when you consider it OK.
> >>
> >>  -- Bob
> >>
> >> --- In ASCOM-Talk@yahoogroups.com, "John" <stnoble@> wrote:
> >>>
> >>>
> >>> Chris
> >>> Many thanks for posting the file. I was also able to test it tonight here
in the UK with success. Installed without difficulty and using TheSkyX Pro,
Paramount ME, Maxim DL5.18 calibrated at once and very satisfactory tracking.
> >>> Is it correct that 'Enable Simultaneous RA and DEC corrections' should be
OFF. I tested it with this off.
> >>> John
> >>>
> >>
> >
> >
> >
> >
> > ------------------------------------
> >
> > 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
> >
> >
> >
> >
>

Hello group,

After installing the TeleAPI v5.0.4 I tried to connect TheSky6Pro to the
Gemini.Net v1.0.41.0, but it fails to connect with an error message "Failed to
load driver ASCOM.GeminiTelescope.Telescope
System.Runtime.InteropServices.COMException (0x800702E4 ..."

I suspect a permission issue, since I had to define the Gemini driver to launch
as administrator for getting it to start standalone.

Somebody can help?

Clear skies

Antoine

I will update my own message.

After running ASCOM Diagnostics, reinstalling ASCOM Platform6SP1, installing the
Gemini.Net version 1.0.44.0 with still no luck, I discovered I had to run
TheSky6Pro as administrator for everything to work. I must say also that I can
connect to other ASCOM telescope driver (POTH, Simulator)even when running
TheSky6 as normal user.

I then tried to connect CCDSoftv5 through FocusAPI to ASCOM focuser drivers.
Everything works fine with Simulator, MicroTouch Focuser and Optec TCF-S, but
when trying to connect to Gemini.NET Focuser, I get the same COM registration
issue. Again running CCDSoft as Administrator solves the issue.

So it seems I don't have an ASCOM issue but definitely a problem with my
Gemini.NET install. Maybe I should repost this thread on the Gemini.Net list?

Clear skies

Antoine

--- In ASCOM-Talk@yahoogroups.com, "antoine.pavlin" <antoine.pavlin@...> wrote:
>
> Hello group,
>
> After installing the TeleAPI v5.0.4 I tried to connect TheSky6Pro to the
Gemini.Net v1.0.41.0, but it fails to connect with an error message "Failed to
load driver ASCOM.GeminiTelescope.Telescope
System.Runtime.InteropServices.COMException (0x800702E4 ..."
>
> I suspect a permission issue, since I had to define the Gemini driver to
launch as administrator for getting it to start standalone.
>
> Somebody can help?
>
> Clear skies
>
> Antoine
>

Hello group,

Ooops, seems my reply didn't go through. I post again.

I'll reply to my own message.

After reinstalling ASCOM Platform6SP1, installing version 1.0.44.0 and running
ASCOM Diagnostics with no change to the issue, I discovered that TheSky6 would
connect through TeleAPI to other ASCOM drivers (Simulator, Poth). I also found
that running TheSky6Pro as Administrator allows me to connect to the Gemini.NET
driver, so I have at least a workaround.

I then tested CCDSoftv5 connection to ASCOM focuser drivers through FocusAPI. I
can connect fine to the MicroTouch focuser driver and to the Optec TCF-S driver.
If I try to connect to Gemini.Net Focuser driver, I get the same COM
registration issue. Again running CCDSoft as Administrator allows me to connect
to Gemini.NET. So it seems definitely that I don't have a problem with ASCOM
Platform installation, but with my install of Gemini.NET. At this point I'm not
sure it is the right place to discuss this issue. Maybe I should restart this
thread in the Gemini.Net forum?

Clear skies

Antoine

--- In ASCOM-Talk@yahoogroups.com, "antoine.pavlin" <antoine.pavlin@...> wrote:
>
> Hello group,
>
> After installing the TeleAPI v5.0.4 I tried to connect TheSky6Pro to the
Gemini.Net v1.0.41.0, but it fails to connect with an error message "Failed to
load driver ASCOM.GeminiTelescope.Telescope
System.Runtime.InteropServices.COMException (0x800702E4 ..."
>
> I suspect a permission issue, since I had to define the Gemini driver to
launch as administrator for getting it to start standalone.
>
> Somebody can help?
>
> Clear skies
>
> Antoine
>

Since my EQ6 died a slow, horrible death I decided to replace it with an
IEQ45--the price for the pier mount version seemed reasonable and most of the
reviews were favourable.  That said, it doesn't look like Ioptron has provided
very functional ASCOM drivers.  By all accounts sync doesn't work and neither
does pulse guiding.  Pretty much every aspect still needs to be entered via the
hand controller.  I guess EQMOD really spoiled me.  I'm hoping that I can leave
the hand controller in the garage and run the mount through the rs232 port. 
I'll likely code my own driver but no doubt Ioptron has some surprises in store
for me.  Their rs485 command set has a lot more features (PEC support, encoder
position/etc), but I haven't seen a USB-rs485 adapter that has +12V.  I seem to
remember another user (Bill?) mentioning that he'd start working on a new driver
as well but I don't know how that fared...

Hi Anotine,

I would suspect that the permission issue is with TheSky and/or TeleAPI rather
than the Gemini.NET driver.

I would recommend that you try to reinstall all the components, including
TheSky, 'As Administrator', and then try to run it as a regular user. I've not
heard of any permission issues between Gemini.NET and Windows 7 up to now, and
this driver has been in use for a number of years.

Regards,

     -Paul

--- In ASCOM-Talk@yahoogroups.com, "antoine.pavlin" <antoine.pavlin@...> wrote:
>
>
>
>
> Hello group,
>
> Ooops, seems my reply didn't go through. I post again.
>
> I'll reply to my own message.
>
> After reinstalling ASCOM Platform6SP1, installing version 1.0.44.0 and running
ASCOM Diagnostics with no change to the issue, I discovered that TheSky6 would
connect through TeleAPI to other ASCOM drivers (Simulator, Poth). I also found
that running TheSky6Pro as Administrator allows me to connect to the Gemini.NET
driver, so I have at least a workaround.
>
> I then tested CCDSoftv5 connection to ASCOM focuser drivers through FocusAPI.
I can connect fine to the MicroTouch focuser driver and to the Optec TCF-S
driver. If I try to connect to Gemini.Net Focuser driver, I get the same COM
registration issue. Again running CCDSoft as Administrator allows me to connect
to Gemini.NET. So it seems definitely that I don't have a problem with ASCOM
Platform installation, but with my install of Gemini.NET. At this point I'm not
sure it is the right place to discuss this issue. Maybe I should restart this
thread in the Gemini.Net forum?
>
> Clear skies
>
> Antoine
>
> --- In ASCOM-Talk@yahoogroups.com, "antoine.pavlin" <antoine.pavlin@> wrote:
> >
> > Hello group,
> >
> > After installing the TeleAPI v5.0.4 I tried to connect TheSky6Pro to the
Gemini.Net v1.0.41.0, but it fails to connect with an error message "Failed to
load driver ASCOM.GeminiTelescope.Telescope
System.Runtime.InteropServices.COMException (0x800702E4 ..."
> >
> > I suspect a permission issue, since I had to define the Gemini driver to
launch as administrator for getting it to start standalone.
> >
> > Somebody can help?
> >
> > Clear skies
> >
> > Antoine
> >
>