diff --git a/program/hal/hal-I2CLineSensor/hal-I2CLineSensor.vi b/program/hal/hal-I2CLineSensor/hal-I2CLineSensor.vi deleted file mode 100644 index d9d225d..0000000 Binary files a/program/hal/hal-I2CLineSensor/hal-I2CLineSensor.vi and /dev/null differ diff --git a/program/hal/hal-ads1115/_chatReg.vi b/program/hal/hal-ads1115/_chatReg.vi new file mode 100644 index 0000000..1e5db93 Binary files /dev/null and b/program/hal/hal-ads1115/_chatReg.vi differ diff --git a/program/hal/hal-ads1115/ads1115.lvlib b/program/hal/hal-ads1115/ads1115.lvlib index 260f9fc..43a4520 100644 --- a/program/hal/hal-ads1115/ads1115.lvlib +++ b/program/hal/hal-ads1115/ads1115.lvlib @@ -7,17 +7,16 @@ 1.0.0.0 false - - - + + + - diff --git a/program/hal/hal-ads1115/begin.vi b/program/hal/hal-ads1115/begin.vi index e911bfc..2a3151e 100644 Binary files a/program/hal/hal-ads1115/begin.vi and b/program/hal/hal-ads1115/begin.vi differ diff --git a/program/hal/hal-ads1115/chatReg.vi b/program/hal/hal-ads1115/chatReg.vi deleted file mode 100644 index 74157ef..0000000 Binary files a/program/hal/hal-ads1115/chatReg.vi and /dev/null differ diff --git a/program/hal/hal-ads1115/end.vi b/program/hal/hal-ads1115/end.vi deleted file mode 100644 index bafc3a6..0000000 Binary files a/program/hal/hal-ads1115/end.vi and /dev/null differ diff --git a/program/hal/hal-ads1115/example/[todo]get analog value.vi b/program/hal/hal-ads1115/example/[todo]get analog value.vi new file mode 100644 index 0000000..c4b1de4 Binary files /dev/null and b/program/hal/hal-ads1115/example/[todo]get analog value.vi differ diff --git a/program/hal/hal-ads1115/example/update register only.vi b/program/hal/hal-ads1115/example/update register only.vi new file mode 100644 index 0000000..fae6a93 Binary files /dev/null and b/program/hal/hal-ads1115/example/update register only.vi differ diff --git a/program/hal/hal-ads1115/example/write register only.vi b/program/hal/hal-ads1115/example/write register only.vi new file mode 100644 index 0000000..cbc1f71 Binary files /dev/null and b/program/hal/hal-ads1115/example/write register only.vi differ diff --git a/program/hal/hal-ads1115/getReg.vi b/program/hal/hal-ads1115/getReg.vi deleted file mode 100644 index ce1d6f8..0000000 Binary files a/program/hal/hal-ads1115/getReg.vi and /dev/null differ diff --git a/program/hal/hal-ads1115/hal-ads1115.vi b/program/hal/hal-ads1115/hal-ads1115.vi deleted file mode 100644 index 9f2eb9f..0000000 Binary files a/program/hal/hal-ads1115/hal-ads1115.vi and /dev/null differ diff --git a/program/hal/hal-ads1115/isBusy.vi b/program/hal/hal-ads1115/isReady.vi similarity index 55% rename from program/hal/hal-ads1115/isBusy.vi rename to program/hal/hal-ads1115/isReady.vi index f0d771c..72c9a36 100644 Binary files a/program/hal/hal-ads1115/isBusy.vi and b/program/hal/hal-ads1115/isReady.vi differ diff --git a/program/hal/hal-ads1115/readValue.vi b/program/hal/hal-ads1115/readValue.vi new file mode 100644 index 0000000..42a86a8 Binary files /dev/null and b/program/hal/hal-ads1115/readValue.vi differ diff --git a/program/hal/hal-ads1115/setConfig.vi b/program/hal/hal-ads1115/setConfig.vi new file mode 100644 index 0000000..a6eb51e Binary files /dev/null and b/program/hal/hal-ads1115/setConfig.vi differ diff --git a/program/hal/hal-ads1115/setPGA.vi b/program/hal/hal-ads1115/setPGA.vi index e2daa7d..96c631f 100644 Binary files a/program/hal/hal-ads1115/setPGA.vi and b/program/hal/hal-ads1115/setPGA.vi differ diff --git a/program/hal/hal-ads1115/setReg.vi b/program/hal/hal-ads1115/setReg.vi deleted file mode 100644 index afff3b2..0000000 Binary files a/program/hal/hal-ads1115/setReg.vi and /dev/null differ diff --git a/program/midle/Line-Sensor.vi b/program/midle/Line-Sensor.vi index b7a5f53..cb8919f 100644 Binary files a/program/midle/Line-Sensor.vi and b/program/midle/Line-Sensor.vi differ diff --git a/program/runtime/Main.vi b/program/runtime/Main.vi new file mode 100644 index 0000000..51ae9f9 Binary files /dev/null and b/program/runtime/Main.vi differ diff --git a/program/runtime/documentation/myRIO Project Documentation.html b/program/runtime/documentation/myRIO Project Documentation.html new file mode 100644 index 0000000..5cc0231 --- /dev/null +++ b/program/runtime/documentation/myRIO Project Documentation.html @@ -0,0 +1,541 @@ + + + + +myRIO Project + + + + + + + +

myRIO Project

+ +

You can use the myRIO Project template as a starting point for creating myRIO applications with the myRIO default FPGA personality. With the myRIO Project template, you can easily access myRIO I/O channels and onboard devices without making major modifications to the structure of the application.

+ +

Table of Contents

+

System Requirements

+

Understanding the Components of This Template

+

Running This Template

+

Modifying This Template

+

Related Information

+ +
+ + +

System Requirements

 +

Development System

+ +
    +
  • LabVIEW Full or Professional Development System
    • +
  • LabVIEW Real-Time Module
    • +
  • LabVIEW myRIO Toolkit
    • +
+ +

Hardware

+
    +
  • myRIO
    • +
+ + + +

Understanding the Components of This Template

 +

This template uses a Flat Sequence structure that executes frames from left to right.

+ +

The Flat Sequence structure in this template executes the following frames from left to right:

+
    +
  1. Initialize—Initializes the myRIO, variables, and user interface elements, such as controls and indicators. Initializing code depends on your application needs.
    2. +
  2. Acquire and process data—Acquires data from the myRIO and processes the data for presentation. The While Loop repeats code until you click Stop or an error occurs.
    3. +
  3. Close—Closes user interface elements and variables, and resets the myRIO output values to zero before the application exits. Closing code is optional.
    4. +
+ + +

Running This Template

 +
    +
  1. In the Project Explorer window, navigate to your myRIO target and open the Main VI.
    2. +
  2. Click Run. This application acquires acceleration data from the onboard accelerometer and displays changes to acceleration values in a waveform chart.
    3. +
  3. Rotate or shake the myRIO and observe the changes of the X, Y, and Z acceleration values.
    4. +
  4. Click Stop to stop the application.
    5. +
+ + +

Modifying This Template

 + +

The following table summarizes the design decisions you must make when modifying this template.

+ + + + + + + + + + + + + + + + + + + + + + + + + + +
Design DecisionDesign ExampleDetailed Information
How do you want to control the order of execution in your application?You want data to flow as desired without using the Flat Sequence structure.Controlling the Order of Execution
What data does your application need to initialize?You want your application to open a file for logging.Adding Initialization Code
Which myRIO I/O channels does your application need to access?You want your application to control the DIO channels on the myRIO.Modifying the Data Acquisition and Processing Code
What executions does your application need to complete before exiting?You want your application to close references to make memory resources available.Adding Closing Code
How does your application handle errors?You want your application to report errors at the end of the execution flow.Modifying Error Handling
+ +

Controlling the Order of Execution

+

This template uses the Flat Sequence structure to control data flow. The data leaves each frame as the frame finishes executing. This template uses the Flat Sequence structure to demonstrate the purpose of the code in each frame.

+

Note  Do not overuse the Flat Sequence structure for controlling the execution order because the Flat Sequence structure prohibits parallel operations.

+

When you modify this template, you can remove the Flat Sequence structure and establish data dependency between nodes. For example, wiring the error in and error out clusters through nodes controls the data to flow from one node to another.

+ + +

Adding Initialization Code

+

This template initializes the error in cluster to specific values. You can add code to initialize your user interface and the myRIO. For example, you may want to initialize the data to specific values or to open a file for logging.

+ +

Modifying the Data Acquisition and Processing Code

+

This template uses the Accelerometer Express VI to read the acceleration values from the onboard accelerometer and uses a waveform chart to display the acceleration values.

+

You can add code to acquire data from the myRIO and process the data based on your application needs. The myRIO Toolkit provides Express VIs and Low Level VIs for you to access I/O channels and the onboard devices.

+ +

Adding Closing Code

+

This template uses the Reset VI to reset the onboard accelerometer. You must use the Reset VI after the completion of all operations with the myRIO I/O channels. Otherwise, the Reset VI might return unexpected results.

+

You can add code that executes after the data acquisition and processing completes but before the application exits. Closing code commonly accomplishes the following tasks:

+
    +
  • Frees memory by closing any open references
    • +
  • Flushes any buffers in use
    • +
  • Resets the myRIO
    • +
+ +

Modifying Error Handling

+

By default, if an error occurs in the Accelerometer Express VI, this template stops. If you do not want the error to stop your application, you can remove the OR function and wire the Stop control directly to the conditional terminal of the While Loop. The error in and error out clusters pass error information from the beginning of the VI to the end and report the error at the end of the execution flow.

+ + + +

Related Information

 +

Refer to the LabVIEW Help, available by selecting Help»LabVIEW Help from LabVIEW, for information about LabVIEW concepts or objects used in this sample project. You also can use the Context Help window to learn basic information about LabVIEW objects as you move the cursor over each object. To display the Context Help window in LabVIEW, select Help»Show Context Help.

+

Refer to the myRIO sample projects, available from the Create Project dialog box, for examples of adapting this template to more complex applications.

+ +
+

Legal Information

+ +

Copyright

+

© 2013–2015 National Instruments. All rights reserved.

+ +

Under the copyright laws, this publication may not be reproduced or transmitted in any form, electronic or mechanical, including photocopying, recording, storing in an information retrieval system, or translating, in whole or in part, without the prior written consent of National Instruments Corporation.

+ +

National Instruments respects the intellectual property of others, and we ask our users to do the same. NI software is protected by copyright and other intellectual property laws. Where NI software may be used to reproduce software or other materials belonging to others, you may use NI software only to reproduce materials that you may reproduce in accordance with the terms of any applicable license or other legal restriction.

+ +

End-User License Agreements and Third-Party Legal Notices

+

You can find end-user license agreements (EULAs) and third-party legal notices in the following locations after installation:

+
    +
  • Notices are located in the <National Instruments>\_Legal Information and <National Instruments> directories.
    • +
  • EULAs are located in the <National Instruments>\Shared\MDF\Legal\license directory.
    • +
  • Review <National Instruments>\_Legal Information.txt for information on including legal information in installers built with NI products.
    • +
+

U.S. Government Restricted Rights

+

If you are an agency, department, or other entity of the United States Government ("Government"), the use, duplication, reproduction, release, modification, disclosure or transfer of the technical data included in this manual is governed by the Restricted Rights provisions under Federal Acquisition Regulation 52.227-14 for civilian agencies and Defense Federal Acquisition Regulation Supplement Section 252.227-7014 and 252.227-7015 for military agencies.

+ +

IVI Foundation Copyright Notice

+ +

Content from the IVI specifications reproduced with permission from the IVI Foundation.

+ +

The IVI Foundation and its member companies make no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. The IVI Foundation and its member companies shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.

+ + + +

Trademarks

+ + +

Refer to the NI Trademarks and Logo Guidelines at ni.com/trademarks for information on National Instruments trademarks. Other product and company names mentioned herein are trademarks or trade names of their respective companies.

+ + + +

Patents

+

For patents covering the National Instruments products/technology, refer to the appropriate location: Help»Patents in your software, the patents.txt file on your media, or the National Instruments Patent Notice at ni.com/patents.

+ + + + \ No newline at end of file diff --git a/program/runtime/documentation/myRIO_Project_Diagram.gif b/program/runtime/documentation/myRIO_Project_Diagram.gif new file mode 100644 index 0000000..9e25779 Binary files /dev/null and b/program/runtime/documentation/myRIO_Project_Diagram.gif differ diff --git a/program/runtime/runtime.aliases b/program/runtime/runtime.aliases new file mode 100644 index 0000000..f0f27b0 --- /dev/null +++ b/program/runtime/runtime.aliases @@ -0,0 +1,6 @@ +[Mobile-Robot-K4-001] +Mobile-Robot-K4-001 = "192.168.1.6" + +[My Computer] +My Computer = "192.168.1.8" + diff --git a/program/runtime/runtime.lvlps b/program/runtime/runtime.lvlps new file mode 100644 index 0000000..faa68fe --- /dev/null +++ b/program/runtime/runtime.lvlps @@ -0,0 +1,3 @@ +[ProjectWindow_Data] +ProjectExplorer.ClassicPosition[String] = "33,1,859,328" + diff --git a/program/runtime/runtime.lvproj b/program/runtime/runtime.lvproj new file mode 100644 index 0000000..32851cf --- /dev/null +++ b/program/runtime/runtime.lvproj @@ -0,0 +1,224 @@ + + + false + + + + 100 + false + 10000 + 0 + 9 + true + false + true + true + false + 0 + My Computer/VI Server + My Computer/VI Server + true + true + false + + + + + + + + + + + Mobile-Robot-K4-001 + 192.168.1.6 + OS,Linux;CPU,ARM;DeviceCode,762F;TARGET_TYPE,RT;FPGAPersonality,myRIO_FP_Default; + 762F + ARMLinux + true + 5000 + 1000 + 8 + 8 + false + 300 + 80 + 60 + + 100 + false + 10000 + 0 + 0 + true + true + true + 8001 + /c/ni-rt/startup/startup.rtexe + true + +* + false + /c/ni-rt/startup + true + true + +* + false + true + 3363 + Main Application Instance/VI Server + Main Application Instance/VI Server + +* + true + true + Listen 8000 + +NI.ServerName default +DocumentRoot "$LVSERVER_DOCROOT" +TypesConfig "$LVSERVER_CONFIGROOT/mime.types" +DirectoryIndex index.htm +WorkerLimit 10 +InactivityTimeout 60 + +LoadModulePath "$LVSERVER_MODULEPATHS" +LoadModule LVAuth lvauthmodule +LoadModule LVRFP lvrfpmodule + +# +# Pipeline Definition +# + +SetConnector netConnector + +AddHandler LVAuth +AddHandler LVRFP + +AddHandler fileHandler "" + +AddOutputFilter chunkFilter + + + + false + false + /c/ni-rt/system/www/www.log + 80 + /c/ni-rt/system/www + c+* + 60 + +* + PqVr/ifkAQh+lVrdPIykXlFvg12GhhQFR8H9cUhphgg=:pTe9HRlQuMfJxAG6QCGq7UvoUpJzAzWGKy5SbZ+roSU= + 15 + + true + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + true + + + true + + + + + +