Hi, Anyone have any experience with these ??? http://cgi.ebay.com/UPS-1000VA-Brand-New_W0QQitemZ280141461506QQihZ018QQcategoryZ99265QQssPageNameZWDVWQQrdZ1QQcmdZViewItem Thanks, Tuc
Tuc at T-B-O-H.NET wrote:> Anyone have any experience with these ??? > > http://cgi.ebay.com/UPS-1000VA-Brand-New_W0QQitemZ280141461506QQihZ018QQcategoryZ99265QQssPageNameZWDVWQQrdZ1QQcmdZViewItemAccording to this website, it supports> # Interface 9Pin D-type Connector: > AC fault, battery low, Shutdown UPSThis looks like a contact closure interface, which would be supported through the genericups driver. Don't expect fancy features though, the above is all the information you'd get from it. Probably good enough for a desktop device, but for a server I would opt for something more sophisticated. Best regards, Arjen
On 9/19/07, Charles Lepple <clepple at gmail.com> wrote:> On 9/19/07, Tuc at T-B-O-H.NET <ml at t-b-o-h.net> wrote: > > I also wondered if for FreeBSD anyone > > knew of a "tcpdump" for serial communications. This way if it IS > > doing something never seen before, I can trap it for inclusion. > > ktrace and kdump will show you system calls (including read()s and > write()s on the serial port).I should clarify: these are for monitoring a local program on a *BSD box (similar to using strace on Linux/SysV). Doing some sort of man-in-the-middle monitoring is a hassle due to baud rates and everything. Also, if you want to watch the Windows program interact with the UPS, take a look at portmon from the Sysinternals collection (not sure where it went now that the author works for Microsoft or whatever). -- - Charles Lepple
Maybe Matching Threads
- Debugging problem AFTER the failure?
- Specs for Powercom Kingpro UPSes!
- Unable to set up a "serial-over-USB" UPS (APC BZ2200BI-BR)
- Cyberpower CP550SL/AE550 Serial
- Unable to detect an APC Smart protocol UPS. Windows. APC Smart protocol driver 3.04 (2.6.5-3723:3731M)