search for: fatgear

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 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 s...

...bmodbus` 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 i'm doing wrong but it seams that is not working, > > I tried to put and remove id but it's not fonctioning, > > /etc/nut/ups.conf > > " > > pollinterval = 1 > maxretry = 3 > >...

...your way here. On a side note, some long-awaited tinkering began on making an APC modbus driver a reality, but so far it is in such early stages that it relies on an unpublished version of the modbus library so is not trivial to even build (or get packaged). Jim On Tue, Sep 19, 2023 at 9:13?PM FatGear <fatgear1 at free.fr> wrote: > 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,...

<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 > vendorid=... -x productid=... -x subdriver=... > N...

...39; val='...' Fatal error: 'vendorid' is not a valid variable name for this driver. Look in the man page or call this driver with -h for a list of valid variable names and flags. ?? 0.000163??? [D5] send_to_all: SETINFO driver.state "cleanup.exit" " Best regards, FatGear Le 19/09/2023 ? 21:40, Jim Klimov a ?crit?: > 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 w...