search for: libmodbus

Hi! I was wonering if there is a driver that supports communicating with a Modbus aware device over IP. I have a solar/wind invertor that can broadcast its state and I would like to monitor the batteries. If they discarge to a certain voltage or come to a defined state, I would perform a shutdown. All of this information id provided in Modbus holding registers. This could of course be done

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

...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 summary shown after you run the > `configure` script)? > > On Sat...

...simple entry points are welcome) :) In short, you would either have it installed via packaging prepared by your OS distribution maintainers (for `apc_modbus` in particular, you would need at least NUT v2.8.1), or built by yourself - in case of this driver and USB links, also building the custom libmodbus with USB capability, as per Wiki page linked earlier. Specifically in case of this driver and use-case, your best shot is "built by yourself" anyway, since distributions are not likely to ship the libmodbus with USB patches added (they are not merged into upstream code yet). Hope this he...

...networkupstools.org/docs/user-manual.chunked/_build_prerequisites_to_make_nut_from_scratch_on_various_operating_systems.html) should help you get started. Hoping for good news and no blocker issues, Jim Klimov PS: One known problem remains with the recently introduced apc_modbus driver and/or the libmodbus (core or our fork with rtu_usb branch) - that the USB connections tend to fall apart, as tracked at https://github.com/networkupstools/nut/issues/2609 and others linked from it - for now I've exhausted the hardware-less ideas and the time I had; help is welcome. -------------- next part -------...

...networkupstools.org/docs/user-manual.chunked/_build_prerequisites_to_make_nut_from_scratch_on_various_operating_systems.html) should help you get started. Hoping for good news and no blocker issues, Jim Klimov PS: One known problem remains with the recently introduced apc_modbus driver and/or the libmodbus (core or our fork with rtu_usb branch) - that the USB connections tend to fall apart, as tracked at https://github.com/networkupstools/nut/issues/2609 and others linked from it - for now I've exhausted the hardware-less ideas and the time I had; help is welcome. -------------- next part -------...

...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 summary shown after you run the `configure` script)? > > On Sat, Sep 16,...

...n Modbus holding registers. This could of course be done placing a Modbus-to-SNMP gateway but they seem to be somewhat pricey. There is a GitHub issue tracking the general idea of a NUT MODBUS driver: https://github.com/networkupstools/nut/issues/50 The skeleton code on the referenced branch uses libmodbus, which as I understand, can communicate over TCP. However, since you have a specific device in mind, you might be better served by creating a new driver based on the phoenixcontact_modbus driver (which also uses libmodbus): https://github.com/networkupstools/nut/pull/404 and https://github.com/net...

...rs. This could of course be done placing a >Modbus-to-SNMP gateway but they seem to be somewhat pricey. > >There is a GitHub issue tracking the general idea of a NUT MODBUS >driver: https://github.com/networkupstools/nut/issues/50 > >The skeleton code on the referenced branch uses libmodbus, which as I >understand, can communicate over TCP. > >However, since you have a specific device in mind, you might be better >served by creating a new driver based on the phoenixcontact_modbus >driver (which also uses libmodbus): >https://github.com/networkupstools/nut/pull/404 an...

...k. > > 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 summary shown >> after you run the `configur...

...gt; >> 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 summary shown after you run the `configure` script)? >> >...

...which all but deprecated USB HID support. Really, this feature was very long awaited! At the moment the driver is "read-only", with commands and variables to be implemented later (hopefully some coming before 2.8.1 cut-off point). It can be used with the already published and packaged libmodbus versions for Serial-port and TCP support (with add-in network management cards). However please note that USB support is not currently part of the upstream library, but rather is provided by a fork (PR pending). It is not certain whether/when exactly such a feature will appear in the upstream libra...

...which all but deprecated USB HID support. Really, this feature was very long awaited! At the moment the driver is "read-only", with commands and variables to be implemented later (hopefully some coming before 2.8.1 cut-off point). It can be used with the already published and packaged libmodbus versions for Serial-port and TCP support (with add-in network management cards). However please note that USB support is not currently part of the upstream library, but rather is provided by a fork (PR pending). It is not certain whether/when exactly such a feature will appear in the upstream libra...

...e to do it. The simple fact of it is that the > reason no one has done so is that the apcupsd program is available. You're right, it's the microlink protocol that they have been promising to release. My mistake. We even have a branch where Arnaud was starting to write some code against libmodbus. However, the documentation seems to lag the introduction of the new products that all of a sudden don't work with existing software. > I guess the story about the big evil impersonal corporation beating up on the small OSS software project is more compelling than the reality that the big c...

...ual.chunked/_build_prerequisites_to_make_nut_from_scratch_on_various_operating_systems.html) > should help you get started. > > Hoping for good news and no blocker issues, > Jim Klimov > > PS: One known problem remains with the recently introduced apc_modbus > driver and/or the libmodbus (core or our fork with rtu_usb branch) - that > the USB connections tend to fall apart, as tracked at > https://github.com/networkupstools/nut/issues/2609 and others linked from > it - for now I've exhausted the hardware-less ideas and the time I had; > help is welcome. > -------...

...ual.chunked/_build_prerequisites_to_make_nut_from_scratch_on_various_operating_systems.html) > should help you get started. > > Hoping for good news and no blocker issues, > Jim Klimov > > PS: One known problem remains with the recently introduced apc_modbus > driver and/or the libmodbus (core or our fork with rtu_usb branch) - that > the USB connections tend to fall apart, as tracked at > https://github.com/networkupstools/nut/issues/2609 and others linked from > it - for now I've exhausted the hardware-less ideas and the time I had; > help is welcome. > -------...

...: on IPMIPSU : off MANPAGES : on MODBUS : on NEON : on NSS : off OPENSSL : on PDU : on SERIAL : on SNMP : on SSL_OFF : off USB : on Shared Libs required: libpowerman.so.0 libnetsnmp.so.40 libneon.so.27 libmodbus.so.5 libltdl.so.7 libgd.so.6 Shared Libs provided: libupsclient.so.6 libnutscan.so.2 libnutclientstub.so.1 libnutclient.so.2 Annotations : FreeBSD_version: 1400097 build_timestamp: 2024-06-11T10:20:37+0000 built_by : poudriere-git-3.4.1-30-g79e3edcd port_checkout_unclean: no port_git_hash...

...;> of it is that the reason no one has done so is that the apcupsd >> program is available. > > You're right, it's the microlink protocol that they have been > promising to release. My mistake. We even have a branch where Arnaud > was starting to write some code against libmodbus. Why don't you just lift all the APC modbus code from the modbus module in apcupsd? The work is already done there. > However, the > documentation seems to lag the introduction of the new products that > all of a sudden don't work with existing software. > The Modbus doc for...

...on > NEON : on > NSS : off > OPENSSL : on > PDU : on > SERIAL : on > SNMP : on > SSL_OFF : off > USB : on > Shared Libs required: > libpowerman.so.0 > libnetsnmp.so.40 > libneon.so.27 > libmodbus.so.5 > libltdl.so.7 > libgd.so.6 > Shared Libs provided: > libupsclient.so.6 > libnutscan.so.2 > libnutclientstub.so.1 > libnutclient.so.2 > Annotations : > FreeBSD_version: 1400097 > build_timestamp: 2024-06-11T10:20:37+0000 > built_by : poudriere-git-3.4....

Got an update for APC Modbus users: a new PR is waiting for real-life testing for settable variables and instant commands support. https://github.com/networkupstools/nut/pull/2184 As before, a custom build of libmodbus may be needed for USB support (detailed in the earlier PR), but Serial and TCP may already be well served by a distro near you! Jim On Sun, Oct 22, 2023, 01:08 Jim Klimov <jimklimov+nut at gmail.com> wrote: > Hello fellow NUTs :) > > It is my great pleasure to get a bit of sunsh...