Versions Compared

Old Version 3

changes.mady.by.user admin

Saved on

compared with

New Version 4

changes.mady.by.user admin

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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.


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 Learn

  • Configure communication channels
  • Add device nodes
  • Map device addresses to tags
  • Monitor communication status

Prerequisites

  • Completed "Add Tags to UNS" tutorial
  • Understanding of basic communication concepts

Step 1: Create Channel

  1. Navigate to Devices → Channels
  2. Add new channel:
    • Name: ModbusChannel
    • Protocol: Modbus Master
    • Settings:
      • Interface: TCP/IP
      • Port: 502
      • Timeout: 3000ms

Step 2: Add Device Node

  1. Go to Devices → Nodes
  2. Create node:
    • Name: PLC1
    • Channel: ModbusChannel
    • Station: IP Address (use 127.0.0.1 for simulator)
    • Device ID: 1

Step 3: Create Device Points

  1. Navigate to Devices → Points
  2. Add points:

Digital Input:

  • Name: PLC1_DI_001
  • Node: PLC1
  • Address: 10001 (Modbus coil)
  • Data Type: Digital

Analog Input:

  • Name: PLC1_AI_001
  • Node: PLC1
  • Address: 30001 (Modbus input register)
  • Data Type: Integer
  • Scaling: Enable if needed

Step 4: Map to Tags

Method 1 - Direct Mapping:

  1. Go to Unified Namespace → Tags
  2. Select existing tag
  3. In Device column, select: PLC1_AI_001

Method 2 - Auto-create Tags:

  1. In Devices → Points
  2. Select points
  3. Right-click → Create Tags
  4. Tags created with same names

Step 5: Test Communication

  1. Start Runtime (F5)
  2. Open Devices → Monitor
  3. Check status:
    • Green = Connected
    • Red = Error
    • Yellow = Timeout

Step 6: Troubleshooting

IssueCheck
No connectionFirewall, IP address, port
Wrong valuesAddress offset, data type
IntermittentTimeout settings, network
No updatesPolling rate, scan groups

Using Device Simulator

For testing without real hardware:

  1. Devices → Tools → Simulator
  2. Select protocol matching your channel
  3. Start simulator
  4. 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

...