Jump to content

SkySurveyBanner.jpg.21855908fce40597655603b6c9af720d.jpg

stevear

Members
  • Posts

    37
  • Joined

  • Last visited

Reputation

13 Good

Profile Information

  • Location
    Z34

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Mesu 200 mount and connecting a new Windows 10 laptop. Ascom platform 6.2 is being used. ServoConfig is working and connecting and SiTech.exe is configured as per Steve Richards instructions. Page 18 guides you through connecting the mount via C du C. On pressing "connect" as per the instructions after configuring C du C as per page 18, the Ascom driver reports an error. It says "No connection could be made because the target machine actively refused it. 127.0.0.1:8000". So C du C won't connect. Any solutions to this would be appreciated. Clear skies, Steve
  2. Eventually it all worked. The drivers that were missing were eventually located at https://ftdichip.com/wp-content/uploads/2021/08/CDM212364_Setup.zip After doing this download, the ServoConfig.sys opens and talks to the mount via Comm port 3 Thanks for your help here. However, my wife's windows 10 relatively new laptop also does not have "Ports (Comm & LPT)" listed on device manager. So this connection problem I feel is going to come up again for others. Thanks Steve
  3. Hi Peter, I tried that link for CMD212364 and it returns 404 error page not found? Thanks Steve
  4. Hi Peter, Thanks for the suggestion, to be on the cautious side I have re-run this driver file CDM20830 Setup.exe. It seemingly installs completely correctly. I rebooted the laptop afterwards. Same result, my new laptop does not show the Serial Comm number on Device Manager and ServoConfig.exe does not recognise the connection to the mount. ServoConfig.exe simply says "Couldn't open serial Comm Port", no matter which number is tried. I have to conclude Windows has changed and the drivers on CDM20830 no longer do the job on current (new) windows 10. My old windows 10 laptop still work just fine, connects and runs the mount. I simply do not know what else to do. If you or anyone has a suggestion I'd be very pleased to hear. Clear skies Steve
  5. Thanks for the reply, Yes it is Steve Richards guide i'm using. The new laptop Windows 10 simply did not have Comm ports on device manager, and installing it has not worked. When plugging in the mount via USB, nothing happens, Comm port number does not appear on device manager, nothing does. On my old laptop Comm port 3 pops up when its plugged in and ServoConFig.exe does not recognise the mount under any and all Comm port numbers. I'm at a loss.
  6. Any help on this would be appreciated. It sounds simple, following the Mesu installation guide, and should be. My old laptop still works fine and connects to the mount with no issues. Then I bought a new Windows 10 laptop and I'm trying to connect it to the Mesu 200 mount. The section in the Mesu quick guide page 8 "Connecting your PC says, open device manager and it was discovered that Ports (Comm & LP) was missing. Ports... did not appear when clicking "show hidden devices". So this was installed using the "Add legacy hardware". Now here is the issue, (CDM20830 setup.exe has been run on the new laptop), page 8 of the guide says, open device manager and find the USB serial port comm. The problem is that the USB serial port does not show itself on device manager under Ports (Com & LPT). Extra information. The mount is connected via a working USB cable, I have tried several including a cable that works fine with the older laptop. The PC tells me it is seeing the mount by issuing the connection beeps noise on plugging in the USB cable. On opening ServoConfig.sys and going to Setup Comm port, the software will not recognise any of the Comm ports and always gives the message "Couldn't open serial port". The mount still works fine with the old laptop and when connected the Serial Port Comm always appears as Comm 3 when plugging the USB in. Can anyone advise on how to solve the missing"USB serial port Comm on device manager for a start. I feel this is a Windows 10 issue. Thanks and clear skies Steve
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. By using this site, you agree to our Terms of Use.