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
On 4/7/06, Criggie <criggie@criggie.dyndns.org> wrote:> 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?If you have drivers for another OS, you can observe the communication between the host and the UPS. -- - Charles Lepple
Steven Ellis
2007-Aug-31 02:08 UTC
[Nut-upsuser] New UPS protocol choice - Dynamix PROGRESS
Carlos Rodrigues wrote:> On 4/9/06, Criggie <criggie at criggie.dyndns.org> wrote: > >> caffeine:/etc/nut# upsdrvctl -vvv start >> Network UPS Tools - UPS driver controller 2.0.2 >> exec: /lib/nut/fentonups -a powerpal >> Network UPS Tools - Fenton UPS driver 1.22 (2.0.2) >> Unknown ups - please report this ID string: >> #Dynamix UPS 1700D VER3.12 >> Detected Unknown PS 1700D on /dev/ttyS0 >> Communications with UPS lost - check cabling >> >> >> >> Its a fairly new UPS model - where do I go from here? >> > > It looses the communication immediately? You may want to try the > "powermust" driver (or "megatec" as it is called in the development > branch). >Criggie - Did you make any progress with the megatec driver? Checking on there appears to be some very similar models to the Dynamix units that can use that driver. Steve
Steven Ellis wrote:> Carlos Rodrigues wrote: >> On 4/9/06, Criggie <criggie at criggie.dyndns.org> wrote:>>> caffeine:/etc/nut# upsdrvctl -vvv start >>> Network UPS Tools - UPS driver controller 2.0.2 >>> exec: /lib/nut/fentonups -a powerpal >>> Network UPS Tools - Fenton UPS driver 1.22 (2.0.2) >>> Unknown ups - please report this ID string: >>> #Dynamix UPS 1700D VER3.12 >>> Detected Unknown PS 1700D on /dev/ttyS0 >>> Communications with UPS lost - check cabling>>> Its a fairly new UPS model - where do I go from here?>> It looses the communication immediately? You may want to try the >> "powermust" driver (or "megatec" as it is called in the development >> branch). >> > Criggie - Did you make any progress with the megatec driver? Checking on > there appears to be some very similar models to the Dynamix units that > can use that driver.Yes - Megatec works perfectly in nut 2.2 The only thing that has been lost is "battery-charge" percentage. Megatec has introduced "UPS-temperature" but sadly it reads 0 for me. Apparently the same model is badged by many different suppliers. If it looks basically like this then it should work. http://cdlnz.com/productimages/jpegs/ups1700d.jpg -- Criggie http://criggie.dyndns.org/
On Mon, May 5, 2008 at 4:05 AM, Peter McKenna <peter.mckenna at bitt.co.nz> wrote:> Thanks for your reply Carlos. > The ignoreoff suggestion didn't work. The driver appeared to not connect.Hmmm, my bad. I only added the "ignoreoff" option _after_ 2.2.1.> The Temp reading has never worked returning 0.0.That means the UPS doesn't have a temperature sensor.> The beeper did work in 2.0. I could toggle it with an instant command, but > now doesn't work with the same command. upsc just shows it as disabled. > The beeper has always worked when the ups is unplugged.Define "doesn't work". The beeper can still be heard after you try to disable it, or the driver still shows the beeper as "disabled"? In many models the beeper status flag is bogus (this is mentioned in the manpage btw) and never changes (it is always "enabled" or "disabled"). I'm not sure if in 2.0 the driver exposed the beeper status or not... PS: Please keep the list CC:ed when replying. Thanks. -- Carlos Rodrigues