similar to: Re: [Nut-upsuser] Atlantis-Land UPS with Cypress CY7C63723 chip

Hello Peter! Peter Selinger wrote: > This is useful information. I don't think the device is currently > supported, but the information printed above is enough to write a > subdriver for it. Note that the purpose of the "-x generic" option is > precisely to produce this output. [...] >> Apparently the UPS is recognized but no communication is >>

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

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,

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

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

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

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

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 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 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

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 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

Hello, my Atlantis UPS (model on "subject" line) fails to cycle off the outlet power after a power failure on the mains followed by an automatic shutdown of the computer. The UPS simply remains always on, preventing the computer from restarting. ** Setup: ** Nut version 2.7.2 Nut driver blazer_usb Linux 4.1.1 The config files are pretty default; the peculiar customization is

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

Hi Vladimir, I have got 2.0.3 working on netBSD 3.0. To get it operational I needed to do the following (most of this is from memory...). 1). Recompile kernel with uhid removed. If uhid ataches to the device then libusb is not able to. Have to allow generic usb driver ugen to claim port. >From dmesg usb0 at uhci0: USB revision 1.0 uhub0 at usb0 uhub0: VIA Technologies UHCI root hub, class

Hello. I have this UPS: Krauler UP-D1200VA Megatec USB protocol Vendor ID: 0x0001, Device ID: 0x0000 #KRAULER UP-D1200VA VER6.00 #220.0 004 23.50 50.0 Currently I have nut 2.2.0 installed from sources. Installation was successful except that I had to change a string in 52-nut-usbups.rules from: SUBSYSTEM!="usb_device", GOTO="nut-usbups_rules_end" to:

-----BEGIN PGP SIGNED MESSAGE----- Hello, I leave a mail here because I can't find any solution in order to get the nut working with this UPS despite I search everywhere on the net. I've bought this UPS recently after that an MGE-UPS Ellipse 1200 USB burn. I've those information about the UPS : Reseller link : http://www.alpha-power-technologie.com/images/GPi-usb.pdf In his