Notice: This page contains information for the legacy Phidget21 Library. Phidget21 does not support VINT Phidgets, and will not support any new Phidgets. Phidget21 will be maintained until 2020. We recommend that new projects be developed against the Phidget22 Library.
1135 User Guide
|Go to this device's product page|
Checking the Contents
You should have received:
In order to test your new Phidget you will also need:
Connecting the Pieces
Testing Using Windows 2000 / XP / Vista / 7
Make sure you have the current version of the Phidget library installed on your PC. If you don't, follow these steps:
- Go to the Quick Downloads section on the Windows page
- Download and run the Phidget21 Installer (32-bit, or 64-bit, depending on your system)
- You should see the icon on the right hand corner of the Task Bar.
Running Phidgets Sample Program
Double clicking on the icon loads the Phidget Control Panel; we will use this program to ensure that your new Phidget works properly.
The source code for the InterfaceKit-full sample program can be found in the quick downloads section on the C# Language Page. If you'd like to see examples in other languages, you can visit our Languages page.
Updating Device Firmware
If an entry in this list is red, it means the firmware for that device is out of date. Double click on the entry to be given the option of updating the firmware. If you choose not to update the firmware, you can still run the example for that device after refusing.
Double Click on the icon to activate the Phidget Control Panel and make sure that the Phidget InterfaceKit 8/8/8 is properly attached to your PC.
Testing Using Mac OS X
- Go to the Quick Downloads section on the Mac OS X page
- Download and run the Phidget OS X Installer
- Click on System Preferences >> Phidgets (under Other) to activate the Preference Pane
- Make sure that the is properly attached.
- Double Click on in the Phidget Preference Pane to bring up the Sample program. This program will function in a similar way as the Windows version.
For a step-by-step guide on getting Phidgets running on Linux, check the Linux page.
Using Windows Mobile / CE 5.0 / CE 6.0
For a step-by-step guide on getting Phidgets running on Windows CE, check the Windows CE page.
The Voltage Sensor measures the differential voltage between the input terminals and outputs the difference proportionally. The maximum differential voltage that can be measured accurately is +/-30V. When the positive and negative inputs are equal, the analog output value is 2.5V. When the positive input is 30V greater than the negative input, the analog output is 4.5V and when the positive input is 30V less than the negative input, the analog output is 0.5V.
When measuring voltage levels below 5V, you'll have more accuracy if you connect the leads directly to the analog input of an interface kit.
Since the 1135 Voltage Sensor can measure a differential voltage, the common mode rejection (CMR) is an important specification. CMR refers to the amount of voltage that both input terminals of a differential amplifier can be offset without affecting the output gain. For example, if the positive terminal sees a voltage of 7V and the negative terminal sees a voltage of 5V, then the CMR would be 5V and would output a value of 2V at unity gain. For the 1135 Voltage Sensor, it is able to measure the differential voltage of +/-10V with a CMR of 40V while keeping the accuracy within 2%. Please note that the error specifications do not include the error introduced by the Analog to Digital Conversion on the Analog Input. (if you are using the 1135 with a PhidgetInterfaceKit) The majority of error introduced by the Analog to Digital conversion is from the error in the voltage reference (0.5% max), and the limitation of resolution in the SensorValue property. The best accuracy can be achieved by using a 2 or more point calibration of your system - effectively calibrating the 1135 and the PhidgetInterfaceKit in a single step. If you are calibrating, be sure to use a good quality multimeter to determine the voltage being applied.
Using RawSensorValue in the formula will increase the resolution, which is limited by SensorValue to about 67mV.
The Formula to translate SensorValue into differential voltage is:
where Vdiff is defined as Vpositive - Vnegative.
Other Interfacing Alternatives
If you want maximum accuracy, you can use the RawSensorValue property from the PhidgetInterfaceKit. To adjust a formula, substitute (SensorValue) with (RawSensorValue / 4.095) If the sensor is being interfaced to your own Analog to Digital Converter and not a Phidget device, our formulas can be modified by replacing (SensorValue) with (Vin * 200). It is important to consider the voltage reference and input voltage range of your ADC for full accuracy and range.
Analog Input Cable Connectors
Each Analog Input uses a 3-pin, 0.100 inch pitch locking connector. Pictured here is a plug with the connections labeled. The connectors are commonly available - refer to the Analog Input Primer for manufacturer part numbers.
Phidget analog sensors do not have their own API- they simply output a voltage that is converted to a digital value and accessed through the "Sensor" properties and events on the PhidgetInterfaceKit API. It is not possible to programmatically identify which sensor is attached to the Analog Input. To an InterfaceKit, every sensor looks the same. Your application will need to apply formulas from this manual to the SensorValue (an integer that ranges from 0 to 1000) to convert it into the units of the quantity being measured. For example, this is how you would use a temperature sensor in a C# program:
// set up the interfacekit object InterfaceKit IFK = new InterfaceKit(); // link the new interfacekit object to the connected board IFK.open("localhost", 5001); // Get sensorvalue from analog input zero int sensorvalue = IFK.sensors.Value; // Convert sensorvalue into temperature in degrees Celsius double roomtemp = Math.Round(((sensorvalue * 0.22222) - 61.11), 1);
See the PhidgetInterfaceKit User Guide for more information on the API and a description of our architecture.
For more code samples, find your preferred language on the Languages page.
|Date||Board Revision||Device Version||Comment|
|March 2010||0||N/A||Product Release|