Siemens SoftNet I/O configuration

The workbench includes a fully integrated configurator for Profibus I/Os using Siemens' SoftNet package. Please refer to the following topics in that page for detailed information on how to use and configurate SOFTNET I/Os:

Data exchange
Data types

Data exchange - configuration:

The T5 runtime manages a intermediate variable map representing SOFTNET/Profibus inputs and outputs. A dedicated configuration tool is integrated in the Workbench. Run it using the "File / Open / Fieldbus Configuration" menu command from the main window. Then add the "SoftNet Profibus DP" configuration.

The configuration is represented as a tree:

- SoftNet configuration
  - SoftNet Board (*)
    - Slave (*)
      - exchanged Variable (*)

(*) The items with this mark can appear several times in the configuration.


You need to configurate the networks in order to map I/Os to variables. A SoftNet Board is identified by its board identifier (CP_L2_1 to CP_L2_4) and a free description text.

Each slave is identified by its Profibus DP slave number.

For each linked variable you have to enter:

- its symbol
- an offset (in SoftNet board)
- a mode (input or output or diagnostic)
- a data format on the SoftNet board
- possibly a bit number for a single bit data


Below are the diagnostic reports you can map to variables:







The DP slave is not activated the local database



The DP slave is not in the data transfer phase (CP startup).



The DP slave is in the data transfer phase

Ready Diagnostic


The DP slave is in the data transfer phase, and diagnostic data exist.

















Bit 7 : Diag. Master_Lock: The DP slave has already been assigned parameters by another master, in other  words the local master does not currently have access to this slave.

Bit 6 : Diag. Prm_Fault: This bit is set by the DP slave if the last parameter assignment frame was incorrect (for example wrong length, wrong ident number, invalid parameters).

Bit 5 : Diag. Invalid_Slave_Response: This bit is set as soon as an implausible response is received from an addressed DP slave.

Bit 4 : Diag. Not_Supported: This bit is set whenever a function is requested that is not supported by the particular slave (for example the SYNC mode is requested although the slave does not support this mode).

Bit 3 : Diag. Ext_Diag: This bit is set by the DP slave. If the bit is set, there must be a diagnostic entry in the slave-specific diagnostic area (Ext_Diag_Data). If the bit is not set, there may be a status message in the slave-specific diagnostic area (Ext_Diag_Data). The meaning of the status message must be negotiated with each specific application.

Bit 2 : Diag. Cfg_Fault: This bit is set when the configuration data last sent by the master do not match those determined by the DP slave, in other words when there is a configuration error.

Bit 1 : Diag. Station_Not_Ready: This bit is set when the DP slave is not yet ready for productive data exchange.

Bit 0 : Diag. Station_Non_Existent: This bit is set by the DP master if the DP slave cannot be reached via the bus. If this bit is set, the diagnostic bits contain the status of the last diagnostic message or the initial value. The DP slave always sets this bit to zero.


Bit 7 :  Diag. Deactivated: This bit is set when the DP slave is marked as inactive in the local parameter data record and has been taken out of cyclic processing.

Bit 6 : reserved

Bit 5 : Diag. Sync_Mode: This bit is set by the DP slave as soon as it receives the sync control command.

Bit 4 : Diag. Freeze_Mode: This bit is set by the DP slave as soon as it receives the freeze control command.

Bit 3 : Diag. WD_On (Watchdog on): This bit is set by the DP slave. If this bit is set to 1, the watchdog monitoring is activated on the DP slave.

Bit 2 : The DP slave always sets this bit to 1.

Bit 1 : Diag.Stat_Diag (static diagnostics): If the DP slave sets this bit, the DP master must fetch diagnostic information and continue to fetch it until the bit is cleared again. The DP slave, for example, sets this bit when it is not capable of providing valid user data.

Bit 0 : Diag. Prm_Req: If the DP slave sets this bit, it requires a new parameter assignment and must be reconfigured. This bit remains set until the slave has had parameters assigned to it.

Note: If bit 1 and bit 0 are set, bit 0 has the higher priority.


Bit 7 : Diag. Ext_Diag_Overflow: If this bit is set, there is more diagnostic information than specified in Ext_Diag_Data. The DP slave sets this bit, for example, when there is more channel diagnostic data than the DP slave can enter in its send buffer. The DP master also sets this bit when the DP slave sends more diagnostic data than the DP master can accommodate in its diagnostic buffer.

Bit 6 to 0 : Reserved

Diag. Master_Add

The address of the DP master that assigned parameter to this DP slave is entered in byte 4, the "Diag.Master_Add“ byte. If the DP slave has not been assigned parameters by a DP master, the DP slave sets the address 255 in this byte.

Bytes 5 and 6 Ident_Number

The vendor ID for a DP slave type is assigned in bytes 5 and 6, the "Ident_Number“ byte. This identifier can be used on the one hand for test purposes and on the other for precise identification of the slave.

Data types:

You can freely map a variable of any data type to an I/O. The runtime automatically converts the value to the type of the variable. STRING variables are not supported.