search for: 36v

Hi, Charles, On Wed, 2 May 2007 07:58:08 -0400, you wrote: > > Will that be enough to make it useable as a contribution? I believe > > the more sensible values for 36V UPS'es will be useful to other models > > than the one I have, too. > > Sounds good, but I don't think I saw it hit the list yet... I now have the following in megatec.c: static BatteryVolts batteries[] = { { 12, 9.0, 16.0, 9.7, 13.7 }, /* Mustek PowerMust 600VA Plus */...

...r NUT. However, while NUT does recognize the UPS as using a Mecatec type protocol and can communicate with it, I get the following error message: "This UPS has an unsupported combination of battery voltage/number of batteries" The UPS has 3 batteries of 12V each. The nominal voltage is 36V but the UPS reports 40.8V (which is correct; the float charging voltage is 13.6V per battery). This message is generated by the driver (megatec.c) but I'm not sure what causes it. The comments in the driver code are a bit sparse. Questions: - What condition (voltage, other parameters report...

...r NUT. However, while NUT does recognize the UPS as using a Mecatec type protocol and can communicate with it, I get the following error message: "This UPS has an unsupported combination of battery voltage/number of batteries" The UPS has 3 batteries of 12V each. The nominal voltage is 36V but the UPS reports 40.8V (which is correct; the float charging voltage is 13.6V per battery). This message is generated by the driver (megatec.c) but I'm not sure what causes it. The comments in the driver code are a bit sparse. Questions: - What condition (voltage, other parameters report...

...p\10\17 \216\220\0\0\0\213E\f\213M\10\213@\f\213"..., 8192) = 8192 1246310231.480990 write(4, "\377\377C;_\10|\360\213E\f\211u\0109p\10 \17\216\220\0\0\0\213E\f\213M\10\213@\f\213"..., 8192) = 8192 [...] 1246310231.481945 read(3, "\312u\1\0\336u\1\0\352u\1\0\374u\1\0\16v\1 \0\36v\1\0,v\1\0:v\1\0H"..., 8192) = 8192 1246310231.481986 write(4, "\312u\1\0\336u\1\0\352u\1\0\374u\1\0\16v\1 \0\36v\1\0,v\1\0:v\1\0H"..., 8192) = 8192 1246310231.482063 read(3, "\377\271^\0\377\302v\0\322\247m\0\364\313 \226\0\377\300h\0\374\277h\0\372\304x\0\340\261p\0\341"...

...orted values with e.g. `upsc` command-line client to be sure. What I think happens here is that the driver uses a `battery.voltage.low/nominal/high` group of readings which does not match the hardware circumstances well for some reason. These readings can be provided by a device (and then a 3x12=36V nominal would be reasonable), it can be imposed in your driver configuration with `override.battery.voltage.... = ...` lines, and in some but not all drivers the ranges can be guessed from other information served by the device, as a fallback. Use of overrides is fairly popular, so check if that...

"mustek" is all but deprecated, so the effort should be to get powermust/megatec working. Since you have the latest development code installed, can you please run "/path/to/megatec -DDDD -a the_name_for_your_ups" (this without starting NUT normally - i.e. without upsd, upsmon, etc) and send me the output? The output should help me figure out why you are getting data stale

Hello, I am using Nut 2.8.0 (2.8.0-7 packages) Debian 'Bookworm' in it's Devuan form 'Daedalus'. When I look at my Eaton (ex-MGE Powerware) E5115 UPS boxes in NUT 'upsstats" I am confused by the battery readings. Under the 'System' column I can click on the link and obtain a GUI with a few meters. The NUT 'upsstats' battery voltage meter for these

...[ups1] driver = bestups port = com1 id = 610,1000,230,230,10.0,36.0 nombattvolt=41.1 battvoltmult = 18 With regard to the id option, the 2nd, 3rd and 4th options seemed ok. Not sure about the fifth (10.0). And definitely not sure about the last (36.0). I used 36.0 because the Best 610-1000 lists 36V as the DC bus voltage. Not sure if that is correct or not. According to specs ( http://www.lexis.gr/upload/File/ProductBrochures/XPower/Tigrablack.pdf ) this Xpower ups has three (3) 12V batteries. I used nombattvolt 41.1 since that seemed to be similar also to the Best 610-1000. As for battvo...

..."missing CR...etc.."). As for now there are 2 modification I'd like to suggest you: - For Online Type UPSs the Megatec protocol describes that the battery voltage is provided in the form of V per Cell, not V per block, but the driver doesn't care because I see 2.21V instead of 36V in UPSC (Battery.voltage). I think that this should be corrected so the customer can see the string voltage and not the single Cell voltage (Megatec 0.06). - About battery low and high guesstimation the formula uses these values: batt.volt.low = 104 * batt.volt.nom / 120 (for a 12V VRLA -->...

...2 (12V) 24V Interactive 2000VA 4 (12V) 48V On-Line 1000VA 3 (12V) 36V On-Line 2000VA 6 (12V) 72V On-Line 3000VA 8 (12V) 96V On-Line 5000VA...

Hi, I've been using TrippLite's PowerAlert software with my RM2200XL2U rack system and my APC BackUPS desktop systems. Unfortunately it doesn't work with openSUSE 10.2 (the software has problems with the serial port and UPS interfaces on openSUSE 10.2), so I've been looking at other options. I see that openSUSE 10.2 includes NUT, and it appears to work with my TrippLite UPS via

...; > As for now there are 2 modification I'd like to suggest you: > > > > > > - For Online Type UPSs the Megatec protocol describes that the battery voltage is provided in the form of V per Cell, not V per block, but the driver doesn't care because I see 2.21V instead of 36V in UPSC (Battery.voltage). I think that this should be corrected so the customer can see the string voltage and not the single Cell voltage (Megatec 0.06). > > Right, thanks for pointing out (if only all devices strictly adhered > to the standard and reported it the right way...). > Wh...

Dear Daniele, nice to meet you, I'm a collegue of Gabriele. The problem with "blazer_usb" driver ("blazer_ser" works correctly) is related to the following commands: - "F" and "I": when the KRAULER subdriver check these UPS answers it uses wrong constants to check the lenght of the received packets, so these commands are considered as "not