Problem when using a prolific USB to serail adapter.
-
Hello everybody, I have developped a Visual C++ application that drives a serial COM port (9600 8 N 1). When I use the PC's COM port to dialog with the hardware, the application works correctly; but when I connect the hardware to a USB port via a profilic USB to serial adapter the application shows a error message and closes abruptly. Does somebody encountered such a problem ? or any idea about how to solve or debug ? :confused: Thank you in advance, AG
-
Hello everybody, I have developped a Visual C++ application that drives a serial COM port (9600 8 N 1). When I use the PC's COM port to dialog with the hardware, the application works correctly; but when I connect the hardware to a USB port via a profilic USB to serial adapter the application shows a error message and closes abruptly. Does somebody encountered such a problem ? or any idea about how to solve or debug ? :confused: Thank you in advance, AG
-
It shows the windows error dialog and when I look the details I get the following information : EXE NAME="ERW.exe" FILTER="GRABMI_FILTER_PRIVACY" MATCHING_FILE NAME="ERW.exe" SIZE="454656" CHECKSUM="0xA7F4B92D" BIN_FILE_VERSION="1.4.5.0" BIN_PRODUCT_VERSION="1.4.5.0" PRODUCT_VERSION="1.4.5" FILE_DESCRIPTION="Programmeur ERW" COMPANY_NAME="ELA Innovation" PRODUCT_NAME="ELA Read Write" FILE_VERSION="1.4.5" ORIGINAL_FILENAME="ERW.exe" INTERNAL_NAME="ERW.exe" LEGAL_COPYRIGHT="(c) ELA Innovation. Tous droits réservés." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.4.5.0" UPTO_BIN_PRODUCT_VERSION="1.4.5.0" LINK_DATE="05/16/2006 14:07:44" UPTO_LINK_DATE="05/16/2006 14:07:44" VER_LANGUAGE="Français (France) [0x40c]" MATCHING_FILE NAME="Uninstall.exe" SIZE="35453" CHECKSUM="0x1CDEBCED" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="01/28/2003 14:21:01" UPTO_LINK_DATE="01/28/2003 14:21:01" EXE NAME="kernel32.dll" FILTER="GRABMI_FILTER_THISFILEONLY"> MATCHING_FILE NAME="kernel32.dll" SIZE="1048576" CHECKSUM="0x60165972" BIN_FILE_VERSION="5.1.2600.2180" BIN_PRODUCT_VERSION="5.1.2600.2180" PRODUCT_VERSION="5.1.2600.2180" FILE_DESCRIPTION="DLL du client API BASE Windows NT" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Système d'exploitation Microsoft® Windows®" FILE_VERSION="5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)" ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT="© Microsoft Corporation. Tous droits réservés." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x10626E" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="5.1.2600.2180" UPTO_BIN_PRODUCT_VERSION="5.1.2600.2180" LINK_DATE="08/04/2004 07:54:15" UPTO_LINK_DATE="08/04/2004 07:54:15" VER_LANGUAGE="Français (France) [0x40c]" I presume this information is not usefull !!! :~ -- modified at 11:01 Wednesday 19th July, 2006
-
It shows the windows error dialog and when I look the details I get the following information : EXE NAME="ERW.exe" FILTER="GRABMI_FILTER_PRIVACY" MATCHING_FILE NAME="ERW.exe" SIZE="454656" CHECKSUM="0xA7F4B92D" BIN_FILE_VERSION="1.4.5.0" BIN_PRODUCT_VERSION="1.4.5.0" PRODUCT_VERSION="1.4.5" FILE_DESCRIPTION="Programmeur ERW" COMPANY_NAME="ELA Innovation" PRODUCT_NAME="ELA Read Write" FILE_VERSION="1.4.5" ORIGINAL_FILENAME="ERW.exe" INTERNAL_NAME="ERW.exe" LEGAL_COPYRIGHT="(c) ELA Innovation. Tous droits réservés." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.4.5.0" UPTO_BIN_PRODUCT_VERSION="1.4.5.0" LINK_DATE="05/16/2006 14:07:44" UPTO_LINK_DATE="05/16/2006 14:07:44" VER_LANGUAGE="Français (France) [0x40c]" MATCHING_FILE NAME="Uninstall.exe" SIZE="35453" CHECKSUM="0x1CDEBCED" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="01/28/2003 14:21:01" UPTO_LINK_DATE="01/28/2003 14:21:01" EXE NAME="kernel32.dll" FILTER="GRABMI_FILTER_THISFILEONLY"> MATCHING_FILE NAME="kernel32.dll" SIZE="1048576" CHECKSUM="0x60165972" BIN_FILE_VERSION="5.1.2600.2180" BIN_PRODUCT_VERSION="5.1.2600.2180" PRODUCT_VERSION="5.1.2600.2180" FILE_DESCRIPTION="DLL du client API BASE Windows NT" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Système d'exploitation Microsoft® Windows®" FILE_VERSION="5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)" ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT="© Microsoft Corporation. Tous droits réservés." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x10626E" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="5.1.2600.2180" UPTO_BIN_PRODUCT_VERSION="5.1.2600.2180" LINK_DATE="08/04/2004 07:54:15" UPTO_LINK_DATE="08/04/2004 07:54:15" VER_LANGUAGE="Français (France) [0x40c]" I presume this information is not usefull !!! :~ -- modified at 11:01 Wednesday 19th July, 2006
:confused: Uuuh ?? Can you be more specific ?
algo_2112 wrote:
when I look the details
Where do you look at these details ?? And what is this information ? I suppose the problem is simply that you cannot open the COM port (because you gave the wrong port number for example) and that you have a NULL handler that you try to use. Did you use your debugger to see what's happening exactly ? This must be the first reflex to have ! Whenever you have a problem, use your debugger FIRST.
Cédric Moonen Software developer
Charting control -
:confused: Uuuh ?? Can you be more specific ?
algo_2112 wrote:
when I look the details
Where do you look at these details ?? And what is this information ? I suppose the problem is simply that you cannot open the COM port (because you gave the wrong port number for example) and that you have a NULL handler that you try to use. Did you use your debugger to see what's happening exactly ? This must be the first reflex to have ! Whenever you have a problem, use your debugger FIRST.
Cédric Moonen Software developer
Charting controlThe application works correctly for a while then it suddenly closes and shows the classical windows error dialog inviting you to send a repport. I can't debug because the application works correctly when I use the computer used for developping the application (where Visual Studio runs). The problem appears when I run the App on a laptop computer. I was thinking about timing problems. Because I don't use the RS232 control signals DTS,... -- modified at 11:48 Wednesday 19th July, 2006
-
The application works correctly for a while then it suddenly closes and shows the classical windows error dialog inviting you to send a repport. I can't debug because the application works correctly when I use the computer used for developping the application (where Visual Studio runs). The problem appears when I run the App on a laptop computer. I was thinking about timing problems. Because I don't use the RS232 control signals DTS,... -- modified at 11:48 Wednesday 19th July, 2006
I heard from a developer of such devices (USB to Serial) that they were (1) very difficult to do and (2) most of them on the market don't work all that well. Take this for what it's worth, but you may be hitting limitations of the device. Have you considered periodically closing and reopening the connection? This may delay the issue... earl