Re: [Nut-upsuser] Sweex 1000VA UPS

[Arjen de Korte]

 Disconnecting a UPS from a live server and testing it at a separate
 workstation is a MUST if you're not absolutely sure the configuration is
 correct. I would never use an UPS on a production system without double
 checking that monitoring works. Otherwise your investment gives you a
 false sense of security.

[...]

 But anyway, I will do it in a free day next week and test things out on a
 spare proliant server I 'm lucky to have right now.

While you're at it, try the UPS on a Windows machine with the bundled
software to exclude that the UPS or serial cable are the culprits. It's a
long shot, but you wouldn't be the first to find out that there is a
problem in that area. It also guarantees that the UPS is indeed compatible
to the UPSmart software.

[...]

 I definately will complain to sweex!  I will ask them to send me the
 manage software for linux. As they claim on their website it's supported.

Don't hold your breath. And chances are that they direct you to a shoddy
binary only package for RedHat 6.2 or some other ancient Linux version,
which isn't very useful anymore.

 If it should 'just work' and you don't find enjoyment in trying to make
 it work, do yourself a favor and indeed swap it for one that is better
 supported by the manufacturer (MGE indeed comes to mind, since they
 officially sponsor NUT).
 Don't get me wrong. I enjoy searching for things and trying to make things
 work the right way.
 I would never use opensource if I didn't enjoy this, would I?
 But this time it's just to critical and I'm to much in a rush to get this
 working.

That's exactly what I meant. Personally I enjoyed reverse engineering the
SafeNet protocol and writing a driver for it. And I don't feel too bad
about Sweex providing erronous information on their website and not
willing to provide the details on the device needed to write a driver.
However, as a professional I would be outraged if I had to spend hours and
hours on a €75 UPS trying to make it work because I need it so badly. In
that case, you'd better invest a few euros more and buy a device that is
really supported by the manufacturer (MGE for instance).

[...]

 That version is already quite old, we're at 2.0.4 already, with 2.0.5
 lurking just around the corner.
 Yes I know, but I tried to keep the system as much as possible with the
 stable brand.
 But If it wouls solve my problems I could of course grab nut from unstable
 or testing.

Don't bother. Although there were some changes in genericups, the're not
major and unlikely to be the root cause of your problems.

If you're willing to try a few more things, comment out the part in the
NUT startup script where 'upsmon' is started/stopped and fire it up. With
'upsc [EMAIL PROTECTED]' you should be able to see the status of the UPS,
without the risk of shutting down your system when things are not
configured properly. Try at least /dev/ttyS[0-3] with the UPS in different
serial ports on your server. Remember to stop the script before modifying
and starting it again. Good luck!

Kind regards,
Arjen


___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser

[Nut-upsuser] Elsist Lily 1200 VA

[Federico Granata]

Hi,
I have the UPS in subject, it's possible control it with nut ?

Sorry for my poor english.

___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser

[Nut-upsuser] Help with newhidups subdriver for Dynex UPS

[M.A.E. Hanson]

Hello everyone!
 If this message was posted twice, my apologies.  I'm having issues with my 
webmail today...

I am using the testing version of NUT from SVN at changeset 582.  I have 
successfully created a stub for newhidups driver for my Dynex DX-800U UPS, but 
I am completely lost on the customization of it.  I've followed the 
hid-subdrivers.txt instructions and I understand I need to map all the 
unmapped.* lines of my dynex-hid.c to NUT functions.  However, I can't make 
heads or tails of what I'm supposed to change.  Can someone take some time to 
help a struggling noob?  Here's some info I hope helps:

# /usr/src/nut-testing# pico /usr/local/ups/etc/ups.conf

[mythbox]
driver = newhidups
port = /dev/usb/hiddev0
desc = Living Room

EOF

/usr/src/nut-testing# drivers/newhidups -DD -u root /dev/usb/hiddev0

debug level is '2'
Checking device (/) (005/001)
- VendorID: 
- ProductID: 
- Manufacturer: Linux 2.6.15-chw-2 ehci_hcd
- Product: EHCI Host Controller
- Serial Number: :00:1d.7
- Bus: 005
Trying to match device
Device does not match - skipping
Checking device (/) (004/001)
- VendorID: 
- ProductID: 
- Manufacturer: Linux 2.6.15-chw-2 uhci_hcd
- Product: UHCI Host Controller
- Serial Number: :00:1d.3
- Bus: 004
Trying to match device
Device does not match - skipping
Checking device (/) (003/001)
- VendorID: 
- ProductID: 
- Manufacturer: Linux 2.6.15-chw-2 uhci_hcd
- Product: UHCI Host Controller
- Serial Number: :00:1d.2
- Bus: 003
Trying to match device
Device does not match - skipping
Checking device (/) (002/001)
- VendorID: 
- ProductID: 
- Manufacturer: Linux 2.6.15-chw-2 uhci_hcd
- Product: UHCI Host Controller
- Serial Number: :00:1d.1
- Bus: 002
Trying to match device
Device does not match - skipping
Checking device (0764/0501) (001/003)
- VendorID: 0764
- ProductID: 0501
- Manufacturer: CPS
- Product: DX-800U  
- Serial Number: unknown
- Bus: 001
Trying to match device
Device matches
HID descriptor retrieved (Reportlen = 374)
Report descriptor retrieved (Reportlen = 374)
Found HID device
Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.1.0)

Report Descriptor size = 374
Detected a UPS: CPS/DX-800U  
Using subdriver: APC/CyberPower HID 0.9
Path: UPS.PowerSummary.iProduct, Type: Feature, Value: 1.00
Path: UPS.PowerSummary.iSerialNumber, Type: Feature, Value: 2.00
Path: UPS.PowerSummary.iDeviceChemistry, Type: Feature, Value: 4.00
Path: UPS.PowerSummary.iOEMInformation, Type: Feature, Value: 3.00
Path: UPS.PowerSummary.Rechargeable, Type: Feature, Value: 1.00
Path: UPS.PowerSummary.CapacityMode, Type: Feature, Value: 2.00
Path: UPS.PowerSummary.DesignCapacity, Type: Feature, Value: 100.00
Path: UPS.PowerSummary.CapacityGranularity1, Type: Feature, Value: 5.00
Path: UPS.PowerSummary.CapacityGranularity2, Type: Feature, Value: 10.00
Path: UPS.PowerSummary.WarningCapacityLimit, Type: Feature, Value: 20.00
Path: UPS.PowerSummary.RemainingCapacityLimit, Type: Feature, Value: 10.00
Path: UPS.PowerSummary.FullChargeCapacity, Type: Feature, Value: 100.00
Path: UPS.PowerSummary.RemainingCapacity, Type: Input, Value: 120.00
Path: UPS.PowerSummary.RemainingCapacity, Type: Feature, Value: 120.00
Path: UPS.PowerSummary.RunTimeToEmpty, Type: Input, Value: 240.00
Path: UPS.PowerSummary.RunTimeToEmpty, Type: Feature, Value: 240.00
Path: UPS.PowerSummary.RemainingTimeLimit, Type: Input, Value: 300.00
Path: UPS.PowerSummary.RemainingTimeLimit, Type: Feature, Value: 300.00
Path: UPS.PowerSummary.ConfigVoltage, Type: Feature, Value: 12.00
Path: UPS.PowerSummary.Voltage, Type: Feature, Value: 21.21
Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Input, Value: 1.00
Path: UPS.PowerSummary.PresentStatus.Charging, Type: Input, Value: 0.00
Path: UPS.PowerSummary.PresentStatus.Discharging, Type: Input, Value: 0.00
Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type: Input, 
Value: 1.00
Path: UPS.PowerSummary.PresentStatus.FullyCharged, Type: Input, Value: 1.00
Path: UPS.PowerSummary.PresentStatus.RemainingTimeLimitExpired, Type: Input, 
Value: 1.00
Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Feature, Value: 1.00
Path: UPS.PowerSummary.PresentStatus.Charging, Type: Feature, Value: 0.00
Path: UPS.PowerSummary.PresentStatus.Discharging, Type: Feature, Value: 0.00
Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type: 
Feature, Value: 1.00
Path: UPS.PowerSummary.PresentStatus.FullyCharged, Type: Feature, Value: 
1.00
Path: UPS.PowerSummary.PresentStatus.RemainingTimeLimitExpired, Type: Feature, 
Value: 1.00
Path: UPS.PowerSummary.PresentStatus., Type: Input
Path: UPS.PowerSummary.PresentStatus., Type: Feature
Path: UPS.PowerSummary.AudibleAlarmControl, Type: Feature, Value: 2.00
Path: