-
Notifications
You must be signed in to change notification settings - Fork 39
configuration
arnaudsoullie edited this page Jul 25, 2017
·
2 revisions
To use the DYODE, you need to define a config.yaml
file, and copy it to both the input and the output corner.
Let's say you want to use DYODE to let someone from outside your network access some Modbus/TCP data without the ability to perform any data modification.
The configuration file will be the following
config_name: "Dyode v2"
config_version : 1.0
config_date: 2017-07-25
modules:
"Automate Modbus 1":
type: modbus
port: 9400
ip: 192.168.0.5
port_out: 502
registers:
- 0-105
coils:
- 0-1
- You'll need to add a section for each of the PLC (or let's say Modbus server) that you want to query.
- The port value is not used in DYODE v2, it is only used on DYODE v1 for multiplexing communications.
- The ip is obviously the IP address of the public
- The port_out defines on which port the output counter will instanciate the Modbus server. If you request several devices, make sure that this value is unique for each one.
- Then, simply define which values you want to query. Try to keep it as low as possible to prevent overloading the DYODE.
I also noticed that some ICS software (Schneider IGSS for example) will query a lot of Modbus values, even if they're not used in the application. Take a look at dyode_out.py
and make sure that you'll instantiate enough values for coils and registers.
TO DO This feature only works with DYODE v1 (full)
TO DO This feature only works with DYODE v1 (full)