Programming OWEN controllers
The purpose of this article is to describe the features of programming OWEN controllers in order to avoid common mistakes made by novice users who have recently encountered this brand.
The main advantage of the controllers: a Russian brand, quite budgetary, with good technical support. Suitable for many things and the market for implementations is constantly expanding.
The main disadvantage: the lack of elaboration of hardware and software compatibility between the components. That is, it is, of course, but not everything is convenient and not everything is intuitive.
The reputation of the brand is, let's say, a top three, due to the large number of those who, having tried it once, without achieving any significant results, immediately hangs a label on the brand, calling the products bad words.
Some users sometimes try to compare SIEMENS, SCHNEIDER ELECTRIC brands with OWEN products. Such a comparison, of course, is honorable, but still not correct. You need to understand that OWEN is a relatively young brand, and so far it is used only in Russia. As a rule, it occupies niches of small systems, up to 1000 channels. So far, brands in Russia are underdeveloped or absent for managing large enterprises of a continuous cycle, and OWEN does not claim this niche yet.
What difficulties users may encounter when they encounter OWEN PLC programming for the first time.
Here are some examples:
1. Difficulty in understanding and understanding the programming language: ARIES uses a specific programming language based on the IEC 61131-3 standard, which may differ from more common programming languages such as C# or Python. Users who are not familiar with this language may have difficulty learning and understanding its syntax and functions.
2. Limited Resources and Capabilities: Some models of OWEN controllers have limited resources such as memory or processor power. This can limit programming options and require more efficient use of resources. Some types of libraries will not work, etc.
3. Lack of Documentation and Examples: Some users may find it difficult to access complete and understandable documentation or programming examples for specific OWEN controller models. This can make it difficult to learn and use the controller's capabilities.
4. Bugs in the program and debugging: When programming the OWEN controller, errors and problems in the program may occur. Debugging and fixing these bugs can be tricky, especially for those who are new to programming or for complex systems with a lot of interrelated functions. Over time, experienced users develop a reflex of frequent saves and compilations of the project with loading into the simulation debugger
5. Requirements vs. Expectations Mismatch: Sometimes users may find it difficult to implement required functionality or achieve expected results with an OWEN controller. This may be due to hardware limitations, poor program design, or lack of knowledge and experience in selecting or programming controllers.
In case of difficulties, it is recommended to refer to the documentation, forums or communities specialized in programming and using OWEN controllers. It is also useful to seek help from experienced specialists or developers who have experience with these controllers.
Important steps when working with OWEN controllers:
1. Determining the range of requirements. Before starting work, it is necessary to approve the functions and tasks that the OWEN controller will have to perform: control of temperature, pressure, lighting, channel processing speed, input/output signal composition, and so on.
For example, PLC2** have a wider range of functionality than PLC11*, such as, for example, communication with various DBMS. There are also ample opportunities for processing various exchange protocols.
2. Controller Model Selection: ARIES offers a variety of controller models with different capabilities. You need to choose the model that best suits your task. It should be noted that we do not take into work PLC63, PLC73, PLC100 and PLC150, as we consider them to be insufficiently developed, with hidden architectural flaws. The main models on which we hand over projects are PLC210, PLC110, PLC160, SPK107.
PLC110 is very reliable and proven, easy to program. PLC210 and SPK107 are stronger controller models in terms of functionality, but require more experience and accuracy in programming approaches.
3. Work with documentation. It is best to first study the user manual and technical documentation for the selected ARIES controller model. They contain information about available functions, inputs/outputs, communication protocols and other parameters. It should be noted that due to the constant improvement of the hardware and software base, the OWEN company is forced to fight for the relevance of the current documentation. Given the volume of deliveries and the wide range of products, there are inaccuracies in such documentation and this point requires a careful approach.
4. Setting up and testing the controller. It is very important to check the communication capabilities of the equipment on a demonstration stand before handing it over for installation. Apply power, set all necessary addresses, make sure that all modules connected to the bus respond. From personal experience: either the equipment is not checked well enough by the technical control department and the quality differs from batch to batch, or incorrect installation leads to difficulties in setting up communication.
5. Terms of reference. It is necessary to describe in as much detail as possible the inputs and outputs of the future system. Separately, it is worth describing the algorithms of the system, drawing up a functional diagram. If the Customer is not ready or cannot draw up the terms of reference, then it is worth compiling it yourself, agreeing it with the Customer before starting work. Examples of drafting terms of reference here: https://fast-project.ru/specifications/
6. Controller programming. To create a controller control program, special software is used, provided free of charge by ARIES (Codesys 2.3 or Codesys 3.5). The application program can be written in the IEC 61131-3 logic programming language. In addition, graphic languages for constructing contact diagrams, functional blocks are available, and the text programming language ST is well developed.
7. Testing and debugging. After downloading the program to the controller, it is worth conducting tests to check the correct operation and response of the controller to various situations. If you find errors or problems, you should debug the program and make the necessary changes. Carrying out factory tests of the cabinet before sending the assembled product can significantly save time on commissioning and identify significant shortcomings at an early stage.
8. Warranty. It is worth seeking guarantees from the Contractor for the product being created, both for the program itself and for the equipment. The fact is that when you start and quickly check, you may not find hidden flaws. If such shortcomings are found, it will be easier to eliminate them by contacting the Contractor if there are agreements. Try to get the source codes on the controller. This will help to quickly restore the system's performance in case of a breakdown and lack of communication with those people who previously handed over the system.
#ProgrammingOWEN, #ModernizationITP, #PCSEngineer
Be the first to comment