No, I hadn't heard of it until now. It's a good idea, but it seems to be in a pretty early stage of development and being developed by not enough (maybe just one?) people.Are you aware of the OpenPLC project?
No, I hadn't heard of it until now. It's a good idea, but it seems to be in a pretty early stage of development and being developed by not enough (maybe just one?) people.Are you aware of the OpenPLC project?
Though I haven't used it, not having a need for PLCs. What I have read about it in various industry sources is those who would like to move in that direction are embracing it. I believe, based on other examples of such projects, it has a good chance of becoming a de facto standard when (and if, though that's what I am sanguine about) big industry players look for an easy in to the F/OSS world.No, I hadn't heard of it until now. It's a good idea, but it seems to be in a pretty early stage of development and being developed by not enough (maybe just one?) people.
I was not aware of it either, I certainly hope they allow the use of Boolean ladder display, if just logic block as the Smart Relays do, it won't cut it for me.Are you aware of the OpenPLC project?
I assume you meant "de facto" but it is already based on an actual standard, the same standard that all mainstream PLCs are:Though I haven't used it, not having a need for PLCs. What I have read about it in various industry sources is those who would like to move in that direction are embracing it. I believe, based on other examples of such projects, it has a good chance of becoming a defect standard when (and if, though that's what I am sanguine about) big industry players look for an easy in to the F/OSS world.
Only time will tell.
Which answers...The OpenPLC project was created in accordance with the IEC 61131-3 standard, which defines the basic software architecture and programming languages for PLCs.
https://en.m.wikipedia.org/wiki/IEC_61131-3I certainly hope they allow the use of Boolean ladder display, if just logic block as the Smart Relays do, it won't cut it for me.
Part 3 of IEC 61131 deals with basic software architecture and programming languages of the control program within PLC. It defines three graphical and two textual programming language standards:
- Ladder diagram (LD), graphical
- Function block diagram (FBD), graphical
- Structured text (ST), textual
- Instruction list (IL), textual (deprecated in 3rd edition of the standard[3])
- Sequential function chart (SFC), has elements to organize programs for sequential and parallel control processing, graphical.
There is not much (any) mention of what the hardware consists of ?Are you aware of the OpenPLC project?
Yes, I meant as a standard way to use open source MCU hardware to work with IEC 61131-3.I assume you meant "de facto" but it is already based on an actual standard, the same standard that all mainstream PLCs are:
Which answers...
https://en.m.wikipedia.org/wiki/IEC_61131-3
From the overview:There is not much (any) mention of what the hardware consists of ?
Just this :You can use it to upload PLC code directly to any board or system running OpenPLC Runtime ."
Is it intended to be PC based I wonder?
Is that Mitsubishi? if so their products are not free (and quite expensive too) but every now and then someone may be granted product for free. some 10 years ago we bought some Siemens product and not long after there was a freebee software...When I went with Mit's , they gave it me free.
It was the S/W they supplied free.Is that Mitsubishi? if so their products are not free
and make online program changes while PLC is runningThe ability to upload and monitor are such fundamental and ubiquitous features
Just curious… When would you want to make online program changes while PLC is running?and make online program changes while PLC is running
More often than not, actually.Just curious… When would you want to make online program changes while PLC is running?
You speak of higher stakes than anything I've been involved with. Very impressive stuff!once the PLC controls something substantial (main assembly line etc.) with 2000 stations and 5000 operators, [...]
and it gets more complex too. some systems require higher readiness. an example is a chemical plant. i was working on one making pure sulfuric acid [...] the entire plant must run in strict conditions in a very small window of key parameters (high pressure, high temperature, high velocities) [...] but if any of the key parameters wander outside of that small optimal window, plant starts getting dissolved by acid at a very rapid rate. so if things are out of whack, the whole thing turns into a pond in no time.
will companies start using "*duino" for multi-million dollar industrial PLC?
some companies are already selling the 'success stories'
https://www.industrialshields.com/case-study-automation-concrete-plant-gr
https://www.industrialshields.com/case-study-biogas-plant-automation-gr
i worked in many industries (chemical, automotive, nuclear, food etc.) and projects of different scale.You speak of higher stakes than anything I've been involved with. Very impressive stuff!
On a scale of 1-10, how interested would you be in getting involved with one of these projects?
I concur. Try a Hog slaughter-processing plant, It took two wash cycles to get the smell from my clothes.i did some work in food plants too and for the most part - i did not like it. things one can see or smell that just turn my stomach... i would rather work in a mine or foundry for a year than spend a day in a meet processing plant.
Thanks for your great response. Obviously from my question, I have zero understanding of PLC systems. In fact, I once lost a job because of that.More often than not, actually.
If a PLC doesn't keep running when you make a change, then the state of its outputs must be one of these 3 cases:
All outputs ON (obviously a bad idea)
All outputs OFF (seemingly a better idea)
All outputs retain last state. (eh... hard to say?)
Here's a scenario:
You're working on a bottle case packing line. The PLC controls all the conveyors; when they stop, when they start, how fast they go, how long they run, etc.
On one section a conveyor is running faster than the next one after it, so when the cardboard tray of (4) 6-packs makes the transition between the 2 conveyors, it ends up getting shoved a little sideways. You need to go into the PLC and change the speed value for when that conveyor is in the "sending case out" state.
If you stop the PLC to make this change, in each case:
All outputs ON - total pandemonium. everything turns on. Motors try to run both directions at once.
All outputs retain last state - if the ON-OFF-ON cycle is under a few mS, maybe it isn't noticed. Or, maybe some things get out of sequence. Conveyors kept moving while the PLC was out to lunch and when it comes back, things are not where they should be, and it doesn't know what to do. Usually the ON-OFF-ON is way longer than a few mS, so the 2nd scenario is orders of magnitude more likely.
All outputs OFF - everything stops. Including the case that was passing through the heat shrink oven, which takes 30 minutes to cool down. So 10-20 seconds later when the PLC wakes back up, the plastic heat shrink sleeve is already dripping off onto the conveyor but you still can't get that case out of the oven because you have to run around for 5 minutes resetting e-stops, manually jogging conveyors because cases are straddling between two conveyors and blocking 2 photo eyes (or zero) when they should be blocking only one, homing the palletizer, resetting light curtaints, etc. etc. When you finally get the line moving again, what comes out of the oven is the aftermath of a cardboard tray that was on fire for a few seconds before it was extinguished with exploding soda bottles which then melted and fused the whole mess to the conveyor.
So in this case it is advantageous to keep the line running while the change is made. And while not as drastic as all that, there are usually circumstances in every process where it is exceedingly more convenient to make the change without stopping the program.
I think I understand why you would think that way. I do a lot of non-PLC programming too, so I have one foot in each frame of mind.Thanks for your great response. Obviously from my question, I have zero understanding of PLC systems. In fact, I once lost a job because of that.
It appears to me that the frame of mind for a PLC is vastly different than a procedural programmed system. All of the issues you cite can be simply resolved in software/hardware. Or at least in my mind
Thanks