Skip to end of metadata
Go to start of metadata

Each Project serves as a container for PLC Device management. When you add a Device to a project, you create a group of connected PLC Devices for users to access within a Project.

You can easily register and configure devices with the LoopCloud platform. Configure and register PLC Devices within the Loop platform, where real-time device data and performance can be viewed. Within this platform, devices can be enabled, disabled, and updated with the latest firmware. You can provision individual devices, or with the bootstrap and registration mechanism, mass-deploy your devices onto the platform.

Use the following procedures to configure a LoopCloud Device:

Add a Device via Device Management

Devices have three deployment options: Single, Bulk, and Demo Device. For the purpose of this Getting Start Guide, you are advised to use Single.

To add a device to a project:

  1. In the navigation panel, click Project List.
  2. Select a project to update.
  3. In the navigation panel, select Device Mgmt > Devices.

    NoteThe status is Green (online) when the Device connects MQTT server with its credentials.

  4. At the top right of the Devices window, click the Single deployment option.

  5. In the Device Model Select window, click the tab for the Model type:

    LoopCloud Device Model Information:

    LOOPEDGE: This model supports LoopEdge devices to connect to LoopCloud. It is similar to the embedded model, but with additional LoopEdge integration features, such as remote access and cloud activation.

    EMBEDDED: An embedded system is a special-purpose system in which the computer is completely encapsulated by the device it controls, for example, a Raspberry Pi or an Arduino board. This model can be used for any such device or even a script that can use protocols supported by LoopCloud to send data and receive management commands.

    POLL: Use this model for continuously polling a device. Some legacy systems allow collection of data from their devices using an http interface (SOAP or REST). LoopCloud’s poll model provides a way to integrate legacy systems or devices that are not able to send data; the poll model enables LoopCloud to pull data from those legacy devices. Another use case is web services. For example, Nest provides a web service that allows retrieval of data from their thermostats. In this case, there is no direct connection to a real device, but LoopCloud can collect data from the Nest sensors. Other examples include electric vehicle charging stations or even smart cars.

    WEBHOOK: A webhook, often referred to as an HTTP callback, enables LoopCloud to push data to web applications. See Webhook Model. Once a device is deployed from a model, the webhook will be available at an address with the following format:{projectId}/{deviceId

    For a Demo device, any Model type can be used. The Model should contain the MQTT interface.

  6. In the Device Model Select window, click the Model you want to deploy. Use the filter at the right to find Models for a specific protocol.

    If you do not see the Model protocol that you need, go to Configuration > Models to create one. See Create a Device Model.

  7. Click CONTINUE to download the current configuration file and deploy the device. This file contains the JSON schema, which you can use to configure device parameters.

          The device now appears in the Devices Dashboard. 

Add a Device from a Model

The following procedure provides an alternative to the procedure listed in Add a Device via Device Management.

To Add a Device from a Model:

  1. In the navigation panel, click Project List.
  2. Select a project to update.
  3. In the navigation panel, select Configuration > Models.
  4. Click the model type at the top of the window: LOOPEDGE, EMBEDDED, POLL, or WEBHOOK. See Model Types.
  5. Find the desired model and click the plus sign (+) in the model.

If you do not see the model protocol that you need, go to Configuration > Models to create one. See Create a Device Model.

A message at the bottom of the browser indicates the Device addition to LoopCloud. The Device now appears in the Devices list: Device Mgmt > Devices.

Explore the Devices Dashboard

Many of the details found in the Devices Dashboard are beyond the scope of this Getting Started Guide, however, this example provides an opportunity to become acquainted with the dashboard's features and capabilities.

Use the following example to explore the features of the Devices Dashboard.

Example of a Devices Dashboard

  1. Device ID - This is a system-generated Device identifier. Click the link to explore Device attributes and details displayed in the following tabbed pages: INFO, MAP, EXPLORE, RAW, MQTT, LOG.
  2. Status - The Device status can be viewed via a mouse-over tooltip.
  3. Action - Modify the device status: Block, Online, Delete, Maintenance, Disconnect. See Device Status Actions.
  4. Filter - Open the filter to search for a specific device attribute.
  5. Multi-select - Switch to multi-select mode when you want to take an action on multiple devices.
  6. Map View - Display a map with the Device location information. Mouse over the map marker object to view the Device status.

Device attributes (manufacturer, model number, serial number, and firmware version) listed in the INFO tab become available only once the Device starts sending data to the Loop server.

To navigate to additional Device details, see Explore a LoopCloud Device.

Device Status Actions and How to Delete a Device

Device status is Active by default.

Block - Block a Device from sending any data to the Loop server. Currently, this is enabled only for Polling Devices, because MQTT and REST protocols do not block the data.

Online - Devices become active when bringing them Online from other states.

Delete -  Delete the Device. The Delete status will update in real time, but the actual deletion from LoopCloud takes place after a 24-hour time period.

If you delete a Device by mistake, you have a day to get it back online.

Maintenance - Set a Device to maintenance mode when maintenance is scheduled for a physical device. Alerts will not be sent if no data is coming from the device.

Disconnect - This action is not supported for all Devices.

  • No labels