On Thu, 2007-11-08 at 14:19 +, Carlos Rodrigues wrote:
> Try "megatec_usb". If it doesn't work, it may be possible to add support.
Wow, that worked right away (after recompiling 2.2 for etch):
# cat /etc/nut/ups.conf
[Pro]
driver=megatec_usb
port=/dev/usb/hiddev0
# ./megatec_usb -a Pro -DDD
>>> Adding 'baudrate = 9600' to the 'ups.conf' entry for this UPS should
>>> fix this.
>> Strange, it tells me this is not supported. I'm on 2.0.4.
> Ahh... It goes in the global section. Sorry.
No, it should be in the UPS section since it is a driver specific thing.
That is, if you fix the typo I
Den Thursday 08 November 2007 16.11.11 skrev Tobias Balle-Petersen:
> Tobias Balle-Petersen wrote:
> > Hello Arjen.
> >
> > Arjen de Korte wrote:
> >> Adding 'baudrate = 9600' to the 'ups.conf' entry for this UPS should fix
> >> this.
> >
> > Strange, it tells me this is not supported. I'm on 2.0.4
2007/11/8, [EMAIL PROTECTED] <[EMAIL PROTECTED]>:
> ...
> I'll bet it has something to do w/ their software. They said
> just run their software when I asked them to document the USB protocol
> for their UPS ;-)
The situation should change soon ;-)
Last week, the newly formed MGE Office Protecti
Tobias Balle-Petersen wrote:
> Hello Arjen.
>
> Arjen de Korte wrote:
>> Adding 'baudrate = 9600' to the 'ups.conf' entry for this UPS should fix
>> this.
>
> Strange, it tells me this is not supported. I'm on 2.0.4.
Ahh... It goes in the global section. Sorry.
Tobias
Hello Arjen.
Arjen de Korte wrote:
> Adding 'baudrate = 9600' to the 'ups.conf' entry for this UPS should fix
> this.
Strange, it tells me this is not supported. I'm on 2.0.4.
Tobias
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
> Hello all.
>
> I have now connected the UPS via a serial-cable to a PC running Debian
> Etch and Nut 2.0.4.
>
> When running "upsdrvctl -u root start" I get:
> Communications with UPS lost: Error executing command
> Communications with UPS lost: Error executing command
> Communications with UPS
Hello all.
I have now connected the UPS via a serial-cable to a PC running Debian Etch and
Nut 2.0.4.
When running "upsdrvctl -u root start" I get:
Communications with UPS lost: Error executing command
Communications with UPS lost: Error executing command
Communications with UPS lost: Error exec
On Nov 8, 2007 7:14 AM, Tobias Balle-Petersen <[EMAIL PROTECTED]> wrote:
> Hello
>
> Arnaud Quette wrote:
> > we'll need to have more verbose info.
> > please exec "export USB_DEBUG=3 && /lib/nut/bcmxcp_usb -DDD -a ups1"
> > and send us the gzip'ed output
>
>
> My machine cant seem to find the expo
On Nov 8, 2007 1:18 PM, James Andrewartha <[EMAIL PROTECTED]> wrote:
> I recently installed a Upsonic PrOffice 650 UPS, which is a cheap model[1]
> available in Australia. It has a serial and USB port, and comes with a
> note saying WinPower software can be downloaded from [2]. Investigation of
> t
Hello Ken.
[EMAIL PROTECTED] wrote:
> FYI, I had this problem about a year ago w/ the 9120 and I believe that
> was the same conclusion. It'd be really nice to get the USB port working.
> I've been using a serial->USB cable.
What is the name of the converter you are using?
> Also, AFAIK, you c
"Arjen de Korte" wrote:
> 1) Apparently, this UPS needs to be told only to reply to specific
> requests and not send unsollicited status updates. The bcmxcp (serial)
> driver supposedly does this, the bcmxcp_usb (USB) doesn't. However, the
> UPS remembers the last status, so this might help.
FYI,
Hi,
I recently installed a Upsonic PrOffice 650 UPS, which is a cheap model[1]
available in Australia. It has a serial and USB port, and comes with a
note saying WinPower software can be downloaded from [2]. Investigation of
the software shows it to be Java with native libraries for serial and
>> Have you tried the serial connection?
> No, there is no serial port on my machine.
If you have one, a serial-to-USB converter is a cheap solution to add one.
Many (not all) are supported by recent kernels.
>> 1) Apparently, this UPS needs to be told only to reply to specific
>> requests and no
Hi,
>
> Apologies if this is a known problem. I have just joined the list and
> haven't done an exhaustive search of the archives. Also I am no UPS
> expert, so please excuse me if some of my terminology is poor.
>
> I use an MGE Pulsar Extreme 700C connected via RS232 to the linux
> server it
Hello Arjen.
Arjen de Korte wrote:
> Have you tried the serial connection?
No, there is no serial port on my machine.
> 1) Apparently, this UPS needs to be told only to reply to specific
> requests and not send unsollicited status updates. The bcmxcp (serial)
> driver supposedly does this, the
Hello
Arnaud Quette wrote:
> we'll need to have more verbose info.
> please exec "export USB_DEBUG=3 && /lib/nut/bcmxcp_usb -DDD -a ups1"
> and send us the gzip'ed output
My machine cant seem to find the export command.
Thanks,
Tobias
___
Nut-upsuse
2007/11/8, Tobias Balle-Petersen <[EMAIL PROTECTED]>:
> Hello
>
> Kjell Claesson wrote:
> > Then you should get new version of nut as 2.0.4 is past date.
>
> I have updated to nut 2.2.0-1 as suggested. Unfortunately I still get the
> same type of errors:
>
>
> Network UPS Tools - UPS driver co
Hello...
Just to make sure I did a clean install of debian etch and tested. I still get
the same errors. Nut
2.0.4.
Tobias
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
> I have updated to nut 2.2.0-1 as suggested. Unfortunately I still get the
> same type of errors:
>
>
> Network UPS Tools - UPS driver controller 2.2.0-
> Network UPS Tools - BCMXCP UPS driver 0.11 (2.2.0-)
>
> Warning: This is an experimental driver.
> Some features may not function correctly.
>
Hello
Kjell Claesson wrote:
> Then you should get new version of nut as 2.0.4 is past date.
I have updated to nut 2.2.0-1 as suggested. Unfortunately I still get the same
type of errors:
Network UPS Tools - UPS driver controller 2.2.0-
Network UPS Tools - BCMXCP UPS driver 0.11 (2.2.0-)
W
Tobias Balle-Petersen wrote:
> Hmmm... I guess I need a kernel newer than the one in atable:
Just realized I dont have the etch stable kernel on my testing system. Igonre
the above.
Thanks,
Tobias
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.
Arnaud Quette wrote:
> the source repository is also there (now) if you will to rebuild the package
> ;-)
Hmmm... I guess I need a kernel newer than the one in atable:
Unpacking nut (from nut_2.2.0-1_powerpc.deb) ...
Setting up nut (2.2.0-1) ...
udev requires a kernel >= 2.6.15, not started.
Th
Hi Arnaud.
Arnaud Quette wrote:
> the source repository is also there (now) if you will to rebuild the package
> ;-)
Great, sounds good. I was just about to compile from the source on the site. I
guess this way is
better/easier. I'll give it a try and report back.
Thanks,
Tobias
_
2007/11/8, Tobias Balle-Petersen <[EMAIL PROTECTED]>:
> Hi Arnaud.
>
> Arnaud Quette wrote:
> > add this line to your /etc/apt/sources.list:
> > deb http://opensource.mgeops.com/stable/debian binary/
>
> I'm running on a PowerPC. The repository only has i386 packages as far as I
> can tell.
the s
Hi Kjell.
Kjell Claesson wrote:
>> I have tried two different USB-cables. The one that came with the UPS and
>> another one I had lying around. I have tried both ports on the computer
>> (Apple mac G4).
>>
>
> Was there any difference in the communication ?
Just checked again. The communication
Hi Arnaud.
Arnaud Quette wrote:
> add this line to your /etc/apt/sources.list:
> deb http://opensource.mgeops.com/stable/debian binary/
I'm running on a PowerPC. The repository only has i386 packages as far as I can
tell.
Tobias
___
Nut-upsuser mail
Kjell Claesson wrote:
> Was there any difference in the communication ?
No.
> Both yes and no. It should work but as no one have give a positive feedback on
> this we can not enter it into the chart.
OK, so we don't actually know it works.
>> Does communicating with the UPS demand more of the
28 matches
Mail list logo
