similar to: Some questions

G'day y'all, Here's a tiny patch set for drivers/apcsmart.c and drivers/apcsmart.h. Adds APC SmartUPS 1250 ("8QD" case) + 940-0024C recognition to apcsmart. (Unpatched apcsmart.c v1.99.8 misidentifies the SmartUPS 1250 as a "dumb" UPS.) For NUT 2.0.5+. NUT 2.0.5: Patches apply successfully. Builds successfully. Works as expected under Ubuntu 7.04. NUT 2.2:

On 12/03/2016 10:35 AM, Charles Lepple wrote: > On Dec 3, 2016, at 11:16 AM, Jack McGee <jack at greendesk.net> wrote: >> Dec 3 08:38:16 amethi upsd[18234]: not listening on ::1 port 3493 >> Dec 3 08:38:16 amethi upsd[18234]: listening on 127.0.0.1 port 3493 >> Dec 3 08:38:16 amethi upsd[18234]: no listening interface available > I can't say I fully understand

Gabor: note, these HCL reports go to the nut-upsdev list. Begin forwarded message: > From: Gabor Tjong A Hung > Subject: Re: Network UPS Tools - Compatibility List > Date: September 3, 2013 2:18:31 PM EDT > > Sorry, > I just noticed the "If your device isn?t listed" part: > > [HCL] Forza FX-1500LCD supported by blazer_usb > > > [root at freenas] ~#

Hi I'm having a problem with the bcmxcp_usb driver FSD command: everything seems to work apart from: upsmon -c fsd Environment: Ubuntu 7.04, nut 2.0.5-1, nut-usb 2.0.5-1, Powerware 3105 UPS. upsd appears to send the FSD command to the UPS, upsmon then runs my NOTIFYCMD (which halts my PC) but the UPS just doesn't turn off. Here are the /var/log/daemon.log entries: Jul 24 23:13:16

Hi, I have an OEM of KStar UDC9101S which is Megatec protocol rs232 capable unit. So I use blazer_ser protocol=megatec /dev/ttyUSB0 with no issue to get NUT running. Please direct me what command should I issue to collect the data in order to include the UPS to device database? P.S. tryed /lib/nut/blazer_ser -DD... but no difference from a regular output has being added by the driver.

This UPS is already listed in the compatibility list. But I wanted to add the instant commands supported by upscmd: ============================ Instant commands supported on UPS [PW5125]: beeper.disable - Disable the UPS beeper beeper.enable - Enable the UPS beeper beeper.mute - Temporarily mute the UPS beeper load.on - Turn on the load immediately outlet.1.load.off - Turn off the load on

Dear list, I have an APC Smart-UPS 1500 hooked up via the USB port. Recently, when we had a power outage, the only entry in the logs was: Dec 3 14:43:43 afs1 upsmon[3035]: UPS apc at localhost on battery and then the machine seems to have run until the battery was empty. It only notices the "battery low" after I turn the system back on: Dec 3 16:01:39 afs1 usbhid-ups[21973]:

Well, after our first real extended power outage, I found out that even though the UPS 1000 RM is recognized okay, it does not work properly. It never seems to see any change in UPS status. It looks very similar to the other issue I reported with the APC CyberFort 350. I never was able to get to the bottom of the CyberFort issue, but I'll bet it's the same issue as we have with the

Dear Charles, thanks for your quick answer and your information! I didn't know there is a difference in the PR-series between old and new. So thanks for this valuable information! usbconfig dump_device_desc shows: ugen0.2: <CyberPower Systems product 0x0601> at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON (50mA)

The REDi Blazer 600VA (BLAZER600c) UPS found here [ro_RO]: http://www.emag.ro/ups-redi-blazer-600va-blazer600c/pd/EX5X2BBBM/ which is actually a Centralion Blazer 600VA [en_TW]: http://www.centralion.com/html/product/back-Product-ups-blazer400.htm works with the blazer_ser driver ----------shell output---------- # upsrw ups # upscmd -l ups Instant commands supported on UPS [ups]: beeper.toggle -

Hi Mutlu, 2009/8/7 Mutlu T. <cmtunc at gmail.com> > Redirecting to debian.org domain due to being rejected as spam by free.fr > > > ------- Forwarded message ------- > From: "Mutlu T." <cmtunc at gmail.com> > To: arnaud.quette at free.fr > Cc: > Subject: New NUT HCL entry / (brand)Inform (series)Informer Compact > Date: Fri, 07 Aug 2009 15:31:04

Hi Sergey, 2011/7/15 Sergey Talchuk <tals1975 at gmail.com> > Hi Arnaud, > > both configurations are ok :). Please find the file attached. > logic since the 2nd is automatically guessed from the first using USB Vendor and Product ID ;-) can you please send in upsc, upscmd and upsrw output. and also report the shutdown testing as described here:

Hi All, I have got the Belkin F6S600auUSB UPS working with the blazer_usb driver. I pulled the power to the ups last night and it sent a message to the server saying it was on battery then ran for another 10 minutes and then sent a message to the server telling it to shut down, which it did. upswr did not return anything. [root at verity ~]# upsc ups battery.voltage: 13.50

Hi All, I have got the Belkin F6S600auUSB UPS working with the blazer_usb driver. I pulled the power to the ups last night and it sent a message to the server saying it was on battery then ran for another 10 minutes and then sent a message to the server telling it to shut down, which it did. upswr did not return anything. [root at verity ~]# upsc ups battery.voltage: 13.50

Hey guys, :) recently, I installed Cyberpower PR2200ELCDRT2U, however, I have not managed to get this UPS working with FreeNAS 11, yet. According to compatibility list, PR2200 should work fine, when using powerpanel driver: http://networkupstools.org/ddl/Cyber_Power_Systems/ http://networkupstools.org/ddl/Cyber_Power_Systems/PR2200.html However, when trying to establish a connection between

Thank you for the commands... Please find attached log... Im not sure if the Load.on worked, because in the end I had to manually start the UPS (with button). Anyway, let me know should I need to perform some steps again (probably yes, since I believe it was off). Jakub On 11.03.2015 20:11, hyouko at gmail.com wrote: > 2015-03-11 14:21 GMT+01:00 Jakub Scepka <jakub.scepka at

On Jun 7, 2017, at 1:14 PM, Roger Price wrote: > > 2. On the NAS, use command > > upsrw -s battery.charge.low=80 -u upsmaster -s sekret UPS Robbie, The "upsrw" command contacts upsd, so it sounds like you should be able to add a user to upsd.users on the NAS, and then run something like this on the Mac: upsrw -s battery.charge.low=80 -u upsmaster -s sekret UPS at

Hello, No ttyUSB* device under /dev however the new driver has detected the UPS, the nut services are able to start, just "upsc -l ups" sais unknown error and doesn't return any information. Could be due to the driver unable to detect number of battery packs as reported by the nut-driver.service startup? How can I fix that? root at omv:~# systemctl status nut-driver.service●

http://www.zigor.com/uk/index.php/en/products/upssystems/danubioseries Ships with UPSilon 2000 software, and appears to work with blazer_usb to a certain extent with the following config: [danubio] driver = blazer_usb langid_fix = 0x409 port = stupidly, I seem to have to set this even though it's ignored vendorid=0001 productid=0000 Yes, vendor 0001,

UNITEK Alpha650ipF and Alpha650ipE Build NUT v2.6.4 from sources http://www.networkupstools.org/source/2.6/nut-2.6.4.tar.gz System: RedHat Linux RHEL4 Kernel: 2.6.9-42.0.10.EL (upsc) command output : battery.charge: 100 battery.voltage: 14.30 battery.voltage.high: 13.00 battery.voltage.low: 10.40 battery.voltage.nominal: 12.0 device.mfr: UNITEK device.model: Alph650ipF device.type: ups