Updated some of the architecture/code generation help pages

Signed-off-by: Eisenmann <eisenmann@fortiss.org>

Updated some of the architecture/code generation help pages
465ae3c0 · Martin Eisenmann · 84c9dae8 · 84c9dae8 · 465ae3c0 · 84c9dae8
Commit 465ae3c0 authored 5 years ago by Martin Eisenmann
--- a/org.fortiss.af3.rcp.help/html/ta/pictures/Platform.Example.png
+++ b/org.fortiss.af3.rcp.help/html/ta/pictures/Platform.Example.png
--- a/org.fortiss.af3.rcp.help/html/ta/pictures/Platform.Hierarchic.Adding.Elements.png
+++ b/org.fortiss.af3.rcp.help/html/ta/pictures/Platform.Hierarchic.Adding.Elements.png
--- a/org.fortiss.af3.rcp.help/html/ta/pictures/Platform.Hierarchic.Cluster.png
+++ b/org.fortiss.af3.rcp.help/html/ta/pictures/Platform.Hierarchic.Cluster.png
--- a/org.fortiss.af3.rcp.help/html/ta/pictures/Platform.Hierarchic.Core.png
+++ b/org.fortiss.af3.rcp.help/html/ta/pictures/Platform.Hierarchic.Core.png
--- a/org.fortiss.af3.rcp.help/html/ta/pictures/Platform.Raspberry.Example.png
+++ b/org.fortiss.af3.rcp.help/html/ta/pictures/Platform.Raspberry.Example.png
--- a/org.fortiss.af3.rcp.help/html/ta/platform_architecture.html
+++ b/org.fortiss.af3.rcp.help/html/ta/platform_architecture.html
@@ -38,6 +38,8 @@ that are connected by means of transmission units (abstracting busses or network
 <li><i><a href="platform_architecture_hierarchical.html">Hierarchical platform architecture</a></i>:
 A generic model to describe networked multicore architectures
 in terms of their execution units (e.g., ECUs processors, cores), topology, memories, and I/O ports.</li>
+<li><i><a href="platform_architecture_raspberrypi.html">RaspberryPi platform architecture</a></i>: A model representing RaspberryPi execution units
+that can be connected through a common CAN bus.</li>
 </ul>

 </body>

--- a/org.fortiss.af3.rcp.help/html/ta/platform_architecture_raspberrypi.html
+++ b/org.fortiss.af3.rcp.help/html/ta/platform_architecture_raspberrypi.html
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+
+<html>
+<head>
+	<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+	<title>Using the RaspberryPi Platform Architecture</title>
+</head>
+<body>
+
+<h2><u><font color="#336699">Using the RaspberryPi Platform Architecture</font></u></h2>
+<p>
+The <i>RaspberryPi platform</i> architecture is a platform architecture that represents a RaspberryPi. It can be used to
+<a href="code_generation.html">generate code</a> for one or multiple RaspberryPis, allowing deployment of code to simple embedded hardware.
+</p>
+
+<p>
+The RaspberryPi platform consists of RaspberryPi execution units and CAN busses.
+RaspberryPis can be connected to the CAN bus using <i>CanConnectors</i>.
+RaspberryPis can also have various sensors and actuators such button presses on a Gamepad, MotorControl or Distance Sensors.
+<br>
+The RaspberryPi platform also includes a <i>Light Runner Board</i> representing pre-made board that can be used with a RaspberryPi.
+</p>
+
+<ul>
+<li><i>RaspberryPi</i>: A execution unit representing a RaspberryPi.
+It may have sensors, actuators and CANConnectors.</li>
+<li><i>CANBus</i>: A CAN bus that connects multiple RaspberryPis
+</li>
+<li><i>GamePad/RumblePad</i>: Sensors representing the different buttons found on DualShock and XBox Controllers.
+</li>
+<li><i>Bricklets</i>: Sensors representing the TinkerForge Bricklet sensors.
+</li>
+<li><i>Motor Control</i>: Sensor and Actuator to get or set the desired speed on a motor controller.
+</li>
+<li><i>Camera Server</i>: Sensors returning the results of a LaneDetection server.
+</li>
+<li><i>Control Center</i>: Actuators to display values in a connected Control Center.
+</li>
+<li><i>V2V Communication</i>: Sensors and Actuators to facilitate communication between multiple instances of the model.
+</li>
+</ul>
+
+The following picture shows an example of two RaspberrPis connected over a CAN bus.
+<br><br>
+<img src="./pictures/Platform.Raspberry.Example.png">
+<br><br>
+
+</font>
+</body>
+</html>
\ No newline at end of file