In this video, we'll be talking about Libupm and walking through the Github and just teaching you more about it. So, our brief overview, we'll be first describing what Libupm is and then we'll be going through the Github of Libupm and then just looking at the documentation and all the files inside. So a few things about Libupm, it's a high level repository for sensors that use MRAA. So this basically relies on the MRAA library that we talked about before but this is more specific for each sensor module that's available. So, a sensor has its own class and the filter object oriented programming, this would make clear sense to you but if you're not sure you can just look it up yourself on the internet. Everything needed for the sensor is initialized when the class is instantiated so that when you create an object from the class for that sensor then everything will be set up for you. That's just how Libupm works. So after this I'll just let Andrew walk you through the Github page for the Libupm and tell you more about it. Okay so, here's the Github page and we'll be just going through. Let me make this a little bigger so you guys can see this. It's actually big. Yeah. And then, we'll just scroll down and then on the first directory that you might want to use is the examples and this is basically showing you the example files that you might want to use for each language and we can just click on C++ and share all the files. And then, we'll be showing you one certain code for the sensors but if you want to learn more about this you can just go through the documentation which we'll also be showing you. And then, we can just go to source and as we scroll down, we can see that Libupm supports all of these individual sensors and one code that you might be using for your DragonBoard purposes is jhd1313m1 and it's a pretty long name but this is the code for your LCD. And let's just click it. And as you can see, there are different languages that's supported. There is C, there is C++, and then there's JSON. And then, you can just go to one of these files. Let's just go to this dot C file and then you can see all these individual methods that you will use. And depending on what you want to use, you can just include this file and then you can run the commands. And then, the file might be a little tough to read at first, so we want you to go to the documentation for an easier reference. This can be found in the original Github page and then you just scroll all the way down. And then here is the API documentation. And then, since we like to use C and C++, we'll just click on C and C++. And then once you scroll down, so you'll click on sensor list. Sorry, this is a little slide as well, let's just make this bigger. And then, we can just go find where the LCD might be. It's quite a bit. Yeah. That's a lot but you can just click on Grove Starter Kit as this is what we're using and then as you can see there's the jhd1313m1 and we want to see what this exactly is. So we can just click on it and then we can see that it's the C API for the LCD display as it says on here. And then we can click on the dot H file and then it shows you the description as we saw earlier and then it shows you what each individual method does. So, I say we want to write to the LCD itself. We want to use this method, UPM result, that's the output. And then we can just type in jhd1313m1_write and this will write to the LCD. That concludes our tutorial for the Github and then. Let's go back to the slides. So yeah, on these slides you can see we'll be writing some more resources in the reading. So just look out for those and we'll just teach you more about the Github and links to documentation and supported sensors. And I'll start with some takeaways. So there are classes specific to each sensor in our four commonly used, five, four. Four, five, it's close. Yeah, commonly used languages such as; C, and C++, and Java. Basically, when we went to the Github pages it just shows us how the source code works. We don't fully understand it ourselves as we haven't written it or gone through it, but if you really wanted to, you could learn like every little bit how it works down to that level. Also, as we saw we had access to a lot of documentation, so we don't actually have to see the code ourselves and we just understand how it works from that and how to use all the methods and functions that they have. So, see you guys next time, we'll be out there.
