Language - Delphi
|Embarcadero Delphi is an integrated development environment for console, desktop graphical, web application, and mobile applications.|
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 Delphi specifically.
Delphi is capable of using the complete Phidget API. We also provide example code in Delphi for AdvancedServo, Servo, Phidget Interface Kit, Phidget IR, Encoder, and RFID.
Delphi can be developed with Windows.
You can compare Delphi with our other supported languages.
Just need the Delphi documentation, drivers, libraries, and examples? Here they are:
Libraries and Drivers
- 32-bit Windows Drivers Installer
- 64-bit Windows Drivers Installer
- Windows Driver and Library Files (Zipped)
Getting Started with Delphi
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
Delphi is a .COM-based language. Currently Windows is the only supported operating system for Delphi:
The Phidget examples were written using Borland Delphi 2005 and 7, although they also work with other versions of Delphi as described on this Delphi Language page. We include the method to import ActiveX objects onto these platforms, but our current in-depth support for using our examples and writing your own code is only for Embarcadero Delphi XE2.
Import ActiveX Objects
The ActiveX objects installed with the Phidget libraries are not automatically imported into Delphi, so to begin you will need to manually import them.
In Delphi 2005/2006:
- Go to File→New→Package - Delphi for Win32. Rename and save the package using File→Save Project As...
- Import the ActiveX component, go to Component→Import Component.
- Choose Inport ActiveX Control and click Next
- Select Phidget Library 2.1 and click Next
- Click Next
- Select ‘Add unit to [Package Name] project’ and click Finish.
- Install the ActiveX package you have created by right-mouse-clicking the package name in the Project Manager pane and selecting ‘Install’.
- Delphi should now display a confirmation that the package was installed. Click ok and save the package.
- When you open a new or existing application, you should now see all the Phidget device control objects listed under the ActiveX category.
In slightly newer versions of Delphi:
- Go to Component→Import Component...
- Choose “Import ActiveX Control” and click Next
- Pick Phidget Library 2.1 from the list and click Next
- Set the palette Page to ActiveX and check the Generate Component Wrappers option
- Choose Install into a new package and click next
- Give the package a name and description such as “Phidgets”, and then click Finish
Once installed, all future projects will be able to use the Phidget ActiveX objects.
Embarcadero Delphi XE2
Embarcadero Delphi is the more recent platform for developing Delphi on. To use it, we follow the same setup procedure as Borland, which is to first import the Phidget library as an ActiveX object. We then offer in-depth instructions on how to use the Phidget examples, both as described below.
Import ActiveX Objects
The ActiveX objects installed with the Phidget libraries are not automatically imported into Delphi, so to begin you will need to manually import them. In Embarcadero XE2, do the following:
1. Go to Component→Import Component...
2. Choose “Import ActiveX Control” and click Next:
3. Pick Phidget Library 2.1 from the list and click Next:
4. Choose Install into a new package and click next:
5. Give the package a name and description such as “Phidgets”, and then click Finish.
6. To finish, the objects need to be re-linked. When prompted to do this, click Yes:
At this point, opening a new project will have the use of the Phidget library. If you already had a project open, you will need to close and re-open it for the linking to Phidgets to occur.
Use Our Examples
After you have installed the Active X objects, you can open our examples and run code to test 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, find your Phidget on our webpage, and then check the API documentation for it.
First download the Delphi examples and unpack them. Each project has its own folder. You can open an existing project and navigate to the project file itself to open it:
Then, the project and all of its files will appear in your project navigator on the right. Plug in your Phidget to your computer, and make sure no other programs are accessing the Phidget. Right-click on the project root and select "Run". For example, for the Interface Kit Phidget, your project will probably look something like this:
The GUI form of the example will open, and you can test your device.
Write Your Own Code
In Embarcadero, the lower right panel displays the available ActiveX objects for coding. You can create a new project and then simply drag the ActiveX object that matches your Phidget device into your project.
We have a teaching section below which includes code snippets to augment the examples and help you compose your project.
Follow The Examples
By following the instructions 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 Delphi code will be our .COM API information, with syntax for all of our functions:
- .COM API (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 Delphi.
Specific calls in Delphi 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 Delphi 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
Before you can use the Phidget, you must declare and initialize its ActiveX object. The simplest method is to place the control from the ActiveX component tab on to your form. For this tutorial, we create a Phidget Interface Kit control (PhidgetInterfaceKit1) and then add a text edit field to the form for the purpose of capturing simple output. The object name for any type of Phidget is listed in the API manual. Every type of Phidget also inherits functionality from the Phidget base class.
Next, we need to tell the program to try and connect to the Phidget through a call to open(). The open will tell the program to continuously try to connect to a Phidget, based on the parameters given, even trying to reconnect if it gets disconnected:
procedure TForm1.FormCreate(Sender: TObject); begin PhidgetInterfaceKit1.Open(-1); end;
The parameters (here just a -1) can also be used to open the first Phidget of a type it can find, open based on its serial number, or even open across the network. The API manual lists all of the available modes that open provides.
One important thing to remember is that when working with Phidgets, a local connection will reserve the device until closed. This prevents any other instances from retrieving data from the Phidget, including other programs. The one connection per device limit does not apply when exclusively using the Phidget WebService. To open multiple Phidgets, they each need their own ActiveX object, and you can distinguish between them by serial number.
Step Two: Wait for Attachment (plugging in) of the Phidget
Calling open does not guarantee you can use the Phidget immediately. 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. You can put the wait function right after your open function. So we can modify our opening block to read:
procedure TForm1.FormCreate(Sender: TObject); begin PhidgetInterfaceKit1.Open(-1); PhidgetInterfaceKit1.WaitForAttachment(3000); end;
This function works for any Phidget. WaitForAttachment will block indefinitely until a connection is made to the Phidget, or an optional timeout is exceeded.
Step Three: Do Things with the Phidget
We recommend the use of event driven programming when working with Phidgets. This allows the program to execute other tasks until the Phidget fires a new event.
In Delphi, when the event library was installed as described in the Use Our Examples section, it added Phidget ActiveX components for each type of Phidget. These ActiveX components will show up in the toolbox under the ActiveX tab, usually in the lower right. The ActiveX object for your Phidget can be added to the form and then hooked to the event handlers you wish to use like any other control.
For example, for a Phidget21COMIPhidgetInterfaceKitEvents control, the event handler looks like the following:
procedure TForm1.PhidgetInterfaceKit1SensorChange(ASender: TObject; Index, SensorValue: Integer); begin Edit1.Text := IntToStr(Index) + ': ' + IntToStr(SensorValue); end;
With this method, the code inside PhidgetInterfaceKit1SensorChange will get executed every time the PhidgetInterfaceKit reports a change on one of its analog inputs. Some events such as Attach and Detach belong to the base Phidget object and thus are common to all types of Phidgets. Other events, like this sensor change one, are specific to the type of Phidget. Please refer to the COM API manual for a full list of events and their general usage.
Some values can be directly read and set on the Phidget. These functions can be used inside a polling loop as an alternative to event driven programming. Simply use the CallString such as SensorValue[Index] or OutputState[Index] for PhidgetInterfaceKits:
PhidgetInterfaceKit1.OutputState := true;
Step Four: Close and Delete
Remember that the Open call reserves the Phidget for sole use by your program. Close removes this lock. You can call Close any time outside of the Phidget's own event handlers to end the connection.
Often it’s a good idea to enable logging during development for debugging purposes. This log, depending on the level set, will record certain events and errors from Phidgets. In Delphi, this is accomplished by calling EnableLogging(logLevel, filename) on the Phidget object.
Similarly, you can call DisableLogging() at the end of your program to shut it off. Should you need to contact Phidgets for support, including this log is very helpful for revealing the cause of the problem. Please see the Programming Manual for a general discussion on Phidget logging and the levels provided.
The General Phidget Programming page gives more information about:
- Using Multiple Phidgets (or a Phidget other than the Interface Kit)
- Catching exceptions and errors and using logging
- Event catching versus direct polling
- And more....
Common Problems and Solutions/Workarounds
Embarcadero XE2: The Phidget Manager creates a runtime fault
In Delphi XE2, you cannot use the Phidget Manager as an object directly. If you need to open multiple Phidgets of the same device type, use the serial number to distinguish between them.
Embarcadero XE2 under Windows in Oracle VirtualBox: System Crash
Embarcadero Delphi does not work under Windows running as a guest on Oracle's VirtualBox. Adding an ActiveX object on such a system will crash the system and appear to destroy it, although a hard power cycle will recover the system. VMWare does not suffer from this problem, and of course native Windows 7 works fine.