Re: [Nut-upsuser] online zinto usv

2012-06-08 Thread Arnaud Quette
Hi again Carsten,

2012/6/7 Carsten Burkhardt c.burkha...@b-c-s.de:
 Hello again,

 I have the Online Zinto A finally in use.

 -search
 lsusb -d 06da: -v
 Bus 005 Device 009: ID 06da:0601 Phoenixtec Power Co., Ltd

 -add rule
 /lib/udev/rules.d/52-nut-usbups.rules
 # Online USV-Systeme AG
 #  Online Zinto A - blazer_usb
 ATTR{idVendor}==06da, ATTR{idProduct}==0601, MODE=664, GROUP=nut

 -configure
 /etc/nut/ups.conf
 [zinto]
  driver=blazer_usb
  subdriver = phoenix
 #subdriver = cypress
 #subdriver = ippon
 #subdriver = krauler
 #protocol = zinto
 vendorid = 06da
 productid = 0601
 desc = Zinto via USB
 port = auto
 (...)

just to disambiguate for others, Carsten and I have had a separate
private discussion, which lead to the commit r3652:
http://trac.networkupstools.org/projects/nut/changeset/3652

Carsten has just acknowledged that everything is working fine with
either phoenix or ippon subdrivers.
The above commit links this USB ID with phoenix.

cheers,
Arnaud
-- 
Linux / Unix / Opensource Engineering Expert - Eaton -
http://opensource.eaton.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr

___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] online zinto usv

2012-06-07 Thread Carsten Burkhardt
Hello again,

I have the Online Zinto A finally in use.

-search
lsusb -d 06da: -v
Bus 005 Device 009: ID 06da:0601 Phoenixtec Power Co., Ltd

-add rule
/lib/udev/rules.d/52-nut-usbups.rules
# Online USV-Systeme AG
#  Online Zinto A - blazer_usb
ATTR{idVendor}==06da, ATTR{idProduct}==0601, MODE=664, GROUP=nut

-configure
/etc/nut/ups.conf
[zinto]
 driver=blazer_usb
  subdriver = phoenix
#subdriver = cypress
#subdriver = ippon
#subdriver = krauler
#protocol = zinto
vendorid = 06da
productid = 0601
desc = Zinto via USB
port = auto

-check
/lib/nut/blazer_usb -u nut -a zinto -DDD
Network UPS Tools - Megatec/Q1 protocol USB driver 0.03 (2.4.3)
   0.00 debug level is '3'
   0.083087 Checking device (06DA/0601) (005/031)
   0.105142 - VendorID: 06da
   0.105226 - ProductID: 0601
   0.105260 - Manufacturer: ONLINE
   0.105293 - Product: ZINTO
   0.105324 - Serial Number: unknown
   0.105355 - Bus: 005
   0.105385 Trying to match device
   0.105675 Device matches

-start
/etc/init.d/nut start
Starting Network UPS Tools: driver(s) upsd upsmon.

-control
upsc zinto@localhost
battery.voltage: 27.30
battery.voltage.nominal: 24.0
beeper.status: enabled
device.type: ups
driver.name: blazer_usb
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.productid: 0601
driver.parameter.subdriver: phoenix
driver.parameter.vendorid: 06da
driver.version: 2.4.3
driver.version.internal: 0.03
input.current.nominal: 4.0
input.frequency: 50.0
input.frequency.nominal: 50
input.voltage: 235.7
input.voltage.fault: 235.7
input.voltage.nominal: 230
output.voltage: 235.7
ups.delay.shutdown: 30
ups.delay.start: 180
ups.load: 20
ups.productid: 0601
ups.status: OL
ups.temperature: 66.6
ups.type: offline / line interactive
ups.vendorid: 06da

-- 
MfG
Carsten Burkhardt
 On Mon, Jan 3, 2011 at 11:45 AM, Carsten Burkhardt c.burkha...@b-c-s.de
 wrote:
 Hello,

 many thanks for your assitance.

 The help got unfortunately time outs (explore.txt)

 Looking at the VendorID and ProductID, it is likelt that this device
 is
 recognized as a /dev/tttyUSB(0|1...) device. As such you should
 probably
 point the blazer_ser or megatec drivers to this port.

 I do not have /dev/ttyUSB.

 Arjen mentioned it was likely, but you never can tell.

 If I point to /dev/bus/usb/001/006 the blazer
 or megatec Driver failed to start.

 The /dev/bus/usb/* nodes are not interchangeable with /dev/ttyUSB*
 nodes. The serial drivers such as blazer_ser and megatec need tty
 interfaces.

 Also note that after you run usbhid-ups, the /dev/ttyUSB* device nodes
 may not be there anymore. The easiest thing to do is simply unplug and
 re-plug the USB cable (you only need to do this once).

 Also on a plug cycle a ttyUSB do not create.

 Did you try setting the subdriver, vendorid and productid settings per
 the blazer_usb message as well? (Sorry if I missed that - I didn't see
 your configuration in the list of attachments.)

 Network UPS Tools - Megatec/Q1 protocol USB driver 0.03 (2.4.3)
 Network UPS Tools - UPS driver controller 2.4.3

 No supported devices found. Please check your device availability with
 'lsusb'
 and make sure you have an up-to-date version of NUT. If this does not
 help,
 try running the driver with at least 'subdriver', 'vendorid' and
 'productid'
 options specified. Please refer to the man page for details about these
 options
 (man 8 blazer).

 Driver failed to start (exit status=1)

 --
 - Charles Lepple

-- 
MfG
Carsten Burkhardt


___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser


Re: [Nut-upsuser] online zinto usv

2011-01-03 Thread Charles Lepple
[cc'ing the list again - please use reply all or reply to list.]

On Mon, Jan 3, 2011 at 11:45 AM, Carsten Burkhardt c.burkha...@b-c-s.de wrote:
 Hello,

 many thanks for your assitance.

 The help got unfortunately time outs (explore.txt)

 Looking at the VendorID and ProductID, it is likelt that this device is
 recognized as a /dev/tttyUSB(0|1...) device. As such you should probably
 point the blazer_ser or megatec drivers to this port.

 I do not have /dev/ttyUSB.

Arjen mentioned it was likely, but you never can tell.

 If I point to /dev/bus/usb/001/006 the blazer
 or megatec Driver failed to start.

The /dev/bus/usb/* nodes are not interchangeable with /dev/ttyUSB*
nodes. The serial drivers such as blazer_ser and megatec need tty
interfaces.

 Also note that after you run usbhid-ups, the /dev/ttyUSB* device nodes
 may not be there anymore. The easiest thing to do is simply unplug and
 re-plug the USB cable (you only need to do this once).

 Also on a plug cycle a ttyUSB do not create.

Did you try setting the subdriver, vendorid and productid settings per
the blazer_usb message as well? (Sorry if I missed that - I didn't see
your configuration in the list of attachments.)

Network UPS Tools - Megatec/Q1 protocol USB driver 0.03 (2.4.3)
Network UPS Tools - UPS driver controller 2.4.3

No supported devices found. Please check your device availability with 'lsusb'
and make sure you have an up-to-date version of NUT. If this does not help,
try running the driver with at least 'subdriver', 'vendorid' and 'productid'
options specified. Please refer to the man page for details about these options
(man 8 blazer).

Driver failed to start (exit status=1)

-- 
- Charles Lepple

___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser


Re: [Nut-upsuser] online zinto usv

2010-12-19 Thread Charles Lepple
On Fri, Dec 17, 2010 at 11:43 AM, Arjen de Korte nut+us...@de-korte.org wrote:
 Citeren Carsten Burkhardt c.burkha...@b-c-s.de:

 The help got unfortunately time outs (explore.txt)
 http://www.networkupstools.org/doc/2.2.0/hid-subdrivers.html

 Have you an idea for my problems?

 Looking at the VendorID and ProductID, it is likelt that this device is
 recognized as a /dev/tttyUSB(0|1...) device. As such you should probably
 point the blazer_ser or megatec drivers to this port.

Also note that after you run usbhid-ups, the /dev/ttyUSB* device nodes
may not be there anymore. The easiest thing to do is simply unplug and
re-plug the USB cable (you only need to do this once).

-- 
- Charles Lepple

___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser


[Nut-upsuser] online zinto usv

2010-12-17 Thread Carsten Burkhardt
Hello,

today I'm fighting with a Online Zinto 1000 (lsusb.txt) produced by 
Phoenixtec/Eaton ;-)
http://www.eaton.com/EatonCom/OurCompany/NewsandEvents/NewsList/CT_141334

I have tested different drivers without success (please see attachments 
usbhid-ups.txt, bcmxcp_usb.txt, blazer_usb.txt)

The help got unfortunately time outs (explore.txt)
http://www.networkupstools.org/doc/2.2.0/hid-subdrivers.html

Have you an idea for my problems?

Mit freundlichen Grüßen

Carsten
Network UPS Tools - Generic HID driver 0.34 (2.4.3) 

 
USB communication driver 0.31

/lib/nut/usbhid-ups -a zinto -x vendorid=06da -DD -x explore  nut-explore.txt
   0.00 debug level is '2'
   0.000706 upsdrv_initups...
   0.121349 Checking device (1D6B/0001) (002/001)
   0.121378 - VendorID: 1d6b
   0.121389 - ProductID: 0001
   0.121399 - Manufacturer: unknown
   0.121408 - Product: unknown
   0.121417 - Serial Number: unknown
   0.121427 - Bus: 002
   0.121436 Trying to match device
   0.121452 Device does not match - skipping
   0.121474 Checking device (06DA/0601) (001/005)
   0.143508 - VendorID: 06da
   0.143530 - ProductID: 0601
   0.143550 - Manufacturer: ONLINE
   0.143560 - Product: ZINTO
   0.143569 - Serial Number: unknown
   0.143579 - Bus: 001
   0.143588 Trying to match device
   0.143611 Device matches
   0.149519 HID descriptor length 27
   0.158535 Report Descriptor size = 27
   0.158626 Using subdriver: EXPLORE HID 0.1
   0.161540 refresh_report_buffer: expected 2 bytes, but got 8 instead
   0.161568 Path: ffa4.ffa6, Type: Input, ReportID: 0x00, Offset: 
0, Size: 8, Value: 0.00
   0.161585 Path: ffa4.ffa7, Type: Output, ReportID: 0x00, Offset: 
0, Size: 8, Value: 0.00
   0.161677 Report descriptor retrieved (Reportlen = 27)
   0.161689 Found HID device
   0.161701 Detected a UPS: ONLINE/ZINTO
   0.161712 find_nut_info: unknown info type: load.off.delay
   0.161723 find_nut_info: unknown info type: load.on.delay
   0.161733 find_nut_info: unknown info type: load.off.delay
   0.161753 upsdrv_initinfo...
   0.161769 upsdrv_updateinfo...
   0.412579 libusb_get_interrupt: Connection timed out
   0.412614 Got 0 HID objects...
   0.412625 Quick update...
   0.412721 dstate_init: sock /var/run/nut/usbhid-ups-zinto open on fd 5
   0.412746 upsdrv_updateinfo...
   0.663875 libusb_get_interrupt: Connection timed out
   0.663909 Got 0 HID objects...
   0.663920 Quick update...
   2.415153 upsdrv_updateinfo...
   2.665335 libusb_get_interrupt: Connection timed out
   2.665367 Got 0 HID objects...
   2.665378 Quick update...
   4.416828 upsdrv_updateinfo...
   4.667774 libusb_get_interrupt: Connection timed out
   4.667808 Got 0 HID objects...
   4.667819 Quick update...
^C   6.293200   Signal 2: exiting
   6.293236 upsdrv_cleanup...



Bus 001 Device 005: ID 06da:0601 Phoenixtec Power Co., Ltd 
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   1.10
  bDeviceClass0 (Defined at Interface level)
  bDeviceSubClass 0 
  bDeviceProtocol 0 
  bMaxPacketSize0 8
  idVendor   0x06da Phoenixtec Power Co., Ltd
  idProduct  0x0601 
  bcdDevice0.00
  iManufacturer   3 ONLINE
  iProduct1 ZINTO
  iSerial 0 
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   34
bNumInterfaces  1
bConfigurationValue 1
iConfiguration  0 
bmAttributes 0xa0
  (Bus Powered)
  Remote Wakeup
MaxPower  100mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   1
  bInterfaceClass 3 Human Interface Device
  bInterfaceSubClass  0 No Subclass
  bInterfaceProtocol  0 None
  iInterface  0 
HID Device Descriptor:
  bLength 9
  bDescriptorType33
  bcdHID   1.11
  bCountryCode0 Not supported
  bNumDescriptors 1
  bDescriptorType34 Report
  wDescriptorLength  27
  Report Descriptor: (length is 27)
Item(Global): Usage Page, data= [ 0xa0 0xff ] 65440
(null)
Item(Local ): Usage, data= [ 0x04 ] 4
(null)
Item(Main  ): Collection, data= [ 0x01 ] 1
Application
Item(Local ): Usage, data= [ 0x06 ] 6

Re: [Nut-upsuser] online zinto usv

2010-12-17 Thread Arjen de Korte

Citeren Carsten Burkhardt c.burkha...@b-c-s.de:


The help got unfortunately time outs (explore.txt)
http://www.networkupstools.org/doc/2.2.0/hid-subdrivers.html

Have you an idea for my problems?


Looking at the VendorID and ProductID, it is likelt that this device  
is recognized as a /dev/tttyUSB(0|1...) device. As such you should  
probably point the blazer_ser or megatec drivers to this port.


Best regards, Arjen
--
Please keep list traffic on the list (off-list replies will be rejected)


___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser