Re: [Nut-upsuser] safenet on debian etch
Run the driver in debug mode, I already suggested this in the previous message. The driver will be more verbose about what the cause is that it won't run. how do I run it in debug mode? Run (as root) path to driver/safenet -a everpower1000 -D I think that the problem is that the device does not support the safenet protocol. Maybe, maybe not. when I cat /dev/ttyS1, I get no output at all. is that normal for safenet? Yes. The device will only answer when a query or a command is sent. Regards, Arjen PS Keep the mailinglist CC-ed. I will not reply to private messages. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] Problems with config of newhidups
Hi all, I just downloaded, built and installed nut-2.0.4-pre2. I have an APC Smart ups 3000 connected via a usb cable. I have compiled and installed the usb drivers. I installed the libhidups and libhid.usermap per the README. I have the following ups.conf: [APC-3000-ups] driver = newhidups port = auto desc = APC smart 3000 When I try to start the driver I get the following output: (pocono pts19) # ./upsdrvctl -v start Network UPS Tools - UPS driver controller 2.0.4-pre2 exec: /usr/local/ups/bin/newhidups -a APC-3000-ups Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.4-pre2) No matching USB/HID UPS found Driver failed to start (exit status=1) (pocono pts19) # /proc/bus/usb/devices shows the following: T: Bus=02 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=1.5 MxCh= 0 D: Ver= 1.10 Cls=00(ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=051d ProdID=0002 Rev= 0.06 S: Manufacturer=American Power Conversion S: Product=Smart-UPS 3000 RM FW:666.6.D USB FW:2.4 S: SerialNumber=JS0438010331 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 30mA I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=00 Prot=00 Driver=usbhid E: Ad=81(I) Atr=03(Int.) MxPS= 6 Ivl=100ms Can anyone give me an idea how to get this working? The machine is RHEL4 x86_64. Regards, Tom ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] safenet on debian etch
Here is my output: # /lib/nut/safenet -a everpower1000 -D Network UPS Tools - Generic SafeNet UPS driver 0.03 (2.0.2) debug level is '5' C : ZCADLIOPERJD S : [empty] C : ZCADLIOPERJD S : [empty] C : ZCADLIOPERJD S : [empty] C : ZCADLIOPERJD S : [empty] Communications with UPS lost: Status read failed C : ZCADLIOPERJD S : [empty] Communications with UPS lost: Status read failed SafeNet protocol compatible UPS not found on /dev/ttyS1 Arjen de Korte wrote: Run the driver in debug mode, I already suggested this in the previous message. The driver will be more verbose about what the cause is that it won't run. how do I run it in debug mode? Run (as root) path to driver/safenet -a everpower1000 -D I think that the problem is that the device does not support the safenet protocol. Maybe, maybe not. when I cat /dev/ttyS1, I get no output at all. is that normal for safenet? Yes. The device will only answer when a query or a command is sent. Regards, Arjen PS Keep the mailinglist CC-ed. I will not reply to private messages. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Problems with config of newhidups
On 7/25/06, Tom Diehl [EMAIL PROTECTED] wrote: I installed the libhidups and libhid.usermap per the README. Unfortunately, the libhid.usermap file doesn't change permissions on all systems (particularly those that use udev). What version of Fedora Core is RHEL4 most similar to? -- - Charles Lepple ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] safenet on debian etch
Omry Yadan wrote: Here is my output: # /lib/nut/safenet -a everpower1000 -D Network UPS Tools - Generic SafeNet UPS driver 0.03 (2.0.2) debug level is '5' C : ZCADLIOPERJD S : [empty] C : ZCADLIOPERJD S : [empty] C : ZCADLIOPERJD S : [empty] C : ZCADLIOPERJD S : [empty] Communications with UPS lost: Status read failed C : ZCADLIOPERJD S : [empty] Communications with UPS lost: Status read failed SafeNet protocol compatible UPS not found on /dev/ttyS1 Either the UPS is not connected to /dev/ttyS1 (version 0.03 of the driver does not include hardware detection, which was added in 0.04) or your version of the Everpower 1000 UPS is not supported. Regards, Arjen ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] 3110us support?
is there 3110us support yet? ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Problems with config of newhidups
On 07/25/2006 09:31 PM, Charles Lepple wrote: On 7/25/06, Tom Diehl [EMAIL PROTECTED] wrote: I installed the libhidups and libhid.usermap per the README. Unfortunately, the libhid.usermap file doesn't change permissions on all systems (particularly those that use udev). What version of Fedora Core is RHEL4 most similar to? rhel 4 is a strange hybrid placed between fc2 and fc3 but with bits from fc4. an upgrade from fc3 to centos 4.3 (rhel 4 U3 clone) left the kernel and glibc from fc3, as they were seen as being newer ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] 3110us support?
Hi tis 2006-07-25 klockan 13:49 -0500 skrev John H.: is there 3110us support yet? No, not for the usb. But it does not do any more on usb then on the generic contact driver. There is no voltage or current or battery data, just indication that it is OL or OB. To support 3110 and the 5115 on usb the driver need a ugly hack. They don't conform to the bcmxcp standard. (The strange thing is that the 5115 is working Ok on the serial line, and follows the standard.) On an 'ID_BLOCK_REQUEST' it sends a packet that have number 0x01 this indicate that it should be followed by a new packet 0x02 or 0x82 if it is the last. This does not happen. Even the windows driver reset the pipe at this and also have problem to read the 'STATUS_REQUEST' that follows. The usb implementation is an early one, done by Powercom. And if you look at http://www.powerware.com/end_of_life/products.asp you see that 3110 is out of production and is replaced by the 3105. And that one runs great on the bcmxcp_usb driver. So i would not break the driver to support it on usb when it is supported by the generic driver. But if you can send me some good SnoopyPro log's on the traffic from the windows driver i would dig some deeper into the problem. Regards Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
