similar to: N-Power MEV-3000LT compatibility report and problem

On Aug 11, 2013, at 2:12 PM, ????????? ???????? wrote: > I see no problem with how the device communicates the Blazer/Megatec protocol. > I must have found a bug in the driver. It is possible that the shutdown was tested with a different implementation of the protocol. What do you get from the "I" command? On Aug 11, 2013, at 11:25 AM, ????????? ???????? wrote: > So I

Hello, sorry for messing up the things. I mean many copies of the same text in my previous message and mixing up the command names, it turned out that I forgot the protocol details after so many years. I found my records, connected a serial terminal to the UPS and found that the device itself works as expected so my problem cannot be explained with device incompatibility. Below is excerpt from

Hello, the code below the failing part mentions this flavor of protocol, drivers/blazer_ser.c:463 /* * If a command is invalid, it will be echoed back. * As an exception, Best UPS units will report "ACK" in case of success! */ I prepared a patch, it adds a similar check and also checks (in both occurencies) for blazer_command()<0, the latter

Hello, > What do you get from the "I" command? A string of 8 spaces. >> So I believe the compatibility list deserves two new lines. > >Probably best to delay adding this to the HCL until we can get the driver to shut down the UPS properly. I debugged the problem. From the source, drivers/blazer.c:418 /* * If a command is invalid, it

Hello list, we've got a PowerWalker VI 1000E/RT LCD UPS and like to use it with NUT using the blazer_ser driver. For the blazer_ser driver to display percentage, one has to add battery.voltage.high and battery.voltage.low voltages to the ups config. Here's what I received from the powerwalker customer service: Battery-Low Voltage: 21.6VDC Battery Shutdown: 19.2VDC Now my questions: 1.

Hello First things first, thanks for great work with NUT. For years I used Informer compact 3kVA UPS http://www.informups.com/informer_compact.html with nut/megatec serial driver, but it stopped working when I switched to blazer_ser with 2.6.0 upgrade. I'm using 2.6.0 on gentoo. Blazer_ser seems to connect with UPS, but upsmon reports driver not connected. uname -a Linux localhost

Hi, I'm trying to get an Effekta UPS (works directly with blazer_ser) working behind a seriell to ethernet converter (Brainboxes ES-246). I've set the converter to 2400 baud, 8N1, no flow control. On the linux side I started socat and blazer_ser. All I got are timeouts after 12 seconds. I can see network traffic with tcpdump but I've no idea what to do to get this working. Does

Hi, today I have tested the Zinto 800 with blazer_ser and blazer_usb on Citrix Server 7.0. Both works fine. upsc-Output (blazer_ser): battery.charge: 94 battery.voltage: 25.70 battery.voltage.high: 26.00 battery.voltage.low: 20.80 battery.voltage.nominal: 24.0 device.mfr: device.model: ZINTO 800 device.type: ups driver.name: blazer_ser driver.parameter.pollinterval: 2 driver.parameter.port:

Manufacturer: Aviem Power RT 1000-3000VA Description: Rack/Tower Intelligent Online LCD UPS. connected with serial cable. #upsc battery.voltage: 24.96 battery.voltage.low: 21.5 battery.voltage.nominal: 24.0 beeper.status: enabled device.mfr: device.model: device.type: ups driver.name: blazer_ser driver.parameter.pollinterval: 2 driver.parameter.port: /dev/ttyUSB1 driver.version: 2.6.3

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

Hi Artronic art 1000 bl is supported partially by blazer_ser: battery.voltage: 13.40battery.voltage.nominal: 12.0 beeper.status: enabled device.type: ups driver.name: blazer_ser driver.parameter.pollinterval: 2 driver.parameter.port: /dev/ttyS0 driver.version: 2.6.3 driver.version.internal: 1.51 input.current.nominal: 4.0 input.frequency: 50.1 input.frequency.nominal: 50 input.voltage: 232.9

I am have a nice result whith blazer_ser driver! respect! # ./nut start Network UPS Tools - UPS driver controller 2.4.1 Network UPS Tools - Megatec/Q1 protocol serial driver 1.51 (2.4.1) Supported UPS detected with megatec protocol Vendor information read in 1 tries Battery runtime will not be calculated (runtimecal not set) <================= !!! Starting nut. Network UPS Tools upsd 2.4.1

Hello, I am new to UPS stuff, please be patient with me ;-) Archlinux i686, kernel 3.0-ARCH #1 SMP PREEMPT. nut 2.6.1 installed from source via Arch's AUR repository. Mother board GA D525TUD with two serial ports, both enabled in BIOS. I got some old Orvaldi 520 PL UPS [1], which is supposed to be supported by the vendor [2] with sw called UPSmart. The statically compiled i386 binary ran

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

Hi, I have an OEM of KStar UDC9101S which is Megatec protocol rs232 capable unit. So I use blazer_ser protocol=megatec /dev/ttyUSB0 with no issue to get NUT running. Please direct me what command should I issue to collect the data in order to include the UPS to device database? P.S. tryed /lib/nut/blazer_ser -DD... but no difference from a regular output has being added by the driver.

Hi Charles, I'll try the blazer_ser and the nutdrv_qx with version 2.7.1 later. Below, the result of 'lsusb -vvv' requested: Bus 004 Device 002: ID 04b4:5500 Cypress Semiconductor Corp. HID->COM RS232 Adapter Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.00 bDeviceClass 0 (Defined at Interface level)

Hi Charles, I am done with few things: I made the cable - looks good, because I see some activities. I upgraded NUT to 2.7.3. but I have no success to start driver(this are the outputs) nut.cfg MODE = netserver ups.conf [infosec] driver = nutdrv_qx (or blazer_ser) port = /dev/ttyS1 desc = "XP Pro 2500 RM" output(nutdrv_qx cmd upsdrvctl -DDD start) Network UPS

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

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 -

Hi Charles, >----- Original Message ----- >From: "Charles Lepple" <clepple at gmail.com> >To: "R?bert SZAKSZ" <robert at szaksz.eu> >Cc: nut-upsuser at lists.alioth.debian.org >Sent: Monday, November 16, 2015 3:20:17 PM >Subject: Re: [Nut-upsuser] Contact-closure UPS > >[please use reply-all when responding - the list does not modify the