Serial COM ports Don't Always Communicate

[Guest]

I'm operating XP, SP2; Gateway 400SD; 2.5GHz, 512 RAM, 55GB HD w/ 35 GB free.

I have a weather base station which connects to my pc (and either of two
software applications) via a serial-to-USB converter. Everything was working
fine, as long as I had the COM port # synched up with the software(s). Last
week, after a troublesome install of an external USB hard drive, the
software(s) no longer received data from the base station. I also tried a
different converter cable; uninstalled and reinstalled the software(s);
uninstalled and reinstalled the Ser2USB driver(s); shut off Norton IS;
HotSynched my PDA with both cables successfully; and finally, downloaded a
serial port monitor trialware. From that, I learned that the software is
trying to receive data packets, but it keeps: opening COM port for software,
reading, writing, reading (all apparently nothing), and closing COM port, all
in about 10 second segments, over and over and over.
I've worked with the author of the software and the User Group board for
possible solutions there, but no solution. In my mind, everything points to a
system setting of my PC regarding the COM ports.
Why can't it take the final step and grab the data? Is there some setting
that the hard drive install may have changed that I'm missing?

 

[DanS]

I'm operating XP, SP2; Gateway 400SD; 2.5GHz, 512 RAM, 55GB HD w/ 35
GB free.

I have a weather base station which connects to my pc (and either of
two software applications) via a serial-to-USB converter. Everything
was working fine, as long as I had the COM port # synched up with the
software(s). Last week, after a troublesome install of an external USB
hard drive, the software(s) no longer received data from the base
station. I also tried a different converter cable; uninstalled and
reinstalled the software(s); uninstalled and reinstalled the Ser2USB
driver(s); shut off Norton IS; HotSynched my PDA with both cables
successfully; and finally, downloaded a serial port monitor trialware.
From that, I learned that the software is trying to receive data
packets, but it keeps: opening COM port for software, reading,
writing, reading (all apparently nothing), and closing COM port, all
in about 10 second segments, over and over and over.
I've worked with the author of the software and the User Group board
for possible solutions there, but no solution. In my mind, everything
points to a system setting of my PC regarding the COM ports.
Why can't it take the final step and grab the data? Is there some
setting that the hard drive install may have changed that I'm missing?

Simple. USB-to-RS-232 converters suck the big wazoo.

If you're apt to do serial RS232 comms, get a 'real' PCI RS232 Comm port
card. Something like this...$15 w/free shipping

http://www.pcimicro.com/.sc/ms/dd/Controller Cards--Serial Port%
20Adapter/571/House%20Brand%20Dual%209%20Pin%20Serial%20PCI%20Card%
20Retail%20Box

 

[Guest]

That's an interesting solution, except I only have one card slot, which is
occupied by my wireless card. So if I remove it to keep my weather station
running, I have no network.
The question remains, since it was working just fine, what caused it to
suddenly quit communicating with the weather applications, but HotSync for my
Palm VII works just fine?

 

[DanS]

That's an interesting solution, except I only have one card slot,
which is occupied by my wireless card. So if I remove it to keep my
weather station running, I have no network.
The question remains, since it was working just fine, what caused it
to suddenly quit communicating with the weather applications, but
HotSync for my Palm VII works just fine?

:

What caused it to stop working was the failed attempt at the USB drive
installation.

I missed the part in the original post about it working successfully with
your PDA.

Did you try a system restore ?

 

[Guest]

Thanks. Yes, after a few days I thought of that, but, even though the
calendar showed restore points for 4/1 and 2 [HD install was 4/3 AM], it
wouldn't allow me to do it, and the next restore point was 4/3 PM.

 

[Guest]

Since no one has come up with any thoughts on this, my last move is to send
the base station in for testing.
My assumption is that, since the communication through the Ser-2-USB cables,
and the data to be displayed in the 2 different software applications is
dependent on data provided by the base station device, maybe the base station
device is defective to begin with.

Thanks. Yes, after a few days I thought of that, but, even though the
calendar showed restore points for 4/1 and 2 [HD install was 4/3 AM], it
wouldn't allow me to do it, and the next restore point was 4/3 PM.

What caused it to stop working was the failed attempt at the USB drive
installation.

I missed the part in the original post about it working successfully with
your PDA.

Did you try a system restore ?

 

[DanS]

Since no one has come up with any thoughts on this, my last move is to
send the base station in for testing.
My assumption is that, since the communication through the Ser-2-USB
cables, and the data to be displayed in the 2 different software
applications is dependent on data provided by the base station device,
maybe the base station device is defective to begin with.

:

Had you contacted the device manufacturer or looked for support on their
website ?

Before I was to send the device back, I would try it on a computer with a
REAL serial port first, a friends or perhaps if you have another PC.

Just as an example, the company I work for hired an outside firm to do
some embedded programming, basically because I didn't have the time to do
it. The embedded device is programmed with a serial port. The gentleman
that was doing the work called me because he was having trouble getting
the module to juice up with the code.

After being on the phone with him for 5 minutes, he revealed that he was
using a USB to serial converter to do the programming, AND that it seemed
to work fine with another serial device.

Also, the programming environment for the device has an option to check
if you are using one of these converters. No matter what was tried, the
module would not program through the converter.

I left it like that, and the next day he called to let me know his first
run at the code was done and he'd be e-mailing to me shortly. When I
asked about the programming issue, he said he tried for another 10 or 15
minutes after I got off the phone, then decided to move to a workstation
with a 'real' serial port and everything worked, right off the bat with
no problems what-so-ever.

So in regards to your particular situation, I still firmly believe that
the failed installation attempt of the external USB harddrive caused SOME
issue with the USB port drivers and/or converter drivers and it is a
complete software problem.

I will change my mind when the device is tested with a true RS232 serial
port on a different PC and still shows to be faulty.

Just my 2¢.

Regards,

DanS

 

[Guest]

I ended up loading the application and hooking up the base station to my old
IBM 360 (aka "boat anchor") and connected via the "real" serial port it had.
Still didn't work.
Packed the unit and all cables up and sent back to the vendor.
As it turns out, the problem was that their RJ11-to-db9 serial cable was
defective. Apparently a loose/bad connection, which explains why it initially
worked, then worked intermittently, then not at all.
They (vendor) replaced the cable, and everything is working perfectly.
Thanks for you help and thoughts!

 

[DanS]

I ended up loading the application and hooking up the base station to
my old IBM 360 (aka "boat anchor") and connected via the "real" serial
port it had. Still didn't work.
Packed the unit and all cables up and sent back to the vendor.
As it turns out, the problem was that their RJ11-to-db9 serial cable
was defective. Apparently a loose/bad connection, which explains why
it initially worked, then worked intermittently, then not at all.
They (vendor) replaced the cable, and everything is working perfectly.
Thanks for you help and thoughts!

:

Thank's for checking in !!!

I didn't review the thread, but I don't think anyone even asked about the
cable. I should have, as when I'm supporting our customers that is usually
one of the first questions.

DOH!!!


DanS