Documentation

The Module ID has two functions:

This Setup block belongs to two families of I/O modules that use the same hardware for multiple protocols. Across both families, the Module ID must be unique.

If the PCI Slot parameter is set to -1 (auto-search), the Module ID must be in the range 1:n, where 'n' cannot be larger than the number of modules of this type installed in the target machine. Not all installed I/O modules need to be used.

To use this Setup block with a multi-node I/O module (IO75X-32 family), the Module ID must be defined as a two-element vector. The second vector element is the sub-module ID. It describes the specific node (1:32) within the I/O module. The 32 nodes are internally connected to form two linear networks (daisy-chain), where the first and the last node of both chains are externally accessible. If one node is not configured (has no Setup block), the chain terminates at this point. The sub-module IDs must therefore start at node 1, 16, 17 or 32 and not have any gaps.

	Note
	When using I/O modules of both families simultaneously (single-node and multi-node I/O modules), always use explicit addressing in the PCI Slot parameter. Ignore the Module IDs returned by the getIoInterfaces function and instead assign unique Module IDs accross all modules used.

Select Configuration file to use the configuration files generated with SYCON.net. Use Warmstart to configure the I/O module by the block mask parameters completely.

The drive letter of your target machine where the firmware and configuration files will be stored. The default drive is "C:\".

	Note
	This parameter serves no purpose in MATLAB R2020b and later.

Defines the base sample time at which this driver block gets its sample hit. This parameter can also be set to -1 for inherited sample time. The units are in seconds.

There are two approaches for mapping the block to a specific I/O module installed in your target machine. All modules of the same family (see Module ID above) must be configured using the same method.

0x0000…0xFFFF

The identification number of the slave that is reported to the DPMaster. This number is unique for each slave device as it is uniquely assigned by the Profibus Trade Organization. When the default value 0x0000 applies, the card firmware uses ident number 0xB756 (CIFX DP/DPS Hilscher GmbH).

If you emulate a certain device use the value of property Ident_Number of the related GSD file.

If set, the slave stack does not support the "Set Slave Address" command.

Network station address: 2…126

Available values: 9.6 kBit/s-1.5 Mbit/s and auto-detect.

If set, you do not need to set the module configuration of the slave. The stack takes over the module configuration from the Chk_Cfg telegram received from the master.

See examples below.

If set, DPV1 functions are activated.

If you emulate a certain device please look at the property DPV1_Slave in the related GSD file. Enable DPV1 support in case the property value is 1.

If set, the slave stack supports the SYNC command and the SYNC mode is activated.

If you emulate a certain device please look at the property Sync_Mode_supp in the related GSD file. Enable SYNC support in case the property value is 1.

If set, the slave stack supports the FREEZE command and the FREEZE mode is activated.

If you emulate a certain device please look at the property Freeze_Mode_supp in the related GSD file. Enable FREEZE support in case the property value is 1.

Set to activate FAILSAFE mode.

If you emulate a certain device please look at the property Fail_Safe in the related GSD file. Enable FAILSAFE support in case the property value is 1.

If set, the slave stack expects alarm acknowledges from the master at service access point 51.

If not set, the slave stack expects alarm acknowledges from the master at service access point 50.

If you emulate a certain device please look at the property Extra_Alarm_SAP_supp in the related GSD file. Disable ALARM SAP support in case the property value is 0 or the GSD file does not contain the property.