similar to: Gamatronic UPS using nut 2.0.3

I was told by someone who used to have a Gamatronic to use the Fenton driver. However, when I use the Fenton driver I receive the following error: Unknown ups - please report this ID string: #GAMATRONICS SC06GM0G V8.0 Detected Unknown C06GM0G on /dev/ttyS1 The person who pointed me at this driver mentioned that Gamatronic changed their banner and a patch or code change is needed. I

I have 2 identical AudioCodes MP-112s. They have the same config except for the SIP usernames/passwords and the device IP. The configs in extension.conf and sip.conf are also identical. On one box, when I pick up the phone, I get a fast busy and the logs/debug show an automatic hangup. On the other device, I can make calls without a problem. I can even call the phone that can't make a

On Dec 18, 2013, at 3:17 AM, Leon Vak wrote: > Actually, someone has already done most of the work for our units, however I might have general technical details to contribute, like the fact that the driver for our equipment is called "gamatronic", while actually it is just the well-known SEC protocol (from the former Systems Enhancement Corporation) and not our invention. I wonder

Hi I am running FC5 with nut coming from the fc5 extras repositories. I am trying to configure a Gamatronic D-Compact ups. The cable that came with the ups has a serial connector on one end and a usb on the other. cat /proc/bus/usb/devices produces T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 4 Spd=1.5 MxCh= 0 D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P:

Greetings to all developers of the Network UPS Tools, and Merry Christmas greetings to those of you who celebrate! I have been looking in to your work from time to time, and I am very impressed with your efforts. I think this is a good time to officially supply the required information about Gamatronic products to the community. Furthermore, I would like to know how our company may contribute

This is the same as https://github.com/networkupstools/nut/issues/254 , right? (It's on my TODO list. DDL updates take a little longer than HCL updates.) Other comments below. > On Dec 29, 2015, at 1:55 PM, Thiago Wiezbicki - NHS <thiago.wiezbicki at nhs.com.br> wrote: > > Device Manufacturer: NHS > Device Name: Laser Senoidal 5000VA > > upsc output when the UPS is

Hello Users: I'm using R version 2.0.1, and having problems with RODBC. Everything works fine when I use Rgui, but when I try to use Rterm and issue the commands library(RODBC) con <- odbcConnect("MySQL", "test") I get the following error: Error in sqlQuery(con, str) : first argument is not an open RODBC channel In addition: Warning messages:

*Q: Quick question: does "battery.runtime" update when the device is on battery, or is this field always zero?* *A: Yes, the UPS battery time starts counting when the device starts on battery.* Q: "battery.runtime.low" should be the number of seconds remaining before switching to "LB" status. This seems large, even for a 6000 VA UPS. Is this configurable? A: I

Gidday all - I'm a new user to nut. I've got some cheap powerpal UPSs working fairly well. However I also have a new Dynamix UPS-1700D and an old Powercom KIN-1700 something unit that I cannot make work right. The best method I've found is "trial and error" which sounds a bit last-resort. Is there any better way to find out what protocol is used? -- Criggie

Below the answers: > This is the same as https://github.com/networkupstools/nut/issues/254 , right? Yes, this UPS is the same. > Does battery.runtime only get updated when on battery power, or is this with a different load? > battery.runtime.low: 59940 > battery.temperature: 00 Yes, this time time is updated on battery power, This is a dynamic counter that changes with a different

Device Manufacturer: NHS Device Name: Laser Senoidal 5000VA upsc output when the UPS is in normal condition: battery.charge: 100 battery.current: 0.4 battery.date: 12292015 battery.runtime: 00000 battery.runtime.low: 59940 battery.temperature: 00 battery.voltage: 163.4 device.mfr: NHS Sistemas de Energia device.model: Laser Senoidal 5000VA device.type: ups driver.name: gamatronic

On Jan 13, 2016, at 6:00 AM, Thiago Wiezbicki - NHS <thiago.wiezbicki at nhs.com.br> wrote: > > The battery.run.low can be higher than battery.runtime, do you agree? I agree with that statement, given what the gamatronic driver is currently reporting. However, I think it should report the elapsed time as battery.runtime.elapsed. I have created a Github issue to clarify the

Hi Leon! Thanks for your effort in reaching out! I have been involved in Open Source projects and used Open Source for years. Your questions are very common ones for companies interested in getting involved in Open Source projects, so I will attempt to provide you with some answers. NUT is a collaborative effort, but as these projects go there is not a single person "in charge"

On Nov 12, 2014, at 5:46 AM, Thiago Wiezbicki <thiagowzb at gmail.com> wrote: > > > Device Manufacturer: NHS > Device Name: Expert C Online 6000 > > upsc output: > > battery.charge: 100 > battery.current: 0.6 > battery.date: 01012014 > battery.runtime: 00000 Quick question: does "battery.runtime" update when the device is on battery, or is this

I wasn't clear. battery.runtime.low is not a counter, but a value estimated in seconds that is decreasing conforming the battery is discharging. It's mean: How much time (in seconds) will be necessary until the battery achieve the depleted status ( http://www.networkupstools.org/protocols/sec.html#Estimated_Minutes ) . If the UPS don't have a load, this value will be higher than the

Device Manufacturer: NHS Device Name: Expert C Online 6000 upsc output: battery.charge: 100 battery.current: 0.6 battery.date: 01012014 battery.runtime: 00000 battery.runtime.low: 59940 battery.temperature: 29 battery.voltage: 210.5 device.mfr: NHS Sistemas de Energia device.model: EXPERT GIII 8kVA device.type: ups driver.name: gamatronic driver.parameter.pollinterval: 20

Hi. I recently upgraded to R version 2.4.0, and I have found that the "debug" package no longer works. In particular, when I try to debug a function, I get the following error message: Error in attr(value, "row.names") <- rlabs : row names must be 'character' or 'integer', not 'double' I have, of course, taken all the necessary preceding

Many useful Netscape plugins don't come in Linux versions. Is it possible to make my Linux copy of Netscape use Windows-compiled plugins? If so, how?

> +22 = Gamatronic UPSs with alarm interface > + [CP=RTS] [OL=CTS] [LB=\-DCD] [SD=DTR] > + > +22 = CyberPower SL seriess > + [CP=RTS] [OL=CTS] [LB=\-CAR] [SD=DTR] > + > + This part of the patch is no good. While TIOCM_CAR is equivalent to TIOCM_CD (at least in some implementations) CAR certainly isn't handled the same as DCD by genericups. It won't be

I am using nut 2.2.2 and I have a CyberPower CP550SL. According to the drivers list, I should be using genericups with upstype set to 7, but when I try that and when I run upsc I get: driver.name: genericups driver.parameter.LB: 04 driver.parameter.pollinterval: 2 driver.parameter.port: /dev/ups driver.parameter.upstype: 7 driver.version: 2.2.2 driver.version.internal: 1.34 ups.mfr: CyberPower