User manual

Table Of Contents
<6> Deploy Profiler
This option provides the interface for programming the deployment. The deployment
parameters are stored in EEPROM (and on the flash card in non-volatile storage) and loaded at
firmware startup. The parameters also reside in RAM and will be unchanged if the battery
remains connected. When ‘Deploy Profiler’ is selected, the firmware completes a firmware
initialization and then displays settings that define the MMP profiling behavior.
Initialization
During deployment initialization the firmware does the following:
Step 1 Checks for successful firmware initialization.
Step 2 Prompts to set the RTC (real-time clock).
Step 3 Displays the profiling history for informational purposes.
Step 4 Verifies CTD and ACM settings (automatic, manual, or skip).
Automatic sensor verification confirms that the standard CTD and ACM settings have
been programmed into the sensor EEPROMs. This sensor “roll call” detects whether the
configured CTD and ACM are installed, and changes the configuration if a different sensor is
found. During roll call, if the configured CTD or ACM is not found but an alternate is found, the
firmware reconfigures the settings based on the detected sensor. If a configuration change is
made, the firmware prompts the operator to re-run sensor verification. If no CTD or ACM is
found or if the detected sensor matches the Configuration, the system makes no Configuration
change. If a sensor problem is detected, a warning will be displayed and the firmware will
terminate the deployment.
Manual sensor verification establishes pass-through communications channels to the
sensors, allowing the operator to verify (and change), the CTD and ACM settings.
NOTE
The MMP offload utility and the Unpacker work only with binary files created using standard
sensor settings. Also, some combinations of non-standard settings can inhibit data collection
during a deployment. Contact McLane before attempting to use non-standard sensor settings.
7-37