Discussing the possibilities of TeslaSCADA2 - 2.22 on the Big_ASU forum, a reasonable question arose about what it is and what it is eaten with. As an integrator who delivers a lot of different volumes, both himself and with partners, I am constantly in the process of searching for alternatives.
The search for alternatives to SCADA is mainly facilitated by external circumstances. The market is becoming tougher, customers are getting bigger, and their character is mostly poor and stingy. It would probably be more correct to compare TeslaSCADA2 with Iridium Mobile, since the products are mainly focused on smart homes, but decided to compare with the well-known Trace Mode. A plus of this article will also serve as step-by-step instructions on how to configure these products to communicate using the Modbus TCP + protocol, the files themselves will probably save someone time. Here's what came of it:
Versions of products that compare
Tesla version 2.22
TraceMode version 6.10.1
First, I download distribution from the office. the site http://teslascada.com/ru/downloads-ru/teslascada2 noting in passing the presence of video lessons and forum support. I will meet them later, as we progress, and who reads the instructions until they reach a dead end?)
There is no regular anti-virus on the computer under test, there is only a firewall, so I check the downloaded distribution for viruses on an online resource by many years of habit. The result is inspiring, according to 67 databases, no viruses were detected, so feel free to start the installation - the TeslaSCADA_IDE.exe file in the archive folder.
While installing, skimming TeslaSCADA_IDE_UserManual from the same folder. Yeah, all the documents in English .. Not that a complete plugging, but by the time of entry will have to add a multiplying factor. In general, of course it is strange, the product is Russian, but it is oriented to the west. Okay, maybe the help in Russian will be like in TraceMode (by the way, there it is very detailed and well-structured).
So, everything is installed, I set myself the task of polling a hypothetical slave device via Modbus, reading and writing a couple of registers. While deliberately not reading the documentation to find out how intuitive the user interface. Yeah, I immediately found the Russian language (although under the help button only information about the product is hidden ..), I press - File - Create project, I leave all settings by default.
Where to begin..? Probably from the creation of the operator's screen, because the perception of the whole project depends on the graphic “lotions”. What is there? Flat and three-dimensional geometric shapes, text fields for input and output, buttons and switches, lamps and indicators, valves, conveyors, devices, etc. Well, the graphics are good. Such functionality in Trace Mode is available only in the paid version of the product.
Moving through the menu, with the right mouse button I placed a couple of objects on the screen and immediately created two Tags for them - input and output numbers in INT16 format. Due to the lack of real physical devices, I use a software slave simulator, PeakHmiMBTCPSlave, working via a local bus to check. For real Modbus TCP devices, you need to add a server to the project from the menu on the left.
Strange, but where is the Modbus RTU simply buried, via the RS485 interface? Okay, I'll look later in the description, as long as I continue with what is. So, tags, screen elements and server are added, theoretically it remains only to make the correct bindings and can be launched for execution. Intuitively double-click the left button on the text element and find the binding in the properties of the tag. The text field will display the “measured value”, so I tied it to the read register. The button, respectively, is tied to the register case.
I save and run the created project for execution, after running the slave simulator. The first pancake turned out to be a lump - the slave is silent and does not show any attempts to communicate with it. Well, half of the project still works, pressing a button on the screen causes a change in the output TAG value, and entering the value in the receiving TEG is displayed in the text field.
So the problem is somewhere with a connection. To check, I run Ovenovsky OPC server, no - the slave is working, and it is returning data on request.
I will dig further, there is a vague doubt that I have never entered the addresses of registers because I did not find where this is done .. Yeah, here they are, when you turn on the server in the Modbus project, the register address input field appears. But .. communication with the slave, still no. I take the help of the hall - it's time to get acquainted with the training video on the site. So, the video, as well as the instruction is also in English, seems to be the main market for the distribution of the product, the authors see English-speaking countries, and decided to save money on the dubbing of the video, although there are Latin captions, more reminiscent of advertising slogans than explanations ..
The first video in three minutes repeated the fruits of my two-hour work (I probably still had to start with the instructions) and revealed the reason for the lack of communication - the execution environment-TeslaSCADA_Runtime.exe, which also needs to be installed and launched, was not launched. After that, in the menu - File of the main development environment we find the item - Download to the device and if the network settings are correct, a detected device appears in the opened window to which the project should be loaded.
After the aforementioned actions, the slave began to move and began to regularly show incoming requests, but for some reason a warning about the disconnection from the server runtime popped up.
Joy was short-lived - changes of TAGs did not happen .. After several minutes of searching using the scientific method, the jamb was found, the type of TAGs was incorrectly marked - uint16, instead of int16, in any case, after correction, the exchange went both ways - registers 40001 and 40002 screen. 40001 is tied to a text box, 40002 is tied to a toggle button. The real addresses are lower by 1, the slave emulator gives this offset.
In principle, the project creation algorithm is more or less simple; there are several videos on the source site on this topic. - http://teslascada.com/ru/videotutorialsru
Because For me, the question remains, where is Modbus RTU hidden and whether it exists at all, I finally decided to rummage on the manufacturer’s website. The required protocol really did not appear in the list of supported ones, which causes some confusion.
Despite this fact, TeslaScada2 is a sufficiently advanced Scud system, which has a low entry threshold (for an experienced user) and has sufficient tools to create modern and convenient monitoring and dispatching systems.
In contrast to the Tesla Scada, we set a similar task to the product TRACE MODE - polling a Modbus TCP slave through the operator’s workplace. The distribution kit is available on the developers website, albeit after registration - http://www.adastra.ru/products/dev/scada/. In the free version, one hour of operation of the real-time monitor is available, but without limitation on the number of tags, as in Tesla Scada. The installed product is also divided into the development environment and the execution environment. So, the development environment is established, let's start creating the project. In the layer Sources - receivers create a group - Modbus
Then in the created group we create two components Rin_Word (4) and W_Word (6) - these will be registers for reading and writing to the slave, respectively, 4 and 6 functions. Each resulting physical layer channel is editable. The port number is left zero, for TCP connection this parameter is not used, all you need is to enter the slave ID in the address field and the offset for the channel. For the output channel, all difference will be in the direction of the transfer - type Output
Next, you need to create an RTM node - it's an MRI, in general, you can not bother with the definition, the main thing is to create, without it the project will not work.
In the appeared node, it is necessary to create the Screen component, there may be several
Then you can appreciate the full power of Trace Mode by simply dragging the channels with the mouse to the desired layer, while automatically creating the necessary bindings. It is very convenient when, for example, you need to tie one hundred identical discrete channels to one hundred light bulbs on the screen. Most of the work will be done automatically. In fairness it should be noted that to check whether everything is properly attached, still it is worth it, to rely 100%, that the system itself cannot be properly arranged. So, in turn, we grab the Rin and ROut components from the source-source layer and drag them into the layer channels (System-RTM_1 - channels). Two channels of class HEX16 will automatically be created, already linked to the selected components. Next, the channels created are similarly dragging screen arguments to a layer; this layer works directly with graphic elements on the screen. In the process of these overtightening, the names of both channels and other components are repeatedly changed. If specific names are critical, all renaming is best done after the bindings are completed.
As noted earlier, something needs to be fixed. Namely - change the direction of W_Word to OUT. What caused these glitches with reference, it is better not to bother, but if you get used to them and correct them in time, then this mechanism saves a lot of time. Another necessary fix is shown below.
Now the simplest thing is to place the visualization elements on the screen and bind to them (the last binding, honestly!) Screen arguments. Elements will be the same as in the Tesla Scada button and text box. The selected screen arguments with a mouse each stretch onto its own visualization element. In the properties of the button, you only need to select the condition for switching.
The red man at the top of the screen includes emulation, which makes it possible to check how one or another element of the screen works without being connected to a real device.
The final test will be the launch of the RTM and the check of the real exchange with the slave
The result is the same as with Tesla Scada, but much faster, the description of the process took undoubtedly more time than the action itself - because the mouse moves more in the right direction.
Summary summary: Each of the systems marked in the SCADA report has its advantages and disadvantages, therefore, any of them should be applied on the basis of the technical project of a specific project or feasibility study.
|Properties and options||TeslaScada||Scada Trace Mode|
|Ease of project development||Intuitive. Resembles the OPC server configuration||Requires special skills, but more effective|
|Project creation speed||For large projects, time consuming||High due to drag and drop|
|Number of ready drivers||A small amount of||Several dozen. Built into the system|
|Video availability||For initial reference||A large number - in the public domain.|
|Graphics||Reasonably advanced||In the free version there are few elements.|
|Distributions||Free access on the site||
Available after registration
|Application recommendations||Small projects - automation of private houses, test benches, dispatching of soap objects by quantity.||Large scheduling projects, management of complex installations, production lines|
The links are:
Project Tesla Scada
Project Scada Trace Mode
All the same, in the future, with free time, I will try to make a comparison with the Iridium Mobile product. Understand the price/quality ratio of products, download to iPad or Android smartphone. To be continued...
If there is something missing or inaccuracy, there is a comment below, add
#SCADA, #teslascada, #TeslaSkada, #TraceMode, #Traysmod, #compare, #products