EQMOD communication errors
Posted 16 April 2021 - 01:18 PM
I have upgraded my PC from an old laptop 10 years old and now run a small box type PC Beelink i5 8th generation on windows 10 pro. Everything works OK until I connect my new camera ZWO ASI 533mc. After this EQMOD becomes unresponsive. the message center has all types of comm error like ED=16777216 ER=8977318 MSD=128 MSR=3. I have a heq5 and I am using my old usb to rs232 connector with the same driver. I use Cartes du ciel and connect via my mount hand controller set to PC direct mode. Any help or advice would be most welcome.I think I have some USB issues.
Posted 16 April 2021 - 02:54 PM
if you are looking at the device manager do you see the COM port for the EQMOD disappear after plugging in the camera?
Posted 16 April 2021 - 03:09 PM
Don't know much about the error messages, but if EQMOD is not responsive and your power to the mount is not interrupted, it is more likely the connection between PC and mount that is at fault. I would first check if the cable is connected properly, then check if EQMOD settings are correct. Assuming you are using ASCOM platform, check if the com port number in your ASCOM set up matches that of the PC (see it in device manager) and baud rate (should be 9600 for EQ5) is correct. If everything checks out, perhaps consider using a proper USB EQDIR cable with FTDI or Prolific chip. It should make a more reliable connection. By the way, you really do not need to use the hand controller if using cable to connect to your PC. Just plug the cable directly to the HC port. Not using the hand controller gives you one less thing to worry about.
Posted 16 April 2021 - 03:16 PM
Posted 16 April 2021 - 03:28 PM
If it a prolific based cable its know to have issues like these. FTDI seems to be more reliable.
Where did you get the cable?
Also if the mini pc has a USB 2.0 port use it for the EQMOD cable. I have had issues with USB 3 and serial/usb convertors.
Posted 16 April 2021 - 03:35 PM
Posted 16 April 2021 - 04:18 PM
What is the Timeout value you have set in the EQMOD ASCOM Setup dialog? It should generally be at least 1000 and 2000 is better if you have a slightly underpowered MiniPC.
While you have the dialog open, also check the Retry Count (>2).
Posted 16 April 2021 - 04:39 PM
Posted 16 April 2021 - 04:55 PM
I understand. That is partly why I asked about checking the timeout and retry counts. When the system gets very busy with lots of USB traffic, it can cause delays in communicating with slower devices. Having a longer timeout interval as well as allowing more retries may help in communicating with the mount if that is the issue.
If the MiniPC has only a single root hub, all USB traffic must go through that path even if different ports are being used. It can become a bottleneck at times on some systems.
Edited by jdupton, 16 April 2021 - 04:56 PM.
- jonathan007 likes this