Re: [Nut-upsuser] APC Smart-UPS 1000
On 08/02/2011 14:55, Arjen de Korte wrote:
{ shutdown.return, 0, 0, UPS.Output.APCDelayBeforeReboot, NULL,
1, HU_TYPE_CMD, NULL },
Yes, that does the trick!
# clients/upscmd -u apcmon -p pass123 apc1500 shutdown.return
has the desired effect.
Would you like me to provide any more output?
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] APC Smart-UPS 1000
Citeren Kevin bakd...@gmail.com: Yes, that does the trick! # clients/upscmd -u apcmon -p pass123 apc1500 shutdown.return has the desired effect. Good. I assume you tried this on the CS-500, right? Do you have any idea how long the delay is before the device actually shuts down? Would you like me to provide any more output? It would be nice to know under what conditions you tested this command. We would like to see what happens both with and without mains present at the time of running this command. I both work as expected, we may have found a workable solution. I do have to check the report descriptors of some other APC devices, to check if we're not shooting ourselves in the foot by adding this (to see if there may be conflicts with other known devices). Best regards, Arjen -- Please keep list traffic on the list (off-list replies will be rejected) ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] APC Smart-UPS 1000
On 08/02/2011 16:09, Kevin wrote: The bad news is that the # usbhid-ups -a apc1500 -k -DDD command doesn't work Cancel that. I was using the wrong path. It does work fine. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] APC Smart-UPS 1000
On 08/02/2011 15:50, Arjen de Korte wrote: Do you have any idea how long the delay is before the device actually shuts down? *Further testing:* When the command is issued On power: Switches immediately to battery Waits 60 seconds Sleeps for 2 seconds, switches output power off Restarts On battery: Waits 60 seconds Sleeps When power returns, restarts. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] APC Smart-UPS 1000
Citeren Kevin bakd...@gmail.com: On power: Switches immediately to battery Waits 60 seconds Sleeps for 2 seconds, switches output power off Restarts Although it is a bit weird that the device switches to battery, this doesn't really harm. We know such behavior from older devices with 'dumb' contact closure serial interfaces, which can only be shutdown when running on battery. On battery: Waits 60 seconds Sleeps When power returns, restarts. That's good to know. It looks like we found the correct mapping. If this doesn't conflict with known report descriptors, I'll add this to the development version later today. Best regards, Arjen -- Please keep list traffic on the list (off-list replies will be rejected) ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] APC Smart-UPS 1000
On 08/02/2011 16:48, Arjen de Korte wrote:
That's good to know. It looks like we found the correct mapping. If
this doesn't conflict with known report descriptors, I'll add this to
the development version later today.
For info, I added this line:
{ shutdown.stop, 0, 0,
UPS.APCGeneralCollection.APCDelayBeforeShutdown, NULL, -1,
HU_TYPE_CMD, NULL },
{ shutdown.reboot, 0, 0,
UPS.APCGeneralCollection.APCDelayBeforeReboot, NULL, 10,
HU_TYPE_CMD, NULL },
* { shutdown.return, 0, 0, UPS.Output.APCDelayBeforeReboot, NULL,
1, HU_TYPE_CMD, NULL },*
{ beeper.on, 0, 0, UPS.PowerSummary.AudibleAlarmControl, NULL,
2, HU_TYPE_CMD, NULL },
into the version 2.4.3 apc-hid.c on the other server and the CS 500 on
that is working fine too now.
Thanks for all your help.
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] Plexus 800VA UPS on ReadyNAS Duo
Hi I Bought a cheap Plexus 800VA UPS from ebuyer : http://www.ebuyer.com/product/240319 to use with my Netgear ReadyNAS duo. Initial version of NUT was very old and NAS didn't detect it although in the NAS log it said UPS Disconnected. Syslog did send the following : Jan 25 12:46:36 nas-27lfc kernel: usb 1-1: new low speed USB device using uhci_hcd and address 2 Jan 25 12:46:37 nas-27lfc kernel: usb 1-1: configuration #1 chosen from 1 choice Jan 25 12:46:39 nas-27lfc kernel: usbcore: registered new driver hiddev Jan 25 12:46:39 nas-27lfc kernel: hiddev96: USB HID v1.11 Device [ATCL FOR UPS ATCL FOR UPS] on usb-:00: 17.0-1 Jan 25 12:46:39 nas-27lfc kernel: usbcore: registered new driver usbhid Jan 25 12:46:39 nas-27lfc kernel: drivers/usb/input/hid-core.c: v2.6:USB HID core driver Installed 2.4.1 using apt and installed in place of initial version Found various web documents detailing that blazer_usb would probably be the driver to use. using usb.conf : [UPS] driver = blazer_usb port = auto and running the driver in debug mode gives the following : nas:/etc/nut# /lib/nut/blazer_usb -a UPS -u root -DDD Network UPS Tools - Megatec/Q1 protocol USB driver 0.03 (2.4.1) debug level is '3' Checking device (/) (003/001) - VendorID: - ProductID: - Manufacturer: Linux 2.6.17.14ReadyNAS ehci_hcd - Product: EHCI Host Controller - Serial Number: :00:17.2 - Bus: 003 Trying to match device Device does not match - skipping Checking device (/) (002/001) - VendorID: - ProductID: - Manufacturer: Linux 2.6.17.14ReadyNAS uhci_hcd - Product: UHCI Host Controller - Serial Number: :00:17.1 - Bus: 002 Trying to match device Device does not match - skipping Checking device (0001/) (001/003) - VendorID: 0001 - ProductID: - Manufacturer: ATCL FOR UPS - Product: ATCL FOR UPS - Serial Number: ATCL FOR UPS - Bus: 001 Trying to match device Device matches failed to claim USB device: could not claim interface 0: Device or resource busy detached kernel driver from USB device... Trying megatec protocol... send: Q1 read: error sending control message: Broken pipe blazer_status: short reply Status read 1 failed send: Q1 read: error sending control message: Broken pipe blazer_status: short reply Status read 2 failed send: Q1 read: error sending control message: Broken pipe blazer_status: short reply Status read 3 failed Trying mustek protocol... send: QS read: QS blazer_status: short reply Status read 1 failed send: QS read: QS blazer_status: short reply Status read 2 failed send: QS read: QS blazer_status: short reply Status read 3 failed Trying megatec/old protocol... send: D read: D blazer_status: short reply Status read 1 failed send: D read: D blazer_status: short reply Status read 2 failed send: D read: D blazer_status: short reply Status read 3 failed No supported UPS detected lsusb gives : nas:/etc/nut# lsusb Bus 003 Device 001: ID : Bus 002 Device 001: ID : Bus 001 Device 003: ID 0001: Fry's Electronics Bus 001 Device 001: ID : I also tried the usbhid-ups driver in explore mode as some people seemed to think that may work [UPS] driver = usbhid-ups vendorid = 0001 productid = desc = Plexus 800VA USB port = auto explore nas:/etc/nut# /lib/nut/usbhid-ups -a UPS -u root -DDD Network UPS Tools - Generic HID driver 0.34 (2.4.1) USB communication driver 0.31 debug level is '3' upsdrv_initups... Checking device (/) (003/001) - VendorID: - ProductID: - Manufacturer: Linux 2.6.17.14ReadyNAS ehci_hcd - Product: EHCI Host Controller - Serial Number: :00:17.2 - Bus: 003 Trying to match device Device does not match - skipping Checking device (/) (002/001) - VendorID: - ProductID: - Manufacturer: Linux 2.6.17.14ReadyNAS uhci_hcd - Product: UHCI Host Controller - Serial Number: :00:17.1 - Bus: 002 Trying to match device Device does not match - skipping Checking device (0001/) (001/003) - VendorID: 0001 - ProductID: - Manufacturer: ATCL FOR UPS - Product: ATCL FOR UPS - Serial Number: ATCL FOR UPS - Bus: 001 Trying to match device Device matches HID descriptor, method 1: (9 bytes) = 09 21 11 01 00 01 22 20 00 HID descriptor, method 2: (9 bytes) = 09 21 11 01 00 01 22 20 00 HID descriptor length 32 Report Descriptor size = 32 Report Descriptor: (32 bytes) = 06 a0 ff 09 01 a1 01 09 03 15 00 25 01 75 08 95 08 81 02 09 04 15 00 25 01 75 08 95 08 91 02 c0 Using subdriver: EXPLORE HID 0.1 Can't retrieve Report 0: Broken pipe Path: ffa1.ffa3, Type: Input, ReportID: 0x00, Offset: 0, Size: 8 Can't retrieve Report 0: Broken pipe Path: ffa1.ffa4, Type: Output, ReportID: 0x00, Offset: 0, Size: 8 Report descriptor retrieved (Reportlen = 32) Found HID device Detected a UPS: ATCL FOR UPS/ATCL FOR UPS upsdrv_initinfo... upsdrv_updateinfo... file_report_buffer: expected 0 bytes, but got 128! Report[err]: (128 bytes) = 01 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 01 00
Re: [Nut-upsuser] Plexus 800VA UPS on ReadyNAS Duo
Citeren Mike Barber badpa...@googlemail.com: Installed 2.4.1 using apt and installed in place of initial version Found various web documents detailing that blazer_usb would probably be the driver to use. using usb.conf : [UPS] driver = blazer_usb port = auto and running the driver in debug mode gives the following : [...] Checking device (0001/) (001/003) - VendorID: 0001 - ProductID: - Manufacturer: ATCL FOR UPS - Product: ATCL FOR UPS - Serial Number: ATCL FOR UPS The VendorID / ProductID combination is bogus. The manufacturer of the UPS was too cheap to apply for a real USB ID and made one up. This means that this will give us no clue how to communicate with this device based on this information. A few years ago we ran into this combination for the first time and at that time we found out how to talk to that particular device. However, this doesn't mean that yours will work in the same way (it may be something completely different, there is no way to tell). There is a very small chance that one of the other subdrivers in blazer_usb is able to talk to device. You'll have to help finding it by specifying 'vendorid', 'productid' and 'subdriver' in ups.conf. See 'man 8 blazer' for more information. If this also fails to detect your UPS you're basically out of luck. Unless *you* can provide us with the protocol this device uses (ask the vendor, manufacturer, reverse engineer it, whatever), we can't support it in NUT. using Blazer_usb on 2.6 gives virtually the same output as 2.4.1 You'll definitely need to use this one for the above to have any chance of success. Good luck. Best regards, Arjen -- Please keep list traffic on the list (off-list replies will be rejected) ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] hardware compatibility list
Arjen de Korte nut+us...@de-korte.org va escriure: Citeren Ernest Sales ersa...@gmail.com: I would like to report a working device to add to the hardware compatibility list, but cannot find a way on the website. Would this list be OK for that purpose? Sure. Please list the output of 'upsc' as well as whether or not you tested the shutdown function of the UPS. This is a low-end UPS sold in Spain under the IPAR brand, Mini Energy series, model ME 800. It apparently works well with the megatec_usb driver. Tested on power failure, after exhausting batteries the system is gracefully shut down. upsc output: battery.charge: 100.0 battery.voltage: 13.80 battery.voltage.nominal: 12.0 device.mfr: device.model: TR00061J device.serial: unknown device.type: ups driver.name: megatec_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.4.3 driver.version.internal: 1.6 input.frequency: 50.0 input.frequency.nominal: 50.0 input.voltage: 204.6 input.voltage.fault: 140.0 input.voltage.maximum: 207.9 input.voltage.minimum: 201.2 input.voltage.nominal: 220.0 output.voltage: 202.3 ups.beeper.status: enabled ups.delay.shutdown: 0 ups.delay.start: 2 ups.load: 19.0 ups.mfr: ups.model: TR00061J ups.serial: unknown ups.status: OL ups.temperature: 30.0 ups.type: standby N.B.: the blazer_usb driver recognized the device, but logs showed connection loss about every minute, so I didn't do further trying. Best regards, Ernest ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
