[Nut-upsdev] FSP UPS EP-650 /1K and other, NUT port for mipsel routers like avm fritz!box, firmware usb interface issues

[thomas schorpp]

Am 01.10.2011 07:53, schrieb thomas schorpp:

> Stated above, same for the FSP EP-1K, except of temperature and battery
> voltage:
>
> battery.charge: 100
> battery.runtime: 4000
> battery.voltage: 27.40
> battery.voltage.nominal: 24.0
> beeper.status: enabled
> device.type: ups
> driver.flag.novendor: enabled
> driver.name: blazer_usb
> driver.parameter.chargetime: 8
> driver.parameter.idleload: 30
> driver.parameter.pollinterval: 15
> driver.parameter.port: auto
> driver.parameter.productid: 5161
> driver.parameter.runtimecal: 1200,100,3200,50
> driver.parameter.vendorid: 0665
> driver.version: 2.4.3
> driver.version.internal: 0.03
> input.current.nominal: 5.0
> input.frequency: 50.1
> input.frequency.nominal: 50
> input.voltage: 231.2
> input.voltage.fault: 231.2
> input.voltage.nominal: 220
> output.voltage: 231.2
> ups.delay.shutdown: 30
> ups.delay.start: 180
> ups.load: 27
> ups.productid: 5161
> ups.status: OL
> ups.type: offline / line interactive
>
> Cmds an Alarms untested but the EP-650 is already in the supported
> devices list.
>
> Can You confirm no usb req timeouts for Your device at 2sec polling for
> hours?
>
> Oct 1 06:24:28 fritz.box blazer_usb[11636]: Communications with UPS
> lost: status read failed!
> Oct 1 06:24:43 fritz.box blazer_usb[11636]: Communications with UPS
> lost: status read failed!
> Oct 1 06:24:58 fritz.box blazer_usb[11636]: Communications with UPS
> re-established
>
> USB-Sniffing the proprietary viewpower software I found it uses another
> protocol, with "QPI" requests 1/sec,
> sniff dumps attached (propably off list due to size limits).
>
> I will try some replays with a modified blazer_usb driver or dummy-ups
> and tools/device-recorder.sh.
>
> y
> tom
>
>

For the FSP UPS EP-1K and other with the cypress/inno tech usb idVID=0665
PID=5161

the following commands are working so far:

~$ grep -i handled /var/log/syslog*
/var/log/syslog:Oct  3 08:38:30 fritz.box blazer_usb[11636]: instcmd: command [beeper.toggle] handled
/var/log/syslog:Oct  3 08:38:55 fritz.box blazer_usb[11636]: instcmd: command [beeper.toggle] handled
/var/log/syslog.1:Oct  2 15:56:12 fritz.box blazer_usb[11636]: instcmd: command [test.battery.start.quick] handled

according to viewpower 2.08 this ups does support scheduled load switching and shutdown/restore cmds, too,
BTW is "beeper.toggle" = "Alarms on/off"?

But the usb disconnects and timeouts still occur but are well handled by the fritz!box usb controller and 2.6.32 kernel:

/var/log/syslog.1:Oct  2 17:58:18 fritz.box blazer_usb[11636]: Communications with UPS lost: status read failed!
/var/log/syslog.1:Oct  2 17:58:33 fritz.box blazer_usb[11636]: Communications with UPS lost: status read failed!
/var/log/syslog.1:Oct  2 17:58:48 fritz.box blazer_usb[11636]: Communications with UPS re-established
/var/log/syslog.1:Oct  2 18:19:33 fritz.box blazer_usb[11636]: Communications with UPS lost: status read failed!
/var/log/syslog.1:Oct  2 18:19:48 fritz.box blazer_usb[11636]: Communications with UPS lost: status read failed!
/var/log/syslog.1:Oct  2 18:20:03 fritz.box blazer_usb[11636]: Communications with UPS re-established
/var/log/syslog.1:Oct  2 19:09:19 fritz.box blazer_usb[11636]: Communications with UPS lost: status read failed!
/var/log/syslog.1:Oct  2 19:09:33 fritz.box blazer_usb[11636]: Communications with UPS re-established
/var/log/syslog.1:Oct  2 19:26:19 fritz.box blazer_usb[11636]: Communications with UPS lost: status read failed!
/var/log/syslog.1:Oct  2 19:26:33 fritz.box blazer_usb[11636]: Communications with UPS lost: status read failed!
/var/log/syslog.1:Oct  2 19:26:48 fritz.box blazer_usb[11636]: Communications with UPS re-established
/var/log/syslog.1:Oct  2 20:39:05 fritz.box blazer_usb[11636]: Communications with UPS lost: status read failed!
/var/log/syslog.1:Oct  2 20:39:19 fritz.box blazer_usb[11636]: Communications with UPS re-established
/var/log/syslog.1:Oct  2 20:45:35 fritz.box blazer_usb[11636]: Communications with UPS lost: status read failed!
/var/log/syslog.1:Oct  2 20:45:49 fritz.box blazer_usb[11636]: Communications with UPS re-established
/var/log/syslog.1:Oct  3 00:52:52 fritz.box blazer_usb[11636]: Communications with UPS lost: status read failed!
/var/log/syslog.1:Oct  3 00:53:06 fritz.box blazer_usb[11636]: Communications with UPS re-established
/var/log/syslog.1:Oct  3 03:32:08 fritz.box blazer_usb[11636]: Communications with UPS lost: status read failed!
/var/log/syslog.1:Oct  3 03:32:23 fritz.box blazer_usb[11636]: Communications with UPS lost: status read failed!
/var/log/syslog.1:Oct  3 03:32:38 fritz.box blazer_usb[11636]: Communications with UPS re-established
/var/log/syslog.1:Oct  3 04:28:54 fritz.box blazer_usb[11636]: Communications with UPS lost: status read failed!
/var/log/syslog.1:Oct  3 04:29:08 fritz.box blazer_usb[11636]: Communications with UPS lost: status read failed!
/var/log/syslog.1:Oct  3 04:29:23 fritz.box blazer_usb[11636]: Communications with UPS lost: status read failed!
/var/log/syslog.1:Oct  3 04:29:38 fritz.box upsd[11637]: Data for UPS [ups] is stale - check driver
/var/log/syslog.1:Oct  3 04:29:38 tom3 upsmon[3640]: Poll UPS [ups at fritz.box] failed - Data stale
/var/log/syslog.1:Oct  3 04:29:38 tom3 upsmon[3640]: Communications with UPS ups at fritz.box lost
/var/log/syslog.1:Oct  3 04:29:43 tom3 upsmon[3640]: Poll UPS [ups at fritz.box] failed - Data stale
/var/log/syslog.1:Oct  3 04:29:48 tom3 upsmon[3640]: Poll UPS [ups at fritz.box] failed - Data stale
/var/log/syslog.1:Oct  3 04:29:53 tom3 upsmon[3640]: Poll UPS [ups at fritz.box] failed - Data stale
/var/log/syslog.1:Oct  3 04:29:53 fritz.box blazer_usb[11636]: Communications with UPS re-established
/var/log/syslog.1:Oct  3 04:29:53 fritz.box upsd[11637]: UPS [ups] data is no longer stale
/var/log/syslog.1:Oct  3 04:29:58 tom3 upsmon[3640]: Communications with UPS ups at fritz.box established
/var/log/syslog.1:Oct  3 04:48:24 fritz.box blazer_usb[11636]: Communications with UPS lost: status read failed!
/var/log/syslog.1:Oct  3 04:48:38 fritz.box blazer_usb[11636]: Communications with UPS re-established
Oct  3 17:35:20 tom3 upsmon[3640]: Poll UPS [ups at fritz.box] failed - Data stale
Oct  3 17:35:20 tom3 upsmon[3640]: Communications with UPS ups at fritz.box lost
Oct  3 17:35:25 tom3 upsmon[3640]: Poll UPS [ups at fritz.box] failed - Data stale
Oct  3 17:35:30 tom3 upsmon[3640]: Poll UPS [ups at fritz.box] failed - Data stale
Oct  3 17:35:30 fritz.box blazer_usb[11636]: Communications with UPS re-established
Oct  3 17:35:30 fritz.box upsd[11637]: UPS [ups] data is no longer stale

root at fritz:/var/mod/root# dmesg |grep usb
usb 1-1.4: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -145
usb 1-1.4: reset low speed USB device using musb_hdrc and address 9
root at fritz:/var/mod/root# dmesg |grep usb
usb 1-1.4: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -145
usb 1-1.4: reset low speed USB device using musb_hdrc and address 9
usb 1-1.4: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -145
usb 1-1.4: reset low speed USB device using musb_hdrc and address 9
usb 1-1.4: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -145
usb 1-1.4: reset low speed USB device using musb_hdrc and address 9

What is -E 145, cannot find it in 2.6.32 mips kernel source err*.h ?

The via 8237 usb controller with 2.6.38 on the desktop host
00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South]
did not reset the ups successfully, power cycle of the ups was required.

This does not happen with viewpower even polling at 1/sec  according to viewpower logs.

Fortron Source / Inno-Tech(.in?) should release a firmware fix for better compatibility with NUT,

since surely not many people use this 230MB big gui java-monster viewpower, not working on debian 6 like assured in system requirements,
cause the "statically linked" 32bit-java vm needs  net.ipv6.bindv6only = 0 to open sockets
  
and it does not find the correct ttyUSB device on 2.6.38 if you got another tty*S* devices and there's no customer support at all
to find for viewpower users and using such a power consuming host viewpower needs to monitor a ups in power failure case
will drain the battery very fast, that's very unreasonably,
a 10Watts router will run for many hours on battery and allows alarm users, controlling, monitor the ups in line power failure.

You can find an alpha version of the NUT port for avm.de fritzbox and possibly other SOHO routers here:
http://freetz.org/ticket/1521
For support and contributions add to the ticket, pls.

y
tom