search for: 3731m

...ted the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. ------------ upsdrvctl stop and start don't complain... ------------ C:\Program Files (x86)\NUT\bin>upsdrvctl stop Network UPS Tools - UPS driver controller 2.6.5-3723:3731M C:\Program Files (x86)\NUT\bin>upsdrvctl start Network UPS Tools - UPS driver controller 2.6.5-3723:3731M C:\Program Files (x86)\NUT\bin>Network UPS Tools - BCMXCP UPS driver 0.26 (2.6.5 -3723:3731M) USB communication subdriver 0.21 ------------- But many other commands complain... ------...

On Dec 17, 2013, at 12:45 PM, Bruce Bowler wrote: > upsdrvctl stop and start don't complain... > > ------------ > C:\Program Files (x86)\NUT\bin>upsdrvctl stop > Network UPS Tools - UPS driver controller 2.6.5-3723:3731M > > C:\Program Files (x86)\NUT\bin>upsdrvctl start > Network UPS Tools - UPS driver controller 2.6.5-3723:3731M > > C:\Program Files (x86)\NUT\bin>Network UPS Tools - BCMXCP UPS driver > 0.26 (2.6.5 -3723:3731M) > USB communication subdriver 0.21 > ------------- I...

On 2014-01-14 10:12, dstrr wrote: > Hello. > Trouble to communicate with APC SmartUPS via serial port. > UPS connected to the com1 port on windows host. > Communication witch hyperterm works well. > There is a log: > > YSM > ^ASmart-UPS SC1000 > n5S0713T63247 > m03/29/07 > L240.0 > B27.10 > > apcupsd also can communicate with the UPS and works well. >

Hello. Trouble to communicate with APC SmartUPS via serial port. UPS connected to the com1 port on windows host. Communication witch hyperterm works well. There is a log: YSM ^ASmart-UPS SC1000 n5S0713T63247 m03/29/07 L240.0 B27.10 apcupsd also can communicate with the UPS and works well. running apcsmart -a ups gives the following: com1: device reports different attributes than what were set

...t will correctly dump variables from the UPS, so communication with the UPS itself seems to work. However, when I try to run 'upsc xs1500', I get the following output from upsd (running with debugging output): C:\Program Files (x86)\NUT\sbin>upsd -DDDDD Network UPS Tools upsd 2.6.5-3723:3731M 0.000000 listen_add: added ::1:3493 0.000000 listen_add: added 127.0.0.1:3493 0.015628 setuptcp: try to bind to 127.0.0.1 port 3493 0.031310 listening on 127.0.0.1 port 3493 0.031310 setuptcp: try to bind to ::1 port 3493 0.031310 listening on ::1 port 3493...

...y dump variables from the UPS, so communication with the UPS itself seems to work. However, when I try to run 'upsc xs1500', I get the following output from upsd (running with debugging output): > > C:\Program Files (x86)\NUT\sbin>upsd -DDDDD > Network UPS Tools upsd 2.6.5-3723:3731M > 0.000000 listen_add: added ::1:3493 > 0.000000 listen_add: added 127.0.0.1:3493 > 0.015628 setuptcp: try to bind to 127.0.0.1 port 3493 > 0.031310 listening on 127.0.0.1 port 3493 > 0.031310 setuptcp: try to bind to ::1 port 3493 > 0.031310...

...es from > the UPS, so communication with the UPS itself seems to work. However, when > I try to run 'upsc xs1500', I get the following output from upsd (running > with debugging output): > > C:\Program Files (x86)\NUT\sbin>upsd -DDDDD > Network UPS Tools upsd 2.6.5-3723:3731M > 0.000000 listen_add: added ::1:3493 > 0.000000 listen_add: added 127.0.0.1:3493 > 0.015628 setuptcp: try to bind to 127.0.0.1 port 3493 > 0.031310 listening on 127.0.0.1 port 3493 > 0.031310 setuptcp: try to bind to ::1 port 3493 > 0.031310...

...system Windows 7 x64 NUT version 2.6.5 Windows port UPS Victron NetPro connected via serial port When I run driver when UPS cable is connected to computer's serial port it exits with following output victronups - -DDDD -a victron Network UPS Tools -GE/IMU/Victron UPS driver 0.20 (2.6.5.-3723:3731M) 0.000000 debug level is "4" 0.000000 w32_serial_open (COM1) 0.000000 setting initial state on COM1 0.015600 0000000050 = w32_serial_open (COM1) 0.015600 Warning: no locking method is available: No error 0.015600 tcgetattr(COM1): Input/output error But... when I run the driver and few se...