Contact & Support
Yes. The ENV-Link-Mini provides support for wind speed and wind direction indicators.
An example of instruments that have been proven are:
Wind Direction: http://inspeed.com/wind_speed_direction/e-Vane_2.asp
There is no self-test function on the WSDA-Base-101 Analog Base Station to test the analog outputs.
However, each channel can be tested by using whatever wireless node you have.
Using Node Commander software, confirm that any given channel on whatever wirelees node you have is working.
From there, reconfigure the sensor channel with Node Commander so that the output in Node Commander is VOLTS.
Again using Node Commander, direct the sensor output in VOLTS to each of the output channels on the backplane of the analog base station.
Using your DAQ, multi-meter or other analog measurement system, confirm that the analog voltage output matches the digital voltage output as reported by Node Commander.
Our MIP Monitor software, as written, will not allow you to save the 12 hard and soft iron calibration coefficients to a file, and then read that file back into the software to rewrite the values to the inertial sensor.
However, you cand accomplish the task by recording the values that are displayed (or take a screen grab).
This would be followed by using the data communications protocol EEPROM Write command to write the values back into the device.
This would require either a terminal program or the ability to write software, an understanding of how to construct the command packets, and a list of the EEPROM addresses involved.
Please contact your Lord MicroStrain support engineer for further details.
The Internal or External GPS selector refers to the function that allows the user to turn off the on-board GPS and use a computer to send GPS updates to the device.
If you are using the internal GPS, always select ‘Internal’.
Refer to the data communications protocol if you intend to supply external GPS.
MIP Monitor software also has a test function that allows you to input user selected GPS parameters.
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):
- height above ellipsoid
- height above MSL
- horizontal accuracy
- vertical accuracy
AHRS (100 Hz):
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.
However, new LXRS functions such as synchronized sampling, beaconing, etc. will not be available for your older node.
Without the magnetometer, the only heading reference is from the GPS and this heading reference can only be used on a platform that has some constant lateral motion. This is the only way GPS can get a good heading. Once a heading reference is obtained (either magnetometer or GPS heading) it can be maintained for a short time (less than 30 seconds typically) with just the gyroscopes. This, of course, would have to be done through a fusion filter external to the -35. The LORD MicroStrain 3DM-GX3-45 product actually has this functionality built-in.
The main difference between single byte (SB) and MIP is as follows:
- All MIP commands and data have a header and checksum. SB only has a header (the echo of the command byte) and a checksum on the replies. This means that the programmer has to create a header and calculate the checksum for a command before s/he sends the command. This was not necessary with SB.
- MIP setup and control commands (like start and stop continuous mode) send an ACK/NACK field with a reply. SB does not. The ACK/NACK field has an error code that can be used to confirm that a command was accepted.
- MIP packets can contain multiple command and data fields. SB commands and data only have one fixed field.
The reason we created MIP was the higher reliability for communications and control, plus the ability to have custom data messages. SB was prone to phantom commands in a noisy environment. In addition, SB had a limited number of data combinations available.
To move code from Single Byte to MIP with simple applications is fairly painless if you follow some guidelines.
- You can “prebuild” all your setup and control commands and make them constants in your code. You can plug the prebuilt packet constants into the same part of the code that you previously used to send a single byte command (In essence, you are sending a “multi-byte” command instead of a single byte command). We have a “packet builder” tool in the MIP Monitor that will build the packet for you. You can try out the command and then copy the packet and paste it directly into your code as a string constant.
- When you design the MIP data message, make sure all the “data rate decimation” values are the same. This will make all the data packets identical, which makes finding data in the packet similar to finding data in a SB data message (by using fixed offsets).