Documentation search search close
CONTENTS
https://www.speedgoat.com/help/slrt/page/icon_documentation.jpg
v10.0.1.x for R2026a
View other versions

IO756 - Setup

IO756 - Setup — Configure the IO756 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

Configuration-Tab
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]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]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.
Warmstart-Tab
Input Instance-ID

Instance-ID of the communication point for input data (Target to Originator direction)

Input Data Length

Data length in byte should be in the range 0…504

RT transfer format (Input)

Available settings are: "Connection is pure data and modeless" or "32-bit run/idle header" and should correspond to the settings of Ethernet/IP Scanner.

Output Instance-ID

Instance-ID of the communication point for output data (Originator to Target direction)

Output Data Length

Data length in byte should be in the range 0…504

RT Transfer Format (Output)

Available settings are: "Connection is pure data and modeless" or "32-bit run/idle header" and should correspond to the settings of Ethernet/IP Scanner.

Enable BOOTP

If enabled, the device tries to obtain its IP configuration from a BOOTP server.

Enable DHCP

If enabled, the device tries to obtain its IP configuration from a DHCP server.

IP Address

IP Address (if neither BOOTP nor DHCP is selected)

Network Mask

Network mask (if neither BOOTP nor DHCP is selected)

Gateway

Gateway Address (if neither BOOTP nor DHCP is selected)

Warmstart Device Info-Tab
Vendor ID

Vendor identification: This is an identification number for the manufacturer of an EtherNet/IP device. The value 0 is not valid.

CIP Device Type (Product Type)

CIP Device Type. It is used to identify the device profile that a particular product is using. Device profiles define minimum requirements a device must implement as well as common options.

Product Code

The vendor assigned Product Code identifies a particular product within a device type. Each vendor assigns this code to each of its products.

Serial Number

This parameter is a number used in conjunction with the Vendor ID to form a unique identifier for each device on any CIP network.

Minor Revision

Minor revision number of the simulated device

Major Revision

Major revision number of the simulated device

Device Name

This text string should represent a short description of the product/product family represented by the product code.

The parameters Vendor ID, Product Type, Product Code, Minor revision and Major revision can be used from Ethernet/IP Scanner for "electronic keying". If "electronic keying" was configured for exact match, then all this parameters of the adapter match with the configuration of the scanner. It is also possible, that scanner checks some of this parameters before establishing the communication.