Skip to content
PDF

Setup and Default Operation#

This section will walk you through the hardware setup, explain the default operation of the kit and give an introduction to the Management System.

Setting up the Hardware#

The MFN 100 is delivered in a separate box and has to be mounted on the kit. A mating connector is already connected to the power supply. Also, the SIMATIC ET 200SP I/O module is already connected to the I/O port of the MFN 100 with a network cable. In order to completely set up the kit, you will need a power cord and two network cables.

  1. Mount the MFN 100 on the DIN rail on the left side of the kit.

    Note

    If you need help with mounting the MFN 100 on the DIN rail, please refer to the Hardware Installation guide enclosed in the box of the MFN 100.

  2. Plug the mating connector that is connected to the power supply into the bottom side of the MFN 100.

  3. Connect port 2 of the MFN to a DHCP-enabled network with access to the Management System or internet access if the Management System is hosted by TTTech Industrial.

    Note

    If you are not sure how to allow external devices to connect to your network, please contact your IT administrator.

  4. Connect the power cord to the power supply and to a power outlet. Make sure the power supply is turned off.

  5. Push the button to switch on the power supply.

The MFN 100 will start after a few minutes and the blue light will turn on. All necessary services are initiated and after that, data is sent to the Management System.

Default Operation#

The Nerve Blue Kit comes with two default applications which can replicate scenarios found in industrial automation. The applications allow for data to be generated at the I/O, be acquired by the MFN 100 via Ethernet fieldbus, translated to OPC UA and be sent to the cloud for visualization. The data can be generated as a continuous flow throughout the cycle, as a regular data flow, or as irregular event based data flow. These different data flows mimic various types of industrial process and show data flow from I/O to cloud.

The applications use the push button that is connected to the SIMATIC ET200 SP I/O module via the terminal block. Data is sent between the SIMATIC I/O module and the MFN 100 I/O port via PROFINET and the illumination of the button is controlled via the CODESYS soft PLC running on the MFN 100.

The two default CODESYS applications: app1 and app2 are used to alter flow of data from the I/O modules. Both apps control the illumination of the button and record two values: iCountNumber and iCountButton.

app1 app2
iCountNumber
(continuous data flow from the application to the Management System)
  • Continuous count upwards from 0 to 1000.
  • Resets to 0 automatically when it has reached 1000.
  • Continuous count downwards from 1000 to 0.
  • Resets to 1000 automatically when it has reached 0.
iCountButton
(irregular and regular data flow from the application to the Management System)
  • Counts the number of times that the button has been pressed (irregular data flow).
  • The push button lights up after 10 button presses.
  • The value resets to 0 when the button is held for two seconds. The light of the button goes out.
  • Counts the duration that the button is held (regular data flow).
  • The counter continuously increases from 0. The push button lights up when the value reaches 25.
  • The value continuously decreases to 0 when the button is released.

The Management System allows users to deploy either of the default applications from the repository to the MFN 100. This demonstrates the ability to update CODESYS applications remotely and alter applications running on machines wherever they are in the world.

Beyond the two default applications, users can also use the kit to develop their own CODESYS applications, which can be uploaded to the repository in the Management System and then deployed to the MFN 100. These applications can then be used in conjunction with corresponding actuators and/or sensors.

Note

The default application app1 is loaded automatically during the initial startup of the MFN 100.

Connecting to the Management System#

The Nerve Management System is a web-based service that permits management of Nerve Blue nodes that are registered.

Note

Google Chrome or Firefox Version 63 or later are recommended for the usage of the Management System.

Before connecting, make sure that the MFN 100 of the starter kit is connected to the network through port 2 and that an IP address has been assigned by the DHCP server. If you need help with assigning an IP address, please contact your IT administrator.
The login credentials for the Management System are in the customer profile. The customer profile has been sent in form of a PDF as part of the delivery.

Note

If you have not received a customer profile, please contact your sales representative or TTTech Industrial customer support at support@tttech-industrial.com.

  1. Go to the URL of the Management System in the customer profile.
  2. Log in with the credentials provided in the customer profile.

    !Management System Login

You will reach the dashboard of the Management System, which shows the Node Tree by default.

!Management System Dashboard

One element in the Node Tree is already created at first login, containing the MFN 100 of the Nerve Blue Kit. All newly registered nodes will be located under Root > Unassigned by default.

From here you can manage nodes, provision workloads and deploy workloads among other options. See the user guide for more information on the Management System.

Note

Port 443 (HTTPS) and port 8883 (MQTTS) of the corporate firewall have to be open for communication between nodes and the Management System.

Moving a Node from One Tree Element to Another#

Moving nodes in the Node Tree is possible by drag and drop. Please make sure that you have created a new tree element before attempting to move a node.

  1. Select Node Tree in the left-hand menu.
  2. Expand the tree element of the node you want to move. The default element is Root > Unassigned.
  3. Choose the node you want to move.
  4. Drag and drop the node to your newly created element. Elements expand automatically once you hover over them.
  5. Select APPLY CHANGES (n) in the upper-right corner of the Node Tree.

    Note

    (n) is a placeholder for the number of changes made to the Node Tree. If you have performed three changes, you will see (3) in the button above the Node Tree.

The node has now been moved to the new element. Note that a node cannot be moved back to Unassigned once it has been moved to another element.