search for: getbaseinfo

...builders/Debian-x64-gcc/builds/389 > Here is what I got from running the just-compiled nut-2.7.3.1.tar.gz: [~]>/usr/local/libexec/nut/solis -a lobos -u root -D -D -D Network UPS Tools - Microsol Solis UPS driver 0.63 (2.7.3.1) 0.000000 debug level is '3' 0.001946 getbaseinfo: sending CMD_UPSCONT and ENDCHAR to sync 0.002111 getbaseinfo: requesting 25 bytes from ser_get_buf_len() 0.963327 getbaseinfo: received 25 bytes from ser_get_buf_len() 0.963360 CommReceive: RecPack: (25 bytes) => 00 17 91 49 5e 5e bc fe bb 46 88 ac 1b 0.963375 0a a...

Hi; I'm having some trouble to comunicate with my just bought (08/17/15) Ups. According to SOLIS(8): SUPPORTED HARDWARE This driver has been tested with : Solis 1000 VA Solis 1500 VA Solis 2000 VA Solis 3000 VA Back-UPS BZ1200-BR Back-UPS BZ2200BI-BR So solis is the one to go for. Here is my scenario: SW: nut-2.7.3 (compiled from ports) OS: FreeBSD

This patch introduces a handful of new options, I mentioned earlier in: http://www.mail-archive.com/nut-upsdev at lists.alioth.debian.org/msg02088.html See the large commit message in the follow-up for the details and rationale. I realize it's a bit larger diff - so if it's required I can split it into few smaller ones. Michal Soltys (1): APC smart driver update and new features.

Sorry for a bit longer delay than I anticipated, I was stuffed with the work. This is the next iteration of the patch adding some functionality to apcsmart driver, and relying on 'ignorelb' recently added. Follow up from previous thread: http://www.mail-archive.com/nut-upsdev at lists.alioth.debian.org/msg02331.html Main differences is that V3 is split into many small patches, so the

This is 2nd version of the earlier patch featuring a few new features and fixes to the apcsmart driver, following the remarks in: http://www.mail-archive.com/nut-upsdev at lists.alioth.debian.org/msg02294.html Major changes from v1: - handle battery.charge and battery.runtime checks at main.c level - handle "immutable but writable" conflict gracefully at driver level -

...the result of the 'a' > command to the SC1000 UPS, which queries the available commands for > the UPS did not include the ^Z (dec 26) command in the return > string. Thus, the driver did not enable the commands for modifying > the eeprom values. (See the do_capabilities() and getbaseinfo() in > drivers/apcsmart.c.) However, the UPS did accept the ^Z command and > did in fact return the list of eeprom values (capabilities) as it is > documented to do. The short of it is: the SC1000 claims it does not > support the ^Z command, when in reality it does. > > This may...

...ifying as a Solis 1.0 (which is not) but at least it is doing it on its own, without gdb. Here is the output: /usr/local/libexec/nut/solis -a lobos -u root -D -D -D Network UPS Tools - APC/Microsol Solis UPS driver 0.64 (2.7.3.1) 0.000000 debug level is '3' 0.001843 getbaseinfo: sending CMD_UPSCONT and ENDCHAR to sync 1.330248 getbaseinfo: received 25 bytes from ser_get_buf_len() 1.330283 CommReceive: RecPack: (25 bytes) => bb 47 88 ad 1b 0a a0 18 02 30 14 10 0b 1.330298 00 00 00 01 00 09 a1 49 5e 5e 25 fe Detected Solis 1.0 on /dev/cuaU0 UPS Date 1...

Turns out another user reported the same issue with a slightly different model: https://github.com/networkupstools/nut/issues/231 <https://github.com/networkupstools/nut/issues/231> The "stty -f /dev/cuaU0 raw" trick should help, but I am confused as to why FreeBSD has different "raw" settings than what is set up at the same time as the baud rate:

...* UPS internal time */ - ihour = RecPack[26]; - imin = RecPack[27]; - isec = RecPack[28]; + /* ihour = RecPack[26]; */ + /* imin = RecPack[27]; */ + /* isec = RecPack[28]; */ /* Flag1 */ /* SobreTemp = ( ( 0x01 & RecPack[33]) = 0x01 ); */ @@ -546,18 +530,8 @@ static void getbaseinfo(void) unsigned char temp[256]; unsigned char Pacote[37]; int tam, i, j=0; - time_t *tmt; - struct tm *now; const char *Model; - tmt = ( time_t * ) malloc( sizeof( time_t ) ); - time( tmt ); - now = localtime( tmt ); - dian = no...

Dear Andreas, some googling revealed, you created a driver for the xanto series of online-usv.de. In what state it is currently? I've to manage a S2000 and would like to use nut for it, is it usable by now? Do you need another tester? TIA, Pete

...er.c:259: warning: pointer targets in passing argument 2 of command_read_sequence differ in signedness bcmxcp_ser.c:271: warning: pointer targets in passing argument 2 of command_read_sequence differ in signedness gcc -I../include -O -Wall -Wsign-compare -c -o solis.o solis.c solis.c: In function getbaseinfo: solis.c:531: warning: pointer targets in passing argument 2 of ser_get_buf_len differ in signedness solis.c:539: warning: pointer targets in passing argument 1 of CommReceive differ in signedness solis.c:541: warning: pointer targets in passing argument 1 of CommReceive differ in signedness solis....