DESIGO XWORKS, DESIGO Insight . 1-й день курса.

Name: DESIGO XWORKS, DESIGO Insight . 1-й день курса.
Uploaded: 2014-04-25T14:58:22.000Z
Duration: 4 h 56 min 28 s

Understanding Controller Setup and Configuration

Initial Setup of Controllers

The discussion begins with the importance of understanding the foundational aspects of controller setup within a training framework.

An example is provided regarding the creation of a controller, specifically referencing the 36 ED model, emphasizing its configuration process.

The necessity to assign an IP address to the controller is highlighted, with an example IP address given as 10.1.

Managing Multiple Controllers

The speaker explains how to create multiple controllers in a network segment, indicating that one should be designated as the primary server for synchronization purposes.

It is emphasized that having a primary server is crucial for time synchronization and managing emergencies effectively across all controllers.

The primary server's role includes maintaining network time and handling emergency protocols; all other controllers will align with this primary server.

Addressing Network Segmentation

A brief overview of creating additional segments within the network is discussed, noting that structure can vary significantly based on requirements.

The speaker mentions limitations in adding new segments within existing networks due to structural constraints.

Understanding Node and Subnet IDs

Key concepts such as Node ID and Subnet ID are introduced; Subnet ID serves as an analogy for network addressing while Node ID represents device identification.

Automatic numbering of controllers upon creation is explained, simplifying management without manual intervention unless necessary.

Adding Modules and Cards

Instructions are provided on integrating additional modules or cards into controllers, particularly focusing on compatibility with specific models like version 27 or 128 controllers.

Details about selecting appropriate cards (e.g., PSB B card for integration purposes) are shared to enhance functionality within the system.

Installation Limitations

There are restrictions noted regarding how many cards can be added simultaneously; only certain configurations allow for dual installations due to physical space constraints.

How to Configure Network Controllers

Understanding Controller Visibility

The initial discussion revolves around the physical setup of network cards and their documentation, emphasizing that only specific configurations are allowed.

A critical step in programming is understanding how to view the controller, which is essential for troubleshooting and configuration.

Instructions are provided on accessing network card properties through local connections, highlighting the importance of correct settings.

Configuring IP Addresses

An example IP address (10.100.101.10) and subnet mask (255.255.255.0) are suggested for proper network configuration.

Common errors that prevent visibility of controllers are discussed, indicating that issues often arise during simulation setups.

Ensuring Proper Setup

Emphasis is placed on managing security settings within Windows to ensure smooth operation of the controllers.

Participants are instructed to connect their cables properly to the controller's interface for effective communication.

Troubleshooting Connection Issues

The system's independence from computer status is highlighted; even if a computer fails, programs in controllers continue functioning.

Steps are outlined for preventing connection issues with controllers by adjusting additional parameters in network settings.

Driver Installation and Configuration

Importance of installing drivers correctly from specified directories is stressed; this includes USB adapter drivers and standard PC card drivers.

Users must navigate through control panel settings post-driver installation to ensure proper functionality of network interfaces.

Finalizing Configuration Settings

Key points about ensuring correct protocol application based on hardware specifications (e.g., PC card 21 vs 10).

The session concludes with a reminder about registration processes related to controller visibility and configuration management.

This structured summary provides an organized overview of key discussions regarding configuring network controllers, focusing on practical steps and troubleshooting methods while linking directly back to relevant timestamps for further exploration.

Configuring a Controller: Steps and Insights

Understanding IP Mask and Reset Process

The importance of knowing the IP mask is highlighted, emphasizing that a standard operation involves resetting the controller before configuration.

A factory reset is necessary to revert the controller to its default settings, which includes an initial IP address.

Initial properties such as device name and address must be configured for proper functionality; this process is crucial for effective setup.

Steps to Reset the Controller

Before configuring, it's essential to reset the controller to avoid conflicts with existing settings or programs.

The reset process involves pressing two buttons in sequence: one button is held down while briefly pressing another, then releasing it.

The procedure requires holding one button until a service light blinks, indicating successful reset; alternatively, power cycling can achieve the same result.

Post-Reset Configuration

After resetting, wait for specific indicators (like blinking lights) before proceeding with further configurations.

It's advised to disconnect from any conflicting networks during setup to prevent issues related to duplicate IP addresses.

Connecting and Identifying Devices

Once reset, users should access the controller through software by selecting appropriate ports for connection.

Users are prompted to choose their network card settings without altering default parameters during device identification.

Troubleshooting Configuration Issues

If devices appear unconfigured post-reset, it may indicate issues with previous setups or conflicts within virtual environments.

Observations reveal that some controllers may not display complete configuration details like Device ID or Name immediately after setup.

Programming with CFC: Understanding the Basics

Introduction to CFC Programming Environment

The session begins with an introduction to the programming environment called CFC, where users can start programming by accessing it through right or left clicks.

The speaker emphasizes the importance of establishing a connection between sensors, controllers, and programs as they create their project topology.

Libraries and Blocks in CFC

Discussion on libraries within CFC, highlighting that standard object libraries will be heavily utilized during programming.

Users are encouraged to select blocks from recently used or standard options for efficient programming.

A specific library (px FV 0400) is mentioned as universally available for all participants.

Working with Analog Inputs

The speaker demonstrates how to manipulate analog input blocks by clicking twice to increase or decrease values, emphasizing visibility in design.

Properties of the analog block are discussed; users need to ensure they have licenses ready for programming.

Licensing and Setup Requirements

Participants are reminded about unpacking license archives necessary for software functionality.

Importance of having a valid key for programming is reiterated; sharing keys within companies is addressed.

Configuring Block Properties

The properties of objects linked to analog values are explained, including signal addressing and its relevance in connecting temperature readings.

Instructions on setting visible parameters such as upper/lower limits and sensitivity zones are provided.

Naming Conventions in Programming

Emphasis on naming conventions: using both English and Russian names for clarity in operation and maintenance purposes is recommended.

It’s advised not to alter certain settings unless necessary; maintaining simplicity in naming helps avoid confusion later on.

Understanding Addressing in Modular Controllers

Setting Up External Temperature Inputs

The discussion begins with the importance of setting external air temperature, indicating that a value of -35 degrees will be used. This sets the stage for understanding properties related to temperature inputs.

The speaker mentions that an address will be applied later, emphasizing the need for proper configuration before proceeding.

Address Configuration Process

The process of assigning addresses to objects is introduced, highlighting the necessity of linking physical signals or sensors to the controller's code.

Right-clicking on any object brings up a menu for addressing, which is crucial for ongoing operations and configurations.

Understanding BNET and Signal Types

An explanation of BNET as a virtual value within the program is provided. It serves as an internal variable not directly tied to physical components but essential for programming logic.

Different signal types are discussed, particularly focusing on standard temperature sensors. The speaker suggests selecting simple options like R1K temperature sensors for ease of use.

Addressing Methodology in Modular Controllers

A distinction between addressing methods for compact versus modular controllers is made. Modular controllers have specific address markers that help identify each module uniquely.

Each module has a unique identifier based on its position and function within the system, which aids in organizing and managing multiple inputs/outputs effectively.

Practical Considerations in Module Setup

The speaker emphasizes how modules can be addressed flexibly (e.g., using leading zeros), suggesting best practices for maintaining clarity during programming.

A practical tip is shared about ensuring electrical connections are secure before finalizing module setups, underscoring safety during installation processes.

Final Thoughts on Controller Configuration

There’s mention of potential issues when reprogramming modules if changes occur unexpectedly; thus, it’s important to maintain clear documentation throughout setup.

The conversation hints at specialized software available for project design that could assist users in navigating complex configurations more efficiently.

Understanding Compact Controllers and Addressing

Overview of Temperature Sensors and Addressing

Discussion on using temperature sensors with compact controllers, emphasizing the importance of correctly setting the address for input signals.

Mention of feedback mechanisms and types of sensors (digital, contact), highlighting the need to understand how to operate compact controllers effectively.

Input Types and Codes

Explanation of universal codes for compact controllers: 03 for discrete inputs, 04 for analog outputs, and 05 for discrete logic outputs.

Importance of specifying input type and number when programming; a clear structure is necessary to avoid confusion.

Discrete Outputs and Inputs

Clarification on how to denote discrete outputs in programming; example given as "05.1" for specific output identification.

Inquiry about identifying a second discrete input on board, leading into further discussions about coding conventions.

Universal Inputs and Addressing Challenges

Question raised regarding universal input identification; emphasis on avoiding common mistakes in addressing.

Acknowledgment that addressing can be complex due to inconsistent labeling among modules; caution advised against errors in setup.

Practical Application of Addressing

Instruction on calculating addresses by subtracting from a base value; practical tips provided for users unfamiliar with the system.

Guidance on recognizing older controller versions versus newer ones, stressing the importance of understanding module specifications during setup.

Module Selection Process

Discussion about selecting module types within software interfaces; highlights potential pitfalls when working with older models.

Reminder that certain settings may not require adjustment unless specific conditions are met within project parameters.

This structured summary captures key insights from the transcript while providing timestamps for easy reference.

Overview of Controller Modules and Programming

Introduction to Controller Modules

The controller modules can be easily programmed by simply opening a software application and clicking a single button to load the program. A standard cable is required for connection to the computer.

Loading Programs into Controllers

To load programs, one must connect two cables: one for the controller and another for parallel communication. This allows for seamless program loading without complex steps.

Project Management in Programming

When using multiple modules within a single controller, it is necessary to create two separate projects. One project will handle specific controllers while the other manages module addresses.

Understanding Module Communication

The process involves creating a table that facilitates communication between different modules, ensuring that each module understands its assigned address correctly.

System Expansion Considerations

Expanding the system requires careful planning; understanding how many physical data points are available is crucial before proceeding with any upgrades or expansions.

Physical Data Points and System Capacity

New Module Specifications

Newer modules are designed based on precise physical data rather than just analog signals, which enhances their functionality in various applications.

Historical Context of Controller Models

The naming conventions of controllers (e.g., 64 vs. 128 models) reflect their capacity to handle specific numbers of input/output points, which has evolved over time.

Load Unit Calculations

The calculation of load units has shifted from being based solely on data points to considering both load units and physical connections when assessing system capabilities.

Planning for System Expansion

Before expanding systems, it's essential to calculate existing physical data points against potential new loads to ensure compatibility and efficiency in operation.

Practical Steps for System Configuration

Example Scenario for Expansion

In an example scenario where a system with a 64-controller needs expansion, one must account for existing load units consumed by current modules before adding new ones.

Managing Legacy Systems

Older models still exist in the market but require understanding their limitations compared to newer models that offer enhanced features like increased data point capacities.

Addressing Data Point Management

Each module's capability varies; thus, managing how many outputs or inputs are utilized becomes critical in maintaining operational efficiency across systems.

Conclusion on Module Functionality

Final Thoughts on Module Utilization

It’s important to understand how each module functions within its designated role; this includes recognizing discrepancies between expected performance versus actual output during operations.

Connecting to the Site and Compiling Code

Initial Steps for Connection

The first step is to connect to the specified site, which serves as a control point in the network.

Select your port from the available options and initiate the connection. Confirm that you are connected successfully.

Compilation Process

During compilation, it’s recommended to check "calate Trans sequence" for generating sequences that dictate program operation cycles.

If changes are made, simply press "Start" again to begin recompilation without needing a full reset.

Uploading Program Changes

After compiling, select whether to upload only changes or the entire program; opt for uploading everything if starting fresh.

A warning will indicate that the station will be cleared for a complete upload; confirm this action.

Real-Time Monitoring and Testing

Entering Test Mode

To view real-time temperature values, enter test mode by pressing the designated button.

In test mode, ensure there are no errors displayed (indicated by zeros), confirming successful uploads.

Viewing Temperature Values

Highlight specific data points in test mode using left-click; this allows monitoring of analog temperature readings.

Adding Inputs and Outputs

Modifying Program Logic

Experiment with adding different types of inputs and outputs within the program logic framework.

Addressing Signal Types

Ensure correct signal types are selected; incorrect settings can lead to miscommunication with sensors.

Final Adjustments and Additions

Troubleshooting Issues

If issues arise with discrete outputs, consider removing unnecessary components before reattempting configurations.

Adding New Components

Proceed with adding new analog inputs and digital outputs systematically while ensuring proper library usage.

Configuration and Programming of Control Systems

Initial Setup and Adjustments

The discussion begins with the need to avoid testing in a trial mode, emphasizing that adjustments are necessary for proper functionality.

Colleagues from Khabarovsk have made progress, but there is an issue with overlapping elements that require repositioning for clarity.

The speaker suggests programming steps, indicating a focus on setting parameters correctly for optimal performance.

Binary Outputs and Inputs

A binary output is added to the system; the speaker mentions naming conventions for components like heating valves and fan operation modes.

Clarification is provided regarding status control signals, distinguishing between operational statuses and feedback mechanisms.

Manual Controls and Planning

There’s a transition to manual control settings; participants are encouraged to document their configurations carefully to avoid future issues.

The importance of time management during collaborative work is highlighted, stressing that planning can prevent complications when colleagues leave unexpectedly.

System Configuration Insights

Discussion shifts towards different tram systems in Moscow versus Krasnodar, illustrating logistical considerations in transportation methods relevant to project planning.

The speaker notes differences in tram operations which may affect travel efficiency for team members involved in the project.

Finalizing Settings and Testing Procedures

Attention returns to configuring binary outputs; specific properties are set up for digital outputs related to air supply fans.

Participants are prompted to ensure all settings are recorded accurately before proceeding with further programming tasks.

Addressing Common Issues

A critical moment arises where participants must address potential problems at higher levels of configuration.

Emphasis is placed on documenting addresses manually as they configure temperature sensors and other inputs crucial for system monitoring.

Loading Programs and Testing Modes

Once configurations are complete, participants prepare to load programs into the system while discussing how changes will be implemented effectively.

The necessity of selecting appropriate signal modules during setup is reiterated, ensuring correct functionality within the overall control framework.

This structured approach provides a comprehensive overview of key discussions surrounding control system configuration while maintaining clarity through timestamped references.

Understanding Online and Offline Modes in Control Systems

The Importance of System States

Discussion on the critical state of systems, emphasizing that certain conditions can lead to failures or accidents.

Clarification that not all systems are suitable for specific types of incidents, highlighting the uniformity of responses across different scenarios.

Online Mode Operations

Explanation of how commands (e.g., turning on a fan) are issued in online mode, where real-time adjustments can be made to system values.

Description of how values can be manipulated live within the program, affecting system operations immediately.

Transitioning Between Modes

Insight into the differences between online and offline modes; once out of test mode, discrepancies may arise between expected and actual system states.

Emphasis on how changes made during online operation can lead to inconsistencies if not properly managed.

Handling Changes in System Values

Discussion about potential issues when values are altered in offline mode versus online mode, stressing the importance of maintaining consistency.

Recommendations for managing discrepancies by resetting changes to ensure proper functionality.

Real-world Implications

Highlighting practical scenarios where operators might inadvertently change settings after programming has been completed, leading to operational challenges.

Explanation that modifications made in either mode affect existing blocks but do not allow for new connections or blocks to be added.

Analog Value Adjustments

Introduction to adjusting analog values similarly to digital commands (like starting a fan), demonstrating practical applications within control systems.

Mention of visual indicators reflecting changes in analog settings based on user inputs.

This structured overview captures key discussions from the transcript while providing timestamps for easy reference.