[Nut-upsuser] Nut with Powercom iCute ICT-530U (USB)

[Peter Selinger]

I don't know if it would be possible to write a driver for your UPS. 
There is currently a project for getting a serial-over-usb megatec
protocol to work. 

If you send the output of 

newhidups -DD -u root -x explore -x vendorid=0d9f auto

, I might be able to tell you whether it resembles other devices that
we have seen. -- Peter

=?windows-1252?Q?Dominik_Gora=3Bczkowski?= wrote:
> 
> Yup, this is a bad news, as I get this horrible message:
> Network UPS Tools - UPS driver controller 2.0.5
> Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5)=
> 
> 
> No matching HID UPS found
> Driver failed to start (exit status=3D1)
> 
> Is there a chance, that the serial-over-usb Powercom UPS will be=20
> supported in the near future? Or maybe there is a way to mount it as a=20
> serial port and use standard powercom drivers? I am not nearly as good=20
> programmer to write my own driver :|
> 
> Dominik Goraczkowski
> 
> 
> Peter Selinger napisa?(a):
> > The line "Product=3DUSB to Serial" is bad news. It means that your
> > device cannot be supported by newhidups / usbhid-ups (which is a
> > native USB driver).=20
> >
> > I don't think any of our other drivers currently supports Powercom
> > serial-over-usb devices.
> >
> > -- Peter
> >
> > Dominik_Gora;czkowski wrote:
> >  =20
> >> Hello Peter!
> >>
> >> Well, my /proc/usb/devices says:
> >>
> >> T: Bus=3D01 Lev=3D01 Prnt=3D01 Port=3D01 Cnt=3D02 Dev#=3D 3 Spd=3D1.5 =
> MxCh=3D 0
> >> D: Ver=3D 1.00 Cls=3D00(>ifc ) Sub=3D00 Prot=3D00 MxPS=3D 8 #Cfgs=3D 1=
> 
> >> P: Vendor=3D0d9f ProdID=3D0002 Rev=3D 0.00
> >> S: Manufacturer=3DPOWERCOM CO., LTD.
> >> S: Product=3DUSB to Serial
> >> C:* #Ifs=3D 1 Cfg#=3D 1 Atr=3D80 MxPwr=3D100mA
> >> I: If#=3D 0 Alt=3D 0 #EPs=3D 2 Cls=3D03(HID ) Sub=3D00 Prot=3D00 Drive=
> r=3Dhid
> >> E: Ad=3D81(I) Atr=3D03(Int.) MxPS=3D 8 Ivl=3D10ms
> >> E: Ad=3D02(O) Atr=3D03(Int.) MxPS=3D 8 Ivl=3D10ms
> >>
> >> And the manufacturer's UPS monitor (not working though) says:
> >>
> >> Copyright(c) Powercom Co., Ltd., all rights reserved.
> >> UPSMON_USB V0.9 program start!
> >> UPSMON_USB: The UPS USB serial port use (null).
> >> UPSMON_USB: Ac Fail count down is seted 30 seconds.
> >> UPSMON_USB: UPS shutdown delay time is seted 1 minutes and 30 seconds.=
> 
> >> hiddev driver version is 1.0.4
> >> HID: vendor 0xd9f product 0x2 version 0x0 applications [1]: ffa00001
> >> HID: bus: 1 devnum: 3 ifnum: 0
> >> UPS HID device name: "POWERCOM CO., LTD. USB to Serial"
> >>
> >> Is anything of this looking familiar? I haven't got any reply from the=
> =20
> >> manufacturer, so nut is probably my only option of making this UPS=20
> >> working under Linux.
> >> I'll try the new hid driver - from what I red, I need to compile the=20
> >> project with special options to bulid USB drivers and have usbtools=20
> >> installed already on my system, is this correct?
> >>
> >> Dominik Goraczkowski
> >>
> >> P.S. I've tried to set all options to sent this message encoded=20
> >> correctly this time.
> >>
> >> Peter Selinger napisa?(a):
> >>    =20
> >>> Hi Dominik,
> >>>
> >>> no, I don't think I have seen this device before. What is its
> >>> USB manufacturer and product ID (lsusb or usbview should show this, a=
> s
> >>> does the newhidups driver).=20
> >>>
> >>> If it is a HID device, then it should not be very difficult to suppor=
> t
> >>> it in NUT, if it isn't already compatible.=20
> >>>
> >>> Try the newhidups driver (called usbhid-ups in the newest SVN sources=
> ,
> >>> newhidups in the 2.0.5 release). If it doesn't recognize the device
> >>> ("no matching devices found..."), try with -u root. If this doesn't
> >>> work, try the -x explore and -x productid=3DXXXX options and send the=
> 
> >>> resulting debug output.
> >>>
> >>> -- Peter
> >>>
> >>> P.S. could you please set your email program to encode text as plain
> >>> text or quoted printable, rather than base64? I use an ancient mail
> >>> reader and it shows your email like this:
> >>>
> >>> SGkhCgpJcyB0aGVyZSBhbnkgdXNlciBvZiBudXQgaGF2aW5nIHRoaXMgdHlwZSBvZiBVU=
> FM/ICgK
> >>> aHR0cDovL3d3dy5wY211cHMuY29tLnR3L3Byb2R1Y3QvaUN1dGUuaHRtbCkKSXQgd29ya=
> 3Mgbmlj
> >>> ZSB1bmRlciB3aW5kb3dzIGFuZCBhbHNvIGlzIGRldGVjdGVkIHVuZGVyIExpbnV4IGFuZ=
> CBpbnN0
> >>> etc.
> >>>
> >>>  =20
> >>>      =20
> >>>> Hi!
> >>>>
> >>>> Is there any user of nut having this type of UPS? (
> >>>> http://www.pcmups.com.tw/product/iCute.html)
> >>>> It works nice under windows and also is detected under Linux and ins=
> talled
> >>>> as USB HID device. There is problem however, as the software provide=
> d by its
> >>>> manufacturer (http://www.pcmups.com.tw/download/Download/UPSMON_USBV=
> 091.zip)
> >>>> doesn't seem to comunicate with the UPS at all. It shows messages su=
> gesting
> >>>> that the UPS is connected and detected, but there is no action when =
> AC is
> >>>> disconnected. The hardware is working fine, as the windows version o=
> f their
> >>>> UPS monitor instantly shows power surges and turns off the PC. I've =
> sent
> >>>> mail to the manufacturer but received no reply so far.
> >>>> So, will nut work with this type of ups? In the compatibility list (=
> 
> >>>> http://www.networkupstools.org/compat/stable.html) there is enigmati=
> c
> >>>> statement "various" in the Powercom section. Shall I have hope and d=
> ownload
> >>>> the package or just lie down and cry? ;)
> >>>>
> >>>> Dominik Gor=B1czkowski
> >>>>        =20
> >
> >  =20
> 
>