I tried all Meade's drivers in ASCOM. The one that works best is Meade Autostar/Audiostar Project (2019). It appears as 'Meade Generic' in the ASCOM chooser once downloaded and installed. I use it with CCDCommander, PHD2 and The Sky 6 at the same time. The Meade USB to serial cable provides the capability of using the USB port on a personal computer to connect to a conventional Meade RS232 serial device. This updated version enables the USB to Serial cable to be used with the following Windows operating systems: Supports the following Windows OS Family (32 and 64 bit): Windows 10; Windows 8.1.
Envisage Software (Click to download)
Meade's DSI camera control and basic image processing software.
CaptureView Software (Click to download)
This software provides an efficient way to transfer, browse, modify and distribute digital media. Upon installation, please use serial number 783A3-68000-07296416. Requires WindowsXP.
NEW- USB to Serial Software v1.12.0 (Click to download)
The Meade USB to serial cable provides the capability of using the USB port on a personal computer to connect to a conventional Meade RS232 serial device.
This updated version enables the USB to Serial cable to be used with the following Windows operating systems:
Drivers Meade Virginia
Supports the following Windows OS Family (32 and 64 bit):
Ultimate Drivers Meadowvale-streetsville
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Vista
- Windows XP SP2 and SP3
- Windows 2000 SP4
- Windows Server 2012R2
- Windows Server 2012
- Windows Server 2008R2
- Windows Server 2008
- Windows Server 2003
The 07507 RS232-USB cable will only work with Windows 10 if it looks like the below. Note the curved body on the 9-pin side. This cable is Win10 compliant (32/64 bit).
The older Meade style cable is NOT Windows 10 compatible and is shown below.
Drivers Medical Certification
Driver Meade LX200GPS / R Ascom 2008
Young Drivers Meadowhall
Hi. not getting to connect PHD2, with the mount of my lx200gps. Using the 2008 Meade LX200GPS / R Ascom driver, can you tell me what other driver I can use for this mount?
If the telescope will not connect with that driver. i suspect that the other compatible drivers will also have problems.
Drivers that should work:
The LX200GPS driver (the one you have)
The Generic LX200 driver
The 'Advanced LX200 Generic' driver
The 'Meade Autostar/Audiostar' driver
The 'Meade Universal Driver Project'
The 'Meade LX200 Classic and Autostar...' driver
But before you try those ... in order to connect to the Autostar, nothing else on your PC should be trying to (or already) connected to the telescope.
The message you are seeing means that the PC has sent a message to the telescope (or whatever COM port you told it) and it is not hearing a reply.
Does Andrew's MyScope app successfully talk to your scope? (i believe you have done updates and other connections to the scope from the PC) If you can talk to the scope with any other program, then all of the hardware (and the initial connection firmware in the telescope) IS working correctly.
My first guess (with no other information) is that you are either telling ASCOM to use the wrong COM port on the PC.
My second guess is that some other program has already grabbed the connection, and ASCOM cannot reach the port (but i would expect a different error message).
MyScope is here: http://members.optusnet.com.au/johansea
Possibly. But they may be 'rough' (bumpy, over-shooting)
The 'real' LX200GPS drivers know all of the motion commands that the LX200GPS can understand.
This means they do not have to use a large hammer when a tiny tap would work.
I do not know what finesse of commands PHD2 is able to ask for.
For large motions, the 'generic' drivers will probably do as well as the LX200GPS drivers.
For small adjustments (specifically: guiding) the generic drivers will not try to use the 'pulse guide' commands the LX200GPS can perform. These are 'move east for XXXX milliseconds' (at guide speed) commands. The 'generic' drivers can simply say 'move east (at guide speed)' and some time later say 'stop'. The 'pulse guide' does not require a separate 'stop' command, since the stop is given by the time specification.
If I was doing this, i would certainly *try* the 'generic' drivers, just to see what would happen.
But that still doesn't tell us why the real LX200GPS driver could not connect.
When i am playing with ASCOM, i use the POTH driver between the application and the LX200GPS driver.
POTH offers a small 'pop-up window' with a minimal hand controller ... that lets me test simple operations 'directly' instead of trying to work out why (for example) PHD2 (or any program) is telling the scope to point at the ground.
I also turn on the 'serial log' function, which records all of the commands that were being sent to the scope for later debugging.
If the questioner is experiencing problems with guiding I suggest they just revert to the trusty hardware ST4 guide cable to guide at night while they debug their software configuration during the day. That way they won't lose clear nights fiddling around with PC to mount interfaces.
Use the manual guide tool in PhD2 and your ears and eyes in the comfort of your workshop under good lighting to chase the PhD2/ASCOM/Driver/Mount problem to ground.
PS: Personally, I use the ST4 hardware interface only. Why? Less software involved and fewer interfaces between software running around in the computers. Plus I can test it with a few switches and LEDs. And less vulnerability to something being obsoleted.
Already working. The problem was that I had to connect to the COM 5 port.
I learn by falling, and failures, and with your great help. Greetings
I tried all Meade's drivers in ASCOM. The one that works best is Meade Autostar/Audiostar Project (2019). It appears as 'Meade Generic' in the ASCOM chooser once downloaded and installed.
I use it with CCDCommander, PHD2 and The Sky 6 at the same time.
It even allows to park it, but not to stop tracking, for example.
Observatorio El gallinero
El berrueco, Madrid