IO-Link Data Collection
There is no adapter script to write and no port to enter. MachineMetrics asks for the master block's IP address, then discovers the attached sensors from their IODD files and names the data items automatically.
Automatic Configuration
In most cases, the IO-Link integration will automatically configure itself based on IODD (IO Device Description) files.
Step 1: Add Machine in MachineMetrics
- Log into MachineMetrics at app.machinemetrics.com
- Navigate to Assets → Machines
- Click Add Machine
- Enter machine/sensor details:
- Name: (e.g., "Hydraulic-Press-Sensors" or "Assembly-Station-01")
- Type: (Select appropriate type or "Sensor Station")
- Click Next
Step 2: Select IO-Link Integration
- In Data Collection Method, select IO-Link or IFM IoT
- If not visible, contact MachineMetrics support
Step 3: Enter Master Block IP Address
- Enter the IFM master block's IP address (e.g., 192.168.1.150)
- The connector will automatically discover connected sensors
Step 4: Save and Test
- Click Test Connection
- MachineMetrics will:
- Connect to the master block
- Discover connected sensors
- Automatically create data items for each sensor
- If successful, click Save
Note: The IO-Link connector automatically discovers and configures sensors. No manual adapter script configuration is required.
Data Item Naming Convention
Automatically-configured sensors produce data items with a specific naming structure:
Format:
iolink_p<n>_<vendorid>_<deviceid>_<subindex>_<shortname>
Components:
<n>- Port number (1-8 or 1-4, depending on master block)<vendorid>- Manufacturer's vendor ID<deviceid>- Specific device/model ID<subindex>- Data item index within sensor's process data (starts at 1)<shortname>- Truncated, processed display name for identification
Example: IFM Humidity Air Sensor
IFM humidity/temperature sensor (Vendor ID: 310, Device ID: 1337) connected to Port 2:
iolink_p2_310_1337_1_humidity
iolink_p2_310_1337_2_temperature
iolink_p2_310_1337_3_devicestatus
Explanation:
p2- Connected to Port 2310- IFM vendor ID1337- Humidity sensor device ID1,2,3- Sub-indexes for different measurementshumidity,temperature,devicestatus- Shortened names
Data Transformation
The IO-Link connector uses automatic sensor discovery and configuration. Manual configuration of process data, bit offsets, gradients, and offsets is not required.
If you need to transform or manipulate the IFM data items to solve your specific use case, use transform adapter scripts to process the automatically discovered data items.
See the Adapter Scripts reference for information on:
- Renaming data items
- Applying mathematical transformations
- Combining multiple data items
- Creating custom variables from sensor data
Data Mapping
Step 1: Verify Data Collection
- Navigate to machine page in MachineMetrics
- Go to Diagnostics tab
- Verify data items are populating with values
- Check data item names match expected format
Step 2: Configure Data Mapping
- Go to Machine Settings → Data Mapping tab
- Map IO-Link data items to MachineMetrics data types:
Example Mappings:
| IO-Link Data Item | MachineMetrics Type | Subtype |
|---|---|---|
iolink_p1_310_1337_1_humidity | SAMPLE | Custom (Humidity %) |
iolink_p1_310_1337_2_temperature | SAMPLE | TEMPERATURE |
iolink_p2_310_2001_1_pressure | SAMPLE | PRESSURE |
iolink_p3_310_2500_1_flow | SAMPLE | Custom (Flow Rate) |
- Set appropriate Component (Machine, Coolant, Hydraulic, etc.)
- Add display names if needed
- Click Save
Step 3: Configure Units (If Needed)
- Note the units for each sensor from datasheet
- Include units in display names if not automatically included
- Example: "Coolant Temperature (°C)" or "Hydraulic Pressure (bar)"
Step 4: Set Up Alerts (Optional)
- Navigate to Automations
- Create alerts based on sensor thresholds:
- High temperature warnings
- Low pressure alerts
- Vibration limit notifications
Related Articles
- Master Block Setup — the block needs its static IP first
- Adapter Scripts — transforming the discovered data items
- Troubleshooting — when values are missing or wrong