[Nut-upsuser] Cannot access Patriot Pro II from new system

[Olav Seyfarth]

Hi list,

on my previous (lenny or squeeze) machine, I had it up and running, but
that machine and configs are gone - and on my new jessie machine (see
device and config details below) I cannot start the driver:

# /lib/nut/bestups -DDDDD -a Patriot_Pro_II_750
   0.000000    debug level is '5'
   0.000806    send_to_all: SETINFO device.type "ups"
   0.000842    send_to_all: SETINFO driver.version "2.7.2"
   0.000862    send_to_all: SETINFO driver.version.internal "1.06"
   0.000884    send_to_all: SETINFO driver.name "bestups"
  17.264987    Unable to detect a Best/SOLA or Phoenix protocol UPS

I see no other relevant log entries.

I've noticed this tread:
http://lists.alioth.debian.org/pipermail/nut-upsdev/2014-November/006801.html
But unless I misunderstood something, the driver bestups should still
work in jessie, right?

Might this be a clable issue?

The cable is the original cable that used to work with Best software (on
Windows XP) and NUT (unsure which version, default repos). I checked
it's wiring, it's as described in
http://www.networkupstools.org/cables.html#_phoenixtec_best_power except
that PC Pins 1,8 and 9 are connected to ground/shield.

Or a serial setup failure?

stty tells me that the driver sets speed to 2400baud, but does that mean
that the driver can establish a connection to the device?
How to tell?

If I interpreted other posts correctly, I should be able to use a
terminal program to access the UPS device. So I started minicom  -D
/dev/ttyS0 (without and with " -b 2400" or " -b 9600") and tried to
enter "Q1 \r" but I don't even get a local echo.

So what does that mean and what else can I try?

Thank you for your ideas and hints!
Olav

P.S.: Once it works, should I contribute my values to
https://github.com/networkupstools/nut-ddl/tree/master/Best_Power ? How?

__________________________________

My new machine is ASUS H7-Plus; it has an internal serial connector
(with tappet(?) so that I can only plug the internal cable in one way)
but I bought a 3rd pary shield.
My OS is jessie, Debian kernel 3.16.7-ckt17-1
My NUT version: 2.7.2-4, installed via apt-get from repos
My UPS is a Patriot Pro II 750, P/N PP0750E S/N 186PFA4126 REV:00 (with
battery replaced),
manual available
http://powerquality.eaton.de/Products-services/legacy/patriot-pro-info.asp,
should be very similar to
http://www.networkupstools.org/ddl/Best_Power/Patriot_Pro_II_400.html
My config (all to default, except for these lines):

/etc/nut/nut.conf:
MODE=standalone

/etc/nut/ups.conf:
[Patriot_Pro_II_750]
    driver = bestups
    port = /dev/ttyS0

/etc/nut/upsd.users:
[upsmon]
    upsmon master
    password = somepass

/etc/nut/upsmon.conf:
MONITOR Patriot_Pro_II_750 at localhost 1 upsmon somepass master

/etc/passwd:
nut:x:112:119::/var/lib/nut:/bin/false

/etc/group:
dialout:x:20:nut
nut:x:119:

/etc/udev/rules.d/99_nut-serialups.rules:
KERNEL=="ttyS0", GROUP="nut"
________________

# ls -l /etc/nut
-rw-r----- 1 root nut  1544 Nov 23 12:36 nut.conf
-rw-r----- 1 root nut  4634 Nov 23 14:03 ups.conf
-rw-r----- 1 root nut  4577 Nov 23 13:26 upsd.conf
-rw-r----- 1 root nut  2177 Nov 23 14:04 upsd.users
-rw-r----- 1 root nut 15233 Nov 23 14:04 upsmon.conf
-rw-r----- 1 root nut  3887 Mär 20  2015 upssched.conf

# ls -l /dev/ttyS0
crw-rw---- 1 root nut 4, 64 Nov 23 14:13 /dev/ttyS0

# setserial -gav /dev/ttyS0
/dev/ttyS0, Line 0, UART: 16550A, Port: 0x03f8, IRQ: 4
    Baud_base: 115200, close_delay: 50, divisor: 0
    closing_wait: 3000
    Flags: spd_normal skip_test

# stty -F /dev/ttyS0
speed 2400 baud; line = 0;
min = 1; time = 0;
-brkint -icrnl -imaxbel
-opost -onlcr
-isig -icanon -iexten -echo -echoe -echok -echoctl -echoke

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 665 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20151123/7d52a602/attachment.sig>