-
-
Notifications
You must be signed in to change notification settings - Fork 362
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
modbus_connect: unable to connect: No such device when trying to connect apc_modbus via tcp #2757
Labels
APC
impacts-release-2.8.2
Issues reported against NUT release 2.8.2 (maybe vanilla or with minor packaging tweaks)
modbus
question
Comments
When i run i get the following output:
so it looks like it is reading some information from a different config file? |
Seems so. Which |
Oh yes because of the custom build driver i edited the wrong ups.conf |
jimklimov
added
question
APC
modbus
impacts-release-2.8.2
Issues reported against NUT release 2.8.2 (maybe vanilla or with minor packaging tweaks)
labels
Jan 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
APC
impacts-release-2.8.2
Issues reported against NUT release 2.8.2 (maybe vanilla or with minor packaging tweaks)
modbus
question
I am coming from this issue #2732
I am now trying to connect to the ups via tcp modbus. If i start the driver manually with:
sudo ./apc_modbus -DDDDD -s apc -x vendorid=051D -x productid=0003 -x porttype=tcp -x port=192.168.11.131 -x user=root
the driver starts reading out all the information correctly.
But
sudo upsdrvctl start
fails with 'modbus_connect: unable to connect: No such device'.my ups.conf:
when i start the driver manually with
sudo ./apc_modbus -a USV2
also themodbus_connect: unable to connect: No such device
error occurs.The text was updated successfully, but these errors were encountered: