What can i do to get better at coding controls logics?

and don't be condescending to people. that means talking down to people.

This may seem like an after thought, but I've witnessed the damage this can cause in a plant. Engineers a lot of the time just assume they are more intelligent than people like operators or maintenance. The truth is simply that engineers are generally more educated about certain aspects of how the machines work, and that doesn't necessarily mean more intelligent.

I've learned that operators are invaluable in my job, because they are the people that know the process the best. ALWAYS value the input operators and maintenance people can give. Sometimes it won't be helpful, and sometimes operators can be downright annoying. It's great advice, however, to stay on their good side and engage them whenever you can for input.
 
This may seem like an after thought, but I've witnessed the damage this can cause in a plant. Engineers a lot of the time just assume they are more intelligent than people like operators or maintenance. The truth is simply that engineers are generally more educated about certain aspects of how the machines work, and that doesn't necessarily mean more intelligent.

I've learned that operators are invaluable in my job, because they are the people that know the process the best. ALWAYS value the input operators and maintenance people can give. Sometimes it won't be helpful, and sometimes operators can be downright annoying. It's great advice, however, to stay on their good side and engage them whenever you can for input.

I agree! I was kinda both making a joke and being serious. You def. have to take the input w/ a grain of salt. especially the what they think is the problem part. but 99% of the time, if they say something is wrong, something is wrong. you just have to find out what is wrong.

additionally, the better you treat people... (duh button) the more likely they will help you. and don't think they can't help you.
 
and get used to everyone thinking the problem in the black magic mystery box (aka, the thing they don't understand).

plc a function (f of x). bad input = bad output. good input bad output, it probably the program.

good output no worky = electrical.

find the domain where f of x equals.... it the plc. but i didn't finish. no, i'm convinced it the program.
 
Last edited:
When working on programming, is it possible that a logic in a lower rung will cause a previously correct (before the later logic was added) rung before it to fault?.
This leads me to believe you're unclear on the PLC scan cycle. A cursory look at the PLC 1 curriculum doesn't mention this subject. Was the scan cycle covered in that unit?

Also PLC boot camp may be useful.
 
also, seen some plc's and hmi's able to change a tag between rungs. ab and wonderware come to mind.
 
Don't get discouraged. Programming is an art that is honed over time. Right now, you've got this toolbox full of tools that you don't know how to use. So doing even the simplest things is like pulling teeth! It can be very frustrating, I know. But if you keep at it, you'll eventually get over the hump to the point where it actually becomes "fun" because you'll *know* the toolbox, and then it'll be all about how creative you can be with building functionality into your programs - and that's when software development starts to become magical.

I would just apply for a job with a Controls company as a Junior Engineer. I know Chem-E's who have done just that. No programming experience in college to speak of. Then you'll get exposed to actual applications that you can analyze and learn from. Plus, you'll have experienced people around you who can answer your questions as they occur to you.
 
Not that I really have a foot to stand on in regards to experience (I am quite young for this field), but I think that truly one of the most important things to understand in regards to programming is the overall process, the end goal. I always make a list of inputs and outputs before I do ANY programming, as this allows me to understand exactly what I'm working with. When one has a grasp of the tools they are working with, they can start working on the actual project. Someone mentioned working backwards from the output and that is a really great way to approach programming most of the time. I feel like with an eye for process any engineer should be fine transitioning, it's just pretty daunting at the start, like myself transitioning into chemical engineering.

While this isn't a part of your question, I will mention that many of the process engineers that I work with have their degrees in Chemical Engineering. I work in Food and Beverage in the Central Valley of California, which is a huge market for food and beverage manufacturing (we have the worlds largest single site winery and the worlds largest single site cheese plant, one of which I currently work for). If you were willing to come out to the desert between the mountains, that is. 🍻
 
This leads me to believe you're unclear on the PLC scan cycle. A cursory look at the PLC 1 curriculum doesn't mention this subject. Was the scan cycle covered in that unit?

Also PLC boot camp may be useful.


you are correct. I am NOT 100% understanding scan cycle. the PLC 1 mentions it briefly by simply saying something along the lines of "it'll read this instruction on the left, and if logic passes, do the output on the right before going to the next rung"

however, when the scan gets more complicated by adding rungs with branches using the same output bit on a previous rung, or if there are branches on the logic side of the program (left side) I get confused on why the right side doesnt/does get energized most times.
 
Over 25 years ago, I wanted to learn this complicated PLC thingy.
More and more machines were coming to my factory with them in.

My boss would not pay for software or schooling preferring to get the 'experts' in when they went wrong or needed changes.
I paid for a quick course myself and it was a complete waste of money and time.
I was no wiser when the course had finished
(looking back and knowing what I know now - the tutor was useless.)
He concentrated on 'scan times' and scan which meant nothing to me and nothing practical.
So I bought a PLC and the software and leads and set them up in my shed.
I spent 2 years after work in that shed teaching my self with books and trial and error.

There is no quick route to understanding PLC's and being competent - but getting an actual plc and software etc is far far better for understanding what is happening.
 
dude, i was so there at one point. i feel ya. i wish i was a better teacher. i so want to help you right now but don't know how.
 

Similar Topics

I am making massive headway into the PLC replacement i have mentioned in various threads, its all running and even the AB stepper drive was easy...
Replies
18
Views
8,505
Good Afternoon , It seems like we always have problems with using Type J Thermocouples with our slip rings . Would using a RTD at 10...
Replies
6
Views
1,622
I am beginner in B&R Automation Studio and TIA Portal. Have an experience in electrical part of PLC cabinets. Now its time to get a new skills...
Replies
8
Views
1,632
Bla Bla Bla, why doesn't it work, l need help and l don't understand PLC's. Or better they understand everything, but can't understand +1 -1 = 6...
Replies
22
Views
5,960
I rarely need to add a network card to the drives we install... very rarely. But my sales-guy said he needs to quote a network-connected ACH580...
Replies
6
Views
2,555
Back
Top Bottom