search for: mec0003

...it with higher debug level 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 :) )...

...------------------------------ From: <hyouko at gmail.com> Sent: Tuesday, July 08, 2014 12:16 AM To: "Hill" <hill at fermot.com.pl> Cc: "Charles Lepple" <clepple at gmail.com>; <nut-upsuser at lists.alioth.debian.org> Subject: Re: [Nut-upsuser] Lupus 500 MEC0003 Problems >> Everything looks fine apart from ups.beeper.status always shows enabled >> even if the status bit fom the ups has changed state. > > Probably because the driver updates the beeper status only every > 'pollfreq' (default 30) seconds, so it may have missed t...

...otocol USB driver 0.12 (2.7.4) No supported devices found. detail below. Another info : This driver "blazer_usb" and this UPS have no problem on a raspberry pi3. With the same configuration!! What I can do?? Thanks in advance DL usbconfig dump_devices_des ugen0.4: <MEC MEC0003> at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON (100mA) bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0110 bDeviceClass = 0x0000 <Probed by interface class> bDeviceSubClass = 0x0000 bDeviceProtocol = 0x0000 bMaxPacketSize0 = 0x0008 idVendor = 0x0001 id...

...output of upsc, and note if any of those values look wrong? > Some of the more pertinent info from the status: > > productid 0000 > vendorid 0001 > firmware VER40141F1 > > and from lsusb > > idvendor 0x0001 Fry's Electronics > iManufacturer MEC > iProduct MEC0003 > > The driver is using the Megatec protocol with the Krauler subdriver Were the blazer and/or nutusb_qx drivers able to match the Krauler subdriver automatically, or did you have to specify it manually in ups.conf? > So I connected the USB to my Windows machine and using Upsilon2000...

...ing the blazer_usb driver and running NUT 2.6.5. But unfortunately none of the Instcmds such as load.off etc. worked. Some of the more pertinent info from the status: productid 0000 vendorid 0001 firmware VER40141F1 and from lsusb idvendor 0x0001 Fry's Electronics iManufacturer MEC iProduct MEC0003 The driver is using the Megatec protocol with the Krauler subdriver So I connected the USB to my Windows machine and using Upsilon2000 it was possible to shutdown the UPS. I then installed NUT 2.7.1 and tried the nutusb_qx driver to see if this improved matters, unfortunately it didn't help....

> Everything looks fine apart from ups.beeper.status always shows enabled > even if the status bit fom the ups has changed state. Probably because the driver updates the beeper status only every 'pollfreq' (default 30) seconds, so it may have missed the change. > After more testing the indexes work as follows > > 0x0a = load.on / cancel.shutdown.stayoff /

...-------------------------------- From: <hyouko at gmail.com> Sent: Monday, June 30, 2014 12:42 AM To: "Charles Lepple" <clepple at gmail.com> Cc: "Hill" <hill at fermot.com.pl>; <nut-upsuser at lists.alioth.debian.org> Subject: Re: [Nut-upsuser] Lupus 500 MEC0003 Problems > Sorry for the huge delay and thanks Charles for taking care of this topic. > >>> I'm running OpenSuse 13.1 and I have a Lupus 500 USB (Fideltronik) >>> >>> After quite a bit of playing around I managed to get the status of the >>> UPS using...

Sorry for the huge delay and thanks Charles for taking care of this topic. >> I'm running OpenSuse 13.1 and I have a Lupus 500 USB (Fideltronik) >> >> After quite a bit of playing around I managed to get the status of the UPS using the blazer_usb driver and running NUT 2.6.5. >> But unfortunately none of the Instcmds such as load.off etc. worked. > > Can you post

...0.005913 - Bus: 002 0.005919 Trying to match device 0.005928 Device does not match - skipping 0.005943 Checking device (0001/0000) (008/034) 0.028354 - VendorID: 0001 0.028397 - ProductID: 0000 0.028404 - Manufacturer: MEC 0.028412 - Product: MEC0003 0.028418 - Serial Number: unknown 0.028425 - Bus: 008 0.028432 Trying to match device 0.028484 Device matches 0.031351 Skipping protocol Voltronic 0.01 0.031395 Skipping protocol Voltronic-QS 0.01 0.031487 Skipping protocol Mustek 0.02 0.031510...

...Size0 8 idVendor 0x0001 Fry's Electronics idProduct 0x0000 bcdDevice 1.00 iManufacturer 1 iProduct 2 MEC0003 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 34 bNumInterfaces 1 bConfigurationV...

...UT. Any hints? Thanks... Some info: * lsusb: Bus 005 Device 003: ID 0001:0000 Fry's Electronics * usb-devices: T: Bus=05 Lev=01 Prnt=01 Port=02 Cnt=02 Dev#= 3 Spd=1.5 MxCh= 0 D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0001 ProdID=0000 Rev=01.00 S: Product=MEC0003 C: #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA I: If#= 0 Alt= 0 #EPs= 2 Cls=03(HID ) Sub=00 Prot=00 Driver=(none) * Test using nutdrv_qx -DDDDD in nutdrv_qx.log (attached). * Test using blazer_usb -DDDDD in blazer_usb.log (attached). * Capture of successful communications with the UPS using the appli...

...ommand[i].index, buf, buflen); +                ret = usb_get_string_simple(udev, command[i].index, buf, blen);              }              if (ret <= 0) { @@ -1075,6 +1083,7 @@ static qx_usb_device_id_t    qx_usb_id[] = {      { USB_DEVICE(0x0001, 0x0000),    "MEC",        "MEC0003",     &fabula_subdriver },    /* Fideltronik/MEC LUPUS 500 USB */      { USB_DEVICE(0x0001, 0x0000),    "ATCL FOR UPS",    "ATCL FOR UPS",        &fuji_subdriver },    /* Fuji UPSes */      { USB_DEVICE(0x0001, 0x0000),    NULL,        NULL,     &krauler_su...

...Device type: UPS Bus type: USB WWW: http://fideltronikinigo.com/viper/viper-1200/ " nut-scanner -U" output: [nutdev1] driver = "blazer_usb" port = "auto" vendorid = "0001" productid = "0000" product = "MEC0003" vendor = "MEC" bus = "004" --------------------------------------------------- But "blazer_usb" driver does not work with this device. My working "ups.conf": [Viper1200] driver = "nutdrv_qx" port = &quot...

...utput upon connecting the UPS: [168841.020036] usb 5-2: new low-speed USB device number 8 using uhci_hcd [168841.187222] usb 5-2: New USB device found, idVendor=0001, idProduct=0000 [168841.187231] usb 5-2: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [168841.187236] usb 5-2: Product: MEC0003 [168841.294695] hid-generic 0003:0001:0000.0005: hiddev0,hidraw0: USB HID v1.11 Device [MEC0003] on usb-0000:00:1d.3-2/input0 output of : sudo /lib/nut/blazer_usb -a myups -u nut -DDDD 0.000000 debug level is '4' 0.166331 Checking device (1D6B/0003) (007/001) 0.166618...

...et_string(udev, index, buf, buflen);      if (ret <= 0) {          upsdebugx(3, "read: %s (%d)", ret ? usb_strerror() : "timeout", ret); @@ -1075,6 +1040,7 @@ static qx_usb_device_id_t    qx_usb_id[] = {      { USB_DEVICE(0x0001, 0x0000),    "MEC",        "MEC0003",     &fabula_subdriver },    /* Fideltronik/MEC LUPUS 500 USB */      { USB_DEVICE(0x0001, 0x0000),    "ATCL FOR UPS",    "ATCL FOR UPS",        &fuji_subdriver },    /* Fuji UPSes */      { USB_DEVICE(0x0001, 0x0000),    NULL,        NULL,     &krauler_su...