search for: recpack

...r 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 a0 ed 01 07 07 bb 46 82 ae 1b 09 0.963387 getbaseinfo: requesting 25 bytes from ser_get_buf_len() 2.048306 getbaseinfo: received 25 bytes from ser_get_buf_len() 2.048343 CommReceive: RecPack: (25 byte...

On Aug 23, 2015, at 6:26 PM, Mario Lobo <mlobo at digiart.art.br> wrote: > > I hope it helps! It is a bit easier to read than the ktrace output. Here are the bytes received, without the other messages: Network UPS Tools - Microsol Solis UPS driver 0.63 (2.7.3.1) CommReceive: RecPack: (25 bytes) => 00 17 91 49 5e 5e bc fe bb 46 88 ac 1b 0a a0 ed 01 07 07 bb 46 82 ae 1b 09 CommReceive: RecPack: (25 bytes) => a0 04 02 06 1d 0d 03 00 00 00 01 00 17 91 49 5e 5e dc fe bb 47 83 ad 1a 09 CommReceive: RecPack: (25 bytes) => a0 0a 02 07 1d 0d 03 00 00 00 01 00 17 91 49 5e 5e e3...

...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 1999/10/09 System Date 2015/09/09 day of week Wed UPS internal Time 16:20:48 Shutdown programming not activated 1.330381 getupdateinfo: reque...

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:

...a */ -static int Day, Month, Year; -static int dian=0, mesn=0, anon=0, weekn=0; -static int ihour,imin, isec; -/* unsigned char DaysOnWeek; */ -/* char seman[4]; */ - /* int FExpansaoBateria; */ /* internal variables */ /* package handshake variables */ @@ -142,19 +136,9 @@ static unsigned char RecPack[37]; #ifdef PORTUGUESE #define M_UNKN "Mod?lo rhino desconhecido\n" #define NO_RHINO "Rhino n?o detectado! abortando ...\n" -#define UPS_DATE "Data no UPS %4d/%02d/%02d\n" -#define SYS_DATE "Data do Sistema %4d/%02d/%02d dia da semana %s\n" -#def...

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

...table in > /usr/local/libexec/nut/solis inside freenas, with the patches that I have > posted in the forum: Dear guys, Following your suggestions I was able to make NUT recognize my UPS model. Actually, the only modification I had to introduce in solis.c was to change this line: if( ( (RecPack[0] & 0xF0) == 0xA0 ) to if( ( (RecPack[0] & 0xF0) == 0xA0 || (RecPack[0] & 0xF0) == 0xB0 ) Unfortunately some important information, as for instance the battery charge, do not work (e.g., battery charge is always zero). But at least now I have access to whether the UPS is on bat...

Hello Charles and Douglas, I really believe that BZ2200-BR model is the same as mine BZ1200-BR, with different capacity. If you see the BZ2200-BR specs you will notice the manufacturer "APC-Microsol". Those no-breaks have a USB port in it, but in fact it is a serial<->usb cable, usually uses the port "/dev/cuaU0". In mine, the serial<->usb chip is from FTDI, and