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

1104 User Guide

From Phidgets Legacy Support
Revision as of 20:52, 25 July 2012 by Mparadis (talk | contribs) (Created page with "Category:UserGuide ==Getting Started== ===Checking the Contents=== {{UGbox| '''You should have received:''' * A Vibration Sensor * A Sensor Cable | '''In order to test y...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)


Getting Started

Checking the Contents

You should have received:

  • A Vibration Sensor
  • A Sensor Cable

In order to test your new Phidget you will also need:

  • A PhidgetInterfaceKit 8/8/8
  • A USB Cable

Connecting the Pieces

  1. Connect the Vibration Sensor to the Analog Input 6 on the PhidgetInterfaceKit 8/8/8 board using the sensor cable.
  2. Connect the PhidgetInterfaceKit to your PC using the USB cable.

1104 0 Connecting The Hardware.jpg

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:

  1. Go to the Quick Downloads section on the Windows page
  2. Download and run the Phidget21 Installer (32-bit, or 64-bit, depending on your system)
  3. You should see the Ph.jpg icon on the right hand corner of the Task Bar.

Running Phidgets Sample Program

Double clicking on the Ph.jpg 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 Ph.jpg icon to activate the Phidget Control Panel and make sure that the Phidget InterfaceKit 8/8/8 is properly attached to your PC.

1018 2 Control Panel Screen.jpg

Double Click on Phidget InterfaceKit

  1. 8/8/8 in the Phidget Control Panel to bring up InterfaceKit-full and check that the box labelled Attached contains the word True.
  2. Make sure that the Ratiometric box is Ticked.
  3. Lightly touch the sensor disk and you will see the Analog In value fluctuate between 0 and 1000.
  4. You can adjust the input sensitivity by moving the slider pointer.
  5. Click on the Sensors button to bring up the Advanced Sensor Form.
Sensor InterfaceKit Screen 421.jpg
  1. In the Sensor 6 box, select the 1104 - Vibration Sensor from the drop down menu.
  2. The motion of the sensor is represented here.
Note: This sensor is designed to only measure the presence of acceleration and vibration
1104 0 Advanced Sensor Form Screen.jpg

Testing Using Mac OS X

  1. Go to the Quick Downloads section on the Mac OS X page
  2. Download and run the Phidget OS X Installer
  3. Click on System Preferences >> Phidgets (under Other) to activate the Preference Pane
  4. Make sure that the Phidget InterfaceKit 8/8/8 is properly attached.
  5. Double Click on Phidget InterfaceKit 8/8/8 in the Phidget Preference Pane to bring up the InterfaceKit-full Sample program. This program will function in a similar way as the Windows version.

Using Linux

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.

Technical Details

This sensor buffers a piezoelectric transducer. As the transducer is displaced from the mechanical neutral axis, bending creates strain within the piezoelectric element and generates voltages. If the assembly is supported by its mounting points and left to vibrate “in free space” the device will behave as a form of vibration sensor. The sensing element should not be treated as a flexible switch, and is not intended to be bent.

SensorValue 500 roughly corresponds to 0g acceleration. Acceleration will deflect the sensing element up or down, causing SensorValue to swing either way. This sensor is not meant to measure precise acceleration and vibration - use it to detect an acceleration impulse, or the presence of vibration.

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.


Each Analog Input uses a 3-pin, 0.100 inch pitch locking connector. Pictured here is a plug with the connections labelled. The connectors are commonly available - refer to the Analog Input Primer for manufacturer part numbers.

Analoginput.jpg


API

We document API Calls specific to this product in this section. Functions common to all Phidgets and functions not applicable to this device are not covered here. This section is deliberately generic. For calling conventions under a specific language, refer to the associated API manual in the Quick Downloads section for that language. For exact values, refer to the device specifications.

Data Structures

Functions

Events

Product History

Date Board Revision Device Version Comment
September 2005 0 N/A Product Release
May 2008 0A N/A Redesign due to component obsolescence