search for: ppro2

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

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

...read: 'PR2,400,120,120,10.8,13.6' 9.896482 send: 'RT' 9.927323 read: '053' 9.927433 send: 'SS?' 10.928470 read: timeout (0) 10.928491 qx_process_answer: short reply (pins_shutdown_mode) The set of instcmds looks good: $ upscmd -l ppro2 Instant commands supported on UPS [ppro2]: shutdown.return - Turn off the load and return when power is back shutdown.stayoff - Turn off the load and remain off shutdown.stop - Stop a shutdown in progress test.battery.start - Start a battery test test.battery.start.deep - Start a deep battery test...

Hi All I am connecting a ups via a usb to serial converter. Works fine, however when the converter is unplugged and plugged back in, udev creates another device e.g instead of ttyUSB0 it creates ttyUSB1. Here is the udev rule that I added to the top of the 025_nut-usbups.rules file in order to create a static symlink should udev decide to create the device as either ttyUSB0 or ttyUSB1.