Devices
Last updated
Last updated
In inSCADA you can define the devices to be connected. inSCADA models any communication device (PLC, RTU, Flowcomputer etc.) you want to communicate with its communication protocol and its parameters. Regardless of the protocols, the most important common point of these models is the data blocks. In inSCADA, you must define blocks for data exchange over the device. These data blocks are called Frame in inSCADA. See Architecture for a more detailed description.
Using options located in the upper right corner;
you can add, create, edit, and delete a device in the device library.
With the Import Template, you can import a device registered in the Device Library in inSCADA to any related connection. This allows you to instantly use your pre-defined devices, which you have previously defined or that came with inSCADA. When you import device template, your device, frame, and all tags will be added to your project for the relevant connection.
When you click the Import Template button, a dialog window titled "Device Picker" will appear on your screen. In this dialog, the parameters requested from you are;
You can select the connection to which you want to add a device. Here you will see the connections of the selected project in the device grid list.
You can select the device you want to add. Your defined devices will be listed in Wizards->Device library.
During the Import process, you can enter the prefix information that the defined device information will receive when saving under the respective project. For example, a variable in the device defined in your Device Library is defined as "Temperature". When you define "Station_01_" as prefix, your new variable name under the project will be "Station_01_Temperature".
It has a similar function as Prefix. The only difference is that it is used as a suffix. For example, when you define "_TT100" as a Suffix, the new name of your variable will be "Temperature_TT100".
Check your naming under your project during your definitions. If you use an existing naming, your operation will be canceled.
You can select any of the defined connections that you can access to your device.
You can give your device any name (15 characters).
You can enter a detailed description of your device (50 characters).
You can select the protocol to communicate with your device. inSCADA ;
Modbus TCP,
Modbus UDP,
Modbus RTU Over TCP,
Modbus TCP Slave,
Modbus UDP Slave,
Modbus RTU Over TCP Slave,
DNP3,
DNP3 Slave,
IEC 104 (soon)
MQTT (soon)
ProfiNET (soon)
comes with protocols as standard. The form is dynamically refreshed according to the protocol you select and allows you to enter device parameters in accordance with the protocol you select. Please refer to the Communication Protocols section of this document for details of device parameters that differ according to protocols.
All protocols associated with your device also have an address number that must be defined. You can enter this address number as defined on your device in accordance with the protocol.
inSCADA uses word blocks called frames to read data from devices. After querying each of the defined frames on the device, it waits for the Scan Time (ms) parameter and gives the CPU time for processing. By making adjustments to this parameter, you can reach the optimum communication speed allowed by your network and equipment.
By using options on the right side of the toolbar named Frame,
you can add, edit, and delete frames.
You can select the device to add to the Frame.
You can enter any name (15 characters) for the frame.
You can enter a detailed description (50 characters) for the frame.
You can select the type for the frame depending on your communication protocol. For a detailed description of the frame types, see Communication Protocols.
Frame start address defines the start address to be read/written from/to the device.
Quantity determines the amount of words to read from the start address. This amount must be within the limits allowed by the protocols or device.
inSCADA scans the frames within a device by waiting for Device Scan Time. If Scan Time Factor is entered in a frame, it waits for the frame during Device Scan Time x Frame Scan Time Factor. In this way, you can adjust the frequency of reading of your frames and optimize your communication speed in accordance with your resources. For example 1,2,3 etc.
It is mostly used for protocols that do not use timestamps. If you set 0, all values read with the corresponding frame are labeled with the current time of the computer. If you set -60, you will tag the same data an hour ago. When stored in the database, the data is recorded with these timestamps.
Minutes Offset is generally used effectively on devices that transmit data from previous hours and previous days in communication tables. For example, if a Gas Flowcomputer returns the previous hour values as a modbus table, it is best to read them by typing -60 in the minutes offset field. In this way, when you pull the data from the database for report and analysis, you have the opportunity to examine the data with the relevant time.
With this parameter, you can ensure that your frames do not enter the reading queue. You cannot read a frame to the device if it is not readable.
With this parameter, you can ensure that your frames do not enter the write queue. You cannot write a frame to the device if it is not set to Writeable.
