search for: ignoreoff

.../pipermail/nut-upsuser/2007-December/003573.html which was discussing the issue with the megatec_usb driver detecting the ups.status as OFF instead of OL or OB. With the patch now applied I get the following: battery.charge: 67.2 battery.voltage: 25.20 battery.voltage.nominal: 23.5 driver.flag.ignoreoff: enabled driver.name: megatec_usb driver.parameter.bus: 003 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.productid: 0000 driver.parameter.vendorid: 0001 driver.version: 2.2.1- driver.version.internal: 1.5.9 input.frequency: 50.0 input.voltage: 229.0 input.voltage.fa...

.../pipermail/nut-upsuser/2007-December/003573.html which was discussing the issue with the megatec_usb driver detecting the ups.status as OFF instead of OL or OB. With the patch now applied I get the following: battery.charge: 67.2 battery.voltage: 25.20 battery.voltage.nominal: 23.5 driver.flag.ignoreoff: enabled driver.name: megatec_usb driver.parameter.bus: 003 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.productid: 0000 driver.parameter.vendorid: 0001 driver.version: 2.2.1- driver.version.internal: 1.5.9 input.frequency: 50.0 input.voltage: 229.0 input.voltage.fa...

...ation not permitted Driver failed to start (exit status=1) My ups.conf looks like this [qnapups] driver = usbhid-ups port = auto mfr = "Plexus" model = "Plexus 500VA UPS" desc = "Workstation" pollinterval=1 ignoreoff lsusb shows before the UPS is plugged in [~] # lsusb Bus 001 Device 003: ID 04a9:10b0 Canon, Inc. Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Bus 001 Device 001: ID 1d6b:0002 And after [~] # lsusb Bus 001 Device 004: ID 0001:0000 Fry's Electronics Bus 001 Device 003: ID 04a...

Gidday all - I'm a new user to nut. I've got some cheap powerpal UPSs working fairly well. However I also have a new Dynamix UPS-1700D and an old Powercom KIN-1700 something unit that I cannot make work right. The best method I've found is "trial and error" which sounds a bit last-resort. Is there any better way to find out what protocol is used? -- Criggie

..., thanks for the patch. But I have a few comments: Are you saying the UPS raises the "OFF" flag when a timed shutdown command is sent to it, before actually shutting down? If so, that is a violation of the megatec protocol. The megatec version in the development trunk has an option "ignoreoff" to accomodate UPSes that exibit this behavior. > Know working SMS Models : > > SINUS Single : Only versions > Manager III : Only serial versions I'll add this to the compatibility list. > /* Known battery types must be in ascending order by "nominal" first, a...

...d issue (as root): blazer_usb -a ups -DDD >> /path/to/my/precious/log 2>&1 (keep it running till the test is over - this is the log we are after) 6) Turn the UPS off 6.1) Turn the UPS on [Me too, I'm inclined to see it as a bogus value (in the old megatec driver there was the 'ignoreoff' option that dealed with it - although the value was mapped as an on/off status rather than the actual 'shutdown active'), but the 7th bit of the status byte should change only while the UPS is shutting down and then be back at its original value: if you turned off the UPS with a button...

I've done all the steps. However FSD indication did NOT disappear. So it seems UPS always send the FSD flag. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20150316/fd7ccc7a/attachment.html>

On Mar 16, 2015, at 12:26 PM, cinowell <cinowell at gmail.com> wrote: > I've done all the steps. However FSD indication did NOT disappear. So it seems UPS always send the FSD flag. I know this sounds kind of ridiculous, but you could use a hex editor to change 'FSD' to 'OFF' in blazer_usb (it only seems to occur once), which would restore the behavior of

...-a ups -DDD >> /path/to/my/precious/log 2>&1 > (keep it running till the test is over - this is the log we are after) > 6) Turn the UPS off > 6.1) Turn the UPS on > > [Me too, I'm inclined to see it as a bogus value (in the old megatec > driver there was the 'ignoreoff' option that dealed with it - although > the value was mapped as an on/off status rather than the actual > 'shutdown active'), but the 7th bit of the status byte should change > only while the UPS is shutting down and then be back at its original > value: if you turned off t...

Hi again, I tested several times using the Megatec driver from nut 2.2.2 to no avail, as it definitely never "sees" the UPS. Always getting : # drivers/megatec -DDD -a Alpha Network UPS Tools 2.2.2 - Megatec protocol driver 1.5.14 [megatec] Carlos Rodrigues (c) 2003-2008 debug level is '3' Starting UPS detection process... Asking for UPS status [Q1]... Q1 => FAILED

...iled (minimum failures: 2). > Cancelling any pending shutdown or battery test. > Asking for UPS information [I]... > I => OK [#Sinapse ? ? ? ? MS II ? ? ?MS3006AG ?] > I VALUES => [Sinapse MS II MS3006AG] > Megatec protocol UPS detected [Sinapse MS II MS3006AG]. > Parameter [ignoreoff]: [false] > Asking for UPS power ratings [F]... > F => OK [#230.0 026 240.0 50.0] > F VALUES => [230.0 26.0 240.0 50.0] > Unsupported battery voltage (240.0V). > This UPS has an unsupported combination of battery voltage/number of > batteries. > Parameter [battvoltmult]:...

...ing any pending shutdown or battery test. > Asking for UPS information [I]... > get_data_agiler: raw dump: (0 bytes) => > get_data_agiler: raw dump: (0 bytes) => > I => FAILED [short read] > I detail: (0 bytes) => > Megatec protocol UPS detected. > Parameter [ignoreoff]: [false] > Asking for UPS power ratings [F]... > get_data_agiler: raw dump: (0 bytes) => > get_data_agiler: raw dump: (24 bytes) => 23 32 33 30 2e 30 20 30 30 32 20 > 31 32 2e 30 30 20 35 30 2e 30 0d 30 30 > F => OK [#230.0 002 12.00 50.0] > 12.0V battery, interva...

...failures: 2). Cancelling any pending shutdown or battery test. set_data_krauler: index [0b] set_data_krauler: retry [UPS No Ack] Asking for UPS information [I]... set_data_krauler: index [0c] I => OK [# VT120725 ] Megatec protocol UPS detected [ VT120725]. Parameter [ignoreoff]: [false] Asking for UPS power ratings [F]... set_data_krauler: index [0d] F => OK [#220.0 000 024.0 50.0] 24.0V battery, interval [19.4V, 27.4V]. Done setting up the UPS. Asking for UPS status [Q1]... set_data_krauler: index [03] Q1 => OK [(221.8 140.0 222.0 016 49.9 27.5 30.0 00001001] Calc...

...failures: 2). Cancelling any pending shutdown or battery test. set_data_krauler: index [0b] set_data_krauler: retry [UPS No Ack] Asking for UPS information [I]... set_data_krauler: index [0c] I => OK [# VT120725 ] Megatec protocol UPS detected [ VT120725]. Parameter [ignoreoff]: [false] Asking for UPS power ratings [F]... set_data_krauler: index [0d] F => OK [#220.0 000 024.0 50.0] 24.0V battery, interval [19.4V, 27.4V]. Done setting up the UPS. Asking for UPS status [Q1]... set_data_krauler: index [03] Q1 => OK [(221.8 140.0 222.0 016 49.9 27.5 30.0 00001001] Calc...

...60.2 13.6 N/.A 00001001] > 0 out of 5 detection attempts failed (minimum failures: 2). > Cancelling any pending shutdown or battery test. > Asking for UPS information [I]... > I => FAILED [short read] > I detail: (0 bytes) => > Megatec protocol UPS detected. > Parameter [ignoreoff]: [false] > Asking for UPS power ratings [F]... > F => OK [#120.0 005 12.00 60.0] > 12.0V battery, present voltage (8549026304.0V) outside of supported > intervals. > This UPS has an unsupported combination of battery voltage/number of > batteries. > Cannot calculate charge...

...battery test. Asking for UPS information [I]... I => FAILED [short read] I detail: (1 bytes) => 49 send_to_all: SETINFO ups.mfr "unknown" send_to_all: SETINFO ups.model "unknown" Megatec protocol UPS detected. send_to_all: SETINFO ups.serial "unknown" Parameter [ignoreoff]: [false] Asking for UPS power ratings [F]... ok get_data_phoenix: got so far [#120.0 0] get_data_phoenix: (8 bytes) => 23 31 32 30 2e 30 20 30 ok get_data_phoenix: got so far [#120.0 006 24.00] get_data_phoenix: (16 bytes) => 23 31 32 30 2e 30 20 30 30 36 20 32 34 2e 30 30 ok 00]_data_ph...