Skip to main content
Skip table of contents

Dynamic Device setup

Dynamic devices can be used to connect Modbus RTU devices to NSnappy. You can also combine multiple radio devices (doesn’t work yet if the devices are provisioned to NSnappy, this will be fixed later) with this to a single control point. Added devices do not need to be provisioned to NSnappy as every channel is configured manually.

Dynamic Device will get its own virtual serial number and you can name the devices to easily identify them in the future.

Working order should be (assuming customer environment has already been setup):

  1. If Modbus device, first configure it to the base station or Solid-Sky transmitter.

  2. Create Dynamic Device.

  3. Create Control Point for Dynamic Device.

  4. Install the Dynamic Device to the Control Point.

Setting up a dynamic device

  1. Create a new Dynamic Device by pressing +NEW DYNAMIC DEVICE in Settings → Devices.

    image-20251008-071849.png

  2. Give the device a name, select a warehouse to put it in. Good naming practice makes it easier to distinguish dynamic devices and install it on a control point afterwards. You can start from scratch or copy an existing dynamic device and edit details afterwards.

    image-20251008-072200.png

  3. Click edit sensors (channels)

    image-20251008-072343.png

  4. Give the sensor (channel) a name, radio ID or address or virtual ID generated by a basestation. For channel field enter the number of the channel used by a Sky-protocol device, for example Flex-Sky-T-RH has two channels: Channel 1 is temperature and Channel 2 is Humidity. For MTR-, FT10 devices and base stations that use MTR protocol leave the Channel field empty as MTR protocol devices only transmit 1 result per ID, so there are no channels.

    Each sensor (channel) can come from any device that connects to NSnappy via a gateway/base station that is in the same customers warehouse where you are creating the new dynamic devices. This is to prevent overlapping ID numbers to save results on to the same sensor (channel) from another devices that has a matching ID. With Modbus RTU devices the IDs are virtual and when configuring them to base station be sure not to overlap IDs with with other devices that the customer has.

    Here is an example how to configure RMD680 that has been connected and configured to a base station:

    image-20251008-102551.png


    Here is an example how to configure two Sky transmitters as a single dynamic device (temperature and humidity comes from Flex-Sky-nSens-HT-EIS and particle measurement comes from Kube-Sky-PM0440):

    image-20251008-103349.png

Creating a control point for a dynamic device

  1. Go to a site where you want to create the control point and click on +NEW CONTROL POINT.

    image-20251008-104545.png

  2. Fill in the details and check “INSTALLED MEASURING DEVICE” and click continue.

    image-20251008-110338.png

  3. Select device type: Dynamic Device.

    image-20251008-104931.png

  4. Select the dynamic device you want to use on this control point and click Continue.

    image-20251008-105025.png

  5. Rename the channels if you want and select correct purpose for each channel and click Continue.

    image-20251008-111116.png

  6. Add manual measuring channels if you want, if not, then just click SAVE CONTROL POINT.

    image-20251008-111234.png

Installing a Dynamic Device to a Control Point

  1. Click Install device.

  2. Select the dynamic device you created for the control point and click INSTALL DEVICE.

Editing a Dynamic Device

  1. Go to Settings → Devices and select the device you want to edit.

  2. If the device is installed to a control point, first uninstall it, and after that you can go to Dynamic device menu and edit the channels from there.

    image-20251008-111754.png

    image-20251008-111952.png

  3. After editing click Save.

    image-20251008-112034.png

  4. Now the dynamic device can be installed again to the control point.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.