[Nut-upsuser] blazer_ser problem on windows NUT 2.6.5-3780M

[David Bezuidenhout]

I tried it on different USB ports, both USB2 and USB3 ports, on Windows it
refuses to work unless I add at least 4 D flags to the driver on the
command line.



On Sat, May 11, 2013 at 9:05 PM, Kris Jordan
<nut.kj at sagebrushnetworks.com>wrote:

> David Bezuidenhout wrote, On 5/11/2013 10:26 AM:
>
>  Hi,
>>
>> I have a bunch of UPSs, most connected to pcs with Linux working 100%
>> with NUT.
>> The only one I have a problem with, is connected to Windows 7 64bit, and
>> I used the straight MSI installed from the website named
>> NUT-Installer-2.6.5-4.msi
>>
>> Took me a while to find a way to get it to work, but it is ugly for now.
>> Just starting up the service results in a NUT not working at all, and I
>> tracked it down to the blazer_ser driver not finding the UPS. Debugging
>> shows some problem with the communication on my serial-usb port. What I
>> have found is, that it doesn't work until I add 4x debug flags. eg: -DDDD
>>
>
> I had a similar issue with usbhid-ups on a USB 3.0 port until I moved it
> to a USB 2.0 port. Maybe it's timing related, I'd expect adding debugging
> would slow it down a tad.
>
> ______________________________**_________________
> Nut-upsuser mailing list
> Nut-upsuser at lists.alioth.**debian.org<Nut-upsuser at lists.alioth.debian.org>
> http://lists.alioth.debian.**org/cgi-bin/mailman/listinfo/**nut-upsuser<http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20130516/e864e312/attachment-0001.html>