 So, I'm Akshay Am, I'm part of ideal lab here and I'm working as a research assistant in Posse project. So I'm here to pitch an idea about Open PLC, what we are working on, what we are planning to do in the coming months and some requirements that we have a few positions to be filled as an interns. So I'll also give you the requirements in the end of this session. So I'm working on this project called Open PLC. So you might have seen PLC or you might have heard of PLC, it's a program of logic controller. So PLC is generally used for automating a task in industry and so it can be considered as a digital computer. It's a robust digital computer which can perform multiple tasks, it needs multiple inputs and it should be robust as in it should have extended temperature ranges for operation. It should be immune to electrical noise as in the hardware might be subjected to a lot of electrical noise and so it has to be immune to that and it has to be resistant to vibration and other physical stress as described in the standard which we follow. So we are currently following the standards as proposed by IEC. So IEC has different verticals so we currently follow IEC 61131 standard so the standards give a specific tolerance limit to which the vibration physical stress is allowed. So the hardware should work well within the constraints as given by the standards. So PLCs are used for automation and control. So automation is basically delegation of a human activity to machines to achieve some of the points which I mentioned the slides. So it may be higher productivity since most of these machines can work 24-7, ideal conditions with very little maintenance. So automation can increase the productivity, automation can give you a better end product because you have more control over the manufacturing process then there is also the efficient use of energy and resources and improved safety in working conditions. So automation is the future and we are already seeing it. So you might have seen robots in action in manufacturing facilities in automobile manufacturing sector in pharmaceutical industry. So automation is the future and we are trying to make a hardware which can perform this task or it can ease the migration from a classical approach to open PLC-enabled industry. So why PLC? So before PLC we had this classical control where we had relays, switches. So we had switches to give a voltage or to give a change and relays to control a device. So the relays which systems existed way before 1960s and the problem with those systems was the poor scalability, the high on bend and spot, the fault detection poor reliability. You must have seen, right? See when you have a basic structure, basics which relays circuits, the problem is that you cannot scale it beyond the limit and when you scale it beyond the limit then what happens is you will have breakdowns at some point. You might see a lot of issues in automating the task as such. Reusing the modules are not possible because these modules are hardwired, right? So there's a lot of issues involved when you have a switch and a relays circuit. That's a very basic hardware control. So then we have the PLC. So in PLC what we have is a microcontroller controlling high voltage devices, right? Which is connected to a dedicated power supply and it's also connected to a programming device. So you might have seen some PLCs made by Siemens or ABB, right? So how many of you have seen a PLC? Okay. So how many of you are electronics? How many of you are an electronics background? So very few people. Okay, so basically it's a computer and if you, so it's a computer which have relays on one side for output control and isolated inputs for taking in voltage voltages. So there will also be power supply, dedicated power supply because in PLCs the controller might operate in one voltage whereas the IOs might operate in another voltage, right? There might be other devices like an ADC or a DAC which might operate in another voltage. So you might need a separate power supply model which can deliver these different power voltage rails. So that's a general PLC here and then we move on to the programming part. So you have a hardware, right? You have a hardware which can be programmed and you have several inputs and outputs which can be controlled. So PLC programming is done using, I mean in IEC 60131 standard we have five methods or five programming languages. Office three are a graphical and two are textual. So ladder program, function block diagram and sequential function chart. So SFC, LD and FPDs are graphical programming tools or graphical programming languages. So they have graphical programming tools to facilitate the programming. So ladder, I have shown a ladder rung, I have about three rungs, four rungs here, right? So I have two main rungs, right? How many of you have programmed the ladder? Programmed in ladder? None, okay. So basically ladder programming is a very basic graphical way to program a relay. So we have some relay output or this relay can be connected to motor, okay? So you have switches. So you have switches which can be normally on, normally close depending upon what you want. And so what happens is you have rungs which means these are one is input and one is output. Or one may be the power rail and one is intended input stage. So we are connecting the two poles using a switch and that switch is actually something which is implemented in the controller instead of having a hardware switch, okay? So that is how ladder programming is done. Instead of having a real world switch, we have a virtual switch and the logic is then converted into bytecode or the machine code and then compiled to the controller. So then we have functional block diagram, structured text, instruction list and SFC. These things, the structured text, instruction list and sequential function charts are not being used these days. These days we have moved to, I mean industry has moved to ladder programming and functional blocks. So functional block, you might have seen functional block diagrams in action even in normal programming methodologies like, for example, if you have used nodred or any graphical programming tools. Here you have functional blocks which perform a specific application, right? It might have an input function block, output function block, something a roll generator or roll function, right? So something like that. So that's a functional block diagram or the industry also use structured text. Structured text is something which forms the back end of the functional block diagram. So when you have something like a functional block like, okay, input stage, the input stage is actually realized using some structured text, okay? That is how the standard is being used. This is what we have right now. We have a single board which can be used to do a lift experiment, a heat and a heat and fan subsystem or a traffic like experiment. So it's a single board which can be used to perform basic experiments in ladder, okay? This is what we plan to achieve in the next two months. We are planning to make a hardware which is compatible with runtime called Forte. The hardware should have support for CAN and Ethernet. It should have isolated 24-volt input output ports and isolated ADCs. It should have support for add-on cards via serial peripheral interfaces, such as SPI, I2C. And the software part, we are planning to develop applications using functional blocks in IEC 614.9 standard, which is a relatively new standard. So we are trying to migrate, we are trying to support, make support and, I mean, support documents and hardware so that industry can migrate from the IEC 6131 to IEC 499. And the software part will also be exposed to setting up a headless plug-and-play module and the activity, conducts and policy-aware IoT applications and legacy support for ladder. We also should have support for the previous system. We cannot just randomly migrate to the new environment. So what we're planning to do is we will migrate to the new environment, but still we'll keep the legacy support. So this is the open PLC version 2.0 technologies. So for the hardware, we'll be using KitKat for schematic and PCB. NG size for simulation. So all the hardware is planned to be released under OICL license. The current hardware will also be released under OICL license. Then opens a software involved, LDMicro is a tool used to program a ladder. Then we have 4DAC for functional blocks. Eclipse Canada will be used for the front-end. The hardware, the target machine will be the next platform. So we'll only use GPL or LGPL or EPL licenses. So 4DAC is based on EPL, whereas most of the code which is written in SCADA is actually in GPL. Whereas Eclipse Canada, there are two forms of SCADA involved. So Eclipse Canada will be EPL. And you can learn more about these in the upside, from the upside of 4DAC or from Open PLC upside. Okay, so we need three passionate individuals who can contribute to the front-end, who is an application developer, who can develop programs in ladder as well as functional blocks. And he'll also be exposed to a few HMI interfaces, like Eclipse Canada. And he'll also be introduced to concepts of industrial IOT models, basic public subscriber models using MQTT and constraint application product. Then we'll also need a Linux developer who has really good batch skills and who is willing to learn more about network interfaces. And some interfaces in C for SPI to C, because we will need to. So most of the hardware is based around Linux. We still need a lot of, we still need to put in a lot of effort in terms of driver development for the add-on cards. So we'll need people who can do that. Then hardware developer is someone who can take care of DC-DC designs, relay boards, breakout boards, basic designing using a CAD, an enclosure designing using any of the open source tools, like Cochopelli, anti-money, any of those, or even open source CAD. So this is the requirement. So if you're interested, you can write to me or you can contact my manager, or I don't know how it is being done. So yeah, you can contact the right person. You can also write to me. And if you have any questions, you can write to me. So any questions right now? No, thank you.