Deployed dfd6b4a to docs-develop with MkDocs 1.5.3 and mike 1.1.2

docs-develop/connect-field-devices/asset-implemetation/index.html

@@ -4579,59 +4579,59 @@ <h2 id="channel-example">Channel Example</h2>
 <td>2051</td>
 </tr>
 <tr>
-<td>LED4 RED</td>
+<td>LED4_RED</td>
 <td>COILS</td>
 <td>2052</td>
 </tr>
 <tr>
-<td>LED4 GREEN</td>
+<td>LED4_GREEN</td>
 <td>COILS</td>
 <td>2053</td>
 </tr>
 <tr>
-<td>LED4 BLUE</td>
+<td>LED4_BLUE</td>
 <td>COILS</td>
 <td>2054</td>
 </tr>
 <tr>
-<td>Counter 3</td>
+<td>Counter_3</td>
 <td>INPUT REGISTERS</td>
 <td>515</td>
 </tr>
 <tr>
-<td>Quad Counter</td>
+<td>Quad_Counter</td>
 <td>INPUT REGISTERS</td>
 <td>520</td>
 </tr>
 <tr>
-<td>Toggle 4</td>
+<td>Toggle_4</td>
 <td>DISCRETE INPUTS</td>
 <td>2052</td>
 </tr>
 <tr>
-<td>Toggle 5</td>
+<td>Toggle_5</td>
 <td>DISCRETE INPUTS</td>
 <td>2053</td>
 </tr>
 <tr>
-<td>Toggle 6</td>
+<td>Toggle_6</td>
 <td>DISCRETE INPUTS</td>
 <td>2054</td>
 </tr>
 <tr>
-<td>Reset Counter 3</td>
+<td>Reset_Counter_3</td>
 <td>COILS</td>
 <td>3075</td>
 </tr>
 <tr>
-<td>Reset Quad Counter</td>
+<td>Reset_Quad_Counter</td>
 <td>COILS</td>
 <td>3084</td>
 </tr>
 </tbody>
 </table>
 <p>The corresponding Channels definition in the Asset is as follows:</p>
-<p><img alt="" src="../images/Devkit.png" /></p>
+<p><img alt="" src="../images/modbus_asset.png" /></p>
 <p>As shown in the previous image, the Channel definition in an Asset results easily mappable to what available in a generic PLC documentation. </p>
 <p>Once defined the Channels in an Asset, a simple Java application that leverages the Asset API can easily communicate with the Field device by simply referring to the specific Channel of interest.</p>
 <h2 id="channel-definition">Channel Definition</h2>

docs-develop/connect-field-devices/driver-and-assets/index.html

@@ -4430,67 +4430,67 @@ <h2 id="channel-example">Channel Example</h2>
 <td>2051</td>
 </tr>
 <tr>
-<td>LED4 RED</td>
+<td>LED4_RED</td>
 <td>COILS</td>
 <td>2052</td>
 </tr>
 <tr>
-<td>LED4 GREEN</td>
+<td>LED4_GREEN</td>
 <td>COILS</td>
 <td>2053</td>
 </tr>
 <tr>
-<td>LED4 BLUE</td>
+<td>LED4_BLUE</td>
 <td>COILS</td>
 <td>2054</td>
 </tr>
 <tr>
-<td>Counter 3</td>
+<td>Counter_3</td>
 <td>INPUT REGISTERS</td>
 <td>515</td>
 </tr>
 <tr>
-<td>Quad Counter</td>
+<td>Quad_Counter</td>
 <td>INPUT REGISTERS</td>
 <td>520</td>
 </tr>
 <tr>
-<td>Toggle 4</td>
+<td>Toggle_4</td>
 <td>DISCRETE INPUTS</td>
 <td>2052</td>
 </tr>
 <tr>
-<td>Toggle 5</td>
+<td>Toggle_5</td>
 <td>DISCRETE INPUTS</td>
 <td>2053</td>
 </tr>
 <tr>
-<td>Toggle 6</td>
+<td>Toggle_6</td>
 <td>DISCRETE INPUTS</td>
 <td>2054</td>
 </tr>
 <tr>
-<td>Reset Counter 3</td>
+<td>Reset_Counter_3</td>
 <td>COILS</td>
 <td>3075</td>
 </tr>
 <tr>
-<td>Reset Quad Counter</td>
+<td>Reset_Quad_Counter</td>
 <td>COILS</td>
 <td>3084</td>
 </tr>
 </tbody>
 </table>
 <p>The corresponding Channels definition in the Asset is as follows:</p>
-<p><img alt="" src="../images/Devkit.png" style="border-radius: 7px;" /></p>
+<p><img alt="" src="../images/modbus_asset.png" style="border-radius: 7px;" /></p>
 <p>As shown in the previous image, the Channel definition in an Asset results easily mappable to what available in a generic PLC documentation. </p>
 <p>Once defined the Channels in an Asset, a simple Java application that leverages the Asset API can easily communicate with the Field device by simply referring to the specific Channel of interest.</p>
 <h2 id="drivers-and-assets-in-kura-administrative-ui">Drivers and Assets in Kura Administrative UI</h2>
 <p>Kura provides a specific section of the UI to allow users to manage the different instances of Drivers and Assets.
 Using the Kura Web UI the user can instantiate and manage Drivers</p>
 <p><img alt="" src="../images/Driver_config.png" style="border-radius: 7px;" /></p>
-<p>but also can manage Assets instances based on existing drivers.</p>
-<p><img alt="" src="../images/Asset_config.png" style="border-radius: 7px;" /></p>
+<p>but also can manage Assets instances based on existing drivers. By default the following columns are hidden: <strong>scale</strong>, <strong>offset</strong>, <strong>scaleoffset.type</strong>, <strong>unit</strong>. You can manage the visible columns with the related button in the  button bar.</p>
+<p><img alt="" src="../images/modbus_asset_fullview.png" style="border-radius: 7px;" /></p>
 <p>The user interface allows also to perform specific reads on the configured Assets' channels clicking on the Data tab for the selected Asset.</p>
 <p><img alt="" src="../images/Asset_data.png" style="border-radius: 7px;" /></p>