ConceptCar - User contributions [en]

Adding Resources to the Concept Car

2009-11-14T22:37:54Z

Quarz: /* Operational Controls */

The Concept Car has a modular architecture allowing the addition of resources in a simple way. In order to integrate a new element in the Car architecture it is necessary to integrate it to a new AT90CAN128 board. The AT90CAN128 boards are the interface between the sensors and actuators (i.e. the environment) and the Concept Car's CAN bus. Their main purpose is to do low level tasks, like PWM de- and encoding.

The characteristics of the AT90CAN128 boards are presented in the following.

==Board Dimensions==

[[image:StackableBoardLayout.png|thumb|200px|Figure 4.1. Board Dimensions]]

All boards featuring an AT90CAN128 microcontroller are supposed to fit into any of the 8 spaces at the CAN bus box. Therefore they share the same dimensions, drill holes for mounting and SUB-D jack position. They all have the same dimensions to be interchangeable in place.

This dimensions are precisely the same used for the SensorBoards in the old Hardware Revision 1.0, all Revisions >= 1.2 must comply with these dimensions.

Since the boards can be stacked, it is a good idea to place all connectors, switches and LEDs near the borders.

Figure 4.1 presents the board dimensions.

===Schematic===

First apply this in the schematic:
* Add the 4 drill holes as parts ''MOUNT-HOLE3.0''
* The SUB-D CAN connector must be of type ''F09H''

===Board===

To get a proper board, follow these steps in eagle (when starting from scratch):
# Set the grid to ''1mm''
# Move the edges of the dimension polygon so that it's a square of 73mm x 73mm, with its origin being in the bottom left edge.
# Move the drill holes to the positions 4mm apart from each edge
# Rotate the SUB-D CAN connector to face upwards and move it to position 37.506mm/60.88mm. <tt>MOVE CAN_BUS (37.506mm 60.88mm)</tt> would do this.

==Operational Controls==

[[image:Actorboard_boardDesignIllustration.png|thumb|350px|Figure 4.2. An example of good placement of the operational controls and of their labeling.]]

These are recommendations on what operational controls to use to supply a uniform look&feel (and in some aspects programming) of the sensor- and actor-boards. The placement is not critical, it just looks better this way.

* The CAN bus driver is designed to signal the bus state with 2 LEDs (a green one for ''error active'' state and a red one for ''bus off'' state). Those LEDs are attached to I/O-Pins PA7 (red LED) and PA6 (green LED), over a resistor of 220 Ohms to ground each. The LEDs (package: <tt>CHIP-LED0805</tt>) should be placed as in the list below
* A green power on LED (<tt>CHIP-LED0805</tt>) that is directly attached to the power supply is recommended.
* If any additional LEDs are required, they should be placed at the lower border, like the CAN LEDs 200mil away from it or like in the list below.
* Connectors to peripherals or other boards must be low enough to avoid trouble with other boards in the stack. Recommended type is for example <tt>L02P</tt>, <tt>L03P</tt>, <tt>L05P</tt>.

'''Component placement:'''

Reset Switch: 550x275;
C 100n: 865x 415;
R 10k: 865x335;

LEDS:
Power: Resistor (220 Ohms): 865x255;
LED: 65x175

LEDs with Resistors from left to rigt:
R: 1075x25;
LED: 1075x175;
R: 1230x255;
LED: 1230x175;
R: 1550x255;
R: 1800x255;
R: 2025x255;
R: 2225x255;

Diode BAS85: 2375x2745

Diode Minimelf: 2440x2430, angle 270°

Coil: 2215x2655, angle: 270°

MAX1837: 2365x2630, angle: 90°

Capacitor: 2285x2435

Capacitor: 2595x2435, angle 270°

AT90CAN128: 1825x840, angle 270° (not forced)

CAN: 1475x2150

JTAG: 2450x800

ISP: 2450x1610

ISP is mandatory, but JTAG can be omitted.

'''AT90CAN128 Pin Connections'''

'''Port A:'''

Pin0:

Pin1:

Pin2:

Pin3:

Pin4:

Pin5:

Pin6: CAN_STATUS0

Pin7: CAN_STATUS1

'''Port B:'''

Pin0:

Pin1: SCK

Pin2:

Pin3:

Pin4:

Pin5:

Pin6:

Pin7:

'''Port C:'''

Pin0:

Pin1: LED_OK

Pin2: LED_PWM

Pin3: LED_

Pin4: LED_

Pin5:

Pin6:

Pin7:

'''Port D:'''

Pin0:

Pin1:

Pin2:

Pin3:

Pin4:

Pin5: TXCAN

Pin6: RXCAN

Pin7:

'''Port E:'''

Pin0: PDI

Pin1: PDO

Pin2:

Pin3:

Pin4:

Pin5:

Pin6:

Pin7:

'''Port F:'''

Pin0:

Pin1:

Pin2:

Pin3:

Pin4: TCK

Pin5: TMS

Pin6: TDO

Pin7: TDI

Adding Resources to the Concept Car

2009-11-14T22:15:42Z

Quarz: /* Operational Controls */

Main Page

2009-09-21T13:21:49Z

Quarz: /* WELCOME */

[[image:ConceptCarside.jpg|600px]]

==WELCOME==

So here it is established, the Concept Car's wiki. The corresponding SVN can be accessed [[Svn|this way]]. This should be a gathering point for all documentation.

For starters, here is a collection of the articels:
* [[The ARM7 board‎]]: bootloader, memory mappings, peripheals
* [[Flashing the ARM7 board]]: how to install the bootloader
* [[Simulink Execution on the ARM7 target]]
* [[AT90CAN128 boards]]
* [[CAN IDs]]: Whats going on on the CAN bus
* [[Simulink settings for generating code]]
* [[Simulink2ARM7]]: Workflow of executing a simulink model on the ARM7 board
* [[Power Supply]]
* [[Student Work]]: Contributions of students
* [[Hardware Engineering]]: Description of the ConceptCar Automotive Hardware

==TODO==

[[TODO List]] with tasks to complete

Consult the [http://meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.

== Getting started ==
* [http://www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list]
* [http://www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]

Hardware Engineering

2009-09-21T13:17:43Z

Quarz: New page: this caption will be filled in the next days.

this caption will be filled in the next days.