similar to: [nut] blazer_soi: blazer driver, serial port over tcp/ip (#116)

Displaying 20 results from an estimated 2000 matches similar to: "[nut] blazer_soi: blazer driver, serial port over tcp/ip (#116)"

2013 Nov 06
0
Merging blzr as blazer (and un-merging voltronic?)
On Nov 1, 2013, at 9:03 AM, Charles Lepple wrote: > But if blzr supersedes both voltronic and blazer, I propose we rename blazer_{ser,usb} to blazer_{ser,usb}_old, then rename blzr* to blazer*, and revert the voltronic merge. Dan, The pull request against master looks good - thanks! What do you think about the renaming of blazer to blazer_old, and making blzr the new blazer driver? I still
2013 Nov 01
3
Merging blzr as blazer (and un-merging voltronic?)
Daniele, Thanks again for your work on both the voltronic and blzr drivers. To get the most exposure to new drivers, what we have typically done in the past is to rename the existing driver as *-old, so that users get the new driver by default when they upgrade (but the old driver is still available if there are regressions). This is how we are incorporating Michal's apcsmart updates. On
2013 Nov 06
1
Merging blzr as blazer (and un-merging voltronic?)
In my opinion, there might be just one problem: the blzr driver doesn't provide anymore two splitted drivers (serial and usb), so this isn't going to be a 'silent update' for those using these drivers (should we provide symlinks or the like?). If this doesn't sound like a problem to you, I'll take care of the rename. Plus, if you could take a look to the blazer-fix pull
2014 Jun 02
2
blazer_ser battery.high / battery.low
Hi, thanks for the reply. On 2014-05-29 05:21, Charles Lepple wrote: >> Now my questions: >> 1. should the blazer_ser's high voltage be the voltage during charging >> or right after I've unplugged it from the mains? > sounds like during charging (or more accurately, during float charging at the end of the cycle): > >
2014 Jun 02
0
blazer_ser battery.high / battery.low
On Jun 2, 2014, at 12:25 PM, Andreas Lausch / TBT wrote: > > Hi, > > thanks for the reply. > > On 2014-05-29 05:21, Charles Lepple wrote: >>> Now my questions: >>> 1. should the blazer_ser's high voltage be the voltage during charging >>> or right after I've unplugged it from the mains? >> sounds like during charging (or more
2012 Jun 09
3
[HCL] REDi/Centralion Blazer 600 VA (BLAZER600c) supported by blazer_ser
The REDi Blazer 600VA (BLAZER600c) UPS found here [ro_RO]: http://www.emag.ro/ups-redi-blazer-600va-blazer600c/pd/EX5X2BBBM/ which is actually a Centralion Blazer 600VA [en_TW]: http://www.centralion.com/html/product/back-Product-ups-blazer400.htm works with the blazer_ser driver ----------shell output---------- # upsrw ups # upscmd -l ups Instant commands supported on UPS [ups]: beeper.toggle -
2005 Sep 23
1
Tecnoware Easy Power 1200 and blazer driver (was: Re: Suggestion)
Hi Marcello, Marcello wrote: > a few days ago I bought a "Tecnoware Easy Power 1200" UPS for my little Linux > server, and in these days I haven't found nothing on the net apart the > "driver" for Linux (written in Java) on Tecnoware site (www.tecnoware.com<http://www.tecnoware.com> ). > So i tried NUT: while trying one by one all the possible supported
2011 Apr 12
1
blazer & megatec drivers
Hi, I've being using nut 2.2.2 (Debian Lenny) via megatec_usb driver for IPPON Back UPS 600. Then I upgraded to nut 2.4.3 (Debian Squeeze) with broken megatec_usb. I moved to blazer_usb, it connected IPPON. [myups] driver = blazer_usb port = /dev/usb/hiddev0 desc = "Local UPS" #from megatec.c: batteries[] = {{ 12.0, 9.0, 16.0, 9.7, 13.7, 0.0 },
2010 Dec 30
1
Blazer upsdrv_shutdown function
Hi all, Arjen can you enlighten me about the function of the blazer upsdrv_shutdown function. I think they are in the wrong order. Regards Kjell
2013 Nov 09
1
Salicru SPS One in Debian
Not of a big help here, but I think it's a voltronic power vesta 650: http://www.voltronicpower.com/oCart2/index.php?route=product/product&path=37&product_id=52 If that is the case, it should work both with the blazer drivers (i.e. all but the shutdown sequence) and with the now defunct voltronic ones. With arno's words: "We are currently merging a new driver to replace
2023 Jan 15
1
PR to test for users of Qx devices (blazer and nutdrv_qx)
Cheers, One PR waiting to get into 2.8.1 release timeframe is https://github.com/networkupstools/nut/pull/1652 stemming from issue https://github.com/networkupstools/nut/issues/1279 The gist of it is that "battery.voltage" and "battery.charge" were not always reported correctly with nutdrv-qx driver (might be handled better by blazer drivers though), and the overrides
2012 Jun 04
4
Driver for a REDi Blazer 600VA UPS
I'm running NUT 2.6.3 on Debian wheezy [ with a 3.3.0 i686 kernel ] I've installed NUT via Debian APT [ package nut version 2.6.3-1 ] I have a REDi Blazer 600VA (BLAZER600c) UPS and I want to detect power failures. I have tried the following drivers: * gamatronic: Can't talk to UPS on port /dev/ttyS1! * bestups: Unable to detect a Best/SOLA or Phoenix protocol UPS * blazer_ser: No
2013 Apr 02
3
blazer driver: Possible bugs with battery packs
Hello all, long time away from this list, glad to be around again! I have this Powercom Vanguard VGN VGD-20K31. Some details of this model: * 3-phase input, single phase output * Model has 240V / 12V9AH x 20 x 2SET, plus another set of 20 batteries. All in all, 3 sets * Serial connection to Windows 2k3 server with UPSMon Now I was strongly considering replacing the bundled no-good upsmoon
2023 Jan 17
1
PR to test for users of Qx devices (blazer and nutdrv_qx)
Jim Klimov via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> > > Cheers, > > One PR waiting to get into 2.8.1 release timeframe is https://github.com/networkupstools/nut/pull/1652 stemming from issue https://github.com/networkupstools/nut/issues/1279 > > The gist of it is that "battery.voltage" and "battery.charge" were not always reported
2023 Jan 17
1
PR to test for users of Qx devices (blazer and nutdrv_qx)
Jim Klimov via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> > > Cheers, > > One PR waiting to get into 2.8.1 release timeframe is https://github.com/networkupstools/nut/pull/1652 stemming from issue https://github.com/networkupstools/nut/issues/1279 > > The gist of it is that "battery.voltage" and "battery.charge" were not always reported
1999 May 03
0
login w/o password
I'm using an old Intel netport printserver that loads it application code form a netbios resource. As I don't have (or want) a Win station on my network I thought I can use samba for that issue. The problem now is that this itel netport tries to login with user=netport and NO password. So I set up a ressource like this: [NETPORT] comment = Intel Netport RBL file path =
2006 Apr 11
2
SOS : Help needed for UPS Centralion Blazer 2000VA USB
-----BEGIN PGP SIGNED MESSAGE----- Hello, I leave a mail here because I can't find any solution in order to get the nut working with this UPS despite I search everywhere on the net. I've bought this UPS recently after that an MGE-UPS Ellipse 1200 USB burn. I've those information about the UPS : Reseller link : http://www.alpha-power-technologie.com/images/GPi-usb.pdf In his
2006 Apr 11
2
SOS : Help needed for UPS Centralion Blazer 2000VA USB
-----BEGIN PGP SIGNED MESSAGE----- Hello, I leave a mail here because I can't find any solution in order to get the nut working with this UPS despite I search everywhere on the net. I've bought this UPS recently after that an MGE-UPS Ellipse 1200 USB burn. I've those information about the UPS : Reseller link : http://www.alpha-power-technologie.com/images/GPi-usb.pdf In his
1997 Oct 24
1
NEtport
Hi, is it possible to print to a intel netport express? i am on a linux machine, every other machine on the network is a win95 or nt machine and i cant figure out why it wont let me print to the netport. when i do smbclient '\\Np1\np1_lpt1' -P it just times out and gives this error. smb-print.log -------------------------------------------------------------------- server NP1, service
2011 Nov 17
3
UPS MGE serial cable over network.
Hi, I'm forwarding your mail to the NUT list, because of a lack of time, and also since some others (Charles) already looked at this issue IIRC (related to the development branch 'netport'). cheers, Arnaud -- Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer -