Difference between revisions of "System Architecture"

From Elcano Project Wiki
Jump to navigation Jump to search
Line 16: Line 16:
  
 
* Raspberry Pi CAN interface: https://copperhilltech.com/pican2-can-interface-for-raspberry-pi-2-3-with-smps/
 
* Raspberry Pi CAN interface: https://copperhilltech.com/pican2-can-interface-for-raspberry-pi-2-3-with-smps/
 +
 +
* Raspberry Pi Camera: https://www.raspberrypi.org/products/camera-module-v2/
  
 
* Maxbotix 123x sonars: https://www.maxbotix.com/Ultrasonic_Sensors/MB1230.htm
 
* Maxbotix 123x sonars: https://www.maxbotix.com/Ultrasonic_Sensors/MB1230.htm
 +
 +
* Adafruit GPS breakout: https://www.adafruit.com/product/746
 +
 +
* Adafruit INU: https://www.adafruit.com/product/1120
  
 
* Scanse sweep: https://www.sparkfun.com/products/retired/14117
 
* Scanse sweep: https://www.sparkfun.com/products/retired/14117

Revision as of 18:42, 27 June 2019

The Elcano architecture features a series of microcontrollers connected over the automotive standard CAN bus. CAN is a no-host networking protocol with much of the overhead done in hardware. All Arduino processors are bare bones with no operating system. Messages sent over the bus are low bandwidth; any intense processing such as vision or lidar uses its own processor. Modularization reduces the size of the code running on any one processor. Reliability and security are enhanced since the core processors are not connected to the Internet and do not do machine learning.

Architecture CAN.png