TRICON System Discussion Thread
Thread Content
A new discussion topic for Tricon DCS/ESD has been created; please post any questions related to this brand’s DCS/ESD systems here going forward, to facilitate easy reference and answering. The discussion topics include: hardware installation, software configuration, debugging, problems that occur during use, etc. Those who need TRICON-related materials can download them from http://bbs.hcbbs.com/viewthread.php?tid=363881. For an SIS system using Consen’s Tricon TS3000, what tasks need to be carried out on both the software and hardware of the system during maintenance? What are the key points? This post was last edited by Mobei Yihai on 2009-4-20 20:23.]
1. Carry out the SOE record cleanup work in accordance with the operation sheet, and save the records elsewhere； 2. Conduct inspections on critical hardware circuits ； 3. Carry out necessary upgrades to the older versions of the software ； 4. Clean dust from the operation station and cards ； 5. Test the redundant cards ； 6. Collect hardware testing information.
The main tasks of inspection work include: 1. Operation station/Engineer station/SOE station (system software backup, verification of software versions). 2. Controllers, I/O units (TRICONEX-specific diagnostic software is used to diagnose the system – controllers & I/O cards). 3. Communication section (check whether there are any alarms in the communication devices and whether the connections are secure). 4. Technical requirements (comprehensive functional and performance tests shall be carried out after the inspection work is completed). )
Hardware aspect: 1. If it operates for a long time, it is recommended to shut down the power supply to remove dust. 2. Check the hardware components; this can be done through system diagnostics, and any issues should be replaced promptly. 3. Check the power supply; use a multimeter to measure it, and ensure that the voltage of each power supply is within the specified range. 4. Terminal tightening is actually very important; the SIS system doesn’t need to be operated on a regular basis, but terminal tightening must be carried out during maintenance. 5. Spare parts card testing: New spare parts must be tested using the maintenance online system to ensure they work properly. Software aspect: 1. First, carry out proper backups – back up the project files, and if possible, clone the entire drive as well, storing the backup files in a separate location. 2. Carry out proper software modifications; if changes are made to the software, debugging must be done thoroughly, as many issues are difficult to detect without debugging. 3. Set or modify the password according to the actual situation to prevent unauthorized access.
Thank you to all fellow sailors for your generous help! I found it very inspiring :) :lol I would like to summarize the points below; I hope fellow netizens can offer their feedback. Preparations before a power outage: 1. Carry out backup procedures: 1. Back up project files; if possible, it’s best to create a clone of the entire drive and store the backup files in another location ； 2. Carry out the cleanup of SOE records and store them elsewhere ； 3. Save the operating parameters. II. Check for hardware faults: 1. Verify whether the status lights of the cards are normal, and whether the fans are operating properly; keep records of this ； 2. Check the communication status. 3. View the system information and keep records. III. Prepare the relevant verification instruments and tools. Power outage for maintenance: I. Removing dust from the system hardware ； II. Replace the faulty components and fans ； III. Calibration of lightning protection grids and safety grids ； IV. Replace nameplates and wire labels that are unclear or damaged ； V. Tighten the terminals of all cables ； VI. Inspect all network connectors; replace those that are corroded or loose ； VII. The controller battery should be replaced when it reaches the end of its useful life ； (? ) VIII. Dust removal from the operation station, and replacement of faulty components (monitor, keyboard, mouse, etc.). When the system is powered on, first verify that the UPS is working properly, with an output voltage of 220VAC±10V ； II. Verify that the 24V power supply is working properly. III. The system should be powered on in stages: 1. Power on the system fans. 2. Power on the control station. 3. Power on the operation station. 4. Disconnect the control station and check the status of the indicator lights on the cards. IV. Perform hardware testing of the system: 1. Conduct switch-over tests on redundant modules and cards. 2. Verify the I/O channels. 3. Test network communication. 4. Test backup modules and cards while they are connected. V. Modify the configuration according to the process requirements (optional). VI. Perform system calibration. VII. Back up the project files. I’m not sure if there are any items missing
I think this maintenance plan is fine. Could someone with more experience give some advice and check if there’s anything else that needs to be disclosed?
The difference between DCS and ESD doesn’t seem to be that significant. The documentation all has the same structure; there’s no difference in the configuration either, right?
You can also contact the manufacturer directly and ask them to come up with a plan!
Since it is a SIS system, there should be corresponding inspection cycles and inspection methods.
It’s quite comprehensive; these are the things we did during the maintenance period
With the guidance of an expert, it’s written very comprehensively. However, I think we also need to consider the timing of inspections, that is, how often inspections should be carried out and how often maintenance is required. It’s best to have the manufacturer come up with a plan to prevent problems before they occur.