Programming OWEN controllers
Programming OWEN controllers for novice users.

The main advantage of the controllers: a Russian brand, quite budget-friendly, with good technical support. Suitable for many tasks, the implementation market is constantly expanding.
The main disadvantage: insufficient elaboration of hardware and software compatibility between components. That is, it is, of course, but not everything is convenient and not always intuitive.
The brand's reputation is more likely to slip to the top three due to the large number of those who tried it once, did not achieve significant results and immediately put a label on the brand, calling the products bad words.
Some users sometimes try to compare the brands SIEMENS, SCHNEIDER ELECTRIC with the products of the company OWEN. Such a comparison is, of course, honorable, but still incorrect. You need to understand that OWEN is a relatively young brand, and it is used so far only in Russia. As a rule, it occupies the niches of small systems, up to 1000 I/O channels. For the time being, brands for managing large continuous-cycle enterprises are not sufficiently developed or lacking in Russia, and OWEN does not claim this niche yet.
What difficulties can users encounter when they encounter OWEN PLC programming for the first time.
Here are some examples:
1. Difficulty in understanding and perceiving the programming language: OWEN 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 OWEN controller models have insufficient resources to achieve the result, such as memory or processor power. This may limit programming capabilities 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, which may complicate the process of learning and applying the controller's capabilities.
4. Program errors and debugging: When programming the OWEN controller, errors and problems may occur in the program. Debugging and fixing these errors can be difficult, especially for beginners in 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 a simulation debugger.
5. Inconsistency of requirements with expectations: Sometimes users may encounter difficulties in implementing the required functionality or achieving the expected result using the OWEN controller. This may be due to hardware limitations, incorrect program design, or insufficient knowledge and experience in programming OWEN controllers.
In case of difficulties, it is recommended to consult the documentation, forums or communities specializing in programming and using OWEN controllers. It is also useful to seek help from experienced specialists or developers who have been dealing with these controllers for a long time.
Important steps when working with OWEN controllers:
1. Definition of the range of requirements. Before starting work, it is necessary to approve the functions and tasks that the OWEN controller will have to perform: temperature, pressure, lighting, channel processing speed, input/output signal composition, and so on.
For example, PLK2** have a wider range of functionality than PLK11*, such as, for example, communication with various DBMS. There are also extensive processing capabilities for various exchange protocols.
2. Choosing a controller model: OWEN offers various controller models with different capabilities. It is necessary to choose the model that best suits your task. It should be noted that we do not employ PLK63, PLK73, PLK100 and PLK150, as we consider them insufficiently developed, with hidden architectural flaws. The main models on which we deliver projects are PLK210, PLK110, PLK160, SPK107.
PLK110 is very reliable and proven, easy to program. PLK210 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 study the user's manual and technical documentation for the selected OWEN controller model in advance. They contain information about available functions, inputs/outputs, communication protocols and other parameters. It should be noted that due to the continuous improvement of the hardware and software base, OWEN is forced to fight for the relevance of the current documentation. Given the volume of deliveries and the wide range, there are inaccuracies in such documentation and this moment requires a careful approach.
4. Setting up and testing the controller. It is very important to check the communication capabilities of the equipment at the demonstration stand before putting it into installation. Supply power, set all the 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 the inputs and outputs of the future system in as much detail as possible. Separately, it is necessary to describe the algorithms of the system, to draw up a functional scheme. If the Customer is not ready or cannot draw up the terms of reference, then it is worthwhile to draw it up independently and coordinate it with the Customer before starting work. Examples of drawing up technical specifications here: https://fast-project.ru/specifications /
6. Programming the controller. To create a controller control program, special software is used, provided free of charge by OWEN (Codesys 2.3 or Codesys 3.5). The application program can be written in the logic programming language according to the IEC 61131-3 standard. In addition, graphical languages for building contact circuits and functional blocks are available, and the text programming language ST is well developed.
7. Testing and debugging. After loading the program into the controller, it is worthwhile to conduct tests to verify the correct operation of the program and the controller's response to various situations. If errors or problems are detected, debug the program and make the necessary changes. Carrying out factory tests of the cabinet before sending the assembled product allows you to significantly save time on Comission and identify significant shortcomings at an early stage.
8. Warranty obligations. 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 for the program loaded into the controller. This will help to quickly restore the system's performance if it breaks down and there is no connection with those people who previously handed over the system.



#Programmingoven, #modernizationitp, #engineeringitp
Be the first to comment