On Tuesday 20 June 2006 05:45, Thierry Thomas wrote:
> > IIRC, there were such systems working
>
> Hmmm... it depends! The required patch has been MFC'ed on January 2006:
> it works on 6.1, and on 6.0-STABLE >= Jan 2006, but not on 6.0-RELEASE.
> Either you'll have to apply the required patches
>
>
Le Ven 16 jui 06 à 8:43:12 +0200, Arnaud Quette <[EMAIL PROTECTED]>
écrivait :
> >> finally, what are you bsd and libusb versions?
> >
> >FreeBSD 6.0 and libusb 0.1.12.
>
> IIRC, there were such systems working
Hmmm... it depends! The required patch has been MFC'ed on January 2006:
it works on
On Friday 16 June 2006 21:03, Daniel O'Connor wrote:
> I didn't get around to trying serial today but hopefully I will be able to
> test it RSN.
>
> I'll keep you in mind as I test ;)
Serial works so I am less stressed now - I have a fallback position :)
I am going to try making the newhidups cod
On Friday 16 June 2006 18:20, Rob MacGregor wrote:
> On 6/16/06, Arnaud Quette <[EMAIL PROTECTED]> wrote:
> > > > 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 problem
On 6/16/06, Arnaud Quette <[EMAIL PROTECTED]> wrote:
> > 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?
No, but I'm still using serial on FreeBSD 5.4. I'm un
2006/6/16, Daniel O'Connor <[EMAIL PROTECTED]>:
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
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 i
2006/6/15, Daniel O'Connor <[EMAIL PROTECTED]>:
On Thursday 15 June 2006 18:40, Arnaud Quette wrote:
> > Have you had a chance to look at this? We're getting pretty close to ship
> > date so I won't be able to test it after much longer.
>
> yes, I'm currently modifying some things on the Developm
Hi Daniel,
2006/6/15, Daniel O'Connor <[EMAIL PROTECTED]>:
On Monday 22 May 2006 16:40, Arnaud Quette wrote:
> > I still can't turn the outlets on and off though, the value doesn't
> > change from 0 :( I have tried a few random numbers but no luck. Has
> > anyone had this work? I've tested it us
On Monday 22 May 2006 16:40, Arnaud Quette wrote:
> sorry for the long delay to answer...
No problem :)
> > Well I figured out my shutdown delay problem - setting it starts the
> > shutdown process (this is different to the APC model which is what I have
> > used in the past)
>
> right. And note
Hi Daniel,
sorry for the long delay to answer...
2006/5/22, Daniel O'Connor <[EMAIL PROTECTED]>:
On Tuesday 16 May 2006 10:14, Daniel O'Connor wrote:
> I am trying to talk to an MGE Pulsar Extreme UPS over RS232 with the
> mge-shut driver but I'm having some problems.
..
Well I figured out my
On Tuesday 16 May 2006 10:14, Daniel O'Connor wrote:
> I am trying to talk to an MGE Pulsar Extreme UPS over RS232 with the
> mge-shut driver but I'm having some problems.
..
Well I figured out my shutdown delay problem - setting it starts the shutdown
process (this is different to the APC model
Hi,
I am trying to talk to an MGE Pulsar Extreme UPS over RS232 with the
mge-shut driver but I'm having some problems.
It appears to init OK but I can't, say, turn the outlets off, eg..
harrow:~>upsc [EMAIL PROTECTED]
battery.charge: 78
battery.charge.low: 20
battery.runtime: 05760
driver.name: m
13 matches
Mail list logo
