mirror of https://github.com/espressif/esp-idf.git synced 2024-10-05 20:47:46 -04:00

History

Darian Leung 896ba6a83e can: Fix reset mode entry and exit calls This commit fixes multiple bugs caused by incorrect calls to can_enter_reset_mode() and can_exit_reset_mode. Example test scripts also updated to match new runners.		2019-10-28 15:35:42 +08:00
..
can_network_listen_only	cmake: make main a component again	2018-09-11 09:44:12 +08:00
can_network_master	cmake: make main a component again	2018-09-11 09:44:12 +08:00
can_network_slave	cmake: make main a component again	2018-09-11 09:44:12 +08:00
example_test.py	can: Fix reset mode entry and exit calls	2019-10-28 15:35:42 +08:00
README.md	CAN Driver	2018-07-04 14:01:57 +08:00

README.md

CAN Network Example

Overview

The CAN Network Example demonstrates communication between two ESP32 modules (master and slave) using the CAN2.0B protocol. CAN is a multi-master protocol, therefore the concept of master/slave in this example refers to which node initiates and stops the transfer of a stream of data messages. The example also includes an optional Listen Only module which can passively receive the CAN messages sent between the master and slave module without participating in any CAN bus activity.

The CAN Network Example will execute the following steps over multiple iterations:

Both master and slave go through initialization process
The master repeatedly sends PING messages until it receives a PING_RESP from the slave. The slave will only send a PING_RESP message when it receives a PING message from the master.
Once the master has received the PING_RESP from the slave, it will send a START_CMD message to the slave.
Upon receiving the START_CMD message, the slave will start transmitting DATA messages until the master sends a STOP_CMD. The master will send the STOP_CMD after receiving N DATA messages from the slave (N = 50 by default).
When the slave receives the STOP_CMD, it will confirm that it has stopped by sending a STOP_RESP message to the master.

External Transceiver and Pin Assignment

The CAN controller in the ESP32 does not contain an internal transceiver. Therefore users are responsible for providing an external transceiver compatible with the physical layer specifications of their target ISO standard (such as SN65HVD23X transceivers for ISO 11898-2 compatibility)

The CAN controller in the ESP32 represents dominant bits to the transceiver as logic low, and recessive bits as logic high. The Network Example utilizes the following default pin assignments

TX Pin is routed to GPIO21
RX Pin is routed to GPIO22

The following diagram illustrates an example network

    ----------   ----------   --------------  
   |  Master  | |  Slave   | | Listen Only  | 
   |          | |          | |              | 
   | 21    22 | | 21    22 | | 21    22     | 
    ----------   ----------   --------------  
     |      |     |      |     |      |   
     |      |     |      |     |      |   
    ----------   ----------   ----------  
   | D      R | | D      R | | D      R | 
   |          | |          | |          | 
   |  VP230   | |  VP230   | |  VP230   | 
   |          | |          | |          | 
   | H      L | | H      L | | H      L | 
    ----------   ----------   ----------  
     |      |     |      |     |      |   
     |      |     |      |     |      |   
  |--x------|-----x------|-----x------|--| H
            |            |            |
  |---------x------------x------------x--| L

Note

If there appears to be no activity on the CAN bus when running the example, users can try running the can_self_test example to verify if their transceivers are wired properly.