search for: mec0002

Hello, Has anyone written a driver for this device. Looking at the postings existing for the MEC0002 usb device it would appear that UPS presents its self as HID but may actually be a non standard serial protocol over the usb port. dude

...of the standard numbers.) If this device can be made to return valid data, some additional coding would be needed to map these to the proper pages. > 0.452728 Report[get]: (16 bytes) => 10 03 4d 00 45 00 43 00 30 00 30 00 30 00 32 00 Similar to before, this is a string descriptor ("MEC0002") > 0.623733 Report[get]: (9 bytes) => 16 03 55 00 50 00 53 00 20 Also returned a fragment of a string descriptor ("UPS "). It is possible that the blazer_usb driver initialization has put the UPS into a bad state. If you can schedule some downtime, you might want to try u...

On Sep 8, 2016, at 4:26 AM, Vassilis Virvilis <vasvir at iit.demokritos.gr> wrote: > > The 1000 (bcdUSB 1.00) works with blazer_usb while the 1500 (bcdUSB 1.10) > doesn't. > From the lsusb descriptor output, the 1500 seems to implement the HID Power Device Class (PDC) spec - so it might be possible to adapt usbhid-ups to work with it. What happens if you run the driver in

On Sep 8, 2016, at 9:25 AM, Vassilis Virvilis <vasvir at iit.demokritos.gr> wrote: > > + failed to claim USB device: could not claim interface 0: Device or > resource busy > + detached kernel driver from USB device... > nut_usb_set_altinterface: skipped usb_set_altinterface(udev, 0) > HID descriptor, method 1: (9 bytes) => 09 21 00 01 00 01 22 70 02 > > ****

On Sep 8, 2016, at 10:05 AM, Vassilis Virvilis <vasvir at iit.demokritos.gr> wrote: > Now that's a problem. I am not sure that I can find > > 1) the original software > 2) a (physical) windows machine in the vicinity of the UPS > > I will give it a try but for now looks like a dead end. I have 3 of these > UPS. Two of them have dead batteries and since they take 4

Hi again, > On Sep 8, 2016, at 10:05 AM, Vassilis Virvilis <vasvir at iit.demokritos.gr> > wrote: >> Now that's a problem. I am not sure that I can find >> >> 1) the original software >> 2) a (physical) windows machine in the vicinity of the UPS >> Ha! I jumped several hooks but I think I got it. 01. I contacted the store that sold us the UPS and

Hi again Looks like the ups always replies 22 = 16035500 50005300 20004e00 6f002000 41006300 6b00 The software sends 1) The first time 80 06 0303 4095 0064 100 < 2) The second time with 80 06 030c 4095 0064 100 < 3) The third time with 80 06 030d 4095 0064 100 < 4) repeats step 1) 8 times 5) go to step 2) Regards Vassilis Virvilis

On Sep 16, 2016, at 9:38 AM, Vassilis Virvilis wrote: > > A little deciphering > >> Looks like the ups always replies >> 22 = 16035500 50005300 20004e00 6f002000 41006300 6b00 > > That is > length = 0x16 = 22 > type = 0x3 = string > Message = "UPS No Ack" > > Very fun... that string shows up here, among other places:

A little deciphering > Looks like the ups always replies > 22 = 16035500 50005300 20004e00 6f002000 41006300 6b00 That is length = 0x16 = 22 type = 0x3 = string Message = "UPS No Ack" Very fun... Regards Vassilis Virvilis

> You could also try adding "-x usb_set_altinterface" to the command line > (or adding it to ups.conf). The lsusb output implies that the only valid > setting is 0 (bAlternateSetting), but it might need to be set explicitly. I checked with -x usb_set_altinterface and it says nut_usb_set_altinterface: usb_set_altinterface() should not be necessary - please email the

> that string shows up here, among other places: > > https://github.com/networkupstools/nut/blob/master/drivers/nutdrv_qx.c#L764 > > but if the upsilon screen isn't showing many values, I'm not sure if that > version is going to help. Are there any other settings to select a > different model or protocol? Here is the output of #/etc/upsilon/upsilon config hope

...############# dmesg output when connecting the ups usb 2-1: new low speed USB device using uhci_hcd and address 2 PM: Adding info for usb:2-1 PM: Adding info for No Bus:usbdev2.2_ep00 usb 2-1: configuration #1 chosen from 1 choice PM: Adding info for usb:2-1:1.0 hiddev96: USB HID v1.00 Device [MEC MEC0002] on usb-0000:00:10.1-1 PM: Adding info for No Bus:usbdev2.2_ep81 ########################################################### [dave@luggage ~]$ sudo /sbin/newhidups -u root -DDDDD auto Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.3) debug level is '5' Checking device (0001/0000) (00...

..., the UPS have conection with USB to PC and i have problems to configure nut the ups is conected and Linux report this config Aug 19 23:34:56 dakota kernel: [22393.099595] usb 2-2: new low speed USB device using uhci_hcd and address 7 Aug 19 23:35:06 dakota kernel: [22403.186326] usb 2-2: Product: MEC0002 Aug 19 23:35:06 dakota kernel: [22403.186333] usb 2-2: Manufacturer: MEC Aug 19 23:35:06 dakota kernel: [22403.291219] hiddev96: USB HID v1.00 Device [MEC MEC0002] on usb-0000:00:1d.0-2 I assume the /dev/usb/hiddev96 for the UPS, is ok? i am configured the NUT with this mini How-TO http://fedoranew...

...- Serial Number: unknown - - Bus: 008 + - Bus: 006 - Device release number: 0202 Trying to match device Device does not match - skipping - Checking device (0001/0000) (008/002) + Checking device (0001/0000) (006/002) - VendorID: 0001 - ProductID: 0000 - Manufacturer: MEC - Product: MEC0002 - Serial Number: unknown - - Bus: 008 + - Bus: 006 - Device release number: 0100 Trying to match device Device matches + failed to claim USB device: could not claim interface 0: Device or resource busy + detached kernel driver from USB device... nut_usb_set_altinterface: skipped usb_set_a...

...84 - Bus: 008 0.333686 - Device release number: 0202 0.333689 Trying to match device 0.333710 Device does not match - skipping 0.333721 Checking device (0001/0000) (008/002) 0.356723 - VendorID: 0001 0.356734 - ProductID: 0000 0.356737 - Manufacturer: MEC 0.356740 - Product: MEC0002 0.356743 - Serial Number: unknown 0.356745 - Bus: 008 0.356748 - Device release number: 0100 0.356751 Trying to match device 0.356781 Device matches 0.356811 nut_usb_set_altinterface: skipped usb_set_altinterface(udev, 0) 0.361726 HID descriptor, method 1: (9 bytes) => 09 21...

...vel I can see that the driver reports a "USB no ACK" to these instcmds. Checking the USB with wireshark shows that this text string originated in the UPS, ie it is a text string returned in response to the instcmds. Looking closer at the USB descriptor it presents MEC0003 rather than the MEC0002 that I see all over the fora. So it would appear that there is a new variety of MEC protocol. Has anyone else seen this? Is there any work ongoing with this MEC0003 protocol? What can I do to help this cause? (bear in mind I'm a Linux newbie - but with good backup :) ) Le meas, John PROPRI...

...ith this. Details: dmesg [ 13.690421] usb 4-4: New USB device found, idVendor=0001, idProduct=0000 #This is clearly bogus, and is what was reported in the 2006 thread [ 13.690667] usb 4-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 13.690909] usb 4-4: Product: MEC0002 [ 13.691164] usb 4-4: Manufacturer: MEC [ 13.722779] generic-usb 0003:0001:0000.0003: hiddev97,hidraw2: USB HID v1.00 Device [MEC MEC0002] on usb-0000:00:06.0-4/input0 lsusb -vv # not much more info than dmesg, and it fails to discover the manufacturer! Bus 004 Device 002: ID 0001:0000 Fry&...

Hi, I have two ups (Turbo-X 1000SD, Turbo-X 1500SD). The both report themselves as # lsusb Bus 008 Device 002: ID 0001:0000 Fry's Electronics The are produced by MEC and report MEC0002 as product (although the working one report it in dmesg but not in lsusb) The 1000 (bcdUSB 1.00) works with blazer_usb while the 1500 (bcdUSB 1.10) doesn't. I am attaching lsusb and blazer_urb output for the problematic (1500) one. Any ideas on how to debug this further? Anything else to pos...