Excel displays our time stamp incorrectly.  If you were to open the data file in Notepad you would see the correct time format.  To correct the data in Excel, Highlight all of column A, right click on the highlighted region and select Format Cells.  Under the Number tab select Custom, Scroll to the bottom of the list that appears and select “m/d/yyyy h:mm”.  You will need to add “:ss.000” to the end of this, so it looks like this “m/d/yyyy h:mm:ss.000” .  Setting the cells to this will give you the highest resolution that Excel can show.

We use Universal Coordinated Time (UTC) to collect data on all of our devices.  There is no provision to set the time to a local time zone. 

The IEPE-Link™ -LXRS® accepts inputs from most IEPE sensors using the industry standard 10-32 mini-coaxial connector and 2.3 mA constant current excitation.

 

 

 

 

 

In Node Commander software, on the analog pairing screen, there is a check box for "Float". What is the function of this check box?

 

 

 

If the node is configured to send data to the base station in floating point mode, you need to enable this checkbox and set the 0-3 volt scaling.

 

The WSDA-RGD (with internal GX3 inertial sensor) is configured to produce the following messages on startup.

GPS Data (1 Hz):

  • UTC Time
  • LLH Position
  • NED Velocity

AHRS Data (100 Hz):

  • Euler Angles

From this output the WSDA logs:

GPS (1 Hz):

  • latitude
  • longitude
  • height above ellipsoid
  • height above MSL
  • horizontal accuracy
  • vertical accuracy
  • speed

AHRS (100 Hz):

  • roll
  • pitch
  • yaw

The WSDA-RGD does not log any data until it gets a valid time, if it is set to get time from GPS only it will not log any output from the GX3 until the UTC timestamp from the GX3 is valid, even though the GX3 is producing valid AHRS data.

This data is not user configurable and is not available as a live stream through LiveConnect.

As a general rule, you can calculate the battery life of a wireless node by dividing the amp hours of charge on the battery by the amps consumed during sampling.

Using the V-Link-LXRS as an example, we read in the data sheet (http://files.microstrain.com/V-Link_LXRS_datasheet.pdf) that the internal rechargeable battery has a nominal charge of 650 mAh (milliamp hours).  We next go to the V-Link-LXRS power profile (http://files.microstrain.com/V-Link-LXRS-Power-Profile.pdf) and we read that the V-Link-LXRS consumes 12.816 mA when sampling a 350 ohm strain gauge on 1 channel at 128 Hz.  By dividing 650 mAh by 12.816 mA, we find that the battery will last approximately 50 hours before needing recharge.

All LORD MicroStrain wireless sensor nodes, wireless base stations, and wireless sensor data aggregators are shipped from the factory with their radio frequency set to channel 15 (2.425 GHz).

This channel setting was established during 2012.

Previously all wireless products were set to channel 25 (2.475 GHz).

With the introduction of our LXRS radio technology, and its accompanying increase in radio strength and signal distance, the channel 25 radio frequency (2.475 GHz) and the channel 26 radio frequency (2.480 GHz) created harmonics on the edge of the Zigbee band that precludes their use.

All wireless products, both older and new, continue to support 14 channels running from channel 11 to channel 24.

 

 

 

All LORD MicroStrain wireless sensor nodes, wireless base stations, and wireless sensor data aggregators are shipped from the factory with their radio frequency set to channel 15 (2.425 GHz).

This channel setting was established during 2012.

Previously all wireless products were set to channel 25 (2.475 GHz).

With the introduction of our LXRS radio technology, and its accompanying increase in radio strength and signal distance, the channel 25 radio frequency (2.475 GHz) and the channel 26 radio frequency (2.480 GHz) created harmonics on the edge of the Zigbee band that precludes their use.

All wireless products, both older and new, continue to support 14 channels running from channel 11 to channel 24.

All LORD MicroStrain wireless sensor nodes, wireless base stations, and wireless sensor data aggregators are shipped from the factory with their radio frequency set to channel 15 (2.425 GHz).

This channel setting was established during 2012.

Previously all wireless products were set to channel 25 (2.475 GHz).

If you are mixing new nodes and base stations with older nodes and base stations, please be cognizant of these different channel settings.

The Node Discovery function of Node Commander will help you sort out which nodes are on what channels; Node Discovery is channel independent and allows the base station to communicate with any node, no matter what channel it is on

Sampling methods such as synchronized sampling, low duty cycle, network broadcast, etc. require that all nodes are on the same frequency so you will want to insure that you have adjusted the channels settings of the nodes to suit.

No.  Node Commander is a Windows software which requires a standard version of the XP Pro, Vista, Win 7 or Win 8 operating system.  Smart phones do not have these standard operating systems installed.

Node Commander is a Windows software which will operate on XP Pro, Vista, Win 7 and Win 8.  Any computing platform, whether desktop, laptop, tablet, etc. which supports these standard Windows OS can be used for Node Commander.

Yes.  Node Commander has a function that allows the user to drag and drop its CSV data files into SensorCloud.

 

To enable customers to try our standard products risk free, LORD MicroStrain® offers a 30 day return on the purchase of a starter kit. In order to take advantage of this offer, a purchase order or payment for the starter kit is required when the order is placed. 30 day trial details may be found at: http://www.microstrain.com/support/warranty

The G-Link-LXRS contains 3 accelerometers, one on each of the 3 axes.  A simple linear calibration (over a range of +/- 1g) is done at the factory and this slope (gain and offset) calibration is stored in the non-volatile memory (EEPROM) of the G-Link-LXRS.  The user can elect to use this calibration in conjunction with Node Commander software to measure acceleration, or the user can make their own calibration of the instrument.

In FINITE sampling, the user sets a total number of samples to be taken which equates to a time period.  Because the sampling rate per second is known, the user can adjust the number of samples to be taken to determine how long the sampling period will be.

In CONTINUOUS sampling, the user does not set the total number of samples and therefore does not set the time of the sampling period.  By selecting CONTINUOUS sampling, the user is instructing the system to sample data until the user manually stops the sampling (via software), the power is cycled, the on-board datalogging memory is full, the battery dies, the power fails, etc.

Not what you're looking for? Visit our FAQ page or contact our Sales team.