USB to Serial adapter (Prolific) connected to Smart-UPS 1400 RM XL

[OVERKILL_apc]

I read through the other thread regarding the issues with the USB cables and the USB2.0/USB1.1 compatibility problems. There were a few posts in that thread where some people were having the same issue I'm having. And they were using a USB to RS232 adaptor with a Prolific chipset.

Server is running Windows Server 2008 x64. I've tried both the drivers that came with the adaptor, as well as the most recent ones from Prolific. And the issue persists.

Essentially:

The UPS talks to the computer without issue for somewhere in the neighbourhood of 24hrs. Around that time, it loses connectivity. A simple restart of the Agent service brings that connectivity back.

Is there a fix for this? it is a big PITA having to restart the service every morning.

[OVERKILL_apc]

Indeed, that is my concern. The newest version of the drivers from Prolific's website did not appear to help either.

[OVERKILL_apc]

The UPS is a SmartUPS 1400 XL rack-mount.
The cable being used with the adaptor is 940-0024.

[voidstar_apc]

>
The UPS talks to the computer without issue for somewhere in the neighbourhood of 24hrs. Around that time, it loses connectivity. A simple restart of the Agent service brings that connectivity back.

Is there a fix for this? it is a big PITA having to restart the service every morning.
>

It would be a bit gross but if you guys can't find a direct fix, you might try creating a batch file to [restart the service|http://technet.microsoft.com/en-us/library/cc736564%28WS.10%29.aspx] and then [schedule it to run|http://support.microsoft.com/kb/308569] every 12 hours or so.

[OVERKILL_apc]

Unfortunately, one of my biggest issues with having to restart the service is that I lose my power logs/graphs. Which I find useful to monitor the utility conditions at that particular office.

[OVERKILL_apc · Accepted solution]

Well the serial port on the server was disabled in the BIOS, and it is on the other side of the country. So not an easy thing to change. Hence the USB RS232 port.

This is the same problem as indicated by a few people in that other thread.