IO754 - Setup v2
IO754 - Setup v2 — Configure the IO754 I/O
module
Library
Simulink Real-Time - Speedgoat

Description
Your model can contain only one Setup block
for each I/O module in your target machine.
Ports
This driver block has no input or output ports.
Parameters
Tab: Configuration
- Module ID
The Module ID has two functions:
It logically connects the Setup block and its I/O blocks
It also informs the auto-search feature of the PCI Slot parameter. If only
one I/O module of this family is installed, the Module ID must be set to
1. To see how each I/O module maps to a
Module ID, use this Speedgoat API:
speedgoat.getIoInterfaces("TargetName", "mySpeedgoat")
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.
IO64X/IO75X (single-node modules): IO641,
IO642, IO643, IO644, IO750, IO751, IO752, IO753, IO754, IO755, IO756,
IO758
IO64X-32/IO75X-32 (multi-node modules):
IO642-32, IO752-32, IO754-32, IO756-32
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]](images/note.png) | 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. |
-
Configuration Mode
![[Note]](images/note.png) | Note |
|---|
This parameter is obsolete and will be removed. Please always
select Warmstart. |
-
PCI Slot (-1: auto-search)
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.
- Auto-Search: with the default value -1 the I/O module will be
automatically located in the target machine. If you have
multiple modules of the same family, the Module ID (first
vector element for a multi-node module) defines which module
is associated with this block. To see how each I/O module
maps to a Module ID, use this Speedgoat API:
speedgoat.getIoInterfaces("TargetName", "mySpeedgoat") - Explicit Addressing: to explicitly define the logical
address of the I/O module in the target machine, you can
provide the PCI bus and slot numbers as a vector: [bus,
slot]. To determine these numbers, run the following command
in the MATLAB command window:
speedgoat.getIoInterfaces("TargetName", "mySpeedgoat", "Advanced", true)Note
that the PCI address can change whenever an I/O module is
added or removed. Usually, auto-search is the best option.
Tab: Warmstart
-
Operation Mode
Please refer to the chapter about the operation modes in the
Usage Notes for further information.
-
Bus Startup
Communication starts:
-
Data Swap
Data storage mode:
This parameter determines whether register data will be
swapped between the application context and network transportation or
not. The swap option is valid for both directions: sending and
receiving. This means that if the swap option is enabled, the register
values from the application context will be swapped before they are sent
to the network. All the register values received from the network will
be swapped before they are submitted to the application context. The
register values of Open Modbus/TCP are usually specified in MSB format.
The applications, however, in most cases are in LSB format.
-
Map FC1 and FC3
If set, the function codes FC1 and FC3 are mapped to the TX data area
of the dual-port memory instead of to the RX data area.
![[Note]](images/note.png) | Note |
|---|
Only available in IO mode |
-
Provided Server Connections
Maximum number of ModbusTCP clients allowed to connect to the present
server module: 1 to 16
-
IP Address
Only available if "BootP" and "DHCP" are not set.
-
Netmask
Only available if "BootP" and "DHCP" are not set.
-
Gateway
Only available if "BootP" and "DHCP" are not set.
-
BootP
If set, the device obtains its IP Address, Netmask and Gateway Address
from a BOOTP server.
-
DHCP
If set, the device obtains its IP Address, Netmask and Gateway Address
from a DHCP server.