I built the latest stable 2.4.1, and the same results. I am guessing it has to do with not recognizing firmware version.<br><br>Here is the command line: Note this is using ubuntu<br>$ ps auxwww|grep apcsmart<br>nut 6078 0.0 0.0 1956 496 ? Ss 18:36 0:00 /lib/nut/apcsmart -a ups1<br>
<br>$ ./drivers/apcsmart -a ups1 -DDDD -u nut<br>Network UPS Tools - APC Smart protocol driver 2.00 (2.4.1)<br>APC command table version 2.0<br>debug level is '4'<br>Attempting firmware lookup<br>Not found in table - trying normal method<br>
APC - Attempting to find command set<br>APC - Parsing out command set<br>UPS supports variable [ups.model]<br>poll_data: ups.model<br>UPS supports variable [input.quality]<br>poll_data: input.quality<br>UPS supports command [test.panel.start]<br>
UPS supports variable [input.transfer.reason]<br>poll_data: input.transfer.reason<br>UPS supports command [shutdown.stayoff]<br>UPS supports command [shutdown.return]<br>UPS supports command [test.failure.start]<br>UPS supports command [test.battery.start]<br>
UPS supports command [test.battery.stop]<br>UPS supports variable [ups.test.result]<br>poll_data: ups.test.result<br>UPS supports variable [ups.firmware]<br>poll_data: ups.firmware<br>UPS supports variable [ups.serial]<br>
poll_data: ups.serial<br>APC - UPS capabilities determined<br>Detected BACK-UPS PRO 1400 [QB0306221917] on /dev/ttyS0<br>update_status<br>update_info_all: starting<br>poll_data: ups.firmware<br>poll_data: ups.model<br>poll_data: ups.serial<br>
poll_data: ups.test.result<br>poll_data: input.quality<br>poll_data: input.transfer.reason<br>update_info_all: done<br>dstate_init: sock /var/run/nut/apcsmart-ups1 open on fd 5<br>update_status<br>update_info_normal: starting<br>
poll_data: ups.test.result<br>poll_data: input.quality<br>poll_data: input.transfer.reason<br>update_info_normal: done<br><br><br><br><br><div class="gmail_quote">On Fri, Aug 14, 2009 at 6:40 PM, Charles Lepple <span dir="ltr"><<a href="mailto:clepple@gmail.com">clepple@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">On Fri, Aug 14, 2009 at 5:33 PM, Brian Wagener<<a href="mailto:cptanpanic@gmail.com">cptanpanic@gmail.com</a>> wrote:<br>
> I just installed nut, and I it is detected but I don't get any usefull<br>
> information. I have the serial cable that came with it which is a<br>
> 940-0024C and I tried setting that in the driver, but no difference. What<br>
> can I do to get stuff like battery voltage and such?<br>
> Thanks,<br>
> Brian<br>
><br>
> upsc ups1@localhost<br>
> <a href="http://driver.name" target="_blank">driver.name</a>: apcsmart<br>
> driver.parameter.cable: 940-0024C<br>
> driver.parameter.pollinterval: 2<br>
> driver.parameter.port: /dev/ttyS0<br>
> driver.version: 2.2.1-<br>
> driver.version.internal: 1.99.8<br>
<br>
</div>I would suggest upgrading to the latest source release (2.4.1, or even<br>
the SVN trunk) if possible - a lot of tables are hardcoded in that<br>
driver, and you may need to tweak the source code to get things right.<br>
<br>
At the very least, check how your OS/distro is starting NUT (ps<br>
auxwww|grep apcsmart) and re-run the command with a single "-D"<br>
parameter. The resulting debug output should give us an idea as to how<br>
it is detecting your UPS' capabilities.<br>
<br>
--<br>
<font color="#888888">- Charles Lepple<br>
</font></blockquote></div><br>