Go to https://remotemanager.digi.com/ and login with the account you used for the simulation. All the simulated devices are listed and online.

All the operations in this step can be performed using Remote Manager web interface tools or using web service APIs from API Explorer, your own application, or a third party tool, such as curl.

Let’s check the features of the simulated devices, as listed in the configuration files:

  1. Inspect device location

  2. Access device file system

  3. Update simulated device firmware

  4. Monitor uploaded data

  5. Send data to simulated devices

1. Inspect device location

In the simulation, a route has been provided to the trucks, truck_routes, so all devices appear as if they were moving.

To check the current location of simulated trucks:

  1. Go to the Device Management > Devices tab.

  2. Click on a simulated device.

  3. The latitude and longitude settings are filled up. Also, you can inspect the geo-location of your device in the map on the right side of that screen.

  4. Finally, check the location of all of your devices

    1. Go back to Device Management > Devices.

    2. Click the Map view button on the top left next to Search text box. A map is displayed with all the devices of your account.

2. Access device file system

Another feature in the simulation is the configured file system, file_system_01. You can operate with it as you would do with a real device.

To check if the file system contains the expected files:

  1. Go to the Device Management > Devices tab.

  2. Click on a simulated device.

  3. Select the Files option.

You can navigate through the file system and use the upper button bar to upload, download, or remove a file; refresh the view; and go back, forward, home, or to a specific location.

3. Update simulated device firmware

The simulation allows devices to perform remote firmware updates. Our simulated trucks are based on ConnectCore modules, so, to program a new firmware we must:

  1. Upload the firmware to Remote Manager firmware repository.

    1. Select System > Firmware on the left bar.

    2. Go to the Custom Device Firmware tab.

    3. Click Add Firmware button to open the wizard.

    4. Fill the fields to identify this firmware in the repository. Main parameters are:

      1. Select the Vendor ID called Digi ConnectCore (0xFE080003).

      2. Choose the Device Type of the devices you are going to update with this firmware, refrigerated-truck.

      3. Enter the Firmware Version of this package, 1.0.0.2.

      4. Type the URL of the firmware Release Notes, for example, https://www.digi.com.

    5. Upload to the repository your update package:

      1. Download this file (1.0.0.2.swu) to your computer, or use your own swu package.

      2. Click Add files.

      3. Browse in your local file system for the update package (.swu).

    6. Finally, click Add to upload the firmware to Remote Manager repository. When the upload process finishes, a new entry is added to the table.

  2. Update the device:

    1. Go to the Device Management > Devices tab.

    2. Select the checkbox on the left of one or several simulated devices.

    3. Click the Actions drop-down menu on the top-right corner of the list of devices.

    4. Scroll down to find Update firmware option and click it.

    5. In the Update Firmware wizard, select 1.0.0.2 (custom) from the combo box list.

    6. Click Update.

    7. You can wait for the update to finish in the wizard, or go to the API Explorer and use v1/firmware_updates API to get the progress:

      1. Get the device ID of one of the devices being updated. It follows the format 000A0003-XXXXXXXX-FF0FF0FF-FF0FF00X.

        1. Go to the Device Management > Devices tab.

        2. Copy the Device ID of your device from the table by using the Copy Device ID button that appears next to it when you hover over the item.

      2. Go to the System > API Explorer tab.

      3. Click the Examples combo.

      4. Select v1/firmware_updates > Get firmware update progress.

      5. Modify the request path with your device ID. It should be something similar to:

        /ws/v1/firmware_updates/progress/000A0003-XXXXXXXX-FF0FF0FF-FF0FF00X

        Where 000A0003-XXXXXXXX-FF0FF0FF-FF0FF00X is your device ID.

      6. Click Send. The response indicates the update progress status:

        {
    "id": 1,
    "customer_id": XXXX,
    "device_id": "000A0003-XXXXXXXX-FF0FF0FF-FF0FF00X",
    "progress": [
        {
            "status": 5,
            "time": "2023-09-22T12:53:10.139Z",
            "message": "Sending Data: 4540912 out of 204946944 bytes sent"
        },
        {
            "status": 0,
            "time": "2023-09-22T12:51:15.845Z",
            "message": "Sending Download Request"
        }
    ]
}

        Where 000A0003-XXXXXXXX-FF0FF0FF-FF0FF00X is your device ID.

4. Monitor uploaded data

As configured in the simulation, simulated trucks upload outside and inside temperature values as data streams, following what is configured in data_streams/streams.json:

  • <device_id>/temp_outside contains random doubles between 20C and 30C starting with 25C. This value is generated by the simulator every 2 minutes.

  • <device_id>/temp_inside contains random doubles generated by custom Python code every 30 seconds.

Data points are stored and uploaded in a batch every 150 seconds as it is configured in the profile profiles/trucks.json.

To check all this data:

  1. Get the device ID of one of your simulated devices. It follows the format 000A0003-XXXXXXXX-FF0FF0FF-FF0FF00X.

    1. Go to the Device Management > Devices tab.

    2. Copy the Device ID of your device from the table by using the Copy Device ID button that appears next to it when you hover over the item.

  2. Go to the Insights > Data Streams tab.

  3. Paste the copied device ID in the search box and press Enter. The list of all streams associated to that device appears below. There may also be some streams starting with 000A0003-XXXXXXXX-FF0FF0FF-FF0FF00X/management for maintenance status and device connections and one more 000A0003-XXXXXXXX-FF0FF0FF-FF0FF00X/metrics/sys/location, for the current location of the device as we are simulating a route.

5. Send data to simulated devices

The simulated refrigerated trucks allow to remotely manage their inside temperature with a request with target change_temp, configured in device_requests/requests.json. To set a new temperature, follow these steps:

  1. Go to the Device Management > Devices tab.

  2. Get the device ID of one of your simulated devices. It follows the format 000A0003-XXXXXXXX-FF0FF0FF-FF0FF00X.

    1. Go to the Device Management > Devices tab.

    2. Copy the Device ID of your device from the table by using the Copy Device ID button that appears next to it when you hover over the item.

  3. Go to the System > API Explorer tab.

  4. Click the Examples combo.

  5. Select SCI > Data Service > Send Request. A request appears inside the Body text box.

  6. Modify the request to test:

    1. Replace the device id value with the copied one.

    2. Replace the target_name value with the target to use, change_temp.

    3. Remove the payload of the request, and add a new temperature between 0.0 and 10.0, for example 4.0.

      The request should be similar to the following:

      <sci_request version="1.0">
  <data_service>
    <targets>
      <device id="000A0003-XXXXXXXX-FF0FF0FF-FF0FF00X" />
    </targets>
   <requests>
     <device_request target_name="change_temp">4.5</device_request>
   </requests>
  </data_service>
</sci_request>

      Where 000A0003-XXXXXXXX-FF0FF0FF-FF0FF00X is the device id of the truck to change its inside temperature.

  7. Click Send to send the request to your device.

    In the Response text box you can review the answer from the device:

    <sci_reply version="1.0">
  <data_service>
    <device id="000A0003-XXXXXXXX-FF0FF0FF-FF0FF00X" />
      <requests>
        <device_request target_name="change_temp" status="0">New target temp for '000A0003-XXXXXXXX-FF0FF0FF-FF0FF00X': 4.5C</device_request>
      </requests>
    </device>
  </data_service>
</sci_reply>

    Where 000A0003-XXXXXXXX-FF0FF0FF-FF0FF00X is your device id.

  8. At this moment, the inside temperature of the truck starts to change to get the configured target, 4.5C. You can review it following the steps in Monitor uploaded data. You can review simulation.py file of gs-sample to check how received request is managed and new values of 000A0003-XXXXXXXX-FF0FF0FF-FF0FF00X/temp_inside generated.

For more information on custom code see Custom code implementation.