TheEMSis now attempting to talk toThingWorx 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 theUnboundcategory ofRemote Things.
On the left, clickMonitoring.
ClickStatus -> Remote Things.
Confirm that you see thePiThinglisted in the Unbound section.
NOTE: The namePiThingcomes 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 inRemote Things -> Unboundwould be whatever name you changed to in config.lua.
Create a Remote Thing
Now that theEMS is communicating with ThingWorx Foundation, let's create aRemote Thingto which Foundation can tie said connection.
Note that the namemustmatch the spelling and capitalization of the Thing's name that you entered in the EMS's config.lua for it to auto-connect.
If Project is not already set, search for and select PTCDefaultProject.
In theBase Thing Templatefield, search forremotethingwith.
At the top, ClickSave.
Note the status-indication pop-up indicating that PiThing is now connected.
Use Services to Explore EMS Files
Now that your Remote Thing isSavedandConnected, we can use some of thebuilt-in Servicestoexplore the EMS folders and fileswhich we previously created for testing purposes.
At the top ofPiThing, clickServices.
Under theExecutecolumn, click thePlay SymbolforBrowseDirectory.
In the top-leftpathfield, type/and click the bottom-rightExecutebutton.
Note theotherandtwfolders which we previously created for testing.
In the top-leftpathfield, type/twand click the bottom-rightExecutebutton.
Note thetw_test_01.txtfile which we previously created for testing.
As thetw_test_01.txtfile (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 theBrowseDirectoryService again, and confirm that Foundation is now aware of the EMS and actively communicating.
Step 9: Next Steps
Congratulations! You've successfully completed theSetup a Raspberry Pi as an IoT Deviceguide, and learned how to: