Code: |
AS + 802 |
Symbolic: |
bccLadLiveLoad |
This command will load live changes for a program directly to device memory: this is a standard standard data load sequence.
If the command is accepted, the device will open a live change session that can be started with the bccLadLiveTest message and kept alive with the bccLadLiveWd message: this session must be stopped with bccLadLiveConfirm or bccLadLiveCancel before it expire.
For a single PID, while its live change session is in testing (active) it is not possible to load any other changes: otherwise any further load will replace current changes by creating a new live changes session. Therefore, any PID can have only one live changes session.
REQDATA structure is the following:
Offset |
Type |
Label |
Description |
|---|---|---|---|
0 |
U32 |
SIZE |
Live changes size [byte] |
4 |
U8[12] |
- |
(riservati) |
16 |
U16 |
PID |
Process ID |
18 |
U32 |
FLAGS |
Operating flags: (none) |
If initial request fails, bccNack is received. Specific errors
NACK code |
Description |
Extra data |
|---|---|---|
nackIllegalArgs |
Illegal arguments |
U16 What illegal: 1=Live changes size 2=Process ID 3=Flags |
nackNotFound |
Process not found |
|
ACKDATA structure is the following:
Offset |
Type |
Label |
Description |
|---|---|---|---|
0 |
U8 |
BSIZE |
Required item size (0=default), excluding leading U32 offset data. |
1 |
U8[15] |
|
(riservati) |
16 |
U32 |
SESSID
|
Live changes session ID |
NOTE: to have more information about the transferred data, see the .LAD File Specifications in the ladder diagram documentation.
