Proximity switches and possible issue

[electric06]

I don't have RS5K to look at the whole code, so I might be missing something by saying this. Once you put your part on conv. 1 and that part moves to conv. 2 and stops, then you put another part on conv.1, what tells the conv1 & 2 to move parts to conv.3?

 

[backendcode]

Create a DINT tag for each conveyor as an indexer.

Conveyor1_INDEX
Conveyor2_INDEX
Conveyor3_INDEX
Conveyor4_INDEX
Conveyor5_INDEX

When the machine first starts up (no product on any of the conveyors), MOV a 0 into all the indexers. When your prox is made on conveyor 1, MOV a 1 into the Conveyor1_INDEX. As the state of each prox changes, along with your timers giving additional control, you can use each conveyor's index DINT to keep a running state of the entire machine, MOVing 0-3 into each of them at the proper time. But you don't actually have an entry and exit prox for each conveyor, you only have an entry prox for each conveyor. USING the entry prox of the next conveyor as an exit prox is not the same as actually having an exit prox.

Hope that helps!

Yeah, I am getting close but Once I get the clear pic I will write a PLC code and post it here. Just wondering if I can get sample code from the previous similar application if possible?

Thanks again!

 

[backendcode]

I don't have RS5K to look at the whole code, so I might be missing something by saying this. Once you put your part on conv. 1 and that part moves to conv. 2 and stops, then you put another part on conv.1, what tells the conv1 & 2 to move parts to conv.3?

I just posted the code for conveyor 1 and conveyor 2. Part will move from conveyor 1 to 2. depend upon conveyor 2 condition and part from conveyor 2 will move to 3 depend upon conveyor 3 condition and so on.

Thanks

 

[LoganB]

What PLC and firmware version are you using?

 

[backendcode]

What PLC and firmware version are you using?

I am using AB compact logix L24ER-QB1B with firmware 20.04 and of course using the same version of rslogix5000 but I do have rslogix 5000 V 19 as well.

Thanks

 

[LoganB]

Attached is a very simple setup for indexing. You don't have the ability to toggle between 4 different states if you only have 1 prox per conveyor, so you can only use state 0 for NO product, and state 1 for Product PRESENT.

Keep in mind this doesn't have safeties or anything like that, it's just an example of the indexing.

 

[backendcode]

Attached is a very simple setup for indexing. You don't have the ability to toggle between 4 different states if you only have 1 prox per conveyor, so you can only use state 0 for NO product, and state 1 for Product PRESENT.

Keep in mind this doesn't have safeties or anything like that, it's just an example of the indexing.

Awesome!! I am going to look into code and understand!

You are the best and thanks a lot

 

[LoganB]

I'm certainly not the best

But I'm glad I could help! Let us know if you have any more questions

 

[backendcode]

Actually, your code helped me to take a different approach to the same problem and how we can use move function to manipulate and set some values and equal them to some condition. Thank you again!

I got one stupid question for you, how S:FS work? I am trying to find the explanation but haven't got any luck so far but I will keep trying to find more about it. I am rewriting my PLC code using indexing and move functions and I will show you when I will do and later on my plan would be to use Add-on instruction to reduce the code and it will also help me to easy troubleshoot and make changes would also be easy!

Thank you again!

 

[LoganB]

S:FS is the first scan bit, so it goes true for a single scan when the system is first powered on.

 

[LoganB]

There are some caveats to using it, which are explained in this post:

http://www.plctalk.net/qanda/showthread.php?t=6464

 

[backendcode]

Ok LoganB! Thank you again!

 

[LoganB]

 

[backendcode]

TGIF!

Cheers!!!

 

[JesperMP]

I read the topic header "Proximity switches and possible issue" as if there is a potential issue with some proximity sensors and their application, and you want to inform the community about this. How very helpful.

It turns out you are actually asking about help designing your application, and the proximity sensor is not the "issue".

Is clickbaiting now a thing, even in forum posts ?