All language subtitles for 4. H PLC Battery Fault Detection via Interrupt

We'll come back.

What we want to do today is that we want to add a battery detection mechanism into our program.

We will continue using our previous program called the UDEMY and Escort Posse.

So the first thing we want to do is we want to add to interrupt where the fun the program actually automatically

detects whether there's a fault with a battery with the power supply system.

OK, and this battery for detection is called the will eighty one.

So what we want to do is we want to add the opiated went into our program.

So we're at the opiated one by going in new object organization block and then we change the Oveta and

change it to become opiated.

Eighty one.

Now the symbol name is automatically generated.

Skopje's unescorted felty open the loop or that will be eighty one and you will see that inside a temporary

variables.

Um all the, all the uh all the parameters are already defined and if you want to learn more about it

you can always, you can always go to the Seimas website and download this PDF.

That's the name of the uh this is the name of the PDF.

You can download, you can search for it online and download.

It's free.

So what you want to do, what we want to achieve today is to use this opiated one and detect any of

the.

Power supply problems and there are many types of power supply problems, for example, as described

in this table here, at least one backup battery of the central rack is exhausted or probably eliminated

the battery fault.

OK, this event occurs only if one of the two batteries fails.

If the second secondary if the second battery also fail, this event will not occur again.

So basically, if it happens, it's for four for power supply with two batteries if the first battery

is exhausted.

The fall will occur, and if this is not taken care of in the second battery, fault also occurs without

clearing the first battery fault.

This would not be this.

Olby will not be called again.

OK, and another type will be the big bag of Boornazian essential brake failed or the failure of the

second of the 12 Bovell battery supply or at least one battery backup battery as problem.

Or you can't you can go through this on your own is depends on your application and what you want to

do.

Exactly.

And how would you want to detect the battery problem?

What I want to show you today is how you actually write the program to detect maybe the most common

ones and then you can decide what you want to do, how you want to make your program, incorporate this

into your program for better problem detection, especially for maintenance purposes.

OK, so let's say if we want to make sure if we want to be able to detect a battery fault as a battery

fault.

OK.

In any of the cities, in any of the cities we can be of the Mississippi, you or the slave C.P.U.

So what we want to do is we want to.

Pick the right one.

OK, there are so many variables here, you want to pick the ones you want to pick, the ones that is

useful to you.

OK, um, one thing I want to tell you is that this Olby eighty one is only triggered when there is

a false.

When the focus appears OK.

This obesity one is not like other obese, it's not like the time you threw up or the Obi Obi Wan,

which continuously just keep rolling on and on.

It's not something like this.

Obesity, when only have only only is called when.

Let's say the battery is exhausted, it'll be called once and then when the battery is replaced and

reset.

It would be called again.

OK, so.

Looking at this variable, OK, opiated one, underscore Ebbe and his core class there to.

Two possible values, the Olby or the thirty eight and thirty nine, which is the incoming I, which

is the outgoing and the incoming outgoing, means that the fault has disappeared.

What has been rectified?

Thirty nine means that the fault just came in.

OK, so in that case, which is Koku, this was also here to the description.

So you say, OK, if this is the case, if this is an incoming event, this would be three nice of incoming

events, that means something's happened.

OK, we don't know exactly know what happened.

OK, say something.

Something's wrong.

Something's wrong with the piece.

We don't know what it is yet.

OK, OK, if if if the class is just make this smaller and it is a bit bigger, then we can see clearly.

If the class is thirty nine, that means something's wrong.

OK, we don't know exactly what is wrong, but we'll find out what is wrong by using this.

The.

Sir, it's just decoding a little bit better.

We know something's wrong.

We don't know what is wrong, what is wrong is that we have to choose the fault, underscore it, the

fault identification code.

OK, let's say what we wanted to do is we want to know that at least on the battery in the central wreck

is exhausted.

OK, so we'll put.

The value of the past 16 past twenty one.

OK, that means at least one better.

Just copy the description here for is your understanding later on.

OK.

OK, if that's the case, then we know exactly.

The incoming events the is caused by at least one of the backup batteries of essential exhausted in

this case, we can just do our logic.

Let's say if this happens, we want to sit and talk to you two hundred point zero to one, OK?

Now, you may be asking, well, if this is a redundant policy, it has two sides and it has the massive

policy, so it has to return to the slave CPU side.

And I want to pinpoint whether the better battery fault was coming from the master side or the slave

side.

How do I do it?

Well, it's not that difficult because you can always choose the recipe.

You OK?

So in that case, let me open another career and another network and just, uh, and just put some common

of which side of the c.p.u is coming from default.

It's coming from.

Right.

OK, so we know that we are dealing with this, so we just go like this, we know we're dealing with

this now, what are the values possible for this rescue?

OK, we go back to the.

To the PDF here, and then we highlight this for easier viewing.

OK, we know that the first eight bits will always be zero, will always be zero zero two, but seven

eight bits in total.

It will always be zero four bits, eight to 15.

It depends on whether you're using a standard CPU or using a redundancy.

OK, for standard CPU, meaning that's a single CPU, it doesn't have a redundancy value is always zero.

So the entire word from zero to seven and eight to 15.

So basically from zero to 15, everything is zero.

Everything is zero.

However, if you're using if you're employing a redundant CPU and you want to pinpoint which side was

coming from, then you have to specifically type in which C.P.U do you want to monitor?

For example, you'd want to monitor wreck one.

Actually, zero, because for redundant p.l.c., OK, the two zero in Iraq, one, so if you want to

if you want to monitor zero and then you want to.

Look at the C.P.U.

Of the three, the massive C.P.U, then how do we do it?

OK, and put this step aside so I can see you, sir.

OK.

It's easy for us to see.

It'd be easier for us to see, instead of flipping back and forth, we can just look at both on the

same screen here.

OK, so if that's the case came in second.

So we're looking at this right now.

Yeah.

So.

First of all, we have to know that the bits, uh.

Accounting from right to left, so the leftmost bit.

The left, the left most, that is 15.

OK, so we have to also go backward.

OK, so since we're typing in one bit at a time, we use binary and the way.

Seimas possie knows how do we tell the seaman's posse that we were typing in a binary format and so

we have to give it to hash, then the then the then the compiler.

We know we know that we're talking in the.

Bad news for me, so let's go back to school from 15, 14, 13, 12.

So it take to be 15, 14, 13, 12, and then we're talking about 11.

Turkey would be 11.

We have to decide whether whether we are monitoring the reserve posse or the CPAC.

Let's say we're monitoring the the, uh, the marsupial's events one, OK, and then they tend to be

ten is the direct number.

So let's say you're so zero is B ten, nine, eight.

So, OK, these three number three bits will make up the record number.

And then for seven to zero to four seven zero zero zero, so did seven six five three four three two

one.

So that's just to make sure we have 18.

But we have 16, Bitsie.

OK.

One, two, three, four, five, six, seven, eight, nine, 10, 11, 12, 13, 14.

Uh, it's not big enough for you, but it was just kind of for me.

How would you describe for me?

Do you want one, two, three, four, five, six, seven, eight, nine, 10, 11, 12, 13, 14,

15, 16?

OK, so this is, uh, uh, EPU.

Zero.

You.

OK, if we want to know if we want to have specific actions for this C.P.U detection, we can say if

this happens again, if it's incoming.

Battery pack of battery phones.

If the system detects incomparably fault and it's coming from a return, then please see what this is.

This is our, you know, configuration rect zero a.m. C.P.U.

Then we can do some action, for example, said the memory to one hundred point one.

OK, that's it.

OK, then you would be asking, OK, what happens when a one detects the other one.

The other side of the CPU was pretty well you have to do.

I like to make separate sections for things you see reviewing the all we have to do is put mastership

and reserve C.P.U.

Right.

This is what we want to do.

We want to a direct zero.

Which one let we do this one, the reserve C.P.U?

OK, so in order to change this correct one, that means that bit eight to 10 will be instead of a zero

zero zero, it will become zero zero one.

So let's try again.

Is 15, 14, 13, 12, 11, 10, eight.

Ten, nine, eight, so these three bits, the direct bits and changing this to one, right, and then

the 11th bit.

I'm changing it in the 11th, 11th, bit of changing it to zero.

OK, of course, I was just given another bit, number two hundred and two.

And now if the posse if the battery on the policy side, on the master side has an error and the error

of the battery has some some faults.

OK, um.

It will give you two hundred point zero and telling me, hey, something's wrong, OK, please go check.

But if you want to know exactly is he coming from the other is coming from the left side, you can change.

You can look at this, these two bits, OK.

And two hundred point one, it means that the incoming battery fault is coming from zero domestic policy

or is coming from this bedazzling erm two hundred point two.

Is the incoming events coming from Brek one, the Reserve C.P.U.

Now, of course, you don't want this to be the end of this block, because once it's said there's no

place to reset this.

And if you if this is connected to discarded in the what, we'll never be able to be reset.

So we want to do is one have a mechanism to to reset this.

OK, so what we have to do is very straightforward.

Just copy this.

OK, and we want to to change the outgoing event right now going to.

Sorry, I get you it and then changed this to become thirty eight.

OK, same idea.

We we're looking at this fault here, OK?

We haven't changed the fault.

The fault means that.

Default means that the battery for them has lit, OK, or that's the problem eliminated.

Remember this?

Obeidi was only called once when it failed when it goes into a vault is also called once more when the

vault disappeared or the problem is eliminated.

OK, so if you took over the battery, if you took out the battery, this will be called the Obi Obeidi.

One will be called due to the event.

Thirty nine.

If you reinsert the battery, a healthy battery and hit the reset button, this will be called again

under even thirty eight.

OK, so in this case one event, thirty eight is called.

Then you reset this bit.

OK.

So the battery fault would be this would disappear.

OK.

Similarly, if you want to if you want to try this.

We want to know exactly which side it is, then we just have to copy this one more time.

OK, and then.

See, it is easier to say, oh, we just say if the fog disappeared, okay, if the fog disappeared.

If the thought disappeared, the problem eliminated, then we just reset the bit, that's it.

Right.

It's not that difficult.

He said it.

OK, that's all you that's all you need.

We need this all we're doing today, OK?

And then we know exactly when a thought has occurred, a weight gain of four.

So could you think you've been through, you know, when the fault has disappeared using even thirty

eight?

What exactly it is OK if is twenty one and at least one back a battery of the essential records.

Exhausted if we want to look at all the faults, ok, for example, we want to look at the failure of

it.

Twenty four volt power supply in at least one of the redundant wrecks.

Then we just change this from a twenty one to a twenty seven.

So you can see that's it.

That's what you want to do or you have to do is change this to a twenty seven and of course you to up

the economy, which is why we're not going to do it here.

But if that's what you want to do, that's what we can do.

OK.

So let me change change this back to twenty one and then you can download this and, uh, go ahead and

have a shot at it and see if that's what you want to do.

Well, thanks for joining this

video and hopefully you've learned something from it.

Thank you.