Setup a Raspberry Pi as an IoT Device Part 4

Step 8: Verify Connectivity

The EMS is now attempting to talk to ThingWorx Foundation.

However, ThingWorx does not have detailed information about the Edge device that is attempting to connect to it, so it will show up in the Unbound category of Remote Things.

1. Open ThingWorx Composer.
   
    

   

    

2. On the left, click Monitoring.
   
    

   

3. Click Status -> Remote Things.
   
    

   

    

4. Click Unbound.
   
    

   

    

5. Confirm that you see the PiThing listed in the Unbound section.
   
   NOTE: The name PiThing comes from the config.lua script. PiThing is simply the name that is in that script, hence the name that you see in ThingWorx. To change the name of the device, you could stop both wsems and luaScriptResource, edit config.lua to use a different Thing name other than PiThing, and then restart both of the EMS programs. At that point, the Thing showing up in Remote Things -> Unbound would be whatever name you changed to in config.lua.

Create a Remote Thing

Now that the EMS is communicating with ThingWorx Foundation, let's create a Remote Thing to which Foundation can tie said connection.

1. In ThingWorx Composer, click Browse > Modeling > Things.
   
    

   

    

2. At the top-left, click + New.
   
    

   

    

   
   

    

3. In the Name field, enter PiThing.
   
   

   • Note that the name must match the spelling and capitalization of the Thing's name that you entered in the EMS's config.lua for it to auto-connect.
     
     
    
4. If Project is not already set, search for and select PTCDefaultProject.
   
   
5. In the Base Thing Template field, search for remotethingwith.
   
    

   

    

6. Select RemoteThingWithTunnelsAndFileTransfer.
   
   

7. At the top, Click Save.
   
   

   • Note the status-indication pop-up indicating that PiThing is now connected.
    

   

    

   
   

    

Use Services to Explore EMS Files

Now that your Remote Thing is Saved and Connected, we can use some of the built-in Services to explore the EMS folders and files which we previously created for testing purposes.

1. At the top of PiThing, click Services.
   
   
    
2. Under the Execute column, click the Play Symbol for BrowseDirectory.
   
   
    

3. In the top-left path field, type / and click the bottom-right Execute button.
   
   

   • Note the other and tw folders which we previously created for testing.
     
     
    

4. In the top-left path field, type /tw and click the bottom-right Execute button.
   
   

   • Note the tw_test_01.txt file which we previously created for testing.
     
     

      

    

As the tw_test_01.txt file (and its parent folder) were items which we custom-created for this guide, you should now be 100% convinced that connectivity between Foundation and the EMS is dynamically working.

If so desired, you could explore into other folders (or even add additional files to these folders), run the BrowseDirectory Service again, and confirm that Foundation is now aware of the EMS and actively communicating.

Step 9: Next Steps