Configuration
VS Code Setup
Auto-generate
The fastest way to get started is with the init command:
./wincc-unified-debug-proxy.exe initThis creates the following .vscode/launch.json:
{
"version": "0.2.0",
"configurations": [
{
"type": "node",
"request": "attach",
"name": "WinCC:Dynamics",
"address": "localhost",
"port": 9230,
"restart": true,
"timeout": 30000
},
{
"type": "node",
"request": "attach",
"name": "WinCC:Events",
"address": "localhost",
"port": 9231,
"restart": true,
"timeout": 30000
}
],
"compounds": [
{
"name": "WinCC:All",
"configurations": ["WinCC:Dynamics", "WinCC:Events"],
"stopAll": true
}
]
}Key settings
| Setting | Value | Why |
|---|---|---|
restart | true | VS Code automatically reconnects when the proxy closes the connection |
Debug configurations
WinCC:Dynamics
Connects to the Dynamics proxy (default port 9230). Use this for debugging dynamic property scripts such as animations and value updates.
WinCC:Events
Connects to the Events proxy (default port 9231). Use this for debugging event scripts such as button clicks and screen events.
WinCC:All
Starts both configurations simultaneously. Useful when you want to debug both Dynamics and Events scripts at the same time.
Manual setup
If you already have a launch.json, add the configurations manually to the configurations array and optionally the compound to compounds.
Using custom ports with the proxy? Make sure the port values in launch.json match.