search for: outputid

...e: Input Can't find object 00860004.PowerConverter.Input.Voltage Path: 00860004.PowerConverter.Input.Voltage, Type: Input Can't find object 00860004.PowerConverter.Input.Frequency Path: 00860004.PowerConverter.Input.Frequency, Type: Input Can't find object 00860004.PowerConverter.Output.OutputID Path: 00860004.PowerConverter.Output.OutputID, Type: Input Can't find object 00860004.PowerConverter.Output.FlowID Path: 00860004.PowerConverter.Output.FlowID, Type: Input Can't find object 00860004.PowerConverter.Output.Voltage Path: 00860004.PowerConverter.Output.Voltage, Type: Input Can&...

...3/373. So if I pass 50 as a value, then it gets read as 323 on the PC side? And if the physical range is much greater than the logical range, then it just scales it? The other min/max I don't quite understand is usage min/max. I'm thinking they have something to do with the usages "OutputID", "FlowID", etc. Thank you for the help so far. I really wish there were better learning docs out there for the un-initiated. Rob -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments...

Hello Charles! As promised, I just checked out the CVS and recompiled everything. In the attached .txt is what is coming out from my UPS. I am wondering about all those zeroes. Also, this morning I plan to connect the UPS to a Win box running the monitoring program supplied with the UPS (UPSilon2000) and a USB sniffer program. If you have any suggestions on what to look for in the data,

Hello everybody! I am trying to get an Atlantis-Land OnePower Line Interactive S1501 UPS (actually it is made by Ablerex) to talt to my Linux box through its USB port (no more RS-232...), either using the supplied program (UPSilon2000, works under Win and Linux) or whatever else. The UPSilon2000 program apparently works OK *if* it can talk to the UPS via a serial port; since my UPS has

Hello everybody! I am trying to get an Atlantis-Land OnePower Line Interactive S1501 UPS (actually it is made by Ablerex) to talt to my Linux box through its USB port (no more RS-232...), either using the supplied program (UPSilon2000, works under Win and Linux) or whatever else. The UPSilon2000 program apparently works OK *if* it can talk to the UPS via a serial port; since my UPS has

I have a Belkin F6H500ukUNV ups that I am attempting to get working under nut, however it does not appear to be detected by nut, I'm assuming that I need to feed some information back to you guys to get it included in the database somwhere. I've included (what I can think might be) the relivant outputs. Please let me know if you require anything else. dmesg output /sbin/newhidsups

...3/373. So if I pass 50 as a value, then it gets read as 323 on the PC side? And if the physical range is much greater than the logical range, then it just scales it? The other min/max I don't quite understand is usage min/max. I'm thinking they have something to do with the usages "OutputID", "FlowID", etc. Thank you for the help so far. I really wish there were better learning docs out there for the un-initiated. Rob -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments...

...ure, ReportID: 0x14, Offset: 32, Size: 16, Value: 500.000000 Path: UPS.Flow.[4].ConfigCurrent, Type: Feature, ReportID: 0x14, Offset: 48, Size: 16, Value: 4.160000 Path: UPS.Flow.[4].ConfigVoltage, Type: Feature, ReportID: 0x15, Offset: 0, Size: 16, Value: 120.000000 Path: UPS.PowerConverter.Output.OutputID, Type: Feature, ReportID: 0x1c, Offset: 0, Size: 8, Value: 1.000000 Path: UPS.PowerConverter.Output.FlowID, Type: Feature, ReportID: 0x1c, Offset: 8, Size: 8, Value: 4.000000 So I'm wondering if the "UPS.PowerSummary.FlowID" being equal to 4 means that the voltage in "UPS.PowerS...

...5809 Report[buf]: (8 bytes) => 16 03 55 00 50 00 53 00 0.635817 Path: 00860004.PowerConverter.Input.Frequency, Type: Input, ReportID: 0x04, Offset: 40, Size: 16, Value: 8.3e+06 0.653732 Report[get]: (9 bytes) => 16 03 55 00 50 00 53 00 20 0.653746 Path: 00860004.PowerConverter.Output.OutputID, Type: Input, ReportID: 0x05, Offset: 0, Size: 4, Value: 300000 0.653752 Report[buf]: (9 bytes) => 16 03 55 00 50 00 53 00 20 0.653762 Path: 00860004.PowerConverter.Output.FlowID, Type: Input, ReportID: 0x05, Offset: 4, Size: 4, Value: 0 0.653768 Report[buf]: (9 bytes) => 16 03 55 00...

On Apr 5, 2014, at 7:18 AM, Mick wrote: > $ upsrw -s "ups.delay.shutdown"="30" iDowell at localhost > Username (suzy): admin > Password: > OK This command is sending the value to the UPS (via the usbhid-ups driver). > $ upsc iDowell at localhost ups.delay.shutdown > 30 And this command ends up reading the value back from the UPS. > However, following

...m USB device... 0.907834 HID descriptor length 412 0.962825 Report Descriptor size = 412 0.963065 Using subdriver: EXPLORE HID 0.1 0.966834 Path: UPS.PowerConverter.PowerConverterID, Type: Feature, ReportID: 0x0b, Offset: 0, Size: 8, Value: 0 0.966856 Path: UPS.PowerConverter.Output.OutputID, Type: Feature, ReportID: 0x0b, Offset: 8, Size: 8, Value: 0 0.970828 Path: UPS.PowerConverter.Output.Voltage, Type: Feature, ReportID: 0x0e, Offset: 0, Size: 8, Value: 230 0.974824 Path: UPS.PowerConverter.Output.LowVoltageTransfer, Type: Feature, ReportID: 0x13, Offset: 0, Size: 8, Value...

Hi All, I'm using an iDowell UPS with the usbhid-ups driver: $ upsc iDowell at localhost battery.charge: 100 battery.charge.low: 15 battery.runtime: 650 battery.type: Pb acc device.mfr: iDowell device.model: iBox device.serial: 00000001 device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto

...0270 Report[buf]: (8 bytes) => 16 03 55 00 50 00 53 00 0.490281 Path: 00860004.PowerConverter.Input.Frequency, Type: Input, ReportID: 0x04, Offset: 40, Size: 16, Value: 8.3e+06 0.508193 Report[get]: (9 bytes) => 16 03 55 00 50 00 53 00 20 0.508253 Path: 00860004.PowerConverter.Output.OutputID, Type: Input, ReportID: 0x05, Offset: 0, Size: 4, Value: 300000 0.508264 Report[buf]: (9 bytes) => 16 03 55 00 50 00 53 00 20 0.508358 Path: 00860004.PowerConverter.Output.FlowID, Type: Input, ReportID: 0x05, Offset: 4, Size: 4, Value: 0 0.508369 Report[buf]: (9 bytes) => 16 03 55 00...

...9.642335 Path: UPS.PowerConverter.Output.ffff0050, Type: Feature, ReportID: 0x4e, Offset: 0, Size: 16, Value: 210 9.672044 Path: UPS.PowerConverter.Output.LowVoltageTransfer, Type: Feature, ReportID: 0x47, Offset: 0, Size: 16, Value: 160 9.672277 Path: UPS.PowerConverter.Output.OutputID, Type: Feature, ReportID: 0x40, Offset: 16, Size: 8, Value: 1 9.704301 Path: UPS.PowerConverter.Output.Overload.[1].PresentStatus.ffff007e, Type: Feature, ReportID: 0x49, Offset: 0, Size: 8, Value: 0 9.704542 Path: UPS.PowerConverter.Output.Overload.[1].PresentStatus.ffff007e, Type: I...

...0 4.599949 Path: UPS.PowerConverter.Output.HighVoltageTransfer, Type: Feature, ReportID: 0x13, Offset: 0, Size: 16, Value: 264 4.644947 Path: UPS.PowerConverter.Output.LowVoltageTransfer, Type: Feature, ReportID: 0x14, Offset: 0, Size: 8, Value: 184 4.645147 Path: UPS.PowerConverter.Output.OutputID, Type: Feature, ReportID: 0x0b, Offset: 64, Size: 8, Value: 1 4.645315 Path: UPS.PowerConverter.Output.PresentStatus.ShortCircuit, Type: Feature, ReportID: 0x03, Offset: 24, Size: 8, Value: 0 4.645525 Path: UPS.PowerConverter.Output.PresentStatus.ShortCircuit, Type: Input, ReportID: 0x03, Off...

...set: 24, Size: 16 2.272283 Can't retrieve Report 04: Broken pipe 2.272321 Path: 00860004.PowerConverter.Input.Frequency, Type: Input, ReportID: 0x04, Offset: 40, Size: 16 2.275535 Can't retrieve Report 05: Broken pipe 2.275581 Path: 00860004.PowerConverter.Output.OutputID, Type: Input, ReportID: 0x05, Offset: 0, Size: 4 2.279407 Can't retrieve Report 05: Broken pipe 2.279454 Path: 00860004.PowerConverter.Output.FlowID, Type: Input, ReportID: 0x05, Offset: 4, Size: 4 2.282530 Can't retrieve Report 05: Broken pipe 2.282576 Path: 008...

I tested your fix (newhidups -DDD /dev/null) using both and APC Back-UPS 350 an APC Smart-UPS RT 2000 XL. No more segmentation fault due to the fixed-size array. ~Jacob -----Original Message----- From: nut-upsdev-bounces@lists.alioth.debian.org [mailto:nut-upsdev-bounces@lists.alioth.debian.org] On Behalf Of Peter Selinger Sent: Monday, October 16, 2006 12:12 PM To: Schmier, Jacob Cc: NUT

Oops... changing that to --with-user=nut solved one problem. I have the driver, upsd and upsmon running now. Thank you! Now I'm back to another issue, every 2 seconds I get in the logs: May 3 13:45:23 myhost upsd[2587]: Connected to UPS [eaton]: usbhid-ups-eaton It seems happy to do this forever. On Tue, May 3, 2016 at 8:17 AM, Charles Lepple <clepple at gmail.com> wrote: > On

...60 5.393956 Path: UPS.PowerConverter.Output.HighVoltageTransfer, Type: Feature, ReportID: 0x13, Offset: 0, Size: 16, Value: 138 5.437951 Path: UPS.PowerConverter.Output.LowVoltageTransfer, Type: Feature, ReportID: 0x14, Offset: 0, Size: 8, Value: 93 5.437969 Path: UPS.PowerConverter.Output.OutputID, Type: Feature, ReportID: 0x0b, Offset: 80, Size: 8, Value: 1 5.437980 Path: UPS.PowerConverter.Output.PresentStatus.ShortCircuit, Type: Feature, ReportID: 0x03, Offset: 24, Size: 8, Value: 0 5.437989 Path: UPS.PowerConverter.Output.PresentStatus.ShortCircuit, Type: Input, ReportID: 0x03, Off...

...8 6.130606 Report[get]: (3 bytes) => 47 b0 00 6.130747 Path: UPS.PowerConverter.Output.LowVoltageTransfer, Type: Feature, ReportID: 0x47, Offset: 0, Size: 16, Value: 176 6.130812 Report[buf]: (5 bytes) => 40 01 04 01 01 6.130879 Path: UPS.PowerConverter.Output.OutputID, Type: Feature, ReportID: 0x40, Offset: 16, Size: 8, Value: 1 6.231055 Report[get]: (2 bytes) => 49 00 6.231557 Path: UPS.PowerConverter.Output.PresentStatus.ffff004a, Type: Feature, ReportID: 0x49, Offset: 0, Size: 8, Value: 0 6.231641 Report[buf]: (2 bytes) => 49 0...