...
Since the field for the length is empty ($ Length in bytes), the Membe fields fields should be evaluated:
The Instances Assemblys Member can be decoded as follows:
,,
32,,
,Assem4;
| Member Size | Member Reference | |
|---|---|---|
| First Member | empty | empty |
| Second Member | 32 | empty |
| Third Member | empty | Assem4 |
This means, the first Member is reserved, the second one has a size of 4Byte (32Bit) and the third one references to Assem4.
...
Now the total size of Assem127 can be defined:
| Member Size | Member Reference | Size in Byte | |
|---|---|---|---|
| First Member | empty | empty | |
| Second Member | 32 | empty | 4 (32Bit) |
| Third Member | empty | Assem4 | 1 |
| Total length of Input Assembly Assem127 | 5 |
Configure Output assembly length
The output assembly length is defined in the field “O->T size” and field “O->T format” of Connection 23:
It can be decoded as follows:
O → T
,0,,
| RPI | Size | Format |
|---|---|---|
| empty | 0 | empty |
Since the field “O->T size” is not empty, it can directly be read – 0 Byte.
In this case no further evaluation is needed.
In case this field is refered to a Parameter or Assembly, please use the steps memtioned in the example above: "Configure Input assembly length".
Configure configuration assembly length
The configuration assembly length is automatically calculated by the data length of cfg. #1 and cfg. #2 data segment.
The user is not allowed to directly edit this length.
Configure cfg. #1 data segment
The cfg #1 data segment is defined field "$ config part 1" of Connection23:
Here Assem124 is used to define the format. Go to the definition of Assem124:
In this case, both Values ("Member Size" and "Member Reference" have to be evaluated.
The Assemblys Member informations can be read as follows:
| Member Size | Member Reference | |
|---|---|---|
| First Member | 16 | Param101 |
| Second Member | 16 | empty |
The field of the first Member indicated, that it has a data length of 16 bit. It also has a Reference to Param101.
Go to the definition of Param101:
The "data size in Byte" has a size of 2 Byte, with a default value of 1.
So the default data of Param101 is 0x0001.
The user can also define a value between min. value and max. value.
Go back the definition of Assem124, the Second Member has a length of 16 and has no Reference entry. This means, all data are defined with value 0.
| Member Size | Member Reference | Data (Hex) | Swap | |
|---|---|---|---|---|
| First Member | 16 | Param101 | 01 00 |
|
| Second Member | 16 | empty | 00 00 | 00 00 |
| Total | 01 00 00 00 |
Configure cfg. #2 data segment
The cfg #1 data segment is defined field "$ config part 1" of Connection23:
Here Assem124 is used to define the format. Go to the definition of Assem124:
In this case, both Values ("Member Size" and "Member Reference" have to be evaluated.
The Assemblys Member informations can be read as follows:
| Member Size | Member Reference | |
|---|---|---|
| First Member | 16 | Param101 |
| Second Member | 16 | empty |
Configure 1734-OB8E
example project provided by Stephane in SUPFR-86193