similar to: No power cycle after shutdown on Atlantis Land OnePower A03-S1001

On Wed, 14 Oct 2015, Davide Baldini wrote: > the full output of upsc ${myups} is at https://pastebin.mozilla.org/8849188 ; > in particular: > > ups.delay.shutdown: 30 > ups.delay.start: 180 > > However, the UPS does not shut down, not immediately nor well after the > timeout of the command: upscmd -u admin -p mypass myups shutdown.return 360 What does "ps aux |

On Wed, 14 Oct 2015, Davide Baldini wrote: > upsdrvctl shutdown > ... > instcmd(shutdown.return, [NULL]) > instcmd: FAILED > Shutdown failed! > Driver failed to start (exit status=1) > > This time /var/log/syslog doesn't register anything about the UPS after > issuing the command above. Instead, It logged some errors after a > upscmd -u admin -p mypass

I changed the driver from blazer_usb to nutdrv_qx, by editing /etc/nut/ups.conf. To apply changes, I did: # service nut-server restart # service nut-client restart Then I've run a second test, this time simpler than the first one described in my previous email; the test only consists in toggling off/on a wall switch which controls power to the UPS. This way, electric ground remains

On 10/14/2015 12:18 PM, Roger Price wrote: > Is there any command in the list provided by "upscmd -l myups" which is accepted > by this UPS? None of the command sin the list successfully completes, not even beeper.toggle. My list: # upscmd -l myups Instant commands supported on UPS [myups]: beeper.toggle - Toggle the UPS beeper load.off - Turn off the load

On Oct 2, 2015, at 9:01 PM, Davide Baldini <baldiniebaldini at gmail.com> wrote: > > When I manually unplug the mains, the computer waits 3 minutes, shutdowns, and there it stays. As per the above commands, issued from ups_events.sh, it is instead supposed to boot up after 6 minutes (360 / 60 seconds) counted from t?, the moment of the unplug. After 20 seconds from the shutdown, and

On 10/14/2015 10:17 AM, Roger Price wrote: > What does "ps aux | grep ups" report? ps aux | grep ups nut 2902 0.0 0.0 20588 1140 ? Ss 00:10 0:02 /lib/nut/nutdrv_qx -a myups nut 2946 0.0 0.0 37632 1428 ? Ss 00:10 0:00 /lib/nut/upsd root 2970 0.0 0.0 37616 1436 ? Ss 00:10 0:00 /lib/nut/upsmon root 2973

On Wed, 14 Oct 2015, Davide Baldini wrote: >> Is there any command in the list provided by "upscmd -l myups" which is >> accepted by this UPS? > > None of the command sin the list successfully completes, not even > beeper.toggle. It looks as if the problem is more general than turning off the UPS. The command mechanism is broken. > I added -q and -D to

On 10/14/2015 06:11 PM, Roger Price wrote: > Is /etc/init.d/nut-client a Bash/Dash script? Is it possible to add the option to > the call of the driver in this script? Looks like some options can be passed: /etc/init.d/nut-client is a dash script and when it is started or restarted, it executes: start-stop-daemon -S -q -p $upsmon_pid -x $upsmon \ -- $UPSMON_OPTIONS >/dev/null

On Tue, 13 Oct 2015, Davide Baldini wrote: > Guess I can assume that my OnePower A03-S1001 just doesn't support the > shutdown command. Might this be the case? If the UPS does shut down, then it will have to do so after a delay and not immediately on receiving the shutdown command. Does upsc <ups_name> report anything like ups.delay.shutdown: 30 ups.delay.start: 40

Thanks Roger, the full output of upsc ${myups} is at https://pastebin.mozilla.org/8849188 ; in particular: ups.delay.shutdown: 30 ups.delay.start: 180 However, the UPS does not shut down, not immediately nor well after the timeout of the command: upscmd -u admin -p mypass myups shutdown.return 360 -- Davide

Guess I can assume that my OnePower A03-S1001 just doesn't support the shutdown command. Might this be the case? -- Davide

Atlantis Land A03-P551(V1.2) battery.charge: 100 battery.voltage: 13.70 battery.voltage.high: 13.00 battery.voltage.low: 10.40 battery.voltage.nominal: 12.0 device.mfr: device.model: device.type: ups driver.name: blazer_usb driver.parameter.langid_fix: 0x0409 driver.parameter.pollinterval: 2 driver.parameter.port: x driver.version: 2.6.4 driver.version.internal: 0.08 input.current.nominal: 0.0

Hi Daniele, I finally got a Best Power Patriot Pro II fixed up with a new battery and cable, and tried it with nutdrv_qx (since it uses a variant of the Q1 protocol). It auto-detected the use of Q1. It looks like things mostly work: bestups: battery.charge: 100.0 battery.voltage: 13.9 battery.voltage.nominal: 12 device.mfr: Best Power device.model: Patriot Pro II 400 device.type: ups

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 finally got a Best Power Patriot Pro II fixed up with a new battery and cable, and tried it with nutdrv_qx (since it uses a variant of the Q1 protocol). It auto-detected the use of Q1. > > It looks like things mostly work: Nice, merging bestups.c into nutdrv_qx has been on my todo list for a while, let's see how far we can get. > 1) The bestups driver uses an "ID"

Hello! I'm a total noob in the NUT world, and have 0 experience dealing with Linux distributions. Since NUT is poorly ported to Windows it's driving me crazy, I hope you can help me. I have, after 3 days of painful reading, testing and failing, successfully set up NUT to communicate with my cheap-ass line-interactive 1000VA Chinese UPS (just no brand at all, it is a locally rebranded UPS,

[please keep the list CC'd] On 12/13/05, ngpost1 <ngpost1@etitech.net> wrote: > Charles, > > Another question: > > When I ran the newhidups -DD.... test, there apparently was no > communication with the UPS. Since I assume is talks with the Megatec > protocol, I wanted to force the protocol in the command line. As far as I know (and I am no expert on

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi there! I don't know if you are able to help me. Have tried almost everything at this point.. I recently switched from a BlueWalker(Powerwalker?) PW UPS VI2000 LCD 2000VA offline UPS to a BlueWalker(Powerwalker?) PW UPS VFI 1500 LCD 1500VA Online UPS. Seems like the driver is accepting both, however, the shutdown command wont work. And this