Installation and troubleshooting of

the Mulcom Tokuchu

1
YOKOGAWA
 Contents

 Mulcom Tokuchu
 Mulcom Tokuchu Checklist
 Sample SCS status and control graphic

2
YOKOGAWA
 Mulcom Tokuchu

 How it should work

 How to order
 Installation/ Configuration of HIS
 Installation/ Configuration of FCS
 Fault finding (check list)

3
YOKOGAWA
 How the Mulcom tokuchu operates
ENGHIS HIS HIS

*7 : %M3aaaa
dd.s1 *8 : %M3bbbb dd.s2 dd.s3
V-Net Monitoring

Monitoring
Monitoring

dd.s4 FCS dd.s5 FCS

SCSMON10 *2 : %WBgggg
_SFCPB

Fo
ra
p
S C ai r o
*1 : %WBdddd dd.s6*4 : %WBeeee dd.s7
x
S's f xx x
% S W yyy
*5 : W y
%S
*6 : *3 : %WBcccc SCS SCS
(Active) (Stand-By)
ProSafe-COM NT ProSafe-COM NT
HIS
LIST M-Bus/M-Net

Monitor FCS ProSafe-PLC ProSafe-PLC

4
YOKOGAWA
Mulcom Tokuchu ordering information
 Tokuchu is only needed in case of redundant use
of Mulcom
 For >= 2 operator HIS (optional for Eng HIS). It is
advised to install it on all HIS- and HIS/ENG stations.
 EXA OPC for HIS (LHS2411-S11/Z)
 Mulcom tokuchu (LHS9114-S11)
 Send mail to YEF-SCE PMK (Uehara) with request
 Specify:
# Mulcom pairs
 # HIS stations
 # ENG stations (optional)
 # EXAOPC stations (if applicable)
 Customer name
 Also Keycode and ID information is needed when order is placed
at P&L
 Delivery time can take up to 9 weeks

5
YOKOGAWA
 Installation/configuration of HIS 1/2
 “Administrator” user must exist and MUST have a password (XP)
(see IM 33Q01C10-01E >= Version 8)
 Use installation manual (LHSEM90-C11, =>R 6.01)

 Run <x>:\CS3000\his\users\Program\CreateFile.exe
 Values must be the same on all participating HIS stations
 Values are saved in <x>:\CS3000\his\users\save\BKUHz9114\Hz9114.tmp
 It is allowed to copy this file to the same location on other HIS stations

 Changes will only become active after a

RESTART of the HIS
 If the Tokuchu is not installed on all HIS/ENG stations then there are
restrictions to the use of the NON Tokuchu HIS/ENG stations:
 Do not use faceplates or graphics that directly access Mulcom
tags, since you may then refer to the non active Mulcom (write
actions ,e.g. MOS, can fail). Faceplates connected to FCS
blocks can be used safely (uses ADL).

6
YOKOGAWA
Installation/configuration of HIS 2/2
Vnet address Mulcom pair 1 Vnet address Mulcom
pair 2
Unique message number to
be send out by FCS d1 s1 Defined switches in FCS d1 s1 Mulcom A Mulcom B

7
YOKOGAWA
 Inst. and conf. of monitor FCS 1/12
 File SCSMON1015B.SVA on CD
 SFC block and SEQ table
 SCSMON10 :duplication check (monitor prg)
 SCSMON10-RUN :init for SCSMON10

 Delivered blocks
SCSMON10
SCSMON10
-RUN

ST16 _SFCPB

8
YOKOGAWA
 Inst. and conf. of monitor FCS 2/12
 Multiple Mulcom pair configuration example

 Copy and rename MON10 block for extra Mulcom pair

 SCSMON10-RUN serves SCSMON10 and SCSMON11
 Calc blocks unpack the status word from the Mulcom

9
YOKOGAWA
 Inst. and conf. of monitor FCS 3/12
! USED TO DECODE SYTEM INFORMATION FROM MULCOMS FOR
TOKUCHU REDUNDANCY DISPLAYS
alias SYSTEM_OK SYSTEM_OK_FGS.PV
alias VNET_OK VNET_OK_FGS.PV
alias PLC_OK PLC_OK_FGS.PV
alias MBS_OK MBS_OK_FGS.PV
alias EVENT_OK EVENT_OK_FGS.PV
P01 = RV & 32768 ! SYSTEM OK
P02 = RV & 16384 ! VNET_OK
P03 = RV & 8192 ! PLC_OK
P04 = RV & 4098 ! MBS_OK
P05 = RV & 2048 ! EVENT_OK
IF (P01 <> 0) THEN
SYSTEM_OK = 1
ELSE
SYSTEM_OK = 0
END IF
Calc information is used to IF (P02 <> 0) THEN
VNET_OK = 1
build the Mulcom switch ELSE
VNET_OK = 0
graphic END IF
IF (P03 <> 0) THEN
PLC_OK = 1
ELSE
PLC_OK = 0
END IF
Remark: IF (P04 <> 0) THEN
"SYS_STATUS_F“ Is defined in the Mulcom tag file as MBS_OK = 1
ELSE
a PV, but in the HIS (TFDATA list) it must be defined as
MBS_OK = 0
a PVU16 END IF
IF (P05 <> 0) THEN
EVENT_OK = 1
ELSE
EVENT_OK = 0
Mulcom TAG file END IF

"SYS_STATUS_F" , "", (SYS, 11, 0, 4) (Y,N,B ,N), R 4(N,0) , WB 0001 01 PV (N,0,N , , , , , 0),;
"EVT_STATUS" , "", (SYS, 12, 0, 1) (Y,N,B ,N), R 15(N,0) , WB 0001 04 PV (N,0,N , , , , , 0),;
"RED_STATUS" , "", (SYS, 23, 0, 0) (Y,N,B ,N), R 16(N,0) , WB 0001 05 PV (N,0,N , , , , , 0),;
"MBU_STATUS" , "", (SYS, 14, 0, 0) (Y,N,B ,N), R 34(N,0) , WB 0001 03 PV (N,0,N , , , , , 0),;
"VNET_STATUS" , "", (SYS, 15, 0, 0) (Y,N,B ,N), R 100(N,0) , WB 0001 02 PV (N,0,N , , , , , 0),;

10
YOKOGAWA
 Inst. and conf. of monitor FCS 4/12
 Overview of SFC in SCSMON10
01 Initialize Tuning parameters
SCSMON10
for JOB
_SFCPB
02 Monitor

11
YOKOGAWA
 Inst. and conf. of monitor FCS 5/12
 Tuning parameters
**********************************************************************
* ***
* Definition section (Communication Parametar ,etc) ***
**********************************************************************
******* SCS system tag definition (Depend on SCS configuration)*******
*** This section must be mach with SCS configuration ***
*** USE SYSTEM TAG NUMBER(%WBxxxxxxSxxxx)!! : Not Use TAG Name ***
** SCS1 Status & Control Command **
#define S1HLTHY"%WB000101S0132" !SCS1 SYSTEM STATUS(:Read)1
#define S1SCTRL"%WB000201S0132" !SCS1 SYSTEM STATE (Control Command)

** SCS2 Status & Control Command **

#define S2HLTHY"%WB000101S0133" !SCS2 SYSTEM STATUS(:Read)
#define S2SCTRL"%WB000201S0133" !SCS2 SYSTEM STATE (Control Command)

******* FCS tag/message definition (For HIS Software) *******

*** This section must be mach with HIS software configuration ***
** SCS Active Flag **
#define SCS1STTS "SCS32ACT" !SCS1 Active Flag Tag name(:Read)
#define SCS2STTS "SCS33ACT" !SCS2 Active Flag Tag name(:Read)

** Changeover Request Assignment **

#define MSGSCS1 3 !Changeover request %M3 message Number(SCS1)
#define MSGSCS2 4 !Changeover request %M3 message Number(SCS2)

******* Display String (SCSMON -SFC Block Tag Name- Display Char.) ***
** for [MONITOR MODE] **
#define STRAUTO"AUTO" !AUTO
#define STRSCS1"SCS32(Manual)" !SCS1(Manual Select)
#define STRSCS2"SCS33(Manual)" !SCS2(Manual Select)
** for [ACTIVE SCS ] **
#define ACTNONE"None" !Active SCS is None
#define ACTSCS1"SCS32" !SCS1 Active
#define ACTSCS2"SCS33" !SCS2 Active

12
YOKOGAWA
 Inst. and conf. of monitor FCS 6/12
Source/destination of Tuning parameters

%WB000101S0132
%WB000201S0132

%WB000101S0133
%WB000201S0133

 Source: Mulcom Tag File

"SYS_STATUS_F" , "", (SYS, 11, 0, 4) (Y,N,B ,N), R 4(N,0) , WB 0001 01 PV (N,0,N , , , , , 0),;
"SYS_STATE" , "", (SYS, 11, 0, 5) (N,N,U16,N), R 5(N,0) , WB 0002 01 PVU16 (N,0,N , , , , , 0),;

13
YOKOGAWA
 Inst. and conf. of monitor FCS 7/12
Source/destination of Tuning parameters
SCS32ACT
SCS33ACT
 Source: Common Switch Builder

14
YOKOGAWA
 Inst. and conf. of monitor FCS 8/12
Source/destination of Tuning parameters
SCS32ACT
SCS33ACT
 Source: Common Switch Builder

15
YOKOGAWA
 Inst. and conf. of monitor FCS 9/12
Source/destination of Tuning parameters
3
4

 Destination: CreateFile message number in HIS

16
YOKOGAWA
 Inst. and conf. of monitor FCS 10/12
Source/destination of Tuning parameters
SCS32
SCS33
 Destination:
Switch Graphic
SCSMON10 TUN

17
YOKOGAWA
 Inst. and conf. of monitor FCS 11/12
Patching ADL retry counter in user defined libraries

ADL retry counters must be increased to 7. The standard FCS skeleton files
are patched when the MULCOM redundancy package is installed on the
ENG/HIS station. But user defined FCS libraries must be separately patched
using the following procedure:

1. Call MSDOS command prompt.

2. Go to the correct directory; C:\> cd CS3000\his\users\program

3. Execute the command to patch the ADL counter:

adlcnt <full path and filename> <countervalue>

Example:
C:\> adlcnt C:\CS3000\eng\BKSystem\data\FCS\Skelton\UserDef.l 7
Or
C:\> adlcnt C:\CS3000\eng\BKproject\projname\FCSxxx\Skelton\SFdata.L 7

18
YOKOGAWA
 Inst. and conf. of monitor FCS 12/12
Define Participating HIS stations

Select properties
of EACH FCS
Offline download
needed

19
YOKOGAWA
 Mulcom Tokuchu Test
 Make system healthy
 Both Mulcoms available
 At least 2 HIS stations active
 At least Monitor FCS active
 Activate Switch Graphic
 Activate Mulcom tag Faceplate (V-NET_STN_ADR)
 Switch manually to Mulcom A (if applicable)
 Check for correct number in Faceplate
 Switch manually to Mulcom B
 Check for correct number in Faceplate

 Switch off Mulcom A

 Check for correct number in Faceplate
 If faceplate shows ******* after a while then perform
check
20
YOKOGAWA
Mulcom Tokuchu Checklist 1/11
 On each HIS hosting Mulcom Tokuchu
 Check Administrator password availability
 Check the installed products
 Check the processes with the task manager
 Check the CreateFile properties
 Check the contents of
<x>:\CS3000\HIS\Spconf\UNLoadlist.txt
 Note down HIS station names hosting MulcomTokuchu
 Check the data list of Mulcom stations for PVU16 setting of
“SYS_STATUS”

 On the ENG (HIS) station

 For all FCS systems: Check the “taglist reference station”
list in its properties
 For the Monitor FCS: Check the SCSMON10 settings

21
YOKOGAWA
 Mulcom Tokuchu Checklist 2/11
Administrator password availability (XP)
 Log in with Administrator rights
 Start the Control Panel
 Set it to Classic view
 Restart the PC
 Start the Control Panel
 Start User Accounts
 Check if the Administrator is password protected

22
YOKOGAWA
 Mulcom Tokuchu Checklist 3/11
Check the installed products

 Check for presence of:

 LHS2411-S11 (OPC for HIS)
 LHS9114-S11 (Mulcom Tokuchu)

23
YOKOGAWA
 Mulcom Tokuchu Checklist 4/11
Check the processes with the task manager
 Check for presence of:
 BKHOPC.exe
 BKUHZC9114_001.exe
 BKUHZP0004.exe
These processes must be running
continually; if they show up and
disappear for a few seconds it is also not
OK!
 If this problem occurs you will probably also
get an error message in the System Alarm
overview that process BKUHZP0004.exe was
aborted with error 20001521. This error
means that the OPC server on the HIS is not
(correctly) installed.
This has usually to do with an incorrect
login/password combination for the HIS OPC
server of the process that launches the HIS
OPC server.
See next page for details.

24
YOKOGAWA
 Mulcom Tokuchu Checklist 5/11
Check the BK Bossd and OPC login/password
 First check/change the BK Bossd service login/password combination:
 Open the Services window (Right-click My Computer, Manage, Services
and Application, Services).
 Double-click entry BK bossd and the Log on tab.
 The login and password must be both CENTUM (capitals!). The login may be
preceded by other information, do not change that part. Retype the
passwords to be sure.
 Then check/change the HIS OPC DCOM settings:
 Activate dcomcnfg from Start, Run.
 Select the YOKOGAWA CSHIS OPC Server properties. On Windows 2000
you directly see a list of COM object and you can double-click the entry. On
Windows XP you must open an entire tree: Component Services,
Computers, My Computer, COM Config.
Right-click entry YOKOGAWA CSHIS OPC Server and select Properties.
 Now open tab Identity. There you must again find under
This User login and password CENTUM (capitals!).
The login may be preceded by a computer or domain name; do not change
that name. Retype the passwords to be sure.
 Restart the HIS and verify that BKHOPC.exe, BKUHZC9114_001.exe and
BKUHZP0004.exe are now running.

25
YOKOGAWA
 Mulcom Tokuchu Checklist 6/11
Check the CreateFile properties
 Same value for all Participating HIS stations Vnet adr Mulcom pair 1 Vnet adr Mulcom pair 2
Unique message number to be
send out by FCS d1 s1 Defined switches in FCS d1 s1 Mulcom A Mulcom B

26
YOKOGAWA
Mulcom Tokuchu Checklist 7/11
Check the contents of
D:\CS3000\HIS\Spconf\UNLoadlist.txt

27
YOKOGAWA
 Mulcom Tokuchu Checklist 8/11
Check the “taglist reference station” on ENG HIS
For EACH FCS
 Right click Monitor FCS
 Select properties
 Select Constant 2 Tab

Offline
download
needed
(if changed)

28
YOKOGAWA
 Mulcom Tokuchu Checklist 9/11
Check Switch settings against CreateFile settings
Switch Builder

CreateFile

SCSMON10 settings
******* FCS tag/message definition (For HIS Software) *******
*** This section must be mach with HIS software configuration ***
** SCS Active Flag **
#define SCS1STTS "SCS32ACT" !SCS1 Active Flag Tag name(:Read)
#define SCS2STTS "SCS33ACT" !SCS2 Active Flag Tag name(:Read)

** Changeover Request Assignment **

#define MSGSCS1 3 !Changeover request %M3 message Number(SCS1)
#define MSGSCS2 4 !Changeover request %M3 message Number(SCS2)

29
YOKOGAWA
 Mulcom Tokuchu Checklist 10/11
Check CreateFile settings against SCSMON10 settings
CreateFile

SCSMON10 settings
******* SCS system tag definition (Depend on SCS configuration)*******
*** This section must be mach with SCS configuration ***
*** USE SYSTEM TAG NUMBER(%WBxxxxxxSxxxx)!! : Not Use TAG Name ***
** SCS1 Status & Control Command **
#define S1HLTHY "%WB000101S0132" !SCS1 SYSTEM STATUS(:Read)1
#define S1SCTRL "%WB000201S0132" !SCS1 SYSTEM STATE (Control Command)

** SCS2 Status & Control Command **

#define S2HLTHY "%WB000101S0133" !SCS2 SYSTEM STATUS(:Read)
#define S2SCTRL "%WB000201S0133" !SCS2 SYSTEM STATE (Control Command)

Mulcom TAG file Mulcom V-net addresses

"SYS_STATUS_F" , "", (SYS, 11, 0, 4) (Y,N,B ,N), R 4(N,0) , WB 0001 01 PV (N,0,N , , , , , 0),;
"SYS_STATE" , "", (SYS, 11, 0, 5) (N,N,U16,N), R 5(N,0) , WB 0002 01 PVU16 (N,0,N , , , , , 0),;

30
YOKOGAWA
 Mulcom Tokuchu Checklist 11/11
Check CreateFile settings against SCSMON10 settings

SCSMON10 settings
******* Display String (SCSMON -SFC Block Tag Name- Display Char.) ***
** for [MONITOR MODE] **
#define STRAUTO "AUTO" !AUTO
#define STRSCS1 "SCS32(Manual)" !SCS1(Manual Select)
#define STRSCS2 "SCS33(Manual)" !SCS2(Manual Select)
** for [ACTIVE SCS ] **
#define ACTNONE "None" !Active SCS is None
#define ACTSCS1 "SCS32" !SCS1 Active
#define ACTSCS2 "SCS33" !SCS2 Active

31
YOKOGAWA
Sample SCS status and control graphic

32
YOKOGAWA