Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Testing the validity of a Com Port
Message
From
20/08/2008 12:37:40
 
 
To
20/08/2008 11:03:58
Timothy Bryan
Sharpline Consultants
Conroe, Texas, United States
General information
Forum:
ASP.NET
Category:
Coding, syntax and commands
Miscellaneous
Thread ID:
01340243
Message ID:
01340403
Views:
9
Hi,
>Maybe in this is my answer. My connection is via a third party product and not using the .NET SerialPort object. I suppose I could pre test the port by trying a SerialPort.Open().

Don't think that would help. As mentioned the SerialPort.Open() should succeed whether or not the device in question is connected.
You'd probably need to use the .NET serial port to do a bit more probing to determine if the device was available but, not knowing the device, I've no suggestions as to what might be appropriate. What's the device in question?

>Currently what is happening is a hang when trying to connect. If I unplug the device, unplug the usb cable (it is emulated) and then reconnect and make sure the device is on first, etc. etc. and then verify before I start the application I have a valid device then the connection is successful. I am looking for a way to programatically make sure so I don't get a hang.

>Tim
>
>
>>Hi,
>>
>>What do you mean by 'tries to connect'? The port is valid it should open OK whether or not a device is connected. AFAIK SerialPort.Open() throws an exception if the specified port is not valid.
>>Regards,
>>Viv
>>
>>>I have a windows app that connects to devices via a com port. (Actually I use a serial emulator but it shows up as com 5). If I don't have the device plugged in or turned on when the application starts and tries to connect the application just appears to hang. Is there a way to test if the com port is a valid port before attempting to connect?
>>>Thanks
>>>Tim
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform