Here you go As you can see not very much information is available.
upsc [EMAIL PROTECTED] produces driver.name: newhidups driver.parameter.port: auto driver.version: 2.1.0 driver.version.data: RICHCOMM HID 0.9 driver.version.internal: 0.28 ups.mfr: Richcomm Tech ups.model: UPS2004 So what's next? Eli On Sunday, 18 בJune 2006 05:08, Peter Selinger wrote: > As I said... I would like you to examine the output of upsc. > Presumably: > > upsc [EMAIL PROTECTED] > > (you might want to come up with a shorter synonym for this UPS) > > I would need to see what, if any, variables are reported, and how, if > at all, they change over time (e.g. as you plug/unplug the UPS, as the > battery level changes, when the battery gets low, etc). > > -- Peter > > Eli Wapniarski wrote: > > OK Peter > > > > upsdrvctl start produces > > > > Network UPS Tools - UPS driver controller 2.1.0 > > Network UPS Tools: New USB/HID UPS driver 0.28 (2.1.0) > > > > Detected a UPS: Richcomm Tech /UPS2004 > > Using subdriver: RICHCOMM HID 0.9 > > > > upsd produces > > > > Network UPS Tools upsd 2.1.0 > > Connected to UPS [Gamatronic_D-Compact]: Gamatronic_D-Compact > > Synchronizing..........done > > > > Whats next? > > > > Eli=20 > > > > On Saturday, 17 =D7=91June 2006 20:00, Peter Selinger wrote: > > > Eli Wapniarski wrote: > > > > Firstly forget about my link comment. I misread something. > > > > > > > > I get the same results if I ups.conf contains > > > > > > > > [Gamatronic_D-Compact] > > > > driver=3D newhidups > > > > port =3D auto > > > > desc =3D "Gamatronic D-Compact" > > > > > > > > running > > > > > > > > newhidups -DD -u root -x vendorid=3D0925 -a Gamatronic_D-Compact > > > > > > > > produces > > > > > > > > Network UPS Tools: New USB/HID UPS driver 0.28 (2.1.0) > > > > > > > > Error: UPS [Gamatronic_D-Compact] is for driver , but I'm newhidups! > > > > > > Please put a space between "driver" and "=3D". I don't know why this > > > matters, but apparently it does. NUT thinks that your driver is called > > > "" (the empty string), hence the weird error messages. > > > > > > NUT developers: perhaps parseconf.c should be changed to be more > > > flexible regarding white space, or the fact that the "=3D" must be > > > surrounded by spaces should be documented? I am surprised this error > > > is not more common. Or did I miss something? > > > > > > -- Peter _______________________________________________ Nut-upsuser mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
