HCBBS Forum (English)
Submit Chemical Projects / Find Solutions
Amplify Your Requirements on a Broader Chemical Platform *Engineering · Technology · Equipment · Solutions*
Submit Request

In the CS3000 system, how do different domains communicate with each other? 》? ?

2015-12-21View Original

Thread Content

As the title suggests: HIS0350 and HIS0264 belong to Domain 3 and Domain 2 respectively. What needs to be achieved now is that HIS0350 and HIS0264 have identical operation interfaces and functions (trend lines, historical data). 1. Is it necessary to establish communication between Domain 3 and Domain 2? 2. How do the operation stations in different domains (HIS0350 and HIS 0264) achieve communication? Automatic control instruments
Reply #22015-12-22
How do the operation stations in different domains (HIS0350 and HIS 0264) achieve communication? Solve
Reply #32015-12-22
How do different domains communicate within the CS3000 system?
Reply #42015-12-22
This requires multi-project management authorization for the Yokogawa DCS.
Reply #52015-12-22
How to authorize it, through which module, and how to implement it? What software and hardware devices need to be added?
Reply #62015-12-22
This system really doesn’t understand; I’m sorry
Reply #72015-12-26
Solution for Multi-Project Connection among CS3000 Systems I. Background Plant No. 5 and No. 6 of a spandex company utilize the Yokogawa CS3000 system. To enable interaction and monitoring between these two systems, BCV was used to connect the two DCS systems. However, in practical use it was found that it was not possible to share tasks between the systems, nor could information be exchanged between them; thus, the advantages of multi-project connection were not realized, and this caused many difficulties for the operators on site. The specific configurations for this project are as follows: For System 5: 1 engineer station (HIS0164), 6 operation stations (HIS0163–HIS0158), and 2 control stations (FCS0101–FCS0102). Software version: R2.60.00. For System 6: 1 engineer station (HIS0264), 4 operation stations (HIS0263–HIS0260), and 2 control stations (FCS0201–FCS0202). Software version: R2.20.50. There is 1 bus converter (BCV) available. Additionally, there are 2 sets of the LHS4450 multi-project connection software package, and 2 sets of the LHS5450 multi-project connection configuration software package. II. Solution: The multi-project connection feature enables resource sharing between different projects, allowing for mutual operation and monitoring of critical workstations. Based on the actual conditions of the users, and building on what already exists, the following solution is proposed; it can effectively address the issues present in the current system: upgrade the software version of System 5# to R2.20.50 ; The multi-project connection feature is available only in version R2.10 and later, so the old system must be upgraded first. A “bi-directional” connection between projects can be used, with various options available for implementing this: connection via a bus converter ; Requirements: a. The V domain names in the two projects must be different ; b. The station numbers within the same domain must be different ; c. All V network IP addresses must be different ; d. The bus converter must be configured in the upper-level system ; Connected through a control network ; Requirements: a. The V domain name in both projects must be the same ; b、All station numbers on the V network must be different ; c. All V network IP addresses must be different ; Connect via Ethernet ; Requirements: a. The IP addresses of all stations must be different ; Connect through a frame-based communication gateway ; Requirements: a. The V domain names in the two projects must be different ; b. The station numbers within the same domain must be different ; c. All V network IP addresses must be different ; d. The V network will be used when installing the lower-level gateway ; Based on the existing equipment and software on site, method one, which involves using a bus converter for connection, is adopted in this project. The specific configuration diagram is as follows: The configuration and settings for the upper-level system (i.e., System 6) and the lower-level system (System 5) are carried out separately ; III. Specific steps: Upgrade of the 5# system: Parameter saving and project backup ; Reinstall operating system NT4.0 ; Reinstall the CS3000 system ; Use the CS3000 R2.20 media drives LHSKM02 and LHSKM03, along with the original 5# KEYCODE from R2.06; since the ID MODULE is no longer used starting from R2.20, it can be removed. Then, install two software packages that support multiple-item connections on the engineering station. Upgrade control functionality to R2.20 ; Since version R2.20 introduces many new control functions, in order to use these new functions in the upgraded system, it is necessary to create new FCS files within the configuration settings, then import the backup files of the old version along with all project data, and proceed with offline installation. Upgrade the operation function to R2.20 ; Upgrade of alarm information ; Run the following file: \HIS\TOOL\BKHMsFormat R220 (the installation path for CS3000), and then restart the system. This is because the format for recording and displaying alarm messages has changed in the new version. Upgrade of the long-term trend archival software package ; Due to the increased size of the new version’s long-term trend archive files, it may be impossible to save trends after the upgrade; this requires either specifying a storage space with greater capacity or reducing the duration for which long-term trends are stored. Note: If you want to delete or move the long-term trend storage files, you must first stop the HIS function, that is, run the following file: \HIS\TOOL\BKHHisStop.EXE (located in the CS3000 installation path). c. In the new system configuration, execute the \"Download common components of projects\" function to upgrade the system configuration to R2.20 ; Since the number of definable items has been increased in both the new version of the \"Communication Input/Output\" configuration and the \"Schedule\" configuration, it is not possible to directly import the *.CSV files from the old version; corresponding modifications must first be made in Excel. Hardware connection: Connect systems 6# and 5# to the BCV (bus converter) respectively, setting 6# as the master side and 5# as the slave side ; Software settings: Settings on the 6# system side – check for any duplicates in IP addresses and operator station names across all connected stations ; Define the projects to be connected and their details in the multi-project connection configuration feature ; The specific path is: Syster view\mypjt\common\multipjt; the multi-project operation monitoring function should be set up on each operation station ; The specific path is: Syster view\mypjt\his0164\configuration\opecondef; each HIS should be downloaded to this location ; Lower-level section: “Project Common Files” – Settings on the 5# system side. a. Check for any duplicates in IP addresses and operation station names across all connected stations ; b. Generate a “Unified Operation Monitoring Station” (UHMIS) ; The specific path is: Syster view\mypjt. c. For the configuration of \"Project Common Files\" and \"Workstation List\" BCVs (on the 6# system side), a BCV station is created on the 6# system side ; Offline BCV installation ; Lower garment “Workstation List”” ; Software configuration: (1) Create three control group screens in System 6#, call the important workstations in System 5# for operation and monitoring on the upper-level system, and they can also be added as shortcuts to the overall process view of System 6# and the important control flowcharts. (2) Similarly, an important station of 6# can also be added to 5# for mutual operation and monitoring. (3) The format for calling the 5# system station in the control group is: station name + @ + project ID. IV. Appendix: Attached below are the solutions to the difficulties raised by users: Question 1: Can Yokogawa provide a card with a pulse output of 24 V DV? Answer: In the ADM51T/C-2, it can be configured as a contact output or a pulse output, with a maximum sensing voltage of 30VDC. Question 2: Is it possible to achieve a pure lag time of 10 MIN in a PID-STC regulator? Answer: In the CS3000 system, the self-tuning regulator cannot provide such a function; however, the “Dead-Time” block can be added, and the dead time can be set by adjusting the parameter SMPL in the configuration screen, thereby achieving a lag time of 10 minutes.
Reply #82015-12-29
By purchasing a multi-project software package along with the AVR10D, inter-domain communication can be achieved
Reply #92015-12-29
First, you need to determine whether it is a single project or multiple projects; if it are multiple projects, you need to purchase a multi-project connection software package. It is also necessary to confirm the network type; if both domains are Vnet/IP networks, a layer 3 switch needs to be purchased, and it is recommended to choose a layer 3 switch from Yokogawa. Yokogawa’s switches are labeled with Hertzman. If one is a Vnet and the other is a Vnet/IP, then an AVR10D needs to be purchased. If both are Vnets, a BCV needs to be purchased. That’s basically it.

Submit a Project

**Looking for Chemical Technology, Equipment & Solutions?** No Registration Required Broader Platform Exposure | Global Chemical Service Provider Connections

Submit Request — Free Consultation

Disclaimer

This is an automated machine translation of the original thread. Some technical terms may have inaccuracies; the original text shall prevail. Click "View Original" at the top right to access the source page, which supports IP-based automatic real-time language translation. Please watch out for contact details and sales inducements to prevent fraud. All content and translations are for reference only, representing solely the poster's personal views. For enquiries, email service@hcbbs.com.