Failed to open COM port on windows 7

[jadew]

When this happens, try the following:

1) close the app that has used the port
2) unplug the OLS
3) plug it back
4) unplug again
5) plug and start using it.

If it works, it means that either the port doesn't get gracefully closed or that it fails on the hardware side. I experienced this behavior when unplugging a device that I was connected to. Had to go trough this steps in order to be able to connect again.

[gotchalt]

Nope, doesn't help.
Only a system reboot solves the problem.

I think it's very sad for the OLS project but behaving that way, the tool is almost of no use!

[jadew]

I'm not very familiar with the hardware or the firmware, however, I would try a few things in the hope that it might shed some light on the issue:

1) connect and disconnect with putty (or any other serial client) several times, see if it stops working.
2) capture some data, close the program, open it again, capture, close, open it, capture close, etc (see if you get better results).
3) try some of the other clients and see if you get similar behavior.

[gotchalt]

And now...

tested it on some other machines, running different OS... same problem!

Using the original SUMP Client everything works - at least for the last 50 tries...
That's crap, the OLS-Client is much more handy.

Maybe I should try to reinstall my JAva!?

[jawi]

Hi, seems I missed this topic until now...

Sorry to hear that the client does not work properly for you. Am I right that the client no longer works after you've cancelled an ongoing acquisition (until you reboot your system)? In that case the bug is probably in the used serial library, which might already have been fixed in an upstream version.

Fortunately, I've got a Win7 64 machine at my disposal for some other testing tasks (I normally work on OSX), so I try to reproduce this myself, and see whether a new version of the serial library fixes the issue. Let me get back to you about this...

PS: it shouldn't be necessary to reinstall Java because of this...

[gotchalt]

Hi,
yes in fact. Cancelling a pending Capture seems to be the reason.

Update of JRE aswell as RXTX didn't help.

Quite desperate by now...

[jawi]

Don't despair, I'm working on it already :)

[Aeroengineer1]

I too am having this problem. I find that once it gets started, I cannot use even the original client, so I am not so sure that it is a client issue. I have found that it usually happens when I tell it to stop a capture. I could get it to work by switching to another USB port, but once that port gets an issue, then I am hosed My other USB ports are too far away to try to use to see if I get functionality back. I am using the USB port that is on the side of my Dell monitor. I have a PICKit also plugged in. I have gon into the device manager and deleted the device on the com port while it is plugged in, then unplug it and plug it back in and have it reinstall the driver. This did not work. I am going to try a reboot to see if it comes back. I am running Win 7-64 Pro.

Adam

[Aeroengineer1]

A restart allows me to use the device again in both clients.
OLS v1.01
OLS firmware is 3.07
Adam

[jadew]

Hi Aeroengineer1,

Could you please specify which is the other client you're having issues with?

Thanks

[Aeroengineer1]

It is the SUMP client. I do not remember which version.

Adam

[jadew]

Adam,

Would you mind trying it out with this client: viewtopic.php?f=57&t=4670

It's one that I wrote and I'd like to know if my client is susceptible to this issue as well.

Thank you

[Aeroengineer1]

No problem, I will give it a go. I will first attempt to get it to fail with one of the other clients. I have been avoiding using the stop capture button lately and it has not had the issue. After I get it to fail, I will switch to your client.

Adam

[jawi]

@Areoengineer1: are you using the latest version of OLS client from <http://ols.lxtreme.nl/>, or did you download the Windows-installer from GadgetFactory? In case of the latter, could you try the latest version of the OLS client to see whether that resolves your issue?

[Aeroengineer1]

I am running the latest release from the link that you had posted above. It is 9.6.1 if I remember correctly.

I am wondering if this has nothing to do with the Client, but with the fact that it is going through a USB hub. I will not have much time this weekend, but I will see if I can dig out a USB extension cable and go right into a USB port in the back of the computer and see if the behavior is the same. If it is different, then perhaps we can say that going through a hub is a probable cause.

Adam