basic ASCII encoding (values 0 ... 127) then UTF-8 is the same as ASCII and every
character takes exactly one byte.
Access Type
This property allows some optimization and is required for CANopen support.
Generally the owner of a variable has full access and can modify its value whenever he
needs to. Access type describes what others can do with the variable: If you e.g. set the
variable as "ReadOnly" then a write request will not even be sent to the owner but the
attempt to write will directly fail.
Full access to the variable is provided with access type "ReadWrite" - so if the variable
should not need limitations this is the value to choose.
Default Value
The variable is initialized with this value - depending on "Initialize Value As Invalid" below
you may never actually see this value on screen.
Initialize Value as Invalid
Set this property to consider the variable value invalid until a first value is provided by the
owner. DDOs typically appear disabled (grey mask on top) while the value is invalid.
If you want to consider the "Default Value" above a valid value of the variable even
though it was not set by the owner you should uncheck this property.
Remanent
Set this property if variable value should persist over power cycles. This property only
actually modifies user defined variables owned by PClient. For predefined variables it's
an information about what the owner does.
Force Writing
Normally there is some optimization in place which only forwards "new" variable values if
the value was modified. I.e. PClient only forwards write requests to the variable owner if
the value is different from the current one. The other way around it only forwards the
"new" value sent by the owner if the value differs from the last one received.
This is helpful in most cases where e.g. the value is periodically transferred in a CAN
message.
There are use cases though where every update or write request has to be forwarded
i.e. the write itself is more meaningful than the value it transports. An example from the
predefined variables is "@BeeperRepetitions" which should start a beeper sequence
which could have the same amount as repetitions as the last one. For these cases
"Force Writing" should be checked.
Protocol Specific
Based on the CAN protocol use to communicate with variable owner there could be
additional properties required. These properties would appear here.
One example for these additional properties is index/subindex of the variable in the
owner's object dictionary. This is currently only used if the owner is a CANopen ECU.
Protocol specific properties are explained on the pages of the protocols, see CAN
Freestyle , CANopen and J1939 .
Events
The "Events" tab allows to assign actions to specific events. By default no actions are
assigned.
To Next Page
Loading...