Update block masks by running rpp_update_doc.m

Note: This was needed for the updated buildbot not to complain about
doc inconsistency. The changes bellow are white-space only and are
probably caused by newer version of the pandoc tool on the ritchie
server.

Changelog:
Processing rpp_aout/Analog Output
Processing rpp_can_rx/CAN Receive
diff --git a/sfunction_canreceive.MaskDescription.old b/sfunction_canreceive.MaskDescription.new
index 3283e26..d1bc5ab 100644
--- a/sfunction_canreceive.MaskDescription.old
+++ b/sfunction_canreceive.MaskDescription.new
@@ -1,6 +1,7 @@
<p>Receive a messages from the CAN bus.</p>
<p>The output can be a uint8, uint16, uint32 number or CAN_MESSAGE object. CAN Unpack block can be used to unpack the data from CAN_MESSAGE object.</p>
<p>A Function-call subsystem is triggered every time when a new message has been received.</p>
<p>When Mixed is selected in the <em>Message type</em>, the block is able to receive both, the mesages with Standard and Extended identifier.<br [-/><strong>NOTE:</strong>-]{+/>+}
{+<strong>NOTE:</strong>+} When Mixed is selected, the <em>Message ID</em> and eventualy the <em>Message ID mask</em> have to be shifted by 18 bits to the left.</p>
<p>If the <em>Message filter</em> is set to Single ID, only the messages with the one identifier specified in <em>Message ID</em> will be accepted by the block. But when ID &amp; mask is selected, all messages with identifier compliant to logical AND of the <em>Message ID</em> and <em>Message ID mask</em> will be accepted.</p>
<p>Uncheck <em>Automatic mailbox number</em>, if user defined mailbox number is needed.</p>

Processing rpp_can_setup/CAN Setup
Processing rpp_can_tx/CAN Transmit
Processing rpp_din_cfg/Digital Input Configure
Processing rpp_din/Digital Input
Processing rpp_dout/Digital Output
Processing rpp_fr_cfg/Configure FlexRay node
Processing rpp_fr_rx/Configure RX buffer
Processing rpp_fr_tx/Configure TX buffer
Processing rpp_gio_in/General Purpose Digital Input
Processing rpp_gio_out/General Purpose Digital Output
Processing rpp_hbr/H-Bridge Control
Processing rpp_ircin/IRC Input
Processing rpp_log/SD-RAM Log Data
diff --git a/sfunction_sdrw.MaskDescription.old b/sfunction_sdrw.MaskDescription.new
index 78b8676..484559b 100644
--- a/sfunction_sdrw.MaskDescription.old
+++ b/sfunction_sdrw.MaskDescription.new
@@ -1,2 +1,4 @@
<p>This block allows to log a double value to the SD-RAM. User needs to provide a valid PrintFormat string to format and register the double value on the log. The PrintFormat string should include two specifiers:<br />
1. For the block ID. Any valid integer specifier.<br />
2. For the value to log. Any valid double specifier.</p>
<p>Note that the value of PrintFormat is inserted raw between quotes on code generation and thus there is no validation on it. Error to provide a valid PrintFormat could generate compilation errors or even run-time errors (normally this generates a warning on compile time). Note that the function for logging used is <code>rpp_sdr_printf()</code>, which is a blocking call, and can potentially overrun the step. The ErrFlag will set if <code>rpp_sdr_printf()</code> returns an error (for example out of memory), but will clear back if the next step the call to this function is successful.</p>

diff --git a/sfunction_sdrw.MaskHelp.old b/sfunction_sdrw.MaskHelp.new
index 78b8676..484559b 100644
--- a/sfunction_sdrw.MaskHelp.old
+++ b/sfunction_sdrw.MaskHelp.new
@@ -1,2 +1,4 @@
<p>This block allows to log a double value to the SD-RAM. User needs to provide a valid PrintFormat string to format and register the double value on the log. The PrintFormat string should include two specifiers:<br />
1. For the block ID. Any valid integer specifier.<br />
2. For the value to log. Any valid double specifier.</p>
<p>Note that the value of PrintFormat is inserted raw between quotes on code generation and thus there is no validation on it. Error to provide a valid PrintFormat could generate compilation errors or even run-time errors (normally this generates a warning on compile time). Note that the function for logging used is <code>rpp_sdr_printf()</code>, which is a blocking call, and can potentially overrun the step. The ErrFlag will set if <code>rpp_sdr_printf()</code> returns an error (for example out of memory), but will clear back if the next step the call to this function is successful.</p>

Processing rpp_overrun/Overrun Detection
Processing rpp_power/Power Output
Processing rpp_rpp_ain/Analog Input
Processing rpp_sci_cfg/Serial Configure
Processing rpp_sci_printf/Serial Printf
Processing rpp_sci_rx/Serial Receive
Processing rpp_sci_tx/Serial Send

diff --git a/rpp/blocks/rpp_can_rx.slx b/rpp/blocks/rpp_can_rx.slx
index 0b75a7907a5e343e410947a74bad97d5780ed9f7..fef61fc56f7438be8a631a6e66f1c01b90843abd 100644 (file)
Binary files a/rpp/blocks/rpp_can_rx.slx and b/rpp/blocks/rpp_can_rx.slx differ

diff --git a/rpp/blocks/rpp_log.slx b/rpp/blocks/rpp_log.slx
index 0690a7581b396abbfcbb2f2d9ec66f52776bbf7e..3fbeebbc50f0106f1742268530c35d4447a13a41 100644 (file)
Binary files a/rpp/blocks/rpp_log.slx and b/rpp/blocks/rpp_log.slx differ