Nicely done. Enjoyed reading it.


Peace,
Rod Mollise
Rod's new book:
_Choosing and Using a New CAT_
Available Now!

<http://skywatch.brainiac.com/astroland>




-----Original Message-----
From: Meade-Uncensored@yahoogroups.com
[mailto:Meade-Uncensored@yahoogroups.com] On Behalf Of tnstargazer
Sent: Friday, November 20, 2009 10:01 PM
To: Meade-Uncensored@yahoogroups.com
Subject: [MeadeUncensored] Meade ETX-LS review, parts one and most recently,
part two posted

I welcome your thoughts on the review I've posted, parts one and tonight,
part two. Part one was a few weeks ago, and is an initial impression. Part
two is focused on optics.

thanks for checking it out.

http://amateurastrotech.wordpress.com/

john




------------------------------------

Yahoo! Groups Links

http://uncle-rods.blogspot.com/


Peace,
Rod Mollise
Rod's new book:
_Choosing and Using a New CAT_
Available Now!

<http://skywatch.brainiac.com/astroland>

Hi there,

I've recently purchased a used Meade 127ED APO on an LXD600 GEM. Since then I've
been hard at work trying to get an auto-guiding setup all ready to go.

So far I've done the following:
- I've made some scope rings so I can piggy-back my Galileoscope as a guide
scope.
- I've built a serial-to-2.5mm stereo wire to control my Canon 350D from the
laptop
- I've build a serial-to-RS232 adapter as per the instructions in the manual
(and several helpful websites).

All I need now is a CCD webcam such as the Logitech Quickcam Pro 4000 and I
should have everything I need to get out in the field and start taking photos.

However, I'm having lots of trouble getting my PC to connect to the mount
through the RS232 connection. I'm using the GuideDog software to connect. At
first I couldn't even select a telescope, but installing the ASCOM platform
solved that problem. I also installed the LX200 Classic drivers. Now I'm getting
a message saying that it can't connect to the mount and to check my connections.

Has anyone else had any success trying to do this? I've checked and re-checked
the wiring in my serial-to-RS232 adaptor and I'm sure I've done it right. Is it
possible the mount's RS232 slot is damaged? Is there any way to diagnose this
short of finding another LXD600?

Also, I'm wondering if I should be using the 'RS232' or the 'CCD' slot on the
mount.

Any help would be much appreciated.

Thanks!
Marc

There are lots of things you can do. I don't have an LXD600, I have a
standard LX200 classic. However RS232 is RS232, that's the socket you
want to use, not the CCD socket.

Check that the speed is correct, the classic uses 9600 8 data No parity,
1 stop. (Often printed as 9600 8N1) check your manual

The most common problem is getting the Tx and Rx lines crossed over.

Find out what commands the LXD600 uses, if it is the same format as the
LX200 then commands such as :GR# will return the RA, :GS# gets the
sidereal time and so on. Simply by using a standard terminal program you
can manually send the commands to the mount and see what the response is.

I normally suggest Teraterm as the terminal program
http://www.ayera.com/teraterm/
Is the site I normally get it from...

You can use Hyperterm, which normally works, however I have found that it
can sometimes have a mind of it's own and refuse to work. I have never
found out why this is, neither could a good many people at work. We
started recommending TeraTerm for this reason, it proved to be bomb
proof and made our support staff much happier.


An even more simple test is to link the tx and rx pins on the end of your
cable, you may need a spare socket to make this easy, then using a
terminal program everything you type will echo back onto the screen.
Break the link and the echo will stop. That will prove the Rs232 cable.
(but it will not detect if the Tx and Rx are the wrong way around)

If you can talk to the mount manually with a terminal program then you
will know that there is nothing wrong with the communications, and you
can have a closer look at the software.


Andy





On Tue, 24 Nov 2009 00:14:10 -0000
"marc_angelillo" <mangelillo@...> wrote:

> Hi there,
>
> I've recently purchased a used Meade 127ED APO on an LXD600 GEM. Since then
I've
> been hard at work trying to get an auto-guiding setup all ready to go.
>
> So far I've done the following:
> - I've made some scope rings so I can piggy-back my Galileoscope as a guide
> scope.
> - I've built a serial-to-2.5mm stereo wire to control my Canon 350D from the
> laptop
> - I've build a serial-to-RS232 adapter as per the instructions in the manual
> (and several helpful websites).
>
> All I need now is a CCD webcam such as the Logitech Quickcam Pro 4000 and I
> should have everything I need to get out in the field and start taking photos.
>
> However, I'm having lots of trouble getting my PC to connect to the mount
> through the RS232 connection. I'm using the GuideDog software to connect. At
> first I couldn't even select a telescope, but installing the ASCOM platform
> solved that problem. I also installed the LX200 Classic drivers. Now I'm
getting
> a message saying that it can't connect to the mount and to check my
connections.
>
> Has anyone else had any success trying to do this? I've checked and re-checked
> the wiring in my serial-to-RS232 adaptor and I'm sure I've done it right. Is
it
> possible the mount's RS232 slot is damaged? Is there any way to diagnose this
> short of finding another LXD600?
>
> Also, I'm wondering if I should be using the 'RS232' or the 'CCD' slot on the
> mount.
>
> Any help would be much appreciated.
>
> Thanks!
> Marc
>

My used 2120 SCT Meade telescope came with the bracket and tube for a 9x60
finder scope.

      Problem a standard diagonal screws on the back of tube. Unfortunately any
standard Meade (IE. MA25) eyepiece will not distance focus. Yes I focused the
Objective by screwing in and out.LOL

It seems like a straight mechanical situation. The obj. works, The tube can't be
Changed and the eye piece works in other telescopes and so does the diagonal.

Is it possible that this is a straight thru eyepiece tube.
How would I Tell.

  Could i get the correct connector

Do you need to focus further out or further in?


Peace,
Rod Mollise
Rod's new book:
_Choosing and Using a New CAT_
Available Now!

<http://skywatch.brainiac.com/astroland>



-----Original Message-----
From: Meade-Uncensored@yahoogroups.com
[mailto:Meade-Uncensored@yahoogroups.com] On Behalf Of bob
Sent: Monday, November 23, 2009 10:27 PM
To: Meade-Uncensored@yahoogroups.com
Subject: [MeadeUncensored] Help please with 9x 60 finder scope

      My used 2120 SCT Meade telescope came with the bracket and tube for a
9x60 finder scope.

      Problem a standard diagonal screws on the back of tube. Unfortunately
any standard Meade (IE. MA25) eyepiece will not distance focus. Yes I
focused the Objective by screwing in and out.LOL

It seems like a straight mechanical situation. The obj. works, The tube
can't be Changed and the eye piece works in other telescopes and so does the
diagonal.

Is it possible that this is a straight thru eyepiece tube.
How would I Tell.

  Could i get the correct connector



------------------------------------

Yahoo! Groups Links

It seems further in. In the past if i remenber correctly I unscrewed the
eyepiece tube. Holding the eyepiece it would focus approx 1/4 inch inside
diagonal.

 


________________________________
From: Rod Mollise <rmollise@...>
To: Meade-Uncensored@yahoogroups.com
Sent: Tue, November 24, 2009 5:43:28 AM
Subject: RE: [MeadeUncensored] Help please with 9x 60 finder scope

 
Do you need to focus further out or further in?

Peace,
Rod Mollise
Rod's new book:
_Choosing and Using a New CAT_
Available Now!

<http://skywatch. brainiac. com/astroland>

-----Original Message-----
From: Meade-Uncensored@ yahoogroups. com
[mailto:Meade-Uncensored@ yahoogroups. com] On Behalf Of bob
Sent: Monday, November 23, 2009 10:27 PM
To: Meade-Uncensored@ yahoogroups. com
Subject: [MeadeUncensored] Help please with 9x 60 finder scope

My used 2120 SCT Meade telescope came with the bracket and tube for a
9x60 finder scope.

Problem a standard diagonal screws on the back of tube. Unfortunately
any standard Meade (IE. MA25) eyepiece will not distance focus. Yes I
focused the Objective by screwing in and out.LOL

It seems like a straight mechanical situation. The obj. works, The tube
can't be Changed and the eye piece works in other telescopes and so does the
diagonal.

Is it possible that this is a straight thru eyepiece tube.
How would I Tell.

Could i get the correct connector

------------ --------- --------- ------

Yahoo! Groups Links







[Non-text portions of this message have been removed]

Bob:

I have a 9x60 Right Angle finder, and it DOES NOT use a standard eye piece. 
What I have is an illuminated reticule EP that threads into the top of
the diagonal and is locked down with a tiny     "grub" screw.  The EP
accepts a separate screw-in watch battery powered LED light source.  Also, the
EP can be focused (ala changing the dioptic on a set of binoculars) on the
reticule grid.

Perhaps a picture or two of what you have will help us find an answer for
you.....

 
Cliff Hipsher
ICC USN (Ret.)
'03 883 XLH
I.A.M.B.K.
Safety is NO accident.
I Ride.  Therefore I am....
 
 




________________________________
From: bob <bobmacny11725@...>
To: Meade-Uncensored@yahoogroups.com
Sent: Mon, November 23, 2009 11:27:20 PM
Subject: [MeadeUncensored] Help please with 9x 60 finder scope

 
My used 2120 SCT Meade telescope came with the bracket and tube for a 9x60
finder scope.

Problem a standard diagonal screws on the back of tube. Unfortunately any
standard Meade (IE. MA25) eyepiece will not distance focus. Yes I focused the
Objective by screwing in and out.LOL

It seems like a straight mechanical situation. The obj. works, The tube can't be
Changed and the eye piece works in other telescopes and so does the diagonal.

Is it possible that this is a straight thru eyepiece tube.
How would I Tell.

Could i get the correct connector







[Non-text portions of this message have been removed]

Is your finder from the 2120 premier or some later model. Could you send a
picture of eyepiece and diagonal.




________________________________
From: Clifton Hipsher <red03sporty@...>
To: Meade-Uncensored@yahoogroups.com
Sent: Tue, November 24, 2009 4:36:10 PM
Subject: Re: [MeadeUncensored] Help please with 9x 60 finder scope

 
Bob:

I have a 9x60 Right Angle finder, and it DOES NOT use a standard eye piece. 
What I have is an illuminated reticule EP that threads into the top of
the diagonal and is locked down with a tiny     "grub" screw.  The EP
accepts a separate screw-in watch battery powered LED light source.  Also, the
EP can be focused (ala changing the dioptic on a set of binoculars) on the
reticule grid.

Perhaps a picture or two of what you have will help us find an answer for
you.....

 
Cliff Hipsher
ICC USN (Ret.)
'03 883 XLH
I.A.M.B.K.
Safety is NO accident.
I Ride.  Therefore I am....
 
 

____________ _________ _________ __
From: bob <bobmacny11725@ yahoo.com>
To: Meade-Uncensored@ yahoogroups. com
Sent: Mon, November 23, 2009 11:27:20 PM
Subject: [MeadeUncensored] Help please with 9x 60 finder scope

 
My used 2120 SCT Meade telescope came with the bracket and tube for a 9x60
finder scope.

Problem a standard diagonal screws on the back of tube. Unfortunately any
standard Meade (IE. MA25) eyepiece will not distance focus. Yes I focused the
Objective by screwing in and out.LOL

It seems like a straight mechanical situation. The obj. works, The tube can't be
Changed and the eye piece works in other telescopes and so does the diagonal.

Is it possible that this is a straight thru eyepiece tube.
How would I Tell.

Could i get the correct connector

[Non-text portions of this message have been removed]







[Non-text portions of this message have been removed]

Bob:

My finder was standard issue for the LX5 2080.  I'll post some pictures in just
a bit....
 
Cliff Hipsher
ICC USN (Ret.)
'03 883 XLH
I.A.M.B.K.
Safety is NO accident.
I Ride.  Therefore I am....
 
 




________________________________
From: bob macc <bobmacny11725@...>
To: Meade-Uncensored@yahoogroups.com
Sent: Wed, November 25, 2009 10:03:04 AM
Subject: Re: [MeadeUncensored] Help please with 9x 60 finder scope

 
Is your finder from the 2120 premier or some later model. Could you send a
picture of eyepiece and diagonal.

____________ _________ _________ __
From: Clifton Hipsher <red03sporty@ yahoo.com>
To: Meade-Uncensored@ yahoogroups. com
Sent: Tue, November 24, 2009 4:36:10 PM
Subject: Re: [MeadeUncensored] Help please with 9x 60 finder scope

 
Bob:

I have a 9x60 Right Angle finder, and it DOES NOT use a standard eye piece. 
What I have is an illuminated reticule EP that threads into the top of
the diagonal and is locked down with a tiny     "grub" screw.  The EP
accepts a separate screw-in watch battery powered LED light source.  Also, the
EP can be focused (ala changing the dioptic on a set of binoculars) on the
reticule grid.

Perhaps a picture or two of what you have will help us find an answer for
you.....

 
Cliff Hipsher
ICC USN (Ret.)
'03 883 XLH
I.A.M.B.K.
Safety is NO accident.
I Ride.  Therefore I am....
 
 

____________ _________ _________ __
From: bob <bobmacny11725@ yahoo.com>
To: Meade-Uncensored@ yahoogroups. com
Sent: Mon, November 23, 2009 11:27:20 PM
Subject: [MeadeUncensored] Help please with 9x 60 finder scope

 
My used 2120 SCT Meade telescope came with the bracket and tube for a 9x60
finder scope.

Problem a standard diagonal screws on the back of tube. Unfortunately any
standard Meade (IE. MA25) eyepiece will not distance focus. Yes I focused the
Objective by screwing in and out.LOL

It seems like a straight mechanical situation. The obj. works, The tube can't be
Changed and the eye piece works in other telescopes and so does the diagonal.

Is it possible that this is a straight thru eyepiece tube.
How would I Tell.

Could i get the correct connector

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]







[Non-text portions of this message have been removed]

Just uploaded pictures.  Check "Cliff's (Oldgazer) Stuff....  I can add more
if needed....
 
Cliff Hipsher
ICC USN (Ret.)
'03 883 XLH
I.A.M.B.K.
Safety is NO accident.
I Ride.  Therefore I am....
 
 




________________________________
From: bob macc <bobmacny11725@...>
To: Meade-Uncensored@yahoogroups.com
Sent: Wed, November 25, 2009 10:03:04 AM
Subject: Re: [MeadeUncensored] Help please with 9x 60 finder scope

 
Is your finder from the 2120 premier or some later model. Could you send a
picture of eyepiece and diagonal.

____________ _________ _________ __
From: Clifton Hipsher <red03sporty@ yahoo.com>
To: Meade-Uncensored@ yahoogroups. com
Sent: Tue, November 24, 2009 4:36:10 PM
Subject: Re: [MeadeUncensored] Help please with 9x 60 finder scope

 
Bob:

I have a 9x60 Right Angle finder, and it DOES NOT use a standard eye piece. 
What I have is an illuminated reticule EP that threads into the top of
the diagonal and is locked down with a tiny     "grub" screw.  The EP
accepts a separate screw-in watch battery powered LED light source.  Also, the
EP can be focused (ala changing the dioptic on a set of binoculars) on the
reticule grid.

Perhaps a picture or two of what you have will help us find an answer for
you.....

 
Cliff Hipsher
ICC USN (Ret.)
'03 883 XLH
I.A.M.B.K.
Safety is NO accident.
I Ride.  Therefore I am....
 
 

____________ _________ _________ __
From: bob <bobmacny11725@ yahoo.com>
To: Meade-Uncensored@ yahoogroups. com
Sent: Mon, November 23, 2009 11:27:20 PM
Subject: [MeadeUncensored] Help please with 9x 60 finder scope

 
My used 2120 SCT Meade telescope came with the bracket and tube for a 9x60
finder scope.

Problem a standard diagonal screws on the back of tube. Unfortunately any
standard Meade (IE. MA25) eyepiece will not distance focus. Yes I focused the
Objective by screwing in and out.LOL

It seems like a straight mechanical situation. The obj. works, The tube can't be
Changed and the eye piece works in other telescopes and so does the diagonal.

Is it possible that this is a straight thru eyepiece tube.
How would I Tell.

Could i get the correct connector

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]







[Non-text portions of this message have been removed]

Looks like the same tube And bracket. My tube my have had added a diagonal for
1.25 inch diagonal. It would make sence that a screw in
eyepiece. Now the  question is where do I get an eyepiece.

--- In Meade-Uncensored@yahoogroups.com, Clifton Hipsher <red03sporty@...>
wrote:
>
> Just uploaded pictures.  Check "Cliff's (Oldgazer) Stuff....  I can add more
if needed....
>  
> Cliff Hipsher
> ICC USN (Ret.)
> '03 883 XLH
> I.A.M.B.K.
> Safety is NO accident.
> I Ride.  Therefore I am....
>  
>  
>
>
>
>
> ________________________________
> From: bob macc <bobmacny11725@...>
> To: Meade-Uncensored@yahoogroups.com
> Sent: Wed, November 25, 2009 10:03:04 AM
> Subject: Re: [MeadeUncensored] Help please with 9x 60 finder scope
>
>  
> Is your finder from the 2120 premier or some later model. Could you send a
picture of eyepiece and diagonal.
>
> ____________ _________ _________ __
> From: Clifton Hipsher <red03sporty@ yahoo.com>
> To: Meade-Uncensored@ yahoogroups. com
> Sent: Tue, November 24, 2009 4:36:10 PM
> Subject: Re: [MeadeUncensored] Help please with 9x 60 finder scope
>
>  
> Bob:
>
> I have a 9x60 Right Angle finder, and it DOES NOT use a standard eye piece. 
What I have is an illuminated reticule EP that threads into the top of
the diagonal and is locked down with a tiny     "grub" screw.  The EP
accepts a separate screw-in watch battery powered LED light source.  Also, the
EP can be focused (ala changing the dioptic on a set of binoculars) on the
reticule grid.
>
> Perhaps a picture or two of what you have will help us find an answer for
you.....
>
>  
> Cliff Hipsher
> ICC USN (Ret.)
> '03 883 XLH
> I.A.M.B.K.
> Safety is NO accident.
> I Ride.  Therefore I am....
>  
>  
>
> ____________ _________ _________ __
> From: bob <bobmacny11725@ yahoo.com>
> To: Meade-Uncensored@ yahoogroups. com
> Sent: Mon, November 23, 2009 11:27:20 PM
> Subject: [MeadeUncensored] Help please with 9x 60 finder scope
>
>  
> My used 2120 SCT Meade telescope came with the bracket and tube for a 9x60
finder scope.
>
> Problem a standard diagonal screws on the back of tube. Unfortunately any
standard Meade (IE. MA25) eyepiece will not distance focus. Yes I focused the
Objective by screwing in and out.LOL
>
> It seems like a straight mechanical situation. The obj. works, The tube can't
be Changed and the eye piece works in other telescopes and so does the diagonal.
>
> Is it possible that this is a straight thru eyepiece tube.
> How would I Tell.
>
> Could i get the correct connector
>
> [Non-text portions of this message have been removed]
>
> [Non-text portions of this message have been removed]
>
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>

Thanks for all the helpful hints Andy.

I just tried connecting with Teraterm, but although it said it was connected, I
couldn't seem to type any commands. Is there some special way to send the
commands to the mount? Or is it due to a connection problem?

I'll try the trick where you connect the Rx and Tx pins next. I'll let you know
how that goes.

Thanks,
Marc

--- In Meade-Uncensored@yahoogroups.com, Andy Eskelson <andyyahoo@...> wrote:
>
> There are lots of things you can do. I don't have an LXD600, I have a
> standard LX200 classic. However RS232 is RS232, that's the socket you
> want to use, not the CCD socket.
>
> Check that the speed is correct, the classic uses 9600 8 data No parity,
> 1 stop. (Often printed as 9600 8N1) check your manual
>
> The most common problem is getting the Tx and Rx lines crossed over.
>
> Find out what commands the LXD600 uses, if it is the same format as the
> LX200 then commands such as :GR# will return the RA, :GS# gets the
> sidereal time and so on. Simply by using a standard terminal program you
> can manually send the commands to the mount and see what the response is.
>
> I normally suggest Teraterm as the terminal program
> http://www.ayera.com/teraterm/
> Is the site I normally get it from...
>
> You can use Hyperterm, which normally works, however I have found that it
> can sometimes have a mind of it's own and refuse to work. I have never
> found out why this is, neither could a good many people at work. We
> started recommending TeraTerm for this reason, it proved to be bomb
> proof and made our support staff much happier.
>
>
> An even more simple test is to link the tx and rx pins on the end of your
> cable, you may need a spare socket to make this easy, then using a
> terminal program everything you type will echo back onto the screen.
> Break the link and the echo will stop. That will prove the Rs232 cable.
> (but it will not detect if the Tx and Rx are the wrong way around)
>
> If you can talk to the mount manually with a terminal program then you
> will know that there is nothing wrong with the communications, and you
> can have a closer look at the software.
>
>
> Andy
>
>
>
>
>
> On Tue, 24 Nov 2009 00:14:10 -0000
> "marc_angelillo" <mangelillo@...> wrote:
>
> > Hi there,
> >
> > I've recently purchased a used Meade 127ED APO on an LXD600 GEM. Since then
I've
> > been hard at work trying to get an auto-guiding setup all ready to go.
> >
> > So far I've done the following:
> > - I've made some scope rings so I can piggy-back my Galileoscope as a guide
> > scope.
> > - I've built a serial-to-2.5mm stereo wire to control my Canon 350D from the
> > laptop
> > - I've build a serial-to-RS232 adapter as per the instructions in the manual
> > (and several helpful websites).
> >
> > All I need now is a CCD webcam such as the Logitech Quickcam Pro 4000 and I
> > should have everything I need to get out in the field and start taking
photos.
> >
> > However, I'm having lots of trouble getting my PC to connect to the mount
> > through the RS232 connection. I'm using the GuideDog software to connect. At
> > first I couldn't even select a telescope, but installing the ASCOM platform
> > solved that problem. I also installed the LX200 Classic drivers. Now I'm
getting
> > a message saying that it can't connect to the mount and to check my
connections.
> >
> > Has anyone else had any success trying to do this? I've checked and
re-checked
> > the wiring in my serial-to-RS232 adaptor and I'm sure I've done it right. Is
it
> > possible the mount's RS232 slot is damaged? Is there any way to diagnose
this
> > short of finding another LXD600?
> >
> > Also, I'm wondering if I should be using the 'RS232' or the 'CCD' slot on
the
> > mount.
> >
> > Any help would be much appreciated.
> >
> > Thanks!
> > Marc
> >
>

Update: Tried linking the tx and rx pins and Teraterm seems to be showing
everything I type in the main window. I guess that means it's wired right. Still
not sure how to send a command like :GR# to the mount though. Am I just supposed
to type it?

Thanks again
Marc

--- In Meade-Uncensored@yahoogroups.com, "marc_angelillo" <mangelillo@...>
wrote:
>
> Thanks for all the helpful hints Andy.
>
> I just tried connecting with Teraterm, but although it said it was connected,
I couldn't seem to type any commands. Is there some special way to send the
commands to the mount? Or is it due to a connection problem?
>
> I'll try the trick where you connect the Rx and Tx pins next. I'll let you
know how that goes.
>
> Thanks,
> Marc
>
> --- In Meade-Uncensored@yahoogroups.com, Andy Eskelson <andyyahoo@> wrote:
> >
> > There are lots of things you can do. I don't have an LXD600, I have a
> > standard LX200 classic. However RS232 is RS232, that's the socket you
> > want to use, not the CCD socket.
> >
> > Check that the speed is correct, the classic uses 9600 8 data No parity,
> > 1 stop. (Often printed as 9600 8N1) check your manual
> >
> > The most common problem is getting the Tx and Rx lines crossed over.
> >
> > Find out what commands the LXD600 uses, if it is the same format as the
> > LX200 then commands such as :GR# will return the RA, :GS# gets the
> > sidereal time and so on. Simply by using a standard terminal program you
> > can manually send the commands to the mount and see what the response is.
> >
> > I normally suggest Teraterm as the terminal program
> > http://www.ayera.com/teraterm/
> > Is the site I normally get it from...
> >
> > You can use Hyperterm, which normally works, however I have found that it
> > can sometimes have a mind of it's own and refuse to work. I have never
> > found out why this is, neither could a good many people at work. We
> > started recommending TeraTerm for this reason, it proved to be bomb
> > proof and made our support staff much happier.
> >
> >
> > An even more simple test is to link the tx and rx pins on the end of your
> > cable, you may need a spare socket to make this easy, then using a
> > terminal program everything you type will echo back onto the screen.
> > Break the link and the echo will stop. That will prove the Rs232 cable.
> > (but it will not detect if the Tx and Rx are the wrong way around)
> >
> > If you can talk to the mount manually with a terminal program then you
> > will know that there is nothing wrong with the communications, and you
> > can have a closer look at the software.
> >
> >
> > Andy
> >
> >
> >
> >
> >
> > On Tue, 24 Nov 2009 00:14:10 -0000
> > "marc_angelillo" <mangelillo@> wrote:
> >
> > > Hi there,
> > >
> > > I've recently purchased a used Meade 127ED APO on an LXD600 GEM. Since
then I've
> > > been hard at work trying to get an auto-guiding setup all ready to go.
> > >
> > > So far I've done the following:
> > > - I've made some scope rings so I can piggy-back my Galileoscope as a
guide
> > > scope.
> > > - I've built a serial-to-2.5mm stereo wire to control my Canon 350D from
the
> > > laptop
> > > - I've build a serial-to-RS232 adapter as per the instructions in the
manual
> > > (and several helpful websites).
> > >
> > > All I need now is a CCD webcam such as the Logitech Quickcam Pro 4000 and
I
> > > should have everything I need to get out in the field and start taking
photos.
> > >
> > > However, I'm having lots of trouble getting my PC to connect to the mount
> > > through the RS232 connection. I'm using the GuideDog software to connect.
At
> > > first I couldn't even select a telescope, but installing the ASCOM
platform
> > > solved that problem. I also installed the LX200 Classic drivers. Now I'm
getting
> > > a message saying that it can't connect to the mount and to check my
connections.
> > >
> > > Has anyone else had any success trying to do this? I've checked and
re-checked
> > > the wiring in my serial-to-RS232 adaptor and I'm sure I've done it right.
Is it
> > > possible the mount's RS232 slot is damaged? Is there any way to diagnose
this
> > > short of finding another LXD600?
> > >
> > > Also, I'm wondering if I should be using the 'RS232' or the 'CCD' slot on
the
> > > mount.
> > >
> > > Any help would be much appreciated.
> > >
> > > Thanks!
> > > Marc
> > >
> >
>

--- In Meade-Uncensored@yahoogroups.com, "marc_angelillo" <mangelillo@...>
wrote:
>
> Update: Tried linking the tx and rx pins and Teraterm seems to
> be showing everything I type in the main window. I guess that
> means it's wired right.

No, that only means that the Tx and Rx wires make it all the way
out and back... you could still have them -swapped- at the far end.

And the other half of the test is for Teraterm to -not- echo
what you type if the Tx and Rx lines are -not- tied together.

> Still not sure how to send a command like :GR# to the mount though.
> Am I just supposed to type it?

Yes.  No "enter" needed (the "#" tells the scope to respond).

good luck
--dick

> Thanks again
> Marc
>
> --- In Meade-Uncensored@yahoogroups.com, "marc_angelillo" <mangelillo@> wrote:
> >
> > Thanks for all the helpful hints Andy.
> >
> > I just tried connecting with Teraterm, but although it said it was
connected, I couldn't seem to type any commands. Is there some special way to
send the commands to the mount? Or is it due to a connection problem?
> >
> > I'll try the trick where you connect the Rx and Tx pins next. I'll let you
know how that goes.
> >
> > Thanks,
> > Marc
> >
> > --- In Meade-Uncensored@yahoogroups.com, Andy Eskelson <andyyahoo@> wrote:
> > >
> > > There are lots of things you can do. I don't have an LXD600, I have a
> > > standard LX200 classic. However RS232 is RS232, that's the socket you
> > > want to use, not the CCD socket.
> > >
> > > Check that the speed is correct, the classic uses 9600 8 data No parity,
> > > 1 stop. (Often printed as 9600 8N1) check your manual
> > >
> > > The most common problem is getting the Tx and Rx lines crossed over.
> > >
> > > Find out what commands the LXD600 uses, if it is the same format as the
> > > LX200 then commands such as :GR# will return the RA, :GS# gets the
> > > sidereal time and so on. Simply by using a standard terminal program you
> > > can manually send the commands to the mount and see what the response is.
> > >
> > > I normally suggest Teraterm as the terminal program
> > > http://www.ayera.com/teraterm/
> > > Is the site I normally get it from...
> > >
> > > You can use Hyperterm, which normally works, however I have found that it
> > > can sometimes have a mind of it's own and refuse to work. I have never
> > > found out why this is, neither could a good many people at work. We
> > > started recommending TeraTerm for this reason, it proved to be bomb
> > > proof and made our support staff much happier.
> > >
> > >
> > > An even more simple test is to link the tx and rx pins on the end of your
> > > cable, you may need a spare socket to make this easy, then using a
> > > terminal program everything you type will echo back onto the screen.
> > > Break the link and the echo will stop. That will prove the Rs232 cable.
> > > (but it will not detect if the Tx and Rx are the wrong way around)
> > >
> > > If you can talk to the mount manually with a terminal program then you
> > > will know that there is nothing wrong with the communications, and you
> > > can have a closer look at the software.
> > >
> > >
> > > Andy
> > >
> > >
> > >
> > >
> > >
> > > On Tue, 24 Nov 2009 00:14:10 -0000
> > > "marc_angelillo" <mangelillo@> wrote:
> > >
> > > > Hi there,
> > > >
> > > > I've recently purchased a used Meade 127ED APO on an LXD600 GEM. Since
then I've
> > > > been hard at work trying to get an auto-guiding setup all ready to go.
> > > >
> > > > So far I've done the following:
> > > > - I've made some scope rings so I can piggy-back my Galileoscope as a
guide
> > > > scope.
> > > > - I've built a serial-to-2.5mm stereo wire to control my Canon 350D from
the
> > > > laptop
> > > > - I've build a serial-to-RS232 adapter as per the instructions in the
manual
> > > > (and several helpful websites).
> > > >
> > > > All I need now is a CCD webcam such as the Logitech Quickcam Pro 4000
and I
> > > > should have everything I need to get out in the field and start taking
photos.
> > > >
> > > > However, I'm having lots of trouble getting my PC to connect to the
mount
> > > > through the RS232 connection. I'm using the GuideDog software to
connect. At
> > > > first I couldn't even select a telescope, but installing the ASCOM
platform
> > > > solved that problem. I also installed the LX200 Classic drivers. Now I'm
getting
> > > > a message saying that it can't connect to the mount and to check my
connections.
> > > >
> > > > Has anyone else had any success trying to do this? I've checked and
re-checked
> > > > the wiring in my serial-to-RS232 adaptor and I'm sure I've done it
right. Is it
> > > > possible the mount's RS232 slot is damaged? Is there any way to diagnose
this
> > > > short of finding another LXD600?
> > > >
> > > > Also, I'm wondering if I should be using the 'RS232' or the 'CCD' slot
on the
> > > > mount.
> > > >
> > > > Any help would be much appreciated.
> > > >
> > > > Thanks!
> > > > Marc
> > > >
> > >
> >
>

----- Original Message ----

> From: marc_angelillo <mangelillo@...>
>
> Update: Tried linking the tx and rx pins and Teraterm seems to be showing
> everything I type in the main window. I guess that means it's wired right.
Still
> not sure how to send a command like :GR# to the mount though. Am I just
supposed
> to type it?

I've never used those "terminal" programs, but I've written some programs (in
BASIC) for the LX200.  The commands (and an example program) are shown at the
end of the manual.  The  #1697 CDS (computer drive system) for the
LXD600/650/700/750 GEMs used essentially the same electronics and computer
system as the LX200 classic, and the manual for CDS the has the same info at the
end of that manual.  When you send a command through the COM port in a BASIC
program, the actual text of the message has a "#" sign at both the start and the
end of every command.  When people talk about these commands, the leading # is
usually not mentioned (my computer skills are very limited, so I don't know
why), but the example program in the manual shows these.

So try adding the # at the start.

See also
<http://groups.yahoo.com/group/meade_refractors/>
There are lots of LXD600-750 owners there.

-John



> --- In Meade-Uncensored@yahoogroups.com, "marc_angelillo"
> wrote:
> >
> > Thanks for all the helpful hints Andy.
> >
> > I just tried connecting with Teraterm, but although it said it was
connected,
> I couldn't seem to type any commands. Is there some special way to send the
> commands to the mount? Or is it due to a connection problem?
> >
> > I'll try the trick where you connect the Rx and Tx pins next. I'll let you
> know how that goes.
> >
> > Thanks,
> > Marc
> >
> > --- In Meade-Uncensored@yahoogroups.com, Andy Eskelson wrote:
> > >
> > > There are lots of things you can do. I don't have an LXD600, I have a
> > > standard LX200 classic. However RS232 is RS232, that's the socket you
> > > want to use, not the CCD socket.
> > >
> > > Check that the speed is correct, the classic uses 9600 8 data No parity,
> > > 1 stop. (Often printed as 9600 8N1) check your manual
> > >
> > > The most common problem is getting the Tx and Rx lines crossed over.
> > >
> > > Find out what commands the LXD600 uses, if it is the same format as the
> > > LX200 then commands such as :GR# will return the RA, :GS# gets the
> > > sidereal time and so on. Simply by using a standard terminal program you
> > > can manually send the commands to the mount and see what the response is.
> > >
> > > I normally suggest Teraterm as the terminal program
> > > http://www.ayera.com/teraterm/
> > > Is the site I normally get it from...
> > >
> > > You can use Hyperterm, which normally works, however I have found that it
> > > can sometimes have a mind of it's own and refuse to work. I have never
> > > found out why this is, neither could a good many people at work. We
> > > started recommending TeraTerm for this reason, it proved to be bomb
> > > proof and made our support staff much happier.
> > >
> > >
> > > An even more simple test is to link the tx and rx pins on the end of your
> > > cable, you may need a spare socket to make this easy, then using a
> > > terminal program everything you type will echo back onto the screen.
> > > Break the link and the echo will stop. That will prove the Rs232 cable.
> > > (but it will not detect if the Tx and Rx are the wrong way around)
> > >
> > > If you can talk to the mount manually with a terminal program then you
> > > will know that there is nothing wrong with the communications, and you
> > > can have a closer look at the software.
> > >
> > >
> > > Andy
> > >
> > >
> > >
> > >
> > >
> > > On Tue, 24 Nov 2009 00:14:10 -0000
> > > "marc_angelillo" wrote:
> > >
> > > > Hi there,
> > > >
> > > > I've recently purchased a used Meade 127ED APO on an LXD600 GEM. Since
> then I've
> > > > been hard at work trying to get an auto-guiding setup all ready to go.
> > > >
> > > > So far I've done the following:
> > > > - I've made some scope rings so I can piggy-back my Galileoscope as a
> guide
> > > > scope.
> > > > - I've built a serial-to-2.5mm stereo wire to control my Canon 350D from
> the
> > > > laptop
> > > > - I've build a serial-to-RS232 adapter as per the instructions in the
> manual
> > > > (and several helpful websites).
> > > >
> > > > All I need now is a CCD webcam such as the Logitech Quickcam Pro 4000
and
> I
> > > > should have everything I need to get out in the field and start taking
> photos.
> > > >
> > > > However, I'm having lots of trouble getting my PC to connect to the
mount
> > > > through the RS232 connection. I'm using the GuideDog software to
connect.
> At
> > > > first I couldn't even select a telescope, but installing the ASCOM
> platform
> > > > solved that problem. I also installed the LX200 Classic drivers. Now I'm
> getting
> > > > a message saying that it can't connect to the mount and to check my
> connections.
> > > >
> > > > Has anyone else had any success trying to do this? I've checked and
> re-checked
> > > > the wiring in my serial-to-RS232 adaptor and I'm sure I've done it
right.
> Is it
> > > > possible the mount's RS232 slot is damaged? Is there any way to diagnose
> this
> > > > short of finding another LXD600?
> > > >
> > > > Also, I'm wondering if I should be using the 'RS232' or the 'CCD' slot
on
> the
> > > > mount.
> > > >
> > > > Any help would be much appreciated.
> > > >
> > > > Thanks!
> > > > Marc
> > > >
> > >
> >
>
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>

In the current autostars, the leading "#" is optional.
What it -does- (in the autostar) is guarantee that the -previous-
command is terminated (and/or any noise on the wires is flushed).

have fun
--dick

--- In Meade-Uncensored@yahoogroups.com, John Mahony <jmmahony@...> wrote:
>
> ----- Original Message ----
>
> > From: marc_angelillo <mangelillo@...>
> >
> > Update: Tried linking the tx and rx pins and Teraterm seems to be showing
> > everything I type in the main window. I guess that means it's wired right.
Still
> > not sure how to send a command like :GR# to the mount though. Am I just
supposed
> > to type it?
>
> I've never used those "terminal" programs, but I've written some programs (in
BASIC) for the LX200.  The commands (and an example program) are shown at the
end of the manual.  The  #1697 CDS (computer drive system) for the
LXD600/650/700/750 GEMs used essentially the same electronics and computer
system as the LX200 classic, and the manual for CDS the has the same info at the
end of that manual.  When you send a command through the COM port in a BASIC
program, the actual text of the message has a "#" sign at both the start and the
end of every command.  When people talk about these commands, the leading # is
usually not mentioned (my computer skills are very limited, so I don't know
why), but the example program in the manual shows these.
>
> So try adding the # at the start.
>
> See also
> <http://groups.yahoo.com/group/meade_refractors/>
> There are lots of LXD600-750 owners there.
>
> -John
>
>
>
> > --- In Meade-Uncensored@yahoogroups.com, "marc_angelillo"
> > wrote:
> > >
> > > Thanks for all the helpful hints Andy.
> > >
> > > I just tried connecting with Teraterm, but although it said it was
connected,
> > I couldn't seem to type any commands. Is there some special way to send the
> > commands to the mount? Or is it due to a connection problem?
> > >
> > > I'll try the trick where you connect the Rx and Tx pins next. I'll let you
> > know how that goes.
> > >
> > > Thanks,
> > > Marc
> > >
> > > --- In Meade-Uncensored@yahoogroups.com, Andy Eskelson wrote:
> > > >
> > > > There are lots of things you can do. I don't have an LXD600, I have a
> > > > standard LX200 classic. However RS232 is RS232, that's the socket you
> > > > want to use, not the CCD socket.
> > > >
> > > > Check that the speed is correct, the classic uses 9600 8 data No parity,
> > > > 1 stop. (Often printed as 9600 8N1) check your manual
> > > >
> > > > The most common problem is getting the Tx and Rx lines crossed over.
> > > >
> > > > Find out what commands the LXD600 uses, if it is the same format as the
> > > > LX200 then commands such as :GR# will return the RA, :GS# gets the
> > > > sidereal time and so on. Simply by using a standard terminal program you
> > > > can manually send the commands to the mount and see what the response
is.
> > > >
> > > > I normally suggest Teraterm as the terminal program
> > > > http://www.ayera.com/teraterm/
> > > > Is the site I normally get it from...
> > > >
> > > > You can use Hyperterm, which normally works, however I have found that
it
> > > > can sometimes have a mind of it's own and refuse to work. I have never
> > > > found out why this is, neither could a good many people at work. We
> > > > started recommending TeraTerm for this reason, it proved to be bomb
> > > > proof and made our support staff much happier.
> > > >
> > > >
> > > > An even more simple test is to link the tx and rx pins on the end of
your
> > > > cable, you may need a spare socket to make this easy, then using a
> > > > terminal program everything you type will echo back onto the screen.
> > > > Break the link and the echo will stop. That will prove the Rs232 cable.
> > > > (but it will not detect if the Tx and Rx are the wrong way around)
> > > >
> > > > If you can talk to the mount manually with a terminal program then you
> > > > will know that there is nothing wrong with the communications, and you
> > > > can have a closer look at the software.
> > > >
> > > >
> > > > Andy
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > On Tue, 24 Nov 2009 00:14:10 -0000
> > > > "marc_angelillo" wrote:
> > > >
> > > > > Hi there,
> > > > >
> > > > > I've recently purchased a used Meade 127ED APO on an LXD600 GEM. Since
> > then I've
> > > > > been hard at work trying to get an auto-guiding setup all ready to go.
> > > > >
> > > > > So far I've done the following:
> > > > > - I've made some scope rings so I can piggy-back my Galileoscope as a
> > guide
> > > > > scope.
> > > > > - I've built a serial-to-2.5mm stereo wire to control my Canon 350D
from
> > the
> > > > > laptop
> > > > > - I've build a serial-to-RS232 adapter as per the instructions in the
> > manual
> > > > > (and several helpful websites).
> > > > >
> > > > > All I need now is a CCD webcam such as the Logitech Quickcam Pro 4000
and
> > I
> > > > > should have everything I need to get out in the field and start taking
> > photos.
> > > > >
> > > > > However, I'm having lots of trouble getting my PC to connect to the
mount
> > > > > through the RS232 connection. I'm using the GuideDog software to
connect.
> > At
> > > > > first I couldn't even select a telescope, but installing the ASCOM
> > platform
> > > > > solved that problem. I also installed the LX200 Classic drivers. Now
I'm
> > getting
> > > > > a message saying that it can't connect to the mount and to check my
> > connections.
> > > > >
> > > > > Has anyone else had any success trying to do this? I've checked and
> > re-checked
> > > > > the wiring in my serial-to-RS232 adaptor and I'm sure I've done it
right.
> > Is it
> > > > > possible the mount's RS232 slot is damaged? Is there any way to
diagnose
> > this
> > > > > short of finding another LXD600?
> > > > >
> > > > > Also, I'm wondering if I should be using the 'RS232' or the 'CCD' slot
on
> > the
> > > > > mount.
> > > > >
> > > > > Any help would be much appreciated.
> > > > >
> > > > > Thanks!
> > > > > Marc
> > > > >
> > > >
> > >
> >
> >
> >
> >
> > ------------------------------------
> >
> > Yahoo! Groups Links
> >
> >
> >
>

Providing you linked the Tx and Rx at the far end of the cable i.e. at
the mount end you have proved out the cable, computer and any RS232
interfaces on the computer side,  and most of the connections. As Dick
says you could still have the Tx and Rx swapped. Also as Dick says you
need to check that the echo stops when you break the link.

If that works, then you can forget about the computer end of the system
for a while, as it all tests out. The problem will be at the mount end,
either a connector miswire, or the mount itself (I hope not)

The commands are all simply typed in nothing special.

I'll do a couple of tests on my LX200 for you to give you an idea as to
what the commands and responses look like. I'll also buzz out the LX200
cable just to double check the the connections for you. The number system
in the LX200 handbook is confusion at best :-) I'm assuming that your
mount uses the same cable.



Andy



On Thu, 26 Nov 2009 04:13:40 -0000
"marc_angelillo" <mangelillo@...> wrote:

> Update: Tried linking the tx and rx pins and Teraterm seems to be showing
everything I type in the main window. I guess that means it's wired right. Still
not sure how to send a command like :GR# to the mount though. Am I just supposed
to type it?
>
> Thanks again
> Marc
>
> --- In Meade-Uncensored@yahoogroups.com, "marc_angelillo" <mangelillo@...>
wrote:
> >
> > Thanks for all the helpful hints Andy.
> >
> > I just tried connecting with Teraterm, but although it said it was
connected, I couldn't seem to type any commands. Is there some special way to
send the commands to the mount? Or is it due to a connection problem?
> >
> > I'll try the trick where you connect the Rx and Tx pins next. I'll let you
know how that goes.
> >
> > Thanks,
> > Marc
> >
> > --- In Meade-Uncensored@yahoogroups.com, Andy Eskelson <andyyahoo@> wrote:
> > >
> > > There are lots of things you can do. I don't have an LXD600, I have a
> > > standard LX200 classic. However RS232 is RS232, that's the socket you
> > > want to use, not the CCD socket.
> > >
> > > Check that the speed is correct, the classic uses 9600 8 data No parity,
> > > 1 stop. (Often printed as 9600 8N1) check your manual
> > >
> > > The most common problem is getting the Tx and Rx lines crossed over.
> > >
> > > Find out what commands the LXD600 uses, if it is the same format as the
> > > LX200 then commands such as :GR# will return the RA, :GS# gets the
> > > sidereal time and so on. Simply by using a standard terminal program you
> > > can manually send the commands to the mount and see what the response is.
> > >
> > > I normally suggest Teraterm as the terminal program
> > > http://www.ayera.com/teraterm/
> > > Is the site I normally get it from...
> > >
> > > You can use Hyperterm, which normally works, however I have found that it
> > > can sometimes have a mind of it's own and refuse to work. I have never
> > > found out why this is, neither could a good many people at work. We
> > > started recommending TeraTerm for this reason, it proved to be bomb
> > > proof and made our support staff much happier.
> > >
> > >
> > > An even more simple test is to link the tx and rx pins on the end of your
> > > cable, you may need a spare socket to make this easy, then using a
> > > terminal program everything you type will echo back onto the screen.
> > > Break the link and the echo will stop. That will prove the Rs232 cable.
> > > (but it will not detect if the Tx and Rx are the wrong way around)
> > >
> > > If you can talk to the mount manually with a terminal program then you
> > > will know that there is nothing wrong with the communications, and you
> > > can have a closer look at the software.
> > >
> > >
> > > Andy
> > >
> > >
> > >
> > >
> > >
> > > On Tue, 24 Nov 2009 00:14:10 -0000
> > > "marc_angelillo" <mangelillo@> wrote:
> > >
> > > > Hi there,
> > > >
> > > > I've recently purchased a used Meade 127ED APO on an LXD600 GEM. Since
then I've
> > > > been hard at work trying to get an auto-guiding setup all ready to go.
> > > >
> > > > So far I've done the following:
> > > > - I've made some scope rings so I can piggy-back my Galileoscope as a
guide
> > > > scope.
> > > > - I've built a serial-to-2.5mm stereo wire to control my Canon 350D from
the
> > > > laptop
> > > > - I've build a serial-to-RS232 adapter as per the instructions in the
manual
> > > > (and several helpful websites).
> > > >
> > > > All I need now is a CCD webcam such as the Logitech Quickcam Pro 4000
and I
> > > > should have everything I need to get out in the field and start taking
photos.
> > > >
> > > > However, I'm having lots of trouble getting my PC to connect to the
mount
> > > > through the RS232 connection. I'm using the GuideDog software to
connect. At
> > > > first I couldn't even select a telescope, but installing the ASCOM
platform
> > > > solved that problem. I also installed the LX200 Classic drivers. Now I'm
getting
> > > > a message saying that it can't connect to the mount and to check my
connections.
> > > >
> > > > Has anyone else had any success trying to do this? I've checked and
re-checked
> > > > the wiring in my serial-to-RS232 adaptor and I'm sure I've done it
right. Is it
> > > > possible the mount's RS232 slot is damaged? Is there any way to diagnose
this
> > > > short of finding another LXD600?
> > > >
> > > > Also, I'm wondering if I should be using the 'RS232' or the 'CCD' slot
on the
> > > > mount.
> > > >
> > > > Any help would be much appreciated.
> > > >
> > > > Thanks!
> > > > Marc
> > > >
> > >
> >
>
>

----- Original Message ----

> From: autostaretx <rseymour@...>
>
> In the current autostars, the leading "#" is optional.

Emphasis on "current autostars".  This is a classic, so it's not only not
current, it's not even autostar.

-John


> What it -does- (in the autostar) is guarantee that the -previous-
> command is terminated (and/or any noise on the wires is flushed).
>
> have fun
> --dick
>
> --- In Meade-Uncensored@yahoogroups.com, John Mahony wrote:
> >
> > ----- Original Message ----
> >
> > > From: marc_angelillo
> > >
> > > Update: Tried linking the tx and rx pins and Teraterm seems to be showing
> > > everything I type in the main window. I guess that means it's wired right.
> Still
> > > not sure how to send a command like :GR# to the mount though. Am I just
> supposed
> > > to type it?
> >
> > I've never used those "terminal" programs, but I've written some programs
(in
> BASIC) for the LX200.  The commands (and an example program) are shown at the
> end of the manual.  The  #1697 CDS (computer drive system) for the
> LXD600/650/700/750 GEMs used essentially the same electronics and computer
> system as the LX200 classic, and the manual for CDS the has the same info at
the
> end of that manual.  When you send a command through the COM port in a BASIC
> program, the actual text of the message has a "#" sign at both the start and
the
> end of every command.  When people talk about these commands, the leading # is
> usually not mentioned (my computer skills are very limited, so I don't know
> why), but the example program in the manual shows these.
> >
> > So try adding the # at the start.
> >
> > See also
> >
> > There are lots of LXD600-750 owners there.
> >
> > -John
> >
> >
> >
> > > --- In Meade-Uncensored@yahoogroups.com, "marc_angelillo"
> > > wrote:
> > > >
> > > > Thanks for all the helpful hints Andy.
> > > >
> > > > I just tried connecting with Teraterm, but although it said it was
> connected,
> > > I couldn't seem to type any commands. Is there some special way to send
the
> > > commands to the mount? Or is it due to a connection problem?
> > > >
> > > > I'll try the trick where you connect the Rx and Tx pins next. I'll let
you
>
> > > know how that goes.
> > > >
> > > > Thanks,
> > > > Marc
> > > >
> > > > --- In Meade-Uncensored@yahoogroups.com, Andy Eskelson wrote:
> > > > >
> > > > > There are lots of things you can do. I don't have an LXD600, I have a
> > > > > standard LX200 classic. However RS232 is RS232, that's the socket you
> > > > > want to use, not the CCD socket.
> > > > >
> > > > > Check that the speed is correct, the classic uses 9600 8 data No
parity,
> > > > > 1 stop. (Often printed as 9600 8N1) check your manual
> > > > >
> > > > > The most common problem is getting the Tx and Rx lines crossed over.
> > > > >
> > > > > Find out what commands the LXD600 uses, if it is the same format as
the
> > > > > LX200 then commands such as :GR# will return the RA, :GS# gets the
> > > > > sidereal time and so on. Simply by using a standard terminal program
you
> > > > > can manually send the commands to the mount and see what the response
> is.
> > > > >
> > > > > I normally suggest Teraterm as the terminal program
> > > > > http://www.ayera.com/teraterm/
> > > > > Is the site I normally get it from...
> > > > >
> > > > > You can use Hyperterm, which normally works, however I have found that
> it
> > > > > can sometimes have a mind of it's own and refuse to work. I have never
> > > > > found out why this is, neither could a good many people at work. We
> > > > > started recommending TeraTerm for this reason, it proved to be bomb
> > > > > proof and made our support staff much happier.
> > > > >
> > > > >
> > > > > An even more simple test is to link the tx and rx pins on the end of
> your
> > > > > cable, you may need a spare socket to make this easy, then using a
> > > > > terminal program everything you type will echo back onto the screen.
> > > > > Break the link and the echo will stop. That will prove the Rs232
cable.
> > > > > (but it will not detect if the Tx and Rx are the wrong way around)
> > > > >
> > > > > If you can talk to the mount manually with a terminal program then you
> > > > > will know that there is nothing wrong with the communications, and you
> > > > > can have a closer look at the software.
> > > > >
> > > > >
> > > > > Andy
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On Tue, 24 Nov 2009 00:14:10 -0000
> > > > > "marc_angelillo" wrote:
> > > > >
> > > > > > Hi there,
> > > > > >
> > > > > > I've recently purchased a used Meade 127ED APO on an LXD600 GEM.
Since
>
> > > then I've
> > > > > > been hard at work trying to get an auto-guiding setup all ready to
go.
> > > > > >
> > > > > > So far I've done the following:
> > > > > > - I've made some scope rings so I can piggy-back my Galileoscope as
a
> > > guide
> > > > > > scope.
> > > > > > - I've built a serial-to-2.5mm stereo wire to control my Canon 350D
> from
> > > the
> > > > > > laptop
> > > > > > - I've build a serial-to-RS232 adapter as per the instructions in
the
> > > manual
> > > > > > (and several helpful websites).
> > > > > >
> > > > > > All I need now is a CCD webcam such as the Logitech Quickcam Pro
4000
> and
> > > I
> > > > > > should have everything I need to get out in the field and start
taking
>
> > > photos.
> > > > > >
> > > > > > However, I'm having lots of trouble getting my PC to connect to the
> mount
> > > > > > through the RS232 connection. I'm using the GuideDog software to
> connect.
> > > At
> > > > > > first I couldn't even select a telescope, but installing the ASCOM
> > > platform
> > > > > > solved that problem. I also installed the LX200 Classic drivers. Now
> I'm
> > > getting
> > > > > > a message saying that it can't connect to the mount and to check my
> > > connections.
> > > > > >
> > > > > > Has anyone else had any success trying to do this? I've checked and
> > > re-checked
> > > > > > the wiring in my serial-to-RS232 adaptor and I'm sure I've done it
> right.
> > > Is it
> > > > > > possible the mount's RS232 slot is damaged? Is there any way to
> diagnose
> > > this
> > > > > > short of finding another LXD600?
> > > > > >
> > > > > > Also, I'm wondering if I should be using the 'RS232' or the 'CCD'
slot
> on
> > > the
> > > > > > mount.
> > > > > >
> > > > > > Any help would be much appreciated.
> > > > > >
> > > > > > Thanks!
> > > > > > Marc
> > > > > >
> > > > >
> > > >
> > >
> > >
> > >
> > >
> > > ------------------------------------
> > >
> > > Yahoo! Groups Links
> > >
> > >
> > >
> >
>
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>

Sorry about the delay, Sods Law kicked in and the scope failed.
It was the well known tantalum cap going short circuit on the power
board. They have now been replaced and all is well.

Here is the info on the serial cable, and also some example commands.
View this post in a fixed width font such as courier to make the ascii
art look OK

I formatted the serial output to make it easier to see what was going on,
the response and commands actually got recorded as one long line with no
line feeds or returns

-------------------------


LX200 serial cable

The serial port on the LX200 mount uses a RJ11 type connector. This has 6
pins, however some cables may come with only 4 pins fitted, the outer two
locations are empty.

Hold the connector with the gold pins uppermost
With the cable toward you

You are looking into the back of the connector where the cable enters.


*************
*           *
*           *
*************
     ****   Locking clip
     ****



***************
* | | | | | | *
* | | | | | | *
* | | | | | | *
* 1 2 3 4 5 6 *
*             *
***************
       CCC
       CCC
       CCC  Cable
       CCC

The pin identified as 2  connects to pin 5 of the 9 way D Type
The pin identified as 4  connects to pin 2 of the 9 way D Type
The pin identified as 5  connects to pin 3 of the 9 way D Type

all other pins are not connected.



Example commands:
Note that I must have an odd terminal setting somewhere
The response to the GD and GA commands show a Beta char rather than a *

I left the local echo on the terminal program so that the commands show
up. The format is :<command>#         <result from mount>     (comment)



:GS#         18:26:05#       (Gets the current sidereal time)
:GL#         14:03:43#       (Gets the local time in 24H format)
:GR#         18:05.1#        (Gets the current Right Ascension)
:GC#         11/26/09#       (Gets the calendar date)
:GD#         -38ß27#         (Gets the current declination)
:GA#         -00ß08#         (Gets the current altitude)






Andy








On Thu, 26 Nov 2009 08:47:16 +0000
Andy Eskelson <andyyahoo@...> wrote:

> Providing you linked the Tx and Rx at the far end of the cable i.e. at
> the mount end you have proved out the cable, computer and any RS232
> interfaces on the computer side,  and most of the connections. As Dick
> says you could still have the Tx and Rx swapped. Also as Dick says you
> need to check that the echo stops when you break the link.
>
> If that works, then you can forget about the computer end of the system
> for a while, as it all tests out. The problem will be at the mount end,
> either a connector miswire, or the mount itself (I hope not)
>
> The commands are all simply typed in nothing special.
>
> I'll do a couple of tests on my LX200 for you to give you an idea as to
> what the commands and responses look like. I'll also buzz out the LX200
> cable just to double check the the connections for you. The number system
> in the LX200 handbook is confusion at best :-) I'm assuming that your
> mount uses the same cable.
>
>
>
> Andy
>
>
>
> On Thu, 26 Nov 2009 04:13:40 -0000
> "marc_angelillo" <mangelillo@...> wrote:
>
> > Update: Tried linking the tx and rx pins and Teraterm seems to be showing
everything I type in the main window. I guess that means it's wired right. Still
not sure how to send a command like :GR# to the mount though. Am I just supposed
to type it?
> >
> > Thanks again
> > Marc
> >
> > --- In Meade-Uncensored@yahoogroups.com, "marc_angelillo" <mangelillo@...>
wrote:
> > >
> > > Thanks for all the helpful hints Andy.
> > >
> > > I just tried connecting with Teraterm, but although it said it was
connected, I couldn't seem to type any commands. Is there some special way to
send the commands to the mount? Or is it due to a connection problem?
> > >
> > > I'll try the trick where you connect the Rx and Tx pins next. I'll let you
know how that goes.
> > >
> > > Thanks,
> > > Marc
> > >
> > > --- In Meade-Uncensored@yahoogroups.com, Andy Eskelson <andyyahoo@> wrote:
> > > >
> > > > There are lots of things you can do. I don't have an LXD600, I have a
> > > > standard LX200 classic. However RS232 is RS232, that's the socket you
> > > > want to use, not the CCD socket.
> > > >
> > > > Check that the speed is correct, the classic uses 9600 8 data No parity,
> > > > 1 stop. (Often printed as 9600 8N1) check your manual
> > > >
> > > > The most common problem is getting the Tx and Rx lines crossed over.
> > > >
> > > > Find out what commands the LXD600 uses, if it is the same format as the
> > > > LX200 then commands such as :GR# will return the RA, :GS# gets the
> > > > sidereal time and so on. Simply by using a standard terminal program you
> > > > can manually send the commands to the mount and see what the response
is.
> > > >
> > > > I normally suggest Teraterm as the terminal program
> > > > http://www.ayera.com/teraterm/
> > > > Is the site I normally get it from...
> > > >
> > > > You can use Hyperterm, which normally works, however I have found that
it
> > > > can sometimes have a mind of it's own and refuse to work. I have never
> > > > found out why this is, neither could a good many people at work. We
> > > > started recommending TeraTerm for this reason, it proved to be bomb
> > > > proof and made our support staff much happier.
> > > >
> > > >
> > > > An even more simple test is to link the tx and rx pins on the end of
your
> > > > cable, you may need a spare socket to make this easy, then using a
> > > > terminal program everything you type will echo back onto the screen.
> > > > Break the link and the echo will stop. That will prove the Rs232 cable.
> > > > (but it will not detect if the Tx and Rx are the wrong way around)
> > > >
> > > > If you can talk to the mount manually with a terminal program then you
> > > > will know that there is nothing wrong with the communications, and you
> > > > can have a closer look at the software.
> > > >
> > > >
> > > > Andy
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > On Tue, 24 Nov 2009 00:14:10 -0000
> > > > "marc_angelillo" <mangelillo@> wrote:
> > > >
> > > > > Hi there,
> > > > >
> > > > > I've recently purchased a used Meade 127ED APO on an LXD600 GEM. Since
then I've
> > > > > been hard at work trying to get an auto-guiding setup all ready to go.
> > > > >
> > > > > So far I've done the following:
> > > > > - I've made some scope rings so I can piggy-back my Galileoscope as a
guide
> > > > > scope.
> > > > > - I've built a serial-to-2.5mm stereo wire to control my Canon 350D
from the
> > > > > laptop
> > > > > - I've build a serial-to-RS232 adapter as per the instructions in the
manual
> > > > > (and several helpful websites).
> > > > >
> > > > > All I need now is a CCD webcam such as the Logitech Quickcam Pro 4000
and I
> > > > > should have everything I need to get out in the field and start taking
photos.
> > > > >
> > > > > However, I'm having lots of trouble getting my PC to connect to the
mount
> > > > > through the RS232 connection. I'm using the GuideDog software to
connect. At
> > > > > first I couldn't even select a telescope, but installing the ASCOM
platform
> > > > > solved that problem. I also installed the LX200 Classic drivers. Now
I'm getting
> > > > > a message saying that it can't connect to the mount and to check my
connections.
> > > > >
> > > > > Has anyone else had any success trying to do this? I've checked and
re-checked
> > > > > the wiring in my serial-to-RS232 adaptor and I'm sure I've done it
right. Is it
> > > > > possible the mount's RS232 slot is damaged? Is there any way to
diagnose this
> > > > > short of finding another LXD600?
> > > > >
> > > > > Also, I'm wondering if I should be using the 'RS232' or the 'CCD' slot
on the
> > > > > mount.
> > > > >
> > > > > Any help would be much appreciated.
> > > > >
> > > > > Thanks!
> > > > > Marc
> > > > >
> > > >
> > >
> >
> >

Ok, based on your last message Andy, it looks like my cable is correctly wired.
Also, I did verify that after I severed the connection between the tx and rx
pins it stopped echoing my commands. Thanks so much for all the work you've gone
through to help me.

So now I'm facing the possibility that the rs232 jack on my mount is faulty :(
My only hope is that it may be because I didn't type in a '#' character before
my commands as shown in the manual. I'll try that when I get home.

If all else fails, I was told on the Meade Refractors group that Shoestring
Astronomy (http://www.shoestringastronomy.com/) sells adapters to connect a
laptop to the ST-4 style CCD port on the mount. So I might have to purchase one
of those..

I'll keep you all posted on my progress.

Thanks for all the help!
Marc

--- In Meade-Uncensored@yahoogroups.com, Andy Eskelson <andyyahoo@...> wrote:
>
> Sorry about the delay, Sods Law kicked in and the scope failed.
> It was the well known tantalum cap going short circuit on the power
> board. They have now been replaced and all is well.
>
> Here is the info on the serial cable, and also some example commands.
> View this post in a fixed width font such as courier to make the ascii
> art look OK
>
> I formatted the serial output to make it easier to see what was going on,
> the response and commands actually got recorded as one long line with no
> line feeds or returns
>
> -------------------------
>
>
> LX200 serial cable
>
> The serial port on the LX200 mount uses a RJ11 type connector. This has 6
> pins, however some cables may come with only 4 pins fitted, the outer two
> locations are empty.
>
> Hold the connector with the gold pins uppermost
> With the cable toward you
>
> You are looking into the back of the connector where the cable enters.
>
>
> *************
> *           *
> *           *
> *************
>     ****   Locking clip
>     ****
>
>
>
> ***************
> * | | | | | | *
> * | | | | | | *
> * | | | | | | *
> * 1 2 3 4 5 6 *
> *             *
> ***************
>       CCC
>       CCC
>       CCC  Cable
>       CCC
>
> The pin identified as 2  connects to pin 5 of the 9 way D Type
> The pin identified as 4  connects to pin 2 of the 9 way D Type
> The pin identified as 5  connects to pin 3 of the 9 way D Type
>
> all other pins are not connected.
>
>
>
> Example commands:
> Note that I must have an odd terminal setting somewhere
> The response to the GD and GA commands show a Beta char rather than a *
>
> I left the local echo on the terminal program so that the commands show
> up. The format is :<command>#         <result from mount>     (comment)
>
>
>
> :GS#         18:26:05#       (Gets the current sidereal time)
> :GL#         14:03:43#       (Gets the local time in 24H format)
> :GR#         18:05.1#        (Gets the current Right Ascension)
> :GC#         11/26/09#       (Gets the calendar date)
> :GD#         -38ß27#         (Gets the current declination)
> :GA#         -00ß08#         (Gets the current altitude)
>
>
>
>
>
>
> Andy
>
>
>
>
>
>
>
>
> On Thu, 26 Nov 2009 08:47:16 +0000
> Andy Eskelson <andyyahoo@...> wrote:
>
> > Providing you linked the Tx and Rx at the far end of the cable i.e. at
> > the mount end you have proved out the cable, computer and any RS232
> > interfaces on the computer side,  and most of the connections. As Dick
> > says you could still have the Tx and Rx swapped. Also as Dick says you
> > need to check that the echo stops when you break the link.
> >
> > If that works, then you can forget about the computer end of the system
> > for a while, as it all tests out. The problem will be at the mount end,
> > either a connector miswire, or the mount itself (I hope not)
> >
> > The commands are all simply typed in nothing special.
> >
> > I'll do a couple of tests on my LX200 for you to give you an idea as to
> > what the commands and responses look like. I'll also buzz out the LX200
> > cable just to double check the the connections for you. The number system
> > in the LX200 handbook is confusion at best :-) I'm assuming that your
> > mount uses the same cable.
> >
> >
> >
> > Andy
> >
> >
> >
> > On Thu, 26 Nov 2009 04:13:40 -0000
> > "marc_angelillo" <mangelillo@...> wrote:
> >
> > > Update: Tried linking the tx and rx pins and Teraterm seems to be showing
everything I type in the main window. I guess that means it's wired right. Still
not sure how to send a command like :GR# to the mount though. Am I just supposed
to type it?
> > >
> > > Thanks again
> > > Marc
> > >
> > > --- In Meade-Uncensored@yahoogroups.com, "marc_angelillo" <mangelillo@>
wrote:
> > > >
> > > > Thanks for all the helpful hints Andy.
> > > >
> > > > I just tried connecting with Teraterm, but although it said it was
connected, I couldn't seem to type any commands. Is there some special way to
send the commands to the mount? Or is it due to a connection problem?
> > > >
> > > > I'll try the trick where you connect the Rx and Tx pins next. I'll let
you know how that goes.
> > > >
> > > > Thanks,
> > > > Marc
> > > >
> > > > --- In Meade-Uncensored@yahoogroups.com, Andy Eskelson <andyyahoo@>
wrote:
> > > > >
> > > > > There are lots of things you can do. I don't have an LXD600, I have a
> > > > > standard LX200 classic. However RS232 is RS232, that's the socket you
> > > > > want to use, not the CCD socket.
> > > > >
> > > > > Check that the speed is correct, the classic uses 9600 8 data No
parity,
> > > > > 1 stop. (Often printed as 9600 8N1) check your manual
> > > > >
> > > > > The most common problem is getting the Tx and Rx lines crossed over.
> > > > >
> > > > > Find out what commands the LXD600 uses, if it is the same format as
the
> > > > > LX200 then commands such as :GR# will return the RA, :GS# gets the
> > > > > sidereal time and so on. Simply by using a standard terminal program
you
> > > > > can manually send the commands to the mount and see what the response
is.
> > > > >
> > > > > I normally suggest Teraterm as the terminal program
> > > > > http://www.ayera.com/teraterm/
> > > > > Is the site I normally get it from...
> > > > >
> > > > > You can use Hyperterm, which normally works, however I have found that
it
> > > > > can sometimes have a mind of it's own and refuse to work. I have never
> > > > > found out why this is, neither could a good many people at work. We
> > > > > started recommending TeraTerm for this reason, it proved to be bomb
> > > > > proof and made our support staff much happier.
> > > > >
> > > > >
> > > > > An even more simple test is to link the tx and rx pins on the end of
your
> > > > > cable, you may need a spare socket to make this easy, then using a
> > > > > terminal program everything you type will echo back onto the screen.
> > > > > Break the link and the echo will stop. That will prove the Rs232
cable.
> > > > > (but it will not detect if the Tx and Rx are the wrong way around)
> > > > >
> > > > > If you can talk to the mount manually with a terminal program then you
> > > > > will know that there is nothing wrong with the communications, and you
> > > > > can have a closer look at the software.
> > > > >
> > > > >
> > > > > Andy
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On Tue, 24 Nov 2009 00:14:10 -0000
> > > > > "marc_angelillo" <mangelillo@> wrote:
> > > > >
> > > > > > Hi there,
> > > > > >
> > > > > > I've recently purchased a used Meade 127ED APO on an LXD600 GEM.
Since then I've
> > > > > > been hard at work trying to get an auto-guiding setup all ready to
go.
> > > > > >
> > > > > > So far I've done the following:
> > > > > > - I've made some scope rings so I can piggy-back my Galileoscope as
a guide
> > > > > > scope.
> > > > > > - I've built a serial-to-2.5mm stereo wire to control my Canon 350D
from the
> > > > > > laptop
> > > > > > - I've build a serial-to-RS232 adapter as per the instructions in
the manual
> > > > > > (and several helpful websites).
> > > > > >
> > > > > > All I need now is a CCD webcam such as the Logitech Quickcam Pro
4000 and I
> > > > > > should have everything I need to get out in the field and start
taking photos.
> > > > > >
> > > > > > However, I'm having lots of trouble getting my PC to connect to the
mount
> > > > > > through the RS232 connection. I'm using the GuideDog software to
connect. At
> > > > > > first I couldn't even select a telescope, but installing the ASCOM
platform
> > > > > > solved that problem. I also installed the LX200 Classic drivers. Now
I'm getting
> > > > > > a message saying that it can't connect to the mount and to check my
connections.
> > > > > >
> > > > > > Has anyone else had any success trying to do this? I've checked and
re-checked
> > > > > > the wiring in my serial-to-RS232 adaptor and I'm sure I've done it
right. Is it
> > > > > > possible the mount's RS232 slot is damaged? Is there any way to
diagnose this
> > > > > > short of finding another LXD600?
> > > > > >
> > > > > > Also, I'm wondering if I should be using the 'RS232' or the 'CCD'
slot on the
> > > > > > mount.
> > > > > >
> > > > > > Any help would be much appreciated.
> > > > > >
> > > > > > Thanks!
> > > > > > Marc
> > > > > >
> > > > >
> > > >
> > >
> > >
>

A simplfied end-to-end pinout diagram is here:
http://rseymour.home.wolfenet.com/LXserial.html

The "ß" in Andy's explanation is the degree symbol (in some fonts),
and may appear as a Beta or the German "Sharp S".

Yes,  i know that the LXD600 is essentially a Classic LX200.
That's why i was very careful to keep saying "autostar".
The programming of the autostars frequently was directly "ported"
from the classic, so how it handles the leading "#" may be germane.
Someone with a classic might try commands -without- a leading "#" to
see if it really matters.  Andy's example seems to indicate that it
doesn't.

have fun
--dick

--- In Meade-Uncensored@yahoogroups.com, Andy Eskelson <andyyahoo@...> wrote:
>
> Sorry about the delay, Sods Law kicked in and the scope failed.
> It was the well known tantalum cap going short circuit on the power
> board. They have now been replaced and all is well.
>
> Here is the info on the serial cable, and also some example commands.
> View this post in a fixed width font such as courier to make the ascii
> art look OK
>
> I formatted the serial output to make it easier to see what was going on,
> the response and commands actually got recorded as one long line with no
> line feeds or returns
>
> -------------------------
>
>
> LX200 serial cable
>
> The serial port on the LX200 mount uses a RJ11 type connector. This has 6
> pins, however some cables may come with only 4 pins fitted, the outer two
> locations are empty.
>
> Hold the connector with the gold pins uppermost
> With the cable toward you
>
> You are looking into the back of the connector where the cable enters.
>
>
> *************
> *           *
> *           *
> *************
>     ****   Locking clip
>     ****
>
>
>
> ***************
> * | | | | | | *
> * | | | | | | *
> * | | | | | | *
> * 1 2 3 4 5 6 *
> *             *
> ***************
>       CCC
>       CCC
>       CCC  Cable
>       CCC
>
> The pin identified as 2  connects to pin 5 of the 9 way D Type
> The pin identified as 4  connects to pin 2 of the 9 way D Type
> The pin identified as 5  connects to pin 3 of the 9 way D Type
>
> all other pins are not connected.
>
>
>
> Example commands:
> Note that I must have an odd terminal setting somewhere
> The response to the GD and GA commands show a Beta char rather than a *
>
> I left the local echo on the terminal program so that the commands show
> up. The format is :<command>#         <result from mount>     (comment)
>
>
>
> :GS#         18:26:05#       (Gets the current sidereal time)
> :GL#         14:03:43#       (Gets the local time in 24H format)
> :GR#         18:05.1#        (Gets the current Right Ascension)
> :GC#         11/26/09#       (Gets the calendar date)
> :GD#         -38ß27#         (Gets the current declination)
> :GA#         -00ß08#         (Gets the current altitude)
>
>
>
>
>
>
> Andy
>
>
>
>
>
>
>
>
> On Thu, 26 Nov 2009 08:47:16 +0000
> Andy Eskelson <andyyahoo@...> wrote:
>
> > Providing you linked the Tx and Rx at the far end of the cable i.e. at
> > the mount end you have proved out the cable, computer and any RS232
> > interfaces on the computer side,  and most of the connections. As Dick
> > says you could still have the Tx and Rx swapped. Also as Dick says you
> > need to check that the echo stops when you break the link.
> >
> > If that works, then you can forget about the computer end of the system
> > for a while, as it all tests out. The problem will be at the mount end,
> > either a connector miswire, or the mount itself (I hope not)
> >
> > The commands are all simply typed in nothing special.
> >
> > I'll do a couple of tests on my LX200 for you to give you an idea as to
> > what the commands and responses look like. I'll also buzz out the LX200
> > cable just to double check the the connections for you. The number system
> > in the LX200 handbook is confusion at best :-) I'm assuming that your
> > mount uses the same cable.
> >
> >
> >
> > Andy
> >
> >
> >
> > On Thu, 26 Nov 2009 04:13:40 -0000
> > "marc_angelillo" <mangelillo@...> wrote:
> >
> > > Update: Tried linking the tx and rx pins and Teraterm seems to be showing
everything I type in the main window. I guess that means it's wired right. Still
not sure how to send a command like :GR# to the mount though. Am I just supposed
to type it?
> > >
> > > Thanks again
> > > Marc
> > >
> > > --- In Meade-Uncensored@yahoogroups.com, "marc_angelillo" <mangelillo@>
wrote:
> > > >
> > > > Thanks for all the helpful hints Andy.
> > > >
> > > > I just tried connecting with Teraterm, but although it said it was
connected, I couldn't seem to type any commands. Is there some special way to
send the commands to the mount? Or is it due to a connection problem?
> > > >
> > > > I'll try the trick where you connect the Rx and Tx pins next. I'll let
you know how that goes.
> > > >
> > > > Thanks,
> > > > Marc
> > > >
> > > > --- In Meade-Uncensored@yahoogroups.com, Andy Eskelson <andyyahoo@>
wrote:
> > > > >
> > > > > There are lots of things you can do. I don't have an LXD600, I have a
> > > > > standard LX200 classic. However RS232 is RS232, that's the socket you
> > > > > want to use, not the CCD socket.
> > > > >
> > > > > Check that the speed is correct, the classic uses 9600 8 data No
parity,
> > > > > 1 stop. (Often printed as 9600 8N1) check your manual
> > > > >
> > > > > The most common problem is getting the Tx and Rx lines crossed over.
> > > > >
> > > > > Find out what commands the LXD600 uses, if it is the same format as
the
> > > > > LX200 then commands such as :GR# will return the RA, :GS# gets the
> > > > > sidereal time and so on. Simply by using a standard terminal program
you
> > > > > can manually send the commands to the mount and see what the response
is.
> > > > >
> > > > > I normally suggest Teraterm as the terminal program
> > > > > http://www.ayera.com/teraterm/
> > > > > Is the site I normally get it from...
> > > > >
> > > > > You can use Hyperterm, which normally works, however I have found that
it
> > > > > can sometimes have a mind of it's own and refuse to work. I have never
> > > > > found out why this is, neither could a good many people at work. We
> > > > > started recommending TeraTerm for this reason, it proved to be bomb
> > > > > proof and made our support staff much happier.
> > > > >
> > > > >
> > > > > An even more simple test is to link the tx and rx pins on the end of
your
> > > > > cable, you may need a spare socket to make this easy, then using a
> > > > > terminal program everything you type will echo back onto the screen.
> > > > > Break the link and the echo will stop. That will prove the Rs232
cable.
> > > > > (but it will not detect if the Tx and Rx are the wrong way around)
> > > > >
> > > > > If you can talk to the mount manually with a terminal program then you
> > > > > will know that there is nothing wrong with the communications, and you
> > > > > can have a closer look at the software.
> > > > >
> > > > >
> > > > > Andy
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On Tue, 24 Nov 2009 00:14:10 -0000
> > > > > "marc_angelillo" <mangelillo@> wrote:
> > > > >
> > > > > > Hi there,
> > > > > >
> > > > > > I've recently purchased a used Meade 127ED APO on an LXD600 GEM.
Since then I've
> > > > > > been hard at work trying to get an auto-guiding setup all ready to
go.
> > > > > >
> > > > > > So far I've done the following:
> > > > > > - I've made some scope rings so I can piggy-back my Galileoscope as
a guide
> > > > > > scope.
> > > > > > - I've built a serial-to-2.5mm stereo wire to control my Canon 350D
from the
> > > > > > laptop
> > > > > > - I've build a serial-to-RS232 adapter as per the instructions in
the manual
> > > > > > (and several helpful websites).
> > > > > >
> > > > > > All I need now is a CCD webcam such as the Logitech Quickcam Pro
4000 and I
> > > > > > should have everything I need to get out in the field and start
taking photos.
> > > > > >
> > > > > > However, I'm having lots of trouble getting my PC to connect to the
mount
> > > > > > through the RS232 connection. I'm using the GuideDog software to
connect. At
> > > > > > first I couldn't even select a telescope, but installing the ASCOM
platform
> > > > > > solved that problem. I also installed the LX200 Classic drivers. Now
I'm getting
> > > > > > a message saying that it can't connect to the mount and to check my
connections.
> > > > > >
> > > > > > Has anyone else had any success trying to do this? I've checked and
re-checked
> > > > > > the wiring in my serial-to-RS232 adaptor and I'm sure I've done it
right. Is it
> > > > > > possible the mount's RS232 slot is damaged? Is there any way to
diagnose this
> > > > > > short of finding another LXD600?
> > > > > >
> > > > > > Also, I'm wondering if I should be using the 'RS232' or the 'CCD'
slot on the
> > > > > > mount.
> > > > > >
> > > > > > Any help would be much appreciated.
> > > > > >
> > > > > > Thanks!
> > > > > > Marc

If it -is- wired like a classic LX200, the rs232 socket has
-two- separate feeds into -two- receiver circuits.

Using Andy's numbering system,
Pin 3 could substitute for pin 4 (data from scope)
and Pin 6 could substitute for pin 5 (data to scope)
Pin 2 would still be "ground"
(and realize that the "tied together" test does not test the
  connection of the -ground- wire at all)
If you choose to try that secondary port, you have to use -both-
pins 3 and 6 for bidirectional communication.

I -don't- know if the primary port is "blessed" in any way,
but i'm pretty sure it can handle the basic commands being discussed.

good luck
--dick

--- In Meade-Uncensored@yahoogroups.com, "marc_angelillo" <mangelillo@...>
wrote:
>
> Ok, based on your last message Andy, it looks like my cable is correctly
wired. Also, I did verify that after I severed the connection between the tx and
rx pins it stopped echoing my commands. Thanks so much for all the work you've
gone through to help me.
>
> So now I'm facing the possibility that the rs232 jack on my mount is faulty :(
My only hope is that it may be because I didn't type in a '#' character before
my commands as shown in the manual. I'll try that when I get home.
>
> If all else fails, I was told on the Meade Refractors group that Shoestring
Astronomy (http://www.shoestringastronomy.com/) sells adapters to connect a
laptop to the ST-4 style CCD port on the mount. So I might have to purchase one
of those..
>
> I'll keep you all posted on my progress.
>
> Thanks for all the help!
> Marc
>
> --- In Meade-Uncensored@yahoogroups.com, Andy Eskelson <andyyahoo@> wrote:
> >
> > Sorry about the delay, Sods Law kicked in and the scope failed.
> > It was the well known tantalum cap going short circuit on the power
> > board. They have now been replaced and all is well.
> >
> > Here is the info on the serial cable, and also some example commands.
> > View this post in a fixed width font such as courier to make the ascii
> > art look OK
> >
> > I formatted the serial output to make it easier to see what was going on,
> > the response and commands actually got recorded as one long line with no
> > line feeds or returns
> >
> > -------------------------
> >
> >
> > LX200 serial cable
> >
> > The serial port on the LX200 mount uses a RJ11 type connector. This has 6
> > pins, however some cables may come with only 4 pins fitted, the outer two
> > locations are empty.
> >
> > Hold the connector with the gold pins uppermost
> > With the cable toward you
> >
> > You are looking into the back of the connector where the cable enters.
> >
> >
> > *************
> > *           *
> > *           *
> > *************
> >     ****   Locking clip
> >     ****
> >
> >
> >
> > ***************
> > * | | | | | | *
> > * | | | | | | *
> > * | | | | | | *
> > * 1 2 3 4 5 6 *
> > *             *
> > ***************
> >       CCC
> >       CCC
> >       CCC  Cable
> >       CCC
> >
> > The pin identified as 2  connects to pin 5 of the 9 way D Type
> > The pin identified as 4  connects to pin 2 of the 9 way D Type
> > The pin identified as 5  connects to pin 3 of the 9 way D Type
> >
> > all other pins are not connected.
> >
> >
> >
> > Example commands:
> > Note that I must have an odd terminal setting somewhere
> > The response to the GD and GA commands show a Beta char rather than a *
> >
> > I left the local echo on the terminal program so that the commands show
> > up. The format is :<command>#         <result from mount>     (comment)
> >
> >
> >
> > :GS#         18:26:05#       (Gets the current sidereal time)
> > :GL#         14:03:43#       (Gets the local time in 24H format)
> > :GR#         18:05.1#        (Gets the current Right Ascension)
> > :GC#         11/26/09#       (Gets the calendar date)
> > :GD#         -38ß27#         (Gets the current declination)
> > :GA#         -00ß08#         (Gets the current altitude)
> >
> >
> >
> >
> >
> >
> > Andy
> >
> >
> >
> >
> >
> >
> >
> >
> > On Thu, 26 Nov 2009 08:47:16 +0000
> > Andy Eskelson <andyyahoo@> wrote:
> >
> > > Providing you linked the Tx and Rx at the far end of the cable i.e. at
> > > the mount end you have proved out the cable, computer and any RS232
> > > interfaces on the computer side,  and most of the connections. As Dick
> > > says you could still have the Tx and Rx swapped. Also as Dick says you
> > > need to check that the echo stops when you break the link.
> > >
> > > If that works, then you can forget about the computer end of the system
> > > for a while, as it all tests out. The problem will be at the mount end,
> > > either a connector miswire, or the mount itself (I hope not)
> > >
> > > The commands are all simply typed in nothing special.
> > >
> > > I'll do a couple of tests on my LX200 for you to give you an idea as to
> > > what the commands and responses look like. I'll also buzz out the LX200
> > > cable just to double check the the connections for you. The number system
> > > in the LX200 handbook is confusion at best :-) I'm assuming that your
> > > mount uses the same cable.
> > >
> > >
> > >
> > > Andy
> > >
> > >
> > >
> > > On Thu, 26 Nov 2009 04:13:40 -0000
> > > "marc_angelillo" <mangelillo@> wrote:
> > >
> > > > Update: Tried linking the tx and rx pins and Teraterm seems to be
showing everything I type in the main window. I guess that means it's wired
right. Still not sure how to send a command like :GR# to the mount though. Am I
just supposed to type it?
> > > >
> > > > Thanks again
> > > > Marc
> > > >
> > > > --- In Meade-Uncensored@yahoogroups.com, "marc_angelillo" <mangelillo@>
wrote:
> > > > >
> > > > > Thanks for all the helpful hints Andy.
> > > > >
> > > > > I just tried connecting with Teraterm, but although it said it was
connected, I couldn't seem to type any commands. Is there some special way to
send the commands to the mount? Or is it due to a connection problem?
> > > > >
> > > > > I'll try the trick where you connect the Rx and Tx pins next. I'll let
you know how that goes.
> > > > >
> > > > > Thanks,
> > > > > Marc
> > > > >
> > > > > --- In Meade-Uncensored@yahoogroups.com, Andy Eskelson <andyyahoo@>
wrote:
> > > > > >
> > > > > > There are lots of things you can do. I don't have an LXD600, I have
a
> > > > > > standard LX200 classic. However RS232 is RS232, that's the socket
you
> > > > > > want to use, not the CCD socket.
> > > > > >
> > > > > > Check that the speed is correct, the classic uses 9600 8 data No
parity,
> > > > > > 1 stop. (Often printed as 9600 8N1) check your manual
> > > > > >
> > > > > > The most common problem is getting the Tx and Rx lines crossed over.
> > > > > >
> > > > > > Find out what commands the LXD600 uses, if it is the same format as
the
> > > > > > LX200 then commands such as :GR# will return the RA, :GS# gets the
> > > > > > sidereal time and so on. Simply by using a standard terminal program
you
> > > > > > can manually send the commands to the mount and see what the
response is.
> > > > > >
> > > > > > I normally suggest Teraterm as the terminal program
> > > > > > http://www.ayera.com/teraterm/
> > > > > > Is the site I normally get it from...
> > > > > >
> > > > > > You can use Hyperterm, which normally works, however I have found
that it
> > > > > > can sometimes have a mind of it's own and refuse to work. I have
never
> > > > > > found out why this is, neither could a good many people at work. We
> > > > > > started recommending TeraTerm for this reason, it proved to be bomb
> > > > > > proof and made our support staff much happier.
> > > > > >
> > > > > >
> > > > > > An even more simple test is to link the tx and rx pins on the end of
your
> > > > > > cable, you may need a spare socket to make this easy, then using a
> > > > > > terminal program everything you type will echo back onto the screen.
> > > > > > Break the link and the echo will stop. That will prove the Rs232
cable.
> > > > > > (but it will not detect if the Tx and Rx are the wrong way around)
> > > > > >
> > > > > > If you can talk to the mount manually with a terminal program then
you
> > > > > > will know that there is nothing wrong with the communications, and
you
> > > > > > can have a closer look at the software.
> > > > > >
> > > > > >
> > > > > > Andy
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Tue, 24 Nov 2009 00:14:10 -0000
> > > > > > "marc_angelillo" <mangelillo@> wrote:
> > > > > >
> > > > > > > Hi there,
> > > > > > >
> > > > > > > I've recently purchased a used Meade 127ED APO on an LXD600 GEM.
Since then I've
> > > > > > > been hard at work trying to get an auto-guiding setup all ready to
go.
> > > > > > >
> > > > > > > So far I've done the following:
> > > > > > > - I've made some scope rings so I can piggy-back my Galileoscope
as a guide
> > > > > > > scope.
> > > > > > > - I've built a serial-to-2.5mm stereo wire to control my Canon
350D from the
> > > > > > > laptop
> > > > > > > - I've build a serial-to-RS232 adapter as per the instructions in
the manual
> > > > > > > (and several helpful websites).
> > > > > > >
> > > > > > > All I need now is a CCD webcam such as the Logitech Quickcam Pro
4000 and I
> > > > > > > should have everything I need to get out in the field and start
taking photos.
> > > > > > >
> > > > > > > However, I'm having lots of trouble getting my PC to connect to
the mount
> > > > > > > through the RS232 connection. I'm using the GuideDog software to
connect. At
> > > > > > > first I couldn't even select a telescope, but installing the ASCOM
platform
> > > > > > > solved that problem. I also installed the LX200 Classic drivers.
Now I'm getting
> > > > > > > a message saying that it can't connect to the mount and to check
my connections.
> > > > > > >
> > > > > > > Has anyone else had any success trying to do this? I've checked
and re-checked
> > > > > > > the wiring in my serial-to-RS232 adaptor and I'm sure I've done it
right. Is it
> > > > > > > possible the mount's RS232 slot is damaged? Is there any way to
diagnose this
> > > > > > > short of finding another LXD600?
> > > > > > >
> > > > > > > Also, I'm wondering if I should be using the 'RS232' or the 'CCD'
slot on the
> > > > > > > mount.
> > > > > > >
> > > > > > > Any help would be much appreciated.
> > > > > > >
> > > > > > > Thanks!
> > > > > > > Marc
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> >
>

The # seems to be a terminator character. I did try sending a load of #
first, then the :GA# command and it worked every time, the scope ignored
the extra #.

It does not hurt to add the extra #, and in some cases it might help  put
the scope into a ready state, perhaps if the previous command got messed
up somehow. When all is working it is not necessary.

Andy


On Thu, 26 Nov 2009 15:50:29 -0000
"autostaretx" <rseymour@...> wrote:

> A simplfied end-to-end pinout diagram is here:
> http://rseymour.home.wolfenet.com/LXserial.html
>
> The "ß" in Andy's explanation is the degree symbol (in some fonts),
> and may appear as a Beta or the German "Sharp S".
>
> Yes,  i know that the LXD600 is essentially a Classic LX200.
> That's why i was very careful to keep saying "autostar".
> The programming of the autostars frequently was directly "ported"
> from the classic, so how it handles the leading "#" may be germane.
> Someone with a classic might try commands -without- a leading "#" to
> see if it really matters.  Andy's example seems to indicate that it
> doesn't.
>
> have fun
> --dick
>
> --- In Meade-Uncensored@yahoogroups.com, Andy Eskelson <andyyahoo@...> wrote:
> >
> > Sorry about the delay, Sods Law kicked in and the scope failed.
> > It was the well known tantalum cap going short circuit on the power
> > board. They have now been replaced and all is well.
> >
> > Here is the info on the serial cable, and also some example commands.
> > View this post in a fixed width font such as courier to make the ascii
> > art look OK
> >
> > I formatted the serial output to make it easier to see what was going on,
> > the response and commands actually got recorded as one long line with no
> > line feeds or returns
> >
> > -------------------------
> >
> >
> > LX200 serial cable
> >
> > The serial port on the LX200 mount uses a RJ11 type connector. This has 6
> > pins, however some cables may come with only 4 pins fitted, the outer two
> > locations are empty.
> >
> > Hold the connector with the gold pins uppermost
> > With the cable toward you
> >
> > You are looking into the back of the connector where the cable enters.
> >
> >
> > *************
> > *           *
> > *           *
> > *************
> >     ****   Locking clip
> >     ****
> >
> >
> >
> > ***************
> > * | | | | | | *
> > * | | | | | | *
> > * | | | | | | *
> > * 1 2 3 4 5 6 *
> > *             *
> > ***************
> >       CCC
> >       CCC
> >       CCC  Cable
> >       CCC
> >
> > The pin identified as 2  connects to pin 5 of the 9 way D Type
> > The pin identified as 4  connects to pin 2 of the 9 way D Type
> > The pin identified as 5  connects to pin 3 of the 9 way D Type
> >
> > all other pins are not connected.
> >
> >
> >
> > Example commands:
> > Note that I must have an odd terminal setting somewhere
> > The response to the GD and GA commands show a Beta char rather than a *
> >
> > I left the local echo on the terminal program so that the commands show
> > up. The format is :<command>#         <result from mount>     (comment)
> >
> >
> >
> > :GS#         18:26:05#       (Gets the current sidereal time)
> > :GL#         14:03:43#       (Gets the local time in 24H format)
> > :GR#         18:05.1#        (Gets the current Right Ascension)
> > :GC#         11/26/09#       (Gets the calendar date)
> > :GD#         -38ß27#         (Gets the current declination)
> > :GA#         -00ß08#         (Gets the current altitude)
> >
> >
> >
> >
> >
> >
> > Andy
> >
> >
> >
> >
> >
> >
> >
> >
> > On Thu, 26 Nov 2009 08:47:16 +0000
> > Andy Eskelson <andyyahoo@...> wrote:
> >
> > > Providing you linked the Tx and Rx at the far end of the cable i.e. at
> > > the mount end you have proved out the cable, computer and any RS232
> > > interfaces on the computer side,  and most of the connections. As Dick
> > > says you could still have the Tx and Rx swapped. Also as Dick says you
> > > need to check that the echo stops when you break the link.
> > >
> > > If that works, then you can forget about the computer end of the system
> > > for a while, as it all tests out. The problem will be at the mount end,
> > > either a connector miswire, or the mount itself (I hope not)
> > >
> > > The commands are all simply typed in nothing special.
> > >
> > > I'll do a couple of tests on my LX200 for you to give you an idea as to
> > > what the commands and responses look like. I'll also buzz out the LX200
> > > cable just to double check the the connections for you. The number system
> > > in the LX200 handbook is confusion at best :-) I'm assuming that your
> > > mount uses the same cable.
> > >
> > >
> > >
> > > Andy
> > >
> > >
> > >
> > > On Thu, 26 Nov 2009 04:13:40 -0000
> > > "marc_angelillo" <mangelillo@...> wrote:
> > >
> > > > Update: Tried linking the tx and rx pins and Teraterm seems to be
showing everything I type in the main window. I guess that means it's wired
right. Still not sure how to send a command like :GR# to the mount though. Am I
just supposed to type it?
> > > >
> > > > Thanks again
> > > > Marc
> > > >
> > > > --- In Meade-Uncensored@yahoogroups.com, "marc_angelillo" <mangelillo@>
wrote:
> > > > >
> > > > > Thanks for all the helpful hints Andy.
> > > > >
> > > > > I just tried connecting with Teraterm, but although it said it was
connected, I couldn't seem to type any commands. Is there some special way to
send the commands to the mount? Or is it due to a connection problem?
> > > > >
> > > > > I'll try the trick where you connect the Rx and Tx pins next. I'll let
you know how that goes.
> > > > >
> > > > > Thanks,
> > > > > Marc
> > > > >
> > > > > --- In Meade-Uncensored@yahoogroups.com, Andy Eskelson <andyyahoo@>
wrote:
> > > > > >
> > > > > > There are lots of things you can do. I don't have an LXD600, I have
a
> > > > > > standard LX200 classic. However RS232 is RS232, that's the socket
you
> > > > > > want to use, not the CCD socket.
> > > > > >
> > > > > > Check that the speed is correct, the classic uses 9600 8 data No
parity,
> > > > > > 1 stop. (Often printed as 9600 8N1) check your manual
> > > > > >
> > > > > > The most common problem is getting the Tx and Rx lines crossed over.
> > > > > >
> > > > > > Find out what commands the LXD600 uses, if it is the same format as
the
> > > > > > LX200 then commands such as :GR# will return the RA, :GS# gets the
> > > > > > sidereal time and so on. Simply by using a standard terminal program
you
> > > > > > can manually send the commands to the mount and see what the
response is.
> > > > > >
> > > > > > I normally suggest Teraterm as the terminal program
> > > > > > http://www.ayera.com/teraterm/
> > > > > > Is the site I normally get it from...
> > > > > >
> > > > > > You can use Hyperterm, which normally works, however I have found
that it
> > > > > > can sometimes have a mind of it's own and refuse to work. I have
never
> > > > > > found out why this is, neither could a good many people at work. We
> > > > > > started recommending TeraTerm for this reason, it proved to be bomb
> > > > > > proof and made our support staff much happier.
> > > > > >
> > > > > >
> > > > > > An even more simple test is to link the tx and rx pins on the end of
your
> > > > > > cable, you may need a spare socket to make this easy, then using a
> > > > > > terminal program everything you type will echo back onto the screen.
> > > > > > Break the link and the echo will stop. That will prove the Rs232
cable.
> > > > > > (but it will not detect if the Tx and Rx are the wrong way around)
> > > > > >
> > > > > > If you can talk to the mount manually with a terminal program then
you
> > > > > > will know that there is nothing wrong with the communications, and
you
> > > > > > can have a closer look at the software.
> > > > > >
> > > > > >
> > > > > > Andy
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Tue, 24 Nov 2009 00:14:10 -0000
> > > > > > "marc_angelillo" <mangelillo@> wrote:
> > > > > >
> > > > > > > Hi there,
> > > > > > >
> > > > > > > I've recently purchased a used Meade 127ED APO on an LXD600 GEM.
Since then I've
> > > > > > > been hard at work trying to get an auto-guiding setup all ready to
go.
> > > > > > >
> > > > > > > So far I've done the following:
> > > > > > > - I've made some scope rings so I can piggy-back my Galileoscope
as a guide
> > > > > > > scope.
> > > > > > > - I've built a serial-to-2.5mm stereo wire to control my Canon
350D from the
> > > > > > > laptop
> > > > > > > - I've build a serial-to-RS232 adapter as per the instructions in
the manual
> > > > > > > (and several helpful websites).
> > > > > > >
> > > > > > > All I need now is a CCD webcam such as the Logitech Quickcam Pro
4000 and I
> > > > > > > should have everything I need to get out in the field and start
taking photos.
> > > > > > >
> > > > > > > However, I'm having lots of trouble getting my PC to connect to
the mount
> > > > > > > through the RS232 connection. I'm using the GuideDog software to
connect. At
> > > > > > > first I couldn't even select a telescope, but installing the ASCOM
platform
> > > > > > > solved that problem. I also installed the LX200 Classic drivers.
Now I'm getting
> > > > > > > a message saying that it can't connect to the mount and to check
my connections.
> > > > > > >
> > > > > > > Has anyone else had any success trying to do this? I've checked
and re-checked
> > > > > > > the wiring in my serial-to-RS232 adaptor and I'm sure I've done it
right. Is it
> > > > > > > possible the mount's RS232 slot is damaged? Is there any way to
diagnose this
> > > > > > > short of finding another LXD600?
> > > > > > >
> > > > > > > Also, I'm wondering if I should be using the 'RS232' or the 'CCD'
slot on the
> > > > > > > mount.
> > > > > > >
> > > > > > > Any help would be much appreciated.
> > > > > > >
> > > > > > > Thanks!
> > > > > > > Marc
>
>

Thinking about my little problem of the caps failing, is there any
indication that the mount is doing anything at all? are the motors ticking
away and so on? I'm just wondering it the problem is something as silly
as no power getting to the electronics


Andy


On Thu, 26 Nov 2009 15:40:07 -0000
"marc_angelillo" <mangelillo@...> wrote:

> Ok, based on your last message Andy, it looks like my cable is correctly
wired. Also, I did verify that after I severed the connection between the tx and
rx pins it stopped echoing my commands. Thanks so much for all the work you've
gone through to help me.
>
> So now I'm facing the possibility that the rs232 jack on my mount is faulty :(
My only hope is that it may be because I didn't type in a '#' character before
my commands as shown in the manual. I'll try that when I get home.
>
> If all else fails, I was told on the Meade Refractors group that Shoestring
Astronomy (http://www.shoestringastronomy.com/) sells adapters to connect a
laptop to the ST-4 style CCD port on the mount. So I might have to purchase one
of those..
>
> I'll keep you all posted on my progress.
>
> Thanks for all the help!
> Marc
>
> --- In Meade-Uncensored@yahoogroups.com, Andy Eskelson <andyyahoo@...> wrote:
> >
> > Sorry about the delay, Sods Law kicked in and the scope failed.
> > It was the well known tantalum cap going short circuit on the power
> > board. They have now been replaced and all is well.
> >
> > Here is the info on the serial cable, and also some example commands.
> > View this post in a fixed width font such as courier to make the ascii
> > art look OK
> >
> > I formatted the serial output to make it easier to see what was going on,
> > the response and commands actually got recorded as one long line with no
> > line feeds or returns
> >
> > -------------------------
> >
> >
> > LX200 serial cable
> >
> > The serial port on the LX200 mount uses a RJ11 type connector. This has 6
> > pins, however some cables may come with only 4 pins fitted, the outer two
> > locations are empty.
> >
> > Hold the connector with the gold pins uppermost
> > With the cable toward you
> >
> > You are looking into the back of the connector where the cable enters.
> >
> >
> > *************
> > *           *
> > *           *
> > *************
> >     ****   Locking clip
> >     ****
> >
> >
> >
> > ***************
> > * | | | | | | *
> > * | | | | | | *
> > * | | | | | | *
> > * 1 2 3 4 5 6 *
> > *             *
> > ***************
> >       CCC
> >       CCC
> >       CCC  Cable
> >       CCC
> >
> > The pin identified as 2  connects to pin 5 of the 9 way D Type
> > The pin identified as 4  connects to pin 2 of the 9 way D Type
> > The pin identified as 5  connects to pin 3 of the 9 way D Type
> >
> > all other pins are not connected.
> >
> >
> >
> > Example commands:
> > Note that I must have an odd terminal setting somewhere
> > The response to the GD and GA commands show a Beta char rather than a *
> >
> > I left the local echo on the terminal program so that the commands show
> > up. The format is :<command>#         <result from mount>     (comment)
> >
> >
> >
> > :GS#         18:26:05#       (Gets the current sidereal time)
> > :GL#         14:03:43#       (Gets the local time in 24H format)
> > :GR#         18:05.1#        (Gets the current Right Ascension)
> > :GC#         11/26/09#       (Gets the calendar date)
> > :GD#         -38ß27#         (Gets the current declination)
> > :GA#         -00ß08#         (Gets the current altitude)
> >
> >
> >
> >
> >
> >
> > Andy
> >
> >
> >
> >
> >
> >
> >
> >
> > On Thu, 26 Nov 2009 08:47:16 +0000
> > Andy Eskelson <andyyahoo@...> wrote:
> >
> > > Providing you linked the Tx and Rx at the far end of the cable i.e. at
> > > the mount end you have proved out the cable, computer and any RS232
> > > interfaces on the computer side,  and most of the connections. As Dick
> > > says you could still have the Tx and Rx swapped. Also as Dick says you
> > > need to check that the echo stops when you break the link.
> > >
> > > If that works, then you can forget about the computer end of the system
> > > for a while, as it all tests out. The problem will be at the mount end,
> > > either a connector miswire, or the mount itself (I hope not)
> > >
> > > The commands are all simply typed in nothing special.
> > >
> > > I'll do a couple of tests on my LX200 for you to give you an idea as to
> > > what the commands and responses look like. I'll also buzz out the LX200
> > > cable just to double check the the connections for you. The number system
> > > in the LX200 handbook is confusion at best :-) I'm assuming that your
> > > mount uses the same cable.
> > >
> > >
> > >
> > > Andy
> > >
> > >
> > >
> > > On Thu, 26 Nov 2009 04:13:40 -0000
> > > "marc_angelillo" <mangelillo@...> wrote:
> > >
> > > > Update: Tried linking the tx and rx pins and Teraterm seems to be
showing everything I type in the main window. I guess that means it's wired
right. Still not sure how to send a command like :GR# to the mount though. Am I
just supposed to type it?
> > > >
> > > > Thanks again
> > > > Marc
> > > >
> > > > --- In Meade-Uncensored@yahoogroups.com, "marc_angelillo" <mangelillo@>
wrote:
> > > > >
> > > > > Thanks for all the helpful hints Andy.
> > > > >
> > > > > I just tried connecting with Teraterm, but although it said it was
connected, I couldn't seem to type any commands. Is there some special way to
send the commands to the mount? Or is it due to a connection problem?
> > > > >
> > > > > I'll try the trick where you connect the Rx and Tx pins next. I'll let
you know how that goes.
> > > > >
> > > > > Thanks,
> > > > > Marc
> > > > >
> > > > > --- In Meade-Uncensored@yahoogroups.com, Andy Eskelson <andyyahoo@>
wrote:
> > > > > >
> > > > > > There are lots of things you can do. I don't have an LXD600, I have
a
> > > > > > standard LX200 classic. However RS232 is RS232, that's the socket
you
> > > > > > want to use, not the CCD socket.
> > > > > >
> > > > > > Check that the speed is correct, the classic uses 9600 8 data No
parity,
> > > > > > 1 stop. (Often printed as 9600 8N1) check your manual
> > > > > >
> > > > > > The most common problem is getting the Tx and Rx lines crossed over.
> > > > > >
> > > > > > Find out what commands the LXD600 uses, if it is the same format as
the
> > > > > > LX200 then commands such as :GR# will return the RA, :GS# gets the
> > > > > > sidereal time and so on. Simply by using a standard terminal program
you
> > > > > > can manually send the commands to the mount and see what the
response is.
> > > > > >
> > > > > > I normally suggest Teraterm as the terminal program
> > > > > > http://www.ayera.com/teraterm/
> > > > > > Is the site I normally get it from...
> > > > > >
> > > > > > You can use Hyperterm, which normally works, however I have found
that it
> > > > > > can sometimes have a mind of it's own and refuse to work. I have
never
> > > > > > found out why this is, neither could a good many people at work. We
> > > > > > started recommending TeraTerm for this reason, it proved to be bomb
> > > > > > proof and made our support staff much happier.
> > > > > >
> > > > > >
> > > > > > An even more simple test is to link the tx and rx pins on the end of
your
> > > > > > cable, you may need a spare socket to make this easy, then using a
> > > > > > terminal program everything you type will echo back onto the screen.
> > > > > > Break the link and the echo will stop. That will prove the Rs232
cable.
> > > > > > (but it will not detect if the Tx and Rx are the wrong way around)
> > > > > >
> > > > > > If you can talk to the mount manually with a terminal program then
you
> > > > > > will know that there is nothing wrong with the communications, and
you
> > > > > > can have a closer look at the software.
> > > > > >
> > > > > >
> > > > > > Andy
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Tue, 24 Nov 2009 00:14:10 -0000
> > > > > > "marc_angelillo" <mangelillo@> wrote:
> > > > > >
> > > > > > > Hi there,
> > > > > > >
> > > > > > > I've recently purchased a used Meade 127ED APO on an LXD600 GEM.
Since then I've
> > > > > > > been hard at work trying to get an auto-guiding setup all ready to
go.
> > > > > > >
> > > > > > > So far I've done the following:
> > > > > > > - I've made some scope rings so I can piggy-back my Galileoscope
as a guide
> > > > > > > scope.
> > > > > > > - I've built a serial-to-2.5mm stereo wire to control my Canon
350D from the
> > > > > > > laptop
> > > > > > > - I've build a serial-to-RS232 adapter as per the instructions in
the manual
> > > > > > > (and several helpful websites).
> > > > > > >
> > > > > > > All I need now is a CCD webcam such as the Logitech Quickcam Pro
4000 and I
> > > > > > > should have everything I need to get out in the field and start
taking photos.
> > > > > > >
> > > > > > > However, I'm having lots of trouble getting my PC to connect to
the mount
> > > > > > > through the RS232 connection. I'm using the GuideDog software to
connect. At
> > > > > > > first I couldn't even select a telescope, but installing the ASCOM
platform
> > > > > > > solved that problem. I also installed the LX200 Classic drivers.
Now I'm getting
> > > > > > > a message saying that it can't connect to the mount and to check
my connections.
> > > > > > >
> > > > > > > Has anyone else had any success trying to do this? I've checked
and re-checked
> > > > > > > the wiring in my serial-to-RS232 adaptor and I'm sure I've done it
right. Is it
> > > > > > > possible the mount's RS232 slot is damaged? Is there any way to
diagnose this
> > > > > > > short of finding another LXD600?
> > > > > > >
> > > > > > > Also, I'm wondering if I should be using the 'RS232' or the 'CCD'
slot on the
> > > > > > > mount.
> > > > > > >
> > > > > > > Any help would be much appreciated.
> > > > > > >
> > > > > > > Thanks!
> > > > > > > Marc
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> >
>
>

Andy, yes there is definitely power getting to the electronics since the motors
are turning and the LED amp lights are on.

Dick, good point about the alternative pins. I'll definitely give that a try
before purchasing a CCD adapter from Shoestring Astronomy. Also, thanks for that
extra pin diagram. It's made me 100% certain that I've wired everything
correctly.

Marc

--- In Meade-Uncensored@yahoogroups.com, Andy Eskelson <andyyahoo@...> wrote:
>
> Thinking about my little problem of the caps failing, is there any
> indication that the mount is doing anything at all? are the motors ticking
> away and so on? I'm just wondering it the problem is something as silly
> as no power getting to the electronics
>
>
> Andy
>
>
> On Thu, 26 Nov 2009 15:40:07 -0000
> "marc_angelillo" <mangelillo@...> wrote:
>
> > Ok, based on your last message Andy, it looks like my cable is correctly
wired. Also, I did verify that after I severed the connection between the tx and
rx pins it stopped echoing my commands. Thanks so much for all the work you've
gone through to help me.
> >
> > So now I'm facing the possibility that the rs232 jack on my mount is faulty
:( My only hope is that it may be because I didn't type in a '#' character
before my commands as shown in the manual. I'll try that when I get home.
> >
> > If all else fails, I was told on the Meade Refractors group that Shoestring
Astronomy (http://www.shoestringastronomy.com/) sells adapters to connect a
laptop to the ST-4 style CCD port on the mount. So I might have to purchase one
of those..
> >
> > I'll keep you all posted on my progress.
> >
> > Thanks for all the help!
> > Marc
> >
> > --- In Meade-Uncensored@yahoogroups.com, Andy Eskelson <andyyahoo@> wrote:
> > >
> > > Sorry about the delay, Sods Law kicked in and the scope failed.
> > > It was the well known tantalum cap going short circuit on the power
> > > board. They have now been replaced and all is well.
> > >
> > > Here is the info on the serial cable, and also some example commands.
> > > View this post in a fixed width font such as courier to make the ascii
> > > art look OK
> > >
> > > I formatted the serial output to make it easier to see what was going on,
> > > the response and commands actually got recorded as one long line with no
> > > line feeds or returns
> > >
> > > -------------------------
> > >
> > >
> > > LX200 serial cable
> > >
> > > The serial port on the LX200 mount uses a RJ11 type connector. This has 6
> > > pins, however some cables may come with only 4 pins fitted, the outer two
> > > locations are empty.
> > >
> > > Hold the connector with the gold pins uppermost
> > > With the cable toward you
> > >
> > > You are looking into the back of the connector where the cable enters.
> > >
> > >
> > > *************
> > > *           *
> > > *           *
> > > *************
> > >     ****   Locking clip
> > >     ****
> > >
> > >
> > >
> > > ***************
> > > * | | | | | | *
> > > * | | | | | | *
> > > * | | | | | | *
> > > * 1 2 3 4 5 6 *
> > > *             *
> > > ***************
> > >       CCC
> > >       CCC
> > >       CCC  Cable
> > >       CCC
> > >
> > > The pin identified as 2  connects to pin 5 of the 9 way D Type
> > > The pin identified as 4  connects to pin 2 of the 9 way D Type
> > > The pin identified as 5  connects to pin 3 of the 9 way D Type
> > >
> > > all other pins are not connected.
> > >
> > >
> > >
> > > Example commands:
> > > Note that I must have an odd terminal setting somewhere
> > > The response to the GD and GA commands show a Beta char rather than a *
> > >
> > > I left the local echo on the terminal program so that the commands show
> > > up. The format is :<command>#         <result from mount>     (comment)
> > >
> > >
> > >
> > > :GS#         18:26:05#       (Gets the current sidereal time)
> > > :GL#         14:03:43#       (Gets the local time in 24H format)
> > > :GR#         18:05.1#        (Gets the current Right Ascension)
> > > :GC#         11/26/09#       (Gets the calendar date)
> > > :GD#         -38ß27#         (Gets the current declination)
> > > :GA#         -00ß08#         (Gets the current altitude)
> > >
> > >
> > >
> > >
> > >
> > >
> > > Andy
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > On Thu, 26 Nov 2009 08:47:16 +0000
> > > Andy Eskelson <andyyahoo@> wrote:
> > >
> > > > Providing you linked the Tx and Rx at the far end of the cable i.e. at
> > > > the mount end you have proved out the cable, computer and any RS232
> > > > interfaces on the computer side,  and most of the connections. As Dick
> > > > says you could still have the Tx and Rx swapped. Also as Dick says you
> > > > need to check that the echo stops when you break the link.
> > > >
> > > > If that works, then you can forget about the computer end of the system
> > > > for a while, as it all tests out. The problem will be at the mount end,
> > > > either a connector miswire, or the mount itself (I hope not)
> > > >
> > > > The commands are all simply typed in nothing special.
> > > >
> > > > I'll do a couple of tests on my LX200 for you to give you an idea as to
> > > > what the commands and responses look like. I'll also buzz out the LX200
> > > > cable just to double check the the connections for you. The number
system
> > > > in the LX200 handbook is confusion at best :-) I'm assuming that your
> > > > mount uses the same cable.
> > > >
> > > >
> > > >
> > > > Andy
> > > >
> > > >
> > > >
> > > > On Thu, 26 Nov 2009 04:13:40 -0000
> > > > "marc_angelillo" <mangelillo@> wrote:
> > > >
> > > > > Update: Tried linking the tx and rx pins and Teraterm seems to be
showing everything I type in the main window. I guess that means it's wired
right. Still not sure how to send a command like :GR# to the mount though. Am I
just supposed to type it?
> > > > >
> > > > > Thanks again
> > > > > Marc
> > > > >
> > > > > --- In Meade-Uncensored@yahoogroups.com, "marc_angelillo"
<mangelillo@> wrote:
> > > > > >
> > > > > > Thanks for all the helpful hints Andy.
> > > > > >
> > > > > > I just tried connecting with Teraterm, but although it said it was
connected, I couldn't seem to type any commands. Is there some special way to
send the commands to the mount? Or is it due to a connection problem?
> > > > > >
> > > > > > I'll try the trick where you connect the Rx and Tx pins next. I'll
let you know how that goes.
> > > > > >
> > > > > > Thanks,
> > > > > > Marc
> > > > > >
> > > > > > --- In Meade-Uncensored@yahoogroups.com, Andy Eskelson <andyyahoo@>
wrote:
> > > > > > >
> > > > > > > There are lots of things you can do. I don't have an LXD600, I
have a
> > > > > > > standard LX200 classic. However RS232 is RS232, that's the socket
you
> > > > > > > want to use, not the CCD socket.
> > > > > > >
> > > > > > > Check that the speed is correct, the classic uses 9600 8 data No
parity,
> > > > > > > 1 stop. (Often printed as 9600 8N1) check your manual
> > > > > > >
> > > > > > > The most common problem is getting the Tx and Rx lines crossed
over.
> > > > > > >
> > > > > > > Find out what commands the LXD600 uses, if it is the same format
as the
> > > > > > > LX200 then commands such as :GR# will return the RA, :GS# gets the
> > > > > > > sidereal time and so on. Simply by using a standard terminal
program you
> > > > > > > can manually send the commands to the mount and see what the
response is.
> > > > > > >
> > > > > > > I normally suggest Teraterm as the terminal program
> > > > > > > http://www.ayera.com/teraterm/
> > > > > > > Is the site I normally get it from...
> > > > > > >
> > > > > > > You can use Hyperterm, which normally works, however I have found
that it
> > > > > > > can sometimes have a mind of it's own and refuse to work. I have
never
> > > > > > > found out why this is, neither could a good many people at work.
We
> > > > > > > started recommending TeraTerm for this reason, it proved to be
bomb
> > > > > > > proof and made our support staff much happier.
> > > > > > >
> > > > > > >
> > > > > > > An even more simple test is to link the tx and rx pins on the end
of your
> > > > > > > cable, you may need a spare socket to make this easy, then using a
> > > > > > > terminal program everything you type will echo back onto the
screen.
> > > > > > > Break the link and the echo will stop. That will prove the Rs232
cable.
> > > > > > > (but it will not detect if the Tx and Rx are the wrong way around)
> > > > > > >
> > > > > > > If you can talk to the mount manually with a terminal program then
you
> > > > > > > will know that there is nothing wrong with the communications, and
you
> > > > > > > can have a closer look at the software.
> > > > > > >
> > > > > > >
> > > > > > > Andy
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On Tue, 24 Nov 2009 00:14:10 -0000
> > > > > > > "marc_angelillo" <mangelillo@> wrote:
> > > > > > >
> > > > > > > > Hi there,
> > > > > > > >
> > > > > > > > I've recently purchased a used Meade 127ED APO on an LXD600 GEM.
Since then I've
> > > > > > > > been hard at work trying to get an auto-guiding setup all ready
to go.
> > > > > > > >
> > > > > > > > So far I've done the following:
> > > > > > > > - I've made some scope rings so I can piggy-back my Galileoscope
as a guide
> > > > > > > > scope.
> > > > > > > > - I've built a serial-to-2.5mm stereo wire to control my Canon
350D from the
> > > > > > > > laptop
> > > > > > > > - I've build a serial-to-RS232 adapter as per the instructions
in the manual
> > > > > > > > (and several helpful websites).
> > > > > > > >
> > > > > > > > All I need now is a CCD webcam such as the Logitech Quickcam Pro
4000 and I
> > > > > > > > should have everything I need to get out in the field and start
taking photos.
> > > > > > > >
> > > > > > > > However, I'm having lots of trouble getting my PC to connect to
the mount
> > > > > > > > through the RS232 connection. I'm using the GuideDog software to
connect. At
> > > > > > > > first I couldn't even select a telescope, but installing the
ASCOM platform
> > > > > > > > solved that problem. I also installed the LX200 Classic drivers.
Now I'm getting
> > > > > > > > a message saying that it can't connect to the mount and to check
my connections.
> > > > > > > >
> > > > > > > > Has anyone else had any success trying to do this? I've checked
and re-checked
> > > > > > > > the wiring in my serial-to-RS232 adaptor and I'm sure I've done
it right. Is it
> > > > > > > > possible the mount's RS232 slot is damaged? Is there any way to
diagnose this
> > > > > > > > short of finding another LXD600?
> > > > > > > >
> > > > > > > > Also, I'm wondering if I should be using the 'RS232' or the
'CCD' slot on the
> > > > > > > > mount.
> > > > > > > >
> > > > > > > > Any help would be much appreciated.
> > > > > > > >
> > > > > > > > Thanks!
> > > > > > > > Marc
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > >
> >
> >
>

Gday John

I modified my PEC editor a few years back to allow it to talk to an LXD 750at a
users request ( it uses the 1697CDS protocols )
The leading # was not required for normal operation.

Andrew Johansen Melbourne Australia



--- In Meade-Uncensored@yahoogroups.com, John Mahony <jmmahony@...> wrote:
>
> ----- Original Message ----
>
> > From: autostaretx <rseymour@...>
> >
> > In the current autostars, the leading "#" is optional.
>
> Emphasis on "current autostars".  This is a classic, so it's not only not
current, it's not even autostar.
>
> -John
>
>
> > What it -does- (in the autostar) is guarantee that the -previous-
> > command is terminated (and/or any noise on the wires is flushed).
> >
> > have fun
> > --dick
> >
> > --- In Meade-Uncensored@yahoogroups.com, John Mahony wrote:
> > >
> > > ----- Original Message ----
> > >
> > > > From: marc_angelillo
> > > >
> > > > Update: Tried linking the tx and rx pins and Teraterm seems to be
showing
> > > > everything I type in the main window. I guess that means it's wired
right.
> > Still
> > > > not sure how to send a command like :GR# to the mount though. Am I just
> > supposed
> > > > to type it?
> > >
> > > I've never used those "terminal" programs, but I've written some programs
(in
> > BASIC) for the LX200.  The commands (and an example program) are shown at
the
> > end of the manual.  The  #1697 CDS (computer drive system) for the
> > LXD600/650/700/750 GEMs used essentially the same electronics and computer
> > system as the LX200 classic, and the manual for CDS the has the same info at
the
> > end of that manual.  When you send a command through the COM port in a BASIC
> > program, the actual text of the message has a "#" sign at both the start and
the
> > end of every command.  When people talk about these commands, the leading #
is
> > usually not mentioned (my computer skills are very limited, so I don't know
> > why), but the example program in the manual shows these.
> > >
> > > So try adding the # at the start.
> > >
> > > See also
> > >
> > > There are lots of LXD600-750 owners there.
> > >
> > > -John
> > >
> > >
> > >
> > > > --- In Meade-Uncensored@yahoogroups.com, "marc_angelillo"
> > > > wrote:
> > > > >
> > > > > Thanks for all the helpful hints Andy.
> > > > >
> > > > > I just tried connecting with Teraterm, but although it said it was
> > connected,
> > > > I couldn't seem to type any commands. Is there some special way to send
the
> > > > commands to the mount? Or is it due to a connection problem?
> > > > >
> > > > > I'll try the trick where you connect the Rx and Tx pins next. I'll let
you
> >
> > > > know how that goes.
> > > > >
> > > > > Thanks,
> > > > > Marc
> > > > >
> > > > > --- In Meade-Uncensored@yahoogroups.com, Andy Eskelson wrote:
> > > > > >
> > > > > > There are lots of things you can do. I don't have an LXD600, I have
a
> > > > > > standard LX200 classic. However RS232 is RS232, that's the socket
you
> > > > > > want to use, not the CCD socket.
> > > > > >
> > > > > > Check that the speed is correct, the classic uses 9600 8 data No
parity,
> > > > > > 1 stop. (Often printed as 9600 8N1) check your manual
> > > > > >
> > > > > > The most common problem is getting the Tx and Rx lines crossed over.
> > > > > >
> > > > > > Find out what commands the LXD600 uses, if it is the same format as
the
> > > > > > LX200 then commands such as :GR# will return the RA, :GS# gets the
> > > > > > sidereal time and so on. Simply by using a standard terminal program
you
> > > > > > can manually send the commands to the mount and see what the
response
> > is.
> > > > > >
> > > > > > I normally suggest Teraterm as the terminal program
> > > > > > http://www.ayera.com/teraterm/
> > > > > > Is the site I normally get it from...
> > > > > >
> > > > > > You can use Hyperterm, which normally works, however I have found
that
> > it
> > > > > > can sometimes have a mind of it's own and refuse to work. I have
never
> > > > > > found out why this is, neither could a good many people at work. We
> > > > > > started recommending TeraTerm for this reason, it proved to be bomb
> > > > > > proof and made our support staff much happier.
> > > > > >
> > > > > >
> > > > > > An even more simple test is to link the tx and rx pins on the end of
> > your
> > > > > > cable, you may need a spare socket to make this easy, then using a
> > > > > > terminal program everything you type will echo back onto the screen.
> > > > > > Break the link and the echo will stop. That will prove the Rs232
cable.
> > > > > > (but it will not detect if the Tx and Rx are the wrong way around)
> > > > > >
> > > > > > If you can talk to the mount manually with a terminal program then
you
> > > > > > will know that there is nothing wrong with the communications, and
you
> > > > > > can have a closer look at the software.
> > > > > >
> > > > > >
> > > > > > Andy
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Tue, 24 Nov 2009 00:14:10 -0000
> > > > > > "marc_angelillo" wrote:
> > > > > >
> > > > > > > Hi there,
> > > > > > >
> > > > > > > I've recently purchased a used Meade 127ED APO on an LXD600 GEM.
Since
> >
> > > > then I've
> > > > > > > been hard at work trying to get an auto-guiding setup all ready to
go.
> > > > > > >
> > > > > > > So far I've done the following:
> > > > > > > - I've made some scope rings so I can piggy-back my Galileoscope
as a
> > > > guide
> > > > > > > scope.
> > > > > > > - I've built a serial-to-2.5mm stereo wire to control my Canon
350D
> > from
> > > > the
> > > > > > > laptop
> > > > > > > - I've build a serial-to-RS232 adapter as per the instructions in
the
> > > > manual
> > > > > > > (and several helpful websites).
> > > > > > >
> > > > > > > All I need now is a CCD webcam such as the Logitech Quickcam Pro
4000
> > and
> > > > I
> > > > > > > should have everything I need to get out in the field and start
taking
> >
> > > > photos.
> > > > > > >
> > > > > > > However, I'm having lots of trouble getting my PC to connect to
the
> > mount
> > > > > > > through the RS232 connection. I'm using the GuideDog software to
> > connect.
> > > > At
> > > > > > > first I couldn't even select a telescope, but installing the ASCOM
> > > > platform
> > > > > > > solved that problem. I also installed the LX200 Classic drivers.
Now
> > I'm
> > > > getting
> > > > > > > a message saying that it can't connect to the mount and to check
my
> > > > connections.
> > > > > > >
> > > > > > > Has anyone else had any success trying to do this? I've checked
and
> > > > re-checked
> > > > > > > the wiring in my serial-to-RS232 adaptor and I'm sure I've done it
> > right.
> > > > Is it
> > > > > > > possible the mount's RS232 slot is damaged? Is there any way to
> > diagnose
> > > > this
> > > > > > > short of finding another LXD600?
> > > > > > >
> > > > > > > Also, I'm wondering if I should be using the 'RS232' or the 'CCD'
slot
> > on
> > > > the
> > > > > > > mount.
> > > > > > >
> > > > > > > Any help would be much appreciated.
> > > > > > >
> > > > > > > Thanks!
> > > > > > > Marc
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > >
> > > > ------------------------------------
> > > >
> > > > Yahoo! Groups Links
> > > >
> > > >
> > > >
> > >
> >
> >
> >
> >
> > ------------------------------------
> >
> > Yahoo! Groups Links
> >
> >
> >
>

It works! I don't know what I did different, but this time I plugged everything
in and typed #:GR# and got a response right away! I disconnected and then tried
without the leading '#' and it still worked... so I have no idea what the
problem was before.

In any case, I still can't connect to the mount with GuideDog or PHD Guiding.
GuideDog just says it can't connect and to check connections. PHD Guiding says
"ASCOM driver problem during connection". If I try again it then says "Could not
establish instance of MeadeEx.Telescope".

I guess I'm not using the right ASCOM driver for the mount, but I thought it was
a Meade Classic, which is why I got the "Meade Classic and Autostar I" driver. I
also tried the "Generic LX-200" driver. That one connects fine, but I can't seem
to slew using the controls in GuideDog. The only other Meade driver is the
"Meade LX200GPS and LX200R" driver, but it clearly says on the ASCOM site not to
use it with the LX200 Classic.

So a little good news and a little bad. Any suggestions? If I can just get the
thing to slew from my PC I'll be extatic.

Thanks

Marc


--- In Meade-Uncensored@yahoogroups.com, "johansea" <johansea@...> wrote:
>
> Gday John
>
> I modified my PEC editor a few years back to allow it to talk to an LXD 750at
a users request ( it uses the 1697CDS protocols )
> The leading # was not required for normal operation.
>
> Andrew Johansen Melbourne Australia
>
>
>
> --- In Meade-Uncensored@yahoogroups.com, John Mahony <jmmahony@> wrote:
> >
> > ----- Original Message ----
> >
> > > From: autostaretx <rseymour@>
> > >
> > > In the current autostars, the leading "#" is optional.
> >
> > Emphasis on "current autostars".  This is a classic, so it's not only not
current, it's not even autostar.
> >
> > -John
> >
> >
> > > What it -does- (in the autostar) is guarantee that the -previous-
> > > command is terminated (and/or any noise on the wires is flushed).
> > >
> > > have fun
> > > --dick
> > >
> > > --- In Meade-Uncensored@yahoogroups.com, John Mahony wrote:
> > > >
> > > > ----- Original Message ----
> > > >
> > > > > From: marc_angelillo
> > > > >
> > > > > Update: Tried linking the tx and rx pins and Teraterm seems to be
showing
> > > > > everything I type in the main window. I guess that means it's wired
right.
> > > Still
> > > > > not sure how to send a command like :GR# to the mount though. Am I
just
> > > supposed
> > > > > to type it?
> > > >
> > > > I've never used those "terminal" programs, but I've written some
programs (in
> > > BASIC) for the LX200.  The commands (and an example program) are shown at
the
> > > end of the manual.  The  #1697 CDS (computer drive system) for the
> > > LXD600/650/700/750 GEMs used essentially the same electronics and computer
> > > system as the LX200 classic, and the manual for CDS the has the same info
at the
> > > end of that manual.  When you send a command through the COM port in a
BASIC
> > > program, the actual text of the message has a "#" sign at both the start
and the
> > > end of every command.  When people talk about these commands, the leading
# is
> > > usually not mentioned (my computer skills are very limited, so I don't
know
> > > why), but the example program in the manual shows these.
> > > >
> > > > So try adding the # at the start.
> > > >
> > > > See also
> > > >
> > > > There are lots of LXD600-750 owners there.
> > > >
> > > > -John
> > > >
> > > >
> > > >
> > > > > --- In Meade-Uncensored@yahoogroups.com, "marc_angelillo"
> > > > > wrote:
> > > > > >
> > > > > > Thanks for all the helpful hints Andy.
> > > > > >
> > > > > > I just tried connecting with Teraterm, but although it said it was
> > > connected,
> > > > > I couldn't seem to type any commands. Is there some special way to
send the
> > > > > commands to the mount? Or is it due to a connection problem?
> > > > > >
> > > > > > I'll try the trick where you connect the Rx and Tx pins next. I'll
let you
> > >
> > > > > know how that goes.
> > > > > >
> > > > > > Thanks,
> > > > > > Marc
> > > > > >
> > > > > > --- In Meade-Uncensored@yahoogroups.com, Andy Eskelson wrote:
> > > > > > >
> > > > > > > There are lots of things you can do. I don't have an LXD600, I
have a
> > > > > > > standard LX200 classic. However RS232 is RS232, that's the socket
you
> > > > > > > want to use, not the CCD socket.
> > > > > > >
> > > > > > > Check that the speed is correct, the classic uses 9600 8 data No
parity,
> > > > > > > 1 stop. (Often printed as 9600 8N1) check your manual
> > > > > > >
> > > > > > > The most common problem is getting the Tx and Rx lines crossed
over.
> > > > > > >
> > > > > > > Find out what commands the LXD600 uses, if it is the same format
as the
> > > > > > > LX200 then commands such as :GR# will return the RA, :GS# gets the
> > > > > > > sidereal time and so on. Simply by using a standard terminal
program you
> > > > > > > can manually send the commands to the mount and see what the
response
> > > is.
> > > > > > >
> > > > > > > I normally suggest Teraterm as the terminal program
> > > > > > > http://www.ayera.com/teraterm/
> > > > > > > Is the site I normally get it from...
> > > > > > >
> > > > > > > You can use Hyperterm, which normally works, however I have found
that
> > > it
> > > > > > > can sometimes have a mind of it's own and refuse to work. I have
never
> > > > > > > found out why this is, neither could a good many people at work.
We
> > > > > > > started recommending TeraTerm for this reason, it proved to be
bomb
> > > > > > > proof and made our support staff much happier.
> > > > > > >
> > > > > > >
> > > > > > > An even more simple test is to link the tx and rx pins on the end
of
> > > your
> > > > > > > cable, you may need a spare socket to make this easy, then using a
> > > > > > > terminal program everything you type will echo back onto the
screen.
> > > > > > > Break the link and the echo will stop. That will prove the Rs232
cable.
> > > > > > > (but it will not detect if the Tx and Rx are the wrong way around)
> > > > > > >
> > > > > > > If you can talk to the mount manually with a terminal program then
you
> > > > > > > will know that there is nothing wrong with the communications, and
you
> > > > > > > can have a closer look at the software.
> > > > > > >
> > > > > > >
> > > > > > > Andy
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On Tue, 24 Nov 2009 00:14:10 -0000
> > > > > > > "marc_angelillo" wrote:
> > > > > > >
> > > > > > > > Hi there,
> > > > > > > >
> > > > > > > > I've recently purchased a used Meade 127ED APO on an LXD600 GEM.
Since
> > >
> > > > > then I've
> > > > > > > > been hard at work trying to get an auto-guiding setup all ready
to go.
> > > > > > > >
> > > > > > > > So far I've done the following:
> > > > > > > > - I've made some scope rings so I can piggy-back my Galileoscope
as a
> > > > > guide
> > > > > > > > scope.
> > > > > > > > - I've built a serial-to-2.5mm stereo wire to control my Canon
350D
> > > from
> > > > > the
> > > > > > > > laptop
> > > > > > > > - I've build a serial-to-RS232 adapter as per the instructions
in the
> > > > > manual
> > > > > > > > (and several helpful websites).
> > > > > > > >
> > > > > > > > All I need now is a CCD webcam such as the Logitech Quickcam Pro
4000
> > > and
> > > > > I
> > > > > > > > should have everything I need to get out in the field and start
taking
> > >
> > > > > photos.
> > > > > > > >
> > > > > > > > However, I'm having lots of trouble getting my PC to connect to
the
> > > mount
> > > > > > > > through the RS232 connection. I'm using the GuideDog software to
> > > connect.
> > > > > At
> > > > > > > > first I couldn't even select a telescope, but installing the
ASCOM
> > > > > platform
> > > > > > > > solved that problem. I also installed the LX200 Classic drivers.
Now
> > > I'm
> > > > > getting
> > > > > > > > a message saying that it can't connect to the mount and to check
my
> > > > > connections.
> > > > > > > >
> > > > > > > > Has anyone else had any success trying to do this? I've checked
and
> > > > > re-checked
> > > > > > > > the wiring in my serial-to-RS232 adaptor and I'm sure I've done
it
> > > right.
> > > > > Is it
> > > > > > > > possible the mount's RS232 slot is damaged? Is there any way to
> > > diagnose
> > > > > this
> > > > > > > > short of finding another LXD600?
> > > > > > > >
> > > > > > > > Also, I'm wondering if I should be using the 'RS232' or the
'CCD' slot
> > > on
> > > > > the
> > > > > > > > mount.
> > > > > > > >
> > > > > > > > Any help would be much appreciated.
> > > > > > > >
> > > > > > > > Thanks!
> > > > > > > > Marc
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > ------------------------------------
> > > > >
> > > > > Yahoo! Groups Links
> > > > >
> > > > >
> > > > >
> > > >
> > >
> > >
> > >
> > >
> > > ------------------------------------
> > >
> > > Yahoo! Groups Links
> > >
> > >
> > >
> >
>

Gday Marc

I cant say how the ASCOM drivers work
but in most cases, you send a #x06 command to the scope
and it responds with a letter to define what it is.
The LXD750 etc respond with "G" (IIRC), vs the std "A" or "P"
of the later models.
If the driver isnt written to detect a "G" as meaning a Meade scope, then it
wont get any further.

Andrew Johansen Melbourne Australia

--- In Meade-Uncensored@yahoogroups.com, "marc_angelillo" <mangelillo@...>
wrote:
>
> It works! I don't know what I did different, but this time I plugged
everything in and typed #:GR# and got a response right away! I disconnected and
then tried without the leading '#' and it still worked... so I have no idea what
the problem was before.
>
> In any case, I still can't connect to the mount with GuideDog or PHD Guiding.
GuideDog just says it can't connect and to check connections. PHD Guiding says
"ASCOM driver problem during connection". If I try again it then says "Could not
establish instance of MeadeEx.Telescope".
>
> I guess I'm not using the right ASCOM driver for the mount, but I thought it
was a Meade Classic, which is why I got the "Meade Classic and Autostar I"
driver. I also tried the "Generic LX-200" driver. That one connects fine, but I
can't seem to slew using the controls in GuideDog. The only other Meade driver
is the "Meade LX200GPS and LX200R" driver, but it clearly says on the ASCOM site
not to use it with the LX200 Classic.
>
> So a little good news and a little bad. Any suggestions? If I can just get the
thing to slew from my PC I'll be extatic.
>
> Thanks
>
> Marc
>
>
> --- In Meade-Uncensored@yahoogroups.com, "johansea" <johansea@> wrote:
> >
> > Gday John
> >
> > I modified my PEC editor a few years back to allow it to talk to an LXD
750at a users request ( it uses the 1697CDS protocols )
> > The leading # was not required for normal operation.
> >
> > Andrew Johansen Melbourne Australia
> >
> >
> >
> > --- In Meade-Uncensored@yahoogroups.com, John Mahony <jmmahony@> wrote:
> > >
> > > ----- Original Message ----
> > >
> > > > From: autostaretx <rseymour@>
> > > >
> > > > In the current autostars, the leading "#" is optional.
> > >
> > > Emphasis on "current autostars".  This is a classic, so it's not only not
current, it's not even autostar.
> > >
> > > -John
> > >
> > >
> > > > What it -does- (in the autostar) is guarantee that the -previous-
> > > > command is terminated (and/or any noise on the wires is flushed).
> > > >
> > > > have fun
> > > > --dick
> > > >
> > > > --- In Meade-Uncensored@yahoogroups.com, John Mahony wrote:
> > > > >
> > > > > ----- Original Message ----
> > > > >
> > > > > > From: marc_angelillo
> > > > > >
> > > > > > Update: Tried linking the tx and rx pins and Teraterm seems to be
showing
> > > > > > everything I type in the main window. I guess that means it's wired
right.
> > > > Still
> > > > > > not sure how to send a command like :GR# to the mount though. Am I
just
> > > > supposed
> > > > > > to type it?
> > > > >
> > > > > I've never used those "terminal" programs, but I've written some
programs (in
> > > > BASIC) for the LX200.  The commands (and an example program) are shown
at the
> > > > end of the manual.  The  #1697 CDS (computer drive system) for the
> > > > LXD600/650/700/750 GEMs used essentially the same electronics and
computer
> > > > system as the LX200 classic, and the manual for CDS the has the same
info at the
> > > > end of that manual.  When you send a command through the COM port in a
BASIC
> > > > program, the actual text of the message has a "#" sign at both the start
and the
> > > > end of every command.  When people talk about these commands, the
leading # is
> > > > usually not mentioned (my computer skills are very limited, so I don't
know
> > > > why), but the example program in the manual shows these.
> > > > >
> > > > > So try adding the # at the start.
> > > > >
> > > > > See also
> > > > >
> > > > > There are lots of LXD600-750 owners there.
> > > > >
> > > > > -John
> > > > >
> > > > >
> > > > >
> > > > > > --- In Meade-Uncensored@yahoogroups.com, "marc_angelillo"
> > > > > > wrote:
> > > > > > >
> > > > > > > Thanks for all the helpful hints Andy.
> > > > > > >
> > > > > > > I just tried connecting with Teraterm, but although it said it was
> > > > connected,
> > > > > > I couldn't seem to type any commands. Is there some special way to
send the
> > > > > > commands to the mount? Or is it due to a connection problem?
> > > > > > >
> > > > > > > I'll try the trick where you connect the Rx and Tx pins next. I'll
let you
> > > >
> > > > > > know how that goes.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Marc
> > > > > > >
> > > > > > > --- In Meade-Uncensored@yahoogroups.com, Andy Eskelson wrote:
> > > > > > > >
> > > > > > > > There are lots of things you can do. I don't have an LXD600, I
have a
> > > > > > > > standard LX200 classic. However RS232 is RS232, that's the
socket you
> > > > > > > > want to use, not the CCD socket.
> > > > > > > >
> > > > > > > > Check that the speed is correct, the classic uses 9600 8 data No
parity,
> > > > > > > > 1 stop. (Often printed as 9600 8N1) check your manual
> > > > > > > >
> > > > > > > > The most common problem is getting the Tx and Rx lines crossed
over.
> > > > > > > >
> > > > > > > > Find out what commands the LXD600 uses, if it is the same format
as the
> > > > > > > > LX200 then commands such as :GR# will return the RA, :GS# gets
the
> > > > > > > > sidereal time and so on. Simply by using a standard terminal
program you
> > > > > > > > can manually send the commands to the mount and see what the
response
> > > > is.
> > > > > > > >
> > > > > > > > I normally suggest Teraterm as the terminal program
> > > > > > > > http://www.ayera.com/teraterm/
> > > > > > > > Is the site I normally get it from...
> > > > > > > >
> > > > > > > > You can use Hyperterm, which normally works, however I have
found that
> > > > it
> > > > > > > > can sometimes have a mind of it's own and refuse to work. I have
never
> > > > > > > > found out why this is, neither could a good many people at work.
We
> > > > > > > > started recommending TeraTerm for this reason, it proved to be
bomb
> > > > > > > > proof and made our support staff much happier.
> > > > > > > >
> > > > > > > >
> > > > > > > > An even more simple test is to link the tx and rx pins on the
end of
> > > > your
> > > > > > > > cable, you may need a spare socket to make this easy, then using
a
> > > > > > > > terminal program everything you type will echo back onto the
screen.
> > > > > > > > Break the link and the echo will stop. That will prove the Rs232
cable.
> > > > > > > > (but it will not detect if the Tx and Rx are the wrong way
around)
> > > > > > > >
> > > > > > > > If you can talk to the mount manually with a terminal program
then you
> > > > > > > > will know that there is nothing wrong with the communications,
and you
> > > > > > > > can have a closer look at the software.
> > > > > > > >
> > > > > > > >
> > > > > > > > Andy
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > On Tue, 24 Nov 2009 00:14:10 -0000
> > > > > > > > "marc_angelillo" wrote:
> > > > > > > >
> > > > > > > > > Hi there,
> > > > > > > > >
> > > > > > > > > I've recently purchased a used Meade 127ED APO on an LXD600
GEM. Since
> > > >
> > > > > > then I've
> > > > > > > > > been hard at work trying to get an auto-guiding setup all
ready to go.
> > > > > > > > >
> > > > > > > > > So far I've done the following:
> > > > > > > > > - I've made some scope rings so I can piggy-back my
Galileoscope as a
> > > > > > guide
> > > > > > > > > scope.
> > > > > > > > > - I've built a serial-to-2.5mm stereo wire to control my Canon
350D
> > > > from
> > > > > > the
> > > > > > > > > laptop
> > > > > > > > > - I've build a serial-to-RS232 adapter as per the instructions
in the
> > > > > > manual
> > > > > > > > > (and several helpful websites).
> > > > > > > > >
> > > > > > > > > All I need now is a CCD webcam such as the Logitech Quickcam
Pro 4000
> > > > and
> > > > > > I
> > > > > > > > > should have everything I need to get out in the field and
start taking
> > > >
> > > > > > photos.
> > > > > > > > >
> > > > > > > > > However, I'm having lots of trouble getting my PC to connect
to the
> > > > mount
> > > > > > > > > through the RS232 connection. I'm using the GuideDog software
to
> > > > connect.
> > > > > > At
> > > > > > > > > first I couldn't even select a telescope, but installing the
ASCOM
> > > > > > platform
> > > > > > > > > solved that problem. I also installed the LX200 Classic
drivers. Now
> > > > I'm
> > > > > > getting
> > > > > > > > > a message saying that it can't connect to the mount and to
check my
> > > > > > connections.
> > > > > > > > >
> > > > > > > > > Has anyone else had any success trying to do this? I've
checked and
> > > > > > re-checked
> > > > > > > > > the wiring in my serial-to-RS232 adaptor and I'm sure I've
done it
> > > > right.
> > > > > > Is it
> > > > > > > > > possible the mount's RS232 slot is damaged? Is there any way
to
> > > > diagnose
> > > > > > this
> > > > > > > > > short of finding another LXD600?
> > > > > > > > >
> > > > > > > > > Also, I'm wondering if I should be using the 'RS232' or the
'CCD' slot
> > > > on
> > > > > > the
> > > > > > > > > mount.
> > > > > > > > >
> > > > > > > > > Any help would be much appreciated.
> > > > > > > > >
> > > > > > > > > Thanks!
> > > > > > > > > Marc
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > ------------------------------------
> > > > > >
> > > > > > Yahoo! Groups Links
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > >
> > > > ------------------------------------
> > > >
> > > > Yahoo! Groups Links
> > > >
> > > >
> > > >
> > >
> >
>

That could be it.  I think there are a handful of minor differences in the
command set between the LX200 classic and the LXD600-750 GEMs to account for the
diff between a GEM and a fork, and that could be causing a problem with the
ASCOM driver.

Ask on the meade_refractors group.  There has to be someone there who has
connected their scope to a computer (or at least several who have tried).

-John




----- Original Message ----
> From: johansea <johansea@...>
>
> Gday Marc
>
> I cant say how the ASCOM drivers work
> but in most cases, you send a #x06 command to the scope
> and it responds with a letter to define what it is.
> The LXD750 etc respond with "G" (IIRC), vs the std "A" or "P"
> of the later models.
> If the driver isnt written to detect a "G" as meaning a Meade scope, then it
> wont get any further.
>
> Andrew Johansen Melbourne Australia
>
> --- In Meade-Uncensored@yahoogroups.com, "marc_angelillo"
> wrote:
> >
> > It works! I don't know what I did different, but this time I plugged
> everything in and typed #:GR# and got a response right away! I disconnected
and
> then tried without the leading '#' and it still worked... so I have no idea
what
> the problem was before.
> >
> > In any case, I still can't connect to the mount with GuideDog or PHD
Guiding.
> GuideDog just says it can't connect and to check connections. PHD Guiding says
> "ASCOM driver problem during connection". If I try again it then says "Could
not
> establish instance of MeadeEx.Telescope".
> >
> > I guess I'm not using the right ASCOM driver for the mount, but I thought it
> was a Meade Classic, which is why I got the "Meade Classic and Autostar I"
> driver. I also tried the "Generic LX-200" driver. That one connects fine, but
I
> can't seem to slew using the controls in GuideDog. The only other Meade driver
> is the "Meade LX200GPS and LX200R" driver, but it clearly says on the ASCOM
site
> not to use it with the LX200 Classic.
> >
> > So a little good news and a little bad. Any suggestions? If I can just get
the
> thing to slew from my PC I'll be extatic.
> >
> > Thanks
> >
> > Marc
> >
> >
> > --- In Meade-Uncensored@yahoogroups.com, "johansea" wrote:
> > >
> > > Gday John
> > >
> > > I modified my PEC editor a few years back to allow it to talk to an LXD
> 750at a users request ( it uses the 1697CDS protocols )
> > > The leading # was not required for normal operation.
> > >
> > > Andrew Johansen Melbourne Australia
> > >
> > >
> > >
> > > --- In Meade-Uncensored@yahoogroups.com, John Mahony wrote:
> > > >
> > > > ----- Original Message ----
> > > >
> > > > > From: autostaretx
> > > > >
> > > > > In the current autostars, the leading "#" is optional.
> > > >
> > > > Emphasis on "current autostars".  This is a classic, so it's not only
not
> current, it's not even autostar.
> > > >
> > > > -John
> > > >
> > > >
> > > > > What it -does- (in the autostar) is guarantee that the -previous-
> > > > > command is terminated (and/or any noise on the wires is flushed).
> > > > >
> > > > > have fun
> > > > > --dick
> > > > >
> > > > > --- In Meade-Uncensored@yahoogroups.com, John Mahony wrote:
> > > > > >
> > > > > > ----- Original Message ----
> > > > > >
> > > > > > > From: marc_angelillo
> > > > > > >
> > > > > > > Update: Tried linking the tx and rx pins and Teraterm seems to be
> showing
> > > > > > > everything I type in the main window. I guess that means it's
wired
> right.
> > > > > Still
> > > > > > > not sure how to send a command like :GR# to the mount though. Am I
> just
> > > > > supposed
> > > > > > > to type it?
> > > > > >
> > > > > > I've never used those "terminal" programs, but I've written some
> programs (in
> > > > > BASIC) for the LX200.  The commands (and an example program) are shown
> at the
> > > > > end of the manual.  The  #1697 CDS (computer drive system) for the
> > > > > LXD600/650/700/750 GEMs used essentially the same electronics and
> computer
> > > > > system as the LX200 classic, and the manual for CDS the has the same
> info at the
> > > > > end of that manual.  When you send a command through the COM port in a
> BASIC
> > > > > program, the actual text of the message has a "#" sign at both the
start
> and the
> > > > > end of every command.  When people talk about these commands, the
> leading # is
> > > > > usually not mentioned (my computer skills are very limited, so I don't
> know
> > > > > why), but the example program in the manual shows these.
> > > > > >
> > > > > > So try adding the # at the start.
> > > > > >
> > > > > > See also
> > > > > >
> > > > > > There are lots of LXD600-750 owners there.
> > > > > >
> > > > > > -John
> > > > > >
> > > > > >
> > > > > >
> > > > > > > --- In Meade-Uncensored@yahoogroups.com, "marc_angelillo"
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > Thanks for all the helpful hints Andy.
> > > > > > > >
> > > > > > > > I just tried connecting with Teraterm, but although it said it
was
>
> > > > > connected,
> > > > > > > I couldn't seem to type any commands. Is there some special way to
> send the
> > > > > > > commands to the mount? Or is it due to a connection problem?
> > > > > > > >
> > > > > > > > I'll try the trick where you connect the Rx and Tx pins next.
I'll
> let you
> > > > >
> > > > > > > know how that goes.
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > > Marc
> > > > > > > >
> > > > > > > > --- In Meade-Uncensored@yahoogroups.com, Andy Eskelson wrote:
> > > > > > > > >
> > > > > > > > > There are lots of things you can do. I don't have an LXD600, I
> have a
> > > > > > > > > standard LX200 classic. However RS232 is RS232, that's the
> socket you
> > > > > > > > > want to use, not the CCD socket.
> > > > > > > > >
> > > > > > > > > Check that the speed is correct, the classic uses 9600 8 data
No
> parity,
> > > > > > > > > 1 stop. (Often printed as 9600 8N1) check your manual
> > > > > > > > >
> > > > > > > > > The most common problem is getting the Tx and Rx lines crossed
> over.
> > > > > > > > >
> > > > > > > > > Find out what commands the LXD600 uses, if it is the same
format
> as the
> > > > > > > > > LX200 then commands such as :GR# will return the RA, :GS# gets
> the
> > > > > > > > > sidereal time and so on. Simply by using a standard terminal
> program you
> > > > > > > > > can manually send the commands to the mount and see what the
> response
> > > > > is.
> > > > > > > > >
> > > > > > > > > I normally suggest Teraterm as the terminal program
> > > > > > > > > http://www.ayera.com/teraterm/
> > > > > > > > > Is the site I normally get it from...
> > > > > > > > >
> > > > > > > > > You can use Hyperterm, which normally works, however I have
> found that
> > > > > it
> > > > > > > > > can sometimes have a mind of it's own and refuse to work. I
have
> never
> > > > > > > > > found out why this is, neither could a good many people at
work.
> We
> > > > > > > > > started recommending TeraTerm for this reason, it proved to be
> bomb
> > > > > > > > > proof and made our support staff much happier.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > An even more simple test is to link the tx and rx pins on the
> end of
> > > > > your
> > > > > > > > > cable, you may need a spare socket to make this easy, then
using
> a
> > > > > > > > > terminal program everything you type will echo back onto the
> screen.
> > > > > > > > > Break the link and the echo will stop. That will prove the
Rs232
> cable.
> > > > > > > > > (but it will not detect if the Tx and Rx are the wrong way
> around)
> > > > > > > > >
> > > > > > > > > If you can talk to the mount manually with a terminal program
> then you
> > > > > > > > > will know that there is nothing wrong with the communications,
> and you
> > > > > > > > > can have a closer look at the software.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Andy
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Tue, 24 Nov 2009 00:14:10 -0000
> > > > > > > > > "marc_angelillo" wrote:
> > > > > > > > >
> > > > > > > > > > Hi there,
> > > > > > > > > >
> > > > > > > > > > I've recently purchased a used Meade 127ED APO on an LXD600
> GEM. Since
> > > > >
> > > > > > > then I've
> > > > > > > > > > been hard at work trying to get an auto-guiding setup all
> ready to go.
> > > > > > > > > >
> > > > > > > > > > So far I've done the following:
> > > > > > > > > > - I've made some scope rings so I can piggy-back my
> Galileoscope as a
> > > > > > > guide
> > > > > > > > > > scope.
> > > > > > > > > > - I've built a serial-to-2.5mm stereo wire to control my
Canon
> 350D
> > > > > from
> > > > > > > the
> > > > > > > > > > laptop
> > > > > > > > > > - I've build a serial-to-RS232 adapter as per the
instructions
> in the
> > > > > > > manual
> > > > > > > > > > (and several helpful websites).
> > > > > > > > > >
> > > > > > > > > > All I need now is a CCD webcam such as the Logitech Quickcam
> Pro 4000
> > > > > and
> > > > > > > I
> > > > > > > > > > should have everything I need to get out in the field and
> start taking
> > > > >
> > > > > > > photos.
> > > > > > > > > >
> > > > > > > > > > However, I'm having lots of trouble getting my PC to connect
> to the
> > > > > mount
> > > > > > > > > > through the RS232 connection. I'm using the GuideDog
software
> to
> > > > > connect.
> > > > > > > At
> > > > > > > > > > first I couldn't even select a telescope, but installing the
> ASCOM
> > > > > > > platform
> > > > > > > > > > solved that problem. I also installed the LX200 Classic
> drivers. Now
> > > > > I'm
> > > > > > > getting
> > > > > > > > > > a message saying that it can't connect to the mount and to
> check my
> > > > > > > connections.
> > > > > > > > > >
> > > > > > > > > > Has anyone else had any success trying to do this? I've
> checked and
> > > > > > > re-checked
> > > > > > > > > > the wiring in my serial-to-RS232 adaptor and I'm sure I've
> done it
> > > > > right.
> > > > > > > Is it
> > > > > > > > > > possible the mount's RS232 slot is damaged? Is there any way
> to
> > > > > diagnose
> > > > > > > this
> > > > > > > > > > short of finding another LXD600?
> > > > > > > > > >
> > > > > > > > > > Also, I'm wondering if I should be using the 'RS232' or the
> 'CCD' slot
> > > > > on
> > > > > > > the
> > > > > > > > > > mount.
> > > > > > > > > >
> > > > > > > > > > Any help would be much appreciated.
> > > > > > > > > >
> > > > > > > > > > Thanks!
> > > > > > > > > > Marc