FrameworX PLCs and field devices to acquire real-time data. This tutorial uses simulated Modbus device, but the concepts apply to all protocols.Overview
Connect FrameworX to PLCs and field devices to acquire real-time data. This tutorial uses a simulated Modbus device, but the concepts apply to all protocols.
What You'll LearnThis Tutorial Teaches you to:
- Configure communication channels
- Add device nodes
- Map device addresses to tags
- Monitor communication status
Prerequisites
Completed " Table of Contents |
---|
maxLevel | 2 |
---|
minLevel | 2 |
---|
indent | 10px |
---|
exclude | Teaches |
---|
style | none |
---|
|
1. Create Device
" tutorialUnderstanding of basic communication conceptsStep 1: Create Channel
- Navigate to Devices → ChannelsProtocols
- Select Modbus
- Click on New Add new channel:
- Channel Name:
ModbusChannel
- Protocol:
Modbus Master
Settings:Protocol
- Interface: TCP/IP
- Port: 502
- Timeout: 3000ms
Step 2:
2. Add Device Node
- Go to Devices → Nodes
- Create node:
- Name:
PLC1
- Channel:
ModbusChannel
- Station: IP Address (use 127.0.0.1 for simulator)
- Port 502
- Device ID: 1
Step
3
: . Create Device Points
- Navigate to Devices → Points
- Add points:
Digital Input:
- Tag Name:
PLC1_DI_001
TankFarm/Tank1/Level
- Node:
PLC1
- Address:
10001
(Modbus coil) 40001
- Data Type: Native
- AccessType: DigitalReadWrite
Analog Input:
- Name:
PLC1_AI_001
TankFarm/Tank2/Level
- Node:
PLC1
- Address:
30001
(Modbus input register) 40002
- Data Type: IntegerNativeScaling
- AccessType:
Enable if needed- ReadWrite
Method 1 - Direct Mapping:
- Go to Unified Namespace → Tags
- Select existing tag
- In Device column, select:
PLC1_AI_001
Method 2 - Auto-create Tags:
- In Devices → Points
- Select points
- Right-click → Create Tags
- Tags created with same names
4. Starting Modbus Device Simulator
- Devices → Channels
- Select ModbusChannel
- Run Modbus Simulator
5.
Step 5: Test Communication
- Start Runtime (F5)
- Open Devices → Monitor
- Check status :
- Green = Connected
- Red = Error
- Yellow = Timeout
Step 6: Troubleshooting
Issue | Check |
---|
No connection | Firewall, IP address, port |
Wrong values | Address offset, data type |
Intermittent | Timeout settings, network |
No updates | Polling rate, scan groups |
Using Device Simulator
For testing without real hardware:
- Devices → Tools → Simulator
- Select protocol matching your channel
- Start simulator
- Values update automatically
Best Practices
- Test with simulator first
- Use meaningful point names
- Group related points
- Set appropriate scan rates
- Document address mapping
Next Steps
[Connect to a PLC] - Specific PLC brands[Define Alarms] - Alarm on device values[Historian] - Log device data- (if the ActivityCounter is increasing and LastErrorCode stays fixed, it means everything is running properly)