modbus-usb and Smart-UPS 750 - comm lost / restored every 2 seconds

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

modbus-usb and Smart-UPS 750 - comm lost / restored every 2 seconds

Romain Aviolat
Hi there,

I wanted to extract the load of my Smart-UPS 750 with apcupsd, and that kind of info wasn't present with the usb driver:

root@rpi20:~/apcupsd-svn-2376-branches-Branch-3_14# apcaccess
APC      : 001,027,0659
DATE     : 2016-05-20 21:13:45 +0000 
HOSTNAME : rpi20
VERSION  : 3.14.14 (30 May 2015) debian
UPSNAME  : smartups750
CABLE    : USB Cable
DRIVER   : USB UPS Driver
UPSMODE  : Stand Alone
STARTTIME: 2016-05-20 21:13:44 +0000 
MODEL    : Smart-UPS 750
STATUS   : ONLINE
BCHARGE  : 100.0 Percent
TIMELEFT : 103.0 Minutes
MBATTCHG : 5 Percent
MINTIMEL : 3 Minutes
MAXTIME  : 0 Seconds
ALARMDEL : 30 Seconds
BATTV    : 27.0 Volts
NUMXFERS : 0
TONBATT  : 0 Seconds
CUMONBATT: 0 Seconds
XOFFBATT : N/A
STATFLAG : 0x05000008
MANDATE  : 2015-11-11
SERIALNO : 3S1546X01495 
NOMBATTV : 24.0 Volts
FIRMWARE : UPS 09.3 / ID=18
END APC  : 2016-05-20 21:13:51 +0000 

so I decided to try the new usb-modbus driver available with the latest 3.14.13 version.

it's way better:

root@rpi20:~/apcupsd-svn-2376-branches-Branch-3_14# apcaccess
APC      : 001,039,0899
DATE     : 2016-05-20 21:11:24 +0000 
HOSTNAME : rpi20
VERSION  : 3.14.14 (30 May 2015) debian
UPSNAME  : APCUPS
CABLE    : USB Cable
DRIVER   : MODBUS UPS Driver
UPSMODE  : Stand Alone
STARTTIME: 2016-05-20 21:11:18 +0000 
MODEL    : Smart-UPS 750
STATUS   : ONLINE
LINEV    : 234.7 Volts
LOADPCT  : 8.4 Percent
LOADAPNT : 11.7 Percent
BCHARGE  : 100.0 Percent
TIMELEFT : 103.0 Minutes
MBATTCHG : 5 Percent
MINTIMEL : 3 Minutes
MAXTIME  : 0 Seconds
OUTPUTV  : 234.7 Volts
DWAKE    : 0 Seconds
DSHUTD   : 90 Seconds
ITEMP    : 33.3 C
BATTV    : 27.0 Volts
LINEFREQ : 50.0 Hz
OUTCURNT : 0.38 Amps
NUMXFERS : 0
TONBATT  : 0 Seconds
CUMONBATT: 0 Seconds
XOFFBATT : N/A
SELFTEST : ??
STATFLAG : 0x05000008
MANDATE  : 2015-11-11
SERIALNO : 3S1546X01495
BATTDATE : 2015-11-11
NOMOUTV  : 230 Volts
NOMPOWER : 500 Watts
NOMAPNT  : 750 VA
FIRMWARE : UPS 09.3 / 00.4
END APC  : 2016-05-20 21:11:24 +0000 
                                                                              
 But I've got constantly comm lost / restored messages, about every 2 seconds on my console:


Broadcast message from root@rpi20 (somewhere) (Fri May 20 21:11:25 2016):     
                                                                              
Warning communications lost with UPS APCUPS                                   
                                                                              
                                                                              
Broadcast message from root@rpi20 (somewhere) (Fri May 20 21:11:27 2016):     
                                                                              
Communications restored with UPS APCUPS                                       

Here's the output with a good debug:

************************************
root@rpi20:~/apcupsd-svn-2376-branches-Branch-3_14# apcupsd -b -d1000
0.000 apcupsd: apcupsd.c:156 Options parsed.
0.001 apcupsd: apcconfig.c:755 After config scriptdir: "/etc/apcupsd"
0.001 apcupsd: apcconfig.c:756 After config pwrfailpath: "/etc/apcupsd"
0.001 apcupsd: apcconfig.c:757 After config nologinpath: "/etc"
0.001 apcupsd: apcupsd.c:179 Config file /etc/apcupsd/apcupsd.conf processed.
0.001 apcupsd: newups.c:102 write_lock at drivers.c:109
0.001 apcupsd: drivers.c:111 Looking for driver: modbus
0.001 apcupsd: drivers.c:115 Driver dumb is configured.
0.001 apcupsd: drivers.c:115 Driver apcsmart is configured.
0.002 apcupsd: drivers.c:115 Driver net is configured.
0.002 apcupsd: drivers.c:115 Driver usb is configured.
0.002 apcupsd: drivers.c:115 Driver snmplite is configured.
0.002 apcupsd: drivers.c:115 Driver pcnet is configured.
0.002 apcupsd: drivers.c:115 Driver modbus is configured.
0.002 apcupsd: drivers.c:118 Driver modbus found and attached.
0.002 apcupsd: newups.c:108 write_unlock at drivers.c:135
0.002 apcupsd: drivers.c:137 Driver ptr=0x16822b8
0.002 apcupsd: drivers.c:138 Attached to driver: modbus
0.003 apcupsd: apcupsd.c:251 NIS thread started.
0.005 apcupsd: apclog.c:62 apcupsd 3.14.14 (30 May 2015) debian startup succeeded
0.006 apcupsd: apclog.c:62 NIS server startup succeeded
usb_set_debug: Setting debugging level to 10 (on)
0.006 apcupsd: HidUps.cpp:50 Initializing libusb
usb_os_init: Found USB VFS at /dev/bus/usb
usb_os_find_busses: Found 001
0.006 apcupsd: HidUps.cpp:55 Found 1 USB busses
usb_os_find_devices: Found 005 on 001
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 003 on 001
usb_os_find_devices: Found 002 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
0.007 apcupsd: HidUps.cpp:57 Found 4 USB devices
0.007 apcupsd: HidUps.cpp:68 001:005 - 051d:0003
USB error: could not detach kernel driver from interface 0: No data available
0.009 apcupsd: HidUps.cpp:266 Report descriptor:
0.010 apcupsd: HidUps.cpp:267 Dumping 515 bytes @ 0x01684738
0.010 apcupsd: HidUps.cpp:267 00000000  05 84 09 04 a1 01 09 24 a1 02 75 08 95 01 15 00  .......$..u.....
0.010 apcupsd: HidUps.cpp:267 00000010  26 ff 00 85 01 09 fe 79 02 b1 23 85 02 09 ff 79  &......y..#....y
0.010 apcupsd: HidUps.cpp:267 00000020  03 b1 23 85 03 09 fd 79 01 b1 23 05 85 85 04 09  ..#....y..#.....
0.010 apcupsd: HidUps.cpp:267 00000030  8f 79 01 b1 23 85 05 09 89 79 04 b1 23 85 06 09  .y..#....y..#...
0.010 apcupsd: HidUps.cpp:267 00000040  8b b1 23 09 2c b1 23 85 0e 09 83 25 64 b1 23 09  ..#.,.#....%d.#.
0.010 apcupsd: HidUps.cpp:267 00000050  67 b1 23 85 0c 09 66 81 23 09 66 b1 a3 85 10 09  g.#...f.#.f.....
0.011 apcupsd: HidUps.cpp:267 00000060  8d b1 22 09 8e b1 23 85 0f 09 8c b1 a2 85 11 09  .."...#.........
0.011 apcupsd: HidUps.cpp:267 00000070  29 b1 a2 85 09 09 85 75 10 27 ff ff 00 00 b1 a3  )......u.'......
0.011 apcupsd: HidUps.cpp:267 00000080  85 0d 09 68 27 ff ff 00 00 66 01 10 55 00 81 a3  ...h'....f..U...
0.011 apcupsd: HidUps.cpp:267 00000090  09 68 b1 a3 05 84 85 12 09 57 16 ff ff 26 ff 7f  .h.......W...&..
0.011 apcupsd: HidUps.cpp:267 000000a0  b1 a2 85 13 09 55 75 18 17 ff ff ff ff 27 18 c5  .....Uu......'..
0.011 apcupsd: HidUps.cpp:267 000000b0  13 00 b1 a2 05 85 85 08 09 2a 75 10 27 64 05 00  .........*u.'d..
0.011 apcupsd: HidUps.cpp:267 000000c0  00 16 78 00 81 22 09 2a b1 a2 05 84 85 0a 09 40  ..x..".*.......@
0.012 apcupsd: HidUps.cpp:267 000000d0  15 00 27 ff ff 00 00 67 21 d1 f0 00 55 05 b1 23  ..'....g!...U..#
0.012 apcupsd: HidUps.cpp:267 000000e0  85 0b 09 30 b1 a3 85 14 09 5a 75 08 15 01 25 03  ...0.....Zu...%.
0.012 apcupsd: HidUps.cpp:267 000000f0  65 00 55 00 81 22 09 5a b1 a2 09 02 a1 02 85 07  e.U..".Z........
0.012 apcupsd: HidUps.cpp:267 00000100  05 85 09 44 75 01 15 00 25 01 81 a3 09 44 b1 a3  ...Du...%....D..
0.012 apcupsd: HidUps.cpp:267 00000110  09 45 81 a3 09 45 b1 a3 09 d0 81 a3 09 d0 b1 a3  .E...E..........
0.012 apcupsd: HidUps.cpp:267 00000120  09 d1 81 a3 09 d1 b1 a3 09 42 81 a3 09 42 b1 a3  .........B...B..
0.012 apcupsd: HidUps.cpp:267 00000130  05 84 09 68 81 a2 09 68 b1 a2 09 69 81 a3 09 69  ...h...h...i...i
0.013 apcupsd: HidUps.cpp:267 00000140  b1 a3 05 85 09 43 81 a2 09 43 b1 a2 05 84 09 73  .....C...C.....s
0.013 apcupsd: HidUps.cpp:267 00000150  81 a3 09 73 b1 a3 05 85 09 4b 81 a3 09 4b b1 a3  ...s.....K...K..
0.013 apcupsd: HidUps.cpp:267 00000160  05 84 09 65 81 a3 09 65 b1 a3 05 85 09 db 81 a3  ...e...e........
0.013 apcupsd: HidUps.cpp:267 00000170  09 db b1 a3 06 86 ff 09 80 81 a3 09 80 b1 a3 95  ................
0.013 apcupsd: HidUps.cpp:267 00000180  03 81 01 b1 01 c0 c0 06 86 ff 85 89 09 fd 15 00  ................
0.013 apcupsd: HidUps.cpp:267 00000190  26 ff 00 75 08 95 3f 81 02 85 90 09 fc 15 00 26  &..u..?........&
0.013 apcupsd: HidUps.cpp:267 000001a0  ff 00 75 08 95 3f 91 02 85 96 09 f1 15 00 26 01  ..u..?........&.
0.013 apcupsd: HidUps.cpp:267 000001b0  00 75 08 95 3f b1 22 85 8d 09 f7 15 00 26 ff 00  .u..?."......&..
0.014 apcupsd: HidUps.cpp:267 000001c0  75 08 95 02 b1 22 85 8e 09 f6 15 00 26 ff 00 75  u...."......&..u
0.014 apcupsd: HidUps.cpp:267 000001d0  08 95 02 b1 23 85 93 09 f3 15 00 26 ff 00 75 08  ....#......&..u.
0.014 apcupsd: HidUps.cpp:267 000001e0  95 02 b1 22 85 94 09 f2 15 00 26 ff 00 75 08 95  ..."......&..u..
0.014 apcupsd: HidUps.cpp:267 000001f0  02 b1 23 85 92 09 f4 15 00 26 ff 00 75 08 95 02  ..#......&..u...
0.014 apcupsd: HidUps.cpp:267 00000200  b1 23 c0                                         .#.
0.014 apcupsd: ModbusUsbComm.cpp:67 Open: Found ModbusRTUTx in report id 137
0.015 apcupsd: ModbusUsbComm.cpp:76 Open: Found ModbusRTURx in report id 144
0.015 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=532, nregs=16
0.061 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
0.061 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed530f0
0.061 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 02 14 00 10 05 ba                          ........
0.080 apcupsd: ModbusUsbComm.cpp:216 Dumping 37 bytes @ 0x7ed531f0
0.081 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 20 53 6d 61 72 74 2d 55 50 53 01 37 35 30  ...Smart-UPS.750
0.081 apcupsd: ModbusUsbComm.cpp:216 00000010  20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20  ................
0.081 apcupsd: ModbusUsbComm.cpp:216 00000020  20 20 20 31 47                                   ...1G
0.081 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=564, nregs=8
0.128 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
0.128 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed530f0
0.128 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 02 34 00 08 04 7a                          ...4...z
0.145 apcupsd: ModbusUsbComm.cpp:216 Dumping 21 bytes @ 0x7ed531f0
0.146 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 10 33 53 31 35 34 36 58 30 31 34 39 35 20  ...3S1546X01495.
0.146 apcupsd: ModbusUsbComm.cpp:216 00000010  20 00 00 6c 54                                   ...lT
0.146 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=596, nregs=8
0.192 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
0.192 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed530f0
0.192 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 02 54 00 08 04 64                          ...T...d
0.209 apcupsd: ModbusUsbComm.cpp:216 Dumping 21 bytes @ 0x7ed531f0
0.209 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 10 41 50 43 55 50 53 20 20 20 20 20 20 20  ...APCUPS.......
0.210 apcupsd: ModbusUsbComm.cpp:216 00000010  20 20 20 2b 92                                   ...+.
0.210 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=591, nregs=1
0.256 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
0.256 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed530f0
0.256 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 02 4f 00 01 b4 65                          ...O...e
0.273 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed531f0
0.273 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 16 a1 77 9c                             .....w.
0.274 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=595, nregs=1
0.320 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
0.320 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed530f0
0.320 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 02 53 00 01 75 a3                          ...S..u.
0.337 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed531f0
0.337 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 16 a1 77 9c                             .....w.
0.338 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=592, nregs=1
0.383 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
0.384 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed530f0
0.384 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 02 50 00 01 85 a3                          ...P....
0.401 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed531f0
0.401 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 00 20 b9 9c                             .......
0.402 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=516, nregs=8
0.448 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
0.448 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed530f0
0.448 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 02 04 00 08 04 75                          .......u
0.465 apcupsd: ModbusUsbComm.cpp:216 Dumping 21 bytes @ 0x7ed531f0
0.466 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 10 00 00 00 00 00 00 00 00 55 50 53 20 30  ...........UPS.0
0.466 apcupsd: ModbusUsbComm.cpp:216 00000010  39 2e 33 7e 43                                   9.3~C
0.466 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=2048, nregs=2
0.512 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
0.512 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed530f0
0.512 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 08 00 00 02 c6 6b                          .......k
0.529 apcupsd: ModbusUsbComm.cpp:216 Dumping 9 bytes @ 0x7ed531f0
0.530 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 04 30 30 2e 34 e9 4b                       ...00.4.K
0.530 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=589, nregs=1
0.576 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
0.576 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed530f0
0.576 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 02 4d 00 01 15 a5                          ...M....
0.593 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed531f0
0.594 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 01 f4 b8 53                             ......S
0.594 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=588, nregs=1
0.639 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
0.639 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed530f0
0.639 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 02 4c 00 01 44 65                          ...L..De
0.657 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed531f0
0.658 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 02 ee 39 68                             .....9h
0.658 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=1029, nregs=1
0.703 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
0.703 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed530f0
0.703 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 04 05 00 01 95 3b                          .......;
0.721 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed531f0
0.722 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 00 5a 38 7f                             ....Z8.
0.722 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=1030, nregs=1
0.767 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
0.768 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed530f0
0.769 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 04 06 00 01 65 3b                          ......e;
0.785 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed531f0
0.786 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 00 00 b8 44                             ......D
0.787 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=151, nregs=1
0.833 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
0.833 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed530f0
0.834 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 97 00 01 35 e6                          ......5.
0.849 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed531f0
0.850 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 3a ac aa 99                             ...:...
0.851 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=142, nregs=1
0.897 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
0.898 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed530f0
0.898 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 8e 00 01 e4 21                          .......!
0.913 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed531f0
0.914 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 3a ac aa 99                             ...:...
0.915 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=140, nregs=1
0.961 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
0.962 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed530f0
0.962 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 8c 00 01 45 e1                          ......E.
0.977 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed531f0
0.978 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 00 0c b8 41                             ......A
0.979 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=131, nregs=1
1.024 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
1.025 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed530f0
1.025 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 83 00 01 75 e2                          ......u.
1.040 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed531f0
1.041 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 03 60 b8 9c                             ....`..
1.042 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=144, nregs=1
1.087 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
1.087 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed530f0
1.087 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 90 00 01 84 27                          .......'
1.105 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed531f0
1.106 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 18 fa 32 07                             .....2.
1.106 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=135, nregs=1
1.152 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
1.152 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed530f0
1.152 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 87 00 01 34 23                          ......4#
1.169 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed531f0
1.170 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 10 a6 35 fe                             .....5.
1.170 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=130, nregs=1
1.216 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
1.216 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed530f0
1.216 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 82 00 01 24 22                          ......$"
1.233 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed531f0
1.234 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 c8 00 ef 84                             .......
1.234 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=128, nregs=2
1.279 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
1.280 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed530f0
1.280 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 80 00 02 c5 e3                          ........
1.297 apcupsd: ModbusUsbComm.cpp:216 Dumping 9 bytes @ 0x7ed531f0
1.298 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 04 00 00 18 24 f0 28                       ......$.(
1.298 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=0, nregs=2
1.344 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
1.344 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed530f0
1.344 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 00 00 02 c4 0b                          ........
1.361 apcupsd: ModbusUsbComm.cpp:216 Dumping 9 bytes @ 0x7ed531f0
1.362 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 04 00 00 00 02 7b f2                       .......{.
1.362 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=2, nregs=1
1.408 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
1.408 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed530f0
1.408 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 02 00 01 25 ca                          ......%.
1.425 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed531f0
1.426 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 00 08 b9 82                             .......
1.426 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=24, nregs=1
1.472 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
1.472 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed530f0
1.472 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 18 00 01 04 0d                          ........
1.489 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed531f0
1.490 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 00 00 b8 44                             ......D
1.490 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=23, nregs=1
1.536 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
1.536 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed530f0
1.536 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 17 00 01 34 0e                          ......4.
1.554 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed531f0
1.554 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 03 10 b9 78                             ......x
1.554 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=20, nregs=2
1.600 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
1.600 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed530f0
1.600 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 14 00 02 84 0f                          ........
1.618 apcupsd: ModbusUsbComm.cpp:216 Dumping 9 bytes @ 0x7ed531f0
1.618 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 04 00 00 00 00 fa 33                       ........3
1.618 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=22, nregs=1
1.664 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
1.664 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed530f0
1.664 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 16 00 01 65 ce                          ......e.
1.682 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed531f0
1.682 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 00 00 b8 44                             ......D
1.682 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=22, nregs=1
1.728 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
1.728 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed530f0
1.728 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 16 00 01 65 ce                          ......e.
1.746 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed531f0
1.746 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 00 00 b8 44                             ......D
1.746 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=150, nregs=1
1.792 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
1.792 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed530f0
1.792 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 96 00 01 64 26                          ......d&
1.810 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed531f0
1.810 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 00 01 79 84                             .....y.
1.810 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=150, nregs=1
1.856 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
1.856 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed530f0
1.857 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 96 00 01 64 26                          ......d&
1.874 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed531f0
1.874 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 00 01 79 84                             .....y.
1.875 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=136, nregs=1
1.921 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
1.921 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed530f0
1.921 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 88 00 01 04 20                          ........
1.938 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed531f0
1.938 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 08 64 be 6f                             ....d.o
1.938 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=138, nregs=1
1.984 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
1.984 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed530f0
1.984 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 8a 00 01 a5 e0                          ........
2.001 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed531f0
2.001 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 0b b0 be c0                             .......
2.001 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=18, nregs=1
2.047 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
2.047 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed530f0
2.047 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 12 00 01 24 0f                          ......$.
2.065 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed531f0
2.065 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 00 00 b8 44                             ......D
2.065 apcupsd: newups.c:102 write_lock at modbus.cpp:570
2.065 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=532, nregs=16
2.112 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
2.112 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53040
2.112 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 02 14 00 10 05 ba                          ........
2.130 apcupsd: ModbusUsbComm.cpp:216 Dumping 37 bytes @ 0x7ed53140
2.130 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 20 53 6d 61 72 74 2d 55 50 53 01 37 35 30  ...Smart-UPS.750
2.130 apcupsd: ModbusUsbComm.cpp:216 00000010  20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20  ................
2.130 apcupsd: ModbusUsbComm.cpp:216 00000020  20 20 20 31 47                                   ...1G
2.130 apcupsd: modbus.cpp:324 Got CI_UPSMODEL: Smart-UPS 750
2.130 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=564, nregs=8
2.176 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
2.176 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53040
2.176 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 02 34 00 08 04 7a                          ...4...z
2.194 apcupsd: ModbusUsbComm.cpp:216 Dumping 21 bytes @ 0x7ed53140
2.194 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 10 33 53 31 35 34 36 58 30 31 34 39 35 20  ...3S1546X01495.
2.194 apcupsd: ModbusUsbComm.cpp:216 00000010  20 00 00 6c 54                                   ...lT
2.194 apcupsd: modbus.cpp:328 Got CI_SERNO: 3S1546X01495
2.194 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=596, nregs=8
2.240 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
2.240 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53040
2.240 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 02 54 00 08 04 64                          ...T...d
2.258 apcupsd: ModbusUsbComm.cpp:216 Dumping 21 bytes @ 0x7ed53140
2.258 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 10 41 50 43 55 50 53 20 20 20 20 20 20 20  ...APCUPS.......
2.258 apcupsd: ModbusUsbComm.cpp:216 00000010  20 20 20 2b 92                                   ...+.
2.258 apcupsd: modbus.cpp:332 Got CI_IDEN: APCUPS
2.258 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=591, nregs=1
2.304 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
2.304 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53040
2.304 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 02 4f 00 01 b4 65                          ...O...e
2.322 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed53140
2.322 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 16 a1 77 9c                             .....w.
2.322 apcupsd: modbus.cpp:346 Got CI_MANDAT: 5793
2.322 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=595, nregs=1
2.368 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
2.368 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53040
2.368 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 02 53 00 01 75 a3                          ...S..u.
2.386 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed53140
2.386 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 16 a1 77 9c                             .....w.
2.386 apcupsd: modbus.cpp:353 Got CI_BATTDAT: 5793
2.386 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=592, nregs=1
2.432 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
2.432 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53040
2.432 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 02 50 00 01 85 a3                          ...P....
2.450 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed53140
2.450 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 00 20 b9 9c                             .......
2.450 apcupsd: modbus.cpp:360 Got CI_NOMOUTV: 20
2.450 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=516, nregs=8
2.496 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
2.496 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53040
2.496 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 02 04 00 08 04 75                          .......u
2.514 apcupsd: ModbusUsbComm.cpp:216 Dumping 21 bytes @ 0x7ed53140
2.514 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 10 00 00 00 00 00 00 00 00 55 50 53 20 30  ...........UPS.0
2.514 apcupsd: ModbusUsbComm.cpp:216 00000010  39 2e 33 7e 43                                   9.3~C
2.514 apcupsd: modbus.cpp:336 Got CI_REVNO: UPS 09.3
2.514 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=2048, nregs=2
2.560 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
2.560 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53040
2.560 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 08 00 00 02 c6 6b                          .......k
2.578 apcupsd: ModbusUsbComm.cpp:216 Dumping 9 bytes @ 0x7ed53140
2.578 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 04 30 30 2e 34 e9 4b                       ...00.4.K
2.578 apcupsd: modbus.cpp:340 Got MODBUS_MAP_ID: 00.4
2.578 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=589, nregs=1
2.624 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
2.624 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53040
2.624 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 02 4d 00 01 15 a5                          ...M....
2.642 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed53140
2.642 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 01 f4 b8 53                             ......S
2.642 apcupsd: modbus.cpp:379 Got CI_NOMPOWER: 500
2.642 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=588, nregs=1
2.688 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
2.688 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53040
2.688 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 02 4c 00 01 44 65                          ...L..De
2.706 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed53140
2.706 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 02 ee 39 68                             .....9h
2.706 apcupsd: modbus.cpp:383 Got CI_NomApparent: 750
2.706 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=1029, nregs=1
2.752 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
2.752 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53040
2.752 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 04 05 00 01 95 3b                          .......;
2.770 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed53140
2.770 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 00 5a 38 7f                             ....Z8.
2.770 apcupsd: modbus.cpp:387 Got CI_DSHUTD: 90
2.770 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=1030, nregs=1
2.816 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
2.816 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53040
2.816 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 04 06 00 01 65 3b                          ......e;
2.834 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed53140
2.834 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 00 00 b8 44                             ......D
2.834 apcupsd: modbus.cpp:391 Got CI_DWAKE: 0
2.834 apcupsd: newups.c:108 write_unlock at modbus.cpp:572
2.834 apcupsd: newups.c:102 write_lock at modbus.cpp:584
2.834 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=151, nregs=1
2.880 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
2.880 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53050
2.880 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 97 00 01 35 e6                          ......5.
2.898 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed53150
2.898 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 3a ac aa 99                             ...:...
2.898 apcupsd: modbus.cpp:428 Got CI_VLINE: 234.687500
2.899 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=142, nregs=1
2.945 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
2.945 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53050
2.946 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 8e 00 01 e4 21                          .......!
2.962 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed53150
2.962 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 3a ac aa 99                             ...:...
2.962 apcupsd: modbus.cpp:432 Got CI_VOUT: 234.687500
2.963 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=140, nregs=1
3.008 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
3.008 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53050
3.009 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 8c 00 01 45 e1                          ......E.
3.025 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed53150
3.025 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 00 0c b8 41                             ......A
3.025 apcupsd: modbus.cpp:436 Got CI_OutputCurrent: 0.375000
3.026 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=131, nregs=1
3.071 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
3.072 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53050
3.072 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 83 00 01 75 e2                          ......u.
3.089 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed53150
3.089 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 03 60 b8 9c                             ....`..
3.089 apcupsd: modbus.cpp:440 Got CI_VBATT: 27.000000
3.089 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=144, nregs=1
3.136 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
3.136 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53050
3.136 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 90 00 01 84 27                          .......'
3.154 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed53150
3.154 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 18 fa 32 07                             .....2.
3.154 apcupsd: modbus.cpp:444 Got CI_FREQ: 49.953125
3.154 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=135, nregs=1
3.200 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
3.200 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53050
3.200 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 87 00 01 34 23                          ......4#
3.218 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed53150
3.218 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 10 a6 35 fe                             .....5.
3.218 apcupsd: modbus.cpp:448 Got CI_ITEMP: 33.296875
3.218 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=130, nregs=1
3.264 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
3.264 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53050
3.264 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 82 00 01 24 22                          ......$"
3.282 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed53150
3.282 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 c8 00 ef 84                             .......
3.282 apcupsd: modbus.cpp:452 Got CI_BATTLEV: 100.000000
3.282 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=128, nregs=2
3.328 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
3.328 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53050
3.328 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 80 00 02 c5 e3                          ........
3.346 apcupsd: ModbusUsbComm.cpp:216 Dumping 9 bytes @ 0x7ed53150
3.346 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 04 00 00 18 24 f0 28                       ......$.(
3.346 apcupsd: modbus.cpp:456 Got CI_RUNTIM: 6180
3.346 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=0, nregs=2
3.392 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
3.392 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53050
3.392 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 00 00 02 c4 0b                          ........
3.410 apcupsd: ModbusUsbComm.cpp:216 Dumping 9 bytes @ 0x7ed53150
3.410 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 04 00 00 00 02 7b f2                       .......{.
3.410 apcupsd: modbus.cpp:510 Got CI_STATUS: 0x2
3.410 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=2, nregs=1
3.456 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
3.456 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53050
3.456 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 02 00 01 25 ca                          ......%.
3.474 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed53150
3.474 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 00 08 b9 82                             .......
3.474 apcupsd: modbus.cpp:473 Got CI_WHY_BATT: 8
3.474 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=24, nregs=1
3.520 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
3.520 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53050
3.520 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 18 00 01 04 0d                          ........
3.538 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed53150
3.538 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 00 00 b8 44                             ......D
3.538 apcupsd: modbus.cpp:520 Got CI_Calibration: 0x0
3.538 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=23, nregs=1
3.584 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
3.584 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53050
3.584 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 17 00 01 34 0e                          ......4.
3.602 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed53150
3.602 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 03 10 b9 78                             ......x
3.602 apcupsd: modbus.cpp:460 Got CI_ST_STAT: 0x310
3.602 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=20, nregs=2
3.648 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
3.648 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53050
3.648 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 14 00 02 84 0f                          ........
3.666 apcupsd: ModbusUsbComm.cpp:216 Dumping 9 bytes @ 0x7ed53150
3.666 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 04 00 00 00 00 fa 33                       ........3
3.667 apcupsd: modbus.cpp:524 Got CI_Overload: 0x0
3.667 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=22, nregs=1
3.713 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
3.713 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53050
3.714 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 16 00 01 65 ce                          ......e.
3.730 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed53150
3.730 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 00 00 b8 44                             ......D
3.731 apcupsd: modbus.cpp:528 Got CI_NeedReplacement: 0x0
3.731 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=22, nregs=1
3.777 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
3.777 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53050
3.778 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 16 00 01 65 ce                          ......e.
3.794 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed53150
3.794 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 00 00 b8 44                             ......D
3.795 apcupsd: modbus.cpp:532 Got CI_BatteryPresent: 0x0
3.795 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=150, nregs=1
3.841 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
3.841 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53050
3.841 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 96 00 01 64 26                          ......d&
3.858 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed53150
3.858 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 00 01 79 84                             .....y.
3.858 apcupsd: modbus.cpp:536 Got CI_Boost: 0x1
3.858 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=150, nregs=1
3.904 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
3.904 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53050
3.905 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 96 00 01 64 26                          ......d&
3.922 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed53150
3.922 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 00 01 79 84                             .....y.
3.923 apcupsd: modbus.cpp:540 Got CI_Trim: 0x1
3.923 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=136, nregs=1
3.969 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
3.970 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53050
3.970 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 88 00 01 04 20                          ........
3.986 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed53150
3.986 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 08 64 be 6f                             ....d.o
3.987 apcupsd: modbus.cpp:420 Got CI_LOAD: 8.390625
3.987 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=138, nregs=1
4.032 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
4.033 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53050
4.033 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 8a 00 01 a5 e0                          ........
4.049 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed53150
4.049 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 0b b0 be c0                             .......
4.050 apcupsd: modbus.cpp:424 Got CI_LoadApparent: 11.687500
4.050 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=18, nregs=1
4.097 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
4.098 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53050
4.098 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 12 00 01 24 0f                          ......$.
4.114 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed53150
4.114 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 00 00 b8 44                             ......D
4.115 apcupsd: modbus.cpp:395 Got CI_LowBattery: 0
4.115 apcupsd: newups.c:108 write_unlock at modbus.cpp:591
4.116 apcupsd: device.c:238 Before do_action: 0x5000008 (OB:0).
4.116 apcupsd: newups.c:102 write_lock at action.c:355
4.116 apcupsd: newups.c:108 write_unlock at action.c:662
4.117 apcupsd: device.c:244 Before fillUPS: 0x5000008 (OB:0).
4.117 apcupsd: newups.c:102 write_lock at modbus.cpp:584
4.117 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=151, nregs=1
4.164 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
4.164 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53050
4.165 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 97 00 01 35 e6                          ......5.
4.194 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed53150
4.194 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 3a ac aa 99                             ...:...
4.195 apcupsd: modbus.cpp:428 Got CI_VLINE: 234.687500
4.195 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=142, nregs=1
4.241 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
4.242 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53050
4.242 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 8e 00 01 e4 21                          .......!
4.258 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed53150
4.258 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 3a ac aa 99                             ...:...
4.259 apcupsd: modbus.cpp:432 Got CI_VOUT: 234.687500
4.259 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=140, nregs=1
4.305 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
4.306 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53050
4.306 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 8c 00 01 45 e1                          ......E.
4.322 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed53150
4.322 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 00 0c b8 41                             ......A
4.323 apcupsd: modbus.cpp:436 Got CI_OutputCurrent: 0.375000
4.323 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=131, nregs=1
4.369 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
4.370 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53050
4.370 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 83 00 01 75 e2                          ......u.
4.386 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed53150
4.386 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 03 60 b8 9c                             ....`..
4.387 apcupsd: modbus.cpp:440 Got CI_VBATT: 27.000000
4.387 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=144, nregs=1
4.433 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
4.434 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53050
4.434 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 90 00 01 84 27                          .......'
4.450 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed53150
4.450 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 18 fa 32 07                             .....2.
4.451 apcupsd: modbus.cpp:444 Got CI_FREQ: 49.953125
4.451 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=135, nregs=1
4.497 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
4.498 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53050
4.498 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 87 00 01 34 23                          ......4#
4.514 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed53150
4.514 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 10 a6 35 fe                             .....5.
4.515 apcupsd: modbus.cpp:448 Got CI_ITEMP: 33.296875
4.516 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=130, nregs=1
4.562 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
4.562 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53050
4.563 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 82 00 01 24 22                          ......$"
4.578 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed53150
4.578 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 c8 00 ef 84                             .......
4.579 apcupsd: modbus.cpp:452 Got CI_BATTLEV: 100.000000
4.579 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=128, nregs=2
4.625 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
4.626 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53050
4.626 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 80 00 02 c5 e3                          ........
4.642 apcupsd: ModbusUsbComm.cpp:216 Dumping 9 bytes @ 0x7ed53150
4.642 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 04 00 00 18 24 f0 28                       ......$.(
4.643 apcupsd: modbus.cpp:456 Got CI_RUNTIM: 6180
4.643 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=0, nregs=2
4.689 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
4.689 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53050
4.689 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 00 00 02 c4 0b                          ........
4.706 apcupsd: ModbusUsbComm.cpp:216 Dumping 9 bytes @ 0x7ed53150
4.706 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 04 00 00 00 02 7b f2                       .......{.
4.706 apcupsd: modbus.cpp:510 Got CI_STATUS: 0x2
4.706 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=2, nregs=1
4.752 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
4.752 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53050
4.753 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 02 00 01 25 ca                          ......%.
4.770 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed53150
4.770 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 00 08 b9 82                             .......
4.771 apcupsd: modbus.cpp:473 Got CI_WHY_BATT: 8
4.771 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=24, nregs=1
4.817 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
4.818 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53050
4.818 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 18 00 01 04 0d                          ........
4.834 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed53150
4.834 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 00 00 b8 44                             ......D
4.835 apcupsd: modbus.cpp:520 Got CI_Calibration: 0x0
4.835 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=23, nregs=1
4.881 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
4.882 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53050
4.883 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 17 00 01 34 0e                          ......4.
4.898 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed53150
4.898 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 03 10 b9 78                             ......x
4.898 apcupsd: modbus.cpp:460 Got CI_ST_STAT: 0x310
4.898 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=20, nregs=2
4.944 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
4.944 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53050
4.944 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 14 00 02 84 0f                          ........
4.962 apcupsd: ModbusUsbComm.cpp:216 Dumping 9 bytes @ 0x7ed53150
4.962 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 04 00 00 00 00 fa 33                       ........3
4.962 apcupsd: modbus.cpp:524 Got CI_Overload: 0x0
4.962 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=22, nregs=1
5.006 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
5.007 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53050
5.007 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 16 00 01 65 ce                          ......e.
5.025 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed53150
5.025 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 00 00 b8 44                             ......D
5.026 apcupsd: modbus.cpp:528 Got CI_NeedReplacement: 0x0
5.026 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=22, nregs=1
5.072 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
5.072 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53050
5.072 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 16 00 01 65 ce                          ......e.
5.089 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed53150
5.090 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 00 00 b8 44                             ......D
5.090 apcupsd: modbus.cpp:532 Got CI_BatteryPresent: 0x0
5.090 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=150, nregs=1
5.137 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
5.137 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53050
5.137 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 96 00 01 64 26                          ......d&
5.154 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed53150
5.154 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 00 01 79 84                             .....y.
5.155 apcupsd: modbus.cpp:536 Got CI_Boost: 0x1
5.155 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=150, nregs=1
5.200 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
5.201 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53050
5.201 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 96 00 01 64 26                          ......d&
5.218 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed53150
5.218 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 00 01 79 84                             .....y.
5.219 apcupsd: modbus.cpp:540 Got CI_Trim: 0x1
5.219 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=136, nregs=1
5.264 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
5.265 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53050
5.265 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 88 00 01 04 20                          ........
5.282 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed53150
5.282 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 08 64 be 6f                             ....d.o
5.283 apcupsd: modbus.cpp:420 Got CI_LOAD: 8.390625
5.283 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=138, nregs=1
5.328 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
5.329 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53050
5.329 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 8a 00 01 a5 e0                          ........
5.346 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed53150
5.346 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 0b b0 be c0                             .......
5.347 apcupsd: modbus.cpp:424 Got CI_LoadApparent: 11.687500
5.347 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=18, nregs=1
5.392 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
5.393 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53050
5.393 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 12 00 01 24 0f                          ......$.
5.410 apcupsd: ModbusUsbComm.cpp:216 Dumping 7 bytes @ 0x7ed53150
5.410 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 02 00 00 b8 44                             ......D
5.411 apcupsd: modbus.cpp:395 Got CI_LowBattery: 0
5.411 apcupsd: newups.c:108 write_unlock at modbus.cpp:591
5.411 apcupsd: device.c:250 Before do_action: 0x5000008 (OB:0).
5.411 apcupsd: newups.c:102 write_lock at action.c:355
5.412 apcupsd: newups.c:108 write_unlock at action.c:662
5.412 apcupsd: device.c:256 Before do_reports: 0x5000008 (OB:0).
5.412 apcupsd: device.c:264 Before device_check_state: 0x5000008 (OB:0).
5.412 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=0, nregs=2
5.458 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
5.458 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53048
5.459 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 00 00 02 c4 0b                          ........
5.474 apcupsd: ModbusUsbComm.cpp:216 Dumping 9 bytes @ 0x7ed53148
5.474 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 04 00 00 00 02 7b f2                       .......{.
5.475 apcupsd: modbus.cpp:510 Got CI_STATUS: 0x2
6.475 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=0, nregs=2
6.521 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
6.521 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53048
6.522 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 00 00 02 c4 0b                          ........
7.022 apcupsd: modbus.cpp:262 UpdateCi: Failed reading 0/2
7.022 apcupsd: apclog.c:62 Communications with UPS lost.
7.022 apcupsd: action.c:89 calling execute_ups_event commfailure event=0
7.024 apcupsd: apcexec.c:198 exec closed fd 3
7.025 apcupsd: apcexec.c:198 exec closed fd 4
7.025 apcupsd: apcexec.c:198 exec closed fd 5
7.025 apcupsd: apcexec.c:198 exec closed fd 7
/etc/apcupsd/commfailure: 18: /etc/apcupsd/commfailure: mail: not found
7.183 apcupsd: newups.c:90 read_lock at apcstatus.c:50
7.184 apcupsd: newups.c:96 read_unlock at apcstatus.c:384
                                                                              
Broadcast message from root@rpi20 (pts/0) (Fri May 20 21:08:16 2016):         
                                                                              
Warning communications lost with UPS APCUPS                                   
                                                                              
usb_set_debug: Setting debugging level to 10 (on)
8.207 apcupsd: HidUps.cpp:50 Initializing libusb
usb_os_init: Found USB VFS at /dev/bus/usb
usb_os_find_busses: Found 001
8.208 apcupsd: HidUps.cpp:55 Found 0 USB busses
usb_os_find_devices: Found 005 on 001
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 003 on 001
usb_os_find_devices: Found 002 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
8.211 apcupsd: HidUps.cpp:57 Found 0 USB devices
8.211 apcupsd: HidUps.cpp:68 001:005 - 051d:0003
USB error: could not detach kernel driver from interface 0: No data available
8.213 apcupsd: HidUps.cpp:266 Report descriptor:
8.214 apcupsd: HidUps.cpp:267 Dumping 515 bytes @ 0x0168f808
8.214 apcupsd: HidUps.cpp:267 00000000  05 84 09 04 a1 01 09 24 a1 02 75 08 95 01 15 00  .......$..u.....
8.214 apcupsd: HidUps.cpp:267 00000010  26 ff 00 85 01 09 fe 79 02 b1 23 85 02 09 ff 79  &......y..#....y
8.214 apcupsd: HidUps.cpp:267 00000020  03 b1 23 85 03 09 fd 79 01 b1 23 05 85 85 04 09  ..#....y..#.....
8.215 apcupsd: HidUps.cpp:267 00000030  8f 79 01 b1 23 85 05 09 89 79 04 b1 23 85 06 09  .y..#....y..#...
8.215 apcupsd: HidUps.cpp:267 00000040  8b b1 23 09 2c b1 23 85 0e 09 83 25 64 b1 23 09  ..#.,.#....%d.#.
8.215 apcupsd: HidUps.cpp:267 00000050  67 b1 23 85 0c 09 66 81 23 09 66 b1 a3 85 10 09  g.#...f.#.f.....
8.216 apcupsd: HidUps.cpp:267 00000060  8d b1 22 09 8e b1 23 85 0f 09 8c b1 a2 85 11 09  .."...#.........
8.216 apcupsd: HidUps.cpp:267 00000070  29 b1 a2 85 09 09 85 75 10 27 ff ff 00 00 b1 a3  )......u.'......
8.216 apcupsd: HidUps.cpp:267 00000080  85 0d 09 68 27 ff ff 00 00 66 01 10 55 00 81 a3  ...h'....f..U...
8.216 apcupsd: HidUps.cpp:267 00000090  09 68 b1 a3 05 84 85 12 09 57 16 ff ff 26 ff 7f  .h.......W...&..
8.217 apcupsd: HidUps.cpp:267 000000a0  b1 a2 85 13 09 55 75 18 17 ff ff ff ff 27 18 c5  .....Uu......'..
8.217 apcupsd: HidUps.cpp:267 000000b0  13 00 b1 a2 05 85 85 08 09 2a 75 10 27 64 05 00  .........*u.'d..
8.217 apcupsd: HidUps.cpp:267 000000c0  00 16 78 00 81 22 09 2a b1 a2 05 84 85 0a 09 40  ..x..".*.......@
8.217 apcupsd: HidUps.cpp:267 000000d0  15 00 27 ff ff 00 00 67 21 d1 f0 00 55 05 b1 23  ..'....g!...U..#
8.218 apcupsd: HidUps.cpp:267 000000e0  85 0b 09 30 b1 a3 85 14 09 5a 75 08 15 01 25 03  ...0.....Zu...%.
8.218 apcupsd: HidUps.cpp:267 000000f0  65 00 55 00 81 22 09 5a b1 a2 09 02 a1 02 85 07  e.U..".Z........
8.218 apcupsd: HidUps.cpp:267 00000100  05 85 09 44 75 01 15 00 25 01 81 a3 09 44 b1 a3  ...Du...%....D..
8.219 apcupsd: HidUps.cpp:267 00000110  09 45 81 a3 09 45 b1 a3 09 d0 81 a3 09 d0 b1 a3  .E...E..........
8.219 apcupsd: HidUps.cpp:267 00000120  09 d1 81 a3 09 d1 b1 a3 09 42 81 a3 09 42 b1 a3  .........B...B..
8.219 apcupsd: HidUps.cpp:267 00000130  05 84 09 68 81 a2 09 68 b1 a2 09 69 81 a3 09 69  ...h...h...i...i
8.219 apcupsd: HidUps.cpp:267 00000140  b1 a3 05 85 09 43 81 a2 09 43 b1 a2 05 84 09 73  .....C...C.....s
8.220 apcupsd: HidUps.cpp:267 00000150  81 a3 09 73 b1 a3 05 85 09 4b 81 a3 09 4b b1 a3  ...s.....K...K..
8.220 apcupsd: HidUps.cpp:267 00000160  05 84 09 65 81 a3 09 65 b1 a3 05 85 09 db 81 a3  ...e...e........
8.220 apcupsd: HidUps.cpp:267 00000170  09 db b1 a3 06 86 ff 09 80 81 a3 09 80 b1 a3 95  ................
8.221 apcupsd: HidUps.cpp:267 00000180  03 81 01 b1 01 c0 c0 06 86 ff 85 89 09 fd 15 00  ................
8.221 apcupsd: HidUps.cpp:267 00000190  26 ff 00 75 08 95 3f 81 02 85 90 09 fc 15 00 26  &..u..?........&
8.221 apcupsd: HidUps.cpp:267 000001a0  ff 00 75 08 95 3f 91 02 85 96 09 f1 15 00 26 01  ..u..?........&.
8.221 apcupsd: HidUps.cpp:267 000001b0  00 75 08 95 3f b1 22 85 8d 09 f7 15 00 26 ff 00  .u..?."......&..
8.222 apcupsd: HidUps.cpp:267 000001c0  75 08 95 02 b1 22 85 8e 09 f6 15 00 26 ff 00 75  u...."......&..u
8.222 apcupsd: HidUps.cpp:267 000001d0  08 95 02 b1 23 85 93 09 f3 15 00 26 ff 00 75 08  ....#......&..u.
8.222 apcupsd: HidUps.cpp:267 000001e0  95 02 b1 22 85 94 09 f2 15 00 26 ff 00 75 08 95  ..."......&..u..
8.222 apcupsd: HidUps.cpp:267 000001f0  02 b1 23 85 92 09 f4 15 00 26 ff 00 75 08 95 02  ..#......&..u...
8.223 apcupsd: HidUps.cpp:267 00000200  b1 23 c0                                         .#.
8.223 apcupsd: ModbusUsbComm.cpp:67 Open: Found ModbusRTUTx in report id 137
8.223 apcupsd: ModbusUsbComm.cpp:76 Open: Found ModbusRTURx in report id 144
8.224 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=0, nregs=2
8.269 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
8.269 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53048
8.270 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 00 00 02 c4 0b                          ........
8.289 apcupsd: ModbusUsbComm.cpp:216 Dumping 9 bytes @ 0x7ed53148
8.290 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 04 00 00 00 02 7b f2                       .......{.
8.290 apcupsd: modbus.cpp:510 Got CI_STATUS: 0x2
8.290 apcupsd: apclog.c:62 Communications with UPS restored.
8.291 apcupsd: action.c:89 calling execute_ups_event commok event=0
8.292 apcupsd: apcexec.c:198 exec closed fd 3
8.293 apcupsd: apcexec.c:198 exec closed fd 4
8.293 apcupsd: apcexec.c:198 exec closed fd 5
8.293 apcupsd: apcexec.c:198 exec closed fd 6
/etc/apcupsd/commok: 18: /etc/apcupsd/commok: mail: not found
8.412 apcupsd: newups.c:90 read_lock at apcstatus.c:50
8.412 apcupsd: newups.c:96 read_unlock at apcstatus.c:384
                                                                              
Broadcast message from root@rpi20 (pts/0) (Fri May 20 21:08:17 2016):         
                                                                              
Communications restored with UPS APCUPS                                       
                                                                              
9.292 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=0, nregs=2
9.338 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
9.338 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53048
9.338 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 00 00 02 c4 0b                          ........
9.839 apcupsd: modbus.cpp:262 UpdateCi: Failed reading 0/2
9.840 apcupsd: apclog.c:62 Communications with UPS lost.
9.840 apcupsd: action.c:89 calling execute_ups_event commfailure event=0
9.842 apcupsd: apcexec.c:198 exec closed fd 3
9.843 apcupsd: apcexec.c:198 exec closed fd 4
9.843 apcupsd: apcexec.c:198 exec closed fd 5
9.843 apcupsd: apcexec.c:198 exec closed fd 6
/etc/apcupsd/commfailure: 18: /etc/apcupsd/commfailure: mail: not found
9.960 apcupsd: newups.c:90 read_lock at apcstatus.c:50
9.961 apcupsd: newups.c:96 read_unlock at apcstatus.c:384
                                                                              
Broadcast message from root@rpi20 (pts/0) (Fri May 20 21:08:18 2016):         
                                                                              
Warning communications lost with UPS APCUPS                                   
                                                                              
usb_set_debug: Setting debugging level to 10 (on)
11.036 apcupsd: HidUps.cpp:50 Initializing libusb
usb_os_init: Found USB VFS at /dev/bus/usb
usb_os_find_busses: Found 001
11.037 apcupsd: HidUps.cpp:55 Found 0 USB busses
usb_os_find_devices: Found 005 on 001
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 003 on 001
usb_os_find_devices: Found 002 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
11.039 apcupsd: HidUps.cpp:57 Found 0 USB devices
11.040 apcupsd: HidUps.cpp:68 001:005 - 051d:0003
USB error: could not detach kernel driver from interface 0: No data available
11.042 apcupsd: HidUps.cpp:266 Report descriptor:
11.042 apcupsd: HidUps.cpp:267 Dumping 515 bytes @ 0x0168f808
11.043 apcupsd: HidUps.cpp:267 00000000  05 84 09 04 a1 01 09 24 a1 02 75 08 95 01 15 00  .......$..u.....
11.043 apcupsd: HidUps.cpp:267 00000010  26 ff 00 85 01 09 fe 79 02 b1 23 85 02 09 ff 79  &......y..#....y
11.043 apcupsd: HidUps.cpp:267 00000020  03 b1 23 85 03 09 fd 79 01 b1 23 05 85 85 04 09  ..#....y..#.....
11.043 apcupsd: HidUps.cpp:267 00000030  8f 79 01 b1 23 85 05 09 89 79 04 b1 23 85 06 09  .y..#....y..#...
11.044 apcupsd: HidUps.cpp:267 00000040  8b b1 23 09 2c b1 23 85 0e 09 83 25 64 b1 23 09  ..#.,.#....%d.#.
11.044 apcupsd: HidUps.cpp:267 00000050  67 b1 23 85 0c 09 66 81 23 09 66 b1 a3 85 10 09  g.#...f.#.f.....
11.044 apcupsd: HidUps.cpp:267 00000060  8d b1 22 09 8e b1 23 85 0f 09 8c b1 a2 85 11 09  .."...#.........
11.045 apcupsd: HidUps.cpp:267 00000070  29 b1 a2 85 09 09 85 75 10 27 ff ff 00 00 b1 a3  )......u.'......
11.045 apcupsd: HidUps.cpp:267 00000080  85 0d 09 68 27 ff ff 00 00 66 01 10 55 00 81 a3  ...h'....f..U...
11.045 apcupsd: HidUps.cpp:267 00000090  09 68 b1 a3 05 84 85 12 09 57 16 ff ff 26 ff 7f  .h.......W...&..
11.045 apcupsd: HidUps.cpp:267 000000a0  b1 a2 85 13 09 55 75 18 17 ff ff ff ff 27 18 c5  .....Uu......'..
11.046 apcupsd: HidUps.cpp:267 000000b0  13 00 b1 a2 05 85 85 08 09 2a 75 10 27 64 05 00  .........*u.'d..
11.046 apcupsd: HidUps.cpp:267 000000c0  00 16 78 00 81 22 09 2a b1 a2 05 84 85 0a 09 40  ..x..".*.......@
11.046 apcupsd: HidUps.cpp:267 000000d0  15 00 27 ff ff 00 00 67 21 d1 f0 00 55 05 b1 23  ..'....g!...U..#
11.046 apcupsd: HidUps.cpp:267 000000e0  85 0b 09 30 b1 a3 85 14 09 5a 75 08 15 01 25 03  ...0.....Zu...%.
11.047 apcupsd: HidUps.cpp:267 000000f0  65 00 55 00 81 22 09 5a b1 a2 09 02 a1 02 85 07  e.U..".Z........
11.047 apcupsd: HidUps.cpp:267 00000100  05 85 09 44 75 01 15 00 25 01 81 a3 09 44 b1 a3  ...Du...%....D..
11.047 apcupsd: HidUps.cpp:267 00000110  09 45 81 a3 09 45 b1 a3 09 d0 81 a3 09 d0 b1 a3  .E...E..........
11.048 apcupsd: HidUps.cpp:267 00000120  09 d1 81 a3 09 d1 b1 a3 09 42 81 a3 09 42 b1 a3  .........B...B..
11.048 apcupsd: HidUps.cpp:267 00000130  05 84 09 68 81 a2 09 68 b1 a2 09 69 81 a3 09 69  ...h...h...i...i
11.048 apcupsd: HidUps.cpp:267 00000140  b1 a3 05 85 09 43 81 a2 09 43 b1 a2 05 84 09 73  .....C...C.....s
11.048 apcupsd: HidUps.cpp:267 00000150  81 a3 09 73 b1 a3 05 85 09 4b 81 a3 09 4b b1 a3  ...s.....K...K..
11.049 apcupsd: HidUps.cpp:267 00000160  05 84 09 65 81 a3 09 65 b1 a3 05 85 09 db 81 a3  ...e...e........
11.049 apcupsd: HidUps.cpp:267 00000170  09 db b1 a3 06 86 ff 09 80 81 a3 09 80 b1 a3 95  ................
11.049 apcupsd: HidUps.cpp:267 00000180  03 81 01 b1 01 c0 c0 06 86 ff 85 89 09 fd 15 00  ................
11.049 apcupsd: HidUps.cpp:267 00000190  26 ff 00 75 08 95 3f 81 02 85 90 09 fc 15 00 26  &..u..?........&
11.050 apcupsd: HidUps.cpp:267 000001a0  ff 00 75 08 95 3f 91 02 85 96 09 f1 15 00 26 01  ..u..?........&.
11.050 apcupsd: HidUps.cpp:267 000001b0  00 75 08 95 3f b1 22 85 8d 09 f7 15 00 26 ff 00  .u..?."......&..
11.050 apcupsd: HidUps.cpp:267 000001c0  75 08 95 02 b1 22 85 8e 09 f6 15 00 26 ff 00 75  u...."......&..u
11.051 apcupsd: HidUps.cpp:267 000001d0  08 95 02 b1 23 85 93 09 f3 15 00 26 ff 00 75 08  ....#......&..u.
11.051 apcupsd: HidUps.cpp:267 000001e0  95 02 b1 22 85 94 09 f2 15 00 26 ff 00 75 08 95  ..."......&..u..
11.051 apcupsd: HidUps.cpp:267 000001f0  02 b1 23 85 92 09 f4 15 00 26 ff 00 75 08 95 02  ..#......&..u...
11.051 apcupsd: HidUps.cpp:267 00000200  b1 23 c0                                         .#.
11.052 apcupsd: ModbusUsbComm.cpp:67 Open: Found ModbusRTUTx in report id 137
11.052 apcupsd: ModbusUsbComm.cpp:76 Open: Found ModbusRTURx in report id 144
11.052 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=0, nregs=2
11.099 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
11.099 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53048
11.099 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 00 00 02 c4 0b                          ........
11.120 apcupsd: ModbusUsbComm.cpp:216 Dumping 9 bytes @ 0x7ed53148
11.120 apcupsd: ModbusUsbComm.cpp:216 00000000  01 03 04 00 00 00 02 7b f2                       .......{.
11.120 apcupsd: modbus.cpp:510 Got CI_STATUS: 0x2
11.120 apcupsd: apclog.c:62 Communications with UPS restored.
11.120 apcupsd: action.c:89 calling execute_ups_event commok event=0
11.121 apcupsd: apcexec.c:198 exec closed fd 3
11.122 apcupsd: apcexec.c:198 exec closed fd 4
11.122 apcupsd: apcexec.c:198 exec closed fd 5
11.122 apcupsd: apcexec.c:198 exec closed fd 6
/etc/apcupsd/commok: 18: /etc/apcupsd/commok: mail: not found
11.239 apcupsd: newups.c:90 read_lock at apcstatus.c:50
11.239 apcupsd: newups.c:96 read_unlock at apcstatus.c:384
                                                                              
Broadcast message from root@rpi20 (pts/0) (Fri May 20 21:08:20 2016):         
                                                                              
Communications restored with UPS APCUPS                                       
                                                                              
12.121 apcupsd: ModbusComm.cpp:48 ReadRegister: reg=0, nregs=2
12.167 apcupsd: ModbusUsbComm.cpp:105 ModbusTx: Sending frame
12.167 apcupsd: ModbusUsbComm.cpp:106 Dumping 8 bytes @ 0x7ed53048
12.167 apcupsd: ModbusUsbComm.cpp:106 00000000  01 03 00 00 00 02 c4 0b                          ........
12.668 apcupsd: modbus.cpp:262 UpdateCi: Failed reading 0/2
12.668 apcupsd: apclog.c:62 Communications with UPS lost.
12.668 apcupsd: action.c:89 calling execute_ups_event commfailure event=0
12.670 apcupsd: apcexec.c:198 exec closed fd 3
12.670 apcupsd: apcexec.c:198 exec closed fd 4
12.670 apcupsd: apcexec.c:198 exec closed fd 5
12.670 apcupsd: apcexec.c:198 exec closed fd 6
/etc/apcupsd/commfailure: 18: /etc/apcupsd/commfailure: mail: not found
12.786 apcupsd: newups.c:90 read_lock at apcstatus.c:50
12.787 apcupsd: newups.c:96 read_unlock at apcstatus.c:384
                                                                              
Broadcast message from root@rpi20 (pts/0) (Fri May 20 21:08:21 2016):         
************************************

I tried to compile the latest version from the trunk r2376 but the problem persist.

Any idea ?

Thanks for your help,

Romain

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Apcupsd-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users
Reply | Threaded
Open this post in threaded view
|

Re: modbus-usb and Smart-UPS 750 - comm lost / restored every 2 seconds

Adam Kropelin-3
Try the latest released-but-not-yet-announced 3.14.14. That has some improvements to modbus-usb that are likely to help.

--Adam

On Tue, Jun 7, 2016 at 2:14 PM, Romain Aviolat <[hidden email]> wrote:
Hi there,

I wanted to extract the load of my Smart-UPS 750 with apcupsd, and that kind of info wasn't present with the usb driver:

root@rpi20:~/apcupsd-svn-2376-branches-Branch-3_14# apcaccess
APC      : 001,027,0659
DATE     : 2016-05-20 21:13:45 +0000 
HOSTNAME : rpi20
VERSION  : 3.14.14 (30 May 2015) debian
UPSNAME  : smartups750
CABLE    : USB Cable
DRIVER   : USB UPS Driver
UPSMODE  : Stand Alone
STARTTIME: 2016-05-20 21:13:44 +0000 
MODEL    : Smart-UPS 750
STATUS   : ONLINE
BCHARGE  : 100.0 Percent
TIMELEFT : 103.0 Minutes
MBATTCHG : 5 Percent
MINTIMEL : 3 Minutes
MAXTIME  : 0 Seconds
ALARMDEL : 30 Seconds
BATTV    : 27.0 Volts
NUMXFERS : 0
TONBATT  : 0 Seconds
CUMONBATT: 0 Seconds
XOFFBATT : N/A
STATFLAG : 0x05000008
MANDATE  : 2015-11-11
SERIALNO : 3S1546X01495 
NOMBATTV : 24.0 Volts
FIRMWARE : UPS 09.3 / ID=18
END APC  : 2016-05-20 21:13:51 +0000 

so I decided to try the new usb-modbus driver available with the latest 3.14.13 version.

it's way better:

root@rpi20:~/apcupsd-svn-2376-branches-Branch-3_14# apcaccess
APC      : 001,039,0899
DATE     : 2016-05-20 21:11:24 +0000 
HOSTNAME : rpi20
VERSION  : 3.14.14 (30 May 2015) debian
UPSNAME  : APCUPS
CABLE    : USB Cable
DRIVER   : MODBUS UPS Driver
UPSMODE  : Stand Alone
STARTTIME: 2016-05-20 21:11:18 +0000 
MODEL    : Smart-UPS 750
STATUS   : ONLINE
LINEV    : 234.7 Volts
LOADPCT  : 8.4 Percent
LOADAPNT : 11.7 Percent
BCHARGE  : 100.0 Percent
TIMELEFT : 103.0 Minutes
MBATTCHG : 5 Percent
MINTIMEL : 3 Minutes
MAXTIME  : 0 Seconds
OUTPUTV  : 234.7 Volts
DWAKE    : 0 Seconds
DSHUTD   : 90 Seconds
ITEMP    : 33.3 C
BATTV    : 27.0 Volts
LINEFREQ : 50.0 Hz
OUTCURNT : 0.38 Amps
NUMXFERS : 0
TONBATT  : 0 Seconds
CUMONBATT: 0 Seconds
XOFFBATT : N/A
SELFTEST : ??
STATFLAG : 0x05000008
MANDATE  : 2015-11-11
SERIALNO : 3S1546X01495
BATTDATE : 2015-11-11
NOMOUTV  : 230 Volts
NOMPOWER : 500 Watts
NOMAPNT  : 750 VA
FIRMWARE : UPS 09.3 / 00.4
END APC  : 2016-05-20 21:11:24 +0000 
                                                                              
 But I've got constantly comm lost / restored messages, about every 2 seconds on my console:


Broadcast message from root@rpi20 (somewhere) (Fri May 20 21:11:25 2016):     
                                                                              
Warning communications lost with UPS APCUPS                                   
                                                                              
                                                                              
Broadcast message from root@rpi20 (somewhere) (Fri May 20 21:11:27 2016):     
                                                                              
Communications restored with UPS APCUPS                                       


------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Apcupsd-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users
Reply | Threaded
Open this post in threaded view
|

Re: modbus-usb and Smart-UPS 750 - comm lost / restored every 2 seconds

Romain Aviolat
Yep that's what I tried, the logs that I sent are from the 3.14.14 version.

On Tue, Jun 7, 2016 at 8:35 PM, Adam Kropelin <[hidden email]> wrote:
Try the latest released-but-not-yet-announced 3.14.14. That has some improvements to modbus-usb that are likely to help.

--Adam

On Tue, Jun 7, 2016 at 2:14 PM, Romain Aviolat <[hidden email]> wrote:
Hi there,

I wanted to extract the load of my Smart-UPS 750 with apcupsd, and that kind of info wasn't present with the usb driver:

root@rpi20:~/apcupsd-svn-2376-branches-Branch-3_14# apcaccess
APC      : 001,027,0659
DATE     : 2016-05-20 21:13:45 +0000 
HOSTNAME : rpi20
VERSION  : 3.14.14 (30 May 2015) debian
UPSNAME  : smartups750
CABLE    : USB Cable
DRIVER   : USB UPS Driver
UPSMODE  : Stand Alone
STARTTIME: 2016-05-20 21:13:44 +0000 
MODEL    : Smart-UPS 750
STATUS   : ONLINE
BCHARGE  : 100.0 Percent
TIMELEFT : 103.0 Minutes
MBATTCHG : 5 Percent
MINTIMEL : 3 Minutes
MAXTIME  : 0 Seconds
ALARMDEL : 30 Seconds
BATTV    : 27.0 Volts
NUMXFERS : 0
TONBATT  : 0 Seconds
CUMONBATT: 0 Seconds
XOFFBATT : N/A
STATFLAG : 0x05000008
MANDATE  : 2015-11-11
SERIALNO : 3S1546X01495 
NOMBATTV : 24.0 Volts
FIRMWARE : UPS 09.3 / ID=18
END APC  : 2016-05-20 21:13:51 +0000 

so I decided to try the new usb-modbus driver available with the latest 3.14.13 version.

it's way better:

root@rpi20:~/apcupsd-svn-2376-branches-Branch-3_14# apcaccess
APC      : 001,039,0899
DATE     : 2016-05-20 21:11:24 +0000 
HOSTNAME : rpi20
VERSION  : 3.14.14 (30 May 2015) debian
UPSNAME  : APCUPS
CABLE    : USB Cable
DRIVER   : MODBUS UPS Driver
UPSMODE  : Stand Alone
STARTTIME: 2016-05-20 21:11:18 +0000 
MODEL    : Smart-UPS 750
STATUS   : ONLINE
LINEV    : 234.7 Volts
LOADPCT  : 8.4 Percent
LOADAPNT : 11.7 Percent
BCHARGE  : 100.0 Percent
TIMELEFT : 103.0 Minutes
MBATTCHG : 5 Percent
MINTIMEL : 3 Minutes
MAXTIME  : 0 Seconds
OUTPUTV  : 234.7 Volts
DWAKE    : 0 Seconds
DSHUTD   : 90 Seconds
ITEMP    : 33.3 C
BATTV    : 27.0 Volts
LINEFREQ : 50.0 Hz
OUTCURNT : 0.38 Amps
NUMXFERS : 0
TONBATT  : 0 Seconds
CUMONBATT: 0 Seconds
XOFFBATT : N/A
SELFTEST : ??
STATFLAG : 0x05000008
MANDATE  : 2015-11-11
SERIALNO : 3S1546X01495
BATTDATE : 2015-11-11
NOMOUTV  : 230 Volts
NOMPOWER : 500 Watts
NOMAPNT  : 750 VA
FIRMWARE : UPS 09.3 / 00.4
END APC  : 2016-05-20 21:11:24 +0000 
                                                                              
 But I've got constantly comm lost / restored messages, about every 2 seconds on my console:


Broadcast message from root@rpi20 (somewhere) (Fri May 20 21:11:25 2016):     
                                                                              
Warning communications lost with UPS APCUPS                                   
                                                                              
                                                                              
Broadcast message from root@rpi20 (somewhere) (Fri May 20 21:11:27 2016):     
                                                                              
Communications restored with UPS APCUPS                                       


------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Apcupsd-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users



------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Apcupsd-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users
Reply | Threaded
Open this post in threaded view
|

Re: modbus-usb and Smart-UPS 750 - comm lost / restored every 2 seconds

Adam Kropelin-3
In that case, try tags/Release-3_14_13 to see if the new modbus-usb is actually the source of the problem.


On Tue, Jun 7, 2016 at 2:39 PM, Romain Aviolat <[hidden email]> wrote:
Yep that's what I tried, the logs that I sent are from the 3.14.14 version.

On Tue, Jun 7, 2016 at 8:35 PM, Adam Kropelin <[hidden email]> wrote:
Try the latest released-but-not-yet-announced 3.14.14. That has some improvements to modbus-usb that are likely to help.

--Adam

On Tue, Jun 7, 2016 at 2:14 PM, Romain Aviolat <[hidden email]> wrote:
Hi there,

I wanted to extract the load of my Smart-UPS 750 with apcupsd, and that kind of info wasn't present with the usb driver:

root@rpi20:~/apcupsd-svn-2376-branches-Branch-3_14# apcaccess
APC      : 001,027,0659
DATE     : 2016-05-20 21:13:45 +0000 
HOSTNAME : rpi20
VERSION  : 3.14.14 (30 May 2015) debian
UPSNAME  : smartups750
CABLE    : USB Cable
DRIVER   : USB UPS Driver
UPSMODE  : Stand Alone
STARTTIME: 2016-05-20 21:13:44 +0000 
MODEL    : Smart-UPS 750
STATUS   : ONLINE
BCHARGE  : 100.0 Percent
TIMELEFT : 103.0 Minutes
MBATTCHG : 5 Percent
MINTIMEL : 3 Minutes
MAXTIME  : 0 Seconds
ALARMDEL : 30 Seconds
BATTV    : 27.0 Volts
NUMXFERS : 0
TONBATT  : 0 Seconds
CUMONBATT: 0 Seconds
XOFFBATT : N/A
STATFLAG : 0x05000008
MANDATE  : 2015-11-11
SERIALNO : 3S1546X01495 
NOMBATTV : 24.0 Volts
FIRMWARE : UPS 09.3 / ID=18
END APC  : 2016-05-20 21:13:51 +0000 

so I decided to try the new usb-modbus driver available with the latest 3.14.13 version.

it's way better:

root@rpi20:~/apcupsd-svn-2376-branches-Branch-3_14# apcaccess
APC      : 001,039,0899
DATE     : 2016-05-20 21:11:24 +0000 
HOSTNAME : rpi20
VERSION  : 3.14.14 (30 May 2015) debian
UPSNAME  : APCUPS
CABLE    : USB Cable
DRIVER   : MODBUS UPS Driver
UPSMODE  : Stand Alone
STARTTIME: 2016-05-20 21:11:18 +0000 
MODEL    : Smart-UPS 750
STATUS   : ONLINE
LINEV    : 234.7 Volts
LOADPCT  : 8.4 Percent
LOADAPNT : 11.7 Percent
BCHARGE  : 100.0 Percent
TIMELEFT : 103.0 Minutes
MBATTCHG : 5 Percent
MINTIMEL : 3 Minutes
MAXTIME  : 0 Seconds
OUTPUTV  : 234.7 Volts
DWAKE    : 0 Seconds
DSHUTD   : 90 Seconds
ITEMP    : 33.3 C
BATTV    : 27.0 Volts
LINEFREQ : 50.0 Hz
OUTCURNT : 0.38 Amps
NUMXFERS : 0
TONBATT  : 0 Seconds
CUMONBATT: 0 Seconds
XOFFBATT : N/A
SELFTEST : ??
STATFLAG : 0x05000008
MANDATE  : 2015-11-11
SERIALNO : 3S1546X01495
BATTDATE : 2015-11-11
NOMOUTV  : 230 Volts
NOMPOWER : 500 Watts
NOMAPNT  : 750 VA
FIRMWARE : UPS 09.3 / 00.4
END APC  : 2016-05-20 21:11:24 +0000 
                                                                              
 But I've got constantly comm lost / restored messages, about every 2 seconds on my console:


Broadcast message from root@rpi20 (somewhere) (Fri May 20 21:11:25 2016):     
                                                                              
Warning communications lost with UPS APCUPS                                   
                                                                              
                                                                              
Broadcast message from root@rpi20 (somewhere) (Fri May 20 21:11:27 2016):     
                                                                              
Communications restored with UPS APCUPS                                       



------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Apcupsd-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users
Reply | Threaded
Open this post in threaded view
|

Re: modbus-usb and Smart-UPS 750 - comm lost / restored every 2 seconds

Romain Aviolat
Adam,

exactly the same issue with 3.14.13

Romain

**********************
10.326 apcupsd: ModbusUsbComm.cpp:100 ModbusTx: Sending frame
10.327 apcupsd: apclog.c:179 Dumping 8 bytes @ 0x7ea1a070
10.327 apcupsd: apclog.c:212 00000000  01 03 00 00 00 02 c4 0b                          ........
10.829 apcupsd: modbus.cpp:257 UpdateCi: Failed reading 0/2
10.829 apcupsd: apclog.c:62 Communications with UPS lost.
10.830 apcupsd: action.c:89 calling execute_ups_event commfailure event=0
10.833 apcupsd: apcexec.c:198 exec closed fd 3
10.833 apcupsd: apcexec.c:198 exec closed fd 4
10.833 apcupsd: apcexec.c:198 exec closed fd 5
10.833 apcupsd: apcexec.c:198 exec closed fd 7
/etc/apcupsd/commfailure: 18: /etc/apcupsd/commfailure: mail: not found
10.987 apcupsd: newups.c:90 read_lock at apcstatus.c:50
10.988 apcupsd: newups.c:96 read_unlock at apcstatus.c:375
                                                                              
Broadcast message from root@rpi20 (pts/0) (Tue Jun  7 18:58:09 2016):         
                                                                              
Warning communications lost with UPS APCUPS                                   
**********************


On Tue, Jun 7, 2016 at 8:43 PM, Adam Kropelin <[hidden email]> wrote:
In that case, try tags/Release-3_14_13 to see if the new modbus-usb is actually the source of the problem.


On Tue, Jun 7, 2016 at 2:39 PM, Romain Aviolat <[hidden email]> wrote:
Yep that's what I tried, the logs that I sent are from the 3.14.14 version.

On Tue, Jun 7, 2016 at 8:35 PM, Adam Kropelin <[hidden email]> wrote:
Try the latest released-but-not-yet-announced 3.14.14. That has some improvements to modbus-usb that are likely to help.

--Adam

On Tue, Jun 7, 2016 at 2:14 PM, Romain Aviolat <[hidden email]> wrote:
Hi there,

I wanted to extract the load of my Smart-UPS 750 with apcupsd, and that kind of info wasn't present with the usb driver:

root@rpi20:~/apcupsd-svn-2376-branches-Branch-3_14# apcaccess
APC      : 001,027,0659
DATE     : 2016-05-20 21:13:45 +0000 
HOSTNAME : rpi20
VERSION  : 3.14.14 (30 May 2015) debian
UPSNAME  : smartups750
CABLE    : USB Cable
DRIVER   : USB UPS Driver
UPSMODE  : Stand Alone
STARTTIME: 2016-05-20 21:13:44 +0000 
MODEL    : Smart-UPS 750
STATUS   : ONLINE
BCHARGE  : 100.0 Percent
TIMELEFT : 103.0 Minutes
MBATTCHG : 5 Percent
MINTIMEL : 3 Minutes
MAXTIME  : 0 Seconds
ALARMDEL : 30 Seconds
BATTV    : 27.0 Volts
NUMXFERS : 0
TONBATT  : 0 Seconds
CUMONBATT: 0 Seconds
XOFFBATT : N/A
STATFLAG : 0x05000008
MANDATE  : 2015-11-11
SERIALNO : 3S1546X01495 
NOMBATTV : 24.0 Volts
FIRMWARE : UPS 09.3 / ID=18
END APC  : 2016-05-20 21:13:51 +0000 

so I decided to try the new usb-modbus driver available with the latest 3.14.13 version.

it's way better:

root@rpi20:~/apcupsd-svn-2376-branches-Branch-3_14# apcaccess
APC      : 001,039,0899
DATE     : 2016-05-20 21:11:24 +0000 
HOSTNAME : rpi20
VERSION  : 3.14.14 (30 May 2015) debian
UPSNAME  : APCUPS
CABLE    : USB Cable
DRIVER   : MODBUS UPS Driver
UPSMODE  : Stand Alone
STARTTIME: 2016-05-20 21:11:18 +0000 
MODEL    : Smart-UPS 750
STATUS   : ONLINE
LINEV    : 234.7 Volts
LOADPCT  : 8.4 Percent
LOADAPNT : 11.7 Percent
BCHARGE  : 100.0 Percent
TIMELEFT : 103.0 Minutes
MBATTCHG : 5 Percent
MINTIMEL : 3 Minutes
MAXTIME  : 0 Seconds
OUTPUTV  : 234.7 Volts
DWAKE    : 0 Seconds
DSHUTD   : 90 Seconds
ITEMP    : 33.3 C
BATTV    : 27.0 Volts
LINEFREQ : 50.0 Hz
OUTCURNT : 0.38 Amps
NUMXFERS : 0
TONBATT  : 0 Seconds
CUMONBATT: 0 Seconds
XOFFBATT : N/A
SELFTEST : ??
STATFLAG : 0x05000008
MANDATE  : 2015-11-11
SERIALNO : 3S1546X01495
BATTDATE : 2015-11-11
NOMOUTV  : 230 Volts
NOMPOWER : 500 Watts
NOMAPNT  : 750 VA
FIRMWARE : UPS 09.3 / 00.4
END APC  : 2016-05-20 21:11:24 +0000 
                                                                              
 But I've got constantly comm lost / restored messages, about every 2 seconds on my console:


Broadcast message from root@rpi20 (somewhere) (Fri May 20 21:11:25 2016):     
                                                                              
Warning communications lost with UPS APCUPS                                   
                                                                              
                                                                              
Broadcast message from root@rpi20 (somewhere) (Fri May 20 21:11:27 2016):     
                                                                              
Communications restored with UPS APCUPS                                       



------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Apcupsd-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users



------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Apcupsd-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users
Reply | Threaded
Open this post in threaded view
|

Re: modbus-usb and Smart-UPS 750 - comm lost / restored every 2 seconds

Adam Kropelin-3
Hmmm... So it appears that whenever apcupsd sends the UPS the same command twice in a row, the second one never elicits a response. I'd guess that's because the UPS never receives the second command. This could be a bug either in the USB drivers for your PC or a bug in the UPS firmware. Can you check for an UPS firmware upgrade?

On Tue, Jun 7, 2016 at 3:02 PM, Romain Aviolat <[hidden email]> wrote:
Adam,

exactly the same issue with 3.14.13

Romain

**********************
10.326 apcupsd: ModbusUsbComm.cpp:100 ModbusTx: Sending frame
10.327 apcupsd: apclog.c:179 Dumping 8 bytes @ 0x7ea1a070
10.327 apcupsd: apclog.c:212 00000000  01 03 00 00 00 02 c4 0b                          ........
10.829 apcupsd: modbus.cpp:257 UpdateCi: Failed reading 0/2
10.829 apcupsd: apclog.c:62 Communications with UPS lost.
10.830 apcupsd: action.c:89 calling execute_ups_event commfailure event=0
10.833 apcupsd: apcexec.c:198 exec closed fd 3
10.833 apcupsd: apcexec.c:198 exec closed fd 4
10.833 apcupsd: apcexec.c:198 exec closed fd 5
10.833 apcupsd: apcexec.c:198 exec closed fd 7
/etc/apcupsd/commfailure: 18: /etc/apcupsd/commfailure: mail: not found
10.987 apcupsd: newups.c:90 read_lock at apcstatus.c:50
10.988 apcupsd: newups.c:96 read_unlock at apcstatus.c:375
                                                                              
Broadcast message from root@rpi20 (pts/0) (Tue Jun  7 18:58:09 2016):         
                                                                              
Warning communications lost with UPS APCUPS                                   
**********************


On Tue, Jun 7, 2016 at 8:43 PM, Adam Kropelin <[hidden email]> wrote:
In that case, try tags/Release-3_14_13 to see if the new modbus-usb is actually the source of the problem.


On Tue, Jun 7, 2016 at 2:39 PM, Romain Aviolat <[hidden email]> wrote:
Yep that's what I tried, the logs that I sent are from the 3.14.14 version.

On Tue, Jun 7, 2016 at 8:35 PM, Adam Kropelin <[hidden email]> wrote:
Try the latest released-but-not-yet-announced 3.14.14. That has some improvements to modbus-usb that are likely to help.

--Adam

On Tue, Jun 7, 2016 at 2:14 PM, Romain Aviolat <[hidden email]> wrote:
Hi there,

I wanted to extract the load of my Smart-UPS 750 with apcupsd, and that kind of info wasn't present with the usb driver:

root@rpi20:~/apcupsd-svn-2376-branches-Branch-3_14# apcaccess
APC      : 001,027,0659
DATE     : 2016-05-20 21:13:45 +0000 
HOSTNAME : rpi20
VERSION  : 3.14.14 (30 May 2015) debian
UPSNAME  : smartups750
CABLE    : USB Cable
DRIVER   : USB UPS Driver
UPSMODE  : Stand Alone
STARTTIME: 2016-05-20 21:13:44 +0000 
MODEL    : Smart-UPS 750
STATUS   : ONLINE
BCHARGE  : 100.0 Percent
TIMELEFT : 103.0 Minutes
MBATTCHG : 5 Percent
MINTIMEL : 3 Minutes
MAXTIME  : 0 Seconds
ALARMDEL : 30 Seconds
BATTV    : 27.0 Volts
NUMXFERS : 0
TONBATT  : 0 Seconds
CUMONBATT: 0 Seconds
XOFFBATT : N/A
STATFLAG : 0x05000008
MANDATE  : 2015-11-11
SERIALNO : 3S1546X01495 
NOMBATTV : 24.0 Volts
FIRMWARE : UPS 09.3 / ID=18
END APC  : 2016-05-20 21:13:51 +0000 

so I decided to try the new usb-modbus driver available with the latest 3.14.13 version.

it's way better:

root@rpi20:~/apcupsd-svn-2376-branches-Branch-3_14# apcaccess
APC      : 001,039,0899
DATE     : 2016-05-20 21:11:24 +0000 
HOSTNAME : rpi20
VERSION  : 3.14.14 (30 May 2015) debian
UPSNAME  : APCUPS
CABLE    : USB Cable
DRIVER   : MODBUS UPS Driver
UPSMODE  : Stand Alone
STARTTIME: 2016-05-20 21:11:18 +0000 
MODEL    : Smart-UPS 750
STATUS   : ONLINE
LINEV    : 234.7 Volts
LOADPCT  : 8.4 Percent
LOADAPNT : 11.7 Percent
BCHARGE  : 100.0 Percent
TIMELEFT : 103.0 Minutes
MBATTCHG : 5 Percent
MINTIMEL : 3 Minutes
MAXTIME  : 0 Seconds
OUTPUTV  : 234.7 Volts
DWAKE    : 0 Seconds
DSHUTD   : 90 Seconds
ITEMP    : 33.3 C
BATTV    : 27.0 Volts
LINEFREQ : 50.0 Hz
OUTCURNT : 0.38 Amps
NUMXFERS : 0
TONBATT  : 0 Seconds
CUMONBATT: 0 Seconds
XOFFBATT : N/A
SELFTEST : ??
STATFLAG : 0x05000008
MANDATE  : 2015-11-11
SERIALNO : 3S1546X01495
BATTDATE : 2015-11-11
NOMOUTV  : 230 Volts
NOMPOWER : 500 Watts
NOMAPNT  : 750 VA
FIRMWARE : UPS 09.3 / 00.4
END APC  : 2016-05-20 21:11:24 +0000 
                                                                              
 But I've got constantly comm lost / restored messages, about every 2 seconds on my console:


Broadcast message from root@rpi20 (somewhere) (Fri May 20 21:11:25 2016):     
                                                                              
Warning communications lost with UPS APCUPS                                   
                                                                              
                                                                              
Broadcast message from root@rpi20 (somewhere) (Fri May 20 21:11:27 2016):     
                                                                              
Communications restored with UPS APCUPS                                       



------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Apcupsd-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users



------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Apcupsd-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users



------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Apcupsd-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users
Reply | Threaded
Open this post in threaded view
|

Re: modbus-usb and Smart-UPS 750 - comm lost / restored every 2 seconds

Romain Aviolat
it looks like I already have the latest version out there: FIRMWARE : UPS 09.3 / 00.

currently the UPS is connected to a raspberrypi, maybe I could try to connect it to a "regular" x86 machine ?


On Tue, Jun 7, 2016 at 9:38 PM, Adam Kropelin <[hidden email]> wrote:
Hmmm... So it appears that whenever apcupsd sends the UPS the same command twice in a row, the second one never elicits a response. I'd guess that's because the UPS never receives the second command. This could be a bug either in the USB drivers for your PC or a bug in the UPS firmware. Can you check for an UPS firmware upgrade?

On Tue, Jun 7, 2016 at 3:02 PM, Romain Aviolat <[hidden email]> wrote:
Adam,

exactly the same issue with 3.14.13

Romain

**********************
10.326 apcupsd: ModbusUsbComm.cpp:100 ModbusTx: Sending frame
10.327 apcupsd: apclog.c:179 Dumping 8 bytes @ 0x7ea1a070
10.327 apcupsd: apclog.c:212 00000000  01 03 00 00 00 02 c4 0b                          ........
10.829 apcupsd: modbus.cpp:257 UpdateCi: Failed reading 0/2
10.829 apcupsd: apclog.c:62 Communications with UPS lost.
10.830 apcupsd: action.c:89 calling execute_ups_event commfailure event=0
10.833 apcupsd: apcexec.c:198 exec closed fd 3
10.833 apcupsd: apcexec.c:198 exec closed fd 4
10.833 apcupsd: apcexec.c:198 exec closed fd 5
10.833 apcupsd: apcexec.c:198 exec closed fd 7
/etc/apcupsd/commfailure: 18: /etc/apcupsd/commfailure: mail: not found
10.987 apcupsd: newups.c:90 read_lock at apcstatus.c:50
10.988 apcupsd: newups.c:96 read_unlock at apcstatus.c:375
                                                                              
Broadcast message from root@rpi20 (pts/0) (Tue Jun  7 18:58:09 2016):         
                                                                              
Warning communications lost with UPS APCUPS                                   
**********************


On Tue, Jun 7, 2016 at 8:43 PM, Adam Kropelin <[hidden email]> wrote:
In that case, try tags/Release-3_14_13 to see if the new modbus-usb is actually the source of the problem.


On Tue, Jun 7, 2016 at 2:39 PM, Romain Aviolat <[hidden email]> wrote:
Yep that's what I tried, the logs that I sent are from the 3.14.14 version.

On Tue, Jun 7, 2016 at 8:35 PM, Adam Kropelin <[hidden email]> wrote:
Try the latest released-but-not-yet-announced 3.14.14. That has some improvements to modbus-usb that are likely to help.

--Adam

On Tue, Jun 7, 2016 at 2:14 PM, Romain Aviolat <[hidden email]> wrote:
Hi there,

I wanted to extract the load of my Smart-UPS 750 with apcupsd, and that kind of info wasn't present with the usb driver:

root@rpi20:~/apcupsd-svn-2376-branches-Branch-3_14# apcaccess
APC      : 001,027,0659
DATE     : 2016-05-20 21:13:45 +0000 
HOSTNAME : rpi20
VERSION  : 3.14.14 (30 May 2015) debian
UPSNAME  : smartups750
CABLE    : USB Cable
DRIVER   : USB UPS Driver
UPSMODE  : Stand Alone
STARTTIME: 2016-05-20 21:13:44 +0000 
MODEL    : Smart-UPS 750
STATUS   : ONLINE
BCHARGE  : 100.0 Percent
TIMELEFT : 103.0 Minutes
MBATTCHG : 5 Percent
MINTIMEL : 3 Minutes
MAXTIME  : 0 Seconds
ALARMDEL : 30 Seconds
BATTV    : 27.0 Volts
NUMXFERS : 0
TONBATT  : 0 Seconds
CUMONBATT: 0 Seconds
XOFFBATT : N/A
STATFLAG : 0x05000008
MANDATE  : 2015-11-11
SERIALNO : 3S1546X01495 
NOMBATTV : 24.0 Volts
FIRMWARE : UPS 09.3 / ID=18
END APC  : 2016-05-20 21:13:51 +0000 

so I decided to try the new usb-modbus driver available with the latest 3.14.13 version.

it's way better:

root@rpi20:~/apcupsd-svn-2376-branches-Branch-3_14# apcaccess
APC      : 001,039,0899
DATE     : 2016-05-20 21:11:24 +0000 
HOSTNAME : rpi20
VERSION  : 3.14.14 (30 May 2015) debian
UPSNAME  : APCUPS
CABLE    : USB Cable
DRIVER   : MODBUS UPS Driver
UPSMODE  : Stand Alone
STARTTIME: 2016-05-20 21:11:18 +0000 
MODEL    : Smart-UPS 750
STATUS   : ONLINE
LINEV    : 234.7 Volts
LOADPCT  : 8.4 Percent
LOADAPNT : 11.7 Percent
BCHARGE  : 100.0 Percent
TIMELEFT : 103.0 Minutes
MBATTCHG : 5 Percent
MINTIMEL : 3 Minutes
MAXTIME  : 0 Seconds
OUTPUTV  : 234.7 Volts
DWAKE    : 0 Seconds
DSHUTD   : 90 Seconds
ITEMP    : 33.3 C
BATTV    : 27.0 Volts
LINEFREQ : 50.0 Hz
OUTCURNT : 0.38 Amps
NUMXFERS : 0
TONBATT  : 0 Seconds
CUMONBATT: 0 Seconds
XOFFBATT : N/A
SELFTEST : ??
STATFLAG : 0x05000008
MANDATE  : 2015-11-11
SERIALNO : 3S1546X01495
BATTDATE : 2015-11-11
NOMOUTV  : 230 Volts
NOMPOWER : 500 Watts
NOMAPNT  : 750 VA
FIRMWARE : UPS 09.3 / 00.4
END APC  : 2016-05-20 21:11:24 +0000 
                                                                              
 But I've got constantly comm lost / restored messages, about every 2 seconds on my console:


Broadcast message from root@rpi20 (somewhere) (Fri May 20 21:11:25 2016):     
                                                                              
Warning communications lost with UPS APCUPS                                   
                                                                              
                                                                              
Broadcast message from root@rpi20 (somewhere) (Fri May 20 21:11:27 2016):     
                                                                              
Communications restored with UPS APCUPS                                       



------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Apcupsd-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users



------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Apcupsd-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users



------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Apcupsd-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users



------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Apcupsd-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users
Reply | Threaded
Open this post in threaded view
|

Re: modbus-usb and Smart-UPS 750 - comm lost / restored every 2 seconds

Adam Kropelin-3
Ahh! I knew I had seen this issue before. This is a raspberry pi issue.
See the end of the thread linked below where I believe this was determined to be due to "weak" USB ports on the pi.


On Tue, Jun 7, 2016 at 4:12 PM, Romain Aviolat <[hidden email]> wrote:
it looks like I already have the latest version out there: FIRMWARE : UPS 09.3 / 00.

currently the UPS is connected to a raspberrypi, maybe I could try to connect it to a "regular" x86 machine ?


On Tue, Jun 7, 2016 at 9:38 PM, Adam Kropelin <[hidden email]> wrote:
Hmmm... So it appears that whenever apcupsd sends the UPS the same command twice in a row, the second one never elicits a response. I'd guess that's because the UPS never receives the second command. This could be a bug either in the USB drivers for your PC or a bug in the UPS firmware. Can you check for an UPS firmware upgrade?

On Tue, Jun 7, 2016 at 3:02 PM, Romain Aviolat <[hidden email]> wrote:
Adam,

exactly the same issue with 3.14.13

Romain

**********************
10.326 apcupsd: ModbusUsbComm.cpp:100 ModbusTx: Sending frame
10.327 apcupsd: apclog.c:179 Dumping 8 bytes @ 0x7ea1a070
10.327 apcupsd: apclog.c:212 00000000  01 03 00 00 00 02 c4 0b                          ........
10.829 apcupsd: modbus.cpp:257 UpdateCi: Failed reading 0/2
10.829 apcupsd: apclog.c:62 Communications with UPS lost.
10.830 apcupsd: action.c:89 calling execute_ups_event commfailure event=0
10.833 apcupsd: apcexec.c:198 exec closed fd 3
10.833 apcupsd: apcexec.c:198 exec closed fd 4
10.833 apcupsd: apcexec.c:198 exec closed fd 5
10.833 apcupsd: apcexec.c:198 exec closed fd 7
/etc/apcupsd/commfailure: 18: /etc/apcupsd/commfailure: mail: not found
10.987 apcupsd: newups.c:90 read_lock at apcstatus.c:50
10.988 apcupsd: newups.c:96 read_unlock at apcstatus.c:375
                                                                              
Broadcast message from root@rpi20 (pts/0) (Tue Jun  7 18:58:09 2016):         
                                                                              
Warning communications lost with UPS APCUPS                                   
**********************


On Tue, Jun 7, 2016 at 8:43 PM, Adam Kropelin <[hidden email]> wrote:
In that case, try tags/Release-3_14_13 to see if the new modbus-usb is actually the source of the problem.


On Tue, Jun 7, 2016 at 2:39 PM, Romain Aviolat <[hidden email]> wrote:
Yep that's what I tried, the logs that I sent are from the 3.14.14 version.

On Tue, Jun 7, 2016 at 8:35 PM, Adam Kropelin <[hidden email]> wrote:
Try the latest released-but-not-yet-announced 3.14.14. That has some improvements to modbus-usb that are likely to help.

--Adam

On Tue, Jun 7, 2016 at 2:14 PM, Romain Aviolat <[hidden email]> wrote:
Hi there,

I wanted to extract the load of my Smart-UPS 750 with apcupsd, and that kind of info wasn't present with the usb driver:

root@rpi20:~/apcupsd-svn-2376-branches-Branch-3_14# apcaccess
APC      : 001,027,0659
DATE     : 2016-05-20 21:13:45 +0000 
HOSTNAME : rpi20
VERSION  : 3.14.14 (30 May 2015) debian
UPSNAME  : smartups750
CABLE    : USB Cable
DRIVER   : USB UPS Driver
UPSMODE  : Stand Alone
STARTTIME: 2016-05-20 21:13:44 +0000 
MODEL    : Smart-UPS 750
STATUS   : ONLINE
BCHARGE  : 100.0 Percent
TIMELEFT : 103.0 Minutes
MBATTCHG : 5 Percent
MINTIMEL : 3 Minutes
MAXTIME  : 0 Seconds
ALARMDEL : 30 Seconds
BATTV    : 27.0 Volts
NUMXFERS : 0
TONBATT  : 0 Seconds
CUMONBATT: 0 Seconds
XOFFBATT : N/A
STATFLAG : 0x05000008
MANDATE  : 2015-11-11
SERIALNO : 3S1546X01495 
NOMBATTV : 24.0 Volts
FIRMWARE : UPS 09.3 / ID=18
END APC  : 2016-05-20 21:13:51 +0000 

so I decided to try the new usb-modbus driver available with the latest 3.14.13 version.

it's way better:

root@rpi20:~/apcupsd-svn-2376-branches-Branch-3_14# apcaccess
APC      : 001,039,0899
DATE     : 2016-05-20 21:11:24 +0000 
HOSTNAME : rpi20
VERSION  : 3.14.14 (30 May 2015) debian
UPSNAME  : APCUPS
CABLE    : USB Cable
DRIVER   : MODBUS UPS Driver
UPSMODE  : Stand Alone
STARTTIME: 2016-05-20 21:11:18 +0000 
MODEL    : Smart-UPS 750
STATUS   : ONLINE
LINEV    : 234.7 Volts
LOADPCT  : 8.4 Percent
LOADAPNT : 11.7 Percent
BCHARGE  : 100.0 Percent
TIMELEFT : 103.0 Minutes
MBATTCHG : 5 Percent
MINTIMEL : 3 Minutes
MAXTIME  : 0 Seconds
OUTPUTV  : 234.7 Volts
DWAKE    : 0 Seconds
DSHUTD   : 90 Seconds
ITEMP    : 33.3 C
BATTV    : 27.0 Volts
LINEFREQ : 50.0 Hz
OUTCURNT : 0.38 Amps
NUMXFERS : 0
TONBATT  : 0 Seconds
CUMONBATT: 0 Seconds
XOFFBATT : N/A
SELFTEST : ??
STATFLAG : 0x05000008
MANDATE  : 2015-11-11
SERIALNO : 3S1546X01495
BATTDATE : 2015-11-11
NOMOUTV  : 230 Volts
NOMPOWER : 500 Watts
NOMAPNT  : 750 VA
FIRMWARE : UPS 09.3 / 00.4
END APC  : 2016-05-20 21:11:24 +0000 
                                                                              
 But I've got constantly comm lost / restored messages, about every 2 seconds on my console:


Broadcast message from root@rpi20 (somewhere) (Fri May 20 21:11:25 2016):     
                                                                              
Warning communications lost with UPS APCUPS                                   
                                                                              
                                                                              
Broadcast message from root@rpi20 (somewhere) (Fri May 20 21:11:27 2016):     
                                                                              
Communications restored with UPS APCUPS                                       



------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Apcupsd-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users



------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Apcupsd-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users



------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Apcupsd-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users



------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Apcupsd-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users



------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Apcupsd-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users
Reply | Threaded
Open this post in threaded view
|

Re: modbus-usb and Smart-UPS 750 - comm lost / restored every 2 seconds

Romain Aviolat
Thanks a lot Adam, connecting it to a *traditional* machine did the trick !

Romain

On Tue, Jun 7, 2016 at 10:54 PM, Adam Kropelin <[hidden email]> wrote:
Ahh! I knew I had seen this issue before. This is a raspberry pi issue.
See the end of the thread linked below where I believe this was determined to be due to "weak" USB ports on the pi.


On Tue, Jun 7, 2016 at 4:12 PM, Romain Aviolat <[hidden email]> wrote:
it looks like I already have the latest version out there: FIRMWARE : UPS 09.3 / 00.

currently the UPS is connected to a raspberrypi, maybe I could try to connect it to a "regular" x86 machine ?


On Tue, Jun 7, 2016 at 9:38 PM, Adam Kropelin <[hidden email]> wrote:
Hmmm... So it appears that whenever apcupsd sends the UPS the same command twice in a row, the second one never elicits a response. I'd guess that's because the UPS never receives the second command. This could be a bug either in the USB drivers for your PC or a bug in the UPS firmware. Can you check for an UPS firmware upgrade?

On Tue, Jun 7, 2016 at 3:02 PM, Romain Aviolat <[hidden email]> wrote:
Adam,

exactly the same issue with 3.14.13

Romain

**********************
10.326 apcupsd: ModbusUsbComm.cpp:100 ModbusTx: Sending frame
10.327 apcupsd: apclog.c:179 Dumping 8 bytes @ 0x7ea1a070
10.327 apcupsd: apclog.c:212 00000000  01 03 00 00 00 02 c4 0b                          ........
10.829 apcupsd: modbus.cpp:257 UpdateCi: Failed reading 0/2
10.829 apcupsd: apclog.c:62 Communications with UPS lost.
10.830 apcupsd: action.c:89 calling execute_ups_event commfailure event=0
10.833 apcupsd: apcexec.c:198 exec closed fd 3
10.833 apcupsd: apcexec.c:198 exec closed fd 4
10.833 apcupsd: apcexec.c:198 exec closed fd 5
10.833 apcupsd: apcexec.c:198 exec closed fd 7
/etc/apcupsd/commfailure: 18: /etc/apcupsd/commfailure: mail: not found
10.987 apcupsd: newups.c:90 read_lock at apcstatus.c:50
10.988 apcupsd: newups.c:96 read_unlock at apcstatus.c:375
                                                                              
Broadcast message from root@rpi20 (pts/0) (Tue Jun  7 18:58:09 2016):         
                                                                              
Warning communications lost with UPS APCUPS                                   
**********************


On Tue, Jun 7, 2016 at 8:43 PM, Adam Kropelin <[hidden email]> wrote:
In that case, try tags/Release-3_14_13 to see if the new modbus-usb is actually the source of the problem.


On Tue, Jun 7, 2016 at 2:39 PM, Romain Aviolat <[hidden email]> wrote:
Yep that's what I tried, the logs that I sent are from the 3.14.14 version.

On Tue, Jun 7, 2016 at 8:35 PM, Adam Kropelin <[hidden email]> wrote:
Try the latest released-but-not-yet-announced 3.14.14. That has some improvements to modbus-usb that are likely to help.

--Adam

On Tue, Jun 7, 2016 at 2:14 PM, Romain Aviolat <[hidden email]> wrote:
Hi there,

I wanted to extract the load of my Smart-UPS 750 with apcupsd, and that kind of info wasn't present with the usb driver:

root@rpi20:~/apcupsd-svn-2376-branches-Branch-3_14# apcaccess
APC      : 001,027,0659
DATE     : 2016-05-20 21:13:45 +0000 
HOSTNAME : rpi20
VERSION  : 3.14.14 (30 May 2015) debian
UPSNAME  : smartups750
CABLE    : USB Cable
DRIVER   : USB UPS Driver
UPSMODE  : Stand Alone
STARTTIME: 2016-05-20 21:13:44 +0000 
MODEL    : Smart-UPS 750
STATUS   : ONLINE
BCHARGE  : 100.0 Percent
TIMELEFT : 103.0 Minutes
MBATTCHG : 5 Percent
MINTIMEL : 3 Minutes
MAXTIME  : 0 Seconds
ALARMDEL : 30 Seconds
BATTV    : 27.0 Volts
NUMXFERS : 0
TONBATT  : 0 Seconds
CUMONBATT: 0 Seconds
XOFFBATT : N/A
STATFLAG : 0x05000008
MANDATE  : 2015-11-11
SERIALNO : 3S1546X01495 
NOMBATTV : 24.0 Volts
FIRMWARE : UPS 09.3 / ID=18
END APC  : 2016-05-20 21:13:51 +0000 

so I decided to try the new usb-modbus driver available with the latest 3.14.13 version.

it's way better:

root@rpi20:~/apcupsd-svn-2376-branches-Branch-3_14# apcaccess
APC      : 001,039,0899
DATE     : 2016-05-20 21:11:24 +0000 
HOSTNAME : rpi20
VERSION  : 3.14.14 (30 May 2015) debian
UPSNAME  : APCUPS
CABLE    : USB Cable
DRIVER   : MODBUS UPS Driver
UPSMODE  : Stand Alone
STARTTIME: 2016-05-20 21:11:18 +0000 
MODEL    : Smart-UPS 750
STATUS   : ONLINE
LINEV    : 234.7 Volts
LOADPCT  : 8.4 Percent
LOADAPNT : 11.7 Percent
BCHARGE  : 100.0 Percent
TIMELEFT : 103.0 Minutes
MBATTCHG : 5 Percent
MINTIMEL : 3 Minutes
MAXTIME  : 0 Seconds
OUTPUTV  : 234.7 Volts
DWAKE    : 0 Seconds
DSHUTD   : 90 Seconds
ITEMP    : 33.3 C
BATTV    : 27.0 Volts
LINEFREQ : 50.0 Hz
OUTCURNT : 0.38 Amps
NUMXFERS : 0
TONBATT  : 0 Seconds
CUMONBATT: 0 Seconds
XOFFBATT : N/A
SELFTEST : ??
STATFLAG : 0x05000008
MANDATE  : 2015-11-11
SERIALNO : 3S1546X01495
BATTDATE : 2015-11-11
NOMOUTV  : 230 Volts
NOMPOWER : 500 Watts
NOMAPNT  : 750 VA
FIRMWARE : UPS 09.3 / 00.4
END APC  : 2016-05-20 21:11:24 +0000 
                                                                              
 But I've got constantly comm lost / restored messages, about every 2 seconds on my console:


Broadcast message from root@rpi20 (somewhere) (Fri May 20 21:11:25 2016):     
                                                                              
Warning communications lost with UPS APCUPS                                   
                                                                              
                                                                              
Broadcast message from root@rpi20 (somewhere) (Fri May 20 21:11:27 2016):     
                                                                              
Communications restored with UPS APCUPS                                       



------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Apcupsd-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users



------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Apcupsd-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users



------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Apcupsd-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users



------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Apcupsd-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users



------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Apcupsd-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users



------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Apcupsd-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users
Reply | Threaded
Open this post in threaded view
|

Re: modbus-usb and Smart-UPS 750 - comm lost / restored every 2 seconds

Romain Aviolat
just for the record, I didn't notice that before but you're right I've got plenty of errors related to the USB ports on my kernel log files on my raspi so that's definitively the cause;

********************
[1640508.603885] usb 1-1.3: reset full-speed USB device number 85 using dwc_otg
[1640568.744189] usb 1-1.3: reset full-speed USB device number 85 using dwc_otg
[1640627.914489] usb 1-1.3: reset full-speed USB device number 85 using dwc_otg
[1640688.084781] usb 1-1.3: reset full-speed USB device number 85 using dwc_otg
[1640748.295092] usb 1-1.3: reset full-speed USB device number 85 using dwc_otg
[1640808.425386] usb 1-1.3: reset full-speed USB device number 85 using dwc_otg
[1640868.575788] usb 1-1.3: reset full-speed USB device number 85 using dwc_otg
[1640928.795982] usb 1-1.3: reset full-speed USB device number 85 using dwc_otg
[1640987.946287] usb 1-1.3: reset full-speed USB device number 85 using dwc_otg
[1641048.096575] usb 1-1.3: reset full-speed USB device number 85 using dwc_otg
[1641108.226858] usb 1-1.3: reset full-speed USB device number 85 using dwc_otg
[1641168.377155] usb 1-1.3: reset full-speed USB device number 85 using dwc_otg
[1641226.387438] usb 1-1.3: reset full-speed USB device number 85 using dwc_otg
********************

+++
Romain


On Wed, Jun 8, 2016 at 9:48 PM, Romain Aviolat <[hidden email]> wrote:
Thanks a lot Adam, connecting it to a *traditional* machine did the trick !

Romain

On Tue, Jun 7, 2016 at 10:54 PM, Adam Kropelin <[hidden email]> wrote:
Ahh! I knew I had seen this issue before. This is a raspberry pi issue.
See the end of the thread linked below where I believe this was determined to be due to "weak" USB ports on the pi.


On Tue, Jun 7, 2016 at 4:12 PM, Romain Aviolat <[hidden email]> wrote:
it looks like I already have the latest version out there: FIRMWARE : UPS 09.3 / 00.

currently the UPS is connected to a raspberrypi, maybe I could try to connect it to a "regular" x86 machine ?


On Tue, Jun 7, 2016 at 9:38 PM, Adam Kropelin <[hidden email]> wrote:
Hmmm... So it appears that whenever apcupsd sends the UPS the same command twice in a row, the second one never elicits a response. I'd guess that's because the UPS never receives the second command. This could be a bug either in the USB drivers for your PC or a bug in the UPS firmware. Can you check for an UPS firmware upgrade?

On Tue, Jun 7, 2016 at 3:02 PM, Romain Aviolat <[hidden email]> wrote:
Adam,

exactly the same issue with 3.14.13

Romain

**********************
10.326 apcupsd: ModbusUsbComm.cpp:100 ModbusTx: Sending frame
10.327 apcupsd: apclog.c:179 Dumping 8 bytes @ 0x7ea1a070
10.327 apcupsd: apclog.c:212 00000000  01 03 00 00 00 02 c4 0b                          ........
10.829 apcupsd: modbus.cpp:257 UpdateCi: Failed reading 0/2
10.829 apcupsd: apclog.c:62 Communications with UPS lost.
10.830 apcupsd: action.c:89 calling execute_ups_event commfailure event=0
10.833 apcupsd: apcexec.c:198 exec closed fd 3
10.833 apcupsd: apcexec.c:198 exec closed fd 4
10.833 apcupsd: apcexec.c:198 exec closed fd 5
10.833 apcupsd: apcexec.c:198 exec closed fd 7
/etc/apcupsd/commfailure: 18: /etc/apcupsd/commfailure: mail: not found
10.987 apcupsd: newups.c:90 read_lock at apcstatus.c:50
10.988 apcupsd: newups.c:96 read_unlock at apcstatus.c:375
                                                                              
Broadcast message from root@rpi20 (pts/0) (Tue Jun  7 18:58:09 2016):         
                                                                              
Warning communications lost with UPS APCUPS                                   
**********************


On Tue, Jun 7, 2016 at 8:43 PM, Adam Kropelin <[hidden email]> wrote:
In that case, try tags/Release-3_14_13 to see if the new modbus-usb is actually the source of the problem.


On Tue, Jun 7, 2016 at 2:39 PM, Romain Aviolat <[hidden email]> wrote:
Yep that's what I tried, the logs that I sent are from the 3.14.14 version.

On Tue, Jun 7, 2016 at 8:35 PM, Adam Kropelin <[hidden email]> wrote:
Try the latest released-but-not-yet-announced 3.14.14. That has some improvements to modbus-usb that are likely to help.

--Adam

On Tue, Jun 7, 2016 at 2:14 PM, Romain Aviolat <[hidden email]> wrote:
Hi there,

I wanted to extract the load of my Smart-UPS 750 with apcupsd, and that kind of info wasn't present with the usb driver:

root@rpi20:~/apcupsd-svn-2376-branches-Branch-3_14# apcaccess
APC      : 001,027,0659
DATE     : 2016-05-20 21:13:45 +0000 
HOSTNAME : rpi20
VERSION  : 3.14.14 (30 May 2015) debian
UPSNAME  : smartups750
CABLE    : USB Cable
DRIVER   : USB UPS Driver
UPSMODE  : Stand Alone
STARTTIME: 2016-05-20 21:13:44 +0000 
MODEL    : Smart-UPS 750
STATUS   : ONLINE
BCHARGE  : 100.0 Percent
TIMELEFT : 103.0 Minutes
MBATTCHG : 5 Percent
MINTIMEL : 3 Minutes
MAXTIME  : 0 Seconds
ALARMDEL : 30 Seconds
BATTV    : 27.0 Volts
NUMXFERS : 0
TONBATT  : 0 Seconds
CUMONBATT: 0 Seconds
XOFFBATT : N/A
STATFLAG : 0x05000008
MANDATE  : 2015-11-11
SERIALNO : 3S1546X01495 
NOMBATTV : 24.0 Volts
FIRMWARE : UPS 09.3 / ID=18
END APC  : 2016-05-20 21:13:51 +0000 

so I decided to try the new usb-modbus driver available with the latest 3.14.13 version.

it's way better:

root@rpi20:~/apcupsd-svn-2376-branches-Branch-3_14# apcaccess
APC      : 001,039,0899
DATE     : 2016-05-20 21:11:24 +0000 
HOSTNAME : rpi20
VERSION  : 3.14.14 (30 May 2015) debian
UPSNAME  : APCUPS
CABLE    : USB Cable
DRIVER   : MODBUS UPS Driver
UPSMODE  : Stand Alone
STARTTIME: 2016-05-20 21:11:18 +0000 
MODEL    : Smart-UPS 750
STATUS   : ONLINE
LINEV    : 234.7 Volts
LOADPCT  : 8.4 Percent
LOADAPNT : 11.7 Percent
BCHARGE  : 100.0 Percent
TIMELEFT : 103.0 Minutes
MBATTCHG : 5 Percent
MINTIMEL : 3 Minutes
MAXTIME  : 0 Seconds
OUTPUTV  : 234.7 Volts
DWAKE    : 0 Seconds
DSHUTD   : 90 Seconds
ITEMP    : 33.3 C
BATTV    : 27.0 Volts
LINEFREQ : 50.0 Hz
OUTCURNT : 0.38 Amps
NUMXFERS : 0
TONBATT  : 0 Seconds
CUMONBATT: 0 Seconds
XOFFBATT : N/A
SELFTEST : ??
STATFLAG : 0x05000008
MANDATE  : 2015-11-11
SERIALNO : 3S1546X01495
BATTDATE : 2015-11-11
NOMOUTV  : 230 Volts
NOMPOWER : 500 Watts
NOMAPNT  : 750 VA
FIRMWARE : UPS 09.3 / 00.4
END APC  : 2016-05-20 21:11:24 +0000 
                                                                              
 But I've got constantly comm lost / restored messages, about every 2 seconds on my console:


Broadcast message from root@rpi20 (somewhere) (Fri May 20 21:11:25 2016):     
                                                                              
Warning communications lost with UPS APCUPS                                   
                                                                              
                                                                              
Broadcast message from root@rpi20 (somewhere) (Fri May 20 21:11:27 2016):     
                                                                              
Communications restored with UPS APCUPS                                       



------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Apcupsd-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users



------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Apcupsd-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users



------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Apcupsd-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users



------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Apcupsd-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users



------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Apcupsd-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users




------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Apcupsd-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users
Reply | Threaded
Open this post in threaded view
|

El Capitan

John Caradimas
I can confirm that:

- apcupsd 3.14.14 works OK on El Capitan, and so does apcaccess and apcagent, but
- it indeed needs for the USB cable to be disconnected and reconnected in order for Apple’s Power Manager to release the USB port, for apcupsd to capture it and start working with your UPS. 

Since I hate having to crowl under the desk to have the USB cable removed and reconnected, I am switching back to having the UPS managed by my Centos server. I’ll report back how apcaccess works in that setup.

-------------------
John Caradimas




On 08 Jun 2016, at 23:08, Romain Aviolat <[hidden email]> wrote:

just for the record, I didn't notice that before but you're right I've got plenty of errors related to the USB ports on my kernel log files on my raspi so that's definitively the cause;

********************
[1640508.603885] usb 1-1.3: reset full-speed USB device number 85 using dwc_otg
[1640568.744189] usb 1-1.3: reset full-speed USB device number 85 using dwc_otg
[1640627.914489] usb 1-1.3: reset full-speed USB device number 85 using dwc_otg
[1640688.084781] usb 1-1.3: reset full-speed USB device number 85 using dwc_otg
[1640748.295092] usb 1-1.3: reset full-speed USB device number 85 using dwc_otg
[1640808.425386] usb 1-1.3: reset full-speed USB device number 85 using dwc_otg
[1640868.575788] usb 1-1.3: reset full-speed USB device number 85 using dwc_otg
[1640928.795982] usb 1-1.3: reset full-speed USB device number 85 using dwc_otg
[1640987.946287] usb 1-1.3: reset full-speed USB device number 85 using dwc_otg
[1641048.096575] usb 1-1.3: reset full-speed USB device number 85 using dwc_otg
[1641108.226858] usb 1-1.3: reset full-speed USB device number 85 using dwc_otg
[1641168.377155] usb 1-1.3: reset full-speed USB device number 85 using dwc_otg
[1641226.387438] usb 1-1.3: reset full-speed USB device number 85 using dwc_otg
********************

+++
Romain


On Wed, Jun 8, 2016 at 9:48 PM, Romain Aviolat <[hidden email]> wrote:
Thanks a lot Adam, connecting it to a *traditional* machine did the trick !

Romain

On Tue, Jun 7, 2016 at 10:54 PM, Adam Kropelin <[hidden email]> wrote:
Ahh! I knew I had seen this issue before. This is a raspberry pi issue.
See the end of the thread linked below where I believe this was determined to be due to "weak" USB ports on the pi.


On Tue, Jun 7, 2016 at 4:12 PM, Romain Aviolat <[hidden email]> wrote:
it looks like I already have the latest version out there: FIRMWARE : UPS 09.3 / 00.

currently the UPS is connected to a raspberrypi, maybe I could try to connect it to a "regular" x86 machine ?


On Tue, Jun 7, 2016 at 9:38 PM, Adam Kropelin <[hidden email]> wrote:
Hmmm... So it appears that whenever apcupsd sends the UPS the same command twice in a row, the second one never elicits a response. I'd guess that's because the UPS never receives the second command. This could be a bug either in the USB drivers for your PC or a bug in the UPS firmware. Can you check for an UPS firmware upgrade?

On Tue, Jun 7, 2016 at 3:02 PM, Romain Aviolat <[hidden email]> wrote:
Adam,

exactly the same issue with 3.14.13

Romain

**********************
10.326 apcupsd: ModbusUsbComm.cpp:100 ModbusTx: Sending frame
10.327 apcupsd: apclog.c:179 Dumping 8 bytes @ 0x7ea1a070
10.327 apcupsd: apclog.c:212 00000000  01 03 00 00 00 02 c4 0b                          ........
10.829 apcupsd: modbus.cpp:257 UpdateCi: Failed reading 0/2
10.829 apcupsd: apclog.c:62 Communications with UPS lost.
10.830 apcupsd: action.c:89 calling execute_ups_event commfailure event=0
10.833 apcupsd: apcexec.c:198 exec closed fd 3
10.833 apcupsd: apcexec.c:198 exec closed fd 4
10.833 apcupsd: apcexec.c:198 exec closed fd 5
10.833 apcupsd: apcexec.c:198 exec closed fd 7
/etc/apcupsd/commfailure: 18: /etc/apcupsd/commfailure: mail: not found
10.987 apcupsd: newups.c:90 read_lock at apcstatus.c:50
10.988 apcupsd: newups.c:96 read_unlock at apcstatus.c:375
                                                                              
Broadcast message from root@rpi20 (pts/0) (Tue Jun  7 18:58:09 2016):         
                                                                              
Warning communications lost with UPS APCUPS                                   
**********************


On Tue, Jun 7, 2016 at 8:43 PM, Adam Kropelin <[hidden email]> wrote:
In that case, try tags/Release-3_14_13 to see if the new modbus-usb is actually the source of the problem.


On Tue, Jun 7, 2016 at 2:39 PM, Romain Aviolat <[hidden email]> wrote:
Yep that's what I tried, the logs that I sent are from the 3.14.14 version.

On Tue, Jun 7, 2016 at 8:35 PM, Adam Kropelin <[hidden email]> wrote:
Try the latest released-but-not-yet-announced 3.14.14. That has some improvements to modbus-usb that are likely to help.

--Adam

On Tue, Jun 7, 2016 at 2:14 PM, Romain Aviolat <[hidden email]> wrote:
Hi there,

I wanted to extract the load of my Smart-UPS 750 with apcupsd, and that kind of info wasn't present with the usb driver:

root@rpi20:~/apcupsd-svn-2376-branches-Branch-3_14# apcaccess
APC      : 001,027,0659
DATE     : 2016-05-20 21:13:45 +0000 
HOSTNAME : rpi20
VERSION  : 3.14.14 (30 May 2015) debian
UPSNAME  : smartups750
CABLE    : USB Cable
DRIVER   : USB UPS Driver
UPSMODE  : Stand Alone
STARTTIME: 2016-05-20 21:13:44 +0000 
MODEL    : Smart-UPS 750
STATUS   : ONLINE
BCHARGE  : 100.0 Percent
TIMELEFT : 103.0 Minutes
MBATTCHG : 5 Percent
MINTIMEL : 3 Minutes
MAXTIME  : 0 Seconds
ALARMDEL : 30 Seconds
BATTV    : 27.0 Volts
NUMXFERS : 0
TONBATT  : 0 Seconds
CUMONBATT: 0 Seconds
XOFFBATT : N/A
STATFLAG : 0x05000008
MANDATE  : 2015-11-11
SERIALNO : 3S1546X01495 
NOMBATTV : 24.0 Volts
FIRMWARE : UPS 09.3 / ID=18
END APC  : 2016-05-20 21:13:51 +0000 

so I decided to try the new usb-modbus driver available with the latest 3.14.13 version.

it's way better:

root@rpi20:~/apcupsd-svn-2376-branches-Branch-3_14# apcaccess
APC      : 001,039,0899
DATE     : 2016-05-20 21:11:24 +0000 
HOSTNAME : rpi20
VERSION  : 3.14.14 (30 May 2015) debian
UPSNAME  : APCUPS
CABLE    : USB Cable
DRIVER   : MODBUS UPS Driver
UPSMODE  : Stand Alone
STARTTIME: 2016-05-20 21:11:18 +0000 
MODEL    : Smart-UPS 750
STATUS   : ONLINE
LINEV    : 234.7 Volts
LOADPCT  : 8.4 Percent
LOADAPNT : 11.7 Percent
BCHARGE  : 100.0 Percent
TIMELEFT : 103.0 Minutes
MBATTCHG : 5 Percent
MINTIMEL : 3 Minutes
MAXTIME  : 0 Seconds
OUTPUTV  : 234.7 Volts
DWAKE    : 0 Seconds
DSHUTD   : 90 Seconds
ITEMP    : 33.3 C
BATTV    : 27.0 Volts
LINEFREQ : 50.0 Hz
OUTCURNT : 0.38 Amps
NUMXFERS : 0
TONBATT  : 0 Seconds
CUMONBATT: 0 Seconds
XOFFBATT : N/A
SELFTEST : ??
STATFLAG : 0x05000008
MANDATE  : 2015-11-11
SERIALNO : 3S1546X01495
BATTDATE : 2015-11-11
NOMOUTV  : 230 Volts
NOMPOWER : 500 Watts
NOMAPNT  : 750 VA
FIRMWARE : UPS 09.3 / 00.4
END APC  : 2016-05-20 21:11:24 +0000 
                                                                              
 But I've got constantly comm lost / restored messages, about every 2 seconds on my console:


Broadcast message from root@rpi20 (somewhere) (Fri May 20 21:11:25 2016):     
                                                                              
Warning communications lost with UPS APCUPS                                   
                                                                              
                                                                              
Broadcast message from root@rpi20 (somewhere) (Fri May 20 21:11:27 2016):     
                                                                              
Communications restored with UPS APCUPS                                       



------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Apcupsd-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users



------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Apcupsd-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users



------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Apcupsd-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users



------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Apcupsd-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users



------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Apcupsd-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users



------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e_______________________________________________
Apcupsd-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users


------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Apcupsd-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users