ps 1131 software workshop management techniques

PS 1131 SOFTWARE WORKSHOP MANAGEMENT TECHNIQUES CODE
PS 1131 SOFTWARE WORKSHOP MANAGEMENT TECHNIQUES SERIES

If this idea is pursued, the test program(s) should be freely available to anyone so that customers can conduct their own tests. It would be up to the person conducting the test to get the program into the programming software, and then into the PLC (the objective of this test isn't to standardise the programming software). The standard test program(s) would be in IL in text format. By examining the memory flags, you can see which tests passed, and which failed.

When an instruction test passes, it turns on a memory flag. Then you can use those instructions to help prove other instructions, in a boot-strap like process. First you exercise some fundamental instructions, and prove they work. This involves proving the instructions one by one. The next step would be to run the program and see if it produced the expected output. This means PLCopen would have to define a minimum instruction set and address types for conformance. The first and most obvious test would be if the PLC accepted the program and recognised all the instructions, addresses, and constants. At its most basic, it would be an IL program where each network (rung) conducted a different test.

Jeremy Pollard, CET The Caring Canuckian! In reply to Jeremy Pollard: Something that would be very useful would be a set of PLC programs that act as conformance tests. Or help understand why the world really hasn’t changed in 25 years. that sort of testing can help users understand why they may want to investigate using IEC61131, along with the PLCopen initiated programs such as motion control function blocks etc. That is part of the platform that PLCopen can support and nurture. or a Wago program file can be opened by 3s native. I still want to know if ST from Siemens can be cut and pasted into ControlLogix directly. If more users got involved then the outcome may be different. Its up to the users right now to figure things out for themselves - how's that working for you? but I'm not sure that can happen since the organization is funded by vendors. Then users can ask for PLCopen certified compatible products and technologies. and provide the users a list of who meets them. I submitted to the Board of Directors 4 or 5 years ago the concept of having a set of PLCopen standards or specs. all vendors will want to protect their segment. Whether the goal can be reached is still very debatable. PLCopen is trying to move the implementation of the standard to a different level, and as former managing director of PLCopen, the organization is not doing enuff towards that goal. Vladimir - I submit that the intent of the standard was to provide commonality between hardware platforms. Something I haven’t checked.Ĭheers from: Jeremy Pollard, CET The Caring Canuckian! Control Design Manufacturing Automation 3 Red Pine Court, RR# 2 Shanty Bay, Ontario L0L 2L0 705.739.7155 Cell # 705.725.3579

PS 1131 SOFTWARE WORKSHOP MANAGEMENT TECHNIQUES CODE

That is to say if you developed code using Wago's supplied programming system, I am not sure if you can even open the file using generic 3S software. If you develop in their IDE, then you may be able to re-use more of the code regardless of the However, there are a lot of companies that have private labeled 3S software (no slight against any of the other development vendors). The original premise of IEC61131 WAS to provide an independent platform - ain't happening!!

PS 1131 SOFTWARE WORKSHOP MANAGEMENT TECHNIQUES SERIES

You develop in the development environment for the hardware you are going to use.Ĭheck out my series at on IEC-61131 on what it is and what it isn’t.

Ps 1131 software workshop management techniques