Programming in MasterSCADA

There are a sufficient number of various brands of SCADA visualization systems of domestic and foreign development on the automation market, and their number is growing every year. At the request of my clients, I have previously done comparative feasibility studies on the choice of imported brands. In this article, I would like to review the well-known product MasterSCADA v.3.12

This visualization package is supplied by EnSAT, which has been working in the field of automation for about 30 years.

I am familiar with this software product firsthand, since a number of objects were handed over to MasterSCADA, both with key and free versions of the product. Working with this SCADA system made it possible to identify both its advantages and disadvantages. I will try to present them as a direct integrator of automation tools.

Masterscada is a fairly flexible product that has the ability to be customized (improving the solution for the client) in C#. For example, there is experience in writing a driver on the CAN protocol and structured reporting forms. There are several types of Masterscada 3 licenses, usually we purchase NET PRO, since its functionality covers most of the possible requests from our Customers.

Advantages:
1. Cheap. The value for money is beyond praise. So a license for 500 tags with some "goodies" like web clients can be purchased for about 40 thousand rubles.
2. MasterSCADA has most of the functions that are initially required from any SCADA system when scheduling automation objects (buildings, technological installations, etc.). These features include: a customizable archiving system, various levels of user administration, displaying various messages about violations and events, the ability to create reports using standard tools.
3. A fairly wide range of tools for creating graphic forms and inscriptions. In this aspect, MasterSCADA is not inferior to such products as WinCC, Citect, InTouch.
4. The implementation of scripts in Masterskade is available in two possible programming languages C# and ST (PASCAL), in the tool palette there is an object for implementing special functions.
5. The free version, which has a limit of 32 tags, allows you to automate small objects for round-the-clock operation. For example, it makes it possible to debug PID controllers and does not require the purchase of a license key. It often happens that the Customer does not intend to buy SCADA, although the visualization system is necessary for the delivery of the scope of work. The free version is great for this kind of task.
6. It is possible to use a web client, the development environment has a convenient object architecture. Although, at first, after working with WinCC, Citect, InTouch, this was perceived ambiguously and caused rejection.
7. Stable operation of Runtime (project execution system) on various operating systems (XP, W7, W10).
8. In Runtime mode, there is a debug function that allows you to set any value to any tag in real time, including those that differ from the one given by the PLC.
9. The object of the historical and real trend is qualitatively developed, I have not seen analogues. Although in other systems this function is also quite well implemented.
10. Convenient input and editing of tags from the OPC server. If you think over the hierarchy of objects in advance, then it is easy to add new tags to the system.
11. Efficient and not difficult to implement client-server architecture. It is possible to configure the work so that the client station is based on a working server that collects information from the controller. Clients can also have their own OPC server, which can collect data and send it to the server as well, that is, the system architecture is flexible and can be modified at any time to suit the needs of a particular client. This is convenient if different roles must be organized on different clients of the system. For example, the set of video frames on all client stations is the same, but the access levels are different. In this case, the update of the dynamic component of video frames on client machines occurs when changes are made on the server.
12. Technical support works seven days a week (and on weekends), giving any comprehensive competent answers by e-mail. Answer correctly and without emotion. A separate branch operates on the OWEN company forum. For previously asked questions on the forum - the search works.
13. There are many video tutorials on the Internet on how to create projects. Most of them were created on outdated versions, but still detailed and understandable enough to reproduce the posted example.

Disadvantages:
1. A fairly noticeable delay was detected when issuing commands and writing to the tag. The result for the Customer is acceptable, but I would like to see a faster response from the system.
2. No screen zooming (zooming objects while editing). If you're going to draw a lot of small graphics when you're developing screen forms, you risk breaking your eyes. Therefore, the quality of work with small elements suffers greatly.
3. There is no quick fix to rotate an object around its axis while editing. This can only be done by assigning parameters or creating duplicates, which creates inconvenience when adding the same objects that must be deployed in different directions. 
4. Insufficient level of intuitiveness when working with the system, although the developer claims the opposite. Yes, the progress from version 3.6 is obvious, however, there was a feeling that it would be better if the help was written not by those who produced the software product. Disputes would arise and, as a result, the quality of perception would improve.
5. There is no direct possibility of exporting small developments from project to project, for example, graphic objects. Only windows can be exported. This is severely lacking. So, for example, being in another project, you understand that you need to inherit something from your other project. I am forced to open two computers side by side and transfer them with "eyes", which actually angers.
6. Unstable operation of the development environment. There was a case when it worked for a long time without using the save data buttons. At some point, the system issued information about the error and closed. I could not restore my achievements and had to repeat everything again. That is, you need to constantly save the project during development and occasionally restart. There is no guarantee that the program can be restored after a restart, even if the appropriate dialog is displayed suggesting this.
7. The help system is poorly structured and does not describe all the possible properties of objects, it lags far behind the developing system. Apparently, the developer simply does not have enough time to describe everything qualitatively. So sometimes you have to guess.
8. Technical support does not work by phone. Training programs at InSAT are available, but they are quite expensive, they are not in-depth, and for integrators like me they make little sense. It would be great if, as part of supporting novice users, EnSAT would conduct master classes through online webinars on some functions, as, for example, Iridium mobile promotes its product.
9. Hover comments on objects do not work correctly. Apparently, the task of displaying comments has been completed for a "tick". Shows the location of the object in the program (Project. Computer. Plant. Centrifugal pump). For the automation task, this is not at all necessary. Hover comments are necessary and important, but this feature must be built-in, that is, it must be entered by the engineer in a special field. You can't do this in the current version.
10. Tried using object inheritance functions. They are divided in the program into two parts. Replicating changes across instances and replicating changes on frames. So, if you have a project at the delivery stage - do not use that second one (by personnel). This tool works, but does not provide sufficient sets to choose from, and I do not advise you to fully trust it.
11. The built-in reporting tool did not suit me. Attempts to implement reports by third-party applications (Excel VBA, C#) require a connection to the DBMS. The license sold by default does not have the option to communicate with an external DBMS, and the local Masterscada database is closed for access from outside. Tip: when starting to negotiate with the Customer, start a dialogue on the need and nature of the reports. If you need large multifunctional reports, then the cost of the Masterscada license will increase by 25 thousand rubles. and will cease to seem competitive to you.
12. The network write function of the setpoint with feedback (Setpoint) has failed. I had to get out making two fields. One for reading, one for writing.

Summary:
The basis for creating any visualization system on any brand is the development of a correct and inherited template. The template is developed both for the entire application and for each of its elements. For example, an element for indicating the status of pumps, indicating values (temperatures, pressures, etc.), faceplates, pop-up windows that are called when you click on hidden buttons. We have such developments that allow us to save some time in the implementation of the incoming order.
How many tags can be picked up at Masterskade, is there any ceiling? There is an opinion from my friend, an ardent fan of Masterskada, that if you correctly ensure the typing of objects throughout the project, then the project will “fly” even by 10k. It depends on the project development methods. However, the author of this article has an opinion that the volume of tags for this product should not exceed 3k yet. This opinion is due to the lack of a built-in full-fledged archiving system (SQL or ORACLE), the presence of minor bugs and shortcomings. Some "patching" of the implementation is obvious. That is, for more serious objects (above 3K), I would recommend other, mainly imported brands, since they have a worldwide run-in.
How much do we value one tag when considering technical and commercial proposals?
Depends on the problem statement. This immediately becomes clear when you first communicate with the customer. If there is a feeling of a “big but narrow-minded white gentleman”, it is worth laying the risks. Usually we set the price according to the composition of the tags included in the license key. You can always reduce the cost of development, with the final calculation of the used tags, but usually it is not possible to increase the cost, even if there are reasons for this. The cost of tags usually includes project work, such as the creation of an album of video frames, a PLC-Workstation interface. The description of the operator's manual is considered as an option to the Agreement. Practice has shown that most of this work is not directly programming, but communication with the customer. It should be understood that we work with people, and taking into account their specific wishes is the basis of constructive work and mutual understanding.
There is a simple scale to assess the correspondence of the cost to the volume of tags:
Up to 100 tags – 350 rub/tag
From 100 to 1000 tags - 300 rub/tag
From 1000 tags and more - 250 rub / tag

Mnemonic MASTERSKAD:

From my partner Artem:

Thanks for the article - a good and detailed review on SCADA. I also want to share my view of what Masterscada is (Masterscada system). The first time I used this product, I formed some opinion about it. In addition to the Author of the article, I also see such advantages: 

1) Availability of demo versions for development and debugging of the system! A very important thing for a programmer, I think. The demo version is not limited by tags, it has a 1 hour run time limit. Quite enough for development. I have not seen a similar analogue in other systems - either there were demo versions for 30 days and this is the maximum. Usually without a demo at all - that is, theoretically, if you want to work with our scuda - immediately buy it without trying it. There is a very good customer focus here; 

2) Implemented fast copying of objects (duplication and replication) with copying links (bindings)! That is, if we have 4 identical containers with the same set of actuators and sensors, we start one, and then create three more copies by duplication, while connections with the OPC server are copied and replaced in a separate window! Significantly speeds up the process. All this is described in detail in the video tutorials; 

3) Competent and supersonic technical support. Emails are answered very quickly. Work on weekends and holidays! Very pleasing. 

4) Любой желающий может скачать Masterscada бесплатно на официальном сайте и попробовать. Там же выложены демопроекты. На ютуб роликах можно увидеть примеры создания отчетов

As for the cons:

1) The first thing I didn't like was, of course, the lack of zoom! How inconvenient it is. All the nuances have already been said by the Author of the article;

2) A very meager set of standard VFBs (visual functional blocks) - a couple of valves, one pump and little things. For example, there is a VSE PID controller. Normal, colorful, called by the button. But only he himself regulates. If the regulation takes place in the PLC itself, then it is necessary to create your own mimic diagram to display the parameters. Linking to an existing PID controller in this case will not work. Little things, but still. This is all because of the hard-coded properties of variables: Input / Output (Read / Write). This is the opinion formed about MasterSCADA software. I will continue to use this scooter with pleasure.

Opinion of my friend VanRon:

In general, the article touches almost everything. I do not agree on the shortcomings in paragraphs 5.9. To transfer images from project to project, for example, it is enough to add them to the library, the same with any objects, the only thing there is already its drawbacks with the same images during transfer, but in general not significant. Regarding point 9, comments are available in many FBs when you hover over a free plan, well, nothing prevents you from creating your own FBs, but this is certainly not an option. Of the pluses, one can also note the work with templates (instances), if you learn it correctly, you can greatly reduce the development time. Another of the pluses has recently appeared the function of saving the project for a quick start from a shortcut, I advise you to try if the project has a large number of tags, for example. And your friend very correctly noted by the maximum number of tags, after 5-7k the tin begins. MasterScada spoils it a lot. What we managed to notice is that images heavily load the project, non-native FBs, a large number of scripts, a large number of elements on the meme also kill the project and make the project slow down as a whole. Otherwise, all the minuses listed in the heart ... But still, Insat works, in version 4 and zoom there is also a flip, but it’s too early to cut real projects there, this is my opinion, maybe they don’t spend much on testing and debugging, it’s hard to say why it turns out damp, but they always work on comments and correct them, the best domestic Scad so far no.

Related Article about VideoCards

Services provided by our Company

#MasterSCADA, #PLCARM, #InSAT, #OPCserver, #ProgrammingSCADA, #objectarchitecture