search for: phoenixtec

Hi! all. I have been reading every mail and news about nut and 06da:0002 Phoenixtec but not found a solution. I have a very nice working ups from: CENER ref: "Active 1000VA 230V 12 CENER" and front logo "LA 900" It has COM3 and USB plugs, I don't know if it needs a standar RS232 I have test with varius drivers in ups.conf [MyUPS] driver = bcmxcp_usb | u...

On Dec 3, 2014, at 2:02 PM, janc at telefonica.net wrote: > USB error: error sending control message: Invalid or incomplete > multibyte or wide character This is a wild guess, but what about using the option "langid_fix=0x0409"? -- Charles Lepple clepple at gmail

On Dec 1, 2014, at 3:00 AM, janc at telefonica.net wrote: > I have a very nice working ups from: > CENER ref: "Active 1000VA 230V 12 CENER" and front logo "LA 900" Do you know what software was originally recommended for the UPS? Unfortunately, Phoenixtec seems to have made a lot of different USB-to-serial adapters. The most likely driver is blazer_usb (or nutdrv_qx, which is newer). You may need to shut down the UPS completely (turn power off, and unplug) if the other drivers have sent commands that put the UPS into a bad state. -- Charles Leppl...

On Dec 4, 2014, at 7:01 AM, janc at telefonica.net wrote: > I have got this output with driver usbhid-ups > > ups.conf > > [Phoenixtec] > driver = usbhid-ups > vendorid = 06da > productid = 0002 > port = auto > #~ langid_fix=0x0409 Oh, sorry - I meant for you to try that with blazer_usb. -- Charles Lepple clepple at gmail

Roman, I don't think I already asked, but could you post the output of lsusb -v -d 06da:0003 Just to be sure that we're not exceeding some buffer limitations of the device. Best regards, Arjen -- Please keep list traffic on the list

2015-06-08 13:09 GMT+02:00 Bastien Nocera <hadess at hadess.net>: > On Mon, 2015-06-08 at 10:13 +0200, Arnaud Quette wrote: > > -ATTRS{idVendor}=="06da", ENV{UPOWER_VENDOR}="Liebert" > > > > +ATTRS{idVendor}=="06da", ENV{UPOWER_VENDOR}="Phoenixtec Power Co., Ltd" > > I'm guessing this would require changes in NUT, so I should mention I > don't like that change. Maybe: > +ATTRS{idVendor}=="06da", ENV{UPOWER_VENDOR}="Phoenixtec Power" > would be better? The names are supposed to be human readable...

Hi Charles. I have got this output with driver usbhid-ups ups.conf [Phoenixtec] driver = usbhid-ups vendorid = 06da productid = 0002 port = auto #~ langid_fix=0x0409 desc = "CENER ONLINE 1000VA" # export USB_DEBUG=5 # ./usbhid-ups -a Phoenixtec Network UPS Tools - Generic HID driver 0.37 (2.6.4) USB communication driver 0.32 0.000000 debug level is '3' 0...

...R_LA900_usb Network UPS Tools - Generic HID driver 0.37 (2.6.4) USB communication driver 0.32 0.000000 debug level is '4' 0.000563 upsdrv_initups... 0.299203 Checking device (06DA/0002) (008/003) 0.327122 - VendorID: 06da 0.327217 - ProductID: 0002 0.327261 - Manufacturer: Phoenixtec Power 0.327285 - Product: USB Cable (V2.00) 0.327314 - Serial Number: unknown 0.327341 - Bus: 008 0.327361 Trying to match device 0.327414 Device matches 0.335127 HID descriptor, method 1: (9 bytes) => 09 21 00 01 21 01 22 51 00 0.335240 i=0, extra[i]=09, extra[i+1]=21 0.335...

Hello again. Back in the day (2007) I wrote a USB-capable driver for my Masterguard/Phoenixtec UPSes (in case you locally archived this list, this very mail is a reply to a rather long thread from then), which I used ever since. However, the world has been going on since then and I need to get away with the old 2.0.4 binaries currently in use. These boxes (I use two A3000-19 and two A700-19)...

On Dec 11, 2014, at 5:43 AM, janc at telefonica.net wrote: > 0.339329 Entering libusb_get_report > 0.342986 Report[get]: (2 bytes) => 01 00 > 0.343085 Path: 008c0001.008c0003, Type: Feature, ReportID: 0x01, Offset: 0, Size: 8, Value: 0 > 0.343120 Entering libusb_get_report > 0.346953 Report[get]: (2 bytes) => 02 00 > 0.346993 Path: 008c0001.008c0002,

On Dec 4, 2014, at 7:01 AM, janc at telefonica.net wrote: > 0.339848 Report[get]: (2 bytes) => 01 00 > 0.339928 Path: 008c0001.008c0003, Type: Feature, ReportID: 0x01, Offset: 0, Size: 8, Value: 0 > 0.343852 Report[get]: (2 bytes) => 02 00 > 0.343931 Path: 008c0001.008c0002, Type: Input, ReportID: 0x02, Offset: 0, Size: 1, Value: 0 > 0.343975 Report[buf]: (2 bytes) => 02

Hello. I've been experimenting with the USB connection of an Ippon BackComfoPro 800. This is the device "06da:0003 Phoenixtec Power Co., Ltd". The current SVN version of NUT does not work with this device. The megatec_usb driver can't get a proper reply to a Q1 request, failing with an error message about "short read (14 bytes)" instead. I have found the reason for this. The function run_query in megat...

Citeren Roman Mamedov <roman at rm.pp.ru>: >> Another useful thing would be to run the bundled driver on a Windows >> box while running 'usbsnoop' so that we can get an idea what it is >> doing. Maybe we're missing something here. I still would like to see that. > Keep in mind that the patched megatec_usb driver (which I use since > yesterday) can

...R_LA900_usb Network UPS Tools - Generic HID driver 0.37 (2.6.4) USB communication driver 0.32 0.000000 debug level is '4' 0.000676 upsdrv_initups... 0.288980 Checking device (06DA/0002) (008/004) 0.316956 - VendorID: 06da 0.317057 - ProductID: 0002 0.317087 - Manufacturer: Phoenixtec Power 0.317113 - Product: USB Cable (V2.00) 0.317142 - Serial Number: unknown 0.317168 - Bus: 008 0.317189 Trying to match device 0.317243 Device matches 0.324987 HID descriptor, method 1: (9 bytes) => 09 21 00 01 21 01 22 51 00 0.325083 i=0, extra[i]=09, extra[i+1]=21 0.325...

Has anyone gotten the newhidups driver to work w/ the Powerware 9120 series? Here's what I get for debug info (It's the Phoenixtec device): $ sudo lsusb Bus 002 Device 002: ID 0846:1040 NetGear, Inc. Bus 002 Device 001: ID 0000:0000 Bus 001 Device 002: ID 06da:0002 Phoenixtec Power Co., Ltd Bus 001 Device 001: ID 0000:0000 $sudo /lib/nut/newhidups -DDDDD auto Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.3) debug lev...

Hello: I have a UPS model MXE II MAXIM brand online, 3500VA 2100W. Connects to the PC by a USB 2.0 port. I wanted to use nut, but this brand is not on the list of nut drivers. lsusb returns: ... Bus 003 Device 003: ID 06DA: 0201 Phoenixtec Power Co., Ltd ... I did not find this manufacturer in the driver list. Anyone know if you can have compatibility with other make and model of UPS. With what driver it could start testing? Greetings and thanks, Walter (original Spanish text translated by Google)

Salut Bastien 2015-06-04 13:04 GMT+02:00 Bastien Nocera <hadess at hadess.net>: > On Sat, 2015-05-30 at 18:51 +0200, Arnaud Quette wrote: > > > > > > 2015-05-29 14:09 GMT+02:00 Bastien Nocera <hadess at hadess.net>: > > > On Fri, 2015-05-29 at 13:59 +0200, Arnaud Quette wrote: > > > > Hi Richard and the list, > > > > > >

...g site I can not get nut to work with my UPS. http://bernaerts.dyndns.org/linux/75-debian/335-debian-wheezy-install-monitor-eaton-ups Hope that you can find out what is wrong by the provided info in the email Best Regards, Magnus Karlsson # lsusb -s 001:005 -v Bus 001 Device 005: ID 06da:0002 Phoenixtec Power Co., Ltd UPS Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x06da Phoenixt...

...d): COMMAND: 31 RECONNECT USB DEVICE Communications with UPS lost: Error executing command Could not communicate with the ups: Inappropriate ioctl for device CLOSING Driver failed to start (exit status=1) co-nh5:/tmp/mnt/projects/pwusb/nut-2.4.1# lsusb -s 2:4 -v Bus 002 Device 004: ID 06da:0002 Phoenixtec Power Co., Ltd Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x06da Phoenixtec P...

...T+02:00 Bastien Nocera <hadess at hadess.net>: > > On Mon, 2015-06-08 at 10:13 +0200, Arnaud Quette wrote: > > > -ATTRS{idVendor}=="06da", ENV{UPOWER_VENDOR}="Liebert" > > > > > > +ATTRS{idVendor}=="06da", ENV{UPOWER_VENDOR}="Phoenixtec Power > > Co., Ltd" > > > > I'm guessing this would require changes in NUT, so I should mention > > I > > don't like that change. Maybe: > > +ATTRS{idVendor}=="06da", ENV{UPOWER_VENDOR}="Phoenixtec Power" > > would be bet...