similar to: Masterguard A-19 3000

Hello again. Back in the day (2007) I wrote a USB-capable driver for my Masterguard/Phoenixtec UPSes (in case you locally archived this list, this very mail is a reply to a rather long thread from then), which I used ever since. However, the world has been going on since then and I need to get away with the old 2.0.4 binaries currently in use. These boxes (I use two A3000-19 and two A700-19) are

> What driver are you using? You can try the "masterguard" driver, or "megatec". I have tried the "masterguard" driver. The "megatec" doesn't work as well, it says that it is not detecting a Megatec protocol UPS. I think I will try swapping the RXD and TXD pins. Steve

Hi, I'm trying to talk to an old Masterguard UPS A3000 so I can determine current load and status etc, to determine the best replacement options. After a fair amount of google fu, and attempting different things, this is where I have ended up. First, environment: OS: Linux (Debian Stable) NUT Version: 2.7.2-1 (Debian unstable package) UPS details (on the rear lable): Manufacturer:

=?ISO-8859-1?Q?Edgar_Fu=DF?= wrote: > > > On the other hand, if it is not a HID device, then it is most likely a > > serial-over-USB protocol > Yes, it is serial-over USB, but non-standard. > > > might be supportable by one of the existing serial-over-USB drivers > I did not look into these as they wouldn't support the specific > serial protocol

can you also give a try to megatec and send us back some upsc output of your various tests? Mathias Mayrhofer wrote: > > Arnaud QUETTE wrote: > > > Mathias Mayrhofer wrote: > it works (except of the temperature) > > thanks a million!! > > > > Sorry to bother you, > > > 'nut' is great (it was the only thing that worked on by belkin usv), >

I've just written an NUT driver to manage a Masterguard UPS connected via USB, and some questions arose. Why I wrote a new driver? The servers in question only have two serial ports, so I want to use USB. I first wrote the low-level USB routines expecting to integrate them into the existing masterguard driver. However, that driver was so rudimentary I wrote my own one. It can be

This is the patch to include SVN revision level in version number displays. There should be two enclosures; the patch itself and a new source file. common/upsversion.c. upversion.c defines a single function. upsversion(), that returns a version string for display. Some Makefile trickery ensures that this file will be recompiled whenever the project's SVN revision level has changed since it

It seems the `libmodbus` library or headers were not found, or something similar - so the driver against it was not built. Did you install `libmodbus-dev` before the build? What does `config.log` in the build root say (and.or the summary shown after you run the `configure` script)? On Sat, Sep 16, 2023 at 7:46?PM FatGear <fatgear1 at free.fr> wrote: > Hi, > > I don't know what

Hi all, I am facing difficulty on how to use bootstrap sampling and below is my example of function. Read a data , use some functions and use iteration to find the solution( ie, convergence is reached). I want to use bootstrap approach to do it several times (200 or 300 times) this whole process and see the distribution of parameter of interest. Below is a small example that resembles my

Hello there, I don't think that's working,? I have done all your repo but i don't know how it's supposed to work. I have a idea, change vendor id and product id? to make the driver try to connect to the ups, what do you think of that ? With this driver maybe : usbhid-ups FatGear Le 16/09/2023 ? 20:40, Jim Klimov a ?crit?: > It seems the `libmodbus` library or headers were

Hi, a few days ago, I bought some of those Mustek UPSes that have both a serial and a USB connector. Currently only the serial port is supported by the megatec driver. This works fine so far. Now I have seen there is a megatec_usb driver, which currently only supports 2 other UPSes. How can I help to find out whether the PowerMust might actually work with the megatec_usb driver? -- Regards,

Hi, Sorry to bother all of you this way, I see no other way at this point. I am trying to get a Siemens Masteguard working and found, by trial and error. Has anyone seen this before? I have the following info: 9600 BAUD 8 bits no parity 1 stop The commands look a lot like the SENA protocol except for the messaging format. It reacts as follows Sending ascii command:

Folks Has anyone any experience with these? http://www.automation.siemens.co.uk/main/business%20groups/power/ups/products/ups%20systems/single%20phase/ http://www.automation.siemens.co.uk/main/business%20groups/power/ups/products/ups%20systems/single%20phase/Siemens%20leaflet%20UPS%20Series%20A.pdf They look a very solid machine, I've got a chance to pick one up for NZ$50 with an extra

Jim Klimov via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> writes: > The opposite opinion is that programs should be quiet until asked to > squeak (e.g. by restarting with higher debug verbosity... "that would help > troubleshooting why the rack went down last week, right!" says the sysadmin > me). That's a fair summary but my opinion is: daemon-type

Jim Klimov via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> writes: > The opposite opinion is that programs should be quiet until asked to > squeak (e.g. by restarting with higher debug verbosity... "that would help > troubleshooting why the rack went down last week, right!" says the sysadmin > me). That's a fair summary but my opinion is: daemon-type

Well, now that the `subdriver` option got added to `usbhid-ups` too, you can at least try that (by building again the current master). See command-line help for the subdrivers it would currently recognize, and copy e.g. the first word as the matching option, e.g.: ./drivers/usbhid-ups -DDDDDD -d1 -s test -x port=auto -x vendorid=... -x productid=... -x subdriver=... and try to lockpick your

--- Arjen de Korte <nut+users at de-korte.org> wrote: > > > I also did: > > > > # ./megatec_usb -DDDDD -x vendor=06da -x mfr=OMRON > > /dev/usb/hiddev0 > > Please have a look at 'man 8 megatec_usb' again. > > You probably need to specify the '-x vendorid' and > '-x productid' options > and most likely, the

--- Arjen de Korte <nut+users at de-korte.org> wrote: > > > I also did: > > > > # ./megatec_usb -DDDDD -x vendor=06da -x mfr=OMRON > > /dev/usb/hiddev0 > > Please have a look at 'man 8 megatec_usb' again. > > You probably need to specify the '-x vendorid' and > '-x productid' options > and most likely, the

Hello There, I tried your advice and i don't think it works either, See the logs, " /tmp/nut# ./drivers/usbhid-ups -DDDDDD -d1 -s test -x port=auto -x vendorid=... -x productid=... -x subdriver=... Network UPS Tools - Generic HID driver 0.52 (2.8.0-2557-g81fca30b2) USB communication driver (libusb 1.0) 0.46 ?? 0.000000??? [D3] main_arg: var='port' val='auto' ??

<facepalm ;)> the ellispis "something=..." were supposed to be replaced by your device ID numbers, etc. On Sat, Sep 23, 2023, 18:26 FatGear <fatgear1 at free.fr> wrote: > Hello There, > > I tried your advice and i don't think it works either, > > See the logs, > > " > > /tmp/nut# ./drivers/usbhid-ups -DDDDDD -d1 -s test -x port=auto -x