CAN: Clarify block help text

[jenkicar/rpp-simulink.git] / rpp / blocks / sfunction_canreceive.c

diff --git a/rpp/blocks/sfunction_canreceive.c b/rpp/blocks/sfunction_canreceive.c
index d52434c39145c8f4988dd58eafc055daff5d9e3b..b4dae661320cc3b7cd36155d95418db68c2dbf51 100644 (file)
--- a/rpp/blocks/sfunction_canreceive.c
+++ b/rpp/blocks/sfunction_canreceive.c
@@ -88,18 +88,19 @@ Help: |
   0x003 and EFF IDs 0x00080000 and 0x000c0000.
 
   The mailbox number can be assigned automatically or manually. Automatic mailbox
-  numbers are generated in ascending order from 0 to 31. Every mailbox must have a unique
+  numbers are generated in ascending order from 1 to 64. Every mailbox must have a unique
   number. It is possible to mix blocks with automatically and manually
   assigned mailboxes. If the manually assigned mailbox number would
   collide with the automatic one then the automatically generated
-  block will get assigned a next higher non-colliding ID.
+  block will get assigned a next higher non-colliding number.
   The mailbox numbers are shared between CAN Transmit and CAN Receive
   blocks with the same CAN port (module) parameter.
 
-  The order in which the messages are received and their priority depends on their
-  mailbox numbers. The lower the mailbox number is, the higher is the priority.
-  If you want to have the priority of the messages under control, you have to specify
-  the numbers of the mailboxes manually. 
+  On message reception, the mailboxes and their acceptance filters are
+  consulted in the order of increasing mailbox number. If a message
+  can be accepted by more than one block you may want to assign the
+  mailbox number manually to have better control over which block
+  receives the message.
 
   The output of this block is a message data in selected format: uint8, uint16, uint32
   or CAN\_MESSAGE. The CAN\_MESSAGE object can be unpacked by `CAN Unpack` block.