Alert.png

Notice: This page contains information for the legacy Phidget21 Library.

Phidget21 is out of support. Bugfixes may be considered on a case by case basis.

Phidget21 does not support VINT Phidgets, or new USB Phidgets released after 2020. We maintain a selection of legacy devices for sale that are supported in Phidget21.

We recommend that new projects be developed against the Phidget22 Library.


Click on the 2phidget22.jpg button in the menu bar to go to the Phidget22 version of this page.

Alert.png

Language - Visual Basic 6.0: Difference between revisions

From Phidgets Legacy Support
No edit summary
 
(60 intermediate revisions by 4 users not shown)
Line 1: Line 1:
[[Category:Language]]
[[Category:Language]]
[[File:icon-Visual Basic.png|64x64px]] Visual Basic 6.0 is the greatest programming language of all time.
{{OSLang|[[File:icon-Visual Basic.png|64x64px|link=|alt=]]|Visual Basic 6.0, developed by [http://www.microsoft.com Microsoft] is a high level programming language that uses the COM programming model.}}
 
__TOC__
__TOC__


==Introduction==
==Introduction==


{{LanguageSupport|Visual Basic 6.0|the complete Phidget API, including events|all Phidget devices.|Windows (environments include [[#Visual Studio | Visual Studio]], [[#Borland | Borland]], [[#Cygwin/MinGW | Cygwin, and MinGW]]), [[#Mac OS X | Mac OS X]], and [[#Linux | Linux]]|}}
{{LanguageSupport|Visual Basic 6.0|the complete Phidget API, including events|all Phidget devices.| the Microsoft Visual Basic 6 IDE|}}


==Quick Downloads==
==Quick Downloads==
Just need the Visual Basic 6.0 documentation, drivers, libraries, and examples?  Here they are:
{{QuickDownloads|Visual Basic 6.0|
 
{{APIQuickDownloads|{{SERVER}}/documentation/COM_API_Manual.pdf COM}}|
===API Documentation===
{{ExampleQuickDownloads|{{SERVER}}/downloads/phidget21/examples/com/VB6.zip|}}|
*[http://www.phidgets.com/documentation/COM_API_Manual.pdf API Manual]
{{WindowsQuickDownloads}}
 
}}
===Example Code===
* [http://www.phidgets.com/downloads/examples/VB6_2.1.8.20120131.zip Example Code]
 
===Libraries and Drivers:===
*[http://www.phidgets.com/downloads/libraries/Phidget-x86_2.1.8.20111220.exe 32 bit Windows Drivers Installer]
*[http://www.phidgets.com/downloads/libraries/Phidget-x64_2.1.8.20111220.exe 64 bit Windows Drivers Installer]
*[http://www.phidgets.com/downloads/libraries/phidget21-x86_2.1.8.20110615.zip 32 bit Windows Drivers and Libraries]
*[http://www.phidgets.com/downloads/libraries/phidget21-x64_2.1.8.20110615.zip 64 bit Windows Drivers and Libraries]


==Getting started with Visual Basic 6.0==
==Getting started with Visual Basic 6.0==
Line 28: Line 19:
{{ExampleCodeReasons}}
{{ExampleCodeReasons}}


Instructions are divided up by operating system. Choose:
==Windows (XP/Vista/7/8)==
*[[#Windows(2000/XP/Vista/7)|Windows 2000 / XP / Vista / 7]]
 
==Windows(2000/XP/Vista/7)==


===Description of Library Files===
===Description of Library Files===
Visual Basic 6.0 programs on Windows depend on three files, which the installers in [[#Libraries and Drivers|Quick Downloads]] put onto your system:
Visual Basic 6.0 programs on Windows depend on two files, which the installers in [[#Libraries and Drivers|Quick Downloads]] put onto your system:
* <b>{{Code|phidget21.dll}}</b> contains the actual Phidgets library, which is used at run-time.  By default, it is placed in {{Code|C:\Windows\System32}}.
* <b>{{Code|phidget21.dll}}</b> contains the actual Phidget library, which is used at run-time.  By default, it is placed in {{Code|C:\Windows\System32}}.
* <b>{{Code|phidget21.lib}}</b> is used by your compiler to link to the dll.  Your compiler has to know where this file is, by default our installer puts {{Code|phidget21.lib}} into {{Code|C:\Program Files\Phidgets}}, so you can either point your compiler to that location, or copy and link to it in a directory for your project workspace. {{Code|phidget21.lib}} is written to be compatible with most compilers - but your specific compiler may need a different format. Check our documentation for your specific compiler for details. Please note that we provide versions of the {{Code|phidget21.lib}} that are specifically optimized for 32-bit or 64-bit systems. If you are using a 64 bit versions of Windows, the {{Code|phidget21.lib}} is placed in {{Code|C:\Program Files\Phidgets}}; The 32 bit version of {{Code|phidget21.lib}} is placed in {{Code|C:\Program Files\Phidgets\x86}}.
* <b>{{Code|Phidget21COM.dll}}</b> is the Component Object Model(COM) library and provides your project access to the Phidget ActiveX objects.  Your compiler has to know where this file is, by default our installer places this file into {{Code|C:\Program Files\Phidgets}}, so you can either point your compiler to that location, or copy and link to it in a directory for your project workspace. If you are manually installing this file, you must register it through command line by running: {{Code|regsvr32 Phidget21COM.dll}}.
* <b>{{Code|phidget21.h}}</b> lists all the Phidget API function calls available to your code.  Your compiler also has to know where this file is.  By default, our installer puts {{Code|phidget21.h}} into {{Code|C:\Program Files\Phidgets}} so you can either point your compiler to that location, or copy and link to it in a directory for your project workspace.  


If you do not want to use our installer, you can download all three [http://www.phidgets.com/downloads/libraries/phidget21-x86_2.1.8.20110615.zip files] and manually install them where you want; refer to our [[Manual Installation Instructions | Manual Installation Instructions]].
If you do not want to use our installer, you can download both [{{SERVER}}/downloads/phidget21/libraries/windows/Phidget-x86.zip files] and manually install them where you want; refer to our [[OS_-_Windows#Manual_File_Installation | Manual Installation Instructions]].


 
We include instructions on [[#Use Our Examples | using our examples]] and [[#Write Your Own Code | writing your own code]] for the Microsoft Visual Basic 6.0 IDE.
We include instructions on [[#Use Our Examples | using our examples] and [[#Write Your Own Code | writing your own code]] for Microsoft Visual Basic 6.0 IDE.


====Visual Basic 6.0====
====Visual Basic 6.0====
Line 48: Line 34:
=====Use Our Examples=====
=====Use Our Examples=====


To run the examples, you first download the [http://www.phidgets.com/downloads/examples/VB6_2.1.8.20120131.zip examples] and unpack them into a folder.   
To run the examples, you first download the [{{SERVER}}/downloads/phidget21/examples/com/VB6.zip examples] and unpack them into a folder. Here, you can find a HelloWorld example program that is a simple test for any Phidget deviceYou will also find specific example programs for all the devices. {{FindYourDevice}}


Since the examples were written in Visual Studio 2005, if you are opening the examples in Visual Studio 2008/2010, you will need to go through the Visual Studio Conversion Wizard to open and convert the 2005 project.  
1. Open up the {{Code|.vbp}} project into the Visual Basic IDE.


[[File:VS2005 Conversion Wizard.PNG|link=|alt=Conversion Wizard]]
2. Next, navigate to Project &rarr; Components to ensure that your project has access to the Phidget ActiveX objects


This will load all of the examples available for C/C++, and then you can set your main project to be the one that matches your device.  If you aren't sure what the software example for your device is called, check the software object listed in the [[Device List | Getting Started Guide for your Device]].
[[File:VB6 Components.PNG|link=|alt=Components]]


The only thing left to do is to run the examples! Click on Debug &rarr; Start Debugging. Please note that the projects, by default try to find the {{Code|phidget21.h}} and {{Code|phidget21.lib}} in the {{Code|$(SystemDrive)\Program Files\Phidgets}}. If you have these files installed in another location, please change the path to the file's location accordingly. Please see the [[#Write Your Own Code | Write Your Own Code]] section for details.  
3. The Components menu will show up. Ensure that the Phidget COM library is selected. If it is not, then browse for {{Code|Phidget21COM.dll}} and add it. By default, it is placed in {{Code|C:\Program Files\Phidgets}}. Accept the changes.  


[[File:VS2005 Run.PNG|link=|alt=Run]]
[[File:VB6 Library.PNG|link=|alt=Library]]


Once you have the C/C++ examples running, we have a [[#Follow the Examples|teaching]] section below to help you follow them.
4. Navigate to Project &rarr; References and ensure that the Phidget COM library is selected.


=====Write Your Own Code=====
[[File:VB6 References.PNG|link=|alt=References]]


When you are building a project from scratch, or adding Phidget function calls to an existing project, you'll need to configure your development environment to properly link the Phidget C/C++ libraries. To begin:
5. The only thing left to do is to run the examples! Click on Run &rarr; Start.  


1. Generate a new Visual C++: Win32 Console Application project with a descriptive name such as PhidgetTest.
[[File:VB6 Run.PNG|link=|alt=Run]]


[[File:VS2005 New Project.PNG|link=|alt=New Project]]
Once you have the Visual Basic 6.0 examples running, we have a [[#Follow the Examples|teaching]] section below to help you follow them.


2. Next, select Console Application.
=====Write Your Own Code=====


[[File:VS2005 New Project 2.PNG|link=|alt=New Project]]
When you are building a project from scratch, or adding Phidget function calls to an existing project, you'll need to configure your development environment to properly link the Phidget COM library. To begin:  


3. Open the project properties window.
1. Generate a new Standard EXE project.


4. Navigate to Configuration Properties &rarr; C/C++.
[[File:VB6 New Project.PNG|link=|alt=New Project]]


5. Add {{Code|"C:\Program Files\Phidgets"}} to the additional directories field. This step will find the {{Code|phidget21.h}} file in the corresponding directory. If the file is placed in another location, please adjust the path  to the file's location accordingly.
2. Next, navigate to Project &rarr; Components to add the Phidget ActiveX objects into your project.


[[File:VS2005 Header.PNG|link=|alt=Header File]]
[[File:VB6 Components.PNG|link=|alt=Components]]


6. Navigate to Configuration Properties &rarr; Linker &rarr; Input.
3. The Components menu will show up. Browse for {{Code|Phidget21COM.dll}} and add it. By default, it is placed in {{Code|C:\Program Files\Phidgets}}. Accept the changes.  


7. Edit the additional dependencies and add {{Code|"C:\Program  Files\Phidgets\phidget21.lib"}}. This step will find the {{Code|phidget21.lib}} file in the corresponding directory. If the file is placed in another location, please adjust the path  to the file's location accordingly.
[[File:VB6 Library.PNG|link=|alt=Library]]


[[File:VS2005 Library.PNG|link=|alt=Library File]]
4. Navigate to Project &rarr; References and ensure that the Phidget COM library is selected.


8. The project now has access to the Phidget21 function calls and you are ready to begin coding.
[[File:VB6 References.PNG|link=|alt=References]]


Then, in your code, you will need to include the Phidget library:
5. Navigate to Project &rarr; Project1 Properties, select the {{Code|Make}} tab and ensure that the {{Code|Remove information about unused ActiveX Controls}} checkbox is unchecked.


<div class="source">
[[File:VB6 Unused ActiveX Controls.PNG|link=|alt=Unused ActiveX Controls]]
<syntaxhighlight lang=cpp>


  #include <phidget21.h>
6. Then, you will need to declare and initialize the Phidget ActiveX object for your device.  


</syntaxhighlight>
The simplest method is to place the Phidget ActiveX object from the toolbox directly onto your form. If the toolbox is not present on your screen, navigate to View &rarr; Toolbox to show the toolbar. Next, find the ActiveX object for your device in the toolbox, and double click it to add it to the form.
</div>


[[File:VB6 Toolbox ActiveX.PNG|link=|alt=Accessing Phidget ActiveX objects from the toolbox]]


The same [[#Follow the Examples|teaching]] section which describes the examples also has further resources for programming your Phidget.
Alternatively, you can dynamically create the Phidget ActiveX object in code. For example, for an PhidgetInterfaceKit, you would type:
 
===GCC on Windows===
 
====Cygwin/MinGW====
 
=====Use Our Examples=====
 
Download the [http://www.phidgets.com/downloads/examples/phidget21-c-examples_2.1.8.20111028.tar.gz examples] and unpack them into a folder. Afterwards, unpack the examples, and then find the source code ''for your specific device''. If you aren't sure what the software example for your device is called, check the software object listed in the [[Device List | Getting Started guide for your device]]. Then, compile the code and run it. When compiling, you need to link to the phidget21 library.
To compile, link the Phidget libraries and build a binary executable, enter the following in a command line prompt in the directory with {{Code|example.c}}:
<b>Cygwin</b>


<div class="source">
<div class="source">
<syntaxhighlight lang=bash>
<syntaxhighlight lang=vb>
  gcc example.c -o example -I"/cygdrive/c/Program Files/Phidgets" -L"/cygdrive/c/Program Files/Phidgets" -lphidget21
Dim WithEvents PhidgetInterfaceKit As PhidgetInterfaceKit
</syntaxhighlight>
</div>
 
<b>MinGW</b>
<div class="source">
<syntaxhighlight lang=bash>
  gcc example.c -o example -I"C:\Program Files\Phidgets" -L"C:\Program Files\Phidgets" -lphidget21
</syntaxhighlight>
</div>
 
In this case, {{Code|example.c}} would be the '''.c''' file specific to your device.  After using gcc, you will have an executable named {{Code|example}} that you can run.  
It is assumed that {{Code|phidget21.h}} and {{Code|phidget21.lib}} are placed in {{Code|C:\Program Files\Phidgets}}. If the files are placed in another location, please adjust the paths to the file's location accordingly.
 
=====Write Your Own Code=====
 
When writing your code from scratch, you start it as you would any C/C++ code with Cygwin/MinGW in your favourite text editor. In your '''{{Code|.c}}''' source code file, you must include a reference to the library header:
 
<div class="source">
<syntaxhighlight lang=cpp>
 
  #include <phidget21.h>


Private Sub Form_Load()
  ...
  Set PhidgetInterfaceKit = Controls.Add("Phidget21COM.PhidgetInterfaceKit", "PhidgetInterfaceKit")
  ...
End Sub
</syntaxhighlight>
</syntaxhighlight>
</div>
</div>


Then, you would compile your completed C/C++ code the same way as shown in the [[#Use Our Examples 5| Use Our Examples]] section above.  
The object name for each type of Phidget is listed in the [{{SERVER}}/documentation/COM_API_Manual.pdf COM API Manual]. Please see the [{{SERVER}}/downloads/phidget21/examples/com/VB6.zip examples] on how to add a reference to your particular Phidget.


To learn how to write your own code for your Phidget, and to learn more about our API, we have a [[#Follow the Examples|teaching]] section to help you follow the provided C/C++ examples and which has resources such as the API reference.
The project now has access to the Phidget function calls and you are ready to begin coding.


===Dev C++===
The same [[#Follow the Examples|teaching]] section which describes the examples also has further resources for programming your Phidget.


=====Use Our Examples=====
==Follow the Examples==
 
1. Download the [http://www.phidgets.com/downloads/examples/phidget21-c-examples_2.1.8.20111028.tar.gz examples] and unpack them into a folder. Here, you can find example programs for all the devices. If you aren't sure what the software example for your device is called, check the software object listed in the [[Device List | Getting Started guide for your device]]. You will need this example source code to be copied into your Dev C++ project later on.
 
2. In order to control Phidgets with Dev C++, we will use the {{Code|reimp}} tool to convert the {{Code|phidget21.lib}} to a format that Dev C++ accepts. Download the [http://www.phidgets.com reimp tool].
 
3. Open up command line and traverse to the directory containing the reimp tool. Type the following command to create {{Code|libphidget21.a}}.
<div class="source">
<syntaxhighlight lang=bash>
  reimp.exe "C:\Program Files\Phidgets\phidget21.lib"
</syntaxhighlight>
</div>
The command above assumes that the {{Code|phidget21.lib}} is in the corresponding directory. If the file is placed in another location, please adjust the path to the file's location accordingly. Please note that the 64 bit version of {{Code|phidget21.lib}} is not supported on Dev C/C++. Please use the 32 bit version of {{Code|phidget21.lib}}.


4. Place {{Code|libphidget21.a}} in {{Code|<Dev-Cpp Install Directory>/lib}}.
By following the instructions for your operating system and compiler above, you probably now have a working example and want to understand it better so you can change it to do what you want. This teaching section has resources for you to learn from the examples and write your own.


5. Next, a new project will need to be created. Generate a new console application with a descriptive name such as PhidgetTest. Please select C as the project type.
Your main reference for writing Visual Basic 6.0 code will be our .COM API information, with syntax for all of our functions:


[[File:DevC New Project.PNG|link=|alt=New Project]]
{{UsingAPhidgetInCodeGeneral|both of which are available in Visual Basic 6.0|[{{SERVER}}/documentation/COM_API_Manual.pdf COM API Manual]}}


6. Next, the project settings needs to be set up. Navigate to Project Options &rarr; Directories &rarr; Include Directories.
===Example Flow===


7. Add a new path to {{Code|C:\Program Files\Phidgets}}. This step will find the {{Code|phidget21.h}} file in the corresponding directory. If the file is placed in another location, please adjust the path to the file's location accordingly.
{{ExamplePseudocode|In Visual Basic 6.0, you need to name these '''event''' functions by which events you want to catch.  Using the underscore between your variable name and the event name from our .COM API (and then delegating each variable that gets passed with the event) will allow the function to be run when the event fires. <br>
 
In the example code, the event functions common to all Phidgets are called things like '''OnAttach''' and '''OnDetach''', etc.<br><br>
[[File:DevC Header.PNG|link=|alt=Header File]]
Some event functions will be specific to each device, like when a tag is read on an RFID board, or when a sensor value changes on an Interface Kit.
 
Other functions are given in the device-specific examples to show you more detail on using your Phidget.
8. Navigate to Project Options &rarr; Parameters &rarr; Linker.
|Creating a Phidget software object in Visual Basic 6.0 is specific to the Phidget. For a Phidget Spatial, for example, this would involve creating a PhidgetSpatial object.  The examples show how to do this and other API functions|
 
[{{SERVER}}/documentation/COM_API_Manual.pdf COM API Manual]}}
9. Add {{Code|-lphidget21}} to the field. This step will find the {{Code|libphidget21.a}} file in {{Code|<Dev-Cpp Install Directory>/lib}}.
 
[[File:DevC Library.PNG|link=|alt=Library File]]


10. To import the example program into your project, please open up {{Code|main.c}} in the editor.
===Code Snippets===


11. An empty C file will pop up. Please copy and paste the contents of the example program.  
Specific calls in Visual Basic 6 will differ in syntax from those on the [[General Phidget Programming]] page, but the concepts stay the same.  


[[File:DevC Source.PNG|link=|alt=Source Code]]
It may help to have the [[General Phidget Programming]] page and this section open at the same time, because they parallel each other and you can refer to the Visual Basic 6 syntax.  However, ''many'' additional concepts are covered on the General Phidget Programming page on a high level, such as using multiple Phidgets, handling errors, and different styles of programming.


12. Now, you can run the example. Click on Execute &rarr; Compile & Run.
====Step One: Initialize and Open====


[[File:DevC Run.PNG|link=|alt=Run]]
The open() function opens the software object, but not hardware. So, it is not a guarantee you can use the Phidget immediately.


The different types of open can be used with parameters to try and get the first device it can find, open based on its serial number, or even open across the network. The API manual lists and [[General Phidget Programming]] discusses all of the available modes that open provides.


Once you have the C/C++ examples running, we have a [[#Follow the Examples|teaching]] section below to help you follow them.
For example, if we were using an Interface Kit Phidget board as our device, the create and open calls would look like this:
 
=====Write Your Own Code=====
 
When you are building a project from scratch, or adding Phidget function calls to an existing project, you'll need to configure your development environment to properly link the Phidget C/C++ libraries. Please see the [[#Use Our Examples 6 | Use Our Examples]] section for instructions.
 
In your '''{{Code|.c}}''' source code file, you must include a reference to the library header:


<div class="source">
<div class="source">
<syntaxhighlight lang=cpp>
<syntaxhighlight lang=vb>
 
Public WithEvents PhidgetInterfaceKit1 As PhidgetInterfaceKit
  #include <phidget21.h>
Set PhidgetInterfaceKit1 = Controls.Add("Phidget21COM.PhidgetInterfaceKit", "PhidgetInterfaceKit1")
 
</syntaxhighlight>
</syntaxhighlight>
</div>
</div>


Then, you would compile your completed C/C++ code the same way as the [[#Use Our Examples 6 | examples]] above.  
Then later, you would open the device as shown below along with the [[#Step Two: Wait for Attachment (plugging in) of the Phidget|attachment]] of the Phidget.


To learn how to write your own code for your Phidget, and to learn more about our API, we have a [[#Follow the Examples|teaching]] section to help you follow the provided C/C++ examples and which has resources such as the API reference.
====Step Two: Wait for Attachment (plugging in) of the Phidget====


==Linux==
To use the Phidget, it must be plugged in (attached). We can handle this by using event driven programming and tracking the AttachEvents and DetachEvents, or we can handle this by calling waitForAttachment. This function works for any Phidget. WaitForAttachment will block indefinitely until a connection is made to the Phidget, or an optional timeout is exceeded.


C/C++ has support on Linux through the gcc compiler. 
Again, if we were still using an Interface Kit Phidget board as our device (as opposed to a Spatial, or Temperature Sensor, or....), the wait for attachment would look like this:


The first step in using C/C++ on Linux is to install the Phidget libraries.  Compile and install them as explained on the main [[OS - Linux | Linux page]].  That Linux page also describes the different Phidget files, their installed locations, and their roles.
<div class="source">
 
<syntaxhighlight lang=vb>
===Use Our Examples===
Private Sub Form_Load()
 
    PhidgetInterfaceKit1.Open
After installing the Phidget libraries for Linux as above, you're ready to download and run the examples:
    PhidgetInterfaceKit1.WaitforAttachment (3000)
*[http://www.phidgets.com/downloads/examples/phidget21-c-examples_2.1.8.20111028.tar.gz Generic C/C++ Examples]
End Sub
 
</syntaxhighlight>
To run the example code, you'll need to download and unpack the examples, and then find the source code for your device.  The source file will be named the same as the ''software object'' for your device.  If you are not sure what the software object for your device is, it can be found in the Software/API section on the [[#Device List|Product Page for your device]].  Then, compile the code under your platform and run it.  When compiling, you need to link to the phidget21 library.
 
To compile, link the Phidget libraries and build a binary executable on Linux, do the following in a terminal in the directory with {{Code|example.c}}:
 
<div style="background-color: #f3f3f3; border-color: #1c9edb; border-width:1px; border-style: dashed;">
<font size="3">
<source lang=bash>
  gcc example.c -o example -lphidget21
</source>
</font>
</div>
</div>


In this case, {{Code|example.c}} would be the '''.c''' file specific to your device.  After using gcc, you will have an executable named {{Code|example}} that you can run. 
====Step Three: Do Things with the Phidget====


On Linux, if you have not set up [[OS - Linux | your udev rules for USB access]], you will need to run the program '''as root''':
We recommend the use of event driven programming when working with Phidgets. In VB.NET we can hook an event handler into the event of a sensor changing on an Interface Kit board with the following code:


<div style="background-color: #f3f3f3; border-color: #1c9edb; border-width:1px; border-style: dashed;">
<div class="source">
<font size="3">
<syntaxhighlight lang=vb>
<source lang=bash>
Private Sub PhidgetInterfaceKit1_OnSensorChange(ByVal Index As Long, ByVal SensorValue As Long)
 
    Text1.Text = Index & ":" & SensorValue
    sudo ./example
End Sub
 
</syntaxhighlight>
</source>
</font>
</div>
</div>


===Write Your Own Code===
With this function, the code inside ifKit_SensorChange will get executed every time the Phidget Interface Kit reports a change on one of its analog inputs. This is because it handles the OnSensorChange event after the underscore.  Some events such as Attach and Detach belong to the base Phidget object and thus are common to all types of Phidgets. In the instance above, the sensor value read is then put into a text box (Text1) for display.


When writing your code from scratch, you start it as you would any C/C++ code on Linux, such as within a text editor like Emacs, Vi, Gedit, or KateIn your '''{{Code|.c}}''' source code file, you must include a reference to the library header:
Some values can be read and sent directly to the Phidget, simply use the instance members and properties. This is also how you would set properties on the Phidget such as the output state or
sensor sensitivityFor example, turning on the digital output 0 (for say, turning on an LED) on an Interface Kit board would be via:


<div style="background-color: #f3f3f3; border-color: #1c9edb; border-width:1px; border-style: dashed;">
<div class="source">
<font size="3">
<syntaxhighlight lang=vb>
<source lang=cpp>
phid.OutputState(4) = True
 
</syntaxhighlight>
  #include <phidget21.h>
 
</source>
</font>
</div>
</div>


Then, you would compile your completed C/C++ code the same way as the examples above.
====Step Four: Close and Delete====


To learn how to write your own code for your Phidget, and to learn more about our API, we have a [[#Follow the Examples|teaching]] section to help you follow the provided C/C++ examples and which has resources such as the API reference.
Make sure to close your Phidget (PhidgetInterfaceKit1.Close, for example) at the end of your program so that other programs can gain access to it.


==Follow the Examples==
{{MoreHowTos}}


By following the instructions for your operating system and compiler above, you probably now have a working example and want to understand it better so you can change it to do what you want. This [[#Follow the Examples|teaching]] section has resources for you to learn from the examples and write your own.
The design given in this document can also be followed for almost all Phidgets. For example, if you were using a PhidgetRFID instead of an PhidgetInterfaceKit, you would place a PhidgetRFID ActiveX
object instead of a PhidgetInterfaceKit. The methods and events available would change but they can be accessed in a similar manner.


Next comes our C/C++ API information, with syntax for all of our functions:
The ''complete'' set of functions you have available for all Phidgets can be found in the [{{SERVER}}/documentation/COM_API_Manual.pdf .COM API].  You can also find more description on any device-specific function in the Device API page for your specific Phidget, which can be found in its [[:Category:UserGuide|user guide]].


{{UsingAPhidgetInCodeGeneral|both of which are available in C/C++|[http://www.phidgets.com/documentation/Phidget21_C_Doc.zip C/C++ API]}}
==Common Problems and Solutions/Workarounds==


===Example Flow===
==={{ProblemSolution|Windows|My application does not compile when a function contains more than one parameter.}}===
 
{{ExamplePseudocode|In C/C++, you can name these '''event''' functions whatever you like.  You will then pass them as function pointers to the Phidget library below in the Main Code section.  This hooks them into the actual events when they occur. <br>
In the example code, the event functions common to all Phidgets are called things like '''AttachHandler()''' and '''DetachHandler()''', etc.<br><br>
Some event functions will be specific to each device, like when a tag is read on an RFID board, or when a sensor value changes on an Interface Kit.
Other functions are given in the examples to show you more detail on using your Phidget.  For example, '''DeviceInitialize()''' will show what needs to be set up for your Phidget before using it.
|Creating a Phidget software object in C is specific to the Phidget.  For a Phidget Spatial, for example, this would involve creating an object with the {{Code|CPhidgetSpatialHandle}} type, and then initializing it using the {{Code|CPhidgetSpatial_create function}}.  The examples show how to do this and other API functions.<br><br>
Other C calls follow a similar syntax - {{Code|CPhidgetXXX_function}}, where XXX is the name of your device, and function is an action available from the API for your specific Phidget.|
[http://www.phidgets.com/documentation/Phidget21_C_Doc.zip C/C++ API]}}
 
==Common Problems and Solutions/Workarounds==
{{ProblemSolution|Windows|My application does not compile when a function contains more than one parameter.}}


In Visual Basic 6.0, the common way to handle multiple parameters is to not enclose the parameters with brackets. For example, instead of:
In Visual Basic 6.0, the common way to handle multiple parameters is to not enclose the parameters with brackets. For example, instead of:
Line 297: Line 210:
<syntaxhighlight lang=vb>
<syntaxhighlight lang=vb>
Object.getProperty Parameter1, Parameter2
Object.getProperty Parameter1, Parameter2
</syntaxhighlight>
</div>
If you wish, you can run the function with the parameters enclosed in brackets if you explicitly use the {{Code|Call}} keyword when running the function. For example:
<div class="source">
<syntaxhighlight lang=vb>
Call Object.getProperty(Parameter1, Parameter2)
</syntaxhighlight>
</syntaxhighlight>
</div>
</div>

Latest revision as of 15:37, 7 June 2017

Visual Basic 6.0, developed by Microsoft is a high level programming language that uses the COM programming model.

Introduction

If this is your first time working with a Phidget, we suggest starting with the Getting Started page for your specific device. This can be found in the user guide for your device. That page will walk you through installing drivers and libraries for your operating system, and will then bring you back here to use Visual Basic 6.0 specifically.

Visual Basic 6.0 is capable of using the complete Phidget API, including events. We also provide example code in Visual Basic 6.0 for all Phidget devices.

Visual Basic 6.0 can be developed with the Microsoft Visual Basic 6 IDE.

You can compare Visual Basic 6.0 with our other supported languages.

Quick Downloads

Just need the Visual Basic 6.0 documentation, drivers, libraries, and examples? Here they are:

Documentation

Example Code

Libraries and Drivers


Getting started with Visual Basic 6.0

If you are new to writing code for Phidgets, we recommend starting by running, then modifying existing examples. This will allow you to:

  • Make sure your libraries are properly linked
  • Go from source code to a test application as quickly as possible
  • Ensure your Phidget is hooked up properly

Windows (XP/Vista/7/8)

Description of Library Files

Visual Basic 6.0 programs on Windows depend on two files, which the installers in Quick Downloads put onto your system:

  • phidget21.dll contains the actual Phidget library, which is used at run-time. By default, it is placed in C:\Windows\System32.
  • Phidget21COM.dll is the Component Object Model(COM) library and provides your project access to the Phidget ActiveX objects. Your compiler has to know where this file is, by default our installer places this file into C:\Program Files\Phidgets, so you can either point your compiler to that location, or copy and link to it in a directory for your project workspace. If you are manually installing this file, you must register it through command line by running: regsvr32 Phidget21COM.dll.

If you do not want to use our installer, you can download both files and manually install them where you want; refer to our Manual Installation Instructions.

We include instructions on using our examples and writing your own code for the Microsoft Visual Basic 6.0 IDE.

Visual Basic 6.0

Use Our Examples

To run the examples, you first download the examples and unpack them into a folder. Here, you can find a HelloWorld example program that is a simple test for any Phidget device. You will also find specific example programs for all the devices. The source file will be named the same as the software object for your device. If you are not sure what the software object for your device is, find your Phidget on our webpage, and then check the API documentation for it.

1. Open up the .vbp project into the Visual Basic IDE.

2. Next, navigate to Project → Components to ensure that your project has access to the Phidget ActiveX objects

Components

3. The Components menu will show up. Ensure that the Phidget COM library is selected. If it is not, then browse for Phidget21COM.dll and add it. By default, it is placed in C:\Program Files\Phidgets. Accept the changes.

Library

4. Navigate to Project → References and ensure that the Phidget COM library is selected.

References

5. The only thing left to do is to run the examples! Click on Run → Start.

Run

Once you have the Visual Basic 6.0 examples running, we have a teaching section below to help you follow them.

Write Your Own Code

When you are building a project from scratch, or adding Phidget function calls to an existing project, you'll need to configure your development environment to properly link the Phidget COM library. To begin:

1. Generate a new Standard EXE project.

New Project

2. Next, navigate to Project → Components to add the Phidget ActiveX objects into your project.

Components

3. The Components menu will show up. Browse for Phidget21COM.dll and add it. By default, it is placed in C:\Program Files\Phidgets. Accept the changes.

Library

4. Navigate to Project → References and ensure that the Phidget COM library is selected.

References

5. Navigate to Project → Project1 Properties, select the Make tab and ensure that the Remove information about unused ActiveX Controls checkbox is unchecked.

Unused ActiveX Controls

6. Then, you will need to declare and initialize the Phidget ActiveX object for your device.

The simplest method is to place the Phidget ActiveX object from the toolbox directly onto your form. If the toolbox is not present on your screen, navigate to View → Toolbox to show the toolbar. Next, find the ActiveX object for your device in the toolbox, and double click it to add it to the form.

Accessing Phidget ActiveX objects from the toolbox

Alternatively, you can dynamically create the Phidget ActiveX object in code. For example, for an PhidgetInterfaceKit, you would type:

Dim WithEvents PhidgetInterfaceKit As PhidgetInterfaceKit

Private Sub Form_Load()
   ...
   Set PhidgetInterfaceKit = Controls.Add("Phidget21COM.PhidgetInterfaceKit", "PhidgetInterfaceKit")
   ...
End Sub

The object name for each type of Phidget is listed in the COM API Manual. Please see the examples on how to add a reference to your particular Phidget.

The project now has access to the Phidget function calls and you are ready to begin coding.

The same teaching section which describes the examples also has further resources for programming your Phidget.

Follow the Examples

By following the instructions for your operating system and compiler above, you probably now have a working example and want to understand it better so you can change it to do what you want. This teaching section has resources for you to learn from the examples and write your own.

Your main reference for writing Visual Basic 6.0 code will be our .COM API information, with syntax for all of our functions:

  • COM API Manual (This is the complete set of functions you have available for all Phidgets)
  • Device Specific APIs - The one for your Phidget can be found in its user guide.

To learn the details behind opening, configuring, using, and closing your Phidget, try the General Phidget Programming page. That page also describes using the Phidget in an event-driven manner and in a traditional manner, both of which are available in Visual Basic 6.0.

Example Flow

The Hello World example has this general structure so you can follow along. We also have an in-depth general introduction to writing Phidget code (like open, read data, etc), as well as the COM API Manual for specific syntax:

// ----- Event and Other Functions -----

Create any Language-Specific Functions (exception handling)

Create General Attach, Detach, and Error Handling Functions:

On attach: Print Hello Message
On detach: Print Goodbye Message

 

In Visual Basic 6.0, you need to name these event functions by which events you want to catch. Using the underscore between your variable name and the event name from our .COM API (and then delegating each variable that gets passed with the event) will allow the function to be run when the event fires.
In the example code, the event functions common to all Phidgets are called things like OnAttach and OnDetach, etc.

Some event functions will be specific to each device, like when a tag is read on an RFID board, or when a sensor value changes on an Interface Kit. Other functions are given in the device-specific examples to show you more detail on using your Phidget.

// ----- Main Code -----

Create Manager Software Object
Hook Event Functions created above to Device
Open Device

Wait for 'Enter' key character input
Handle on-going attach and detach events
Print Hello and Goodbye messages
Exit upon input

Close Device

Delete Device

 

Creating a Phidget software object in Visual Basic 6.0 is specific to the Phidget. For a Phidget Spatial, for example, this would involve creating a PhidgetSpatial object. The examples show how to do this and other API functions

Code Snippets

Specific calls in Visual Basic 6 will differ in syntax from those on the General Phidget Programming page, but the concepts stay the same.  

It may help to have the General Phidget Programming page and this section open at the same time, because they parallel each other and you can refer to the Visual Basic 6 syntax.  However, many additional concepts are covered on the General Phidget Programming page on a high level, such as using multiple Phidgets, handling errors, and different styles of programming.

Step One: Initialize and Open

The open() function opens the software object, but not hardware. So, it is not a guarantee you can use the Phidget immediately.

The different types of open can be used with parameters to try and get the first device it can find, open based on its serial number, or even open across the network. The API manual lists and General Phidget Programming discusses all of the available modes that open provides.

For example, if we were using an Interface Kit Phidget board as our device, the create and open calls would look like this:

Public WithEvents PhidgetInterfaceKit1 As PhidgetInterfaceKit
Set PhidgetInterfaceKit1 = Controls.Add("Phidget21COM.PhidgetInterfaceKit", "PhidgetInterfaceKit1")

Then later, you would open the device as shown below along with the attachment of the Phidget.

Step Two: Wait for Attachment (plugging in) of the Phidget

To use the Phidget, it must be plugged in (attached). We can handle this by using event driven programming and tracking the AttachEvents and DetachEvents, or we can handle this by calling waitForAttachment. This function works for any Phidget. WaitForAttachment will block indefinitely until a connection is made to the Phidget, or an optional timeout is exceeded.

Again, if we were still using an Interface Kit Phidget board as our device (as opposed to a Spatial, or Temperature Sensor, or....), the wait for attachment would look like this:

Private Sub Form_Load()
    PhidgetInterfaceKit1.Open
    PhidgetInterfaceKit1.WaitforAttachment (3000)
End Sub

Step Three: Do Things with the Phidget

We recommend the use of event driven programming when working with Phidgets. In VB.NET we can hook an event handler into the event of a sensor changing on an Interface Kit board with the following code:

Private Sub PhidgetInterfaceKit1_OnSensorChange(ByVal Index As Long, ByVal SensorValue As Long)
    Text1.Text = Index & ":" & SensorValue
End Sub

With this function, the code inside ifKit_SensorChange will get executed every time the Phidget Interface Kit reports a change on one of its analog inputs. This is because it handles the OnSensorChange event after the underscore. Some events such as Attach and Detach belong to the base Phidget object and thus are common to all types of Phidgets. In the instance above, the sensor value read is then put into a text box (Text1) for display.

Some values can be read and sent directly to the Phidget, simply use the instance members and properties. This is also how you would set properties on the Phidget such as the output state or sensor sensitivity. For example, turning on the digital output 0 (for say, turning on an LED) on an Interface Kit board would be via:

phid.OutputState(4) = True

Step Four: Close and Delete

Make sure to close your Phidget (PhidgetInterfaceKit1.Close, for example) at the end of your program so that other programs can gain access to it.

More How-To's

The General Phidget Programming page gives more information about:

The design given in this document can also be followed for almost all Phidgets. For example, if you were using a PhidgetRFID instead of an PhidgetInterfaceKit, you would place a PhidgetRFID ActiveX object instead of a PhidgetInterfaceKit. The methods and events available would change but they can be accessed in a similar manner.

The complete set of functions you have available for all Phidgets can be found in the .COM API. You can also find more description on any device-specific function in the Device API page for your specific Phidget, which can be found in its user guide.

Common Problems and Solutions/Workarounds

Windows: My application does not compile when a function contains more than one parameter.

In Visual Basic 6.0, the common way to handle multiple parameters is to not enclose the parameters with brackets. For example, instead of:

Object.getProperty(Parameter1, Parameter2)

You should write:

Object.getProperty Parameter1, Parameter2

If you wish, you can run the function with the parameters enclosed in brackets if you explicitly use the Call keyword when running the function. For example:

Call Object.getProperty(Parameter1, Parameter2)