Are the applications that are communicating using an ASCOM driver? I suspect not. If so then try some other application that uses ASCOM, such as the freeMessage 1 of 77 , Oct 1, 2008View SourceAre the applications that are communicating using an ASCOM driver? I
If so then try some other application that uses ASCOM, such as the free
Cartes du Ciel. If this works then it demonstrates that the ASCOM driver
isn't the problem.
If it doesn't then try to make the serial connection directly from a
real serial port on the PC to the scope and see if that works with ASCOM.
This is trying to split the problem into smaller problems so you can
find out what is happening.
> Is there anything special I need to know or do when connecting MaximDL
> to my RCX400 via either the RCX400 or LX200GPS/R drivers? I can
> connect via The Sky and AutoStar Suite V5, but I can't get MaximDL or
> MaxPoint to communicate using the exact same setup. I've probably
> skipped an important step, or forgotten to configure something, but I
> can't seem to figure out what it is.
> I'd like to configure MaxPoint to talk to my Scope (preferably via
> RCX400 driver, but via LX200GPS/R driver if that's necessary), and
> then connect MaximDL to MaxPoint. I set the Comm port in the driver,
> but there's no connection at all. I know the assembled USB-Serial
> adapter cable plugged into the DB9-RJ11 serial cable plugged into the
> RCX base RS232 port works since it links TheSky and AutoStar Suite
> just fine. I assume MaximDL and MaxPoint can use the same serial
> cable design?
> Does this sound familiar to anyone? If so, can you give me a shove in
> the right direction? Its annoying to have a $600 software pkg not
> function, especially when I KNOW its gotta me my error.
> Sorry to be asking such PITA questions, but this group can probably
> save me a lot of time scratching my head at the cost of being publicly
> embarrassed by the eventual solution. :)
> For more information see http://ASCOM-Standards.org/.
> To unsubscribe from this group, send an email FROM THE ACCOUNT YOU USED TO SUBSCRIBE(!) to:
> Yahoo! Groups Links
> No virus found in this incoming message.
> Checked by AVG - http://www.avg.com
> Version: 8.0.173 / Virus Database: 270.7.5/1701 - Release Date: 30/09/2008 19:08
... However, many LX200gps and RCX400 users reported severe PC system slow-downs after that change. I vaguely recall that TheSky(X?) and MaximDL were usuallyMessage 77 of 77 , Mar 19View Source--- In ASCOM-Talk@yahoogroups.com, "Chris" <chris.rowland@...> wrote:
>However, many LX200gps and RCX400 users reported severe PC system slow-downs after that change. I vaguely recall that TheSky(X?) and MaximDL were usually part of the mix.
> This is a blast from the past!
> I think these investigations were used to develop the serial interface in platform 6. The serial port driver changed to the .NET one and there is a lot more control available.
Since i didn't have the pieces (TheSky and Maxim), i couldn't duplicate their situations.
Most folks "fixed" it by back-pedaling to Platform 5 (if they could).
It really did appear to be a problem with the Helper's serial port connection. It was not a case of the Autostar being laggy.
> --- In ASCOM-Talk@yahoogroups.com, "rcarlson2020@" <rcarlson2020@> wrote:
> > Did you ever hook it up, I'm trying now 3/18/13 peace
> > --- In ASCOM-Talk@yahoogroups.com, Bob Denny <rdenny@> wrote:
> > >
> > > I'm really swamped with work at present, but I will try look at it as
> > > soon as I can. In order for this to be usable by current drivers,
> > > though, the entire Helper would have to be re-done in .NET. I tried to
> > > make a binary compatible Helper a couple of years ago and completely
> > > fell on my sword. I must have spend a week of days trying. And that was
> > > just working on the interfaces themselves, not the "meat of it". It was
> > > a shell. All I was trying to do was make it so that existing crivers
> > > would call into it without modifications.
> > >
> > > But the bigger question is "What is wrong with the current Helper?" I
> > > skim read the thread(s) and can't get a sense that the real problem is
> > > with the current helper versus some problem with the driver vs the RCX
> > > or something else. But I did /skim/ read the thread. I have a ton of
> > > work on my plate and I just can't get deeply involved in this one right
> > > now... Can someone definitively assert that the current Helper.Serial is
> > > broken somehow?
> > >
> > > -- Bob
> > >
> > > > Ideally we make it binary compatible with the existing serial driver
> > > > class. This would mean that the drivers themselves would not need to be
> > > > recompiled. It would still need installing and registering.
> > > >
> > > > Can somebody (or bodies) help with this? I can contribute my source
> > > > code to this but we need someone who can help with making it binary
> > > > compatible with the serial driver in the helper dll. This may mean
> > > > porting the rest of the helper to .NET.
> > > >
> > > > The installation problems I had were with registering this, I used
> > > > regasm and while I could get this to work myself couldn't get it working
> > > > with code posted to others.
> > > >
> > >