0.

Flowchart

START

Confirm Device
Installation Condition

Confirm Builder
Setting

NO
Device_I Device_ NO Tag Assignment
D ID

Acquisiti of
on Device
OK?
OK? YES YES

Download to ALF Node NO Address

Address Assignment
of Dev.
OK?
YES

NO
Offline Device Device Class Setting
Download Class
to Device NO OK?
OK?
YES

YES
Device
Revision Update Capabiity
OK? NO / DD File

YES

Communi NO
ca-tion Troubleshooting
with
Device
OK?

YES

END

YOKOGAWA
File Name: Fieldbus Engineering
1. Foundation Field Bus Device Start-up Procedure
1.1. Preparation before downloading to FF Device
a) FCS Offline load to be done and FCS should run normally (at the beginning)
b) Cabling and Power supply for FF-Devices to be established.
c) Confirm the FF-Device location with TAG No and P&I
Device should be fixed at correct location
d) Collect the following information of FF-Device at field.
 Device_ID (unique number to each device provided by Manufacturer)
 Physical Device_TAG (PD Tag) (provided as part of FF I/O list specification)
 Node address (provided as part of FF I/O list specification)

1.2. Download to FF-Device

1.2.1. Confirm the setting data in [Fieldbus Builder] which is the same as specification
document of the Job (Figure 1.)
 Physical Device_TAG
 Node address
 Device class
Notes: Make sure DCS parameter is master.
Usually, DCS is master in many cases. If the device was set up by DMT before downloading
from DCS, please be careful.

Figure 1.　 Open Fieldbus Builder

1.2.2. Execute [Device Registration – Auto Registration] on [System View] – [Fieldbus Builder]
on Engg HIS. (Figure 2.) TAG of the actual device is same as builder setting; Device_ID
was set to [Fieldbus Builder] automatically. Device_ID is displayed on the builder as
green color (Figure 3.)

YOKOGAWA
File Name: Fieldbus Engineering
 Figure 2. Auto Registration

YOKOGAWA
File Name: Fieldbus Engineering
 Figure 3. Device ID acquisition 2

1.2.3. If Device ID was not set to [Fieldbus Builder], Confirm the information of actual device
by [ Device Panel] on [Tool].
(Device_ID, Device_TAG, and Node address) (Figure 4.)

YOKOGAWA
File Name: Fieldbus Engineering
 Figure 4. Device Panel

YOKOGAWA
File Name: Fieldbus Engineering
 Figure 4. Device Panel

1.2.4. If there is a mismatch setting between DCS and Device, correct the setting of device. If
the setting is wrong, the offline download can not be done. If the device setting is default
(Not assign the Device_TAG and Node address), the following assignment are surely
necessary.
 Device_TAG Assignment
On [Fieldbus Builder], execute [Tag Assignment] from [Advanced Function] menu. Or,
Execute [Tag Assignment] from [ Device Panel] after changing “Device_TAG” on the
window.
 Node address Assignment
On [Fieldbus Builder], execute [Address Assignment] from [Advanced Function] menu.
Or Execute [Address Assignment] from [Device Panel], after changing “Node address”
on the window.

<Procedure 1: Safety>
1) Open [Device Panel] and Execute [Update]
2) Change the Device_TAG and Node address of objective devices and execute [Tag
Assignment] and (or) [Address Assignment].
(Figure 5.)

YOKOGAWA
File Name: Fieldbus Engineering
 <Procedure 2: Be careful for the operation>
Notes: Don’t copy Device_ID to wrong device (same device model)
1) Input the correct setting of Device_TAG and Node address to [Fieldbus Builder].
2) Execute [Auto Registration]

1.2.5. Download (to ALF111)

The color of Device ID is changed from green to black.　(Figure 8.)

Copy & Paste

Figure 8. Download

1.2.6. Initial Download to Device

Execute [Master Data DownlLoad to Device] from [Fieldbus Builder]. (Figure 9.)
On this time, the conformation window of Downloading of Block parameter is
displayed.
<The case the DCS parameter is master>

YOKOGAWA
File Name: Fieldbus Engineering
 1) Download with Block parameter (Figure 10.)
2) Upload the parameter (from the device) (Figure 11.)
3) Download to ALF111 (Figure 8.)

<The case the Device parameter is master>

(The parameter was changed by DMT before downloading)
1) Download without Block parameter (Figure 10.)
2) Upload the parameter (from the device) (Figure 11.)
3) Since the difference between DCS and the device is displayed as “WARNING”,
correct the DCS parameter manually.
If the parameter is changed from [Edit Block Parameter] Dialog Box in
Fieldbus Builder (Figure 12.), the changed contents are not reflected in the
parameter of FF-Block in Drawing. Especially AI_Block parameter has to be
changed from FF-Block Detail in　Drawing builder. (Figure 13.)
4) Download to ALF111 (Figure 8.)
Re-Master Data Download to the device with Block parameter.

Figure 9. Master Data Download to Device

YOKOGAWA
File Name: Fieldbus Engineering
 Figure 10. Block Parameter Download

YOKOGAWA
File Name: Fieldbus Engineering
 Figure 11. Upload

YOKOGAWA
File Name: Fieldbus Engineering
 Figure 12. Edit Block Parameter

Figure 13. FF-Block Detail on Drawing Builder

YOKOGAWA
File Name: Fieldbus Engineering
 1.2.7. If the Master Data download was failed, there is the following possibility.
1) Wrong Device class
Execute [Device Class Setting] on [Advance Function] menu (Figure 14.)
* After changing the device class, the power off/on of the device is necessary.
* In case that the device model (specification) is no-LM type, the device setting can not
be changed, therefore the DCS setting should be changed as per the device setting.
2) Device revision
In case that there is the difference of device file revision between DCS and Device,
execute [Change Device Model/Type] and change to same device revision. (Figure
15.)
3) Re-Master Data Download to the device.

Notes 1: In case of EJA with LM function, since the default setting of device class is “LM”,
therefore if the device is used for “Basic”, [Device Class Setting] and power off/on
of device is necessary.
Notes 2: In case that [Change Device Model/Type] is carried out,
As FF faceplate block became “non assign condition”, after the offline load to device, the
execution of [Resolve Invalid Element] – [Project] – [System view] is necessary.
Until then, the status of FF faceplate is “CNF”. When the device is deleted and re-
created on [Fieldbus Builder], also [Resolve Invalid Element] is necessary.
(The online load of drawing which include the FF faceplate block has same effect as
[Resolve Invalid Element].) (Figure 16)
Notes 3: In case of the difference of device model, (i.e. Actual device is FVP, but the device
model in [Fieldbus Builder] setting is YVP.) the solution is that deleting and re-
assignment the device on [Fieldbus Builder].

YOKOGAWA
File Name: Fieldbus Engineering
 Figure 14. Device Class Setting

YOKOGAWA
File Name: Fieldbus Engineering
 Figure 15. Change Device Model/Type

YOKOGAWA
File Name: Fieldbus Engineering
 Figure 16. Resolve Invalid Element 1

1.2.8. Confirm the status of FF-block on DCS. (Figure 18)

When the communication is OK, the status of FF-block is “NR”
When the communication is NG, the status of FF-block is “CNF”

　 OK NG

Figure 18. FF-Block Status

YOKOGAWA
File Name: Fieldbus Engineering
2. Registration on PRM
2.1. Registration on PRM
2.1.1. Open [Network view] on PRM (Figure 19.)
2.1.2. Execute [Plug & Play]
If the communication between DCS and Device is normal, the non- registered devices is
displayed on [Status bar] with the indication of (Not Registered)
2.1.3. Execute [Plug & Play Register]
The non registered device which is displayed in [Status bar] is registered on PRM. The
indication of (Not Registered) is disappeared, and assigned to the spare folder in [Plant
view].
2.1.4. Execute [Read Device Detail]
The necessary information of registered device for the communication is read.

Figure 19. Registration on PRM

YOKOGAWA
File Name: Fieldbus Engineering
 2.2. Calibration by PRM
2.2.1. EJA
1) Open [Parameter] - [TRANSDUCE Block]
2) Select “Trim enable” on [TRIM_MODE] item　(Figure 20.)
3) Zero adjustment : Input “0” to [TRIM_PV_ZERO] and execute [Set] (Figure 21.)
4) If [EXT_ZERO_ENABLE] is “Enable”, Zero adjust is possible by volume of Device.
5) Span adjustment : Adjustment using optional 2 points is possible (Figure 22.)
[CAL_POINT_LO] (Zero side) [CAL_POINT_HI] (Span side)

Figure 20. TRIM MODE

YOKOGAWA
File Name: Fieldbus Engineering
 Figure 21. TRIM PV ZERO

Figure 22. Calibration

YOKOGAWA
File Name: Fieldbus Engineering
 2.2.2. YVP
1) Check the parameter of Valve setting as per the application.
2) Open [Parameter] - [A/O Block]
3) Select “O/S” on [MODE_BLK] item (from “CAS + Auto”) (Figure 23.)
4) Open [Parameter] - [TRANSDUCE Block]
5) Select “O/S” on [MODE_BLK] item (from “Auto”)
6) Execute “Travel calibration at stop point & Control parameter tuning” on
[AUTO_TUNE_EXEC] (Figure 24.)
7) When the data in [AUTO_TUNE_RESULT] is changed to “Succeeded”,
Tuning is finished. Confirm by [Update] (Figure 24.)
8) Input “MV data” in [COLLECTION_DIRECTORY] - [FINAL_VALUE] and confirm the
Valve action. (Figure 25.)
9) Return the setting of [MODE_BLK] to “CAS+Auto”

Figure 23. A/O Block MODE BLK

YOKOGAWA
File Name: Fieldbus Engineering
 6)

7)

Figure 24. AUTO TUNE EXEC

Figure 25. FINAL VALUE

YOKOGAWA
File Name: Fieldbus Engineering
 2.3. Loop Check (Simulation mode) by PRM
2.3.1. EJA
1) Display [RESOUCE_BLOCK] parameter and [Update]
2) Input “REMOTE LOOP TEST SWITCH” to [TEST_RW] – [Value 9] item
and [Set] (Figure 26.)
3) Display [AI_BLOCK] parameter
4) Select “Active” in [SIMULATE] – [ENABL DISABLE] and [Set] (Figure 27.)
5) Input the value for the test to [SIMULATE_VALUE] (Figure 27.)
6) After simulation is done, all parameters should be returned same as before.

Figure 26. REMOTE LOOP TEST SWITCH

YOKOGAWA
File Name: Fieldbus Engineering
 5)

4)

Figure 27. SIMULATE

3. NOTES
3.1. In case that [Device Recognition Registration] is used to register new device, the updating of the
correct revision of DD/Capability file is necessary and then [Offline load to Device] has to be
done.

3.2. If the device parameter is changed from PRM, “Upload” is necessary from Fieldbus builder on
HIS_ENG. Since the difference between DCS and the device is displayed as “WARNING”,
correct the DCS parameter manually. If the parameter is changed from [Edit Block Parameter]
Dialog Box Parameter Editor in Fieldbus Builder (Figure 12.), the changed contents are not
reflected in the parameter of FF-Block in Drawing. Especially AI_Block parameter has to be
changed from FF-Block parameter in 　 Drawing builder. (Figure 13.) And then execute
download to ALF111 to update the database in DCS.

YOKOGAWA
File Name: Fieldbus Engineering