Vassilis Virvilis
2016-Sep-08 14:05 UTC
[Nut-upsuser] blazer_usb MEC0002 problem Fry's Electronics (Turbo-X) [HID PDC?]
> 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 nut-upsdev list with information about your UPS no other difference from the previous runs> > It might be useful to check and see if the vendor's suggested software > actually works with this UPS, and if so, record some of the messages it > sends.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 batteries each it makes it harder to justify their repair. If I find the software and a windows machine what software should I use to sniff the usb traffic? Thanks for your help so far. It was really insightful and educational. Regards Vassilis Virvilis
Charles Lepple
2016-Sep-09 02:54 UTC
[Nut-upsuser] blazer_usb MEC0002 problem Fry's Electronics (Turbo-X) [HID PDC?]
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 batteries each > it makes it harder to justify their repair. > > If I find the software and a windows machine what software should I use to > sniff the usb traffic?Most of my information on this is old, but there might be some other still-relevant suggestions in the FAQ or the mailing list. Linux has decent USB tracing support that can probably be used with virtual guest machines.> Thanks for your help so far. It was really insightful and educational.You're welcome! Wish we had a solution, but keep us posted if you find the software.
Vassilis Virvilis
2016-Sep-15 14:04 UTC
[Nut-upsuser] blazer_usb MEC0002 problem Fry's Electronics (Turbo-X) [HID PDC?]
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 they were kind enough to give me a copy of the software 02. It is Upsilon2000. Turns out it has support for linux 03. It has 3 candidates for linux, linux-upsilon.tar.gz, centos-upsilon.tar.gz, linux.Z 04. Uncompress & diff & manual installations & tests 05. linux.Z does not have usb support 06. centos is upsilon 2.1.x 08. linux-upsilon is uspilon 3.0 - ok let's go with that 09. Setup usbmon 10. configure upsilon to use usb instead /dev/ttyS1. Not trivial. No documentation, I had to use ltrace to see that it strcmp the device name from the config file with "hid". So "hid" is the USB hurray 11. Collect the usbmon log. Please find it attached. Keep in mind that I broke the circuit with a power switch so the UPS at some point went on battery. Then I turned it back on. The $upsilon status command showed a text screen with most of the info unavailable. So I can't tell if it is really working. Hope that help you decipher this UPS Thank you for your support so far Regards Vassilis Virvilis -------------- next part -------------- A non-text attachment was scrubbed... Name: ups-turbo-x-1500sd.log.gz Type: application/gzip Size: 5818 bytes Desc: not available URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20160915/e4a11a98/attachment.bin>
Possibly Parallel Threads
- blazer_usb MEC0002 problem Fry's Electronics (Turbo-X) [HID PDC?]
- blazer_usb MEC0002 problem Fry's Electronics (Turbo-X) [HID PDC?]
- blazer_usb MEC0002 problem Fry's Electronics (Turbo-X) [HID PDC?]
- blazer_usb MEC0002 problem Fry's Electronics (Turbo-X) [HID PDC?]
- blazer_usb MEC0002 problem Fry's Electronics (Turbo-X) [HID PDC?]