DsPIC Block/CAN Receive - Revision history

LubinKerhuel: LubinKerhuel moved page Block/CAN Receive to DsPIC Block/CAN Receive: Block is a special page, creates many issues

2015-05-03T17:30:55Z

LubinKerhuel moved page Block/CAN Receive to DsPIC Block/CAN Receive: Block is a special page, creates many issues

LubinKerhuel at 18:52, 26 April 2010

2010-04-26T18:52:36Z

LubinKerhuel: /* Dialog Box Parameters */

2008-06-12T18:36:52Z

Dialog Box Parameters

LubinKerhuel: /* Dialog Box Parameters */

2008-06-12T18:29:58Z

Dialog Box Parameters

LubinKerhuel at 19:09, 10 June 2008

2008-06-10T19:09:34Z

LubinKerhuel: New page: Read data from a CAN bus The CAN Receive block with selected Identifier. The CAN message contain between 1 and 8 bytes. The five filters defined which message Identifier will be keept. Me...

2008-05-26T20:54:11Z

New page: Read data from a CAN bus The CAN Receive block with selected Identifier. The CAN message contain between 1 and 8 bytes. The five filters defined which message Identifier will be keept. Me...

New page

Read data from a CAN bus

The CAN Receive block with selected Identifier. The CAN message contain between 1 and 8 bytes. The five filters defined which message Identifier will be keept. Messages with Identifier not contained into one of the five filter are not catch. Two buffer allow to receive up to two different messages between the execution of two CAN Receive block (usually, from one time step to the other). The block works as a FIFO. Message with matching identifier comming while the buffer is already full are lost.

=Dialog Box Parameters=

==Num CAN==
Ref to the CAN peripheral being configured (some PIC have two CAN bus)

==Filter 0 and 1 Acceptance Mask / Filter 2, 3 and 4 Acceptance Mask==
The two acceptance filter acts respectivly on Filter 0-1 and Filter 2-3-4.
A bit set to 0 in the acceptance Filter will be ignored by the respective fitlers.

==Message x Data Length==
For each filter (from 0 to 4) Message Data Length define the length of the message to be received by this filter. A message can contain up to eight bytes. If the Message Data Length is set to a lower value than the message being received, only the first bytes of the message will be taken into account. Iif the Message Data Length is set to a higher value than the message being received, the last bytes content of the message taken into account will be undefined (contains old values).
If the Message Data Lengt is set to a value higher than 1, the block output with the same length as the Message Data Length. A simulink Demux block should be used to get each byte of the message.
If the Message Data Length is set to Off, the Filter is not used. No message will be received.

==Acceptance Filter x==
For each of the 5 filters, the acceptance filter allow to retain only the the CAN message with an identifier that match the Acceptance Filter. The Acceptance Filter is bitewise compare to the CAN message Identifier, except for the bytes where the Filter Acceptance Mask is set to 0.

==Acceptance Filter type==
*Standard or Extended
*Standard 11 bits
*Extended 29 bits

==Output received Data Length==
If checked, a block output with the Real Data Length of the message received appears. This Data Length is read from the CAN bus. It is independant from the Message x Data Length parameter.

==Output Flag New Message==
If checked, a block output with a logic flag set to 1 each time a new message arrived.

==Output Identifier==
If checked, a block output with the Message Identifier received.

==Output Flag Data Request To send==
If checked, a block output with the Data Request To Send Flag appears.

==Receive Error Counter==
The Receive Error Counter output the internal CAN Receive Error Counter. See CAN doccumentation for precision about Error Counter.

==Output Flag Data Lost==
If checked, a block output with a flag appears. This flag is set to 1 when a message with a matching Identifier appears on the CAN bus, but cannot be stored because the buffer is already full.

==Sample Time==
Sample time of the block. -1 for inherited

==Block Ordering Input / Output==
If you want to force the execution order of blocks that are not connected, this option allow to add either an input, an output or both to the block. These virtual connection allow to force the ordering of the blocks.

==Info==
Information

← Older revision		Revision as of 18:52, 26 April 2010
Line 54:		Line 54:
	==Info==		==Info==
	Information		Information
		+
		+	----
		+	<comments \>

← Older revision		Revision as of 19:09, 10 June 2008
Line 1:		Line 1:
		+	[[Image:Block_CAN_Receive.png\|thumb\|rght\|Block CAN Receive]]
	Read data from a CAN bus		Read data from a CAN bus

← Older revision	Revision as of 17:30, 3 May 2015
(No difference)

@@ Line 5: / Line 5: @@
 =Dialog Box Parameters=
-[[Image:Block_CANReceive_DialogBox.png|thumb|right|450px|CAN Receive Dialog]]
+[[Image:Block_CANReceive_TabGeneral_DialogBox.png|thumb|right|450px|CAN Receive Dialog]]
 ==Num CAN==
 Ref to the CAN peripheral being configured (some PIC have two CAN bus)