IO754 - Setup
IO754 - Setup — Configure the IO754 IO
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. |
-
Target Machine Drive Letter
The drive letter of your target machine where the firmware and configuration files
will be stored. The default drive is "C:\".
![[Note]](images/note.png) | Note |
|---|
This parameter serves no purpose in MATLAB R2020b and later. |
-
Configuration Mode
This setting is not yet available.
-
Sample Time
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.
![[Caution]](images/caution.png) | Caution |
|---|
All blocks that interface with the same I/O module must have identical
sample times. |
-
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 (Interface)
-
Bus Startup
Communication starts
automatically
application controlled
-
Watchdog Time
Within that time the device watchdog must be retriggered from the
application program while the application program monitoring is
activated. To deactivate the application program monitoring, set
Watchdog time to 0. This function is not supported by gateway or proxy
devices.
-
Protocol Mode
Mode of data exchange (parameter is disabled):
-
Data Swap
Data-storage mode:
-
Map FC1 and FC3
Checked: Data is read from the output area using FC1, FC3 and FC23.
FC1 then can be used instead of FC2, and FC3 instead of FC4. Unchecked:
Data is read from the input area using FC1, FC3 and FC23.
Tab: Warmstart (Bus)
-
Provided Server Connections
Number of sockets to provide for server requests.
Value 0: Modbus/TCP task exclusively works as TCP
Client
Value 16: Modbus/TCP task exclusively works as Server in
the Message-Mode
Value 4 (default): 4 Server connections provided (Then
still up to 12 TCP client connections are available)
The parameters "Send Acknowledgement Timeout", "Connect
Acknowledgement Timeout" and "Close Acknowledgement Timeout" are for the
timeout between the Modbus/TCP Task and the TCP Task.
-
Client Connection Watchdog Time
Only applicable for client jobs in Message Mode (packet mode). The
connection to the destination-device stays open, until this timeout has
expired. Note: This timeout begins after receiving the answer to a
command Default value: 1000 ms [Range: 100 … 6,000,000 ms]
-
Response Timeout
Only applicable for client jobs in Message Mode (packet mode). After
expiration of this time, the job will be canceled and an error sent to
the application. Note: This timeout begins after a command is sent to
the destination device via TCP. Default value: 2,000 ms [Range: 1 ...
6,000,000 ms]
-
Send Acknowledgment Timeout
Specifies the timeout for trying to send messages via TCP/IP (Value 0
corresponds to default value of 31,000 milliseconds)
-
Connect Acknowledgment Timeout
Specifies the timeout for trying to establish a connection with the
TCP task. (Value 0 corresponds to default value of 31,000 milliseconds)
-
Close Acknowledgment Timeout
Specifies the timeout for trying to close a connection with the TCP
task. (Value 0 corresponds to default value of 13,000 milliseconds)
-
IP Address
Sets the IP address manually, only available if "BootP" and "DHCP" are
unchecked.
-
Netmask
Sets the net mask manually, only available if "BootP" and "DHCP" are
unchecked.
-
Gateway
Set the gateway address manually, only available if "BootP" and "DHCP"
are unchecked.
-
BootP
Checked: The device obtains its IP Address, Netmask, Gateway Address
from a BOOTP server. Unchecked: Values are set manually
-
DHCP
Checked: The device obtains its IP Address, Netmask, Gateway Address
from a DHCP server. Unchecked: Set values manually