03-16-2011 06:18 AM
I'm maintaining a FF system based on the Rockwell 1757-FFLDC. I've encountered a couple different problems lately where the feedback from various vendors has been to use NI-FBUS Configurator. Unfortunately they couldn't tell me if it would work with my FFLDC. Will it work over my Rockwell network? What will I if anything in addition to NI-FBUS Configurator?
03-17-2011 01:20 AM
Hi,
Only NI-FBUS Configurator 3.2 or earlier versions support 1757-FFLD ControlNet linking device. Please check which version you are using.
You will find an ControlNet device icon listed in NI-FBUS Interface Configuration Utility. After adding it, you can use Configurator access 1757-FFLD and its downstream field devices.
03-18-2011 06:09 AM
I'm not currently using NI Configurator at all. I was considering a purchase based on vendor recommendations. They are claiming that their products have parameters that are only accessible by NI Configurator.
03-20-2011 09:56 PM
Could you provide more information? Which parameters are only accessible by NI-FBUS Configurator? Which devices are you using?
NI-FBUS Configurator has stopped the support for 1757-FFLD since version 4.0. Using NI-FBUS interface devices (USB, PCI or PCMCIA) instead of ControlNet linking device to access the FF network may be an option for you.
03-22-2011 09:48 AM
The original information I had was secondhand and not completely correct. After some clarification one of the problems appears to be with a parameter "Maximum_Inactivity_To_Claim_LAS". The original source could see the parameter but he could not it change it. The parameter was set to "1" for our AUMA valve actuators and for example was set to "320" for a E+H PIT. Despite repeatedly being set as basic devices, these actuators have ended up back as Link Master devices. In theory this isn't a problem but it has been a problem for us.
The other issue was with a Rosemount 3095 Multivariable Transmitter (Mass Flow). According to Rosemount, the only way to access the parameters in the Mass Flow calcuation block is with NIFBUS Configurator. This could be based on the fact that the 475 Communicator can't access this information and NIFBUS Configurator is the only other thing he knows.
Honestly I've yet to confirm any of this but this guidance is coming from the respective vendors.
03-25-2011 12:34 AM
To switch between Link Master and Basic device, you can also try setting the parameter BOOT_OPERAT_FUNCTIONAL_CLASS in MIB block of the device.
BOOT_OPERAT_FUNCTIONAL_CLASS
1: Basic
2: Link Master
Set this parameter to 1 and restart, the device will boot to basic mode.
03-25-2011 05:52 AM
Thanks, I'll look into it.