Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
To use the neoVI API in Visual Basic add the Download the file bas_neoVI.vb
module into the VB project (figure 1) by right clicking on the Solution and selecting Add Existing Item from the Add menu. Open the bas_neoVI.vb. Then, call the methods as defined in the WIN32 API Functions and Types Section of this document.
A Visual Basic Dot Net 2010 example (Figure 1) is included to show how the API all works together. The main project files are as follows: 1) the project file: IcsNeoDotNet.sln 2) the form file : Form1.vb, and 3) the neoVI module : bas_neoVI.vb. All project files are included in the following file VBnet2010.zip
. This project will open in Visual Studio 2010, 2012, 2013, 2015, and 2017.
The example shows how to open and close communication to the driver, send messages and read messages on the networks.
Working with the neoVI API, the folloing steps and functions will be used.
Start the application.
Open the driver and find a neoVI or ValueCAN device.
Create the neoVI object using the OpenNeoDevice method.
Transmit messages using the TxMessages method.
Read messages on the network using the GetMessages method.
Optionally readout any errors using the GetErrorMessages method.
Repeat steps 3 through 5 while your application is monitoring the network.
Close the driver when not monitoring by calling the ClosePort method.
To start monitoring again go back to step 2.
When the application exits the neoVI object must freed (destroyed) by calling the FreeObject method.
The intrepidcs API packages all of the WIN32 methods into LabVIEW LLB. Inside the LLB the sub VIs can be accessed to make it easy for you to use neoVI with National Instruments LabVIEW.
Open the “NEO VI Example.llb” found in the Nlabv_neo.zip (546kB)
file. When you first access the main VI or sub VI’s you may receive a warning regarding a Dependency missing. Make sure that your project is pointing to the icsneo40.dll. This is normally installed to the system32 or SysWOW64 directories.
A LabVIEW example (Figure 1) is included to show how the API all works together. An example project can be found here: Nlabv_neo.zip (546kB)
.
The example shows how to open and close communication to the driver, send messages and read messages on the networks.
Copy the import library icsnLW40.lib
, header file icsnLW40.h
, and data structure file icsspyData.h
to your project directory.
Link to icsnLW40.lib import library by selecting Add Files To Project from the Edit pull down menu. In the “Add Files To Project” dialog select the icsnLW40.lib file (figure 1). You can also the headers from step 1 if you wish. Your project should now list the files you added (figure 2).
3. Include the header icsnLW40.h in your C module (Figure 3).
4. Finally, call the methods as defined in the Basic Operation document.
A National Instruments LabWindows example (Figure 1) is included to show how the API all works together. The example files are included in the following file: LWneoVI.zip (10kB)
The example shows how to open and close communication to the driver, send messages and read messages on the networks.
Start your new project and add the Dynamic link helper files
to your project.
Add a #include
“icsneo40DLLAPI.h” to your project
3. Use the Functions “LoadDLLAPI” to load the functions and “UnloadDLLAPI” to unload the functions. Examples are below.
4. Finally, call the methods as defined in the Basic Operation document.
A Visual C++ example (Figure 1) is included to show how the API all works together. The example files are included in the following file: VCNewneoVI.zip
The example shows how to open and close communication to the driver, send messages and read messages on the networks.
Do the following steps to use neoVI in Borland Delphi:
Copy the import library icsn40.pas
, and data structure file icsSpyData.pas
to your project directory.
Link to icsn40.pas import library via the “Add to Project…” option (Figure 1). This dialog is accessible via the “Project” pull down menu in Delphi. When the file dialog appears, select the icsn40.pas.
3. Your project manager will now show the import library icsn40.pas (Figure 2).
4. Include icsn40 and icsSpyData in your interface Uses (Figure 3).
5. Finally, call the methods as defined in the Basic Operation document.
A Borland Delphi example (Figure 1) is included to show how the API all works together. The example files are included in the following file: icsnDelphiSample.zip (14kB)
The example shows how to open and close communication to the driver, send messages, and read messages on the networks.
To use the neoVI API in C# add the icsNeoClass.cs
Class into the C# project (figure 1). Right click on the solution and select “Add Existing Item” from the “Add” menu. Then, call the methods as defined in the WIN32 API Functions and Types Section of this document.
A C# Dot Net 2010 example (Figure 1) is included to show how the API all works together. The main project files are as follows: 1) the project file: IcsApiDotNetCSharp.sln 2) the form file : Form1.cs, and 3) the neoVI module : icsNeoClass.cs. All project files are included in the following file CSnet2010.zip
. This project will open in Visual Studio 2010, 2012, 2013, 2015 and 2017.
The example shows how to open and close communication to the driver, send messages and read messages on the networks.
Do the following steps to use neoVI in Borland C++ Builder:
1) Start your new project and add the Dynamic link helper files to your project.
2) Add a #include "icsneo40DLLAPI.h" to your project
3) Use the Functions "LoadDLLAPI" to load the functions and "UnloadDLLAPI" to unload the functions. Examples are below.
4) Finally, call the methods as defined in the he Basic Operation document.
A Borland C++ Builder example (Figure 1) is included to show how the API all works together. The example files are included in the following file: BCBneoVI.zip (31kB)
The example shows how to open and close communication to the driver, send messages and read messages on the networks.
Visual Studio 2005 and newer contain different options to compile an application. By default, new programs or programs upgraded from earlier versions of Visual Studio will be configured as "ANY CPU". This option will run as a 32 bit program (x86) on a 32 bit version of Windows and as a 64 bit program (x64) in a 64 bit version of Windows. Projects can also be directly specified as 32 bit (x86) or 64 bit (x64). Starting with icsneo40.dll version 3.7.1.73 and newer, a 64 bit dll was introduced. Using software installs from Intrepid Control Systems, the two dlls are installed to their proper locations on the system. The compiler settings will dictate which of the two dlls is used. Windows will map to the proper one.
The folder location for the icsneo40.dll depends on the Windows install. On a 32 bit (x86) PC, just the 32 bit version is installed to the System32 folder. On a 64 bit system (x64) the 32 bit version is stored in the SysWoW64 folder and the 64 bit version is in the System32 folder. Again the operating system will take care of this based on your settings in the compiler. In either case, the application would need to reference System32, or not specify the location at all. Windows will search the application folder followed by the proper system folder locations to access the correct dll based on your compile options
The configuration manager is used to set which compile type needed. The following are steps for changing the compile options Visual Studio 2010. For help with your version and level of Visual Studio, consult Visual Studio help or MSDN. It is possible to change the compile options. The first step is to open the "Configuration Manager". This can be found by right clicking on your Solution and choosing "Configuration Manager" (figure 1).
Once in Configuration Manager, the Active solution platform can be selected. If you do not have the required option, select "<New...>" (figure 2).
After a new Platform has be created, it can be selected from the Standard tool bar (figure 4)
First set the scene for running an .exe file, then an explanation of how the scripts work.
This is the Unity3D Demo in its entirety included to show how the API all works together; The example files are included in the following file: Unity3d Graphics Panel Demo (1537kB)
Open Unity3D. Locate and open the project folder called “Unity Graphic display API”. (Figure 1)
In the project panel open the Unity scene called Unity_API_Demo. Once opened, in the game view is a place holder for the graphical display. This is where all the data will be visually displayed upon execution of the application. (Figure 2)
Next, locate the icsNeoClass.cs and make sure it is in the correct folder, this imports the .DLL into the project panel (cannot be in any other folder, other then the main “project asset folder”).
Locate IcsNeoClassUnity.cs, located in the Scripts folder. This example script handles the functions of the Intrepid Hardware; open, close, transmit, receive, ect… Then attach the IcsNeoClassUnity.cs on the Main Camera. (refer to figure 3)
The demo should be all set up and ready to play out at this point. Press the play button near the top of the Unity3D windows to enter play mode and begin the demo. (Figure 4)
To use the intrepidcs API in Excel or other VBA supported application add the bas_neoVI.vb
module into your project (figure 1) by right clicking on the Project in the VBA Editor and selecting Insert and then Module. Open the bas_neoVI.vb. Then, call the methods as defined in the Basic Operation document. The function calls for use in VBA are the same as the calls in Visual Basic 6.
A VBA Excel example (Figure 1) is included to show how the API all works together. This project only has 1 file, NeoVIExample.XlS. Make sure macros are enabled to run this example. All the needed project files are included in the following file: ExcelVBA.zip
The example shows how to open and close communication to the driver, send messages and read messages on the networks.