CAN communication between two dsPIC - Revision history

LubinKerhuel at 23:31, 17 February 2011

2011-02-17T23:31:08Z

LubinKerhuel at 23:30, 17 February 2011

2011-02-17T23:30:31Z

LubinKerhuel at 23:12, 16 February 2011

2011-02-16T23:12:05Z

LubinKerhuel at 23:06, 16 February 2011

2011-02-16T23:06:39Z

LubinKerhuel at 00:10, 5 January 2011

2011-01-05T00:10:59Z

LubinKerhuel: Created page with "=Description= The objective of this example is to demonstrate how to use the can peripheral embedded on some dsPIC. Two dsPIC exchanges numerical data through the CAN bus. Both ..."

2010-12-30T22:36:55Z

Created page with "=Description= The objective of this example is to demonstrate how to use the can peripheral embedded on some dsPIC. Two dsPIC exchanges numerical data through the CAN bus. Both ..."

New page

=Description=

The objective of this example is to demonstrate how to use the can peripheral embedded on some dsPIC. Two dsPIC exchanges numerical data through the CAN bus. Both microcontrollers (here, two dsPIC 30f4012) are programmed using the dsPIC blockset for simulink available on this website. This example was added in the blockset version 3.4.

Next to come...

@@ Line 1: / Line 1: @@
+                          [[Image:Circuit_CAN.png|right|thumb|350px|Components schematic and electronics picture of two dsPIC 30f4012 exchanging data’s through a CAN bus (CANH and CANL). The MCP2551 is a CAN bus driver which translate dsPIC’s CAN peripheral output into CAN bus level. These two drivers are absolutely required. The MCP2551 represented upside on the top schematic is rotated of 180° in the electronics picture. The electronic picture is composed of two dsPIC 30f4012 connected to their respective MCP2551 driver. The CAN bus wire is here made of the two short green wires on the left side. The electronic schematic is symmetric (no master, no slave…)]]
 =Description=
-This example shows two dsPIC 30f4012 exchanging data through a bus CAN. The dsPIC embedded program is generated through Simulink and Realtime-Workshop Embedded Coder and the [[Download#Download|dsPIC blockset]]. The CAN bus is symmetrical consequently there is no master and no slave. Every 2ms, each dsPIC place one data (frame) on the bus to be read by the other dsPIC. The internal dsPIC CAN peripheral arbitrate bus access to avoid conflict (only one peripheral can write to the bus at one time). Both dsPIC places the received data from the CAN bus to its UART. The dsPIC UART is connected to the PC and the Matlab graphical interface [[Block/Interface_Tx-Matlab|rs232gui}} allows to plot theses data in real time.
+This example shows two dsPIC 30f4012 exchanging data through a bus CAN. The dsPIC embedded program is generated through Simulink and Realtime-Workshop Embedded Coder and the [[Download#Download|dsPIC blockset]]. The CAN bus is symmetrical consequently there is no master and no slave. Every 2ms, each dsPIC place one data (frame) on the bus to be read by the other dsPIC. The internal dsPIC CAN peripheral arbitrate bus access to avoid conflict (only one peripheral can write to the bus at one time). Both dsPIC places the received data from the CAN bus to its UART. The dsPIC UART is connected to the PC and the Matlab graphical interface [[Block/Interface_Tx-Matlab|rs232gui]] allows to plot theses data in real time.
 =Characteristics of a CAN bus =

@@ Line 1: / Line 1: @@
-[[Image:Circuit_CAN.png|right|left|350px|Components schematic and electronics picture of two dsPIC 30f4012 exchanging data’s through a CAN bus (CANH and CANL). The MCP2551 is a CAN bus driver which translate dsPIC’s CAN peripheral output into CAN bus level. These two drivers are absolutely required. The MCP2551 represented upside on the top schematic is rotated of 180° in the electronics picture. The electronic picture is composed of two dsPIC 30f4012 connected to their respective MCP2551 driver. The CAN bus wire is here made of the two short green wires on the left side. The electronic schematic is symmetric (consequently, there is no master, no slave…)]]
 =Description=
-This example shows two dsPIC 30f4012 exchanging data through a bus CAN. The dsPIC embedded program is generated through Simulink and Realtime-Workshop Embedded Coder and the [[Download#Download|dsPIC blockset]]. The CAN bus is symmetrical consequently there is no master and no slave. Every 2ms, each dsPIC place data on the bus to be read by the other dsPIC. The internal dsPIC CAN peripheral arbitrate bus access to avoid conflict (only one peripheral can write to the bus at one time). Both dsPIC copy received data to its UART and also add few other data like CAN bus state etc… The dsPIC UART is connected to the PC and the Matlab graphical interface [[Block/Interface_Tx-Matlab|rs232gui}} allows to plot theses data in real time.
+This example shows two dsPIC 30f4012 exchanging data through a bus CAN. The dsPIC embedded program is generated through Simulink and Realtime-Workshop Embedded Coder and the [[Download#Download|dsPIC blockset]]. The CAN bus is symmetrical consequently there is no master and no slave. Every 2ms, each dsPIC place one data (frame) on the bus to be read by the other dsPIC. The internal dsPIC CAN peripheral arbitrate bus access to avoid conflict (only one peripheral can write to the bus at one time). Both dsPIC places the received data from the CAN bus to its UART. The dsPIC UART is connected to the PC and the Matlab graphical interface [[Block/Interface_Tx-Matlab|rs232gui}} allows to plot theses data in real time.
 =Characteristics of a CAN bus =
 [[Image:Scope_HM205_CAN_01.jpg|thumb|right|350px|Photo (1) of a scope showing absolute voltage of the CANH and CANL wires. 6 CAN composed of recessive (CANH != CANL) and dominant (CANH=CANL) states . The three yellow highlighted belong to the dsPIC (A) and the three blue highlighted belong to the dsPIC (B). The dsPIC (A) frame (yellow) contains 3 data bytes while the dsPIC (B) frame (blue) contains only 2 data bytes (Blue highlighted frames are shorten than the yellow one). Each dsPIC feed its CAN peripheral with the 3 or 2 byte composing the frame at a frequency of 500Hz. A 2 ms time delay separates two consecutive frame created by one dsPIC (resp yellow one or blue one). However, time delay (Delta BA) separating a frame B=>A from a frame A=>B increase (or decrease) slowly because of the slight frequency difference between the two 8Mhz quartz clocking both dsPIC (frequency error). When both frame are close to each other, the CAN peripheral manage automatically bus arbitration to avoid conflict. Consequently, the first dsPIC writing a dominant state (byte) on the bus gets the priority. Consequently, the two frames keep close until switching their respective place and continuing to evaluate in time relatively to each other (see photo (2)). ]]
 [[Image:Scope_HM205_CAN_02.jpg|thumb|right|350px|Photo (2) of a scope showing absolute voltage of the CANH and CANL wires taken few seconds after the first photo (see photo 1). The voltages for dominant and recessive states are specified here. As mentioned in photo (1) caption, the time delay (Delta BA) separating two consecutive frames (B=>A from A=>B) is longer than in photo (1) due to the slight frequency difference between the two quartz driving each dsPIC. ]]
-CAN acronym stands for Controller Area Network. It is a numerical bus coding its two states (one dominant and one recessive) using differential voltage between its two wires named respectively CANH and CANL.
+CAN bus is a “multi-slave” bus where any connected dispositive can send a message. Frames are composed of an id which is set by user, and 1 to 8 data bytes. Device waiting for a specific data will filter out incoming frames based on their id. Thus both emitter and receiver exchanging data must have in common the frame id that will be used.
 Each CAN frame are acknowledged by the receiver. The message is reemitted by its author until it is acknowledged. However, the reemission is stopped after the xx attempted.
@@ Line 24: / Line 23: @@
 * [[Block/CAN_Receive|CAN Receive]].
-The [[Block/CAN_Configuration|CAN Configuration]] block configure CAN peripheral like bus frequency, time quanta, … This block is required as soon as one CAN peripheral is used.
+The [[Block/CAN_Configuration|CAN Configuration]] block configure CAN peripheral like bus frequency, time quanta. This block is required as soon as one CAN peripheral is used.
-The block [[Block/CAN_Transmit|CAN Transmit]] define frame id, data length (1 to 8 bytes) …
+The block [[Block/CAN_Transmit|CAN Transmit]] define frame id, data length (1 to 8 bytes)
 =Electronics=
-[[Image:CAN_addedComponents.jpg|thumb|left|85px|CAN driver]]
+[[Image:CAN_addedComponents.jpg|thumb|left|120px|Added components for CAN bus: two CAN driver (MCP2551) drives the CAN differential signals. Two 10kOhm are required for theses drivers. One 68Ohms resistor is placed between the two CAN lines.]]
 We use the same prototyping board described in the [[PWM_communication_between_two_dsPIC#Electronics|PWM example]]. And a bootloader capable of flashing the binary into the chip through UART is also used as it is described [[PWM_communication_between_two_dsPIC#Bootloader|here]].
@@ Line 40: / Line 39: @@
 =Simulink models=
-Two simulink models generate the code for the dsPIC (A) and the dsPIC (B).  The common parts of these two models have been described on the [[PWM_communication_between_two_dsPIC#Common parts |PWM example]], including the bootloader reset system.
+Two simulink models generate the code for the dsPIC (A) and the dsPIC (B). The common parts of these two models have been described on the [[PWM_communication_between_two_dsPIC#Common parts |PWM example]], including the bootloader reset system.
-Let’s considere only the specific parts related to the CAN bus of these two models.
+Let’s considers only the specific parts related to the CAN bus of these two models.
 ==Model A: Emission ==
 [[Image:SimulinkModel_CAN_a_30f4012.png|thumb|right|350px|Simulink model A: CAN_a_30f4012]]
 The model A creates an internal sine wave signal of type int16 with amplitude 5000 and frequency 4 Hz.
 Optimized method for sine wave generation was described in the [[PWM_communication_between_two_dsPIC# Sine wave generation|PWM example]].
 ==Model B: Reception==
 [[Image:SimulinkModel_CAN_b_30f4012.png|thumb|right|350px|Simulink model B: CAN_b_30f4012]]
 [[Image:rs232gui_CAN_b_ReceivedValue.png|thumb|none|350px|Matlab plot of the data sent by microcontroller B through UART. The rs232gui interface is used to plot incoming data in real-time]]

@@ Line 1: / Line 1: @@
-                          [[Image:Circuit_CAN.png|right|left|350px|Components schematic and electronics picture of two dsPIC 30f4012 exchanging data’s through a CAN bus (CANH and CANL). The MCP2551 is a CAN bus driver which translate dsPIC’s CAN peripheral output into CAN bus level. These two drivers are absolutely required. The MCP2551 represented upside on the top schematic is rotated of 180° in the electronics picture. The electronic picture is composed of two dsPIC 30f4012 connected to their respective MCP2551 driver. The CAN bus wire is here made of the two short green wires on the left side. The electronic schematic is symmetric (consequently, there is no master, no slave…)]]
+[[Image:Circuit_CAN.png|right|left|350px|Components schematic and electronics picture of two dsPIC 30f4012 exchanging data’s through a CAN bus (CANH and CANL). The MCP2551 is a CAN bus driver which translate dsPIC’s CAN peripheral output into CAN bus level. These two drivers are absolutely required. The MCP2551 represented upside on the top schematic is rotated of 180° in the electronics picture. The electronic picture is composed of two dsPIC 30f4012 connected to their respective MCP2551 driver. The CAN bus wire is here made of the two short green wires on the left side. The electronic schematic is symmetric (consequently, there is no master, no slave…)]]
 =Description=
@@ Line 31: / Line 31: @@
 =Electronics=
 [[Image:CAN_addedComponents.jpg|thumb|left|85px|CAN driver]]
 We use the same prototyping board described in the [[PWM_communication_between_two_dsPIC#Electronics|PWM example]]. And a bootloader capable of flashing the binary into the chip through UART is also used as it is described [[PWM_communication_between_two_dsPIC#Bootloader|here]].

@@ Line 1: / Line 1: @@
-[[Image:Circuit_CAN.png|thumb|right|350px|CAN Circuit]]
+                          [[Image:Circuit_CAN.png|right|left|350px|Components schematic and electronics picture of two dsPIC 30f4012 exchanging data’s through a CAN bus (CANH and CANL). The MCP2551 is a CAN bus driver which translate dsPIC’s CAN peripheral output into CAN bus level. These two drivers are absolutely required. The MCP2551 represented upside on the top schematic is rotated of 180° in the electronics picture. The electronic picture is composed of two dsPIC 30f4012 connected to their respective MCP2551 driver. The CAN bus wire is here made of the two short green wires on the left side. The electronic schematic is symmetric (consequently, there is no master, no slave…)]]
 =Description=
+This example shows two dsPIC 30f4012 exchanging data through a bus CAN. The dsPIC embedded program is generated through Simulink and Realtime-Workshop Embedded Coder and the [[Download#Download|dsPIC blockset]]. The CAN bus is symmetrical consequently there is no master and no slave. Every 2ms, each dsPIC place data on the bus to be read by the other dsPIC. The internal dsPIC CAN peripheral arbitrate bus access to avoid conflict (only one peripheral can write to the bus at one time). Both dsPIC copy received data to its UART and also add few other data like CAN bus state etc… The dsPIC UART is connected to the PC and the Matlab graphical interface [[Block/Interface_Tx-Matlab|rs232gui}} allows to plot theses data in real time.
-The objective of this example is to demonstrate how to use the can peripheral embedded on some dsPIC. Two dsPIC exchanges numerical data through the CAN bus. Both microcontrollers (here, two dsPIC 30f4012) are programmed using the dsPIC blockset for simulink available on this website. This example was added in the blockset version 3.4.
+=Characteristics of a CAN bus =
-Next to come...
+[[Image:Scope_HM205_CAN_01.jpg|thumb|right|350px|Photo (1) of a scope showing absolute voltage of the CANH and CANL wires. 6 CAN composed of recessive (CANH != CANL) and dominant (CANH=CANL) states . The three yellow highlighted belong to the dsPIC (A) and the three blue highlighted belong to the dsPIC (B). The dsPIC (A) frame (yellow) contains 3 data bytes while the dsPIC (B) frame (blue) contains only 2 data bytes (Blue highlighted frames are shorten than the yellow one). Each dsPIC feed its CAN peripheral with the 3 or 2 byte composing the frame at a frequency of 500Hz. A 2 ms time delay separates two consecutive frame created by one dsPIC (resp yellow one or blue one). However, time delay (Delta BA) separating a frame B=>A from a frame A=>B increase (or decrease) slowly because of the slight frequency difference between the two 8Mhz quartz clocking both dsPIC (frequency error). When both frame are close to each other, the CAN peripheral manage automatically bus arbitration to avoid conflict. Consequently, the first dsPIC writing a dominant state (byte) on the bus gets the priority. Consequently, the two frames keep close until switching their respective place and continuing to evaluate in time relatively to each other (see photo (2)). ]]

← Older revision		Revision as of 00:10, 5 January 2011
Line 1:		Line 1:
		+	[[Image:Circuit_CAN.png\|thumb\|right\|350px\|CAN Circuit]]
	=Description=		=Description=