Related Products:

EMMK-101, EMMK-102, EMMK-103

Related Documents:

ISCM-0380, ISCM-0385

Type:

Operation

Keywords/Labels:

device configuration settings, quarantined endpoints, data units, device software, device hardware, software packages

Summary:

The article describes the procedures involved with modifying device communication and configuration including adding or removing data units, updating device software and hardware, uploading or removing software packages, and resetting to factory default settings.

Changing Device Configuration Settings

Configure device settings, such as endpoint mappings, data groups, channel mappings, sample rate, and hardware configuration.

  1. Click Configuration (noloc_env_config.png) and select Devices.

  2. Double-click a device to open its configuration page.

  3. Configure the settings you want to modify using the tabs in this device's configuration page.

    Mapping Device Channels and Data Groups

    Map each sensor to a device channel and put all sensors for one asset into a data group for which you can configure data collection behaviors.

    Creating and Configuring Data Sources

    Configure a data source from external sources, such as a Modbus Register, an OPC UA Tag, or a Historian Input.

    Device Property Configurations

    Learn how you can fine-tune file transfer and network performance for wireless and CMS devices.

    Updating a Device's Hardware Configuration

    Update your device's configuration in the web application, including the placement of modules within chassis slots, to match the physical device.

  4. Click Back to Devices.

  5. Select the device you updated and click Update Configuration to apply the changes.

Reintegrating Quarantined Endpoints

Re-establish communication with an endpoint without rebooting the MON-10496.

When an endpoint fails to communicate 5 times, the MON-10496 quarantines the endpoint, or ceases to attempt communication with the endpoint. Until you correct the cause of failure and re-establish communication, data is not collected from the quarantined endpoint.

Common reasons an endpoint fails to communicate:

  • The battery needs to be changed.

  • There is a significant obstruction between the endpoint and the MON-10496.

  1. On the main Dashboard, click Wireless to access the Wireless Dashboard.

  2. Select the quarantined endpoint.

  3. Click the Action menu (noloc_env_action.png) and select Clear Quarantine.

  4. Confirm that the endpoint's status changes and that communication with the endpoint has been re-established.

    Note

    It may take several minutes for the endpoint status to update. The MON-10496 to communicate with endpoints 5 times every 15 minutes before quarantining unresponsive endpoints again.

quarantines

Adding or Removing Units of Data

Allow or restrict specific units for channels with a certain measurement type.

The default setting for units in the web application is imperial. Refer to Changing Measurement Type Units to Metric to switch from imperial to metric.

Note

Each sensor type can have one or more allowed units. The units you allow for a sensor type also determines in what units InsightCM calculates features.

  1. Click the Navigation menu (noloc_env_navmenu.png) and select System > Units.

  2. Select a sensor type.

  3. Click Add Unit or Remove Unit to specify what units each sensor type can use.

Supported Units

See the imperial and metric units for each measurement type.

Measurement Type

Imperial

Metric

Acceleration

g

m/s2

Current

amp

amp

Displacement

mil, volt, in

m, mm, micron

EMSA

uV

uV

Resistance

ohm

ohm

Speed

RPM

RPM

Temperature

F

C

Velocity

ips

m/s, mm/s

Voltage

volt

volt

Changing Measurement Type Units to Metric

Change the measurement type units to metric.

Complete the following steps to switch to metric units.

  1. Open a command prompt on the server machine and change to the following directory:

    <Install Drive>:\Program Files\Cutsforth\InsightCM\
  2. Run the following command:

    InsightCMConsole.exe importdefinition -t unit -f C:\ProgramData\Cutsforth\
    InsightCM\Definitions\UnitDefinitions\MetricUnits.json
  3. Check that the command prompt reports "Success:".

  4. Run the following command:

    InsightCMConsole.exe exportdefinition -t asset -n <sensor name> 
    -o <full path to output definition file>
  5. Open the definition file using a text editor.

  6. Find the property definition where the key value is Unit and change the value of DefaultValue to the appropriate metric unit.

  7. Save the file and run the following command:

    InsightCMConsole.exe importdefinition -t asset -f "<fullpath to definition file>
  8. Repeat steps 4 through 7 for each sensor definition you want to update.

Updating Device Software

Review the application types and versions running on each device and update the application and firmware that the device runs.

  1. Click Configuration (noloc_env_config.png) and select Devices.

  2. Click the Software tab and select one or more online devices.

    Note

    The devices you select must be of the same type.

  3. Depending on your updating goal, complete one of the following steps.

    Update the application on one or more devices to the latest version on InsightCM.

    Click Update Application.

    Note

    • This operation requires devices to reboot and might take several minutes to complete.

    • The web application does not allow you to update applications for devices with a disabled connection status.

    Verify the latest application is running on a device.

    Compare the Configured Version and Latest Version columns in the device table to see if a more recent application version is available on the server.

    Resolve persistent errors with the device operation. This step should only be taken with a recommendation from Cutsforth, as there may be solutions other than formatting the device.

    Click the Action menu (noloc_env_action.png) and select Format Device.

Upgrading Device Hardware

Upgrade your device hardware in InsightCM to match the device types that you have while keeping existing asset mappings intact.

  1. Click Configuration (noloc_env_config.png) and select Devices.

  2. Select a device and click Edit.

  3. Select the Hardware tab and click Upgrade Hardware.

  4. Specify which device type you are upgrading to using the pull-down and click OK.

    Note

    Since this action cannot be undone, ensure that you are upgrading the correct device before confirming the change.

    The changes are applied automatically.

  5. If the IP address of your upgraded device has also changed, click Edit Hardware to update that information.

Uploading or Removing Software Packages

Update the system image on your monitoring devices by uploading the new image versions to InsightCM and deploying the image to your devices.

Before you begin, download the version of the device image you wish to deploy.

To add or remove firmware versions from InsightCM, complete the following steps.

  1. In InsightCM, click the Navigation menu (noloc_env_navmenu.png) and select Utilities > Package Management.

  2. Click Upload, select the system image you wish to deploy to your devices, and click Open.

  3. Select the outdated image(s) and click Remove.

  4. Click Configuration (noloc_env_navmenu.png) and select Devices to navigate to the Device Configuration page.

  5. Select the Software tab.

  6. Select one or more devices of the same toolkit and type.

  7. Click Update Application to apply the new image.

    Note

    To update the firmware for your devices, click the Action menu (noloc_env_action.png) and select Update Firmware.

  8. Verify that the Deployment Status updates to Successful.

What Happens to Files When You Update Device Applications

When you update applications on a device, the device deletes log files (including the tracelog) and configuration files.

To manually retrieve any type of file from the device disk, Cutsforth recommends using WebDAV, a protocol that enables you to securely manipulate files on your target, to retrieve files. Files on the device are located at /home/lvuser/natinst/LabVIEW Data/InsightCM.

Note

For information about configuring WebDAV on a host computer and transferring files from the device, visit ni.com/info and enter the Info Code WebDAVTransfer to access the Cutsforth support document Using WebDAV to Transfer Files to Your Real-Time Target.

Review Detailed Device Information

Review a summary of device information from the most recently acquired sensor data.

Device Dashboard page.png
  1. Click the Configuration pull-down (noloc_env_config.png) and select Devices.

  2. Watch data update while the device performs an acquisition, reboots, or you test its connection using the Action menu (noloc_env_action.png).

  3. Click the View menu (noloc_env_viewmenu.png) to navigate to the Device Configuration page and update settings in a device's configuration.

    Note

    The Features table updates only when data is available from a channel whose status is okay.

  4. Click the View menu (noloc_env_viewmenu.png) to navigate to the Device Health Dashboard page and evaluate the health of a device by viewing statistical data, including graphs of available memory, CPU usage, drive space, and the response time to pings, over a configurable time range.

Device Property Configurations

You can fine-tune file transfer and network performance for wireless and CMS devices using the following features.

Burst Mode - A mode that you can configure on a device to enable the manual or scheduled acquisition of high-resolution data.

Sample Rate - You can configure the sample rate for channels on Cutsforth 923x modules only. Devices always sample from static channels on other module types at 1 Hz and for one second. For more information, refer to Frequently Asked Questions about Sample Rates and Durations .

Time Trigger Offset - An amount of time, in seconds, to delay time-based acquisitions. For example, if a device is configured to perform an acquisition daily at 1:00 PM, and the value of this property is 110 seconds, the device waits until 1:01:50 PM to perform the acquisition. This property is useful for spreading out network traffic when many devices are configured to perform acquisitions at a specific time of day.

Burst ModeSample RateTime Trigger Offset

FAQs on Sample Rates and Durations

Q:

At what sample rate do devices acquire data?

A:

You can configure the sample rate for waveform channels on dynamic modules, such as the Cutsforth 9232, on the Device Configuration page by double-clicking on a device and selecting the Device Properties tab. However, devices always sample from channels that produce single-point values, such as voltage and temperature, at 1 Hz. If a device contains both types of channels, the device samples them at different rates.

Q:

Can you configure unique sample rates or acquisition durations for each channel?

A:

No:

  • All waveform channels on a device share the same configurable sample rate.

  • All single-point channels are sampled at 1 Hz.

If you must sample from two nearby sensors at different rates, consider using two different devices, each with a unique sample rate.

Q:

How do devices log single-point data during a multi-second acquisition?

A:

When a device contains both waveform and single-point channels, you configure the duration of acquisitions on the Operating States tab of the Asset Configuration page for the equipment the device is monitoring. However, devices always log only the final value from single-point channels. Consider the following example where a device acquires from one waveform channel and one single-point channel for four seconds.

loc_eps_diffs_basic.gif
callout_1.gif

The full, four-second acquisition. The device logs waveform data throughout the acquisition.

callout_2.gif

The temperature value from the final second. This is the only temperature value the device logs from this acquisition.

MCSA Device Properties

The Device Properties tab contains a table of properties of the device sample rate and the minimum and maximum current RMS value for the device to calculate all the configured Motor (MCSA) asset features.

The following are built-in properties:

  • Sample Rate—The sample rate is fixed at 5,000 Hz

  • Minimum Working Current (%FLA)—The minimum current RMS value of a motor for the device to calculate all the configured features (except Percent Full Load Amps) that belong to the Motor channel, as a percentage of the motor Full Load Amps. The default is 25%.

  • Maximum Working Current (%FLA)—The maximum current RMS value of a motor for the device to calculate all the configured features (except Percent Full Load Amps) that belong to the Motor channel, as a percentage of the motor Full Load Amps. The default is 200%.

If the instantaneous current RMS of a motor is below Minimum Working Current or above Maximum Working Current, the device only calculates the Percent Full Load Amps feature. The Rotor Bar Sideband feature returns a -100 dB value and other non-calculated features return a zero value.

Resetting a Device to Factory Settings

Reset a device to its original application image.

  1. Click the Configuration pull-down (noloc_env_config.png) and select Devices.

  2. Select the Software tab.

  3. Select a device.

  4. Select the Action menu (noloc_env_action.png) and select Reset to Factory Default.

Do you need more help?

quarantinesBurst ModeSample RateTime Trigger Offset
Was this article helpful?
0 out of 0 found this helpful