1. Start Runtime in Development Mode
Quick Test from Designer
- Open MyFirstSolution in Designer (if not already open)
- Go to Runtime → Startup
- Make sure that under "ExecutionProfile" the option Development is checked
- Click the Run Startup button
- 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
- Go to Runtime → Execution Profiles
- See three default profiles:
- Development
- Validation
- Custom
3. Monitor Runtime Status
Start Full Runtime
- Go to Runtime → Startup
- Ensure Development profile selected
- Click Run Startup
- Watch startup progress
Check Module Status
On the TStartup display, observe which modules are running, paused or stopped.
4. Use Property Watch
Open Property Watch
- Click Runtime → Runtime Diagnostics
- Select Property Watch
- New window opens
Browse Runtime Objects
Navigate the object tree:
- Expand Tag node
- Find your tags (Double1, Double2, Double3)
- Click Double1
- View properties:
- Value: Current value
- Quality: 192 (Good)
- Timestamp: Last update
Modify a Value
Test runtime write:
- Select Double1 Value
- Enter new value: 50
- Press Enter
- Observe value changes
- Note timestamp updates
5. Test Client Connections
Enable Web Client
- Go to Runtime → Startup
- Note the HTMNL5 Client URL: http://127.0.0.1:3201/html5
- Click the play button or copy to browser
Access Web Interface
In your browser:
- Page loads automatically
- If prompted for login:
- Username: Administrator
- Password: (blank for development)
- Main display appears
Test Display Updates
- Return to Property Watch
- Change Double1 value to 75
- Watch web display update in real-time
- Confirms client-server communication
6. Use Trace Window
Open Trace Window
- Click Runtime → Runtime Diagnostics
- Select Trace Window
- Click Settings
- Check Debug
Any error message should display here (it's expected that at this moment no messages will show up, once there are no errors happening).
