You should be able to use anything can can talk to COM.  A bunch can, an d I
doubt there is much advantage to one over the other.  Use whatever you are most
comfortable with.  I've used python + the Win32 extensions to do what scripting
I've done.

Bret

Being a software engineer myself I know that you all probably don't get a lot of
"kudos" and "high fives."  But I just wanted to say thanks for your hard work
and dedication to a free and awesome product.

Most opensource projects that I have dealt with are no where near as well
documented and easy to develop with.  It's nice to see that a LARGE amount of
work and thought has been put into the driver development side and not just the
"end user" side.

I've created a couple of ASCOM drivers for some personal hardware.  Most
recently I'm working on an ASCOM driver for the SupaSlim filterwheel and found
the INNO Script generator.  I'm not sure how long that's been in the dev package
but that, along with the templates and documentation made creating the driver
about a 3 hour ordeal!  Which to me seems pretty darn fast!

So keep up the good work, it's definitely appreciated and noticed!

Jared Wellman

+ 1 !

Hey All,
So I have a couple of quick questions about getting my driver "out there."

I have made a driver for the True Tech Supa Slim filter wheel and would like to
distribute the driver along with the source.  I'm one of the creators of
Sequence Generator Pro so I could post everything at our site but to me it seems
fairly non-intuitive.  I'm wondering what is required for this driver to be
hosted on the ASCOM site or at least linked to our site from the ASCOM site?

Since I don't own this hardware is there a way to run conform without connecting
to the device?

Also is there a common place to post source for the driver as well?  I can
package the source with the driver but a community repository would be better. 
I don't plan on supporting this driver much past it's creation since I don't
even own the hardware.  Does a common repo exist for something like this or
should I just create a google code project?

Thanks!
Jared

So this is limited to the combination of TheSky X and the LX200GPS driver? The
fact that the ASCOM diagnostics pass isn't surprising. Try running TheSky X as
administrator (right click the EXE, run as admin). Does it work?

   -- Bob


On Mar 9, 2012, at 13:30, "allizotiv" <vitozilla@...> wrote:

>
> Bob,
>
> I can use the form chooser just fine in MaxIm.  In TheSkyX, the form
> chooser will work when I have simulator as the selected telescope under
> the ASCOM telescope, but when I try to set the properties for the LX200,
> the error message shows up.  I ran the ASCOM diagnostic and it reports:
> Congratlations, all 1207 function tests passed!  For some reason, I
> don't feel happy about that.  :(
>
> Scratching head,
>
> Kevin
>
>
> --- In ASCOM-Talk@yahoogroups.com, "rdenny@..." <rdenny@...> wrote:
>>
>> Dang it! Looking again at the error message, the security problem is
> preventing the chooser form from loading. You're sure yo can choose from
> MaxIm, right?
>>
>> Just for completeness, run the ASCOM diagnostics and see if that shows
> anything. Maybe something has changed recently pith regard to security.
>>
>> -- Bob
>>
>>
>> On Mar 8, 2012, at 15:57, "allizotiv" vitozilla@... wrote:
>>
>>>
>>> Thanks for the response Bob,
>>>
>>> I tried your suggestions, and nothing changed...the exact same
> error.
>>> Any other ideas?
>>>
>>> Thanks,
>>>
>>> Kevin
>>>
>>>
>>> --- In ASCOM-Talk@yahoogroups.com, "rdenny@" rdenny@ wrote:
>>>>
>>>> You are correct that this is not an ASCOM or driver problem as you
>>> concluded by being able to use it all from MaxIm. This proves the
> whole
>>> ASCOM and driver setup.
>>>>
>>>> See the bold/underlined error below (UnauthorizedAccess etc.). This
> is
>>> going to be a permissions problem relating to TheSky of some sort.
>>> First, try turning Windows User Account Control off. Reboot. Now try
> to
>>> choose the LX200 in TheSky. If that works, then turn USC back on and
> run
>>> TheSky as administrator (right click on TheSkyX.exe, select Run as
>>> administrator, accept the elevation popup). Does that work?
>>>>
>>>> -- Bob
>>>>
>>>>
>>>> On Mar 7, 2012, at 15:43, "allizotiv" vitozilla@ wrote:
>>>>
>>>>>
>>>>> Greetings!
>>>>>
>>>>> I am running TheSkyX Pro 10.1.11, MaxIm DL Pro 5.18, and ASCOM
>>> Platform
>>>>> 6 build 6.0.10028.2207 on a Win 7 64 bit. I have installed the
>>>>> MeadeLX200GPS(5.0.0), TheSkyTelescope(5.2.7), and
>>>>> X2AscomTelescope(1.0.2) drivers.
>>>>>
>>>>> When following the directions in the X2-ASCOM-ReadMe notepad file,
>>> upon
>>>>> clicking on properties in step 3, I get the following error ASCOM
>>>>> Chooser window:
>>>>> Failed to load driver: "MeadeLX200GPS.Telescope"
>>>>> System.UnauthorizedAccessException: Creating an instance of the
> COM
>>>>> component with CLSID {E09E5EA3-18C9-4AAD-96C0-F474E4C374B3}
>>>>> from the IClassFactory failed due to the following error:
> 80070005.
>>>>> at System.RuntimeTypeHandle.CreateInstance(RuntimeType type,
>>>>> Boolean publicOnly, Boolean noCheck, Boolean& canBeCached,
>>>>> RuntimeMethodHandle& ctor, Boolean& bNeedSecurityCheck)
>>>>> at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly,
>>>>> Boolean fillCache)
>>>>> at System.RuntimeType.CreateInstanceImpl(Boolean publicOnly,
>>>>> Boolean skipVisibilityChecks, Boolean fillCache)
>>>>> at System.Activator.CrateInstance(Type type, Boolean nonPublic)
>>>>> at ASCOM.Utilities.ChooserForm.cmdProperties_Click(Object
>>>>> eventSender, EventArgs eventArgs) in C:\ASCOM
>>>>> Build\Export\ASCOM.Utilities\ASCOM.Utilities\ChooserForm.vb:line
> 212
>>>>>
>>>>> I can successfully control the telescope from TheSkyX (using the
>>> built
>>>>> in telescope selection dropdown setup in TheSky) and from Maxim DL
>>> using
>>>>> the LX200GPS driver (I click on properties and it takes you
> through
>>> the
>>>>> normal ASCOM setup), so I don't think there is an issue with the
>>> LX200
>>>>> driver (uninstalled an reinstalled just to make sure).
>>>>>
>>>>> Is this a known problem? If so, is there a fix?
>>>>>
>>>>> Respectfully and with great appreciation for what you guys do,
>>>>>
>>>>> Kevin
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> ------------------------------------
>>>>>
>>>>> 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
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>>
>>>
>>>
>>> ------------------------------------
>>>
>>> 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
>>>
>>>
>>>
>>>
>>
>
>
>
>
>
> ------------------------------------
>
> 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
>
>
>
>

Are you running TheSky X Professional of Serious? Can you connect from TheSky X
to the ASCOM telescope simulator?

   -- Bob


On Mar 10, 2012, at 16:54, "dan_columbus_oh" <dtowslee@...> wrote:

> I have made quite a bit of progress trying to get SkyXPro connected to  my
Atlas EQG via ASCOM X2.. but I have run into a problem I can not get around. 
After installing the ASCOM platform, the SkyX telescope driver and the X2 plugin
I was able to select the SkyX telescope in the telescope selector and was able
to get to the configuration pannel.  I can not though connect to the telescope. 
When I try, I get an error:
>
> Skyxadapter.rascomtele.1 - Internal error writing to the connected property
method '~' of object '~' failed.. Error 206 and then SxyX locks up (I can shut
the main Sky X pannel down, but the telescope toolbar stays put and the error
persists not allowing it to be cleared.  I must restart my computer to get
everything reset.  I am running Win7.  TSX daily build loaded as of today and
all drivers/plugins are current versions.
>
> I went ahead and loaded EQMOD and was able to connect to the mount and drive
it successfully so I think the ASCOM portion of the setup is good.
>
> At a dead end and looking for any suggestions.
>
>
>
>
>
> ------------------------------------
>
> 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 SO much!!!! We struggle, and endure some stress as well, because we see
frequent visitors who want to program but don't know how, or their skills aren't
quite there (or just different). It's easy to become discouraged after pouring
ourselves into this effort, only I to see that we haven't made it possible for
everyone to write drivers and/or client programs.

Thanks again poor spurring us on!!!

   -- Bob


On Mar 12, 2012, at 13:09, "rockjockjared" <jwellman@...> wrote:

> Being a software engineer myself I know that you all probably don't get a lot
of "kudos" and "high fives."  But I just wanted to say thanks for your hard work
and dedication to a free and awesome product.
>
> Most opensource projects that I have dealt with are no where near as well
documented and easy to develop with.  It's nice to see that a LARGE amount of
work and thought has been put into the driver development side and not just the
"end user" side.
>
> I've created a couple of ASCOM drivers for some personal hardware.  Most
recently I'm working on an ASCOM driver for the SupaSlim filterwheel and found
the INNO Script generator.  I'm not sure how long that's been in the dev package
but that, along with the templates and documentation made creating the driver
about a 3 hour ordeal!  Which to me seems pretty darn fast!
>
> So keep up the good work, it's definitely appreciated and noticed!
>
> Jared Wellman
>
>
>
> ------------------------------------
>
> 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
>
>
>
>

Hi,
thanks for your hint. You were right, the dll was still registered, thus the
server was not started at all. This is done now and it really seems to work.
One issue is still open, which means:

The server is started, when the first client connects. But when is the server
shut down? Currently it doesn't seem to close at all until I kill it via
TaskManager, but this can't be the solution.
Did I miss anything there?
Regards,

Matthias

Autocorrect on iPad ... The word 'for' got changed to poor. Sometimes funny!!

   -- Bob


On Mar 13, 2012, at 17:04, Bob Denny <rdenny@...> wrote:

> Thanks SO much!!!! We struggle, and endure some stress as well, because we see
frequent visitors who want to program but don't know how, or their skills aren't
quite there (or just different). It's easy to become discouraged after pouring
ourselves into this effort, only I to see that we haven't made it possible for
everyone to write drivers and/or client programs.
>
> Thanks again poor spurring us on!!!
>
>  -- Bob
>
>
> On Mar 12, 2012, at 13:09, "rockjockjared" <jwellman@...> wrote:
>
>> Being a software engineer myself I know that you all probably don't get a lot
of "kudos" and "high fives."  But I just wanted to say thanks for your hard work
and dedication to a free and awesome product.
>>
>> Most opensource projects that I have dealt with are no where near as well
documented and easy to develop with.  It's nice to see that a LARGE amount of
work and thought has been put into the driver development side and not just the
"end user" side.
>>
>> I've created a couple of ASCOM drivers for some personal hardware.  Most
recently I'm working on an ASCOM driver for the SupaSlim filterwheel and found
the INNO Script generator.  I'm not sure how long that's been in the dev package
but that, along with the templates and documentation made creating the driver
about a 3 hour ordeal!  Which to me seems pretty darn fast!
>>
>> So keep up the good work, it's definitely appreciated and noticed!
>>
>> Jared Wellman
>>
>>
>>
>> ------------------------------------
>>
>> 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
>>
>>
>>
>>
>
>
> ------------------------------------
>
> 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
>
>
>
>

The ASCOM source recently moved to sourceforge.  There was also a repository for
third party drivers that didn't move with the main repository. I'm not sure
whether the plan is to eventually move it or continue using it where it is. 
Perhaps someone who knows the plan can chime in on that front.

To get a link put on the web site, you have to first have conform output showing
your driver passes.  Once you have that, you need to contact Bob Denny, who
actually adds the link.  You used to submit a defect to the ASCOM Jira but
tracker, but as far as I can tell that is no longer monitored. Direct email to
Bob worked for me on my last request.

As for getting conform output without the device, you will probably have to look
for volunteers with the device. I'm the author of the Starlight Xpress camera
driver, and they make a bunch of cameras that I don't own.  I have a yahoo group
where people interested in the driver can find me, and I have them run conform
on the cameras they own.

Bret

 

The ASCOM source recently moved to sourceforge. There was also a repository for third party drivers that didn't move with the main repository. I'm not sure whether the plan is to eventually move it or continue using it where it is. Perhaps someone who knows the plan can chime in on that front.

Sander:

The contrib tree is the part that I didn't get moved with the rest (as  best I
can tell).

Bret

 

Sander:

The contrib tree is the part that I didn't get moved with the rest (as best I can tell).

Bret ~-|**|PrettyHtmlEnd|**|-~ end group email -->

I have post this message before several days and no one have any answer no one
knows about  Dome Control Panel very strange???? I just need to call the
functions and set properties of the Dome Control Panel????


Tsatham


--- In ASCOM-Talk@yahoogroups.com, "tsatham" <tsatham@...> wrote:
>
> Hi all,
>
> I am searching for source code or the API(Application programing Interface) or
script  for the Dome Control Panel ,I would like to slave the dome to the
telescope using a script I could not slave my dome to the scope using ASCOM dome
driver the property Dome.CanSlave always returns false OK the dome did not know
where is the scope many thanks in advance any help very welcome.
>

Hello Bob,

We already tried this, but I tried again, and even when running in
admin, the same error shows.  Very strange.  TSX has built in a LX200
control under the telescope setup, so if I'm running MaxIm with "TSX
controlled telescope", is it necessary to setup the ASCOM telescope
control in TSX vice the LX200 telescope control?  What are the
advantages of using one control over the other?  When in MaxIm, if I
choose LX200 for telescope control I can select properties just fine
(the initial HIGHLY recommended to read help file notification window
opens first...but the error immediately shows when in TSX ASCOM
chooser).  There is something different between the two how they call on
the driver.

Thanks,

Kevin


--- In ASCOM-Talk@yahoogroups.com, Bob Denny <rdenny@...> wrote:
>
> So this is limited to the combination of TheSky X and the LX200GPS
driver? The fact that the ASCOM diagnostics pass isn't surprising. Try
running TheSky X as administrator (right click the EXE, run as admin).
Does it work?
>
> -- Bob
>
>
> On Mar 9, 2012, at 13:30, "allizotiv" vitozilla@... wrote:
>
> >
> > Bob,
> >
> > I can use the form chooser just fine in MaxIm. In TheSkyX, the form
> > chooser will work when I have simulator as the selected telescope
under
> > the ASCOM telescope, but when I try to set the properties for the
LX200,
> > the error message shows up. I ran the ASCOM diagnostic and it
reports:
> > Congratlations, all 1207 function tests passed! For some reason, I
> > don't feel happy about that. :(
> >
> > Scratching head,
> >
> > Kevin
> >
> >
> > --- In ASCOM-Talk@yahoogroups.com, "rdenny@" rdenny@ wrote:
> >>
> >> Dang it! Looking again at the error message, the security problem
is
> > preventing the chooser form from loading. You're sure yo can choose
from
> > MaxIm, right?
> >>
> >> Just for completeness, run the ASCOM diagnostics and see if that
shows
> > anything. Maybe something has changed recently pith regard to
security.
> >>
> >> -- Bob
> >>
> >>
> >> On Mar 8, 2012, at 15:57, "allizotiv" vitozilla@ wrote:
> >>
> >>>
> >>> Thanks for the response Bob,
> >>>
> >>> I tried your suggestions, and nothing changed...the exact same
> > error.
> >>> Any other ideas?
> >>>
> >>> Thanks,
> >>>
> >>> Kevin
> >>>
> >>>
> >>> --- In ASCOM-Talk@yahoogroups.com, "rdenny@" rdenny@ wrote:
> >>>>
> >>>> You are correct that this is not an ASCOM or driver problem as
you
> >>> concluded by being able to use it all from MaxIm. This proves the
> > whole
> >>> ASCOM and driver setup.
> >>>>
> >>>> See the bold/underlined error below (UnauthorizedAccess etc.).
This
> > is
> >>> going to be a permissions problem relating to TheSky of some sort.
> >>> First, try turning Windows User Account Control off. Reboot. Now
try
> > to
> >>> choose the LX200 in TheSky. If that works, then turn USC back on
and
> > run
> >>> TheSky as administrator (right click on TheSkyX.exe, select Run as
> >>> administrator, accept the elevation popup). Does that work?
> >>>>
> >>>> -- Bob
> >>>>
> >>>>
> >>>> On Mar 7, 2012, at 15:43, "allizotiv" vitozilla@ wrote:
> >>>>
> >>>>>
> >>>>> Greetings!
> >>>>>
> >>>>> I am running TheSkyX Pro 10.1.11, MaxIm DL Pro 5.18, and ASCOM
> >>> Platform
> >>>>> 6 build 6.0.10028.2207 on a Win 7 64 bit. I have installed the
> >>>>> MeadeLX200GPS(5.0.0), TheSkyTelescope(5.2.7), and
> >>>>> X2AscomTelescope(1.0.2) drivers.
> >>>>>
> >>>>> When following the directions in the X2-ASCOM-ReadMe notepad
file,
> >>> upon
> >>>>> clicking on properties in step 3, I get the following error
ASCOM
> >>>>> Chooser window:
> >>>>> Failed to load driver: "MeadeLX200GPS.Telescope"
> >>>>> System.UnauthorizedAccessException: Creating an instance of the
> > COM
> >>>>> component with CLSID {E09E5EA3-18C9-4AAD-96C0-F474E4C374B3}
> >>>>> from the IClassFactory failed due to the following error:
> > 80070005.
> >>>>> at System.RuntimeTypeHandle.CreateInstance(RuntimeType type,
> >>>>> Boolean publicOnly, Boolean noCheck, Boolean& canBeCached,
> >>>>> RuntimeMethodHandle& ctor, Boolean& bNeedSecurityCheck)
> >>>>> at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly,
> >>>>> Boolean fillCache)
> >>>>> at System.RuntimeType.CreateInstanceImpl(Boolean publicOnly,
> >>>>> Boolean skipVisibilityChecks, Boolean fillCache)
> >>>>> at System.Activator.CrateInstance(Type type, Boolean nonPublic)
> >>>>> at ASCOM.Utilities.ChooserForm.cmdProperties_Click(Object
> >>>>> eventSender, EventArgs eventArgs) in C:\ASCOM
> >>>>> Build\Export\ASCOM.Utilities\ASCOM.Utilities\ChooserForm.vb:line
> > 212
> >>>>>
> >>>>> I can successfully control the telescope from TheSkyX (using the
> >>> built
> >>>>> in telescope selection dropdown setup in TheSky) and from Maxim
DL
> >>> using
> >>>>> the LX200GPS driver (I click on properties and it takes you
> > through
> >>> the
> >>>>> normal ASCOM setup), so I don't think there is an issue with the
> >>> LX200
> >>>>> driver (uninstalled an reinstalled just to make sure).
> >>>>>
> >>>>> Is this a known problem? If so, is there a fix?
> >>>>>
> >>>>> Respectfully and with great appreciation for what you guys do,
> >>>>>
> >>>>> Kevin
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> ------------------------------------
> >>>>>
> >>>>> 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
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> ------------------------------------
> >>>
> >>> 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
> >>>
> >>>
> >>>
> >>>
> >>
> >
> >
> >
> >
> >
> > ------------------------------------
> >
> > 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
> >
> >
> >
> >
>

Kevin --

So many questions, plus wanting to know all of the differences between the
Bisque LX200 support and the features of the ASCOM LX200 driver. It will be far
more efficient to talk about it over the phone. Please feel free to call 480 396
9700 business hours UTC-7. For all of that.

On the permission violation issue, I am unable to come up with an answer, sorry.
I just can't think of any other reason...

   -- Bob


On Mar 14, 2012, at 9:59, "allizotiv" <vitozilla@...> wrote:

>
> Hello Bob,
>
> We already tried this, but I tried again, and even when running in
> admin, the same error shows.  Very strange.  TSX has built in a LX200
> control under the telescope setup, so if I'm running MaxIm with "TSX
> controlled telescope", is it necessary to setup the ASCOM telescope
> control in TSX vice the LX200 telescope control?  What are the
> advantages of using one control over the other?  When in MaxIm, if I
> choose LX200 for telescope control I can select properties just fine
> (the initial HIGHLY recommended to read help file notification window
> opens first...but the error immediately shows when in TSX ASCOM
> chooser).  There is something different between the two how they call on
> the driver.
>
> Thanks,
>
> Kevin
>
>
> --- In ASCOM-Talk@yahoogroups.com, Bob Denny <rdenny@...> wrote:
>>
>> So this is limited to the combination of TheSky X and the LX200GPS
> driver? The fact that the ASCOM diagnostics pass isn't surprising. Try
> running TheSky X as administrator (right click the EXE, run as admin).
> Does it work?
>>
>> -- Bob
>>
>>
>> On Mar 9, 2012, at 13:30, "allizotiv" vitozilla@... wrote:
>>
>>>
>>> Bob,
>>>
>>> I can use the form chooser just fine in MaxIm. In TheSkyX, the form
>>> chooser will work when I have simulator as the selected telescope
> under
>>> the ASCOM telescope, but when I try to set the properties for the
> LX200,
>>> the error message shows up. I ran the ASCOM diagnostic and it
> reports:
>>> Congratlations, all 1207 function tests passed! For some reason, I
>>> don't feel happy about that. :(
>>>
>>> Scratching head,
>>>
>>> Kevin
>>>
>>>
>>> --- In ASCOM-Talk@yahoogroups.com, "rdenny@" rdenny@ wrote:
>>>>
>>>> Dang it! Looking again at the error message, the security problem
> is
>>> preventing the chooser form from loading. You're sure yo can choose
> from
>>> MaxIm, right?
>>>>
>>>> Just for completeness, run the ASCOM diagnostics and see if that
> shows
>>> anything. Maybe something has changed recently pith regard to
> security.
>>>>
>>>> -- Bob
>>>>
>>>>
>>>> On Mar 8, 2012, at 15:57, "allizotiv" vitozilla@ wrote:
>>>>
>>>>>
>>>>> Thanks for the response Bob,
>>>>>
>>>>> I tried your suggestions, and nothing changed...the exact same
>>> error.
>>>>> Any other ideas?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Kevin
>>>>>
>>>>>
>>>>> --- In ASCOM-Talk@yahoogroups.com, "rdenny@" rdenny@ wrote:
>>>>>>
>>>>>> You are correct that this is not an ASCOM or driver problem as
> you
>>>>> concluded by being able to use it all from MaxIm. This proves the
>>> whole
>>>>> ASCOM and driver setup.
>>>>>>
>>>>>> See the bold/underlined error below (UnauthorizedAccess etc.).
> This
>>> is
>>>>> going to be a permissions problem relating to TheSky of some sort.
>>>>> First, try turning Windows User Account Control off. Reboot. Now
> try
>>> to
>>>>> choose the LX200 in TheSky. If that works, then turn USC back on
> and
>>> run
>>>>> TheSky as administrator (right click on TheSkyX.exe, select Run as
>>>>> administrator, accept the elevation popup). Does that work?
>>>>>>
>>>>>> -- Bob
>>>>>>
>>>>>>
>>>>>> On Mar 7, 2012, at 15:43, "allizotiv" vitozilla@ wrote:
>>>>>>
>>>>>>>
>>>>>>> Greetings!
>>>>>>>
>>>>>>> I am running TheSkyX Pro 10.1.11, MaxIm DL Pro 5.18, and ASCOM
>>>>> Platform
>>>>>>> 6 build 6.0.10028.2207 on a Win 7 64 bit. I have installed the
>>>>>>> MeadeLX200GPS(5.0.0), TheSkyTelescope(5.2.7), and
>>>>>>> X2AscomTelescope(1.0.2) drivers.
>>>>>>>
>>>>>>> When following the directions in the X2-ASCOM-ReadMe notepad
> file,
>>>>> upon
>>>>>>> clicking on properties in step 3, I get the following error
> ASCOM
>>>>>>> Chooser window:
>>>>>>> Failed to load driver: "MeadeLX200GPS.Telescope"
>>>>>>> System.UnauthorizedAccessException: Creating an instance of the
>>> COM
>>>>>>> component with CLSID {E09E5EA3-18C9-4AAD-96C0-F474E4C374B3}
>>>>>>> from the IClassFactory failed due to the following error:
>>> 80070005.
>>>>>>> at System.RuntimeTypeHandle.CreateInstance(RuntimeType type,
>>>>>>> Boolean publicOnly, Boolean noCheck, Boolean& canBeCached,
>>>>>>> RuntimeMethodHandle& ctor, Boolean& bNeedSecurityCheck)
>>>>>>> at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly,
>>>>>>> Boolean fillCache)
>>>>>>> at System.RuntimeType.CreateInstanceImpl(Boolean publicOnly,
>>>>>>> Boolean skipVisibilityChecks, Boolean fillCache)
>>>>>>> at System.Activator.CrateInstance(Type type, Boolean nonPublic)
>>>>>>> at ASCOM.Utilities.ChooserForm.cmdProperties_Click(Object
>>>>>>> eventSender, EventArgs eventArgs) in C:\ASCOM
>>>>>>> Build\Export\ASCOM.Utilities\ASCOM.Utilities\ChooserForm.vb:line
>>> 212
>>>>>>>
>>>>>>> I can successfully control the telescope from TheSkyX (using the
>>>>> built
>>>>>>> in telescope selection dropdown setup in TheSky) and from Maxim
> DL
>>>>> using
>>>>>>> the LX200GPS driver (I click on properties and it takes you
>>> through
>>>>> the
>>>>>>> normal ASCOM setup), so I don't think there is an issue with the
>>>>> LX200
>>>>>>> driver (uninstalled an reinstalled just to make sure).
>>>>>>>
>>>>>>> Is this a known problem? If so, is there a fix?
>>>>>>>
>>>>>>> Respectfully and with great appreciation for what you guys do,
>>>>>>>
>>>>>>> Kevin
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ------------------------------------
>>>>>>>
>>>>>>> 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
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> ------------------------------------
>>>>>
>>>>> 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
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>>
>>>
>>>
>>> ------------------------------------
>>>
>>> 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
>>>
>>>
>>>
>>>
>>
>
>
>
>
>
> ------------------------------------
>
> 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
>
>
>
>

I had this same problem with a Belkin F5U109 USB to Serial adapter
ASCOM 5b was fine but when I installed the 5.5.1 update I got the
described behavior. Uninstalling ASCOM and re installing without
the update and the behavior was normal, if you walked away for 5 min
your program would become responsive again, but once any traffic went
the the telescope the lag would reappear.

this would suggest that the problem is with a change with the ASCOM
platform, my working theory is that the serial port commands are
  timing out but that is just speculation to describe the problem to
the ASCOM dev's it's like setting the count for ReceiveCountedBinary()
too high and having to wait for the timeout for every command sent
to the scope and the program using the driver is stuck waiting for the
command to complete.

I still have the USB adapter, and could try to reproduce the problem
if a Dev wanted to fix it.

--- In ASCOM-Talk@yahoogroups.com, ANDREW LINDSAY <andrew.lindsay@...> wrote:
>
> Dear group,
> I have installed the Ascom package including the Unified Celestron Driver
> 5.0.23 for my Celestron CPC800XLT.
>
> When I try to connect using ASCOM through either TheSkyX or MaxImDL, the
> whole computer slows down to a crawl and becomes unresponsive.
>
> I have tried other native programs that do not use ASCOM to check the comms,
> and in native mode, the communications work flawlessly.
>
> Does anyone have any experience with this, what sort of things should I be
> trying to fix it.
>
> Is the Driver 5.0.23 the latest version?
>
> Best regards
>
> Andrew Lindsay
>

If you want to try enabling serial port logging, reproducing the problem
and posting the log to the files area, with a commentary describing what
you are seeing, including the times of significant events I'll have a look.

But I don't think it's anything as obvious as a timeout or miscounting
bytes.  This sort of thing seems to be associated with USB devices in
some way.

The change from 5.0 to 5.5 was to change from the elderly MCOMM32 serila
driver to using the .NET driver and in most cases it helped. We get far
fewer reports of serial port problems now.  The trouble is that the bad
devices seem to be good at avoiding developers so it's difficult to get
a handle on it - although I may have one at my astro society's observatory.

The USB serial adaptors that seem to be most reliable are the FTDI or
IOPort ones. Prolific seem to be OK if you get a real one but there are
a lot of counterfeit ones about.

Chris

On 15/03/2012 19:52, Adam wrote:
> I had this same problem with a Belkin F5U109 USB to Serial adapter
> ASCOM 5b was fine but when I installed the 5.5.1 update I got the
> described behavior. Uninstalling ASCOM and re installing without
> the update and the behavior was normal, if you walked away for 5 min
> your program would become responsive again, but once any traffic went
> the the telescope the lag would reappear.
>
> this would suggest that the problem is with a change with the ASCOM
> platform, my working theory is that the serial port commands are
>   timing out but that is just speculation to describe the problem to
> the ASCOM dev's it's like setting the count for ReceiveCountedBinary()
> too high and having to wait for the timeout for every command sent
> to the scope and the program using the driver is stuck waiting for the
> command to complete.
>
> I still have the USB adapter, and could try to reproduce the problem
> if a Dev wanted to fix it.
>
> --- In ASCOM-Talk@yahoogroups.com, ANDREW LINDSAY<andrew.lindsay@...>  wrote:
>>
>> Dear group,
>> I have installed the Ascom package including the Unified Celestron Driver
>> 5.0.23 for my Celestron CPC800XLT.
>>
>> When I try to connect using ASCOM through either TheSkyX or MaxImDL, the
>> whole computer slows down to a crawl and becomes unresponsive.
>>
>> I have tried other native programs that do not use ASCOM to check the comms,
>> and in native mode, the communications work flawlessly.
>>
>> Does anyone have any experience with this, what sort of things should I be
>> trying to fix it.
>>
>> Is the Driver 5.0.23 the latest version?
>>
>> Best regards
>>
>> Andrew Lindsay
>>
>
>
>
> ------------------------------------
>
> 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
>
>
>
>

uploaded file "SerialDebug.zip" in files section, I included a trace
for an FTDI device for contrast. I used ASCOM diagnostics to connect
to the driver and when the hand control appeared I  pressed the up
button a few time's once the scope stated moving I release the button
at which time it took aprox 5 sec for the scope to stop moving.

I tried the incomplete driver I am writing and had the same results,
so that eliminates a problem Celestron driver.

If i'm reading the trace log correctly it appears that ReceiveCountedBinary() is
timing out.

hope this helps.

--- In ASCOM-Talk@yahoogroups.com, Chris Rowland <chris_group_mail@...> wrote:
>
> If you want to try enabling serial port logging, reproducing the problem
> and posting the log to the files area, with a commentary describing what
> you are seeing, including the times of significant events I'll have a look.
>
> But I don't think it's anything as obvious as a timeout or miscounting
> bytes.  This sort of thing seems to be associated with USB devices in
> some way.
>
> The change from 5.0 to 5.5 was to change from the elderly MCOMM32 serila
> driver to using the .NET driver and in most cases it helped. We get far
> fewer reports of serial port problems now.  The trouble is that the bad
> devices seem to be good at avoiding developers so it's difficult to get
> a handle on it - although I may have one at my astro society's observatory.
>
> The USB serial adaptors that seem to be most reliable are the FTDI or
> IOPort ones. Prolific seem to be OK if you get a real one but there are
> a lot of counterfeit ones about.
>
> Chris
>
> On 15/03/2012 19:52, Adam wrote:
> > I had this same problem with a Belkin F5U109 USB to Serial adapter
> > ASCOM 5b was fine but when I installed the 5.5.1 update I got the
> > described behavior. Uninstalling ASCOM and re installing without
> > the update and the behavior was normal, if you walked away for 5 min
> > your program would become responsive again, but once any traffic went
> > the the telescope the lag would reappear.
> >
> > this would suggest that the problem is with a change with the ASCOM
> > platform, my working theory is that the serial port commands are
> >   timing out but that is just speculation to describe the problem to
> > the ASCOM dev's it's like setting the count for ReceiveCountedBinary()
> > too high and having to wait for the timeout for every command sent
> > to the scope and the program using the driver is stuck waiting for the
> > command to complete.
> >
> > I still have the USB adapter, and could try to reproduce the problem
> > if a Dev wanted to fix it.
> >
> > --- In ASCOM-Talk@yahoogroups.com, ANDREW LINDSAY<andrew.lindsay@>  wrote:
> >>
> >> Dear group,
> >> I have installed the Ascom package including the Unified Celestron Driver
> >> 5.0.23 for my Celestron CPC800XLT.
> >>
> >> When I try to connect using ASCOM through either TheSkyX or MaxImDL, the
> >> whole computer slows down to a crawl and becomes unresponsive.
> >>
> >> I have tried other native programs that do not use ASCOM to check the
comms,
> >> and in native mode, the communications work flawlessly.
> >>
> >> Does anyone have any experience with this, what sort of things should I be
> >> trying to fix it.
> >>
> >> Is the Driver 5.0.23 the latest version?
> >>
> >> Best regards
> >>
> >> Andrew Lindsay
> >>
> >
> >
> >
> > ------------------------------------
> >
> > 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
> >
> >
> >
> >
>

I tried one more test, which was to get the sidereal time from the
scope using ReceiveTerminatedBinary() and then ReceiveCountedBinary(),
with time out set to 10 sec then writing the buffers to files, both
methods took about 10 sec to complete and both methods produced
buffers with the expected data.

--- In ASCOM-Talk@yahoogroups.com, "Adam" <adamrosas1972@...> wrote:
>
> uploaded file "SerialDebug.zip" in files section, I included a trace
> for an FTDI device for contrast. I used ASCOM diagnostics to connect
> to the driver and when the hand control appeared I  pressed the up
> button a few time's once the scope stated moving I release the button
> at which time it took aprox 5 sec for the scope to stop moving.
>
> I tried the incomplete driver I am writing and had the same results,
> so that eliminates a problem Celestron driver.
>
> If i'm reading the trace log correctly it appears that ReceiveCountedBinary()
is timing out.
>
> hope this helps.
>
> --- In ASCOM-Talk@yahoogroups.com, Chris Rowland <chris_group_mail@> wrote:
> >
> > If you want to try enabling serial port logging, reproducing the problem
> > and posting the log to the files area, with a commentary describing what
> > you are seeing, including the times of significant events I'll have a look.
> >
> > But I don't think it's anything as obvious as a timeout or miscounting
> > bytes.  This sort of thing seems to be associated with USB devices in
> > some way.
> >
> > The change from 5.0 to 5.5 was to change from the elderly MCOMM32 serila
> > driver to using the .NET driver and in most cases it helped. We get far
> > fewer reports of serial port problems now.  The trouble is that the bad
> > devices seem to be good at avoiding developers so it's difficult to get
> > a handle on it - although I may have one at my astro society's observatory.
> >
> > The USB serial adaptors that seem to be most reliable are the FTDI or
> > IOPort ones. Prolific seem to be OK if you get a real one but there are
> > a lot of counterfeit ones about.
> >
> > Chris
> >
> > On 15/03/2012 19:52, Adam wrote:
> > > I had this same problem with a Belkin F5U109 USB to Serial adapter
> > > ASCOM 5b was fine but when I installed the 5.5.1 update I got the
> > > described behavior. Uninstalling ASCOM and re installing without
> > > the update and the behavior was normal, if you walked away for 5 min
> > > your program would become responsive again, but once any traffic went
> > > the the telescope the lag would reappear.
> > >
> > > this would suggest that the problem is with a change with the ASCOM
> > > platform, my working theory is that the serial port commands are
> > >   timing out but that is just speculation to describe the problem to
> > > the ASCOM dev's it's like setting the count for ReceiveCountedBinary()
> > > too high and having to wait for the timeout for every command sent
> > > to the scope and the program using the driver is stuck waiting for the
> > > command to complete.
> > >
> > > I still have the USB adapter, and could try to reproduce the problem
> > > if a Dev wanted to fix it.
> > >
> > > --- In ASCOM-Talk@yahoogroups.com, ANDREW LINDSAY<andrew.lindsay@>  wrote:
> > >>
> > >> Dear group,
> > >> I have installed the Ascom package including the Unified Celestron Driver
> > >> 5.0.23 for my Celestron CPC800XLT.
> > >>
> > >> When I try to connect using ASCOM through either TheSkyX or MaxImDL, the
> > >> whole computer slows down to a crawl and becomes unresponsive.
> > >>
> > >> I have tried other native programs that do not use ASCOM to check the
comms,
> > >> and in native mode, the communications work flawlessly.
> > >>
> > >> Does anyone have any experience with this, what sort of things should I
be
> > >> trying to fix it.
> > >>
> > >> Is the Driver 5.0.23 the latest version?
> > >>
> > >> Best regards
> > >>
> > >> Andrew Lindsay
> > >>
> > >
> > >
> > >
> > > ------------------------------------
> > >
> > > 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
> > >
> > >
> > >
> > >
> >
>

Gday All

I posted re an LX200GPS locking up on a timeout problem
recently but got no answers
http://tech.groups.yahoo.com/group/ASCOM-Talk/message/26537
Is it possible that some new buglet has come about
in one of the serial processes as a result of the
latest platform update???

Andrew Johansen Melbourne Australia

--- In ASCOM-Talk@yahoogroups.com, "Adam" <adamrosas1972@...> wrote:
>
>
>
>
>
>
>
> I tried one more test, which was to get the sidereal time from the
> scope using ReceiveTerminatedBinary() and then ReceiveCountedBinary(),
> with time out set to 10 sec then writing the buffers to files, both
> methods took about 10 sec to complete and both methods produced
> buffers with the expected data.
>
> --- In ASCOM-Talk@yahoogroups.com, "Adam" <adamrosas1972@> wrote:
> >
> > uploaded file "SerialDebug.zip" in files section, I included a trace
> > for an FTDI device for contrast. I used ASCOM diagnostics to connect
> > to the driver and when the hand control appeared I  pressed the up
> > button a few time's once the scope stated moving I release the button
> > at which time it took aprox 5 sec for the scope to stop moving.
> >
> > I tried the incomplete driver I am writing and had the same results,
> > so that eliminates a problem Celestron driver.
> >
> > If i'm reading the trace log correctly it appears that
ReceiveCountedBinary() is timing out.
> >
> > hope this helps.
> >
> > --- In ASCOM-Talk@yahoogroups.com, Chris Rowland <chris_group_mail@> wrote:
> > >
> > > If you want to try enabling serial port logging, reproducing the problem
> > > and posting the log to the files area, with a commentary describing what
> > > you are seeing, including the times of significant events I'll have a
look.
> > >
> > > But I don't think it's anything as obvious as a timeout or miscounting
> > > bytes.  This sort of thing seems to be associated with USB devices in
> > > some way.
> > >
> > > The change from 5.0 to 5.5 was to change from the elderly MCOMM32 serila
> > > driver to using the .NET driver and in most cases it helped. We get far
> > > fewer reports of serial port problems now.  The trouble is that the bad
> > > devices seem to be good at avoiding developers so it's difficult to get
> > > a handle on it - although I may have one at my astro society's
observatory.
> > >
> > > The USB serial adaptors that seem to be most reliable are the FTDI or
> > > IOPort ones. Prolific seem to be OK if you get a real one but there are
> > > a lot of counterfeit ones about.
> > >
> > > Chris
> > >
> > > On 15/03/2012 19:52, Adam wrote:
> > > > I had this same problem with a Belkin F5U109 USB to Serial adapter
> > > > ASCOM 5b was fine but when I installed the 5.5.1 update I got the
> > > > described behavior. Uninstalling ASCOM and re installing without
> > > > the update and the behavior was normal, if you walked away for 5 min
> > > > your program would become responsive again, but once any traffic went
> > > > the the telescope the lag would reappear.
> > > >
> > > > this would suggest that the problem is with a change with the ASCOM
> > > > platform, my working theory is that the serial port commands are
> > > >   timing out but that is just speculation to describe the problem to
> > > > the ASCOM dev's it's like setting the count for ReceiveCountedBinary()
> > > > too high and having to wait for the timeout for every command sent
> > > > to the scope and the program using the driver is stuck waiting for the
> > > > command to complete.
> > > >
> > > > I still have the USB adapter, and could try to reproduce the problem
> > > > if a Dev wanted to fix it.
> > > >
> > > > --- In ASCOM-Talk@yahoogroups.com, ANDREW LINDSAY<andrew.lindsay@> 
wrote:
> > > >>
> > > >> Dear group,
> > > >> I have installed the Ascom package including the Unified Celestron
Driver
> > > >> 5.0.23 for my Celestron CPC800XLT.
> > > >>
> > > >> When I try to connect using ASCOM through either TheSkyX or MaxImDL,
the
> > > >> whole computer slows down to a crawl and becomes unresponsive.
> > > >>
> > > >> I have tried other native programs that do not use ASCOM to check the
comms,
> > > >> and in native mode, the communications work flawlessly.
> > > >>
> > > >> Does anyone have any experience with this, what sort of things should I
be
> > > >> trying to fix it.
> > > >>
> > > >> Is the Driver 5.0.23 the latest version?
> > > >>
> > > >> Best regards
> > > >>
> > > >> Andrew Lindsay
> > > >>
> > > >
> > > >
> > > >
> > > > ------------------------------------
> > > >
> > > > 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
> > > >
> > > >
> > > >
> > > >
> > >
> >
>

Two days ago I went to use the serial connection on my iEQ45 with a serial to
usb adapter and updated the Ascom platform.  This adapter has worked many times
in the past with my minitowers and the iEQ45.  I got an error saying that it
can't connect to the com port 3.  The com port is correct and if I try and use
it with Celestron or Meade Ascom drivers I have no issue.  The only change I
made was update the Ascom platform.  The previous update was back in Aug. 2011.

I tried another adapter that also has worked in the past and obtained the same
results.

I've changed com ports and that has no effect.

Any help would be appreciated.

Don

The other day I went to use my serial port for the iEQ45 so I hooked up the
cable and the serial to USB adapter I always use.  I did an update to ASCOM
Platform 6 and proceeded to try and communicate with my iEQ45 mount.  I got an
error saying that it couldn't open com port 3.  I tried another serial to usb
device and no difference.  I tried different com ports and no difference.  I
then tried using it with a Celestron driver and the com port was recognized, and
it also worked with Meade driver LX200.  I tried two other computers using the
latest ASCOM platform and no dice.  I have tried using it on Windows XP and
Windows 7 machines and no difference.  I tried using other programs that use the
ASCOM platform to communicate and I still get the error no com port open when
using the iOptron driver.

It worked in the past with last years ASCOM Platform 6.

Any idea what may be the issue.

Does anyone have the original ASCOM Platform 6?

Don

Gday Peter

--- In ASCOM-Talk@yahoogroups.com, "Peter Simpson" <peter@...> wrote:
>
> Hi Andrew,
> I checked the SubVersion logs and the last change to
> the Serial code was in April 2011. It thus looks unlikely
>  that a recent Platform code change
> is responsible for the issues that you and Adam are seeing.

It doesnt affect me as i dont use ASCOM :-)
My query was more along the lines of
"has something changed in the guts of "dot net" land"
that is now showing up as a timeout bug????"
I have no means to check this
but it seems a "possible" culprit based on
the various posts to date.

Andrew Johansen Melbourne Australia


> Regards, Peter
> --- In ASCOM-Talk@yahoogroups.com, "johansea" <johansea@> wrote:
> >
> > Gday All
> >
> > I posted re an LX200GPS locking up on a timeout problem
> > recently but got no answers
> > http://tech.groups.yahoo.com/group/ASCOM-Talk/message/26537
> > Is it possible that some new buglet has come about
> > in one of the serial processes as a result of the
> > latest platform update???
> >
> > Andrew Johansen Melbourne Australia
> >
> > --- In ASCOM-Talk@yahoogroups.com, "Adam" adamrosas1972@ wrote:
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > I tried one more test, which was to get the sidereal time from the
> > > scope using ReceiveTerminatedBinary() and then
> ReceiveCountedBinary(),
> > > with time out set to 10 sec then writing the buffers to files, both
> > > methods took about 10 sec to complete and both methods produced
> > > buffers with the expected data.
> > >
> > > --- In ASCOM-Talk@yahoogroups.com, "Adam" <adamrosas1972@> wrote:
> > > >
> > > > uploaded file "SerialDebug.zip" in files section, I included a
> trace
> > > > for an FTDI device for contrast. I used ASCOM diagnostics to
> connect
> > > > to the driver and when the hand control appeared I  pressed the up
> > > > button a few time's once the scope stated moving I release the
> button
> > > > at which time it took aprox 5 sec for the scope to stop moving.
> > > >
> > > > I tried the incomplete driver I am writing and had the same
> results,
> > > > so that eliminates a problem Celestron driver.
> > > >
> > > > If i'm reading the trace log correctly it appears that
> ReceiveCountedBinary() is timing out.
> > > >
> > > > hope this helps.
> > > >
> > > > --- In ASCOM-Talk@yahoogroups.com, Chris Rowland
> <chris_group_mail@> wrote:
> > > > >
> > > > > If you want to try enabling serial port logging, reproducing the
> problem
> > > > > and posting the log to the files area, with a commentary
> describing what
> > > > > you are seeing, including the times of significant events I'll
> have a look.
> > > > >
> > > > > But I don't think it's anything as obvious as a timeout or
> miscounting
> > > > > bytes.  This sort of thing seems to be associated with USB
> devices in
> > > > > some way.
> > > > >
> > > > > The change from 5.0 to 5.5 was to change from the elderly
> MCOMM32 serila
> > > > > driver to using the .NET driver and in most cases it helped. We
> get far
> > > > > fewer reports of serial port problems now.  The trouble is that
> the bad
> > > > > devices seem to be good at avoiding developers so it's difficult
> to get
> > > > > a handle on it - although I may have one at my astro society's
> observatory.
> > > > >
> > > > > The USB serial adaptors that seem to be most reliable are the
> FTDI or
> > > > > IOPort ones. Prolific seem to be OK if you get a real one but
> there are
> > > > > a lot of counterfeit ones about.
> > > > >
> > > > > Chris
> > > > >
> > > > > On 15/03/2012 19:52, Adam wrote:
> > > > > > I had this same problem with a Belkin F5U109 USB to Serial
> adapter
> > > > > > ASCOM 5b was fine but when I installed the 5.5.1 update I got
> the
> > > > > > described behavior. Uninstalling ASCOM and re installing
> without
> > > > > > the update and the behavior was normal, if you walked away for
> 5 min
> > > > > > your program would become responsive again, but once any
> traffic went
> > > > > > the the telescope the lag would reappear.
> > > > > >
> > > > > > this would suggest that the problem is with a change with the
> ASCOM
> > > > > > platform, my working theory is that the serial port commands
> are
> > > > > >   timing out but that is just speculation to describe the
> problem to
> > > > > > the ASCOM dev's it's like setting the count for
> ReceiveCountedBinary()
> > > > > > too high and having to wait for the timeout for every command
> sent
> > > > > > to the scope and the program using the driver is stuck waiting
> for the
> > > > > > command to complete.
> > > > > >
> > > > > > I still have the USB adapter, and could try to reproduce the
> problem
> > > > > > if a Dev wanted to fix it.
> > > > > >
> > > > > > --- In ASCOM-Talk@yahoogroups.com, ANDREW
> LINDSAY<andrew.lindsay@>  wrote:
> > > > > >>
> > > > > >> Dear group,
> > > > > >> I have installed the Ascom package including the Unified
> Celestron Driver
> > > > > >> 5.0.23 for my Celestron CPC800XLT.
> > > > > >>
> > > > > >> When I try to connect using ASCOM through either TheSkyX or
> MaxImDL, the
> > > > > >> whole computer slows down to a crawl and becomes
> unresponsive.
> > > > > >>
> > > > > >> I have tried other native programs that do not use ASCOM to
> check the comms,
> > > > > >> and in native mode, the communications work flawlessly.
> > > > > >>
> > > > > >> Does anyone have any experience with this, what sort of
> things should I be
> > > > > >> trying to fix it.
> > > > > >>
> > > > > >> Is the Driver 5.0.23 the latest version?
> > > > > >>
> > > > > >> Best regards
> > > > > >>
> > > > > >> Andrew Lindsay
> > > > > >>
> > > > > >
> > > > > >
> > > > > >
> > > > > > ------------------------------------
> > > > > >
> > > > > > 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
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>