Home Community User Groups Special Interest Groups [Archive] NI VeriStand Add-Ons NI VeriStand Add-Ons Documents Document

NI VeriStand Add-Ons Documents

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

NI VeriStand Add-on: Modbus Custom Device

by Member on
‎08-13-2014 09:21 PM
- edited on ‎01-30-2017 10:20 AM by: Member Vincent_R.
h1. Overview

* *The Modbus Custom Device allows users to implement a Modbus (TCP or Serial) protocol communication in NI-VeriStand. Master or Slave Modbus types are supported. Two instances of the Custom Device can run on the same target.

h1. Instructions for Use

* *To use the Modbus Custom Device first add the custom device to your System Definition. The settings of the Modbus Custom Device instance are defined via an XML file loaded from the Main page. In that XML file, high-level settings (communication type (Serial, TCP), Modbus type (Master, Slave, specific settings) and also Modbus Items are stored.

 

Below is a screen capture of Custom Device Main page. User can define instance name. To load instance settings, browse to your XML file AND click "Load/Refresh" button. If XML loading is successful, NI-VeriStand channels are created. Content of XML file is also displayed at the bottom of the Main page.Cf. XML file section in the document to understand how to create your XML file.

h1.  

Installing the Waveform Data Logger Custom Device

* *

Copy the "Waveform Data Logger" directory into your "<Public Documents>\National Instruments\<VeriStand>\Custom Devices\" directory

    <li mcestyle="text-align: start;">Example destination path on Windows Vista/7: “C:\Users\Public\Documents\National Instruments\NI VeriStand &lt;year&gt;\Custom Devices”

      h1. Add-on Requirements to Run the Waveform Data Logger Custom Device

      h2. Software

      To use this custom device you must have the following software installed:

        1. NI VeriStand 2012 or later

      h2. Hardware

      This custom device can run on any hardware supported by NI VeriStand. This includes PharLap and VxWorks RT targets, as well as deploying locally to a Windows machine.

      h1. Known Issues
      <li mcestyle="text-align: start;">The "Decimation" setting on the waveforms tab currently has no effect.  All data points will be logged for every waveform.  Support for decimation will be added in a future release.
        <li mcestyle="text-align: start;">https://decibel.ni.com/content/docs/DOC-39149/Fixed in 2014 File segmentation will not work and cause an error to be thrown on any RT targets with a FAT file system (CAR 412309).  To work around this issue, go into MAX, right-click your RT target, select "Format Disk", then make sure "Reliance" is set as the file system format.  Please note that this will delete all files on your RT target, so make sure to back up any files you wish to keep before formatting.

          <h1 mcestyle="text-align: start;">Version History

          <1.4.3>

            <li mcestyle="text-align: start;">&lt;Bug fix&gt; Fixed known issue that waveform properties (units, GUID, system name) were missing from logs.

              <1.4.2>

                1. <Feature> Added a new "Minimum Buffer Size" property to buffer the data for each waveform so that it is written to disk in larger chunks.

              <1.4.1>

                <li mcestyle="text-align: start;">&lt;Bug Fix&gt; Waveform meta-data (including timing information) is no longer lost when a mulit-waveform log file is segmented.

                  <1.4.0>

                    <li mcestyle="text-align: start;">&lt;Feature&gt; "Log multiple triggers simulataneously" can now be set for log files.  When this is set, any start trigger received will start another log instance, even if one is already active.  This setting is only availble when there is a Start Trigger configured, the Stop Trigger is set to "Stop after duration", and the log is set to be retriggerable.</li><li mcestyle="text-align: start;">&lt;Change&gt; The File Page UI has been changed to have the Start Trigger and Stop Trigger settings on separate tabs.</li><li mcestyle="text-align: start;">&lt;Bug Fix&gt; The custom device previously would cause high CPU usage if no waveforms were configured to be logged.

                      <1.3.1>

                        1. Fixed a critical bug where data may not be logged correctly if pre-trigger logging is enabled. It is strongly recommended that you upgrade if you are using a previous version.

                      <1.3.0>

                        1. first public release

                      h1. Support and Contact

                      This add-on is not officially supported by National Instruments.  If you encounter a problem with this add-on, or if you have suggestions for a future revision, please post to the forum for this add-on: Waveform Data Logger Custom Device Feedback .  You *must *use this feedback forum for support. Do not call National Instruments for support for this add-on.

                      National Instruments does not support this code or guarantee its quality in any way. THIS EXAMPLE PROGRAM IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND AND SUBJECT TO CERTAIN RESTRICTIONS AS MORE SPECIFICALLY SET FORTH IN NI.COM'S TERMS OF USE (http://ni.com/legal/termsofuse/unitedstates/us/ ).</p>
                      0 Kudos
                      Contributors