search for: iserialnumber

iSerialNumber does not need to be unique per device - it is not very many bits wide. I?m pretty sure I don?t *need* iSerialNumber?I mean, I could just remove it from the report descriptor altogether. But since it is available to give, and we are writing each board?s serial number into flash as part of the micr...

We're wrapping up our first version of the UPS we're making, and so I'm going over the USB code and came across one loose end. The serial number of the unit (iSerialNumber according to the USB HID doc) is a constant, but it's of course a different constant for each UPS. Right now we store that value in the Flash on the device, but the only way I've seen to pass the serial number over USB is to encode it as a constant in the code and then reference it as a US...

On Aug 31, 2015, at 9:01 AM, Rob Groner <rgroner at RTD.com> wrote: > > iSerialNumber does not need to be unique per device - it is not very many bits wide. > > I?m pretty sure I don?t *need* iSerialNumber?I mean, I could just remove it from the report descriptor altogether. But since it is available to give, and we are writing each board?s serial number into flash as part...

...ceClass = 0x0000 <Probed by interface class> bDeviceSubClass = 0x0000 bDeviceProtocol = 0x0000 bMaxPacketSize0 = 0x0008 idVendor = 0x09ae idProduct = 0x0001 bcdDevice = 0x0001 iManufacturer = 0x0001 <TRIPP LITE> iProduct = 0x0002 <TRIPP LITE SMART1500RMXL2Ua > iSerialNumber = 0x0000 <no string> bNumConfigurations = 0x0001 I swapped over to the tripplite_usb and it's still doing the same thing. # /etc/rc.d/devd restart Stopping devd. Starting devd. # upsdrvctl start Network UPS Tools - UPS driver controller 2.7.4 Network UPS Tools - Tripp Lite OMNIVS /...

Hello everyone, I have a Tripp-Lite UPS (smart1500rmxl2ua) I'm trying to get working with nut. This is a FreeBSD 10.3 box. I've tried using the usbhid-ups<http://networkupstools.org/docs/man/usbhid-ups.html> driver but everytime I try to start up nut, I get this: # upsdrvctl start Network UPS Tools - UPS driver controller 2.7.4 Network UPS Tools - Generic HID driver 0.41 (2.7.4)

On Aug 28, 2015, at 2:21 PM, Rob Groner <rgroner at RTD.com> wrote: > > We?re wrapping up our first version of the UPS we?re making, and so I?m going over the USB code and came across one loose end. The serial number of the unit (iSerialNumber according to the USB HID doc) is a constant, but it?s of course a different constant for each UPS. iSerialNumber does not need to be unique per device - it is not very many bits wide. > Right now we store that value in the Flash on the device, but the only way I?ve seen to pass the serial nu...

...53600 [D1] nut_libusb_open get iManufacturer failed, retrying... 0.374780 [D1] nut_libusb_open get iProduct failed, retrying... 0.395962 [D1] nut_libusb_open get iProduct failed, retrying... 0.417222 [D1] nut_libusb_open get iProduct failed, retrying... 0.438631 [D1] nut_libusb_open get iSerialNumber failed, retrying... 0.460000 [D1] nut_libusb_open get iSerialNumber failed, retrying... 0.481267 [D1] nut_libusb_open get iSerialNumber failed, retrying... 0.481286 [D2] - VendorID: 0463 0.481291 [D2] - ProductID: ffff 0.481296 [D2] - Manufacturer: unknown 0.481301 [D2] - Product:...

...53600 [D1] nut_libusb_open get iManufacturer failed, retrying... 0.374780 [D1] nut_libusb_open get iProduct failed, retrying... 0.395962 [D1] nut_libusb_open get iProduct failed, retrying... 0.417222 [D1] nut_libusb_open get iProduct failed, retrying... 0.438631 [D1] nut_libusb_open get iSerialNumber failed, retrying... 0.460000 [D1] nut_libusb_open get iSerialNumber failed, retrying... 0.481267 [D1] nut_libusb_open get iSerialNumber failed, retrying... 0.481286 [D2] - VendorID: 0463 0.481291 [D2] - ProductID: ffff 0.481296 [D2] - Manufacturer: unknown 0.481301 [D2] - Product:...

...mmary.imanufacturer", 0, 0, > "UPS.PowerSummary.iManufacturer", NULL, "%.0f", 0, NULL }, > { "unmapped.ups.powersummary.iproduct", 0, 0, > "UPS.PowerSummary.iProduct", NULL, "%.0f", 0, NULL }, > { "unmapped.ups.powersummary.iserialnumber", 0, 0, > "UPS.PowerSummary.iSerialNumber", NULL, "%.0f", 0, NULL }, This part looks promising - the UPS appears to implement a portion of the HID Power Device Class specification, rather than just being a HID-enabled USB-to-serial adapter. In the generated code, the c...

Hi, I have an UPS with only the marking D1000 on it and it came with Junda-Tech's UpsMate. Its USB id is 3344:0025, which is apparently a microprocessor. I've could get some of the HID interactions as described on the website, but there are some outstanding. Junda-Tech does not respond to any queries. Does anybody else have the same or a similar UPS with more information? What is the

...ceClass = 0x0000 <Probed by interface class> bDeviceSubClass = 0x0000 bDeviceProtocol = 0x0000 bMaxPacketSize0 = 0x0008 idVendor = 0x09ae idProduct = 0x0001 bcdDevice = 0x0001 iManufacturer = 0x0001 <TRIPP LITE> iProduct = 0x0002 <TRIPP LITE SMART1500RMXL2Ua > iSerialNumber = 0x0000 <no string> bNumConfigurations = 0x0001 I swapped over to the tripplite_usb and it's still doing the same thing. # /etc/rc.d/devd restart Stopping devd. Starting devd. # upsdrvctl start Network UPS Tools - UPS driver controller 2.7.4 Network UPS Tools - Tripp Lite OMNIVS /...

...rType = 0x0001 bcdUSB = 0x0110 bDeviceClass = 0x0000 bDeviceSubClass = 0x0000 bDeviceProtocol = 0x0000 bMaxPacketSize0 = 0x0008 idVendor = 0x0463 idProduct = 0xffff bcdDevice = 0x0001 iManufacturer = 0x0001 <MGE UPS SYSTEMS> iProduct = 0x0002 <Evolution> iSerialNumber = 0x0000 <no string> bNumConfigurations = 0x0001 Feel free to chop off the last few digits of the string after iSerialNumber, if it returns something unique. If idProduct is 0001 (not likely these days), you need tripplite_usb, otherwise usbhid-ups is the correct driver. The other prer...

...ceProtocol: 0x00 bMaxPacketSize0: 0x08 idVendor: 0x0463 idProduct: 0xffff bcdDevice: 0x0100 iManufacturer: 0x01 iProduct: 0x02 iSerialNumber: 0x03 bNumConfigurations: 0x01 0.423251 entering shut_get_descriptor(n 22, 1538) 0.525087 shut_wait_ack(): ACK received 9.705471 Unable to get Report Descriptor It there a possibility to be an issue of the UPS, or the connection between the serial port of th...

...B = 0x0110 bDeviceClass = 0x0000 <Probed by interface class> bDeviceSubClass = 0x0000 bDeviceProtocol = 0x0000 bMaxPacketSize0 = 0x0008 idVendor = 0x0001 idProduct = 0x0000 bcdDevice = 0x0100 iManufacturer = 0x0001 <MEC> iProduct = 0x0002 <MEC0003> iSerialNumber = 0x0000 <no string> ---------------------------------------------------------------------------- ------------------------ /usr/local/libexec/nut/blazer_usb -DD -a ups 2>&1 | tee -a /usr/local/ups.txt 0.886031 Checking device (0001/0000) (/dev/usb//dev/ugen0.4) 0.927...

...eSubClass: 0x00 > bDeviceProtocol: 0x00 > bMaxPacketSize0: 0x08 > idVendor: 0x0463 > idProduct: 0xffff > bcdDevice: 0x0100 > iManufacturer: 0x01 > iProduct: 0x02 > iSerialNumber: 0x03 > bNumConfigurations: 0x01 > > entering shut_get_descriptor(n 22, 1811) > shut_wait_ack(): ACK received > Unable to get Report Descriptor If I put more "D", I see it stucks on "need more data!" like this : > need more data (1691)! > Receiv...

...                     string, sizeof(string));                  if (ret > 0) {                      curDevice->Product = strdup(string); @@ -224,7 +326,7 @@ static int libusb_open(usb_dev_handle **udevp, USBDevice_t *curDevice, USBDevice              }              if (dev->descriptor.iSerialNumber) { -                ret = usb_get_string_simple(udev, dev->descriptor.iSerialNumber, +                ret = nut_usb_get_string(udev, dev->descriptor.iSerialNumber,                      string, sizeof(string));                  if (ret > 0) {                      curDevice->Serial =...

...lass: 0x00 > bDeviceSubClass: 0x00 > bDeviceProtocol: 0x00 > bMaxPacketSize0: 0x08 > idVendor: 0x0463 > idProduct: 0xffff > bcdDevice: 0x0100 > iManufacturer: 0x01 > iProduct: 0x02 > iSerialNumber: 0x03 > bNumConfigurations: 0x01 > > 0.423251 entering shut_get_descriptor(n 22, 1538) > 0.525087 shut_wait_ack(): ACK received > 9.705471 Unable to get Report Descriptor > > > It there a possibility to be an issue of the...

...Note that after the places marked ###, the parser shifts all Usages by one, which mangles the tree. This bug is fixed in nut-cvs-patch-PARSER-2005-08-24. ---------------------------------------------------------------------- Before fixing the HIDParser bug: HIDDumpTree... Path: UPS.PowerSummary.iSerialNumber Path: UPS.PowerSummary.iDeviceChemistry Path: UPS.PowerSummary.iOEMInformation Path: UPS.PowerSummary.Rechargeable Path: UPS.PowerSummary.APCStatusFlag Path: UPS.PowerSummary.APCStatusFlag Path: UPS.PowerSummary.ManufacturerDate Path: UPS.PowerSummary.ConfigVoltage Path: UPS.PowerSummary.Voltage Pa...

...erial Number: QB0518132135 HID descriptor retrieved (Reportlen = 872) Report descriptor retrieved (Reportlen = 872) found 1 (872) Network UPS Tools: New USB/HID UPS driver 0.23 (2.0.2) Report Descriptor size = 872 Detected an UPS: APC/Back-UPS ES 650 FW:818.w1.D USB FW:w1 Path: UPS.PowerSummary.iSerialNumber Path: UPS.PowerSummary.iDeviceChemistry Path: UPS.PowerSummary.iOEMInformation Path: UPS.PowerSummary.Rechargeable Path: UPS.PowerSummary.APCStatusFlag Path: UPS.PowerSummary.APCStatusFlag Path: UPS.PowerSummary.ManufacturerDate Path: UPS.PowerSummary.ConfigVoltage Path: UPS.PowerSummary.Voltage Pa...

...(872) Network UPS Tools: New USB/HID UPS driver 0.23 (2.0.2) Report Descriptor size = 872 Report Descriptor: (200 bytes) => 05 84 09 04 A1 01 09 24 A1 00 85 01 09 FE 79 01 Detected an UPS: APC/Back-UPS ES 650 FW:818.w1.D USB FW:w1 ............. output heavily reduced! Path: UPS.PowerSummary.iSerialNumber Path: UPS.PowerSummary.iDeviceChemistry Path: UPS.PowerSummary.iOEMInformation Path: UPS.PowerSummary.Rechargeable Path: UPS.PowerSummary.APCStatusFlag Path: UPS.PowerSummary.APCStatusFlag Path: UPS.PowerSummary.ManufacturerDate Path: UPS.PowerSummary.ConfigVoltage Path: UPS.PowerSummary.Voltage Pa...