Hi all
I’m getting these errors in docker logs when running the container - container keeps trying to restart.
Does anybody know why?
Thank you
Best
Chris
PORT: 502
MAX CONNECTIONS: 5
OPERATION MODE: 0
MODBUS DELAY MS: 0
KBUS CYCLE TIME MS: 50
KBUS PRIORITY: 60
start init daemons
dip-switch not found in /sys/devices/
INFO: PROFIBUS DP device “UIO_DPC31_XINT” not available
start kbusmodbusslave
verbosity level is 7
Not running in background
kbusmodbusslave running…
ADI Device[0]: libpackbus
Found kbus device on: 0
Modbus: Wait for KBUS to be initialized
KBUS open device failure.
Failed to start KBUS thread!
Have you disabled the runtime ?
Is the K-bus properly running (end module present, etc…) ?
runtime is disabled, yes
we use Controller Type 751-9301 without KBUS
docker container cannot run without KBUS?
Docker can run without K-Bus, but you are using pfc-modbus-server.
As its name says, this container is made to provide kbus IO’s to Modbus server on a PFC.
It has no purpose on CC100.
What do you want to do ? Provide IO’s to Modbus or to another Containerized application ?
You might be interested in the following link :
This could easily be done using CODESYS as well !
2 Likes
Thank you for the links.
We would like to use RS485 (X11) interface on CC100 (751-9101) as Modbusmaster and read the attached energy counters (879-3020) using the Modbus interface.
Well in this case forget about pfc-modbus-server.
Here is a Node-RED example for what you want to do :
And an dashboard example :
thank you, I’ll have a look
do you also know about doing this in pure python?
I’ve only used PyModbus for TCP communication but it looks it can handle serial communication as well. You should mount the /dev/tty serial port like it’s done in the Node-RED example.