 Okay, so we're going to start the first hands-on or lab session now. So this lab session is going to test our communications between our target board and our Laura network. To do this, we're going to load into our target board a pre-compiled file which has an AT command set. So we're just going to treat it literally as a modem to send information up to our Laura network so that we can test all the connectivity of our Laura network to make sure everything is working. So what we're going to do, so we're going to have a first play around with the Laura technology. You're going to see in a few seconds what a Laura network consists of and then we're going to program our discovery board to be a Laura class A-N node. And as I said, we're going to use it as a modem with AT commands at this point. So we're going to use it in one of its basic forms to transmit information across a network. So this is what we need for a Laura network. So in front of you on your desk, you have your device which is called a moat in Laura terms. And this is our discovery board containing the STM32 microcontroller. This device is then going to talk to our gateway. The gateway is just a pipe or a conduit or channel which converts the RF signals from our device into something the network server can understand. So it's just literally there as a format changer from RF to a cable structure. The network server, there's only one in the Laura network and this is controlling the whole of the network. So in equivalent, it is giving out like IP addresses or IDs to each of the device when they join and it will control the routing of all the traffic from the device through to the application servers which are doing the control or the monitoring or analysis of all the devices that are connected to the network. Finally, the application servers. So you can have multiple application servers in a network. You don't just have to have one like our diagram is showing. And these can do different functions. So each application server can be configured to talk to a specific set of notes and they can analyze the data from different devices that are collected and you can view them and different customers can view different application servers depending on what your system needs to control. So what do we need here in our hands-on lab session? So we need our Laura gateway. So we have got on our desk here at the front a blue multi-tech multi-connect conduit which is being used as our gateway for our Laura device. So this will provide the connectivity from our end devices into something we can then view on a laptop. So we have a laptop connected via ethernet to our multi-tech gateway and this is just so we can see what is going on inside the gateway. This particular multi-tech gateway is a three-in-one device. So it contains our gateway, our network server and our application server. So it's all in one box. By default Laura isn't part of the standard kit but the multi-tech box has two auxiliary sockets and you can see there to the top right of the picture there is the Laura card which is the actual Laura gateway element and that plugs into the back of this multi-tech box so that we can have the connectivity to our Laura gateway. And everything is then viewed on a laptop via a web interface which we'll be showing you later on in the hands-on. We also need our Laura 1 Discovery board. So this is containing the Murata module which has inside it the STM32L0. This, like all other STM32 boards, has an integrated ST link so that we can connect it directly to our laptops via a micro USB cable and it will appear as an embed-enabled device. So you will see it appear as a dish drive in your Windows Explorer window. We will need to program some firmware into our target board to make the AT Command and Projects available by default. What's included in the board out of the box is just demonstration software. So we will need to download our iCube-LR1 software package and program into our target board, the AT Slave example. We have already included that in the participant.zip which was on the memory sticks that have gone round. And I will show you how to do that in the coming slides. Finally, we will need a PC terminal software so that we can use our laptop over the USB cable to talk to our LoRa1 board via AT commands. So we will then send a command to our LoRa1 board and then the LoRa1 board will convert that command and transfer it over the LoRa network. So we'll now go straight into the hands-on. So the first thing we need to do is we need to connect our laptops to our target board, the Discovery boards, with a micro USB cable. You will need to wait 30 seconds or a minute while all the drivers load. If you've not got stlink utility already installed in your laptop then you will need to install this first as this will contain all the drivers that the Discovery board will need when you connect it into your target board. If we now look for the binary file that we need to program into our board. So in the participant folder we need to go into the hands-on framework, projects, multi, applications, and LoRa, and then AT slave. And here we have our AT slave xe.bin file. So this is now what we need to drag and drop onto our Discovery board, which should have appeared in your Windows Explorer, like mine has down there, dis underscore L072Z. It's appeared as my eDrive. And to program the board, you just drag and drop the file onto there. And you will notice on your Discovery board that one of the LEDs next to the USB connector should start flashing green and red. This means that the board is being programmed with the required software. So next thing we need to do, we need to launch our terminal window. So we now need to go and find out what comports our board has appeared on. So for me, it has appeared as comp71. We need to set our board rate to be 9,600 with eight data bits, one stop bit, and no parity, and no flow control. We also need to set the carriage return and line feed so that we can move the cursor down every time we type a command on our screen. So if we OK that, and now to validate that we can send a command, I will send the basic AT command, and I get an OK. So I now know my laptop is now talking to my Discovery board. So the first item we need to send to our Laura network is we need to send a join request. So I will go AT plus join, and I've got an OK return from the target board. So to check to see if we have joined, because remember all I'm doing is communicating with the target board. I don't know if the board has successfully joined the network, so I will now go and ask to see what my status is with AT plus NJS equals question mark. So this will tell me my status. It's returned a one, which means that I am now actually connected to the Laura gateway. So I'm now in a position to send a message across the Laura network. So I'm going to now send a message. So AT plus send. So I'm going to send two elements. I'm going to put a keyword in because we are going to look for that keyword in our gateway so that we can send a response. And then I'm going to type my name. So I can see on my diable screen that I have sent the message. So if I send that, I get an OK. So that means my message is now left. And now I want to check to see if the gateway actually received my message. Because again, all I'm doing is talking to the node at this end. So I want to go for AT plus receive equals question mark to ask it what it received. And there I have got my received message from my discovery board or my moat to say that I got a gateway response and my name has been echoed back to me. So I can see that my board has actually sent the message out OK and my board has received a message back and that message is now displayed on my screen. So if we now look at the debug screen from the multi-tech gateway with my webcam, you can see there that my debug screen has generated two items in the debug screen. One of them is my inbound message containing the word moat and then one of them is the outbound message which is the gateway response. So you can see directly on the debug environment through my laptop which my second laptop which is connected to the multi-tech gateway you can see what is actually going on on the Laura network.