FOUNDATION Fieldbus

cancel
Showing results for 
Search instead for 
Did you mean: 

FBUS-HSE/H1 Blinking Module Status Light and No Connection with NI-FBUS Configurator

I have an FBUS-HSE/H1 Linking Device connected to our network with H1 devices attached with conditioned power. When the device powers up, the Power Light turns on and then the Ethernet Link Light.  The Module Status Light comes on Green for a moment and then as the RX Light starts to blink the Module Status Light starts blinking Green.  When I load the Interface Configuration Utility I receive an annunciation from the Linking Device, am able to set the PD Tag.  When I load the Communication Manager it fails to receive any information about the segments.  I have performed the reset on the Linking Device and see that the PD Tag has been reset.  I enter a new PD Tag and try to load the Communications Manager but I still have the same problem.  From the User Manual for the Linking Device (370738a.pdf)  its states that when the Model Status Light is blinking Green, it is in a Standby State.  The manual then states that a Standby State means the Linking Device has completed all the self tests and is ready to operate but can't because no "Active Ethernet Segment" is configured.  I guess I dont understand why this is so, since we are receiving annunciations from the Linking Device. We have had this same problem with another FBUS-HSE/H1 Linking Device and have never been able to get them to operate.

0 Kudos
Message 1 of 4
(7,459 Views)
Hello,

Before the Communications Manager (CM) successfully start the Enet and HSE Linking Device interface, the FBUS-HSE/H1 LD will always stay in the "Standby" status as long as there is no error (if some error happens, the Module Status LED will have different behavior).

I would like to suggest you that:
1. Run Interface Configuration Utility, add an Enet interface only (please don't add HSE/H1 LD now);
2. Run CM and NI-FBUS Configurator; if CM can start up successfully, create a project with the "Enet" interface in the NI-FBUS Configurator. The linking device should show up under the "Enet" link successfully; if not, please take a screen shot;
3. Close both the NI-FBUS Configurator and the CM;
4. Add the HSE/H1 LD interface in Interface Configuration Utility; launch CM and Configurator again and see what happens.

And would you please let me know some details?
1. What's the software version?
2. When the error happens, which interfaces (PCI, PCMCIA, Enet, HSE/H1 LD, etc) have been added by Interface Configuration Utility?
3. What are the settings for the Enet and HSE/H1 LD interfaces and their ports within Interface Configuration Utility? Screen shot?
4. What error message has CM reported?

It could be better and more helpful if I could get you to send me the details with screen shots (for both Interface Configuration Utility and CM), thank you!
0 Kudos
Message 2 of 4
(7,450 Views)
I am currently running NI-FBUS Configurator Version 3.1.1.4054.  The device connected to the Linking Device is a Emerson Rosemount 3095, I have the newest DDs loaded on my laptop.  I have gone through the steps that you gave in your post and have taken screen shots as I went.

First I added just the Ethernet connection



When I started NI Configurator the standard message about the need to open Connection Manager opened and I clicked OK to start it.  It loaded correctly and minimizes itself.



When configurator loads, the only connection available is through the Ethernet.



Once the connection is established, all of the Linking Devices connected to our network show up.  The one circled in red is the FBUS-HSE/H1 device.  After 5 mins the device is still showing up as trying to connect.  I notice that the Transmit Light never blinks except for the occational Sm Identify Annunciation.  The Receive Light blinks a lot however.



I then shutdown everything and load up the Interface Configurator Utility again.  This time I add the HSE/H1 Linking Device to the set of connections.  All of the connection parameters are the defaults, no values are changed from what is received from the device.









All of this information is received when the Interface Manager receives an annunciation from the Linking Device.  At this point there is just the Ethernet Interface and the HSE/H1 Interface for the FBUS-HSE/H1 Linking Device.  The rest of our Linking Devices are not added at this time.  When I load up the Connection Manager I get the following error after it waits on the "Initializing" stage.  I never get to the step where its initializing the two segments on the Linking Device.




I have been using the NI Tools for connection to a Rosemount 3420 without any problems.  We have contacted NI's Fieldbus people and even had another FBUS-HSE/H1 device sent to us.  We have never been able to get NI Tools to work with these Linking Devices.  Hope this information helps, thanks.
0 Kudos
Message 3 of 4
(7,441 Views)
Thank you very much for the detailed information!

Would you please have some additional checks?
1. We strongly recommend you to put the FBUS-HSE/H1 linking device in the same sub-net with your computer. From the pictures above, there are at least 2 sub-nets in your network.
2. Please close all the other HSE utilities (Interface Configuration Utility, HSE/H1 LD firmware upgrade utility, etc.) in the same Ethernet; for example, Interface Configuration Utility and Communications Manager use the same UDP port to detect the HSE LD; running the 2 programs at the same time might lead to a broadcast disturbance;
3. Power-off the HSE/H1 LD; close the CM; wait for more than 30 seconds. This operation will clear all the possible existing sessions between the hardware the the CM software;
4. Power-on the HSE/H1 LD and then lanch CM.

Please let me know if there is still problem. Thank you for your patiance!
0 Kudos
Message 4 of 4
(7,435 Views)