Emerson 375 segment address

[Rob Wallace]

Hi, I did some training several years ago and learnt how when the 375 is connected to a segment it automatically takes on a specific address on the segment.
Can anyone advise me of the address number please.

Also if it can be changed within the 375???

Cheers
Rob

[CHRISC1024]

I don't remember the exact address but I believe it's in the 240 range. I don't believe you can change the defualt address it will go to but I'd have to atake one out and check. I'll see if I can pull one out and see what it says.

[jigish_jepal]

As per AN-013 (Application Note on Integrated and Visitor Host Interoperability) a visitor device like 375 shall use visitor node address in the range 252-255. Not sure whether it really takes address from this range or it can be decided manually.

Surpirsing neither 375 nor 475 appreas as registered products on foundation website under registered products. Any reason of not listing them?

[Bareld Bruining]

Hi, I did some training several years ago and learnt how when the 375 is connected to a segment it automatically takes on a specific address on the segment.
Can anyone advise me of the address number please.

Also if it can be changed within the 375???

Cheers
Rob


Hi Rob,

The hand held (or any other visitor on the network) will be connected on a temperarly address in the range of 248 - 255. You cannot change the address, one is selected for you automatically. If you look on the livelist on your 375 you will see which devices are attached (and have permanent addresses) and which visitors are connected (on one of the temperarly addresses)

Kind regards,

Bareld Bruining

[CHRISC1024]

I'm assuming they would not be a registered device as it is basically a piece of test equiptment and not an instrument. A 375 or 475 is used for set up and calibration of devices.

Just a thought.

[rezabejd]

I'm assuming they would not be a registered device as it is basically a piece of test equipment and not an instrument.

Actually, the Foundation has set up a class of "registered hosts" called "visitor host" and "bench host" (? I think). The profiles call out specific required & optional functionality, as well as functionality that's blocked (i.e., LAS function for a "visitor" host like a 375 / 475 on a live segment).

It doesn't appear any have been registered yet - looking here . . . (http://www.fieldbus.org/index.php?option=com_mtree&task=search&Itemid=324&ffbstatus=Registered&ffbmfg=&ffbcategory=Host)

[CHRISC1024]

Very interesting. Do you know when the Foundation set up visitor host? I was wondering if maybe it was something new and just not registered yet. I'll have to take a look and see if they have any devices registered under those classes? I believe registered hosts would be the control systems if I'm not mistaken.

I just checked on the Fieldbus website and there's no option in the pull down for a vistior host to see if one has been registered. Just becuse a device isn't registered doesn't mean it will not work on a Fieldbus network. I just checked and the Relcom units (FBT-3, FBT-6, ect) are not registered niether is the P&F ADM Kit. All units are acceptable test equiptment for checking a Fieldbus Segment. The Engineering Guidlines even talks about using the Relcom units for taking test readings for certification.

[rezabejd]

You are correct - none of the test equipment we've all been using are registered. It would be nice if they were - but registration is not free and I'm guessing companies like Relcom would rather not pass this cost on to their customers.

Technically, I don't think the ADM or FBT testers qualify in either category - I don't believe the host "sees" them or assigns an address, they are just listening and can't make any changes on the segment.

375's and 475's, on the other hand, can interact with devices, set addresses, maybe even be a link master (?) - not sure.

[jberge]

That's right. FBT and ADM are not hosts nor devices so they are not given any address. They are passive testers.

[jberge]

That's right. The visitor address is assigned to the handheld communicator automatically so you don't need to worry about addressing and timing conflicts etc. It is plug and play. Easy. Other bus protocols do not have this ability. The ability to connect a handheld or laptop to a running bus is pretty much unique to FF. FF was designed for process control - where from time to time you may need to connect a handheld in the field while the bus is running, for instance to do calibration. This is an important capability for field instrumentation. This is one of the reasons FF is the most popular bus for field devices. See more here:
http://www.eddl.org/SiteCollectionDocuments/wp_EDDL%20field.pdf

[jigish_jepal]

MTL's F809F, fieldbus diagnosis module, is a registered product !!!

http://www.fieldbus.org/index.php?option=com_mtree&task=viewlink&link_id=1340&ffbstatus=Registered&Itemid=324

[jigish_jepal]

Foundation's host registration is applicable for configuration tools, recording devices, alarm display panels, Human-Machines Interfaces (HMIs), or systems with a combination of functionality. Refer following link.

http://www.fieldbus.org/index.php?option=com_content&task=view&id=561&Itemid=440

Registration cost should not be hinderence. It is one time cost to be distributed over several hundereds/ thousands of devices. Per device cost may be negligible. Following/ complying to standards has numerous advantages.

[jcpilman]

>jigish_jepal wrote:
>Registration cost should not be hinderence.

Do you really know that? I suspect the per unit cost for host device registration is significant, especially when applied to a device that is otherwise under $800.

...John

[rezabejd]

MTL's F809F, fieldbus diagnosis module, is a registered product !!!
True, but it's not registered as a "host" so far as I can tell . . . from a June 2010 press release:
"In the FOUNDATION fieldbus automation infrastructure, host profiles are a key to system interoperability. They define required features for different classes of tested and registered hosts, including: Class 61 – Integrated Host, Class 62 – Visitor Host, Class 63 – Bench Host Non-Commissioned Device, and Class 64 – Bench Host Commissioned Off-Line Device."
The "visitor host" certification may be important to end users who want to use, for example, brand "Y" asset management software with brand "X" host system. Some end users with a preexisting HART-based asset management system will want to connect it to fieldbus devices on whichever host they end up choosing, rather than learn two different asset management systems.