Documentation error, MasterPiece 200/1 RCOM and MultiVendor Interface(MVI) Complement to description of fault tracing and DSCA 180 hardware
Problem:Solution
A description of this resolution:
"Documentation error, MasterPiece 200/1 RCOM and MultiVendor Interface(MVI) Complement to description of fault tracing and DSCA 180 hardware" resolves the following:
A description of this resolution:
- ADDITIONS
Chapter 6 Hardware
The start-up switch on the front of the DSCA 180 board can be in the following positions:
• AUTO: Not used
• CLEAR: Normal position for start-up and running of the communication.
• STOP: Stops software execution and the communication on the DSCA 180 board. Select ‘STOP’ and press INIT on the DSCA 180 board. This will stop cyclic reporting of configuration error from the DSCA 180 board.
• OFF LINE: Used for fault analyzing with Advant Station 100 ES in off line session.
‘OFF LINE’ also stops the communication.
Chapter 7 Fault tracing
If you follow the instructions in Chapter 3 and 6 and still do not have a correctly working communication link, please check the following:
1. Is the DSCA 180 board correctly strapped?
You must define the same node number for all the communication boards in the MP 200/1 node. All network numbers in the MP 200/1 node must be unique (for DSCA 180 1-9). The slave board address must be unique in the MP 200/1 (slave1 to slave6). If the network number or node number for any of the communication boards in the MP 200/1 is changed after the start-up of the node, the MP 200/1 must be COLD STARTED. (Connect an Advant Station 100 ES to the MP 200/1 and make a DUAP, press INIT on the main CPU with start-up switch in ‘CLEAR’ position and make a LOAP.)
2. Are modems and cables correctly set up?
The DSCA 180 must receive the correct modem signals. When you select full duplex mode for the modem signals, the signal Data Set Ready (DSR), Data Carrier Detect (DCD) and Clear to Send (CTS) must be set (also in telephone mode when the telephone line is connected). In half duplex mode the DSR must be set and DCD and CTS toggle between 0 and 1. Current CTS and DCD values are displayed on the front of the DSCA 180 board. The Cable DSTK 188 is wired for full duplex handling of modem signals (RTS(4)-CTS(5) and DSR(6)-DCD(8)-DTR(20)). Check the Database and PC program application.
– Have the Configuration MS (Line Characteristics, Network Configuration, RTU Status MS and Register Addresses MS) been sent to the DSCA 180 board? (The Network Configuration MS is not used for MVI-Siemens 3964(R), the node number for the RTU/PLC is configured in Line Characteristics MS REF14. The Register Addresses MS are not used for RCOM.) The VALID flag on these MS is set to 1 when the MS is successfully transferred to the module. The slave board address (1 - 6) defines the NET terminal on the Configuration MS.
– For RCOM in master mode, the Command MS for Normalize/de-block must be built and sent to the corresponding slave to start event-driven transmission from the slave.
– Data MS for the actual data transfer must be defined. A SEND MS in a slave must have a corresponding RECEIVE MS in the master and vice versa.
– The PC program with SENDREQ-elements for the flow control must be built and started. (not necessary in slave/passive mode).
3. Are there any System Messages reported in the MP 200/1?
Check system messages by connecting an Advant Station 100 ES to the AC 400. Also check the system messages when you restart the DSCA 180 board. To restart the board press INIT on the DSCA 180 board with the start-up switch in ‘CLEAR’ position. All configuration errors are reported at start-up. Error messages with mtype 34 and with mtype 17 and task name CLGAxxx or CLHAxxx are translated in Chapter 7. Note that some errors are only reported once. Other messages that are important are system messages with mtype 17 and task name CXNU7xx or CXNM910 and mtype 30 and task name CXAM000. These messages are translated in the ABB Master MasterNet User’s Guide.
4. What Status Bits are set in the RTU Status MS?
VALUE (bit0) is set when the MP 200/1’s connection to the RTU is established. If you know the answers to the following questions, further analysis will be easier:
a. Are modems and cables installed as described in the ABB Master Installation Rules manual? Pay particular attention to the power supply and connection to signal ground.
b. How is your control system configured? A block diagram with all node and network numbers is useful. Note also the type of RTU/PLC, the master/active and slaves/passive on the link and the type of modem you are using.
c. Have you made any significant changes in your configuration (e.g., new communication board(s) added, new modems)?
d. Is it possible to repeat your problem?
e. Have you found any way to circumvent the problem?
f. Have you made any other observations related to the problem?
A test tool for monitoring the status of the V.24 leads is also useful for further analysis. The test tool shows the status, with LED indicators, of the modem signals, data transmission (TD) and reception (RD). When an analysis of the data flow is necessary, you need a Data Link Analyzer that monitors and stores the signals sent on the link.
General improvements of descriptions for application building.
The application building for RCOM/MVI in MasterPiece 200/1 and in Advant Controller 400 Series (AC 400) is similar. The User’s Guides for RCOM/MVI in AC 400 have better overview of the function, have figures describing the relationship between Siemens/MODBUS addresses and MVI-Data Set, includes more application examples etc. When you build your RCOM/MVI application in MP 200/1 it can be useful for you to look at examples an descriptions from the AC 400 User’s Guides for RCOM/ MVI. The following User’s Guides for Advant Controller 400 Series are available:
• Multi Vendor Interface Siemens 3964(R) Ord.No. 3BSE000535R0001
• Multi Vendor Interface MODBUS Ord.No. 3BSE000533R0001
• RCOM Ord.No. 3BSE000532R0001
[ref SR4043 VASMASOITA0811 ]
"Documentation error, MasterPiece 200/1 RCOM and MultiVendor Interface(MVI) Complement to description of fault tracing and DSCA 180 hardware" resolves the following:
- Documentation error, MasterPiece 200/1 RCOM and MultiVendor Interface(MVI) Complement to description of fault tracing and DSCA 180 hardware
PRODUCT CONCERNED
MasterPiece 200/1
MANUALS CONCERNED
• Multi Vendor Interface - Siemens 3964(R) Ord. no. 7650 111-221
• Multi Vendor Interface - MODBUS Ord. no. 7650 111-216
• Multi Vendor Interface - Allen-Bradley Ord.no. 3BSE000168R0001
• RCOM - Remote COMmunication Ord. no. 7650 111-215
CHAPTERS CONCERNED
Description of Hardware in Chapter 6.
Description of fault tracing in Chapter 7.
General improvements of descriptions for application building.
- Article imported from the previous version of KnowledgeBank
Asked 12 years ago
Answers
0
Cause: Article was imported from the previous version of KnowledgeBank Resolution:
Answered 12 years ago
Add new comment