The industrial controller Pixel is a Segnetics product from the 12xx - 25xx series, which is widely used in practice. Traditionally, these controls are used for ventilation and air conditioning systems. The Pixel controller itself is a purely electronic device. Therefore, the device functions only when the control program of the Pixel controller is loaded - the core and the system project of ventilation or other equipment.

Often, devices are sold pre-programmed for specific equipment. But in practice one has to deal with different configurations of technical systems.

Control device for industrial ventilation and air conditioning systems, as well as other equipment, fully automatic

Therefore, the practice of Pixel programming is always relevant. Proceeding from, the programming of "Pixels" should be conditionally divided into two stages:

1. System stage (project creation and download).
2. Working step (programming of parameters and start-up).

Pixel System Programming

The system stage of programming involves the creation of a working project for the Pixel with the subsequent loading of the generated code into the permanent memory module of the controller.

It should be clarified: the loaded project is an intermediate program code, which is processed by the main program - the Pixel core - during the controller operation.

The creation of a system program for the "Pixel" is carried out through a special service software called SMLogix. The software supports FBD (Function Block Diagram) programming under the graphical interface.

Interface ("clean") of a software package designed for the development of system software for the control of various industrial and economic equipment

The SMLogix programming system for Pixel controllers is designed for Windows and can be installed on personal computers without restrictions.

It should be noted that the SMLogix complex is a rather complex service software. The software supports the development of software projects at the level of the methodology for constructing FBD schemes with the participation of macros. The programming process takes place in the following sequence:

1. The specific goals of the project are determined.
2. A paper scheme of the project is drawn up.
3. An FBD scheme is made on the basis of a paper sketch.
4. The project is being compiled.
5. Testing and debugging.

Despite the complexity of the service software, you can learn to program SMLogix from scratch if you wish. But to make it easier to learn all the intricacies of FBD programming, it is recommended to practice on ready-made projects for the Pixel controller.

Such projects are available on the manufacturer's official resource. A software service complex is also available for download there. It is advisable to have a “free” (test) Pixel controller at hand.

Examples of developing blocks of an FBD project

Suppose there is a task to implement the function of a discrete regulator to control the heating element. With the help of the Pixel software, this function is realized by creating a block diagram on the working area of ​​the SMLogix program.

This is how a piece of a system program that implements the function of a discrete temperature controller looks like. Heaters can be installed, for example, on air conditioning equipment

After compilation and loading into the controller, the generated code acts as follows:

1. The setpoint is being processed.
2. The points of the boundary temperature are calculated.
3. The heating element turns on or off.

A characteristic feature here is the smooth dynamics of the regulator circuit. In practice, such work is marked by a clear actuation of the relay. Bounce of contacts is completely eliminated.

This is how a full-fledged control program for the controller and air conditioning, as well as other systems, is created.

A control or monitoring function is programmed for each module. Everything is combined into a single functional diagram and loaded into the controller's memory.

Loading the finished compiled program is carried out using one of two interface options. The first one allows you to download and run, the second one supports debugging

Loading the project directly into the Pixel controller memory is done through the buttons on the SMLogix workbar. There are two buttons for this purpose. One button activates the function for downloading and then starting.

The second button activates the function to boot into debug mode. Before downloading the controller, it is necessary to connect and make sure that there is communication through the "Diagnostics and Search" option.

By the way, it will be noticed: through the "Diagnostics and Search" option, the processor core code is updated if necessary.

This is how the "SMLogix" program window looks like, through which programming is performed - updating the core of the Pixel controller

This is a completely separate operation, not directly related to loading the project. In addition, core files differ in extension from project files.

Pixel programming work step

"Pixel" at the working stage includes actions to configure the loaded software project for the existing ventilation and air conditioning system, or other equipment.

The process consists in setting the required operating parameters, for example:

• indoor air temperature,
• air pressure at the outlet of the supply system,
• restrictions on heating the return heat carrier,
• season of the year,
• time for the timer.

The general list of settings, depending on the configuration of the equipment, can be more than a dozen items. In addition, there are system settings that set the current date, time, data exchange rate parameters, etc.

Setting parameters is an integral part of working with this kind of electronics. Correctly selected settings are the key to the smooth operation of the equipment

The working stage of programming supports the function of copying and downloading the project. That is, it is possible, literally, with one click of a button, to copy the operating program to a removable memory module.

Pixel Programmable Logic Controller is an easily configurable device for any client's needs. Existing modifications allow you to select the required combination of analog and digital inputs / outputs. If necessary, their number can be easily increased by the Segnetics MR expansion modules. The built-in display provides text and graphic information.

The basic functionality of the Pixel controller is expanded with additional modules. Communication modules add support for Ethernet PNS or LonWorks networking to the built-in RS-485 interface. The memory module expands the available amount of the PLC's own memory for storing archives, schedules and more complex projects with a large number of variables.

Peculiarities:

• High degree of modularity. There is no need to pay for unused channels or interfaces. Connecting additional modules adds the following features:

communication in the Lonworks network or Ethernet;

increase in I / O channels up to 64;

increase in non-volatile memory up to 256 Kb for storing settings, events, graphs or trends;

use of non-volatile memory such as Fram, which allows making an unlimited number of records.

When adding new modules, there is no need to dismantle the controller or disassemble it. Full software compatibility with the SMH 2010 controller. No need to re-create programs. Anything that worked on SMH 2010 will function similarly on a Pixel controller.

• Full compatibility of Pixel controllers with the MasterSCADA SCADA system.
• Ability to save and transfer control programs using memory modules. No computer required on site.
• The graphic display of the controller allows you to display graphics and text of various sizes.

Specifications:

Discrete inputs

• 6 opto-isolated inputs.
• Actuation voltage levels: Closed dry contact - from 12 to 36VDC. Open "dry" contact - from 0 to 1VDC.

Discrete outputs

• 2 relay outputs and 1 triac or transistor output, depending on the version.

D out - electromagnetic relay

• Switching voltage: up to 277VAC / 30VDC.
• Switched current: up to 10A.
• Switching time: up to 10ms.
• Resource: yes 100,000 switchings.

D out - triac (with optocoupler)

• Switching voltage: up to 277VAC / 50Hz.
• Switching current: 10mA to 0.5A.

D out - Transistor (without optocoupler)

• Switching voltage: up to 36V DC
• Switching current: up to 0.5A

Analog inputs

• 5 inputs for connecting thermoresistors, 1 input for measuring current / voltage.
• Connectable thermal resistances: up to 5 Pt1000 sensors; up to two NTC thermistors with resistance up to 20 kOm (the number of connected sensors depends on the version).
• Measured voltage / current: 0… 10V DC / 0… 20mA DC.
• Resolution: 10mV / 20 µA (10 digits).

Analog outputs

• 2 (without galvanic isolation).
• Range: 0 - 10V DC.
• Load capacity: 12mA per channel.
• Overload protection.

Nutrition

• Resolution: 18-36VDC, 18-29VAC.
• Power consumption: no more than 3.5W.

Interfaces

• Serial port: built-in RS485 (Modbus RTU protocol).
• Network card (optional): Ethernet 10Mbit or LONWorks.

• Keyboard: 5 buttons.
• Display: one-color, resolution 122x32.
• Light indication: 2 LEDs.

Pixel controller it is arranged according to the principle of a personal computer - you can change its components depending on the emerging needs. There is no need to pay for unused channels or interfaces. Increase in base resources controller provided by simply connecting additional modules.

Network cards

Removable NICs - Provides communication over a Lonworks or Ethernet network. When switching from protocol to protocol, no additional programming of the Pixel logic controller is required. The cards are ordered separately, which is undoubtedly convenient when ordering controllers.

Expansion modules

The benefits of using expansion modules are undeniable.
allow you to increase the number of I / O channels up to 64. When adding new modules, there is no need to dismantle the Pixel controller or disassemble it, while the maximum automation of the process is achieved: distribution of addresses, hot pickup, etc.

Memory module

The PMM module is intended for retrieving archives and for loading operating programs into Pixel controller... The speed of preparing controllers for work increases, since it became possible to save and transfer control programs with its help.

Graphic display

The Pixel controller graphic display allows you to display graphics and text in various sizes.

Software packages

Convenience of programming is provided using the unique SMConsctructor tool - a package for automatic creation of programs for controllers and Pixel... SMConsctructor allows you to quickly create control programs and adapt them for a specific object. The constructor has a simple, clear interface, and anyone familiar with ventilation systems can master it.

Buy PIXEL controller and you can get technical advice from the Automation Group of Companies.

"Approved by LLC" Segnetics "SGN.312005.05RE Programmable logic controller" PIXEL "Operation manual SGN.312005.05RE St. Petersburg User manual ..."

Approved

LLC "Segnetiks"

SGN.312005.05RE

Programmable logic controller

Manual

SGN.312005.05RE

Saint Petersburg

User guide

1. Safety instructions 3

2. Basics 4

Introduction 4 Specifications 5

3. Main parts of the controller and control elements 6 Controller 6 Additional equipment 12

4. Installation and connection 15 Order code and markings 15 Mounting 17 Connecting external devices 19

5. Intended use 24 Networking 24 Memory module 45 Digital inputs 47 Digital outputs 53 Analog outputs 58 Analog inputs for connecting temperature sensors 62 Analog inputs for measuring current and voltage 65 Built-in voltage source for setting the setpoints. 69 Service mode. 71 Loading the controller kernel 110

6. Appendix 1. System page (SS). 120 Pixel User Guide

1. Safety instructions Read these instructions before starting work.

Only qualified personnel can install the Pixel controller.

Note. Do not open the controller or make any wiring unless the controller is powered off.

Note. After turning off the power at the terminals for 10 sec. dangerous potential may remain.

Note. Even if power to the controller is disconnected, hazardous voltages from other external sources may be present at other terminals on the controller. For example, the switching voltage of the external network can be connected to the digital output terminals.

- & nbsp– & nbsp–

2. Basic information Introduction "Pixel" is a programmable logic controller designed for automation of engineering systems of buildings and technological processes in industry. The controller can operate both as a separate device and in a computer network as a slave or master device in a Modbus or Ethernet (Modbus TCP / IP) network.

- & nbsp– & nbsp–

Display The device uses a graphic display with a resolution of 122 x 32 dots. Information on the display is described in the built-in help of the SMLogix program.

- & nbsp– & nbsp–

Use in the SMLogix project

Select the required button in the "Devices" tree and place it on the meadow. When you press the button, a unit appears at the output of the corresponding block.

Select the "Keyboard" block in the "FBD" tree and place it on the clearing.

If such a block is in the project, then when you press the buttons "ESC", "Right", "Up", "Down", "OK" at its output "ASCII", the digital code corresponding to this button will be returned.

- & nbsp– & nbsp–

The upper "LED0" is for displaying system alarms and is also accessible to the user from SMLogix. Bottom LED "LED1"

used only from the SMLogix project.

When a system alarm occurs, "LED0" becomes inaccessible from the SMLogix project until the alarm is cleared.

Use in the SMLogix project:

Select the indicator icon in the "Devices" tree and place the block on the clearing. A unit at the input of the unit lights up the indicator.

- & nbsp– & nbsp–

SW2 - Selection: internal / external power supply for sensors with discrete output.

If the sensors with a discrete output do not require galvanic isolation (for example, sensors with a “dry contact” output), then to supply them with power, it is possible to use the + 24V power supply built into the controller (terminal 23 of the controller).

In this case, the controller's system ground must be used to create the ground potential for the sensors (COMM_DIN terminal).

The system ground on the controller board is connected to the COMM_DIN terminal by setting the SW2 jumper.

- & nbsp– & nbsp–

Optional Equipment You can expand the functionality of the controller by connecting additional components to it.

- & nbsp– & nbsp–

The cable connecting the controller to the hub or hub is crimped on both sides with RJ-45 connectors in accordance with the “Straight-through” connection scheme.

When connecting 2 controllers to each other or when connecting directly to a computer, the cable is crimped according to the “Crossover” scheme.

- & nbsp– & nbsp–

Wire type - stranded soft, solid solid.

The use of ferrules to form the terminated ends of a stranded wire is preferred over soldering.

- & nbsp– & nbsp–

Attention! To minimize the likelihood of controller malfunction and improve measurement accuracy, strictly follow the guidelines in this section.

Route analog signal, digital signal, and power cables separately from power cables.

- & nbsp– & nbsp–

To download the SMLogix project and communicate in the ModBus network, the Pixel controller uses the same COM1 (RS485) communication port. If the controller works as a “master” on the COM1 port, then when loading the project, “SMLogix” will disable the “master”, thus allowing the program to be loaded and debugged. The work of the "master" in the network will resume after the end of the debug mode or after the power is turned off. Also, the wizard's requests can be disabled through the Service Mode.

- & nbsp– & nbsp–

Connect the Master to the Slaves using a shielded twisted pair cable. Install 120 Ohm terminator resistors at the extreme points of the network. The 120 ohm resistors are already installed in the Pixel controller. To connect them to the circuit, you must set the appropriate jumpers.

- & nbsp– & nbsp–

After changing the network settings, you can contact "Pixel", including for uploading projects to it, only at this address and at a given speed. At the time of writing new parameters, the COM port of the computer to which the controller is connected is also automatically configured.

For the “Pixel” controller to work as a “Master”, the creation of a corresponding control program is required. For more details, see "Tutorial" or "Help" for working with SMLogix.

Attention! Arbitrarily changing the address and baud rate of the controller can lead to some confusion. By default, the Pixel controller is assigned an address of 0 and a baud rate of 115200 bps. Using these parameters, SMLogix, as a master, communicates with the slave controller. If it is necessary to set what address and what speed are currently set in the "Pixel", then for this purpose there is the "Diagnostics and search" dialog box (Options menu, Test, Diagnostics and search) and the Service Mode menu.

- & nbsp– & nbsp–

The network module "Ethernet" provides communication using the Modbus / TCP protocol. Modbus / TCP is a symbiosis of the standard Modbus protocol and the TCP / IP protocol as a means of communication.

The use of the Ethernet communication channel and the Modbus / TCP protocol provides the following advantages:

High speed of work;

Collaboration of various protocols on one physical network - Ethernet. Pixel controllers can work in the same network with personal computers and other devices;

Several Master Devices can operate on the same network.

The "Ethernet" network module of the "Pixel" controller allows:

- & nbsp– & nbsp–

Implementation peculiarities Before transmitting data, TCP / IP protocol establishes a connection between two controllers for the duration of data exchange.

When the communication is complete, the connection is dropped. The “Ethernet” network module of the “Pixel” controller supports connection with only one controller at a time. That is, more than one master cannot connect to the Slave controller at the same time. If it is required to poll the Slave controller by several masters, then this must be done sequentially, i.e.

synchronize in time the process of masters' access to one Slave. The slave controller monitors the data transfer from the master over the established connection. If there is no data for more than 1.5 seconds, the Slave-controller itself closes the connection so that other masters can poll.

Provision is made for creating a project with Lonwork and Ethernet variables in one project at the same time. The project works with the variables of the network card that is currently connected.

- & nbsp– & nbsp–

It is possible to connect a controller already operating at the facility to the Modbus / TCP network as a Slave. To do this, it is enough to connect the network module "Ethernet" and set the network parameters through the CP "Configuration" "Network module" menu.

- & nbsp– & nbsp–

It should be remembered that in the Modbus / TCP protocol the device has two addresses: an IP address and a standard Modbus address. When creating a network, in addition to assigning an IP address to the slave device, set the Modbus address and check the correspondence of the addresses in the requests from the network master.

The quality of network communication can be monitored by installing a DEVICE (Link) diagnostic block in the SMLogix field.

At the inputs of the DEVICE (Link) "CNum" and "PNum" block, you need to set the number of the connection protocol that you want to control.

"NetPort" - number 3.

- & nbsp– & nbsp–

It is possible to diagnose communication with a specific slave from the SMLogix application project (program). To do this, use the Slave (Link) block located in the "NetPort" tab inside the memory card of a specific device ("Devices" panel of the "SMLogix" project, "NetPort" tab, Slave memory card).

- & nbsp– & nbsp–

Possible errors and difficulties Attention! The IP addresses of the polled slaves in the master project can only be changed by reloading the master project!

Therefore, the assignment of IP addresses to Slave devices must be agreed in advance with the network administrator. Otherwise, you may need to rewrite the wizard project to replace the polled IP addresses. To rewrite the project, you can use the Memory Module (MP) (see MP Services).

Attention! Pixel controller with Ethernet network module

a static IP address (from the “SMLogix” project) and an individual physical MAC address (assigned by the manufacturer of the network module) are assigned. To transmit packets on a TCP / IP network, devices use a physical MAC address-to-IP address table (Protocol Defined). When replacing the “Ethernet” network module, the controller will receive a new MAC-address, and the IP-address will remain the same according to the project. To resume communication with the controller, it is necessary to correct the table of correspondence of MAC addresses to IP addresses of the TCP / IP network.

LON General description The LON network module allows the Pixel controller to be connected to the LonWorks network. Developed by Echelon Corporation, LonWorks technology is used for building automation systems, building distributed control networks in transport and industrial processes.

- & nbsp– & nbsp–

The hardware base of the LonWorks node is the Neuron Chip. It manages all network functions, and also solves specific application problems.

- & nbsp– & nbsp–

On the body of the LON network module there are two LEDs and a SERVICE button, pressing of which causes a message to be sent to the network containing a unique 48 - bit Neuron Chip identifier (Neuron ID). This information is used to configure and manage the node.

ACT - indication of reception / transmission of packets in the network SERVICE - indication of the Service.

An LED connected to the Service Pin displays the status of the network module:

- & nbsp– & nbsp–

Network event - "Wink" is displayed in the low byte of the nviTime.SW variable with a value of 1 for at least 2 seconds. In the service mode menu, you can see the Neuron ID and the State state of the controller. To do this, use the "Configuration" "Network Card" menu.

Variable SndHrtBt - prescribes the time interval for sending output variables regardless of their changes. Those. if the output variable changes, then these changes are sent immediately, and if it does not change, then its data is sent with the SndHrtBt time interval.

Variable NVUpdateRate - defines the time interval for sending changed variables.

If N variables are changed, the total time of their delivery to the network will be:

N * NVUpdateRate / number of NVO variables When NVUpdateRate is equal to zero, the variables are not updated.

- & nbsp– & nbsp–

Possible errors and difficulties In the Lon network, the controller updates its variables by changing their value or with a certain time interval set by the SndHrtBt variable (SNVT_time_sec type) With a large number of variable bindings and a small update interval NVUpdateRate for polling variables using the LonBrowser program, the network card may not have enough performance.

The point is that LonBrowser uses periodic direct network requests (Net Var Fetch) with the Request-Response service to monitor variables. This significantly increases the load on the network.

Therefore, when you enable monitoring of all variables, network traffic increases - sometimes even critically, with a large number of variables. In order to reduce the load on the network, it is necessary to exclude additional requests.

To do this, monitor the variable in the Browser by linking to this variable. In the properties of the variable on the Monitor Options tab, set the checkbox "Bind this variable to the browser for ...". In this case, during monitoring, the update will occur with the update variable (or with a time interval specified by the SndHrtBt variable).

Pixel User Guide

Memory module For storing project data such as setpoints, constants or miscellaneous variables, logging or graphing, each controller has a byte of internal non-volatile EEPROM and a slot for connecting an external memory module. External Memory Module (MP) is a non-volatile memory up to 256K. In addition to the ability to store project data, the Pixel controller provides the function of saving and loading the entire application project from the Memory Module (MP) without the help of SMLogix, as well as automatic system logging on the MP (see Journal).

Installing / removing a module

- & nbsp– & nbsp–

Writing default values

The EEPROM and ARRAY storage units are designed to work with non-volatile memory in SMLogix.

- & nbsp– & nbsp–

Note. To save a project to a memory module, you need a 25xx-xx-x controller with a write function.

- & nbsp– & nbsp–

- & nbsp– & nbsp–

SENSOR SENSOR SENSOR SENSOR SENSOR

- & nbsp– & nbsp–

Note: The given example of connecting sensors is not the only one. For example, it is possible to connect active sensors with reverse conduction transistors at the output (NPN type). In this case, the plus of the supply voltage of the sensors is connected to the COMM_DIN terminal, and the ground potential of the sensors is not used.

- & nbsp– & nbsp–

External connections (electrical and wiring diagrams) are absolutely identical for both versions. Only the technical specifications differ.

Options for external connections of discrete outputs to actuators (for example, implementation with a mechanical relay) are presented below:

- & nbsp– & nbsp–

ATTENTION! In the case of using Dout based on triacs and connecting them according to this option, the source of the Vexternal must be an AC voltage source.

- & nbsp– & nbsp–

ATTENTION! In the case of using DOUT based on triacs and connecting them according to this option, there must be an AC voltage source as the Vexternal source.

- & nbsp– & nbsp–

Analog outputs Analog outputs are designed to supply a specified control voltage to the actuator in the range of 0… 10V.

The required voltage value is set by software.

- & nbsp– & nbsp–

Connecting analog outputs to executive devices Connection of external executive devices to the analog outputs terminals of the "Pixel" controller is carried out in accordance with the figures.

Variant 1. The actuator has a half-wave rectifying circuit of the power supply voltage.

- & nbsp– & nbsp–

When connecting, it is necessary to combine the grounds of the power supplies of the “Pixel” controller and executive devices in the specified way. In the absence of coupling, due to the potential difference between the earths, the performance of the analog output is not guaranteed.

- & nbsp– & nbsp–

Variant 2. The actuator has a full-wave rectifying circuit of the power supply voltage, and the control inputs are galvanically isolated from the source grounds.

- & nbsp– & nbsp–

When connecting, the unification of the grounds of the power supplies of the “Pixel” controller and executive devices with each other is not allowed due to the possibility of failure of one of the devices.

- & nbsp– & nbsp–

Protection The analog outputs of the Pixel controller have a built-in overload protection circuit. The protection circuit operates as follows: when the load current exceeds 6mA, the amplifier's power supply disconnect signal is generated.

In this case, in the event of a signal from the protection circuit, the analog outputs go into the self-test mode. Once a second, the analog outputs turn on and the protection circuit is tested. If the overload is removed, the analog outputs return to normal operation.

In the controller “Pixel”, version 25xx-xx-x, the corresponding signal “Trouble” is simultaneously issued, and information about its presence is recorded in the log. (see System Crashes).

When using two analog outputs in the project, it is necessary to take into account that the “Alarm” signal will be generated if the TOTAL load of the outputs reaches 6mA. It does not matter in what proportion the load will be distributed between the outputs.

- & nbsp– & nbsp–

Attention!!! Because the sensors are connected using a two-wire circuit, it is necessary to minimize the error so that the resistance of the cables used is much less than the resistance value of the sensor

- & nbsp– & nbsp–

Connect an external sensor with a current or voltage output to the terminal of the corresponding measuring input as follows:

- & nbsp– & nbsp–

Built-in voltage source for setting the setpoints.

The Pixel controller has a special low-power voltage source. This source is used if it is necessary to set the setpoints in the application project - some control points of the measured parameter, upon reaching which this or that event should occur - for example: a fan or heating element is turned on.

In this case, the measured parameter is the voltage value. The voltage source is a linear regulator with a 3.9 kOm resistor connected in series with its output. Thus, an external connection to the output terminal of some resistive sensor forms a voltage divider.

The signal from this divider can be applied to terminal Ain5 (analog voltage input) and used in the setpoint building application.

Examples of using the source together with a variable resistor for manual setting of a set point and with a thermistor for regulation are shown in the figures:

- & nbsp– & nbsp–

Service mode (CP) in the Pixel controller is designed to provide the ability to control the operation of the controller, to simplify the diagnostics and adjustment procedures of the controller.

After entering the CP, the CP menu will be displayed on the “Pixel” screen, and all indication of the applied project is blocked. While working in the SR, all button actions do not affect the application project.

Return from the CP menu is carried out by pressing the "Esc" button or automatically after 2 minutes. since the last CP activity, if there is an FBD application project on the controller.

Attention! It is unacceptable to use the key combination "r" + "s" (simultaneous pressing) in the SMLogix project (program), since This combination is used to enter the service mode and is locked for the application project.

- & nbsp– & nbsp–

To organize the user interface when working in the SR in the controller "Pixel" there are 5 buttons of various functional purposes, - "Esc" "w" "r" "s" "OK", and LCD - display size 122x32 pixels, - 4 lines by 20 characters each.

- & nbsp– & nbsp–

To edit a parameter, place the cursor on the selected menu parameter and confirm the selection by pressing the "OK" key. After that, you enter the editing.

In general, editing looks like this:

- & nbsp– & nbsp–

The name of the parameter is displayed on the top line of the screen.

The next line of the screen contains the parameter editing line, the blinking cursor on the current, most senior, digit of the variable and the current value of the edited variable. The number of familiarity in the edit line corresponds to the maximum number of digits of the variable, taking into account the sign.

- & nbsp– & nbsp–

On the very bottom line of the edit menu, the default value is displayed, - the initial value of the variable assigned at the factory.

Entering or editing a number is carried out bitwise from left to right.

"W" - Jump in the edit line to the desired digit.

Each time you press w, the edit cursor moves 1 position to the right. In the case when the cursor occupies the extreme right position - the least significant bit of the variable, the transition by the next pressing "w" will occur to the extreme left position - to the most significant bit of the edited variable.

The choice of the character entered in the digit is carried out by the keys "r" up, or "s" - down, sequentially from the permissible set of characters.

- & nbsp– & nbsp–

The "_" separator after a significant number implies the end of the editing line, and characters following the "_" character are discarded.

For example, if you try to assign a value from the edit line "-34_5678" to a parameter, the value will be assigned "-34".

"OK" - Enter the edited parameter.

In this case, each parameter is checked during input for compliance with the range of accepted values. When an attempt is made to enter a number that is not in the valid range, the edited variable takes on the value prior to editing.

- & nbsp– & nbsp–

To work with the Memory Module (MP), if you need to save the applied project on the MP or load it into the controller from the MP, you can use the menu "Services MP". In this case, only the function of loading an application project from a previously saved MP to the “Pixel” controller is available for the execution of 12xxxx-x.

In the "Configuration" menu the following are available:

- & nbsp– & nbsp–

The “SMLogix Project” menu (available only for the 25xx-xx-x version), if an application project is loaded, allows you to stop and start the project, perform a complete restart, monitor the real tick of the system, and also allows you to manually set the state of the inputs and outputs "Pixel" regardless of the state of the project (emulation of inputs / outputs).

To display the system alarms that occur during operation, the System Alarms menu item is provided in the SR (available only for the 25xx-xx-x version). For a more detailed description of the system alarms that occur and how to deal with them, see the "System Alarms" section.

To restore the chronology of events and emerging alarms, the “Pixel” controller maintains a system log (available only for 25xx-xx-x versions). Viewing the log events is available from the CP "Log" menu.

- & nbsp– & nbsp–

In the case when the project requires a larger amount of data, it is possible to connect an external Memory Module (MP) to the controller.

This allows you to increase the storage capacity up to 250 KB.

- & nbsp– & nbsp–

In addition to the ability to store project data, in the controller "Pixel"

there is a function of saving and loading the entire application project from the Memory Module (MP) without the help of SMLogix, as well as automatic system logging on the MP (see Log).

- & nbsp– & nbsp–

When saving an application project on the MP for subsequent loading into another controller, the size of the ARRAY / EEPROM data must be taken into account first.

If the total amount of ARRAY / EEPROM data exceeds 256 bytes, then all data with a physical address of more than 255 (numbering starting from 0) during operation will be located on the external MP.

Those. for such a project to work, you will need to leave the MP connected to the controller, otherwise there is simply nowhere to place data with an address of more than 255.

Therefore, if it is necessary to transfer such a project to several controllers of the same type "Pixel", it is necessary for each controller to create a copy of the project on a separate MP, since the data of each controller requires placement on its own MP.

If the size of the ARRAY / EEPROM data is less than 256, then after loading the application project from the Memory Module into the “Pixel”, the MP itself can be extracted from the “Pixel” without prejudice to the further operation of the application project (since no external non-volatile memory is required for operation, the available internal).

- & nbsp– & nbsp–

The exact size of the non-volatile memory required to work with ARRAY / EEPROM data can be checked in the Service Mode (CP) "Configuration" "Memory module" menu.

- & nbsp– & nbsp–

One of the tasks that you have to solve when working with the "Pixel" is to download the working project (the "SMLogix" program) to the controller located at a remote site.

This task can be solved using the Memory Module (MP).

To do this, you need to copy the project from the controller with the working project ("Pixel" 1) to the existing MP, and then transfer the MP to the controller, into which you want to load this project ("Pixel" 2).

Note. The function of saving the applied project on the MP is implemented only in the "Pixel" controllers of the 25xx-xx-x version

- & nbsp– & nbsp–

If the total amount of ARRAY / EEPROM data in the project exceeds 256 bytes, then for the project to work it is necessary to leave the MP in the “Pixel” slot 2.

If after loading it is supposed to use MP with "Pixel" 1, then to transfer the project to "Pixel" 2, you need to save the data on the additional MP using the "Save with selection" menu item. (See "Advanced Features") Advanced Features

- & nbsp– & nbsp–

If you need to make a copy of the project that will be used on another controller, and the project requires more than 256 bytes of ARRAY / EEPROM data, then you need to save the project to an additional MP that will be connected to this controller.

Naturally, only if it is planned to keep the original project working. both controllers require an MP for normal operation.

In this case, after the message appears:

- & nbsp– & nbsp–

Note. The source MP for the controller is the module containing the ARRAY / EEPROM data used in the process of the controller operation, the project of which is to be copied.

After detecting the original MP, the controller will read the data to prepare it for copying:

- & nbsp– & nbsp–

This function allows you to download, individually or in any combination, any of the 3 components of the application project (“SMLogix” program) into the controller from the MP.

- & nbsp– & nbsp–

It is necessary to make sure that stopping the program will not lead to an emergency at the facility and only after that press the "OK" button to load a new project or update the configuration.

- & nbsp– & nbsp–

Before starting the project, it is checked that there is enough space on the MT for storing data, settings of the newly loaded project.

If there is not enough space, the following dialog will be displayed on the screen:

- & nbsp– & nbsp–

If you press the "OK" button, the project will be deleted from the MP and the vacated space will be used for storing data and settings. If you press the "ESC" button, then read / write access to the MP will be blocked and the project will be able to use only 256 bytes of non-volatile memory on the internal MP for storing settings and data.

During operation, "Pixel" saves information about the used MP, and if the user installs another MP, the following message may appear on the screen:

- & nbsp– & nbsp–

2. Creation of a bootable MT for loading a project without using a computer at the facility.

Such a need arises if it is inconvenient or undesirable to use a computer to download a project to controllers.

- & nbsp– & nbsp–

The resulting MP can be used to download an application project to the controller at the site without the help of a PC. If the project requires an external MP, the bootable MP with the already prepared data of the EEPROM / ARRAY blocks can be left on the working object as the main MP controller.

- & nbsp– & nbsp–

If an error was found in the project (“SMLogix” program) that does not affect the network settings and EEPROM / ARRAY data, then it can be quickly corrected by quickly reloading the project using the MT.

For this in the laboratory it is necessary to load the revised SMLogix project into the auxiliary controller. Save the revised project by choosing "Save with selection"

saving only program without network settings and data

EEPROM / ARRAY:

- & nbsp– & nbsp–

In the event that changes in the project affect EEPROM / ARRAY data, it is necessary to create a copy of the entire project, and to create such a bootable MP, either you will have to use a working MP (an MP connected to the controller at the site), or replace it with a new bootable one created on an auxiliary controller ...

This is due to the fact that changing the EEPROM / ARRAY data (values ​​of settings, constants and variables) can affect the operation of the project, and all changed EEPROM / ARRAY values ​​will already be contained on the bootable MP, and it is this MP that the controller will need for normal operation after loading ...

- & nbsp– & nbsp–

In the controller "Pixel" in the version 25xx-xx-x, the functions for managing the application project are available. These functions are available from the SMLogix Project menu.

- & nbsp– & nbsp–

Only for version 25xx-xx-x.

After the application project has been loaded into the Pixel, the function of manual control of the controller I / O may be available if the current configuration of the controller and the configuration of expansion modules (MP) matches the one selected in the SMLogix project.

- & nbsp– & nbsp–

In this case, in the "SMLogix Project" "I / O Control" menu, the corresponding menu will be configured to control the hardware I / O of the controller and MP connected to the system bus.

If the configuration of the controller specified in the project does not coincide with the current configuration of the object (the controller or MP on the system bus does not contain the required number of I / Os or is not physically connected), the I / O control function will be unavailable.

In case of configuration mismatch, in the "I / O control" menu

an error message will be displayed in the configuration of this module:

- & nbsp– & nbsp–

The absence or malfunction of the module can be indicated by an identifier value equal to 0.

After loading the application project, the state of each I / O can be switched to manual control when the state is fixed with the required value.

To do this, it is necessary to switch the selected input or output to manual control mode as follows:

- & nbsp– & nbsp–

Variable state editing will become unavailable.

Attention! The manual I / O control mode for all modules is automatically disabled after a project download or a power reset.

- & nbsp– & nbsp–

The following functions are available in the Service Mode (SR) "Configuration" menu:

Kernel version, serial number and product modification, information about the state of the network card and memory module, settings of the Som (RS485) port and control of master requests on this port for the ability to download the project from SMLogix via RS485 if the master is running on this port ModBus network.

- & nbsp– & nbsp–

The EEPROM and ARRAY storage blocks are provided in SMLogix to store project data such as setpoints, constants or miscellaneous variables.

Using these blocks, the data in the project can be written to or read from the non-volatile memory of the Pixel controller.

The "Memory module" menu contains information about the available amount of non-volatile memory of the "Pixel" controller.

- & nbsp– & nbsp–

Each controller has 256 bytes of internal non-volatile EEPROM available for storing user-defined project data.

In the case when a project requires a larger amount of data, it is possible to connect an external Memory Module (MP) to the "Pixel".

This allows you to increase the amount of data storage up to 250 Kb, as well as get at your disposal such functions as saving and loading an application project and the system log (the set of functions is limited for the execution of 12xx-xx-x).

- & nbsp– & nbsp–

Similarly, when removing the MP from the slot, the controller detects the absence of an additional MP and stops working with it. The work continues only with the built-in MP.

Note. In the case of using a project with an MP and the amount of EEPROM / ARRAY data greater than 256 bytes, it is recommended to locate the most critical and necessary data at the lowest addresses within 0 ... 255, since if the MP is deleted, data at addresses over 255 will be unavailable.

- & nbsp– & nbsp–

If there is an external MP, you should make sure that it is allowed to work with this MP - there is a corresponding inscription on the bottom line of the screen.

If the MP contains a previously saved project or settings and data from another project, and, after a corresponding warning, they refused to use this MP (see.

"Services of the memory module"), the display in the "Configuration" menu "Memory module" will show:

- & nbsp– & nbsp–

This means that the external MP is blocked, only 256 bytes of internal memory is used for operation. In this case, the "EEPROM overflow" alarm also occurs. In order to eliminate the accident, it is necessary to provide the amount of EEPROM data necessary for the project operation. To do this, you need to either replace the existing MP with a similar free one, or through the menu "Allow MP operation"

allow to use the existing MT in the project.

At the same time, when trying to connect the MP through the menu "Allow work

MP ", the controller will issue a corresponding warning:

- & nbsp– & nbsp–

If confirmed, all data on the MP will be erased.

After that, if the amount of MT for the project is sufficient, the accident is eliminated, the operation of the EEPROM and ARRAY storage units in the project will be restored.

If the "ESC" button is pressed, the MP will be blocked and the information on it will be unavailable for writing / reading. In this case, the data on the MT (Another saved project or its data) will be saved.

- & nbsp– & nbsp–

Entering the CP menu is carried out by simultaneously pressing the combination of buttons "r" and "s". No shutdown or shutdown of the controller is required.

- & nbsp– & nbsp–

Som port settings (RS485) To set the Som (RS485) port parameters in the Service mode (CP) of the "Pixel" controller, the "SOM port" menu item is provided.

- & nbsp– & nbsp–

To ensure control of reliable operation and simplify diagnostics, as well as for the convenience of detecting, preventing and eliminating possible malfunctions and eliminating error situations during the operation of the Pixel controller, a system for monitoring emergency situations and notifying the user about their occurrence is provided.

For visual notification of an emergency, an alarm indicator is provided on the front side of the case - a red alarm LED.

Depending on the version, “Pixel” provides for a different number of monitored emergencies and different ways of detecting alarms, their handling and shutdown.

The occurrence of alarms will trigger the red alarm LED. The diode starts flashing rapidly.

After the fault has been eliminated, the diode either automatically goes out (version 12xx-xx-x), or for this you need to reset the trouble using a special alarm manager in the "System troubles" menu

(execution 25xx-xx-x.).

- & nbsp– & nbsp–

Resetting alarms and alarm indications In the "Pixel" controller, version 12xx-xx-x, the alarm resetting and switching off the alarm indication occurs automatically after the alarm is eliminated. Thus, the presence of an alarm indication indicates the presence of an active alarm at the present time.

For the 25xx-xx-x version, the alarm indication can be reset or disabled in the special alarm handling menu using the alarm manager - the "System alarms" menu.

In case of a single occurrence or after elimination of the causes, the failure, unlike the version 12xx-xx-x, is not automatically reset until it is confirmed in the "System troubles" menu.

The presence of an emergency indication in this case indicates either the presence of an active emergency at the present time, or a single (short-term) occurrence of an emergency during operation. The alarm manager in the "System troubles" menu will help you to understand this in more detail.

System Alarms Menu

In the controller "Pixel", version 25xx-xx-x, a special menu "System troubles" is provided for registering emergencies occurring during the controller's operation in the SR.

All accidents occurring in the course of controller operation are registered in the "System troubles" menu and can be viewed and processed in order to properly eliminate accidents and their consequences, as well as analyze the causes of their occurrence.

If there is a connected MP, all accidents that occur during operation, the time and date of their occurrence are recorded in the Journal.

- & nbsp– & nbsp–

When a new alarm occurs, the alarm manager initiates the creation of the corresponding item in the "System troubles" menu.

The manager assigns the “Active” status to the troubles and connects the emergency indication - the emergency diode is rapidly blinking.

- & nbsp– & nbsp–

Attention! After switching on the alarm indication, the control of the red LED operation from the application project is blocked, the diode is transferred under the control of the internal alarm manager.

opposite the item "System accidents".

- & nbsp– & nbsp–

In this case, if the cause of the accident is subsequently eliminated by itself (single or rarely occurring accident), the emergency indication does not turn off, the status of the “Active” emergency remains. Icon ""

opposite the "System troubles" item is disabled.

For the final elimination of alarms, it is necessary to edit the alarm status from the service mode menu.

- & nbsp– & nbsp–

Red LED for emergency indication - in rapid blinking mode.

To disable the alarm and alarm indication, it is necessary to transfer the alarm status to the "Confirmed" state.

- & nbsp– & nbsp–

If at the moment of acknowledgment of the trouble the cause of the trouble has been eliminated, the trouble is deleted from the "System troubles" menu. Alarm indication is disabled (If there are no other alarms with the "Active" status).

- & nbsp– & nbsp–

The alarm is assigned the "Confirmed" status. In this case, the alarm indication does not turn off, the alarm LED goes into a slow blinking mode (If there are no other alarms with the "Active" status).

After that, the trouble can be removed from the menu by re-confirmation after the cause of the trouble has been eliminated.

If, for some reason, an alarm cannot be eliminated at the current time or its elimination is postponed, and the alarm indication of this alarm must be turned off to control the occurrence of other alarms, then the alarm status can be transferred to the state of inhibition of activity.

- & nbsp– & nbsp–

Note. After loading the application program using the computer or the Memory Module, all existing alarms are cleared, the statuses are cleared.

Attention! Alarms in the activity inhibited state or in the "Acknowledged" state will revert to the "Active" state after loading, if their cause has not been eliminated by the time of loading.

- & nbsp– & nbsp–

In the “Pixel” controller, the supply voltage is continuously monitored internally during operation.

The battery voltage, the level of the external supply voltage of the entire controller “Usup. + 24V "and internal power supply of the processor module board" Upit. + 5V "

If the voltage level of the battery or external power supply does not correspond to those required for the normal operation of the controller, a corresponding alarm occurs (see the section "System troubles").

You can control the state of the mains voltages using the Service Mode (SR) "Power" menu.

- & nbsp– & nbsp–

In performance controllers 25xx-xx-x, if there is a connected MP, the system events log is automatically kept.

The volume of 4KB is reserved for the log on the external MP, and the log can contain up to 250 records of various events.

Events are sequentially stored in non-volatile memory. If the log is full, completely newer events overwrite the oldest.

- & nbsp– & nbsp–

The record contains the sequence number of the event in the list, the date and time of registration of the event, its description and additional auxiliary information.

- & nbsp– & nbsp–

meaning that the starting address of the list has been reached and there are no older events in the log.

When reaching the most recent record after pressing the "r" button, the screen will display:

- & nbsp– & nbsp–

The Pixel controller features a volatile real-time clock and calendar. If a battery is installed in the controller, the time and date are maintained even when the main power is turned off.

Viewing and editing the current time and date is available both from the “SMLogix” project (program) (FBD-blocks “Time and Date”), and from the menu of the Service Mode (SR) “Time and Date”.

- & nbsp– & nbsp–

it is possible to load the kernel from a computer using standard Windows tools without the help of special programmers.

To do this, just use the HyperTerminal program, a standard Windows component.

An automatic kernel loader is built into the core of the Pixel controller.

The transmission is carried out using the 1K Xmodem protocol. The file containing the controller core has the * .SIM extension, the file with the HyperTerminal connection settings - the * .ht extension The kernel version is the file with updates and fixes (* .sim), and the HyperTerminal connection settings file (* .ht) can be found on the website Segnetics http://www.segnetics.com/.

- & nbsp– & nbsp–

HyperTerminal is a standard Windows component.

To load the controller kernel using a computer, HyperTerminal must be configured to transmit to Pixel.

The configuration file (with * .ht extension) is available on the Segnetics website

http://www.segnetics.com/. It automatically launches the HyperTerminal program with all the necessary settings to load the Pixel kernel.

Note. If HyperTerminal is not installed on your computer, you must install it using standard Windows installation tools.

If for any reason the HyperTerminal configuration file is not available, you can configure the program yourself.

- & nbsp– & nbsp–

2. Select the File menu, the New Connection command.

3. In the Connection Description window that opens, specify the Name of the connection to be created (eg load), select the Icon you like:

- & nbsp– & nbsp–

10. Then close the HyperTerminal window with saving the changes. Now, by clicking the Start button, in the All Programs, Accessories, Communication command bar, an additional HyperTerminal tab will appear, in which the created connection will be available.

- & nbsp– & nbsp–

1. Connect the power terminals to the Pixel controller. In this case, the power source must be turned off.

- & nbsp– & nbsp–

3. Start HyperTerminal using the previously created connection. The configuration file (with * .ht extension) is available on the Segnetics website http://www.segnetics.com/.

It automatically launches the HyperTerminal program with all the necessary settings to load the Pixel kernel.

The connection can also be created by yourself. (see the section Configuring HyperTerminal).

4. Select the number of the COM - port of the computer to which the RS485 / RS232 converter is connected to download the controller.

To do this, in the HyperTerminal program window, on the Call menu, select the Disconnect command (if the communication session is active). From the File menu, select Properties.

In the window that opens, in the Connect via: field, set the connection port number:

- & nbsp– & nbsp–

8. Power on the Pixel controller. It independently activates the transfer process. The counter of packets in the Packet: field will start to grow, in the File: field, the transmission progress indicator will start filling:

- & nbsp– & nbsp–

9. Close the HyperTerminal program. The controller is ready for operation. If after loading “Pixel” does not start automatically, ie. does not display the splash screen or display of the application program, turn off and on the power of the controller.

- & nbsp– & nbsp–

Possible errors and difficulties

1. There was a crash during the kernel boot process. The packet counter is not updated, the transmission process is stopped:

The transfer process must be resumed. Turn off the power to the controller. Stop the transfer process by clicking the Cancel button.

Restart the HyperTerminal transfer process. Power on the controller.

Note. To initialize the boot process, the controller must be in the shutdown state for at least 3 seconds.

2. After starting the transfer process and turning on the controller, the transfer process does not start.

- & nbsp– & nbsp–

3. After a successful download, the controller did not start automatically, ie. no splash screen or application display is displayed.

Turn off the controller power supply for more than 3s and turn it on again. If the controller does not start, repeat the boot process.

- & nbsp– & nbsp–

6. Appendix 1. System page (SS).

System page - the address space of the “Pixel” controller, where data is located that contains system information about the controller and allows you to control its operation. The access to the SS is carried out through the available communication channels using the Modbus RTU protocol.

For CC, the register address space is reserved from 0xFE00 to 0xFFFF.

Read Holding Registers requests (function 0x03) are used to read information. To write information to the SS, the Write Multiple Registers requests (function 0x10) are used.

- & nbsp– & nbsp–

105. See: Criminal Procedure Law of the Russian Federation: Textbook. / Ed. P.A. Lupinskaya. M., 20 ... "MONTHLY SCIENTIFIC - TECHNICAL AND PRODUCTION JOURNAL Published with the assistance of ® Complex of architecture, No. 3 construction, development and reconstruction of Moscow, HUMAN AND SOCIETY No. 2 (11) - 2011 Editorial Board Chairman Doctor of Military Sciences, Doctor of Technical sciences, professor, honored worker of the higher school of the Russian Federation, laureate of the Pra ... "image of a woman, mechanisms for creating and successfully ..." PRINCIPLES Specialty 05.13.19 - Methods and systems of information protection. Information security ABSTRACT of the thesis for the degree of candidate technically ... "

“RU 2 461 569 C2 (19) (11) (13) RUSSIAN FEDERATION (51) IPC C07K 16/18 (2006.01) C12N 15/13 (2006.01) C12N 15/63 (2006.01) A61K 39/395 (2006.01) A61P 25/00 (2006.01) FEDERAL SERVICE FOR INTELLECTUAL PROPERTY (12) DESCRIPTION OF THE INVENTION TO A PATENT (21) (22) Application: 2009118621/10, 18.10.2007 (72) Author (s): ... "

2017 www.site - "Free Electronic Library - Various Documents"

Materials on this site are posted for review, all rights belong to their authors.
If you do not agree that your material is posted on this site, please write to us, we will delete it within 1-2 business days.