Repository navigation
Host Instruction
This page is for host instructor of IoT Workshop, outlining the preparation and actual hosting tasks
1. Understand Oracle IoTCS
For Oracle Code events, here is IoTCS Console where you can manage devices and check IoT messages. Ask Raymond (yuhua.xie@oracle.com) for login credentials.
IoTCS console UI video will show you IoTCS login, Oracle Code IoT App, associated device model, and its message page.
For additional reference, you can read device model, IoT application, and how device connecting to IoTCS, and more documentation: Understanding Oracle IoTCS
2. Get to know IoT Asset Monitor
We will use IoT Asset Monitor to show charts of incoming sensor data, as well as trigger an event to remote device to perform an action. You need to choose a device to show as an asset, to display that particular device data.
For Oracle Code events, here is IoT Asset Monitor, where you can show sensor readings on chart, and trigger device action. Ask Raymond for login credentials.
IoT Asset Monitor video will show you IoTAM login, navigation, create asset and pick asset device, check sensor tab, and general tab.
For general information, please refer to official documentation IoT Asset Monitor
3. Understand Device Registration and Provision
Understand how to register a device, and activate device (by running client code the first time with provision secret). Also need to know where to check device activity at monitor device message
We will adopt a naming convention to register device for each participant at each Oracle Code event, so we can easily recognize and filter device easily.
To register a device, please prepare the following fields:
Activation Code: dev-[Seq#]
Device Name: Code-[CityName]-dev-[Seq#]
Location: Latitude, Longitude
For example, if we are having an Oracle Code event in San Francisco, you can replace [CityName] with SanFrancisco, and pick a sequence number [Seq#] for each participant in that city, starting from 101.
Activation Code: dev-101
Device Name: Code-SanFrancisco-dev-101
For the location, you can use Google map to find out the latitude and longitude of the conference venue, by right-click on the map, and choose "What's here" on the popup menu, then it will should you the latitude and longitude data. Write down the latitude and longitude for your location, as you will need that for each device registration.
After inputting above fields, you can save it to register that device, and it will ask you for a password for encrypting the device provision file to be downloaded. To be consistent, you can just use [CityName1] as the password for all participants, which would be SanFrancisco1 if the event is in San Francisco. The password is required later on to run device client code.
Device registration and provision video will show you how to register a device, check device status (registered, activated) on the device list, and run IoTCS client code for the first time to activate device.
1. Get a Wired Network drop
Make sure the event venue provide a "wired" network drop at IoT Workshop area. If not, you need to raise it to event coordinator.
2. Connect Netis Router
We will provide a Netis Router, with SSID pre-configured as oc-iotws (ask Raymond for password).
Connect the wired network drop provided by conference to the WAN port of Netis router, and ensure the WiFi network oc-iotws has direct internet connection, meaning no passcode is required, nor any acceptance of terms. Wio Node device does not have interface to accept terms of service or input passcode.
The WiFi network is dedicated for Wio Node device connection to Internet. Please do not use this WiFi network for other purpose, to avoid network connection slowdown.
3. Create event account
You need to download Wio App on iPhone or Android device. We will use a custom server http://129.150.86.239:8080 to run Wio virtualization server, so please set the "customize server" accordingly. Then you can sign up for an event account, e.g. if the event is in San Francisco, I would create sf@iot.oracle.com with easy 6-letter password, e.g. aaaaaa. If there are many participants, you may create second or third account, such as sf2@iot.oracle.com and so on.
Here is an creating event account video showing you how to create event account for holding Wio devices for all the participants, so we have a common place to register and use devices for this workshop session.
Please follow step 1 and step 2 at Get Started with Wio Node to setup the account. You can try to follow step 3 to add a device to the account, for next step.
4. Add Wio device
We will follow the similar sequence number [Seq#] approach used for registering device in IoTCS.
When adding a new device to Wio Virtualization server, you can use the dev-[Seq#] as the device name, and also write down that dev-[Seq#] on the Wio Node box. So that a participant with that Wio device (and box) knows his device, and can find the name in the event account.
Here is an adding-devices video showing you how to add device to the account and write down the device ID.
5. Do a test run
Please go through the IoT Workshop once by yourself, so you know what participants will do during the session. Here is the Session Content.
6. Add more Wio devices
If you still have time after running through the workshop session content, please repeat step B.4, add more devices to the account, and write down the sequence number/device name dev-[Seq#] on the box. This is a time-consuming step that you need to prepare the devices for all participants one by one. Do as much as you can today!
If you get to about 20 devices in one account, you may want to create second account, and add further devices in second account, in this case, you also mark which account you added the device to when you write down the serial number on the box, so that participant knows which account to login to find the device.
0. Add more Wio devices
There will have a Keynote session before the IoT Workshop session actually starts, so you want to add as many Wio devices into the event account as you can at this time, to make it ready when participants come in. Just follow step B-4 above.
1. Give out materials
You will hand out a device kit for each participant, with Wio Node device marked dev-[Seq#]. Get participant's email, and send the following information to his/her email:
a. instruction link to this IoT Workshop content
b. provision file with the same "dev-[Seq#].csv", and file password
c. information about $300 credit to sign up Oracle Cloud to try out on Oracle Code website: https://developer.oracle.com/code
That way, if participants have further questions after the IoT Workshop, they have your email to do follow-up; or we can follow up with them if necessary.
2. Introduction to workshop
Explain the purpose and components of Workshop to participants, if needed. Please keep it short as you will be busy on other things already. Or just direct participants to Introduction Page for background information.
3. Ask participant to start with Wio App
Ask each participant to use Wio app on iPhone or Android, and pick his/her own assigned device in the event account (by the serial number, e.g. CD1243 in the example above). Just follow the detail steps of Exercises
4. Facilitate device registration and provision
When a participant gets to Exercises #4, they need a security provision file to run IoTCS client against backend IoT Cloud Service. Please follow step A.3, and this video: Device registration and provision video
5. Show it works
After a participant gets his wio-iotcs-client.js running with proper configuration, the client program will send sensor data to IoTCS and Asset Monitoring. You can show the incoming sensor data, and trigger an event on his buzzer, to prove it works!
Please follow A.2 and this video: IoT Asset Monitor video. Show the "Sensors" tab - chart page, and "Info" tab - buzzer control page.