 My name is Ria Kaur Labana from Bidskoa and we are working on IoT with Arduino and Raspberry Pi. We are a team of six people. So starting with what IoT actually stands for, IoT is actually Internet of Things. So what Internet of Things is for those of you who do not know about it. So giving you the brief overview of the project, so we started with the sensor node. We have a sensor node as you can see, the sensor node is actually collecting data from the sensors. Then we are sending this data to the send, this data is being extracted by Arduino, which is a microcontroller. From there on, we will be sending this data to Raspberry Pi. We have a database on this Raspberry Pi. There it goes to dashboard. We are visualizing, actuating and analyzing data on dashboard. So the main thing that comes is how do we send the data from Arduino to Raspberry Pi? So we have used two modules, Zigbee and ESP8266. So Zigbee is a wireless module that takes care of the wireless data transmission. And the other one is ESP8266, which is a Wi-Fi module. For Zigbee, we... How much distance you are expecting between the Arduino and Raspberry Pi? Raspberry Pi, it can be... Actually, we have our setup here. Because you are saying that either Zigbee or the Y2Me or whatever, Bluetooth, it may be... I am expecting it is a 10 to 15 feet. XB has short distance around... 100 meters maximum, right? So why do they disintegrate? They can be put together also. Zigbee has a range limitation. Zigbee can work only for 15 to 20 meters. That is what I am saying that... What is the meaning in putting that at different location? Why didn't they are integrated together? Sir, actually, suppose in industry, we have to calculate so many data from sensors. So what we are doing, we need at least two Zigbees to communicate. Suppose, means we are making a sensor part, we are adding one-one Zigbees. They are configured as end or router, and where the sensors are connected. And one Zigbee will be at the Raspberry Pi, it will be coordinated. That will be collecting data from all the Zigbees. Correct answer is that there will be a single Raspberry Pi connected to multiple sensors. But the basic technique these days is very popular as a Wi-Fi. Yes, sir. That's why we switched to... So Raspberry Pi comes with the Wi-Fi module built-in, and then there are very 150 rupees Wi-Fi modules available for the sensors also. But sir, Raspberry Pi is very costly, so... Okay, carry on. We started with Zigbee and then we moved on to ESP. ESP, as I already stated, is a Wi-Fi module. So, yeah, these are all the sensors that we have interfaced with Arduino, not going into the detail. This is the Zigbee I was talking about, the RX and the TX pin. As she already said that there is one router and one coordinator. The communication takes place through the RX and the TX pin. Yeah, the configuration of Zigbee as end or router can be done using the XC-TU software. A software comes, it can be done using Arduino UNO or directly through the USB port. This is the setup using Zigbee. This is the acting as the router side, and the coordinator one has the Zigbee attached to Raspberry Pi. This is the node 2. This means that both the Zigbees, both the routers, the previous one and this one, can communicate with the coordinator side with Raspberry Pi. This is the output that we obtained on Thingspeak. Thingspeak is actually an online dashboard that collects the real-time data and give you a plot of that. So, there we have the temperature and all graphs. Now, moving on to ESP. Now, why we switched on to ESP? I already give the reason because we have range limitation for Zigbee. But for ESP, we do not have any such thing. And ESP, we need Wi-Fi connectivity. So, this is our ESP module. It can be programmed using Arduino IDE or the Lua firmware. The setup, this is the setup. We have just replaced Zigbee with ESP8266. And now, on Raspberry Pi, we don't need any other connection. So, this is the output that we obtained on our dashboard. This was the one created by our people. So, yeah, this is, first we were using, connecting ESP to, and now we are using the NodeMCU one. So, yeah, this is the actuation setup that we'll be demonstrating in a few minutes. The actuation using a dashboard. This is the page for that. And now. Hi, I'm Abhishek Kumar. This is the flow of data from when we data is sent to the Raspberry Pi, then the data flow from to the database, then it goes to NodeJS server. We fetch it through the NodeJS server and then it goes to dashboard. From that, we visualize the data and actuate the data and then data analysis which came through Hadoop. Technology we have used are MySQL for database, NodeJS express framework, and socket IO. Chart libraries we have used are your charts for real-time charts and high charts for static charts. And now, come to big data. As we have been saving millions of data, means in one day there are like one lakhs of data. So in a month, we are on GBs of data. So we cannot process it in a relational database. So we are using Hadoop here. And then this is just the flow of Hadoop module. Conclusion like we have transferred sensor data to dashboard using both GB and ESP. And rendered real-time charts on the dashboard using different chart libraries. And big data analysis using Hadoop and actuated the devices using dashboard. This is our dashboard, we have created it. And just log in page. This is our real-time dashboard. It is showing the real-time data. Our sensors are there. This is connected to the Jigby. And our server is ESP, it's running by ESP. And even the real-time charts are showing there. It variates and even shifts its y-axis according to the data changed. And this is the absolute value graph, means what's the exact data there. And you can see the different sensors like temperature, humidity, acceleration, intensity, anything. Let's move to someone else, acceleration. These are three axis, x, y and z. We are showing it through a pie graph. And actually it's not much moving, so it's like an static data. There are three options. We have visualizing, actuating, analysis. Let's go to actuation. These are the, our setup is there. And we can just control these, those all through our dashboard. We can switch on or switch off anything. Actuation. Yeah, okay. Just switch on. Sir, it was working a few minutes ago. We made our thinker. Why did I have to? Remote printer, sir. It was working a few minutes ago, actually. Our remote printer did not work properly. How could you have a test? Yeah. No. Let me ask you another question. You have tested it in the normal environment where you have tried this out. So your Wi-Fi communication, et cetera, works properly. Yeah. There is one thing that you might want to write as an additional caution in a paragraph towards the end of your report, which you might even have. That, while Wi-Fi is extensively being used by a whole lot of people, when you actually implement it in the industrial setup or a home setup or a photograph, any other setup, this Wi-Fi connectivity has to be checked and cross-checked. And even small changes in the physical distribution of your sensors will have to be, will have to result in one more checking. This will be your, actually, seal item. Everything else will work. This communication could be made up of it. Just go to analysis part. Actually, this is the previous analysis. Actually, we don't have the four month data and year data. We have options for that, like our sensors, previous day, current month or current year. But as we have only previous data, we are showing that only. So these are for all the sensors. This is for acceleration at x-axis. Acceleration of what? At x-axis, means horizontal axis. Of a sensor, of a sensor. Now, go to actuation. Actually, our server is running in ASL lab. It's on a Raspberry Pi and we have run it. Only one suggestion, when you use that term, actuation of data. You're not actually actuating data, you're actuating device. Device, yeah, okay. Pardon me for that, actually, I'm just kidding. Okay. Anything else? So have you tried it with a real device, like a real fan or a real bulb? Sir, there is a real bulb, yes. I have that, it's burning a few minutes ago. Sir, there's a small difference between a bulb, which is part of a lab gadget. What's a bulb in our room? Sir, actually no difference, because we are using SMPS power supply. Sir, there is a huge difference. Sir, yes. Because the existing bulb, that works. Is on circuitry. And unless you rewire that circuitry, how will you be able to do that? Sir, it needs AC supply, 230 volt. So that we are giving using SMPS, that power supply we have brought here. So that is. We are using the normal supply that is given. Sir, that is connected to the adapter, like. Sir, will it be working? The last one, sir, will it be? Sir, will it be working? Sir, will it be working? It's kind of locking system, you can say. Sir, like you can actuate it anywhere from in IIT. Like if you open the dashboard in your cell phone, then also you can, if you press the button, like if the, it is connected properly to the Wi-Fi, then it will work. Two and a half years ago, I had controlled a robot working in Rajesh Kusalkar's lab from, if. Delhi. From Canada and the US, using internet. But internally it had exactly the same components. You are, I don't know, and so you can see me and other things on the robots. And he had actually put two different kinds of cameras. One camera on the robot, so that when the robot moves, you can see what is, what the robot is traversing. Another camera in the lab, so that you can see the robot itself when you are controlling. And both of these video streams were being put onto the internet through Wi-Fi. So Wi-Fi is an established mechanism. It works well. It's always the small things which create problems. But this is working. Okay. The different ESP models are there, but the IP just got changed, one is working. Okay, okay. Oh, IP got changed. That's a standard. I think just two ESP models are working. Good work. Okay, okay. Can we go next? Thank you, sir.