Undocumented configuration parameters for FP2000

Question

I have been looking at the configuration of my FP2000 system, and there are settings that I cannot find discussed in the documentation. In the configuration box for the FP2000 itself, there is a parameter called "pause" that is in msec. What does this do? In the configuration of each of the modules, there is a parameter called "retry count". I have a pretty good idea of what this means, but I would like to see a detailed explanation so I can be sure that I am setting it properly. Can someone please tell me where these are discussed? I have looked through the online help with FieldPoint Explorer, and have read through the pdf manual of the FP2000 itself.
Rich

Answer 1

The Retry Count is a communications parameter, to get it's description (and the description of any paramter in FieldPoint Explorer), you can place the mouse cursor over the paramater and press F1. The description of Retry Count is: The number of times the FieldPoint server retries communication after an error with a FieldPoint device before it terminates a communication transaction.
The description for Pause is: Time to sleep for the bank between its data scan cycle. Set this value (1-1000) to give your embedded LabVIEW RT application more CPU time.
In a more detailed explanation: The Pause setting controls how long the IA Control Environment goes to "sleep". FP-20XX modules have two processes running in them at all times; the IA Control Environment an
d the LabVIEW Run-Time Engine. The processor has to share time/computation power between both processes. By changing the priority levels of VI's or by changing the pause parameter, you can control how much processor time is spent on the LabVIEW engine vs the IA Control Environement. By setting the pause parameter, you can have the IA Control Environemt put itself to sleep for periods of time. The IA Control Environment is the portion of the code that publishes FieldPoint data over the ethernet (e.g. making the FP-20XX publish data like a FP-1600 or FP-1601). By putting it to sleep for periods of time, it will delay reading I/O modules, writing to I/O modules (sent commands are not lost but are queued up waiting for the sleep period to end), and transmitting changed data values.
Regards,
Aaron