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.

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.

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.

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.

Profinet uses a name-based station addressing method. The name must be unique in the network and must match the name of the related device node in the Profinet controller configuration.

	Note
	The length of the name is limited to 127 characters. The name must not contain uppercase letters. The only special characters allowed are hyphens and periods. The name must begin with a letter.

The ID can be found in the ProfileBody/deviceIdentity section of the device-related GSDML file. The Vendor ID must match the Vendor ID of the related device node in the Profinet controller configuration.

	Note
	The Vendor ID must be a decimal number. You can use hex2dec() to convert a hexadecimal number to a decimal number.

The ID can be found in the ProfileBody/deviceIdentity section of the related device description file (GSDML). The device ID must match the device ID of the related device node in the Profinet controller configuration.

	Note
	The device ID must be a decimal number. You can use hex2dec() to convert a hexadecimal number to a decimal number.

This parameter must match the ObjectUUID_LocalIndex value in the related device description file (GSDML).

A Profinet device consists of logical APIs, slots and subslots. The pluggable modules and sub-modules of the device are listed in the related device description file (GSDML). The communication between controller and device is based on a configured subset of these modules. The module configuration of a device must match the module configuration of the related device node in the Profinet controller configuration.

The slot/module configuration edit field expects a n-by-7 matrix. Each submodule is represented by one row and must contain the following items:

[API, slot, subslot, module, submodule, input length, output length]

	Tip
	Refer to Configuration Example for information on how to use this parameter.

	Caution
	This parameter is obsolete. Instead, use the IO752 Record block to define records.

As described in the previous block parameter, a sub-module contains data which can be cyclically read and written by the PROFINET controller. A sub-module can also contain acyclic data. A subset of these so-called RECORDs is listed in the related GSDML file. Navigate to a SubmoduleItem and you will find a RecordDataList containing ParameterRecordDataItems. For the correct configuration of the device, you require the Index and Length attributes. The Data attribute contains the default value of the record. This subset of records, which is part of the GSDML file, is written once by the controller when the connection is being established. While the communication is running, the controller can read/write additional records which do not need to be part of the GSDML. Note that you can only define records whose sub-modules are part of the Slot/Module Configuration. Slots and subslots defined in the Record/Parameter Configuration must be part of the Slot/Module Configuration as well.

The Record/Parameter Configuration edit field expects a n-by-5 cell array. Each record is represented by one row and must contain the following items:

{slot, subslot, index, access mode, default value; ...

 slot, subslot, index, access mode, default value}