diff --git a/documentation/html/4diacIDE/advancedFeatures.html b/documentation/html/4diacIDE/advancedFeatures.html
index 0dbd75f..cf68357 100644
--- a/documentation/html/4diacIDE/advancedFeatures.html
+++ b/documentation/html/4diacIDE/advancedFeatures.html
@@ -1,7 +1,7 @@
 <!DOCTYPE html>
 <!--
  Copyright (c) 2017-2018 fortiss GmbH
-               2018 Johannes Kepler University Linz
+               2018-2019 Johannes Kepler University Linz
                2019 Andrea Zoitl
   
  All rights reserved. This program and the accompanying materials
@@ -16,6 +16,8 @@
      - minor text corrections
    Andrea Zoitl
      - updated ToC, improved readability
+   Virendra Ashiwal
+   	 -	remove a extra "(" as typo
 -->
 
 <html lang="en">
@@ -86,7 +88,7 @@
 	<img class="center" src="../../html/4diacIDE/img/adapter/addAdapter.png" alt="add adapter to the interface of a function block."/>
 
 	<p>The function blocks used within the following application snippet are part of the TrafficLight example system. 
-	Two different adapter types have been used, <span class="element4diac">ATimeOut</span> in <span class="element4diac">PedLightCtl_AT</span> and <span class="element4diac">E_TimeOut</span>) and <span class="element4diac">ATrafficLight</span> in <span class="element4diac">PedLightCtl_AT</span>.</p>
+	Two different adapter types have been used, <span class="element4diac">ATimeOut</span> in <span class="element4diac">PedLightCtl_AT</span> and <span class="element4diac">E_TimeOut</span> and <span class="element4diac">ATrafficLight</span> in <span class="element4diac">PedLightCtl_AT</span>.</p>
 
 	<p>The <span class="element4diac">PedLightCtl_AT</span> is a basic function block. Within basic function blocks adapters are accessed by <span class="specificText">FB_INTERFACE_NAME.ADAPTER_INTERFACE_NAME</span>. 
 	The elements of the <span class="element4diac">ATimeOut</span> adapter are therefore accessed by <span class="specificText">timeOut.START</span>, <span class="specificText">timeOut.STOP</span> and <span class="specificText">timeOut.TimeOut</span>.</p>
diff --git a/documentation/html/4diacIDE/use4diacLocally.html b/documentation/html/4diacIDE/use4diacLocally.html
index e891690..f222baf 100644
--- a/documentation/html/4diacIDE/use4diacLocally.html
+++ b/documentation/html/4diacIDE/use4diacLocally.html
@@ -97,7 +97,7 @@
           <p>Here are some tips for editing the application:</p>
           <ul>
               <li>If you hover the mouse over a FB or Data or Event connection end, you'll get information about it.</li>
-              <li>If you try to connect Data connections that have incompatible types, you will a red error in the status bar at the lowest part of 4diac-IDE.</li>
+              <li>If you try to connect Data connections that have incompatible types, you will see a red error in the status bar at the lowest part of 4diac-IDE.</li>
               <li>Selected function blocks in the <span class="view4diac">Application Editor</span> can be parameterized using the <span class="view4diac">Properties View</span> typically located below.</li>
           </ul>
         </li>
diff --git a/documentation/html/development/ideUpdateTargetPlatform.html b/documentation/html/development/ideUpdateTargetPlatform.html
new file mode 100644
index 0000000..e57ad03
--- /dev/null
+++ b/documentation/html/development/ideUpdateTargetPlatform.html
@@ -0,0 +1,51 @@
+!DOCTYPE html> 
+<!--
+ Copyright (c) 2019 Johannes Kepler University 
+  
+ All rights reserved. This program and the accompanying materials
+ are made available under the terms of the Eclipse Public License v1.0
+ which accompanies this distribution, and is available at
+ http://www.eclipse.org/legal/epl-v10.html
+ 
+ Contributors:
+   Alois Zoitl - initial API and implementation and/or initial documentation
+-->
+
+<html lang="en">
+<head>
+    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+    <title>Updating the Target Platform used by 4diac IDE</title>
+    <link rel="stylesheet" type="text/css" href="../help.css">
+</head>
+
+<body>
+<h1 id="topOfPage">Updating the Target Platform used by 4diac IDE</h1>
+
+<p>The target platform defines the dependencies of 4diac IDE to other eclipse projects. Currently the Eclipse 4diac requires the following:</p>
+<ul>
+    <li>Eclipse Java Development Tools, org.eclipse.jdt.feature.group</li>
+    <li>Eclipse Platform SDK, org.eclipse.platform.sdk</li>
+    <li>Eclipse Plug-in Development Environment, org.eclipse.pde.feature.group</li>
+    <li>Eclipse Automated Error Reporting, org.eclipse.epp.logging.aeri.feature.feature.group</li>
+    <li>EMF - Eclipse Modeling Framework SDK, org.eclipse.emf.sdk.feature.group</li>
+    <li>GEF (MVC) SDK, org.eclipse.gef.sdk.feature.group</li>
+    <li>Xtext Complete SDK, org.eclipse.xtext.sdk.feature.group</li>
+</ul>
+<p>For upgrading to new Eclipse platform versions the following steps need to be done:</p>
+<ul>
+    <li>Update org.eclipse.fordiac.ide.product.target in the org.eclipse.fordiac.ide.product plugin</li>
+    <li>Update pom.xml in the org.eclipse.fordiac.ide.master plugin. At least the following steps have to be done:
+        <ul> 
+            <li> Check tycho.version</li>
+            <li> Update tycho-repo.url to the new target platform version</li>
+            <li> Check org.eclipse.equinox.executable version range. Attention this has to be done on two places in the file.
+        </ul>
+    </li>
+    <li>Run product from Eclipse IDE using product editor, i.e., press the synchronize button and then the "Launch an Eclipse Application"</li>
+    <li>Run Maven install for pom.xml in the org.eclipse.fordiac.ide.master plugin locally</li>
+    <li>Test if the generated product can be executed. The generated products are in: /org.eclipse.4diac.ide/plugins/org.eclipse.fordiac.ide.product/target/products/org.eclipse.fordiac.ide.product 
+    <li>Push to Gerrit so that CI build can also check if it is working</li>
+</ul>
+
+</body>
+</html>
diff --git a/documentation/html/examples/pidMotor.html b/documentation/html/examples/pidMotor.html
index c03df06..168617f 100644
--- a/documentation/html/examples/pidMotor.html
+++ b/documentation/html/examples/pidMotor.html
@@ -1,249 +1,305 @@
-<!DOCTYPE html> 
-<!--
- Copyright (c) 2017 fortiss GmbH
-  
- All rights reserved. This program and the accompanying materials
- are made available under the terms of the Eclipse Public License v1.0
- which accompanies this distribution, and is available at
- http://www.eclipse.org/legal/epl-v10.html
- 
- Contributors:
-   Jose Cabral
-     - initial API and implementation and/or initial documentation
--->
-
-<html lang="en">
-<head>
-  <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-	<title>PID control on motor position</title>
-	<link rel="stylesheet" type="text/css" href="../help.css">
-</head>
-
-<body>
-
-<h2 id="topOfPage">Implement a PID controller for the position of a motor of the EV3</h2>
-
-	<p>In this tutorial, an implementation of a PID controller for a motor of the EV3 is presented. The position of the motor will be controlled using PWM. The implementation shows all the steps from creating a PID Functional Block in 4DIAC, up to tuning the PID controller and printing the values in a graph.</p>
-
-	<p>A basic usage knowledge of 4DIAC is necessary to follow through the steps.</p>
-
-	<h3>Creating the PID FB</h3>
-
-	<p>The first thing to do is to create the PID functional block. Go to File &rarr; New &rarr; New type. In the pop-up menu, choose the parent folder to store the new FB, choose PID as the Type name, and select Basic.fbt as Type. Click Finish, and the view to edit the new FB will open. First, the interface must be configured. Use the image below to complete it</p>
-
-	<img src="../../html/examples/img/pidMotor/PIDInterface.png" alt="Interface of the PID FB" />
-
-	<p>The interfaces uses Kp, Ki and Kd as constants to be tuned instead of the times Ti and Td. This allow easily to zero the integral part. The interval is the time between requests to the FB and is expected to be constant.</p>
-
-	<p>With the interface set, the next step is to define the ECC and the algorithm. The ECC graphic is really simple, and it looks like the image below. You may have to create the new algorithms with the names shown before filling the graph.</p>
-
-	<img src="../../html/examples/img/pidMotor/PIDECC.png" alt="Interface of the PID FB" />
-
-	<p>With the ECC graph ready, it is time to write the code that will rule the behavior of the FB. In the Properties tab below the ECC graph, in one of the sides-tabs called "All InternalVars" add two variables of type REAL, called LAST_ERROR and INTEGRATION_ACCUM. These variables are part of the FB and retain their values between events.</p>
-
-	<p>Next, we will edit the algorithms specified in the ECC graph. The simple RESET algorithm just initialize the internal variables. The code for RESET is as following:</p>
-	<div class="code">
- <code>LAST_ERROR := 0.0; INTEGRATION_ACCUM := 0.0;</code>
-	</div>
-
-	<p>The REQ algorithm is the following, but since is more complex, it will be explained in parts.</p>
-
-	<div class="code"><code>VAR
-  proportionalPart: REAL;
-  integralPart: REAL;
-  derivativePart: REAL;
-  Ydesired: REAL;
-  errorFiltered: REAL;
-END_VAR;
-
-  IF ABS(InError) &lt;= Noise THEN
-    errorFiltered := 0;
-  ELSE
-    errorFiltered := InError;
-  END_IF;
-  (* calculate proportional part *)
-  proportionalPart := Kp * errorFiltered;
-  
-  (* run integrator *)
-  integralPart := errorFiltered * Interval * Ki + INTEGRATION_ACCUM;
-    
-  (* run derivative*)
-    
-  derivativePart := (errorFiltered - LAST_ERROR) * Kd / Interval;
-  
-  LAST_ERROR := errorFiltered;
-    
-  (* calculate output Y *)
-  Ydesired := proportionalPart + integralPart + derivativePart; 
-    
-  (* check output for limits *)
-  IF Ydesired &gt;= LIM_H THEN
-    Y := LIM_H;
-    IF Ki &lt;&gt; 0.0 THEN
-      IF (errorFiltered &lt; 0 AND Kp &gt; 0) OR (errorFiltered &gt; 0 AND Kp &lt; 0) THEN
-        INTEGRATION_ACCUM := integralPart;
-      END_IF;
-    ELSE
-      INTEGRATION_ACCUM := 0.0;
-    END_IF;
-    LIM := TRUE;
-  ELSIF Ydesired &lt;= LIM_L THEN
-    Y := LIM_L;
-    IF Ki &lt;&gt; 0.0 THEN
-      IF (errorFiltered &gt; 0 AND Kp &gt; 0) OR (errorFiltered &lt; 0 AND Kp &lt; 0)THEN
-        INTEGRATION_ACCUM := integralPart;
-      END_IF;
-    ELSE
-      INTEGRATION_ACCUM := 0.0;
-    END_IF;
-    LIM := TRUE;
-  ELSE
-    Y := Ydesired;
-    INTEGRATION_ACCUM := integralPart;
-    LIM := FALSE;
-  END_IF; 
-</code></div>
-      <p>The part between VAR and END_VAR is the declaration of the local variables that will be used inside this algorithm. The values are not retained between events.</p>
-      
-      <p>The first IF statement </p>
-      <div class="code"><code>IF ABS(InError) &lt;= Noise THEN
-  errorFiltered := 0;
-ELSE
-  errorFiltered := InError;
-END_IF;</code></div>
-      
-      <p>is to turn off the PID when the value of the error is below the Noise specified in the input. Only when the error is bigger than the Noise threshold, the computation of the PID will be done.</p>
-      
-      <p>The next part is the core of the PID computation. All the values are stored in local variables before mirroring then to the actual outputs and internal variables.</p>
-      
-      <div class="code"><code>(* calculate proportional part *)
-proportionalPart := Kp * errorFiltered;
-  
-(* run integrator *)
-integralPart := errorFiltered * Interval * Ki + INTEGRATION_ACCUM;
-    
-(* run derivative*)
-derivativePart := (errorFiltered - LAST_ERROR) * Kd / Interval;
-  
-LAST_ERROR := errorFiltered;
-    
-(* calculate output Y *)
-Ydesired := proportionalPart + integralPart + derivativePart;</code></div>
-      
-      <p>The last part is really important, because it limits the output and eliminates the integral windup. Because the motor PWM can havae values between -100 and 100, if the output is outside this range, the PID should limit this value. More information about integration windup can be found in the internet, but basically, when the error is too big, the integration part doesn't work as ideally suppossed and insert unexpected behavior to the controller. </p>
-      
-      <div class="code"><code>(* check output for limits *)
-IF Ydesired &gt;= LIM_H THEN
-  Y := LIM_H;
-  IF Ki &lt;&gt; 0.0 THEN
-    IF (errorFiltered &lt; 0 AND Kp &gt; 0) OR (errorFiltered &gt; 0 AND Kp &lt; 0) THEN
-      INTEGRATION_ACCUM := integralPart;
-    END_IF;
-  ELSE
-    INTEGRATION_ACCUM := 0.0;
-  END_IF;
-  LIM := TRUE;
-ELSIF Ydesired &lt;= LIM_L THEN
-  Y := LIM_L;
-  IF Ki &lt;&gt; 0.0 THEN
-    IF (errorFiltered &gt; 0 AND Kp &gt; 0) OR (errorFiltered &lt; 0 AND Kp &lt; 0)THEN
-      INTEGRATION_ACCUM := integralPart;
-    END_IF;
-  ELSE
-    INTEGRATION_ACCUM := 0.0;
-  END_IF;
-  LIM := TRUE;
-ELSE
-  Y := Ydesired;
-  INTEGRATION_ACCUM := integralPart;
-  LIM := FALSE;
-END_IF; </code></div>
-
-	<p>
- The IF and ELSEIF are the limits of the value, and in the ELSE is where allowed values are processed. The output limitation is straightforward, but the windup solution can be confusing. What is done is to activate the integration part only when the desired output is inside the limits (in the ELSE), OR when it is outside the limits AND the error is forcing the way back inside the limits. The source of information about this can be found <a target="_blank" href="https://jagger.berkeley.edu/~pack/me132/Section15.pdf">here.</a>
-	</p>
-
-	<p>Whit the algorithms done, the FB is ready to be exported and compiled with FORTE.</p>
-
-	<h3>Exporting and compiling with FORTE for the Ev3</h3>
-
-	<p>Once the FB is ready, go to File &rarr; Export... and select 4DIAC &rarr; 4DIAC Type Export. Then explore the folder tree on the left and select the PID FB created on the right. Choose where to export and then click Finish.</p>
-
-	<p>To get the source code ready to compile FORTE with the created FB, the generated .cpp and .h files have to be added to the CMAKE configuration. The easiest way to do it is to put both files in the folder src/modules/lms_ev3 and add to the CMakeLists.txt file in that folder, the following line at the end.</p>
-
-	<div class="code">forte_add_sourcefile_hcpp(PID)</div>
-
-	<p>
- The next thing to do is to compile FORTE for the EV3. The easiest way to do it is to copy all the code to the EV3, get the compiling tools inside the EV3 and compile it. The process is really slow compared if it is done in a normal computer, but for one time is much faster than setting all the cross-compiling environment explained <a target="_blank" href="http://www.ev3dev.org/docs/tutorials/using-brickstrap-to-cross-compile/">here.</a> More details are presented in the <a href="../../html/installation/legoMindstormEv3.html#ev3_introduction">section</a> above.
-	</p>
-
-	<h3>Creating the PID Application in 4DIAC</h3>
-
-	<p>After FORTE with the PID can run in the EV3, is time to create the application that will run on it to contorl the motor's position, and store the values. The application will be shown in parts, for a better understanding.</p>
-
-	<h4>ON/OFF the controller</h4>
-
-	<p>The first part of the application can be made in different ways, which allows a better control of the tests. In this example, it consists of two push buttons connected to in2 and in4, one for starting the motor and PID and the other one to reset all parameters (which also stops the motor). It has a cycle to read both buttons waiting for a rising trigger on them which sends the event to the enable or reset of the motor.</p>
-
-	<p>The initialization of the StartButton FB is done from the COLD START FB when configuring the system.</p>
-
-	<img src="../../html/examples/img/pidMotor/PIDButtonPart.png" alt="Button part of the PID application" />
-
-	<h4>Reading the system</h4>
-
-	<p>This part begins with a cycle block that outputs an event every 100ms, that will triger the PID computation. The cycle starts when the motor is enabled, and stops when the motor is reset. This cycle, triggers the reading of the system, in this case the position of the motor. This position is read as WORD (it should be a double, actually, but for now, it can be limited to a WORD) and then is converted to an INT that allows negative values (the WORD_TO_INT block was updated to allow negative values), and then to REAL in order to compute the difference to the set point stablished by the user (INT#1000 in the example). The F_SUB block expect REAL values, and in the input IN1, the set point is given. Take a look that at the output of the WORD_TO_INT block, there is another conversion to a STRING, this conversion is sent to the PC to store the values of the position to plot it. In the last part, it will be shown how is it done.</p>
-
-	<img src="../../html/examples/img/pidMotor/PIDReadingPart.png" alt="Reading part of the PID application" />
-
-	<h4>Input of the PID controller</h4>
-
-	<p>This part takes the error as the difference of the set point and the position read from the motor, and sends it to the PID controller. The rest of the inputs of it are user defined. The gains (Kp, Ki, and Kd) are tuned according to the method. In this example, the Zeigler-Nichols was used, and it will be seen later. The interval is 0.1 that corresponds to the 100ms of the PID Cycle. The limits corresponds to the limit values of the output, in this case the PWM of the motor.</p>
-
-	<img src="../../html/examples/img/pidMotor/PIDInPIDPart.png" alt="Input of PID" />
-
-	<h4>Output of the PID controller</h4>
-
-	<p>The last part corresponds to the output of the PID controller and the sending of the information the a log in a PC. The output of the PID is converted to INT and then to WORD to write then the output to the PWM of the motor. Also, the INT value is converted to STRING, similar to the position in the input part, and once both conversions (position and output) are done, they are written to a file using the CSV_WRITER_2 FB from the UTILS module. This FB allows to write 2 values (SD_1 and SD_2) as CSV. The block is in other color, because is in another device, not in the EV3.</p>
-
-	<img src="../../html/examples/img/pidMotor/PIDOutputPart.png" alt="Output of PID" />
-
-	<h4>Configuring the system</h4>
-
-	<p>Now that the application is done, some other configurations are needed in the system. The first thing is to create both devices and connect them using the Ethernet segment. In the EV3 resource, the first thing to do is to connect the COLD START to the initialization of the StartButton as said before.</p>
-
-  <p>The other configuration in the EV3 resource is the publishing of the conversions of the position and output of the PID. Using a PUBLISH_2_0 with both input and the multicast UDP ID (in this case, 239.192.0.2:65000), and the REQ triggerred by the E_REND FB from the application. With this, the EV3 will send the position and output of the PID to the ID address everytime both conversion are done.</p>
-
-	<img src="../../html/examples/img/pidMotor/PIDPublish.png" alt="Publishing the data to the PC" />
-
-	<p>The configuration of the resource of the PC where the data will be stored, consists of a SUBSCRIBE_2 FB that will receive the information published by the EV3. The ID is the same as the publisher, and the outputs are converted using the STRING2STRING because the output is an ANY type. When both conversion are done, they are written in the file. Take in account that the CSV_WRITER FB doesn't flush inmediately the output, so the FORTE application must exit to read the information in the file.</p>
-
-	<img src="../../html/examples/img/pidMotor/PIDSubscribe.png" alt="Subscribe to data from EV3" />
-
-	<p> NOTE: In windows machines, the used multicast address is not always detected and the packets from the EV3 don't arrive to the FORTE application in the PC. This happens often if the PC is connected to the EV3 through an ad-hoc connection. To overcome this, try adding the address route with gateway to your own machine in the as presented in the Troubleshooting part at the bottom of the <a target="_blank" href="../../html/examples/bbbTraficControl.html#troubleshooting">Traffic Control with BBB example</a></p>
-
-	<h3>Tuning the PID</h3>
-
-	<p> With the application ready and working, it is presented now the <a target="_blank" href="https://en.wikipedia.org/wiki/Ziegler%E2%80%93Nichols_method">Ziegler-Nichols method</a> to tune the PID. The basic idea is to turn off the integral and derivative parts, and increase Kp until the output has stable and constant oscillations. The value of Kp that produces this output is called Ku and the oscillation's period at this Ku is called Tu. With these two values, the values of the Kp, Ki, and Kd are chosen according to the table of the link before. Remember that Kd = Kp/Ti and Ki = Kp*Td.</p>
-
-	<p>The set point is the position 1000. The first value of Kp is 1 and produces a non oscillating result. With Kp = 2, it takes longer, but still without stable oscillations. With Kp = 3, the results show a stable oscillation. So, the critical Ku value must be between 2 and 3. After a binary search between 2 and 3, it is found that Ku = 2.18 and its graph is shown also below. From the data, it can be seen that the oscillations have a period of 600ms (0.6s).</p>
-
-	<img src="../../html/examples/img/pidMotor/PIDKp.png" alt="Graphs of testing Kp" />
-
-	<p>With the values of Ku and Tu, it is computed the values of Kp, Ki and Kd for the PID controller from the table. The values are Kp = 1.308, Ki = 4.36 and Kd = 0.0981. With this values, the PID controller is again tested and the result is as follow:</p>
-
-	<img src="../../html/examples/img/pidMotor/PIDTuned.png" alt="Final tun of the PID controller" />
-
-<h1>Where to go from here?</h1>
-
-<p>Go back to Examples index:</p>
-
-<p><a href="../../html/examples/examplesIndex.html">Examples Index</a></p>
-
-<p>If you want to go back to the Start Here page, we leave you here a fast access</p>
-
-<p><a href="../../html/startHere/startHere.html">Start Here page</a></p>
-
-<p class="goToTop"><a href="#topOfPage">Go to top</a></p>
-
-</body>
-</html>
+<!DOCTYPE html> 
+<!--
+ Copyright (c) 2017 fortiss GmbH
+               2019 Johannes Kepler University Linz
+  
+ All rights reserved. This program and the accompanying materials
+ are made available under the terms of the Eclipse Public License v1.0
+ which accompanies this distribution, and is available at
+ http://www.eclipse.org/legal/epl-v10.html
+ 
+ Contributors:
+   Jose Cabral
+     - initial API and implementation and/or initial documentation
+   Bianca Wiesmayr
+   	 - updated documentation
+-->
+
+<html lang="en">
+<head>
+  <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+	<title>PID control on motor position</title>
+	<link rel="stylesheet" type="text/css" href="../help.css">
+</head>
+
+<body>
+
+<h2 id="topOfPage">Implement a PID controller for the position of an EV3 motor</h2>
+
+	<p>In this tutorial, an implementation of a PID controller for an EV3 motor is presented. 
+	The position of the motor will be controlled using PWM. 
+	The implementation shows all the steps from creating a PID Functional Block in 4diac IDE, up to tuning the PID controller and printing the values in a graph.</p>
+
+	<p>A basic usage knowledge of Eclipse 4diac is necessary to follow through the steps.</p>
+
+	<h3>Creating the PID FB</h3>
+
+	<p>The first thing to do is to create the PID Function Block.
+	Go to File &rarr; New &rarr; New type. 
+	In the pop-up menu, choose the parent folder to store the new FB, choose PID as the Type name, and select Basic as Type. 
+	Click Finish, and the view to edit the new FB opens. 
+	First, the interface must be configured. 
+	Use the image below to complete it:</p>
+
+	<img src="../../html/examples/img/pidMotor/PIDInterface.png" alt="Interface of the PID FB" />
+
+	<p>The interface uses Kp, Ki and Kd as constants to be tuned instead of the times Ti and Td. 
+	This allow to easily zero the integral part. 
+	The interval is the time between requests to the FB and is expected to be constant.</p>
+
+	<p>With the interface set, the next step is to define the ECC and the algorithm. 
+	The ECC graph is really simple, and it should look like the image below. 
+	You may have to create the new algorithms with the names shown before filling the graph.</p>
+
+	<img src="../../html/examples/img/pidMotor/PIDECC.png" alt="Interface of the PID FB" />
+
+	<p>With the ECC graph ready, it is time to write the code that will rule the behavior of the FB. 
+	In the Properties tab below the ECC graph, in one of the sides-tabs called "All InternalVars" add two variables of type REAL, called LAST_ERROR and INTEGRATION_ACCUM. 
+	These variables are part of the FB and retain their values between events.</p>
+
+	<p>Next, we will edit the algorithms specified in the ECC graph. 
+	The simple RESET algorithm just initialize the internal variables. 
+	The code for RESET is as following:</p>
+	<div class="code">
+ <code>LAST_ERROR := 0.0; 
+ INTEGRATION_ACCUM := 0.0;</code>
+	</div>
+
+	<p>The REQ algorithm is the following, but since is more complex, it will be explained in parts.</p>
+
+	<div class="code"><code>VAR
+  proportionalPart: REAL;
+  integralPart: REAL;
+  derivativePart: REAL;
+  Ydesired: REAL;
+  errorFiltered: REAL;
+END_VAR;
+
+  IF ABS(InError) &lt;= Noise THEN
+    errorFiltered := 0;
+  ELSE
+    errorFiltered := InError;
+  END_IF;
+  (* calculate proportional part *)
+  proportionalPart := Kp * errorFiltered;
+  
+  (* run integrator *)
+  integralPart := errorFiltered * Interval * Ki + INTEGRATION_ACCUM;
+    
+  (* run derivative*)
+    
+  derivativePart := (errorFiltered - LAST_ERROR) * Kd / Interval;
+  
+  LAST_ERROR := errorFiltered;
+    
+  (* calculate output Y *)
+  Ydesired := proportionalPart + integralPart + derivativePart; 
+    
+  (* check output for limits *)
+  IF Ydesired &gt;= LIM_H THEN
+    Y := LIM_H;
+    IF Ki &lt;&gt; 0.0 THEN
+      IF (errorFiltered &lt; 0 AND Kp &gt; 0) OR (errorFiltered &gt; 0 AND Kp &lt; 0) THEN
+        INTEGRATION_ACCUM := integralPart;
+      END_IF;
+    ELSE
+      INTEGRATION_ACCUM := 0.0;
+    END_IF;
+    LIM := TRUE;
+  ELSIF Ydesired &lt;= LIM_L THEN
+    Y := LIM_L;
+    IF Ki &lt;&gt; 0.0 THEN
+      IF (errorFiltered &gt; 0 AND Kp &gt; 0) OR (errorFiltered &lt; 0 AND Kp &lt; 0)THEN
+        INTEGRATION_ACCUM := integralPart;
+      END_IF;
+    ELSE
+      INTEGRATION_ACCUM := 0.0;
+    END_IF;
+    LIM := TRUE;
+  ELSE
+    Y := Ydesired;
+    INTEGRATION_ACCUM := integralPart;
+    LIM := FALSE;
+  END_IF; 
+</code></div>
+      <p>The part between VAR and END_VAR is the declaration of the local variables that will be used inside this algorithm. 
+      The values are not retained between events.</p>
+      
+      <p>The first IF-statement </p>
+      <div class="code"><code>IF ABS(InError) &lt;= Noise THEN
+  errorFiltered := 0;
+ELSE
+  errorFiltered := InError;
+END_IF;</code></div>
+      
+      <p>turns off the PID when the value of the error is below the Noise specified in the input. 
+      Only when the error is bigger than the Noise threshold, the computation of the PID will be done.</p>
+      
+      <p>The next part is the core of the PID computation. 
+      All the values are stored in local variables before mirroring them to the actual outputs and internal variables.</p>
+      
+      <div class="code"><code>(* calculate proportional part *)
+proportionalPart := Kp * errorFiltered;
+  
+(* run integrator *)
+integralPart := errorFiltered * Interval * Ki + INTEGRATION_ACCUM;
+    
+(* run derivative*)
+derivativePart := (errorFiltered - LAST_ERROR) * Kd / Interval;
+  
+LAST_ERROR := errorFiltered;
+    
+(* calculate output Y *)
+Ydesired := proportionalPart + integralPart + derivativePart;</code></div>
+      
+      <p>The last part is really important, because it limits the output and eliminates the integral windup. 
+      Because the motor PWM can have values between -100 and 100, if the output is outside this range, the PID should limit this value. 
+      More information about integration windup can be found in the internet, but basically, when the error is too big, the integration part doesn't work as supposed to and inserts unexpected behavior to the controller. </p>
+      
+      <div class="code"><code>(* check output for limits *)
+IF Ydesired &gt;= LIM_H THEN
+  Y := LIM_H;
+  IF Ki &lt;&gt; 0.0 THEN
+    IF (errorFiltered &lt; 0 AND Kp &gt; 0) OR (errorFiltered &gt; 0 AND Kp &lt; 0) THEN
+      INTEGRATION_ACCUM := integralPart;
+    END_IF;
+  ELSE
+    INTEGRATION_ACCUM := 0.0;
+  END_IF;
+  LIM := TRUE;
+ELSIF Ydesired &lt;= LIM_L THEN
+  Y := LIM_L;
+  IF Ki &lt;&gt; 0.0 THEN
+    IF (errorFiltered &gt; 0 AND Kp &gt; 0) OR (errorFiltered &lt; 0 AND Kp &lt; 0)THEN
+      INTEGRATION_ACCUM := integralPart;
+    END_IF;
+  ELSE
+    INTEGRATION_ACCUM := 0.0;
+  END_IF;
+  LIM := TRUE;
+ELSE
+  Y := Ydesired;
+  INTEGRATION_ACCUM := integralPart;
+  LIM := FALSE;
+END_IF; </code></div>
+
+	<p>
+ The IF and ELSEIF are the limits of the value, and in the ELSE allowed values are processed. 
+ The output limitation is straightforward, but the windup solution can be confusing. 
+ What is done is to activate the integration part only when the desired output is inside the limits (in the ELSE), OR when it is outside the limits AND the error is forcing the way back inside the limits. 
+ Information about this can be found <a target="_blank" href="https://jagger.berkeley.edu/~pack/me132/Section15.pdf">here.</a>
+	</p>
+
+	<p>With the algorithms done, the FB is ready to be exported and compiled with 4diac FORTE.</p>
+
+	<h3>Exporting and compiling with FORTE for the EV3</h3>
+
+	<p>Once the FB is ready, go to File &rarr; Export... and select 4diac IDE &rarr; 4diac IDE Type Export. 
+	Then explore the folder tree on the left and select the PID FB created on the right. 
+	Choose where to export and then click Finish.</p>
+
+	<p>To get the source code ready for compiling your FORTE with the created FB, the generated .cpp and .h files have to be added to the CMake configuration. 
+	The easiest way to do that is to put both files into the folder src/modules/lms_ev3 and add a file CMakeLists.txt in that folder, with the following line at the end:</p>
+
+	<div class="code">forte_add_sourcefile_hcpp(PID)</div>
+
+	<p>
+ The next thing to do is to compile FORTE for the EV3. 
+ The easiest way to do it is to copy all the code to the EV3, get the compiling tools inside the EV3 and compile it. 
+ The process is really slow compared if it is done in a normal computer, but for compiling once it is much faster than setting all the cross-compiling environment explained <a target="_blank" href="http://www.ev3dev.org/docs/tutorials/using-brickstrap-to-cross-compile/">here.</a> 
+ More details are presented in the <a href="../../html/installation/legoMindstormEv3.html#ev3_introduction">section</a> above.
+	</p>
+
+	<h3>Creating the PID Application in 4diac IDE</h3>
+
+	<p>After FORTE with the PID runs in the EV3, is time to create the application that will run on it to control the motor position, and store the values. 
+	The application will be shown in parts, for a better understanding.</p>
+
+	<h4>ON/OFF the controller</h4>
+
+	<p>The first part of the application can be made in different ways, which allows a better control of the tests. 
+	In this example, it consists of two push buttons connected to in2 and in4, one for starting the motor and PID, and the other one to reset all parameters (which also stops the motor). 
+	It has a cycle to read both buttons waiting for a rising trigger on them which sends the event to the enable or reset of the motor.</p>
+
+	<p>The initialization of the StartButton FB is done from the COLD START FB when configuring the system.</p>
+
+	<img src="../../html/examples/img/pidMotor/PIDButtonPart.png" alt="Button part of the PID application" />
+
+	<h4>Reading the system</h4>
+
+	<p>This part begins with a cycle block that outputs an event every 100ms, that will trigger the PID computation. 
+	The cycle starts when the motor is enabled, and stops when the motor is reset. 
+	The cycle triggers the reading of the system, in this case the position of the motor. 
+	This position is read as WORD (it should be a double, actually, but for now, it can be limited to a WORD) and is then converted to an INT that allows negative values (the WORD_TO_INT block was updated to allow negative values), and then to REAL in order to compute the difference to the set point established by the user (INT#1000 in the example). 
+	The F_SUB block expects REAL values, and in the input IN1, the set point is given. Take a look that at the output of the WORD_TO_INT block, there is another conversion to a STRING, this conversion is sent to the PC to store the values of the position to plot it. In the last part, it will be shown how is it done.</p>
+
+	<img src="../../html/examples/img/pidMotor/PIDReadingPart.png" alt="Reading part of the PID application" />
+
+	<h4>Input of the PID controller</h4>
+
+	<p>This part takes the error as the difference of the set point and the position read from the motor, and sends it to the PID controller. The rest of the inputs of it are user defined. The gains (Kp, Ki, and Kd) are tuned according to the method. In this example, the Zeigler-Nichols was used, and it will be seen later. The interval is 0.1 that corresponds to the 100ms of the PID Cycle. The limits corresponds to the limit values of the output, in this case the PWM of the motor.</p>
+
+	<img src="../../html/examples/img/pidMotor/PIDInPIDPart.png" alt="Input of PID" />
+
+	<h4>Output of the PID controller</h4>
+
+	<p>The last part corresponds to the output of the PID controller and the sending of the information the a log in a PC. The output of the PID is converted to INT and then to WORD to write then the output to the PWM of the motor. Also, the INT value is converted to STRING, similar to the position in the input part, and once both conversions (position and output) are done, they are written to a file using the CSV_WRITER_2 FB from the UTILS module. This FB allows to write 2 values (SD_1 and SD_2) as CSV. The block is in other color, because is in another device, not in the EV3.</p>
+
+	<img src="../../html/examples/img/pidMotor/PIDOutputPart.png" alt="Output of PID" />
+
+	<h4>Configuring the system</h4>
+
+	<p>Now that the application is done, some other configurations are needed in the system. 
+	The first thing is to create both devices and connect them using the Ethernet segment. 
+	In the EV3 resource, first connect the COLD START to the initialization of the StartButton as mentioned before.</p>
+
+  <p>The other configuration in the EV3 resource is the publishing of the conversions of the position and output of the PID. Using a PUBLISH_2_0 with both input and the multicast UDP ID (in this case, 239.192.0.2:65000), and the REQ triggerred by the E_REND FB from the application. With this, the EV3 will send the position and output of the PID to the ID address everytime both conversion are done.</p>
+
+	<img src="../../html/examples/img/pidMotor/PIDPublish.png" alt="Publishing the data to the PC" />
+
+	<p>The configuration of the resource of the PC where the data will be stored, consists of a SUBSCRIBE_2 FB that will receive the information published by the EV3. The ID is the same as the publisher, and the outputs are converted using the STRING2STRING because the output is an ANY type. When both conversion are done, they are written in the file. Take in account that the CSV_WRITER FB doesn't flush inmediately the output, so the FORTE application must exit to read the information in the file.</p>
+
+	<img src="../../html/examples/img/pidMotor/PIDSubscribe.png" alt="Subscribe to data from EV3" />
+
+	<p> NOTE: In Windows machines, the used Multicast address is not always detected and the packets from the EV3 don't arrive to the FORTE application in the PC. 
+	This happens often if the PC is connected to the EV3 through an ad-hoc connection. 
+	To overcome this, try adding the address route with gateway to your own machine in the as presented in the Troubleshooting part at the bottom of the <a href="../../html/examples/bbbTraficControl.html#troubleshooting">Traffic Control with BBB example</a></p>
+
+	<h3>Tuning the PID</h3>
+
+	<p> With the application ready and working, the <a target="_blank" href="https://en.wikipedia.org/wiki/Ziegler%E2%80%93Nichols_method">Ziegler-Nichols method</a> is presented for tuning the PID. 
+	The basic idea is to turn off the integral and derivative parts, and increase Kp until the output has stable and constant oscillations. 
+	The value of Kp that produces this output is called Ku and the oscillation period at this Ku is called Tu. 
+	With these two values, the values of the Kp, Ki, and Kd are chosen according to the table of the link before. 
+	Remember that Kd = Kp/Ti and Ki = Kp*Td.</p>
+
+	<p>The set point is the position 1000. 
+	The first value of Kp is 1 and produces a non oscillating result. 
+	With Kp = 2, it takes longer, but still without stable oscillations. 
+	With Kp = 3, the results show a stable oscillation. 
+	So, the critical Ku value must be between 2 and 3. 
+	After a binary search between 2 and 3, it is found that Ku = 2.18 and its graph is shown also below. 
+	From the data, it can be seen that the oscillations have a period of 600ms (0.6s).</p>
+
+	<img src="../../html/examples/img/pidMotor/PIDKp.png" alt="Graphs of testing Kp" />
+
+	<p>With the values of Ku and Tu, the values of Kp, Ki and Kd for the PID controller are computed from the table. 
+	The values are Kp = 1.308, Ki = 4.36 and Kd = 0.0981. 
+	With these values, the PID controller is again tested and the result is as follows:</p>
+
+	<img src="../../html/examples/img/pidMotor/PIDTuned.png" alt="Final tun of the PID controller" />
+
+<h1>Where to go from here?</h1>
+
+<p>Go back to Examples index:</p>
+
+<p><a href="../../html/examples/examplesIndex.html">Examples Index</a></p>
+
+<p>If you want to go back to the Start Here page, we leave you here a fast access</p>
+
+<p><a href="../../html/startHere/startHere.html">Start Here page</a></p>
+
+<p class="goToTop"><a href="#topOfPage">Go to top</a></p>
+
+</body>
+</html>
diff --git a/documentation/html/parameters/parameters.html b/documentation/html/parameters/parameters.html
index d3ec577..34b5e23 100644
--- a/documentation/html/parameters/parameters.html
+++ b/documentation/html/parameters/parameters.html
@@ -1,7 +1,7 @@
 <!DOCTYPE html>
 <!--
  Copyright (c) 2016 - 2017 fortiss GmbH
- 			   2019 Andrea Zoitl
+ 	       2019 Andrea Zoitl, Johannes Kepler University Linz
   
  All rights reserved. This program and the accompanying materials
  are made available under the terms of the Eclipse Public License v1.0
@@ -13,6 +13,8 @@
      - initial API and implementation and/or initial documentation
    Andrea Zoitl
      - fixed 4diac branding, corrected links, improved readability
+   Bianca Wiesmayr
+   	 - fixed minor errors
 -->
 
 <html lang="en">
@@ -51,7 +53,7 @@
 
 	<p>
 		The following picture shows an example application from the <a
-			href="../4diacIDE/use4diacLocally.html">Blinking tutorial</a> which
+			href="../../html/4diacIDE/use4diacLocally.html">Blinking tutorial</a> which
 		is extended with IX and QX function blocks. The extended application
 		periodically toggles on pin number 8. It can be started and stopped
 		via pin number 2. You can connect an LED to obtain a blinking light.
@@ -303,7 +305,7 @@
 		details will be forgotten if not used. We recommend to give a quick
 		reading in order to know what can be accessed using 4diac&nbsp;FORTE. The <a
 			href="../../html/examples/pidMotor.html">example</a> presents the
-		control a motor using a PID controller.
+		control of a motor using a PID controller.
 	</p>
 
 <!--***************-->
@@ -592,7 +594,7 @@
 				specific. It must be used with ID. The position can be written, wich
 				sets the position to the desired value.</p>
 
-			<p>The 'speed' reads the current speed in positions by second. It
+			<p>The 'speed' reads the current speed in positions per second. It
 				must be used with IW.</p>
 
 			<p>The 'rot' reads the motor specication of how many steps are in
diff --git a/head.php b/head.php
index 3ccb5c8..e3cabbc 100644
--- a/head.php
+++ b/head.php
@@ -6,9 +6,9 @@
 <script src="//www.eclipse.org/eclipse.org-common/themes/solstice/public/javascript/vendor/cookieconsent/default.min.js"></script>
 
 <?php
-require_once ($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/app.class.php");
+/*require_once ($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/app.class.php");
 $App = new App();
 $Theme = $App->getThemeClass("quicksilver");
-print $Theme->getGoogleTagManager();
+print $Theme->getGoogleTagManager();*/
 ?>