[Nut-upsuser] Powerbox PX20dsp
Anyone has any experience with a subj.? best regards, bbg ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] howto setup BNT-1500AP on gentoo
Did you set correct permissions on /dev/tts/0? If that device is owned by root, then your driver cannot write to or read from it. -- Peter Vitaly Oborsky wrote: Good afternoon. I try to put nut on gentoo. Has executed installation by a standard command emerge nut. All has passed successfully. I use UPS POWERCOM BNT-1500AP. It is connected to serial port 1, i.e. for my system it/dev/tts/0. In/etc/nut/ups.conf [powercom] driver = powercom port = /dev/tts/0 desc = PowerCom BNT-1500AP on IP-PBX modelname = BNT-1500AP linevoltage = 230 type = KIN1500AP also trying: [powercom] driver = powercom port = /dev/tts/0 desc = PowerCom BNT-1500AP on IP-PBX modelname = BNT-1500AP linevoltage = 230 type = Egys At start by a command/etc/init.d/upsdrv start gives out the following: * Starting UPS drivers ... Network UPS Tools - UPS driver controller 2.0.4 Network UPS Tools - PowerCom and similars protocol UPS driver $ Revision: 0.5 $ (2.0.4) data receiving error (-1 instead of 16 bytes) What correct parameters for BNT-1500AP? ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] howto setup BNT-1500AP on gentoo
Peter,
Vitaly sent me the strace output off-list, and it appears to be a timeout issue:
29723 open(/dev/ttyS0, O_RDWR|O_NONBLOCK|O_EXCL|O_NOCTTY) = 6
29723 flock(6, LOCK_EX|LOCK_NB) = 0
[...]
29723 write(6, \1, 1) = 1
29723 select(7, [6], NULL, NULL, {3, 0}) = 0 (Timeout)
29723 write(2, data receiving error (-1 instead..., 46) = 46
29723 select(9, [8], NULL, NULL, {2, 0}) = 0 (Timeout)
29723 write(6, \1, 1) = 1
29723 select(7, [6], NULL, NULL, {3, 0}) = 0 (Timeout)
29723 write(2, data receiving error (-1 instead..., 46) = 46
Vitaly: I'm guessing you tried both /dev/tts/0 and /dev/ttyS0?
On 12/13/06, Peter Selinger [EMAIL PROTECTED] wrote:
Did you set correct permissions on /dev/tts/0? If that device is owned
by root, then your driver cannot write to or read from it. -- Peter
Vitaly Oborsky wrote:
Good afternoon. I try to put nut on gentoo. Has executed installation
by a standard command emerge nut. All has passed successfully. I use
UPS POWERCOM BNT-1500AP. It is connected to serial port 1, i.e. for my
system it/dev/tts/0. In/etc/nut/ups.conf
[powercom]
driver = powercom
port = /dev/tts/0
desc = PowerCom BNT-1500AP on IP-PBX
modelname = BNT-1500AP
linevoltage = 230
type = KIN1500AP
also trying:
[powercom]
driver = powercom
port = /dev/tts/0
desc = PowerCom BNT-1500AP on IP-PBX
modelname = BNT-1500AP
linevoltage = 230
type = Egys
At start by a command/etc/init.d/upsdrv start gives out the following:
* Starting UPS drivers ...
Network UPS Tools - UPS driver controller 2.0.4
Network UPS Tools - PowerCom and similars protocol UPS driver $
Revision: 0.5 $ (2.0.4)
data receiving error (-1 instead of 16 bytes)
What correct parameters for BNT-1500AP?
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
--
- Charles Lepple
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] F6C1500-TW-RK
Greetings Jamie/Peter, I also have a F6C1500-TW-RK which I use with nut. However in my experiences the USB driver has been unstable to the point of avoidance. I have used the newhidups driver on 2 occasions on 2 different FreeBSD 5.5-stable machines and 2 different physical devices of this model. What happened was that the device detected, and showed initial output such as follows: battery.charge: 100 battery.charge.low: 30 battery.charge.warning: 30 battery.runtime: 120 battery.type: PbAc battery.voltage: 0.2 battery.voltage.nominal: 273 driver.name: newhidups driver.parameter.port: auto driver.version: 2.0.4 driver.version.data: Belkin HID 0.1 driver.version.internal: 0.28 input.frequency: 59.9 input.frequency.nominal: 60 input.transfer.high: 140 input.transfer.high.max: 144 input.transfer.high.min: 140 input.transfer.low: 88 input.transfer.low.max: 88 input.transfer.low.min: 84 input.voltage: 119.1 input.voltage.nominal: 120 output.frequency: 60.0 output.voltage: 119.6 ups.beeper.status: enabled ups.delay.restart: 0 ups.delay.shutdown: 0 ups.firmware: 1 ups.load: 19 ups.mfr: Belkin ups.model: unknown ups.power.nominal: 1500 ups.serial: ups.status: OL CHRG ups.test.result: No test initiated ups.type: offline The problem was that both times I tried to use this, the device simply powered off about 10-15 minutes after starting the NUT software, and without any warning or indication in the logs why it happened. The 'belkin' serial driver does also work, and does not experience this stability issue when I use it. The output with the 'belkin' driver contains much less information: battery.charge: 100 battery.temperature: 000 battery.voltage: 27.2 driver.name: belkin driver.parameter.port: /dev/cuaa1 driver.version: 2.0.4 driver.version.internal: 0.21 input.frequency: 59.9 input.transfer.high: 0.0 input.transfer.low: 0.0 input.voltage: 118.9 output.frequency: 59.9 output.voltage: 119.5 ups.firmware: 01 ups.load: 017 ups.mfr: BELKIN ups.model: F6C1500-TW-RK ups.status: OL ups.temperature: 000 - Evan [EMAIL PROTECTED] / systems admin @ www.probsd.net ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
