V6008¶

Code: V6008
Message: Launch request argument is missing or out of range

An argument in the Debug Adapter Protocol launch request is missing or outside the range the debug server accepts, so the debug session does not start. The message names the argument and what was expected of it, for example:

V6008 - launch argument 'program' is required: the path to a compiled .iplc container
V6008 - launch argument 'scanLimit' must be a whole number of at least 1, but was 0; omit it to run without a bound

Every bad launch argument reports this one code. A container that cannot be debugged as built reports its own: V6009 when it carries no debug information, V6010 when it declares several program instances.

Launch Arguments¶

Argument	Accepted values
`program`	Required. A path to a compiled `.iplc` container.
`stopOnEntry`	`true` or `false`. Defaults to `false`.
`scanLimit`	A whole number of at least `1`. Omit the argument to run without a bound.
`freewheelingIntervalMs`	A cycle time in milliseconds, for a program whose task declares no `INTERVAL`. Defaults to `100`.

scanLimit has no value that means unlimited. The debug server rejects both 0 and -1. Omit the argument instead.

Example¶

The following launch configuration produces error V6008:

.vscode/launch.json¶

{
  "type": "ironplc",
  "request": "launch",
  "name": "IronPLC: Debug Active File",
  "program": "${file}",
  "scanLimit": 0
}

Deleting the scanLimit line fixes it. The session then scans until you stop it or a breakpoint pauses it.

To stop after a fixed number of cycles instead, give the count you want:

"scanLimit": 1

Solutions¶

Read the error message for the name of the argument that was rejected and the values it accepts
Set program to a compiled .iplc container, checking the path survives variable substitution
Remove scanLimit to run until you stop the session, or set it to 1 or more
Set a breakpoint instead of a scan bound when you want the session to stop at a particular line

V6008¶

Launch Arguments¶

Example¶

Solutions¶

See Also¶