Re: [Nut-upsuser] Network UPS Tools version 2.0.5 released

2007-01-29 Thread Arjen de Korte
I guess. You'll *have* to connect a UPS, otherwise there is nothing to verify. We already know the genericups driver works with other UPS'es, so there is no need to check that. You need to check if it works with *your* UPS. I have a UPS connected, I meant running the driver manually

Re: [Nut-upsuser] no longer stale when disconnected with 2.0.5

2007-01-29 Thread Arjen de Korte
[...] I think this output doesn't help very much. This is very helpful. The problem is not in the connection to the driver, upd-data_ok switches between 0 and 1. Only the driver can change this value by repetitively switching between DATASTALE and DATAOK. There is nothing upsd can do about

Re: [Nut-upsuser] no longer stale when disconnected with 2.0.5

2007-01-29 Thread Arjen de Korte
[...] I hope this small part of the log helps. Maybe someone with more experience with the 'usbhid-ups' driver is able to decipher what is going on. I'm still waiting for someone to send me a USB-HID UPS so that I can debug things like this myself. Best regards, Arjen

Re: Antwort: Re: [Nut-upsuser] no longer stale when disconnected with 2.0.5

2007-01-29 Thread Arjen de Korte
here the output of upsd -D when starting upsc [EMAIL PROTECTED] ups.status (and stopping after 20-30 sec with an ctrl+c) Ah, you have a problem with 'upsc' rather than with 'upscmd' like you stated before. That changes things. Connection from 127.0.0.1 acl_check: localhost: match 1 ACL

Re: [Nut-upsuser] sweex 1000VA LB OB issue

2007-01-29 Thread Herman
Udo van den Heuvel schreef: Arjen de Korte wrote: This suggests that sweex doesn't know what UPS'es they are actually shipping. Or to stupid to include the right manual.. Spot on. I have told them this more than two years ago, but apparently they just don't care about it. They are

Re: [Nut-upsuser] no longer stale when disconnected with 2.0.5

2007-01-29 Thread Peter Selinger
Hi Arjen, yes, you are right. The calls to dstate_dataok() in usbhid_ups.c:hid_ups_walk() are somewhat random. I am worried about this: if ( (retcode == -EPERM) || (retcode == -EPIPE) || (retcode == -ENODEV) || (retcode == -EACCES) || (retcode == -EIO) ||

[Nut-upsuser] initial configuration assistance

2007-01-29 Thread Gregory Orange
Hi, I've browsed the archives back for a few months and nothing has jumped out at me as being helpful, but since there doesn't seem to be a search facility it's certainly possible I've missed what I'm looking for. Anyway, I wonder if someone can help me. I've very recently installed nut

Re: [Nut-upsuser] initial configuration assistance

2007-01-29 Thread Arjen de Korte
I've configured upsd.conf with [rack1ups] driver = apcsmart cable = 940-0024C port = auto This won't work. You need to specify a serial port for this driver (see 'man 5 ups.conf' and 'man 8 apcsmart'). Only the 'newhidups' driver accepts 'auto' (anything