Meade AutoStar Suit RS232 to Serial adapter compatibility Issues with Win 10

[@lanzer22]

The problem described in this video has to do with Windows not natively supporting some of the USB to COM Port chipset drivers. There are two major chipsets out there, one is PL2303 and the other being CP21x. Whether you have a dedicated USB cable, or one of those RS232 to USB adapters, you can troubleshoot this by going to device manager and it'll show you a device with a yellow or red exclamation mark if your Windows doesn't have the driver for the cable. If in doubt, just install both chipset drivers. There are also plenty of videos on KZbin that talks about "USB to Com Port Installation" or troubleshooting. Windows 11 shares mostly the same architecture as Win 10 so if things work for one, it should work for other other, as long as they have the same drivers installed.

[@SynthAddict]

nice info, thanks finally upgraded from large Dobs to a Meade Astrograph LX85 - looking forward to trying this stuff out - nice tip about Stellarium, haven't used it for years and it's nicely clear and visual for basic presentations - didn't know it could also do scope control 🙂

[@krazynavyvet1483]

Quick question, I know the video is for win10 issue, but I bought a new laptop (ASUS) and have win11 on it. Would there be any issue with the cable you have described using win11? I am thinking of getting back into using my telescope (Meade LX200GPS 8" SCT). I have DLed the program you use, Stellarium. By the way I subscribed to your channel, excellent videos!

[@jinzai1962]

Thanks, MeadeMods...it took me a long time to find you, but -- I am glad that I did. I bought my second ETX in July -- an ETX-125 Observer. It is surprisingly similar to your LX90 -- except that it is primarily a visual OTA. Do you have the LX80/90 autoguide adapter? I bought it on the off chance that it would work with my rig and -- it appears that it does, after I used Star Patch to update the firmware. Waiting on a suitable guidescope to arrive, but -- I will check it out and post my results to my KZbin channel in a few weeks. I am using the QHY5-II and QHY 30mm mini guidescope.

[@Mike-yx4pt]

Really nice video. Excellent work. Way helpful. Good on ya.

[@congresstart6463]

I have a Meade ETX 90 with the non Autostar controller, is it possible to control the telescope without an Autostar controller? I've tried in the past to no avail, making my own cables and such.

[@canalufo5720]

Thank you for your video. CAN YOU HELP ME? I have a etx 70 without a autostar controler just a pad with the moviments for direct the scope. HOW CAN I CONECT IT TO STELLARIUM USING W7? THANK YOU

[@jhetreprashanth4783]

How to do imaging with Meade LX90 and I have DSI 3 imager ? Can we use Stellarium software or is there any other software like Autostar Envisage? I actually am using Envisage but, when I connect the telescope DSI 3 camera to the laptop and start the Envisage software, the software automatically shuts down. So I am unable to do the imaging. Any help in this is much appreciated.

[@meademods6024]

the meade software is not reliable www.meademods.com

[@garryingle7926]

Jhetre Prashanth..... the meade DSI 3 Imager will only with the meade software but you can use Stellarium to guide your scope. make sure you have the latest version for the DSI 3 from meads web sight there could be an issue with the disk that you got. let me know if this helps.

[@gregoryburns4821]

You stated you pinned the RJ45 to DB9 adapter yourself. What are the pin-out instructions to do this? I ordered the items from Amazon as you stated but I am unaware how to pin the adapter correctly. I have a Meade ETX125EC. I have installed the driver that came with the FTDI cable. Thanks for any help you can provide.

[@meademods6024]

i pined my own because i bought a blue RJ45 adapter that you pin your self so i could have my own custom adapter and to be sure my stuff worked perfect. i have sense changed to a different cable. I now make custom cables Direct USb to RJ12 no more out dated serial adapters . www.meademods.com

[@777wrench]

Meade Mods, I have a 1999 lx200gsp. I have a standard Meade DB9 to RS232 cable assembly. I just purchased a UGreen usb to DB9 cable with the PI2303 chip set. My question is do you know if this is compatible with my scope to do the required updates?

[@meademods6024]

yes it works with all meade mounts and alike www.meademods.com

[@bobunger6341]

Hi, I'm hoping you can help me. I just bought an old 10" LXD55 Schmidt-Newtonian that has an Autostar #497 handset. But the handset does not work. Sometimes it won't even boot up properly, a few times the LCd screen was jibberish, a few times it looks like it was going to work, but then crapped out during the alignment process. Is it possible that this could just be a software update that I need to do, or is it likely that I'll need to just buy a new handset?

[@meademods6024]

sorry for the late reply it sounds like the capacitors need to be updated. i repair the LXD55 mounts . you can contact me at www.meademods.com

[@FITCLUBS101]

Could you please add the Amazon links to the proper cables you're describing here?

[@meademods6024]

seller is Ugreen

[@meademods6024]

but i have sense started making my own custom cables you can contact me about this info . www.meademods.com

[@rgruenhaus]

@@meademods6024 Since?

[@charleswilkes2641]

I’m working on a Meade 200LX GPS and my autostar II says I have no sensor board and also can not communicate with auxiliary. Has a fault in level and North. Do you have a solution for this? And do you sell parts?

[@meademods6024]

Hi Charles I do sell part but my stock is getting thin. no sensor board message could mean any of the three sensor boards . Home sensor, gps level sensor, and the GPS board it self. Please message me on my website www.meademods.com thanks

[@meademods6024]

the AUX could just simply be firmware the latest firmware is 4.2i updated from 4.2g this corrects GPS not getting time and date / Location and other known issues.

[@mikeswift926]

I note from your video that you unplug the new chipset cable from the right hand USB port which you demonstrate as working but then plug in the old cable into the left hand USB port and you find that the cable is not recognised. This is because Windows allocates a new port number to the connection so you will find the port number on the right hand side is different to the left hand side. I would be interested to know if the old cable worked by plugging into the same USB port or check/change port numbers?

[@meademods6024]

it does not matter what port you use iv dont that test already and i have used both ports with the new cable and it recognized both cables

[@jbar6618]

@@meademods6024 windows may have detected both cables but windows still assigns a different comm port number to each, which you then use to update the connection settings in Stellarium. Actually Windows assigns a new comm port anytime you don't plug the cable back into exactly the same usb port. BTW. . I use the $2.50 serial to USB cable on ebay which uses the CH340 chipset and driver. If someone doesn't know how to run down and install the drivers then they may think its not compatible with Windows 10. www.ebay.com/itm/USB-2-0-to-RS-232-DB9-Serial-Device-Converter-Adapter-Cable-Support-Win-7-8-10/271627786208?hash=item3f3e4717e0:g:szoAAOSwGPxaQg71

[@meademods6024]

No it did not work. It is not supported by win 10. Again it was the old chips at the new release cable is supported again I don't use cereal anymore I go directly USB to RJ 12 I make my own custom cables

[@williamhyler5666]

Hay I have a Meade ext 90 telescopes I won't to hook it up to stellarium where can I get the driver to make it work

[@meademods6024]

you just may need a new update connection cable . i make custom cables to connect to the pc direct usb to RJ12 . www.meademods.com

[@garryingle7926]

Jedda73.... if you are getting a runtime error win7 you might want to uninstall and reinstall the Meade software. Go to meade web sight and download the latest version of ASU for win7 and that should fix the issue let me know if that works.

[@garryingle7926]

mike... changing the ports you plug into does not change anything the pc will still auto recognize what usb port you are using.

[@pcbuilderlover4271]

Thank you for a Great informative video! A+

[@meademods6024]

i now make custom cables USB direct to RJ12 no more serial adapters. www.meademods.com

[@meademods6024]

Please contact me on my website Www.meademods.com I have a newer style update / Telescope control cable . Thanks for your reply.

[@pecvideos2861]

Hi, I'm hoping you can help me, too. I can connect my win10-Computer with my telescope but i can't upgrade the Autostar-Software. it still runs version 4G0m (from 1999?). I get the message "no connection to the www", although I can get the new data for comets etc. Can you tell me, where I can find the right upgrade-file 4.2i or 4.2k. I can't figure out what to do. Hopefully greetings from Munich. Christian

[@rgruenhaus]

I haven't used Windows since Vista home Supreme so I am hoping for an android version of scope control!

[@Jedda73]

I cant even get the meade ASU to work. Comes up with a runtime error on my windows 7 machine.

[@jinzai1962]

Without any specifics about your rig, I can tell you that two things that trip most people up are: 1. That awful Meade RS-232/USB adapter with the Prolific chipset -- use only FTDI based cables and you must use the Meade cable for the RS-232 side -- it is NOT pinned out the same as Celestron's. FTDI based RS-232/USB converters are easy to find using Amazon. I opted for a pricier model -- $22 -- it has LEDs to indicate activity and is shielded and uses a ferrite shield, as well -- very nice. The comms from the instrument -- are not actually RS-232, they are SPI (Serial Peripheral Interface -- a microcontroller serial protocol -- most definitely not directly RS232 compatible. FTDI chips are a far better way to accomplish the conversion from SPI to USB.) 2. ASU's comms are garbage, as well. Most laptops have COM1 reserved and many use COM3, as well. Use a port above 4 and -- make sure that your port number isn't 'climbing' on you -- that is another issue about using USB to emulate RS-232 communications. It is very bad on XP/Vista/Windows 7. I use a lot of USB based peripherals, and it quickly gets out of hand. I even went into my registry and reset it because the virtual COM Port was up to 22. I would advise against using hubs, too. Better to dedicate an older laptop for your scope and image with a newer one. I have three laptops, so -- YMMV. There are other programs that can talk to your mount, but -- Star Patch is also able to update your handbox firmware and -- you can add GPS to any 497/Audiostar rig. I am using the free version right now, but -- I will definitely upgrade it soon and add GPS. I *highly recommend* checking out Star Patch -- by upgrading my firmware, my ETX-125 now works like an LX90 -- I will be autoguiding very soon! Finally, I can't say enough good about the Meade Stella -- it brings my ETX-125 online and I can control it from a phone or tablet. Stella also talks to most mounts and is Meade's version of SkySafari. I could also Live Stream my guide camera and imaging camera, but that does not rely on Stella -- it uses the machine connected to the imagers -- WOW! Clear skies.

[@meademods6024]

meades old software is not compatible with old versions of windows. www.meademods.com

[@rgruenhaus]

U-grain or U-green?

[@AndrewMurphy8383]

links would help sir

[@ronbaldwin6382]

Hate to say it, but you didn't even go into device manager to verify port numbers, nor did you change port numbers in the software. But yes, cables that used bootlegged (manufactured in violation of intellectual property rights) prolific chipsets will not work under Windows 10.

[@meademods6024]

sorry but you a very wrong my friend!!! the old chipsets were not compatible with WIN 10 so you were probably using an old cable set. the newer chip sets work with WIN 10 and are backwards compatible. www.meademods.com

[@ronbaldwin6382]

@@meademods6024 Hope you're doing well these days. Good to hear back from you. You may be right... I'm thinking Prolific, a manufacturer of USB / serial adapters who discovered that there were bootlegged copies of their hardware flooding the UART market. So, when Prolific developed their drivers for the next release of windows, they found a way to check if the serial chipset was their own, or of bootlegged design. I seem to remember the initial response was to not allow it to function, but later as the knockoffs got better at disguising, it might have caused unexpected behavior. Sorry if I caused confusion. But I am pretty sure I did not see a check of available com port numbers compared to the setting in AutoStar Suite. I've got a Meade scope question for you, is contact info on your website good?