Simulator for OTS projects
- Lango: Language and translation manager
- sara.cardoso
This documentation refers to the OTSBase module, developed in the form of a communication driver, whose objective is to serve in projects used in ActionOTS - Operator Training System mode, to simulate the operation of switches, taps, circuit breakers, etc., replacing these same signals coming from the field in real projects.
Â
Introduction
It is a simulator module. It is configured with the Channel, Node and Points objects as in any other driver of Action.NET. It should be used in projects with OpenDSS, integrated with the Action.NET. In these projects, the channels and nodes of the real project must not be running, i.e. they must remain in the initial RESERVED state.
Channel Configuration
The channel setup is very simple. only the default name for the conversion of tag names is configured, and the type of log generated.
Conversion rule - It is the rule defined for this project, for the default conversion of command tags into cue tags. If it is not filled in (left blank) the rule will be used by default: . CMD. will be converted to . STA. If the rule should be other fill in the field in the form: <command tag text>:<flag tag text>.
Use invalid points - Unused.
Logging Level – You can choose from this list the mode of operation of the log created by the communication module.
Logging level | Messages included in the Log |
Debug | All messages are logged in the LOG. |
Info | Only the Info, Warning, and Error messages are logged in the LOG. |
Warning | Only the Warning and Error messages are logged in the LOG. |
Error | Only Error messages are logged in the LO |
Node Configuration
Only the name of the Node and the name of the channel to which it belongs are configured. A single node can be configured for the channel, which must also be unique in the project.
Points Configuration
To set up the points, use the Action.NET - Manager, go to the Devices / Points, to edit
To create points, fill in the full name of the Tag, choose the node and fill in the Address field, as needed.
Â
The tag defined here is that of the actual point that is used as a command. When there is a change in its state, through a command window, this simulator driver module will be called so that it executes the command, instead of the real driver in the production project. In real projects this tag is used to send a command to an IED.
The choice of point types and subtypes, number that follows the type of point, is done by clicking on the column Address and choosing the type from the available list.
In general, the spine Address It has the shape <tipo>:<valor>: <equipment signaling tag>
Where:
Point Type <tipo> is one of the types listed below, which can be chosen from the list available in the Address column
Value to Signal <valor> It is a number that can have different meanings in each type of command
Signalling tag<signalling tag>It is the full name of the tag that signals the status of the equipment. It can take any form, as long as it is a valid tag. The figure shows the definition of output and input in any case.
By default The module assumes that the command tag has a CMD, and in this place the signaling will have STA. Also that the comado tag is ended by _X and the signaling tag does not have this suffix. From the _ there can be any letter that will be disregarded. In these cases, it is not necessary to type the name of the flag tag.
Ex: Tag.SE_001.DJ52. CMD.POS_L will default to signaling Tag.SE_001.DJ52. STA. POS
Types of Points
Choose the type from the list shown in Point Type
CMD
Type used for the execution of commands, basically opening and closing switches and circuit breakers. After the acronym of the type, a number must be placed, which is the value that is desired to go to the signaling tag of the state of the equipment, when executing this command. In the examples above, it is assumed that the signaling tag has a value of 1 for open and a value of 2 for closed.
SP
Type used for performing the writing of a number entire in a tag. The name of this tag in which the value will be written follows the same rules defined above for command tag and flag tag. The value to be written is whatever is currently in the Output tag.
Ex: let the example in the figure above be: the Tag.SE\DJ510. CMD.SETI_S. Suppose your current value is Changed to 3456. This change will cause a write call to the module OTSBase. This module will then write the number 3456 to the Tag.SE\DJ510. STA. SETI
SPF
Type used for performing the writing of a number float in a tag. The name of this tag in which the value will be written follows the same rules defined above for command tag and flag tag. The value to be written is whatever is currently in the Output tag. The operation is identical to the SP type, only using the float type instead of integer.
TAP
Type used for the execution of commands, basically to increase or decrease the position of the Tap switch of transformers. After the acronym of the type, a number must be placed 1 - To decrease or the number 2- to increase. During the execution of the command, the simulator module reads the current value of the signaling tag, increases or decreases this value by one unit, as defined, and writes the new number in the signaling tag. The name of this tag, in which the value will be written, for default will be obtained by substituting a part of the command tag CMDby MED. Again if this rule is not compatible with the definitions in the project, nasta put the full name of the tag tag in the Signalling Tag.
In the example Tag.SE\TR02. CMD.TAP_D will decrease by one unit in the current value of Tag.SE\TR02. MED. TAP
RLY
Type used for the execution of commands to place a new value, which is described in the address column, in the tag defined here. Therefore, in this case, another tag for signaling is not considered, but only the tag itself that has been changed.
PRT
Type used to define actions of protection and change (opening) of the state of a tag, in this case, defined in Signalling Tag for the value defined in Value to Signal. The name of the main tag will usually be that of a protection point. Changing its state will cause the OTSBase module to call. This will search for all the settings made in Points for this tag and will change the state of each tag defined in the Signalling Tag with this same main tag.
In the example above, the change of P50 or P51 will cause the change to 1 (open) of the two circuit breakers with signals with POSA and POSB endings. In this type, default values are not used.
BLK
Type used for the configuration of interlocks or blocks for the execution of commands. In the TagName column, the name of the tag is placed, which, if at a certain value (defined in Value to Signal), should block and not allow the execution of a command by the tag defined in Signalling Value.
In the example above, when any command arrives for one of the POS_L or POS_D endpoints, the current state of the LOCAL endpoint will be checked. If it is in a state equal to 1. The comado will not be executed.
On this page:
Â