The same example above (also available at log.yml) can be achieved in YAML with: version : 1 formatters : standard : format : "%(asctime)s %(levelname)8s %(name)s: %(message)s" handlers : console : class : logging.StreamHandler formatter : standard root : handlers : level : DEBUG Credits Development Lead Which mimics the default configuration looks like this: keys = standard keys = console keys = root format = % ( asctime ) s % ( levelname ) 8 s % ( name ) s : % ( message ) s class = StreamHandler formatter = standard level = INFO handlers = consoleĪ more verbose example logging with a rotating file handler: () so the file contents mustĪ simple logging configuration (also available at log.conf) ini file is given, it is passed directly to If a relative path is given, it is relative to the current working directory. Here is a YAML example: devices : - modbus : url : :502 listen : bind : 0:9000 logging : version : 1 formatters : standard : format : "%(asctime)s %(levelname)8s %(name)s: %(message)s" handlers : console : class : logging.StreamHandler formatter : standard root : handlers : level : DEBUG -log-config-file (deprecated) The logging configuration will be passed to Logging configuration can be added to the configuration file by adding a new logging keyword. To publish the corresponding bind port on the host Note that for each modbus device you add in the configuration file you need Here is an example of how to run the container: docker run -p 5020:502 -v $PWD/conf.yml:/src/conf.yml modbus-proxy -c /src/conf.yml If, instead, you want to use a configuration file, you must mount the file soĪssuming you have prepared a conf.yml in the current directory: devices : - modbus : url : :502 listen : bind : 0:502 Now you should be able to access your modbus device through the modbus-proxy by To bridge a single modbus device without needing a configuration file is This project ships with a basic Dockerfile which you can useĪs a base to launch modbus-proxy inside a docker container.įirst, build the docker image with: $ docker build -t modbus-proxy. (notice we are now using port 9000 and not 5020): $ python examples/simple_tcp_client.py -a 0:9000 Start a modbus-proxy bridge server with: $ modbus-proxy -b tcp://:9000 -modbus tcp://:5020įinally run a the example client but now address the proxy instead of the server You can run the example client just to be sure direct communication works: $ python examples/simple_tcp_client.py -a 0:5020 Start the simple_tcp_server.py (this will simulate an actual modbus hardware): $ python examples/simple_tcp_server.py -b :5020
To run the examples you will need to have (hint: run modbus-proxy -help to see all available options) Running the examples Providing all arguments in the command line: modbus-proxy -b tcp://0:9000 -modbus tcp://:502 If you have a single modbus device, you can avoid writting a configuration file by Here is aĬonfiguration example for 2 devices: devices : - modbus : url : :502 listen : bind : 0:9000 - modbus : url : :502 listen : bind : 0:9001 Note that the server is capable of handling multiple modbus devices. Tell them to connect to *machine*:9000 (where machine is the host where Now, instead of connecting your client(s) to :502 you just need to A YAML configuration would look like this: devices : - modbus : url : :502 # device url (mandatory) timeout : 10 # communication timeout (s) (optional, default: 10) connection_time : 0.1 # delay after connection (s) (optional, default: 0) listen : bind : 0:9000 # listening address (mandatory)Īssuming you saved this file as modbus-config.yml, start the server with: $ modbus-proxy -c. Suppose you have a PLC modbus device listening on :502 and you want your clients toĬonnect to your machine on port 9000. listen interface (to which url your clients should connect)Ĭonfiguration files can be written in YAML (.modbus connection (the modbus device url).TOML: pip install modbus-proxy (see below)įirst, you will need write a configuration file where you specify for each modbus device you which to control:.YAML: pip install modbus-proxy (see below).You might need to use pip3 command instead.Īdditionally, if you want logging configuration: Note: On some systems pip points to a python 2 installation.
Installationįrom within your favorite python 3 environment type: When multiple clients are connected, cross messages are avoided by serializing communication on a first come first served REQ/REP basis. This allows multiple clients to communicate with the same modbus device. This proxy acts as a bridge between the client and the modbus device. Many modbus devices support only one or very few clients.
0 kommentar(er)
