thr3ads.net - Nut upsuser - [Nut-upsuser] APC BACK UPS 2200 model BZ2200BI-BR [Aug 2015]

If this information is useful, please help other people find it:
Share via:

Mario Lobo

2015-Aug-20 22:33 UTC

[Nut-upsuser] APC BACK UPS 2200 model BZ2200BI-BR

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 10.2-STABLE #2 r286923
UPS: APC BACK UPS 2200 model BZ2200BI-BR (usb interface)
     using a printer-like usb cable (bundled)

When I plug it in, here is what comes up:

ugen1.2: <APC BY SCHNEIDER ELECTRIC> at usbus1
umodem0: <APC BY SCHNEIDER ELECTRIC APC USB SERIAL CONVERTER., 
class 2/0, rev 2.00/1.00, addr 2> on usbus1 
umodem0: data interface 1, has no CM over data, has no break


[>]usbconfig list

ugen1.1: <UHCI root HUB Intel> at usbus1, cfg=0 md=HOST spd=FULL
(12Mbps) pwr=SAVE (0mA) 

ugen0.1: <UHCI root HUB Intel> at usbus0, cfg=0
md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA) 

ugen2.1: <EHCI root HUB Intel>at usbus2, cfg=0 md=HOST spd=HIGH
(480Mbps) pwr=SAVE (0mA) 

ugen1.2:<APC USB SERIAL CONVERTER. APC BY SCHNEIDER ELECTRIC> at
usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA)


And here are the devices I get after pluging it in:

ttyU0
ttyU0.init
ttyU0.lock

cuaU0
cuaU0.init
cuaU0.lock

ugen1.2 (ugen1.2 -> usb/1.2.0)

(no umodem0 device shows)


** ups.conf

[lobos]
  driver = solis
  port = /dev/ttyU0 (or cuaU0, or ugen1.2)


*** RESULTS

** ugen1.2

[>]/usr/local/libexec/nut/solis -D -a lobos -u root
Network UPS Tools - Microsol Solis UPS driver 0.62 (2.7.3)
   0.000000     debug level is '1'
   0.001551     tcgetattr(/dev/ugen1.2): Inappropriate ioctl for device

** ttyU0

[>]/usr/local/libexec/nut/solis -D -a lobos -u root
Network UPS Tools - Microsol Solis UPS driver 0.62 (2.7.3)
   0.000000     debug level is '1'
  21.249301     Solis not detected! aborting ...

** cuaU0

[>]/usr/local/libexec/nut/solis -D -a lobos -u root
Network UPS Tools - Microsol Solis UPS driver 0.62 (2.7.3)
   0.000000     debug level is '1'
  21.065536     Solis not detected! aborting ...


using 'upsdrvctl -t -u root start lobos' yields the same results.


On windows it works with the software that I downloaded for it
but the server is FreeBSD. Windows is just the desktop I use for
occasional audio production.


Would anyone have any pointers of what else I can try to make this
work?

Thanks for any suggestions. 

-- 
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since 2.2.8 [not Pro-Audio.... YET!!]

"UNIX was not designed to stop you from doing stupid things, 
because that would also stop you from doing clever things."

e430benz98 at yahoo.com

2015-Aug-20 23:18 UTC

head link

[Nut-upsuser] APC BACK UPS 2200 model BZ2200BI-BR

I am not an expert on this matter but I can tell you I am having issues with
Freebsd 10.2 with a Tripp Lite ups myself

Hopefully a dev can look in to FreeBSD 10.2

Sent from my LG G3.

-----Original Message-----
From: Mario Lobo <mlobo at digiart.art.br>
To: nut-upsuser at lists.alioth.debian.org
Sent: Thu, 20 Aug 2015 3:50 PM
Subject: [Nut-upsuser] APC BACK UPS 2200 model BZ2200BI-BR

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 10.2-STABLE #2 r286923
UPS: APC BACK UPS 2200 model BZ2200BI-BR (usb interface)
     using a printer-like usb cable (bundled)

When I plug it in, here is what comes up:

ugen1.2: <APC BY SCHNEIDER ELECTRIC> at usbus1
umodem0: <APC BY SCHNEIDER ELECTRIC APC USB SERIAL CONVERTER., 
class 2/0, rev 2.00/1.00, addr 2> on usbus1 
umodem0: data interface 1, has no CM over data, has no break


[>]usbconfig list

ugen1.1: <UHCI root HUB Intel> at usbus1, cfg=0 md=HOST spd=FULL
(12Mbps) pwr=SAVE (0mA) 

ugen0.1: <UHCI root HUB Intel> at usbus0, cfg=0
md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA) 

ugen2.1: <EHCI root HUB Intel>at usbus2, cfg=0 md=HOST spd=HIGH
(480Mbps) pwr=SAVE (0mA) 

ugen1.2:<APC USB SERIAL CONVERTER. APC BY SCHNEIDER ELECTRIC> at
usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA)


And here are the devices I get after pluging it in:

ttyU0
ttyU0.init
ttyU0.lock

cuaU0
cuaU0.init
cuaU0.lock

ugen1.2 (ugen1.2 -> usb/1.2.0)

(no umodem0 device shows)


** ups.conf

[lobos]
  driver = solis
  port = /dev/ttyU0 (or cuaU0, or ugen1.2)


*** RESULTS

** ugen1.2

[>]/usr/local/libexec/nut/solis -D -a lobos -u root
Network UPS Tools - Microsol Solis UPS driver 0.62 (2.7.3)
   0.000000     debug level is '1'
   0.001551     tcgetattr(/dev/ugen1.2): Inappropriate ioctl for device

** ttyU0

[>]/usr/local/libexec/nut/solis -D -a lobos -u root
Network UPS Tools - Microsol Solis UPS driver 0.62 (2.7.3)
   0.000000     debug level is '1'
  21.249301     Solis not detected! aborting ...

** cuaU0

[>]/usr/local/libexec/nut/solis -D -a lobos -u root
Network UPS Tools - Microsol Solis UPS driver 0.62 (2.7.3)
   0.000000     debug level is '1'
  21.065536     Solis not detected! aborting ...


using 'upsdrvctl -t -u root start lobos' yields the same results.


On windows it works with the software that I downloaded for it
but the server is FreeBSD. Windows is just the desktop I use for
occasional audio production.


Would anyone have any pointers of what else I can try to make this
work?

Thanks for any suggestions. 

-- 
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since 2.2.8 [not Pro-Audio.... YET!!]

"UNIX was not designed to stop you from doing stupid things, 
because that would also stop you from doing clever things."

_______________________________________________
Nut-upsuser mailing list
Nut-upsuser at lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20150820/0e944e38/attachment.html>

Charles Lepple

2015-Aug-21 02:26 UTC

head link

[Nut-upsuser] APC BACK UPS 2200 model BZ2200BI-BR

On Aug 20, 2015, at 6:33 PM, Mario Lobo <mlobo at digiart.art.br>
wrote:> 
> ** cuaU0
> 
> [>]/usr/local/libexec/nut/solis -D -a lobos -u root
> Network UPS Tools - Microsol Solis UPS driver 0.62 (2.7.3)
>   0.000000     debug level is '1'
>  21.065536     Solis not detected! aborting ...
It looks like /dev/cuaU0 is the port that was suggested for a similarly-named
model last year:

http://article.gmane.org/gmane.comp.monitoring.nut.user/8554

The binary patches mentioned in that thread have been superseded by source code
chances that are part of NUT 2.7.3.

Unfortunately, as you have seen, the solis driver does not have much debug
output. What happens when you run it under ktrace?

-- 
Charles Lepple
clepple at gmail

Charles Lepple

2015-Aug-21 13:41 UTC

head link

[Nut-upsuser] APC BACK UPS 2200 model BZ2200BI-BR

On Aug 21, 2015, at 9:19 AM, Mario Lobo <mlobo at digiart.art.br>
wrote:> 
> On Aug 20, 2015, at 10:26 PM, Charles Lepple <clepple at gmail.com>
wrote:
>> 
>> On Aug 20, 2015, at 6:33 PM, Mario Lobo <mlobo at digiart.art.br>
wrote:
>>> 
>>> ** cuaU0
>>> 
>>> [>]/usr/local/libexec/nut/solis -D -a lobos -u root
>>> Network UPS Tools - Microsol Solis UPS driver 0.62 (2.7.3)
>>>  0.000000     debug level is '1'
>>> 21.065536     Solis not detected! aborting ...
>> 
>> It looks like /dev/cuaU0 is the port that was suggested for a
similarly-named model last year:
>> 
>> http://article.gmane.org/gmane.comp.monitoring.nut.user/8554
>> 
>> The binary patches mentioned in that thread have been superseded by
source code chances that are part of NUT 2.7.3.
>> 
>> Unfortunately, as you have seen, the solis driver does not have much
debug output. What happens when you run it under ktrace?
> Man ... the output of ktrace is really big! it produced an output file
> of 200 k, attached to this e-mail (solis.txt).
> 
> I don't even know what to look for!
> 
> Do you have any ideas?
It's fairly large, but it compresses well. (Please keep the list CC'd -
this is how people can find this information in the future.)

Not sure what to look for yet. It might be easier to add in the debug calls to
the source code-- can you try building NUT from source? If you installed via the
ports tree (as opposed to binary packages), you should have most of the
dependencies installed. You might also need libtool and autoconf, as mentioned
in the second link below:

http://www.networkupstools.org/docs/developer-guide.chunked/ar01s03.html#_source_code_management
and
http://www.networkupstools.org/docs/developer-guide.chunked/ar01s03.html#building

-- 
Charles Lepple
clepple at gmail


-------------- next part --------------
A non-text attachment was scrubbed...
Name: solis.txt.gz
Type: application/x-gzip
Size: 19492 bytes
Desc: not available
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20150821/fcf93e52/attachment-0001.bin>

Charles Lepple

2015-Aug-23 15:09 UTC

head link

[Nut-upsuser] APC BACK UPS 2200 model BZ2200BI-BR

On Aug 21, 2015, at 10:10 AM, Mario Lobo <mlobo at digiart.art.br>
wrote:> 
>> Not sure what to look for yet. It might be easier to add in the debug
>> calls to the source code-- can you try building NUT from source? If
>> you installed via the ports tree (as opposed to binary packages), you
>> should have most of the dependencies installed. You might also need
>> libtool and autoconf, as mentioned in the second link below:
>> 
>>
http://www.networkupstools.org/docs/developer-guide.chunked/ar01s03.html#_source_code_management
>> and
>>
http://www.networkupstools.org/docs/developer-guide.chunked/ar01s03.html#building
>> 
> 
> Yes I did build it through ports. I try to build a debug version of it.
Mario,

I added a few debug statements throughout the solis driver:

https://github.com/networkupstools/nut/tree/solis_debug

If you run into trouble with the initial build, there will be a tarball snapshot
here shortly that bypasses some of the autoconf/libtool issues (look for the
nut-* link under step 5):

http://buildbot.networkupstools.org/public/nut/builders/Debian-x64-gcc/builds/389

-- 
Charles Lepple
clepple at gmail

Mario Lobo

2015-Aug-23 21:58 UTC

head link

[Nut-upsuser] APC BACK UPS 2200 model BZ2200BI-BR

On Sun, 23 Aug 2015 11:09:03 -0400
Charles Lepple <clepple at gmail.com> wrote:
> On Aug 21, 2015, at 10:10 AM, Mario Lobo <mlobo at digiart.art.br>
wrote:
> > 
> >> Not sure what to look for yet. It might be easier to add in the
> >> debug calls to the source code-- can you try building NUT from
> >> source? If you installed via the ports tree (as opposed to binary
> >> packages), you should have most of the dependencies installed. You
> >> might also need libtool and autoconf, as mentioned in the second
> >> link below:
> >> 
> >>
http://www.networkupstools.org/docs/developer-guide.chunked/ar01s03.html#_source_code_management
> >> and
> >>
http://www.networkupstools.org/docs/developer-guide.chunked/ar01s03.html#building
> >> 
> > 
> > Yes I did build it through ports. I try to build a debug version of
> > it.
> 
> Mario,
> 
> I added a few debug statements throughout the solis driver:
> 
> https://github.com/networkupstools/nut/tree/solis_debug
> 
> If you run into trouble with the initial build, there will be a
> tarball snapshot here shortly that bypasses some of the
> autoconf/libtool issues (look for the nut-* link under step 5):
> 
>
http://buildbot.networkupstools.org/public/nut/builders/Debian-x64-gcc/builds/389
> 
Hi Charles!

Like I said on my last e-mail, I managed to build a debug version of
solis.

Here is an output:

=============================================653             upsdrv_initinfo();
(gdb) next
Detected Solis 1.0 on /dev/cuaU0
UPS Date 1999/09/23
System Date 2015/08/23 day of week Sun
UPS internal Time 13:02:49
Shutdown programming not atived
654             upsdrv_updateinfo();
(gdb) next
656             if (dstate_getinfo("driver.flag.ignorelb")) {
(gdb) next
679             dstate_init(progname, upsname);
(gdb) next
682             dstate_setinfo("driver.parameter.pollinterval",
"%d",
poll_interval); (gdb) next
685             dstate_setinfo("driver.parameter.synchronous",
"%s",
(gdb) next
689             if (dstate_getinfo("ups.mfr") != NULL)
(gdb) next
690                     dstate_setinfo("device.mfr", "%s",
dstate_getinfo("ups.mfr")); (gdb) next
691             if (dstate_getinfo("ups.model") != NULL)
(gdb) next
692                     dstate_setinfo("device.model", "%s",
dstate_getinfo("ups.model")); (gdb) next
693             if (dstate_getinfo("ups.serial") != NULL)
(gdb) next
696             if (nut_debug_level == 0) {
(gdb) next
697                     background();
(gdb) next

Program exited normally.
(gdb) 
=============================================
Funny... Under gdb, it detects something, even if it is a "wrong" ups.

Running it straight, it outputs this:

[~]>/usr/local/libexec/nut/solis -a lobos -u root
Network UPS Tools - Microsol Solis UPS driver 0.62 (2.7.3)
Solis not detected! aborting ...

I just downloaded nut-2.7.3.1.tar.gz from the link you provided and
I'll try to give it a spin. I can do it through the ports because there
aren't any code patches. Only script patches, so you're free to change
the code around as much as needed.

Thanks for sticking with me on this!
-- 
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since 2.2.8 [not Pro-Audio.... YET!!]

"UNIX was not designed to stop you from doing stupid things, 
because that would also stop you from doing clever things."

Mario Lobo

2015-Aug-23 22:26 UTC

head link

[Nut-upsuser] APC BACK UPS 2200 model BZ2200BI-BR (update)

On Sun, 23 Aug 2015 11:09:03 -0400
Charles Lepple <clepple at gmail.com> wrote:
> On Aug 21, 2015, at 10:10 AM, Mario Lobo <mlobo at digiart.art.br>
wrote:
> > 
> >> Not sure what to look for yet. It might be easier to add in the
> >> debug calls to the source code-- can you try building NUT from
> >> source? If you installed via the ports tree (as opposed to binary
> >> packages), you should have most of the dependencies installed. You
> >> might also need libtool and autoconf, as mentioned in the second
> >> link below:
> >> 
> >>
http://www.networkupstools.org/docs/developer-guide.chunked/ar01s03.html#_source_code_management
> >> and
> >>
http://www.networkupstools.org/docs/developer-guide.chunked/ar01s03.html#building
> >> 
> > 
> > Yes I did build it through ports. I try to build a debug version of
> > it.
> 
> Mario,
> 
> I added a few debug statements throughout the solis driver:
> 
> https://github.com/networkupstools/nut/tree/solis_debug
> 
> If you run into trouble with the initial build, there will be a
> tarball snapshot here shortly that bypasses some of the
> autoconf/libtool issues (look for the nut-* link under step 5):
> 
>
http://buildbot.networkupstools.org/public/nut/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 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 bytes) => a0 04 02 06 1d 0d
03 00 00 00 01 00 17 
   2.048358      91 49 5e 5e dc fe bb 47 83 ad 1a 09
   2.048371     getbaseinfo: requesting 25 bytes from ser_get_buf_len()
   3.132287     getbaseinfo: received 25 bytes from ser_get_buf_len()
   3.132321     CommReceive: RecPack: (25 bytes) => a0 0a 02 07 1d 0d
03 00 00 00 01 00 17 
   3.132337      91 49 5e 5e e3 fe bb 46 88 ac 1a 0a
   3.132350     getbaseinfo: requesting 25 bytes from ser_get_buf_len()
   4.217261     getbaseinfo: received 25 bytes from ser_get_buf_len()
   4.217294     CommReceive: RecPack: (25 bytes) => a0 f4 01 08 1d 0d
03 00 00 00 01 00 17 
   4.217309      91 49 5e 5e d1 fe bb 46 88 ad 02 0b
   4.217322     getbaseinfo: requesting 25 bytes from ser_get_buf_len()
   5.302236     getbaseinfo: received 25 bytes from ser_get_buf_len()
   5.302268     CommReceive: RecPack: (25 bytes) => a0 0b 02 09 1d 0d
03 00 00 00 01 00 17 
   5.302283      91 49 5e 5e d4 fe bb 46 88 ad 1e 0a
   5.302296     getbaseinfo: requesting 25 bytes from ser_get_buf_len()
   6.386210     getbaseinfo: received 25 bytes from ser_get_buf_len()
   6.386241     CommReceive: RecPack: (25 bytes) => a0 1b 02 0a 1d 0d
03 00 00 00 01 00 17 
   6.386256      91 49 5e 5e 00 fe bb 46 88 ad 1d 0a
   6.386269     getbaseinfo: requesting 25 bytes from ser_get_buf_len()
   7.471190     getbaseinfo: received 25 bytes from ser_get_buf_len()
   7.471222     CommReceive: RecPack: (25 bytes) => a0 f6 01 0b 1d 0d
03 00 00 00 01 00 17 
   7.471236      91 49 5e 5e da fe bb 47 83 ac 1a 09
   7.471249     getbaseinfo: requesting 25 bytes from ser_get_buf_len()
   8.557168     getbaseinfo: received 25 bytes from ser_get_buf_len()
   8.557200     CommReceive: RecPack: (25 bytes) => a0 f4 01 0c 1d 0d
03 00 00 00 01 00 17 
   8.557215      91 49 5e 5e d0 fe bb 46 88 ad 1e 0a
   8.557241     getbaseinfo: requesting 25 bytes from ser_get_buf_len()
   9.642144     getbaseinfo: received 25 bytes from ser_get_buf_len()
   9.642177     CommReceive: RecPack: (25 bytes) => 0d 02 0d 1d 0d 03
00 00 00 01 00 17 91 
   9.642192      49 5e 5e f5 fe bb 47 83 ad 02 09 a0
   9.642209     getbaseinfo: requesting 25 bytes from ser_get_buf_len()
  10.727265     getbaseinfo: received 25 bytes from ser_get_buf_len()
  10.727293     CommReceive: RecPack: (25 bytes) => 02 0e 1d 0d 03 00
00 00 01 00 17 91 49 
  10.727303      5e 5e d9 fe bb 46 88 ac 1e 0b a0 1d
  10.727313     getbaseinfo: requesting 25 bytes from ser_get_buf_len()
  11.811101     getbaseinfo: received 25 bytes from ser_get_buf_len()
  11.811136     CommReceive: RecPack: (25 bytes) => 02 0f 1d 0d 03 00
00 00 01 00 17 91 49 
  11.811151      5e 5e 07 fe bb 47 88 ac 1c 0a a0 04
  11.811164     getbaseinfo: requesting 25 bytes from ser_get_buf_len()
  12.896076     getbaseinfo: received 25 bytes from ser_get_buf_len()
  12.896112     CommReceive: RecPack: (25 bytes) => 02 10 1d 0d 03 00
00 00 01 00 17 91 49 
  12.896127      5e 5e ed fe bb 46 88 ac 19 0a a0 07
  12.896140     getbaseinfo: requesting 25 bytes from ser_get_buf_len()
  13.981054     getbaseinfo: received 25 bytes from ser_get_buf_len()
  13.981087     CommReceive: RecPack: (25 bytes) => 02 11 1d 0d 03 00
00 00 01 00 17 91 49 
  13.981102      5e 5e ed fe bb 47 88 ad 23 0c a0 4c
  13.981115     getbaseinfo: requesting 25 bytes from ser_get_buf_len()
  15.065032     getbaseinfo: received 25 bytes from ser_get_buf_len()
  15.065066     CommReceive: RecPack: (25 bytes) => 02 12 1d 0d 03 00
00 00 01 00 17 91 49 
  15.065081      5e 5e 41 fe bb 46 83 ae 02 0a a0 1b
  15.065093     getbaseinfo: requesting 25 bytes from ser_get_buf_len()
  16.150009     getbaseinfo: received 25 bytes from ser_get_buf_len()
  16.150044     CommReceive: RecPack: (25 bytes) => 02 13 1d 0d 03 00
00 00 01 00 17 91 49 
  16.150059      5e 5e e9 fe bb 46 88 ad 1d 0a a0 f8
  16.150072     getbaseinfo: requesting 25 bytes from ser_get_buf_len()
  17.235986     getbaseinfo: received 25 bytes from ser_get_buf_len()
  17.236019     CommReceive: RecPack: (25 bytes) => 01 14 1d 0d 03 00
00 00 01 00 17 91 49 
  17.236033      5e 5e e5 fe bb 46 88 ae 1a 0a a0 ef
  17.236050     getbaseinfo: requesting 25 bytes from ser_get_buf_len()
  18.320960     getbaseinfo: received 25 bytes from ser_get_buf_len()
  18.320995     CommReceive: RecPack: (25 bytes) => 15 1d 0d 03 00 00
00 01 00 17 91 49 5e 
  18.321009      5e db fe bb 46 88 ad 1b 0a a0 f2 01
  18.321026     getbaseinfo: requesting 25 bytes from ser_get_buf_len()
  19.405941     getbaseinfo: received 25 bytes from ser_get_buf_len()
  19.405975     CommReceive: RecPack: (25 bytes) => 1d 0d 03 00 00 00
01 00 17 91 49 5e 5e 
  19.405990      df fe bb 47 88 ad 1a 0a a0 f8 01 17
  19.406003     getbaseinfo: requesting 25 bytes from ser_get_buf_len()
  20.489919     getbaseinfo: received 25 bytes from ser_get_buf_len()
  20.489953     CommReceive: RecPack: (25 bytes) => 1d 0d 03 00 00 00
01 00 17 91 49 5e 5e 
  20.489968      e6 fe bb 46 83 ad 02 0a a0 e3 01 18
  20.489981     getbaseinfo: requesting 25 bytes from ser_get_buf_len()
  21.574893     getbaseinfo: received 25 bytes from ser_get_buf_len()
  21.574925     CommReceive: RecPack: (25 bytes) => 1d 0d 03 00 00 00
01 00 17 91 49 5e 5e 
  21.574940      b4 fe bb 47 88 ad 1d 0a a0 0f 02 19
  21.574953     Solis not detected! aborting ...


I hope it helps!.

-- 
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since 2.2.8 [not Pro-Audio.... YET!!]

"UNIX was not designed to stop you from doing stupid things, 
because that would also stop you from doing clever things."

Reasonably Related Threads

Search for more possibly parallel threads

Nut upsuser - Aug 2015 - APC BACK UPS 2200 model BZ2200BI-BR

[Nut-upsuser] APC BACK UPS 2200 model BZ2200BI-BR

[Nut-upsuser] APC BACK UPS 2200 model BZ2200BI-BR

[Nut-upsuser] APC BACK UPS 2200 model BZ2200BI-BR

[Nut-upsuser] APC BACK UPS 2200 model BZ2200BI-BR

[Nut-upsuser] APC BACK UPS 2200 model BZ2200BI-BR

[Nut-upsuser] APC BACK UPS 2200 model BZ2200BI-BR

[Nut-upsuser] APC BACK UPS 2200 model BZ2200BI-BR (update)

Reasonably Related Threads