Re: [Nut-upsuser] Trouble Configuring NUT with Gamatronic USB

2006-06-17 Thread Eli Wapniarski
Hi Peter First let me say that I have appreciated you're help up to now and was quite amazed at how quickly (real time) we were able to get nut to detect the ups. I understand that the rest of this is a different kettle of fish altogether, so I do understand you're reluctance to dig into

Re: [Nut-upsuser] Trouble Configuring NUT with Gamatronic USB

2006-06-17 Thread Peter Selinger
Eli Wapniarski wrote: > > 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

Re: [Nut-upsuser] Trouble Configuring NUT with Gamatronic USB

2006-06-17 Thread Eli Wapniarski
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 nex

Re: [Nut-upsuser] Trouble Configuring NUT with Gamatronic USB

2006-06-17 Thread Peter Selinger
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, a

[Nut-upsuser] CyberPower CP550SL / AE550 success

2006-06-17 Thread Jonathan A. Kollasch
Hi, I finally got the serial cable for this CyberPower CP550SL / AE550, and have successfully tested the genericups type 7 driver. The shutdown delay is about 2 minutes after the shutdown signal, and that signal needs to be rather long, I got it to work with 20 seconds. I suspect that all CyberP

Re: [Nut-upsuser] Trouble Configuring NUT with Gamatronic USB

2006-06-17 Thread Eli Wapniarski
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]:

Re: [Nut-upsuser] Trouble Configuring NUT with Gamatronic USB

2006-06-17 Thread Peter Selinger
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= newhidups > port = auto > desc = "Gamatronic D-Compact" > > running > > newhidups -DD -u root -x vendorid=0925

Re: [Nut-upsuser] Trouble Configuring NUT with Gamatronic USB

2006-06-17 Thread Eli Wapniarski
Firstly forget about my link comment. I misread something. I get the same results if I ups.conf contains [Gamatronic_D-Compact] driver= newhidups port = auto desc = "Gamatronic D-Compact" running newhidups -DD -u root -x vendorid=0925 -a Gamatronic_D-Compact produces Network UPS

Re: [Nut-upsuser] Trouble Configuring NUT with Gamatronic USB

2006-06-17 Thread Peter Selinger
Eli Wapniarski wrote: > > upsdrvctl -D -u root start produces > > Network UPS Tools - UPS driver controller 2.1.0 > Starting UPS: Gamatronic_D-Compact > exec: /usr/bin/ -a Gamatronic_D-Compact > execv: Permission denied > Driver failed to start (exit status=1) > > I think I understand the pr

Re: [Nut-upsuser] MGE Pulsar Extreme communication problems

2006-06-17 Thread Daniel O'Connor
On Friday 16 June 2006 21:03, Daniel O'Connor wrote: > I didn't get around to trying serial today but hopefully I will be able to > test it RSN. > > I'll keep you in mind as I test ;) Serial works so I am less stressed now - I have a fallback position :) I am going to try making the newhidups cod