usb cable faulty and exception error
han.k...@yahoo.co.uk
I received
the USB_focus yesterday. It worked fine
with the 8 volt power supply but not on USB power. I tested it on two computer but both
gave the same problem. After a move instruction the motor moved maybe a
fraction of a second or nothing at all and then the control program freezed. Using ASCOM loss of communication was reported.
After some investigating, I found that the supplied blue USB cable was faulty!. When I connected the same USB cable to a printer, Windows reported a problem with USB connection. Replacing the cable solved all
problems and the focuser works well. So this cable goes in the bin.
Only minor problem left is an exception error when I close the “USB_OpticalTelescopeController v0.55” program. It reports an exception error both in Win7 and win10. I also noticed it can’t write the .INI to a very long complicated path. The ASCOM driver works without any problem.
Here some images of my home made adapter and toothed belt coupling:
vin...@usb-foc.us
From: "han.kleijn via USB_Focus" <usb_...@googlegroups.com>
To: USB_Focus <usb_...@googlegroups.com>
Subject: usb cable faulty and exception error
---
Vous recevez ce message, car vous êtes abonné au groupe Google Groupes "USB_Focus".
Pour vous désabonner de ce groupe et ne plus recevoir d'e-mails le concernant, envoyez un e-mail à l'adresse usb_focus+...@googlegroups.com.
Pour obtenir davantage d'options, consultez la page https://groups.google.com/d/optout.
han.k...@yahoo.co.uk
The exception error only occurs if the program (USB_OpticalTelescopeController v0.55.exe program) is connected and the program is manually closed/stopped. I assume it is something in the closing down sequence of the COM port communication Attached some screen shots.
Han
han.k...@yahoo.co.uk
If the communication is stopped before closing the program then the error doesn't occur. So I assume to fix it, the software should stop communication earlier if the program is stopped. I do some programming myself and assume you should try to capture the communication exception or stop communicating on a close event of the main window.
Han
USB_Focus
Thank you for your help, I will do so.
If the communication is stopped before closing the program then the error doesn't occur. So I assume to fix it, the software should stop communication earlier if the program is stopped. I do some programming myself and assume you should try to capture the communication exception or stop communicating on a close event of the main window.
Han
--