Reception of request parameter group message
No
No
No
Yes
No
No
START
Request PG?
Request to
global destination
or PVED-CL?
Request for
Address Claimed?
Process the request
Timer marked
as active?
Yes
Timer`s value
exceeds limit?
Yes
Signal that Address
Claimed message
has to be sent out
Mark timer inactive
STOP
Timer marked
as active?
Yes
Timer’s valu
e
exceeds limit
?
Reset timer`s value
Mark timer active
Yes
Yes
Yes
Yes
Yes
Yes
No
Due to software architectural limitations, the following deviations apply:
•
If DM1 message (expected to be sent every 1s) is a long message and a long upon-the-request
DM1/DM2 is being sent out, the transmission of the cyclic message will be skipped
•
If DM2 is a long message – more than one CAN message is needed – it will always be transmitted to
the global destination (preceded with the Broadcast Announce Message)
Proprietary error codes are available for deep diagnostics. Further details can be found in
Diagnostics
(proprietary)
on page 35.
Proprietary messages
Both proprietary A and B messages are in use. PDU1 proprietary messages (pgn61184) are used for
configuration and control commands as well as GetCurrentMode and GetCurrentModeResponse
messages, whereas PDU2 format is used for broadcast status messages.
PVED-CL uses a separate CAN buffer for receiving data from each node it can communicate with. This
means there’s no dependency between messages with pgn61184 sent from different nodes.
As three different status messages can be broadcast, three proprietary PDU2 parameter group numbers
are needed.
These numbers are as follows:
•
(65280 + offset_base)
•
(65280 + offse 1)
•
(65280 + offse 2)
Technical Information
PVED-CL Communication Protocol, version 1.38 Technical Information
Communications
11079551 • Rev BA • July 2014
7