[Nut-upsuser] MGE Pulsar Extreme communication problems

Arnaud Quette aquette.dev at gmail.com
Fri Jun 16 06:43:12 UTC 2006

2006/6/16, Daniel O'Connor <doconnor at gsoft.com.au>:
> On Friday 16 June 2006 00:21, Arnaud Quette wrote:
> > possible, I'm not sure for the moment.
> > what is sure that the problem comes from the fbsd usb stack or
> > possibly from libusb for bsd...
> Yeah, possible some interaction is the cause. I have used libusb for other
> things though.
> > the problem is here. But I don't know why we get an I/O error...
> > the USB data is fine and the HID report data seems too, so the problem
> > is deeper.
> OK.
> > Another test: while having newhidups running in debug mode, call upsrw
> > to set ups.delay.start to 120, and check if the I/O error has been
> Yes it is the same.
> > reproduced. I don't have much to say for the moment, but after a good
> > night, I might be back with more... You should also contact bsd
> > hackers to see if there is something known, or other ideas.
> Yeah OK, I'll post and see how I go :)

update us if you have some news on that side

> > finally, what are you bsd and libusb versions?
> FreeBSD 6.0 and libusb 0.1.12.

IIRC, there were such systems working
@Thierry and Rob: are you facing such problems on your setup?

> I will try and find time to try RS232 again - I think an IRQ issue was causing
> problems before

FYI, mge-shut in 2.0.3 is a bit buggy (some regressions), that will be
fixed for 2.0.4.

Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://people.debian.org/~aquette/
OpenSource Developer - http://arnaud.quette.free.fr/

More information about the Nut-upsuser mailing list