Runtime Tutorial

Runtime → Tutorial | Concept | How-to Guide | Reference

1. Start Runtime in Development Mode

Quick Test from Designer

1. Open MyFirstSolution in Designer (if not already open)
2. Go to Runtime → Startup
3. Make sure that under "ExecutionProfile" the option Development is checked
4. Observe startup sequence:
   • TServer Startup...
   • Process starting...
   • Connecting to server...
   • Server Started Successfully
   • Starting modules...

Stop Runtime

• Click Stop button in the Designer → Runtime → Startup
• Wait for clean shutdown
• Once the shutdown is complete, the "Run Startup" button will be available again

2. Explore Execution Profiles

View Available Profiles

1. Go to Runtime → Execution Profiles
2. See three default profiles:
   • Development 
   • Validation 
   • Custom

3. Monitor Runtime Status

Start Full Runtime

1. Go to Runtime → Startup
2. Ensure Development profile selected
3. Click Run Startup
4. Watch startup progress

Check Module Status

On the TStartup display, observe which modules are running:

Monitor Resources

Note the real-time metrics:

• Memory Usage: ~50-100 MB (typical)
• CPU: < 5% (idle)
• Uptime: Counting from startup
• Connected Clients: 0 (none yet)

4. Use Property Watch (3 min)

Open Property Watch

1. Click Runtime → Diagnostics
2. Select Property Watch
3. New window opens

Browse Runtime Objects

Navigate the object tree:

1. Expand Tag node
2. Find your tags (Tag1, Tag2, Tag3)
3. Double-click Tag1
4. View properties:
   • Value: Current value
   • Quality: Good/Bad
   • Timestamp: Last update

Modify a Value

Test runtime write:

1. Select Tag1.Value
2. Enter new value: 50
3. Press Enter
4. Observe value changes
5. Note timestamp updates

5. Apply Online Changes (3 min)

Make a Change in Designer

While runtime is running:

1. Return to Designer (keep runtime active)
2. Go to Unified Namespace → Tags
3. Add a new tag: Tag4
4. Set Type: Double
5. Save (Ctrl+S)

Apply Without Stopping

1. Click Apply Online Changes button
2. Dialog shows pending changes:
   • "Added: Tag4"
3. Click Apply
4. Message: "Changes applied successfully"

Verify in Property Watch

1. Return to Property Watch
2. Click Refresh
3. Expand Tag node
4. Confirm Tag4 appears
5. Runtime never stopped!

6. Test Client Connections (3 min)

Enable Web Client

1. Go to Runtime → Startup
2. Note the Web URL: http://localhost/MyFirstSolution
3. Click the link or copy to browser

Access Web Interface

In your browser:

1. Page loads automatically
2. If prompted for login:
   • Username: Administrator
   • Password: (blank for development)
3. Main display appears

Test Display Updates

1. Return to Property Watch
2. Change Tag1 value to 75
3. Watch web display update in real-time
4. Confirms client-server communication

7. Use Trace Window (2 min)

Open Trace Window

1. Click Runtime → Diagnostics
2. Select Trace Window

Configure Trace Level

Set diagnostic detail:

1. Select Level: Info
2. Check modules to monitor:
   • ? TServer
   • ? Device
   • ? Scripts

Generate Trace Messages

1. In Property Watch, change a tag value
2. Observe trace messages:

   [Info] Tag.Tag1 value changed: 50 -> 75
   [Info] Client connection from 127.0.0.1
   [Info] Display refresh requested

Export Trace Log

• Click Export button
• Save as: MyFirstSolution_trace.log
• Useful for troubleshooting

8. Stop and Restart Runtime (2 min)

Graceful Shutdown

1. Go to Runtime → Startup
2. Click Stop Runtime
3. Confirm when prompted
4. Watch shutdown sequence:

   [00:01] Stopping client connections...
   [00:02] Closing modules...
   [00:03] Saving data...
   [00:04] Runtime stopped

Quick Restart

Test restart capability:

1. Click Run Startup again
2. Solution restarts with Development profile
3. Previous tag values retained (if configured)
4. Clients auto-reconnect

Final Shutdown

• Click Stop Runtime
• Close diagnostic windows
• Runtime exercises complete

Key Takeaways

You've learned to:

• Start runtime in test and full modes
• Understand execution profiles for different environments
• Monitor runtime status and module health
• Use Property Watch for real-time tag monitoring
• Apply changes without stopping execution
• Connect and test client displays
• Use Trace Window for diagnostics
• Properly stop and restart runtime

Productivity Tips Discovered

• F5 for quick test mode
• Online changes prevent downtime
• Property Watch for live debugging
• Trace levels control diagnostic detail
• Profiles separate dev/test/production

Troubleshooting

Runtime won't start?

• Check license is valid for runtime
• Verify no other instance running
• Look for port conflicts (10397)
• Check Windows Event Log

Modules show error state?

• Review module configuration
• Check Trace Window for errors
• Verify database connections
• Ensure proper permissions

Can't apply online changes?

• Some changes require restart
• Check if production profile (protected)
• Verify user has permission
• Save changes before applying

Client can't connect?

• Check firewall allows connection
• Verify URL is correct
• Ensure runtime is running
• Test with localhost first

High CPU or memory usage?

• Check script execution frequency
• Review device communication rates
• Look for infinite loops in scripts
• Monitor historian storage settings

TutoriaL Final steps to deploy your solution to production with proper security, backup, and validation.

In this section...