Normally I will calibrate and Configured the FF Transmitter in the Lab Itself. Configuration such as Node address, Assigning Function bock and range assigning for the Transducer and Output block. After installation and Communicate to the DCS i want to assign one more Function block for activating second sensor for Temperature Transmitters. I have done the same method i used for calibration, but while assigning Function Block and changing Node address using 475 Communicator the communicator shows "the device was connect to a Host System so we don't have permission to change settings". Please provide solution for this Issue whether we can do in the DCS itself? if we can do in the DCS kindly provide Steps involve in DCS mapping for FF transmitters?

 

I could not enable a channel on an ISA100 wireless field transmitter until I had put the device into Out-of-Service mode (OOS). It would not accept the change while in operation.

It might be something similar for your FF situation.

 

Thank you for your reply bro

Yes I know while modify any block we need to put the block in OOS mode.

What i am telling means after the device was commissioned, when i go to the below mentioned steps in 475 communicatorz;
Fieldbus -> Online -> TT-XX-XXXX -> Advance -> Schedule

the schedule option was not open and the Node address can not be changed. It shows warning message "The device was connected to the Host system and changes cannot be made"

Because through the "Schedule" option only I can able to allot (by selecting the check box) the Function block AI1 AI2 AI3 and so on. and then i will modify the Function Block in OOS mode.

If I want to allot the Function Block in the "Schedule" option and to change the node address for a commissioned device means what can i do and how can i make the above mentioned changes.

I want to config in field only, not in the DCS side. If the host system (i.e. DCS) allows the field side to config what modification can I do in the DCS? Kindly Give Reply

 

Function block execution is managed by your DCS (or possibly in a field device acting as LAS [Link Active Scheduler]), the 475 Field Communicator does not have the ability to configure other host devices.

You will need to learn about your DCS and its specific configuration tools.

(The AI block in your TT device needs to be added to the schedule of function blocks to execute; the schedule resides in the DCS or LAS device.)

 

Thank you very much for your reply

Our DCS was Yokogawa.

If I can change the "LAS" from DCS to 475 communicator means we can able to allot the function block in the Schedule.
Is there any possible to change the same.

 

If you disconnected your DCS from the segment, the 475 could become the LAS, and you could add the TT device's AI block to the schedule in the 475, as you mentioned.

However, since you have not changed the schedule in the DCS, when you reconnect the DCS the new AI block will not be executed.

If you need to change the schedule in the Yokogawa DCS, you will need to use whatever tools Yokogawa supplied for that purpose.

 

I agree with Chris: device address, assignment of function blocks, tagging, and scheduling on a device on a running bus can only be done from the DCS. On a running bus a temporary visitor host such as 475 or other portable can only change parameter values. This is a protection mechanism so somebody in the field does not inadvertently trip the loop. Add the block from the DCS engineering software.

Cheers,
Jonas