Phidgets Support - User contributions [en]

I2C Adapter API Guide

2026-04-09T19:50:44Z

Lmpacent: /* I2CSendReceive() */

{{#seo:|description=Get started with your I2C Adapter Phidget}}
[[Category:IntroGuide]]
<div class="nonumtoc">
<div class="toclimit-4">
== Introduction ==
[[Image:ADP0001_0.jpg|thumb|<center>I2C Adapter Phidget (ADP0001_0)</center>]]
This guide will provide information about the DataAdapter API to get you up and running with your new I2C Adapter Phidget.

Before starting this guide, visit the Quick Start Guide on your I2C Adapter Phidget's product page for information about wiring.

== Address Format ==

The I2C Adapter Phidget interprets the device address as follows:

[[Image:I2C_Addr.png|link=|550px]]

The read/write bit is not included in the hexadecimal value for the address, as this bit is handled by the API calls.
You may find that datasheets for some I2C devices include the read/write bit, so a read-only device like a simple temperature sensor might specify the address as '''0xE3''' instead of '''0x71''' in this case. When using such a sensor, be sure to ignore the R/W bit and shift the remaining seven bits down to get the address you need to send to Phidgets API calls.

== Methods ==
=== I2CSendReceive() ===

Parameters:
* int '''address'''
* byte[ ] '''data'''
* int '''receiveLength'''

This is the main function you'll use for simple read and write operations.

* The first parameter is the I2C address of your device, usually specified in the datasheet or printed on the circuit board.
* The second parameter is the data array, which can contain up to 127 bytes. If the data array is empty, the I2C Adapter Phidget will skip sending the write address and bytes.
* The third parameter is the receive length, or the number of bytes you're expecting back from the device for this transaction. Maximum receive length is 127, and if it's zero the I2C Adapter Phidget will skip sending the read address and bytes.

This diagram illustrates the data structure when using {{Code|I2CSendReceive}}:

[[Image:I2C_SendRecv.png|link=|850px]]

''''S'''' represents a start condition, while ''''P'''' represents a stop condition. If your I2C device requires data in a different structure than this, you may need to use {{Code|I2CComplexTransaction()}}, as explained in the next section.

=== I2CComplexTransaction() ===

Parameters:
* int '''address'''
* string '''I2CPacketString'''
* byte[ ] '''data'''

This function gives you more control over the read/write structure for more complex interactions. This is useful for longer commands that make use of repeated start conditions.

* The first parameter is the I2C address of your device, usually specified in the datasheet or printed on the circuit board.
* The second parameter is a string that dictates the read/write sequence to follow.
* The third parameter is the data array, whose length must match the number of writes in the string, up to 127 bytes.

The string is made up of the following characters, case-sensitive with no spaces:
* ''''s'''' for a start condition
* ''''R'''' for a read byte
* ''''T'''' for a write byte
* ''''p'''' for a stop condition

Here's an example:

[[Image:I2C_Complex.png|link=|850px]]

Numerals can also be used after a 'T' or 'R' to make the string compact. In this example, the data array would need to have a length of 3, since a total of three bytes are written in the sequence.

I2C Adapter API Guide

2026-04-09T19:44:04Z

Lmpacent: /* Introduction */

I2C Adapter API Guide

2026-04-09T19:43:28Z

Lmpacent: /* Introduction */

{{#seo:|description=Get started with your I2C Adapter Phidget}}
[[Category:IntroGuide]]
<div class="nonumtoc">
<div class="toclimit-4">
== Introduction ==
[[Image:ADP0001_0.jpg|thumb|<center>I2C Adapter Phidget (ADP0001_0)</center>]]
This guide will provide information about the DataAdapter API to get you up and running with your new I2C Adapter Phidget.

Before starting this guide, visit the Quick Start Guide on your Adapter Phidget's product page for information about wiring.

== Address Format ==

The I2C Adapter Phidget interprets the device address as follows:

[[Image:I2C_Addr.png|link=|550px]]

The read/write bit is not included in the hexadecimal value for the address, as this bit is handled by the API calls.
You may find that datasheets for some I2C devices include the read/write bit, so a read-only device like a simple temperature sensor might specify the address as '''0xE3''' instead of '''0x71''' in this case. When using such a sensor, be sure to ignore the R/W bit and shift the remaining seven bits down to get the address you need to send to Phidgets API calls.

== Methods ==
=== I2CSendReceive() ===

Parameters:
* int '''address'''
* byte[ ] '''data'''
* int '''receiveLength'''

This is the main function you'll use for simple read and write operations.

* The first parameter is the I2C address of your device, usually specified in the datasheet or printed on the circuit board.
* The second parameter is the data array, which can contain up to 127 bytes. If the data array is empty, the I2C Adapter Phidget will skip sending the write address and bytes.
* The third parameter is the receive length, or the number of bytes you're expecting back from the device for this transaction. Maximum receive length is 127, and if it's zero the I2C Adapter Phidget will skip sending the read address and bytes.

This diagram illustrates the data structure when using {{Code|I2CSendReceive}}:

[[Image:I2C_SendRecv.png|link=|850px]]

''''S'''' represents a start condition, while ''''P'''' represents a stop condition. If your I2C device requires data in a different structure than this, you may need to use {{Code|I2CComplexTransaction()}}, as explained in the next section.

=== I2CComplexTransaction() ===

Parameters:
* int '''address'''
* string '''I2CPacketString'''
* byte[ ] '''data'''

This function gives you more control over the read/write structure for more complex interactions. This is useful for longer commands that make use of repeated start conditions.

* The first parameter is the I2C address of your device, usually specified in the datasheet or printed on the circuit board.
* The second parameter is a string that dictates the read/write sequence to follow.
* The third parameter is the data array, whose length must match the number of writes in the string, up to 127 bytes.

The string is made up of the following characters, case-sensitive with no spaces:
* ''''s'''' for a start condition
* ''''R'''' for a read byte
* ''''T'''' for a write byte
* ''''p'''' for a stop condition

Here's an example:

[[Image:I2C_Complex.png|link=|850px]]

Numerals can also be used after a 'T' or 'R' to make the string compact. In this example, the data array would need to have a length of 3, since a total of three bytes are written in the sequence.

File:ADP0001 0.jpg

2026-04-09T19:42:20Z

Lmpacent:

Language - Java

2026-04-02T16:40:00Z

Lmpacent: /* Deploying Applications */

{{#seo:|description=Learn how to use Phidget USB devices with Java.}}
[[Category:Language]]

==Get Started==
With the Phidget22 library, it's easy to create Java applications that work with Phidget devices.

==Java Libraries==
During development, we recommend downloading the appropriate installer or package for your [https://www.phidgets.com/docs/Operating_System_Support operating system]. This will place the required Phidget library files in standard locations where Java will look for them. When [[#Deploying Applications|deploying applications]], you can instead include these files manually as part of your application.

====macOS Considerations====
Legacy Phidgets running a HID USB stack require a driver extension (macOS 10.15 and newer) or a kernel extension (macOS 10.14 and earlier). During development, we recommend downloading the appropriate [https://www.phidgets.com/docs/OS_-_macOS#Quick_Downloads package] which will install the extension. When deploying applications, review the README in the [https://cdn.phidgets.com/downloads/phidget22/libraries/macos/Phidget22_macosdevel.zip macOS Development Files] for information about bundling the extension with your application.

=====Determining USB Stack=====
To determine which USB stack your device is running, navigate to the product page and then to the specification tab, and look for the ''USB Stack'' specification. If you are using a VINT device, navigate to the product page for the VINT Hub you are using.

[[Image:Javascript_networkserver_webusb_spec.png|center|600px|link=https://cdn.phidgets.com/docs/images/8/80/Javascript_networkserver_webusb_spec.png]]

====Linux Considerations====
Linux restricts access to USB devices to the root user. To run your Python application as a regular user, you'll need to [{{SERVER}}/docs/OS_-_Linux#Setting_Udev_Rules set up udev rules] on your system.

==Development Environment Configuration==

Before choosing a development environment, make sure you have the [http://www.oracle.com/technetwork/java/index.html Java Development Kit] installed.

===Visual Studio Code===
{| style="margin:auto;" class="table-no-border mw-collapsible mw-collapsed"
|+ '''Instructions'''
| To start developing with Java in VSCode, open it up and install the '''Extension Pack for Java'''.||[[Image:Language_java_vscode_extension2.png|center|350px|link=https://cdn.phidgets.com/docs/images/b/b4/Language_java_vscode_extension2.png]]
|-
| Next, press '''Ctrl+Shift+P''' to open the command palette, type "java" and select '''Java: Create Java Project'''. || [[Image:Language_java_vscode_createproj.png|center|360px|link=https://cdn.phidgets.com/docs/images/7/78/Language_java_vscode_createproj.png]]
|-
| Select "No Build Tools" and select a directory for the new project. You'll be asked for a project name, and VSCode will create the directory structure. || [[Image:Language_java_vscode_emptyproj.png|center|350px|link=https://cdn.phidgets.com/docs/images/c/c1/Language_java_vscode_emptyproj.png]]
|-
| colspan="2"|You'll need to get a copy of '''phidget22.jar''' to put inside the "lib" folder. [https://www.phidgets.com/downloads/phidget22/libraries/any/Phidget22Java.zip You can download phidget22.jar here].
|-
| colspan="2"| You can now begin writing code in the newly created "App.java" file, or you can download a [[#Example_Code|sample program]] for your device and place it in the "src" folder.
|-
| Compile and run by pressing '''F5''' or by clicking the play button in the top right. || [[Image:Language_java_vscode_run.png|center|350px|link=https://cdn.phidgets.com/docs/images/e/ea/Language_java_vscode_run.png]]
|-
| Once you're ready to compile your project into a .jar executable, click on the '''Java Projects''' section in the explorer. || [[Image:Language_java_vscode_jar.png|center|350px|link=https://cdn.phidgets.com/docs/images/6/65/Language_java_vscode_jar.png]]
|-
| Click on the export icon, and then select your main class and click OK. || [[Image:Language_java_vscode_jar2.png|center|350px|link=https://cdn.phidgets.com/docs/images/7/74/Language_java_vscode_jar2.png]]
|-
| colspan="2"| Now you can run your new .jar file with the following command:
<syntaxhighlight>
java -jar Example.jar
</syntaxhighlight>
|}

===Javac===
{| style="margin:auto;" class="table-no-border mw-collapsible mw-collapsed"
|+ '''Instructions'''
|The easiest way to allow Java to access the Phidgets Java library is to place a copy of '''phidget22.jar''' in the same folder as your .java program. ||[[Image:Language_java_javac_folder.png|center|350px|link=https://cdn.phidgets.com/docs/images/8/89/Language_java_javac_folder.png]]
|-
|[https://www.phidgets.com/downloads/phidget22/libraries/any/Phidget22Java.zip You can download phidget22.jar here].||
|-
|colspan="2"|To run your program, enter the following command in the command prompt or terminal:
<syntaxhighlight>
javac -classpath .;phidget22.jar example.java
</syntaxhighlight>
Then, enter the following command to run the program:
<syntaxhighlight>
java -classpath .;phidget22.jar example
</syntaxhighlight>
||
|-
| colspan="2"| Once you're ready to compile your project into a .jar executable, create a '''manifest.mf''' file with the following contents:
<syntaxhighlight>
Manifest-Version: 1.0
Main-Class: example
Class-Path: phidget22.jar

</syntaxhighlight>
Make sure there's an empty newline at the bottom of the three lines and a space after each colon.
|-
| colspan="2"| Next, create the .jar file with this command:
<syntaxhighlight>
jar cfm example.jar manifest.mf *.class
</syntaxhighlight>
Once the .jar is created, you can execute it with
<syntaxhighlight>
java -jar example.jar
</syntaxhighlight>

|}

===Netbeans===
{| style="margin:auto;" class="table-no-border mw-collapsible mw-collapsed"
|+ '''Instructions'''
|The easiest way to allow Java to access the Phidgets Java library is to place a copy of '''phidget22.jar''' in the same folder as your .java program. ||[[Image:Language_java_javac_folder.png|center|350px|link=https://cdn.phidgets.com/docs/images/8/89/Language_java_javac_folder.png]]
|-
|[https://www.phidgets.com/downloads/phidget22/libraries/any/Phidget22Java.zip You can download phidget22.jar here].||
|-
| To start, open NetBeans and create a new project. Select Java Application and follow the steps as directed by Netbeans.|| [[Image:Windows_netbeans1.jpg|center|350px|link=https://cdn.phidgets.com/docs/images/c/c9/Windows_netbeans1.jpg]]
|-
| Next, add a reference to phidget22.jar by right-clicking on the libraries folder. || [[Image:Windows_netbeans2.jpg|center|350px|link=https://cdn.phidgets.com/docs/images/2/2b/Windows_netbeans2.jpg]]
|-
| Navigate to the folder where you downloaded phidget22.jar, and select it. || [[Image:Windows_netbeans3.jpg|center|350px|link=https://cdn.phidgets.com/docs/images/7/76/Windows_netbeans3.jpg]]
|-
| The project now has access to Phidgets. By default, Netbeans should create an executable .jar file in the '''dist''' folder of the project directory when it's built. If it didn't, go to '''Build -> Packaging''' in the project properties and make sure "Build JAR after compiling" is checked.|| [[Image:Windows_netbeans4.png|center|350px|link=https://cdn.phidgets.com/docs/images/7/78/Windows_netbeans4.png]]
|-
| colspan="2"| You can now run the .jar file from the command prompt with:
<syntaxhighlight>
java -jar phidgetTest.jar
</syntaxhighlight>
|}

===Eclipse===
{| style="margin:auto;" class="table-no-border mw-collapsible mw-collapsed"
|+ '''Instructions'''
| To start, open Eclipse and create a new Java project. Name the project and uncheck the '''create module-info.java file''' box.|| [[Image:java_eclipse_newproj.png|center|350px|link=https://cdn.phidgets.com/docs/images/9/97/Java_eclipse_newproj.png]]
|-
| On the Libraries tab, click Add External JARs and add [https://www.phidgets.com/downloads/phidget22/libraries/any/Phidget22Java.zip phidget22.jar]. to your project as an external jar. Be sure it's being added to the '''Classpath''' and not the module path. || [[Image:java_eclipse_library.png|center|350px|link=https://cdn.phidgets.com/docs/images/1/1b/Java_eclipse_library.png]]
|-
| Create a new Class in your project. || [[Image:java_eclipse_newclass.png|center|350px|link=https://cdn.phidgets.com/docs/images/0/02/Java_eclipse_newclass.png]]
|-
| Name the class, and be sure to check the '''public static void main''' box. Eclipse may require that you add a package name. || [[Image:java_eclipse_newclass2.png|center|350px|link=https://cdn.phidgets.com/docs/images/c/ca/Java_eclipse_newclass2.png]]
|-
| Your project now has access to Phidgets! ||
|-
| Once you're ready to compile your project into a .jar executable, right click on the project in the package explorer and choose '''Export'''. Select '''Runnable JAR file'''. || [[Image:java_eclipse_export.png|center|350px|link=https://cdn.phidgets.com/docs/images/8/8c/Java_eclipse_export.png]]
|-
| Choose the main class and a destination for the .jar file and click finish. || [[Image:java_eclipse_export2.png|center|350px|link=https://cdn.phidgets.com/docs/images/8/8d/Java_eclipse_export2.png]]
|-
| colspan="2"| You can now run the .jar file from the command prompt with:
<syntaxhighlight>
java -jar phidgetTest.jar
</syntaxhighlight>
|}

=== PhidgetSBC Web Interface ===
{| style="margin:auto;" class="table-no-border mw-collapsible mw-collapsed"
|+'''Instructions'''
|<center>{{#ev:youtube|gZmWvWXICIA|rel=0}}</center>
|}

==Example Code==
Navigate to our [https://www.phidgets.com/?view=code_samples&lang=Java Code Sample Generator] to view and download code samples that are tailored to your specific device.

[[Image:Language_java_codesample.png|center|600px|link=https://cdn.phidgets.com/docs/images/a/af/Language_java_codesample.png]]

===Phidget Programming Basics===
{{PhidgetProgrammingBasicsLink}}

== Deploying Applications ==
The following files are required for your Java application:
* phidget22.jar
* phidget22.dll
* phidget22java.dll

The files can be found in the [https://cdn.phidgets.com/downloads/phidget22/libraries/windows/Phidget22-windevel.zip Development Files]. The .jar file is in lib/java, and the dll files are in lib/c/x64.

Java will look for these files in several locations, including the classpath and the working folder of the project.

==API==
[{{SERVER}}/?view=api&lang=Python Phidget22 API]

Language - Java

2026-04-02T16:38:13Z

Lmpacent: /* Java Libraries */

{{#seo:|description=Learn how to use Phidget USB devices with Java.}}
[[Category:Language]]

==Get Started==
With the Phidget22 library, it's easy to create Java applications that work with Phidget devices.

==Java Libraries==
During development, we recommend downloading the appropriate installer or package for your [https://www.phidgets.com/docs/Operating_System_Support operating system]. This will place the required Phidget library files in standard locations where Java will look for them. When [[#Deploying Applications|deploying applications]], you can instead include these files manually as part of your application.

====macOS Considerations====
Legacy Phidgets running a HID USB stack require a driver extension (macOS 10.15 and newer) or a kernel extension (macOS 10.14 and earlier). During development, we recommend downloading the appropriate [https://www.phidgets.com/docs/OS_-_macOS#Quick_Downloads package] which will install the extension. When deploying applications, review the README in the [https://cdn.phidgets.com/downloads/phidget22/libraries/macos/Phidget22_macosdevel.zip macOS Development Files] for information about bundling the extension with your application.

=====Determining USB Stack=====
To determine which USB stack your device is running, navigate to the product page and then to the specification tab, and look for the ''USB Stack'' specification. If you are using a VINT device, navigate to the product page for the VINT Hub you are using.

[[Image:Javascript_networkserver_webusb_spec.png|center|600px|link=https://cdn.phidgets.com/docs/images/8/80/Javascript_networkserver_webusb_spec.png]]

====Linux Considerations====
Linux restricts access to USB devices to the root user. To run your Python application as a regular user, you'll need to [{{SERVER}}/docs/OS_-_Linux#Setting_Udev_Rules set up udev rules] on your system.

==Development Environment Configuration==

Before choosing a development environment, make sure you have the [http://www.oracle.com/technetwork/java/index.html Java Development Kit] installed.

===Visual Studio Code===
{| style="margin:auto;" class="table-no-border mw-collapsible mw-collapsed"
|+ '''Instructions'''
| To start developing with Java in VSCode, open it up and install the '''Extension Pack for Java'''.||[[Image:Language_java_vscode_extension2.png|center|350px|link=https://cdn.phidgets.com/docs/images/b/b4/Language_java_vscode_extension2.png]]
|-
| Next, press '''Ctrl+Shift+P''' to open the command palette, type "java" and select '''Java: Create Java Project'''. || [[Image:Language_java_vscode_createproj.png|center|360px|link=https://cdn.phidgets.com/docs/images/7/78/Language_java_vscode_createproj.png]]
|-
| Select "No Build Tools" and select a directory for the new project. You'll be asked for a project name, and VSCode will create the directory structure. || [[Image:Language_java_vscode_emptyproj.png|center|350px|link=https://cdn.phidgets.com/docs/images/c/c1/Language_java_vscode_emptyproj.png]]
|-
| colspan="2"|You'll need to get a copy of '''phidget22.jar''' to put inside the "lib" folder. [https://www.phidgets.com/downloads/phidget22/libraries/any/Phidget22Java.zip You can download phidget22.jar here].
|-
| colspan="2"| You can now begin writing code in the newly created "App.java" file, or you can download a [[#Example_Code|sample program]] for your device and place it in the "src" folder.
|-
| Compile and run by pressing '''F5''' or by clicking the play button in the top right. || [[Image:Language_java_vscode_run.png|center|350px|link=https://cdn.phidgets.com/docs/images/e/ea/Language_java_vscode_run.png]]
|-
| Once you're ready to compile your project into a .jar executable, click on the '''Java Projects''' section in the explorer. || [[Image:Language_java_vscode_jar.png|center|350px|link=https://cdn.phidgets.com/docs/images/6/65/Language_java_vscode_jar.png]]
|-
| Click on the export icon, and then select your main class and click OK. || [[Image:Language_java_vscode_jar2.png|center|350px|link=https://cdn.phidgets.com/docs/images/7/74/Language_java_vscode_jar2.png]]
|-
| colspan="2"| Now you can run your new .jar file with the following command:
<syntaxhighlight>
java -jar Example.jar
</syntaxhighlight>
|}

===Javac===
{| style="margin:auto;" class="table-no-border mw-collapsible mw-collapsed"
|+ '''Instructions'''
|The easiest way to allow Java to access the Phidgets Java library is to place a copy of '''phidget22.jar''' in the same folder as your .java program. ||[[Image:Language_java_javac_folder.png|center|350px|link=https://cdn.phidgets.com/docs/images/8/89/Language_java_javac_folder.png]]
|-
|[https://www.phidgets.com/downloads/phidget22/libraries/any/Phidget22Java.zip You can download phidget22.jar here].||
|-
|colspan="2"|To run your program, enter the following command in the command prompt or terminal:
<syntaxhighlight>
javac -classpath .;phidget22.jar example.java
</syntaxhighlight>
Then, enter the following command to run the program:
<syntaxhighlight>
java -classpath .;phidget22.jar example
</syntaxhighlight>
||
|-
| colspan="2"| Once you're ready to compile your project into a .jar executable, create a '''manifest.mf''' file with the following contents:
<syntaxhighlight>
Manifest-Version: 1.0
Main-Class: example
Class-Path: phidget22.jar

</syntaxhighlight>
Make sure there's an empty newline at the bottom of the three lines and a space after each colon.
|-
| colspan="2"| Next, create the .jar file with this command:
<syntaxhighlight>
jar cfm example.jar manifest.mf *.class
</syntaxhighlight>
Once the .jar is created, you can execute it with
<syntaxhighlight>
java -jar example.jar
</syntaxhighlight>

|}

===Netbeans===
{| style="margin:auto;" class="table-no-border mw-collapsible mw-collapsed"
|+ '''Instructions'''
|The easiest way to allow Java to access the Phidgets Java library is to place a copy of '''phidget22.jar''' in the same folder as your .java program. ||[[Image:Language_java_javac_folder.png|center|350px|link=https://cdn.phidgets.com/docs/images/8/89/Language_java_javac_folder.png]]
|-
|[https://www.phidgets.com/downloads/phidget22/libraries/any/Phidget22Java.zip You can download phidget22.jar here].||
|-
| To start, open NetBeans and create a new project. Select Java Application and follow the steps as directed by Netbeans.|| [[Image:Windows_netbeans1.jpg|center|350px|link=https://cdn.phidgets.com/docs/images/c/c9/Windows_netbeans1.jpg]]
|-
| Next, add a reference to phidget22.jar by right-clicking on the libraries folder. || [[Image:Windows_netbeans2.jpg|center|350px|link=https://cdn.phidgets.com/docs/images/2/2b/Windows_netbeans2.jpg]]
|-
| Navigate to the folder where you downloaded phidget22.jar, and select it. || [[Image:Windows_netbeans3.jpg|center|350px|link=https://cdn.phidgets.com/docs/images/7/76/Windows_netbeans3.jpg]]
|-
| The project now has access to Phidgets. By default, Netbeans should create an executable .jar file in the '''dist''' folder of the project directory when it's built. If it didn't, go to '''Build -> Packaging''' in the project properties and make sure "Build JAR after compiling" is checked.|| [[Image:Windows_netbeans4.png|center|350px|link=https://cdn.phidgets.com/docs/images/7/78/Windows_netbeans4.png]]
|-
| colspan="2"| You can now run the .jar file from the command prompt with:
<syntaxhighlight>
java -jar phidgetTest.jar
</syntaxhighlight>
|}

===Eclipse===
{| style="margin:auto;" class="table-no-border mw-collapsible mw-collapsed"
|+ '''Instructions'''
| To start, open Eclipse and create a new Java project. Name the project and uncheck the '''create module-info.java file''' box.|| [[Image:java_eclipse_newproj.png|center|350px|link=https://cdn.phidgets.com/docs/images/9/97/Java_eclipse_newproj.png]]
|-
| On the Libraries tab, click Add External JARs and add [https://www.phidgets.com/downloads/phidget22/libraries/any/Phidget22Java.zip phidget22.jar]. to your project as an external jar. Be sure it's being added to the '''Classpath''' and not the module path. || [[Image:java_eclipse_library.png|center|350px|link=https://cdn.phidgets.com/docs/images/1/1b/Java_eclipse_library.png]]
|-
| Create a new Class in your project. || [[Image:java_eclipse_newclass.png|center|350px|link=https://cdn.phidgets.com/docs/images/0/02/Java_eclipse_newclass.png]]
|-
| Name the class, and be sure to check the '''public static void main''' box. Eclipse may require that you add a package name. || [[Image:java_eclipse_newclass2.png|center|350px|link=https://cdn.phidgets.com/docs/images/c/ca/Java_eclipse_newclass2.png]]
|-
| Your project now has access to Phidgets! ||
|-
| Once you're ready to compile your project into a .jar executable, right click on the project in the package explorer and choose '''Export'''. Select '''Runnable JAR file'''. || [[Image:java_eclipse_export.png|center|350px|link=https://cdn.phidgets.com/docs/images/8/8c/Java_eclipse_export.png]]
|-
| Choose the main class and a destination for the .jar file and click finish. || [[Image:java_eclipse_export2.png|center|350px|link=https://cdn.phidgets.com/docs/images/8/8d/Java_eclipse_export2.png]]
|-
| colspan="2"| You can now run the .jar file from the command prompt with:
<syntaxhighlight>
java -jar phidgetTest.jar
</syntaxhighlight>
|}

=== PhidgetSBC Web Interface ===
{| style="margin:auto;" class="table-no-border mw-collapsible mw-collapsed"
|+'''Instructions'''
|<center>{{#ev:youtube|gZmWvWXICIA|rel=0}}</center>
|}

==Example Code==
Navigate to our [https://www.phidgets.com/?view=code_samples&lang=Java Code Sample Generator] to view and download code samples that are tailored to your specific device.

[[Image:Language_java_codesample.png|center|600px|link=https://cdn.phidgets.com/docs/images/a/af/Language_java_codesample.png]]

===Phidget Programming Basics===
{{PhidgetProgrammingBasicsLink}}

== Deploying Applications ==

If you're planning to deploy your application, it should be noted that you don't strictly need the Phidget Drivers installed.

At a minimum, these three files are required:
* phidget22.jar
* phidget22.dll
* phidget22java.dll

All three files can be found in the [https://cdn.phidgets.com/downloads/phidget22/libraries/windows/Phidget22-windevel.zip Development Files]. The .jar file is in lib/java, and the .dll files are in lib/c/x64.

Java will look for these files in several locations, including the classpath and the working folder of the project.

==API==
[{{SERVER}}/?view=api&lang=Python Phidget22 API]

Language - Java

2026-04-02T16:37:19Z

Lmpacent: /* Java Libraries */

{{#seo:|description=Learn how to use Phidget USB devices with Java.}}
[[Category:Language]]

==Get Started==
With the Phidget22 library, it's easy to create Java applications that work with Phidget devices.

==Java Libraries==
During development, we recommend downloading the appropriate installer or package for your [https://www.phidgets.com/docs/Operating_System_Support operating system]. This will put required Phidget library files in standard locations where Java will look for them. When [[#Deploying Applications|deploying applications]], you can manually include these files yourself as part of your application.

====macOS Considerations====
Legacy Phidgets running a HID USB stack require a driver extension (macOS 10.15 and newer) or a kernel extension (macOS 10.14 and earlier). During development, we recommend downloading the appropriate [https://www.phidgets.com/docs/OS_-_macOS#Quick_Downloads package] which will install the extension. When deploying applications, review the README in the [https://cdn.phidgets.com/downloads/phidget22/libraries/macos/Phidget22_macosdevel.zip macOS Development Files] for information about bundling the extension with your application.

=====Determining USB Stack=====
To determine which USB stack your device is running, navigate to the product page and then to the specification tab, and look for the ''USB Stack'' specification. If you are using a VINT device, navigate to the product page for the VINT Hub you are using.

[[Image:Javascript_networkserver_webusb_spec.png|center|600px|link=https://cdn.phidgets.com/docs/images/8/80/Javascript_networkserver_webusb_spec.png]]

====Linux Considerations====
Linux restricts access to USB devices to the root user. To run your Python application as a regular user, you'll need to [{{SERVER}}/docs/OS_-_Linux#Setting_Udev_Rules set up udev rules] on your system.

==Development Environment Configuration==

Before choosing a development environment, make sure you have the [http://www.oracle.com/technetwork/java/index.html Java Development Kit] installed.

===Visual Studio Code===
{| style="margin:auto;" class="table-no-border mw-collapsible mw-collapsed"
|+ '''Instructions'''
| To start developing with Java in VSCode, open it up and install the '''Extension Pack for Java'''.||[[Image:Language_java_vscode_extension2.png|center|350px|link=https://cdn.phidgets.com/docs/images/b/b4/Language_java_vscode_extension2.png]]
|-
| Next, press '''Ctrl+Shift+P''' to open the command palette, type "java" and select '''Java: Create Java Project'''. || [[Image:Language_java_vscode_createproj.png|center|360px|link=https://cdn.phidgets.com/docs/images/7/78/Language_java_vscode_createproj.png]]
|-
| Select "No Build Tools" and select a directory for the new project. You'll be asked for a project name, and VSCode will create the directory structure. || [[Image:Language_java_vscode_emptyproj.png|center|350px|link=https://cdn.phidgets.com/docs/images/c/c1/Language_java_vscode_emptyproj.png]]
|-
| colspan="2"|You'll need to get a copy of '''phidget22.jar''' to put inside the "lib" folder. [https://www.phidgets.com/downloads/phidget22/libraries/any/Phidget22Java.zip You can download phidget22.jar here].
|-
| colspan="2"| You can now begin writing code in the newly created "App.java" file, or you can download a [[#Example_Code|sample program]] for your device and place it in the "src" folder.
|-
| Compile and run by pressing '''F5''' or by clicking the play button in the top right. || [[Image:Language_java_vscode_run.png|center|350px|link=https://cdn.phidgets.com/docs/images/e/ea/Language_java_vscode_run.png]]
|-
| Once you're ready to compile your project into a .jar executable, click on the '''Java Projects''' section in the explorer. || [[Image:Language_java_vscode_jar.png|center|350px|link=https://cdn.phidgets.com/docs/images/6/65/Language_java_vscode_jar.png]]
|-
| Click on the export icon, and then select your main class and click OK. || [[Image:Language_java_vscode_jar2.png|center|350px|link=https://cdn.phidgets.com/docs/images/7/74/Language_java_vscode_jar2.png]]
|-
| colspan="2"| Now you can run your new .jar file with the following command:
<syntaxhighlight>
java -jar Example.jar
</syntaxhighlight>
|}

===Javac===
{| style="margin:auto;" class="table-no-border mw-collapsible mw-collapsed"
|+ '''Instructions'''
|The easiest way to allow Java to access the Phidgets Java library is to place a copy of '''phidget22.jar''' in the same folder as your .java program. ||[[Image:Language_java_javac_folder.png|center|350px|link=https://cdn.phidgets.com/docs/images/8/89/Language_java_javac_folder.png]]
|-
|[https://www.phidgets.com/downloads/phidget22/libraries/any/Phidget22Java.zip You can download phidget22.jar here].||
|-
|colspan="2"|To run your program, enter the following command in the command prompt or terminal:
<syntaxhighlight>
javac -classpath .;phidget22.jar example.java
</syntaxhighlight>
Then, enter the following command to run the program:
<syntaxhighlight>
java -classpath .;phidget22.jar example
</syntaxhighlight>
||
|-
| colspan="2"| Once you're ready to compile your project into a .jar executable, create a '''manifest.mf''' file with the following contents:
<syntaxhighlight>
Manifest-Version: 1.0
Main-Class: example
Class-Path: phidget22.jar

</syntaxhighlight>
Make sure there's an empty newline at the bottom of the three lines and a space after each colon.
|-
| colspan="2"| Next, create the .jar file with this command:
<syntaxhighlight>
jar cfm example.jar manifest.mf *.class
</syntaxhighlight>
Once the .jar is created, you can execute it with
<syntaxhighlight>
java -jar example.jar
</syntaxhighlight>

|}

===Netbeans===
{| style="margin:auto;" class="table-no-border mw-collapsible mw-collapsed"
|+ '''Instructions'''
|The easiest way to allow Java to access the Phidgets Java library is to place a copy of '''phidget22.jar''' in the same folder as your .java program. ||[[Image:Language_java_javac_folder.png|center|350px|link=https://cdn.phidgets.com/docs/images/8/89/Language_java_javac_folder.png]]
|-
|[https://www.phidgets.com/downloads/phidget22/libraries/any/Phidget22Java.zip You can download phidget22.jar here].||
|-
| To start, open NetBeans and create a new project. Select Java Application and follow the steps as directed by Netbeans.|| [[Image:Windows_netbeans1.jpg|center|350px|link=https://cdn.phidgets.com/docs/images/c/c9/Windows_netbeans1.jpg]]
|-
| Next, add a reference to phidget22.jar by right-clicking on the libraries folder. || [[Image:Windows_netbeans2.jpg|center|350px|link=https://cdn.phidgets.com/docs/images/2/2b/Windows_netbeans2.jpg]]
|-
| Navigate to the folder where you downloaded phidget22.jar, and select it. || [[Image:Windows_netbeans3.jpg|center|350px|link=https://cdn.phidgets.com/docs/images/7/76/Windows_netbeans3.jpg]]
|-
| The project now has access to Phidgets. By default, Netbeans should create an executable .jar file in the '''dist''' folder of the project directory when it's built. If it didn't, go to '''Build -> Packaging''' in the project properties and make sure "Build JAR after compiling" is checked.|| [[Image:Windows_netbeans4.png|center|350px|link=https://cdn.phidgets.com/docs/images/7/78/Windows_netbeans4.png]]
|-
| colspan="2"| You can now run the .jar file from the command prompt with:
<syntaxhighlight>
java -jar phidgetTest.jar
</syntaxhighlight>
|}

===Eclipse===
{| style="margin:auto;" class="table-no-border mw-collapsible mw-collapsed"
|+ '''Instructions'''
| To start, open Eclipse and create a new Java project. Name the project and uncheck the '''create module-info.java file''' box.|| [[Image:java_eclipse_newproj.png|center|350px|link=https://cdn.phidgets.com/docs/images/9/97/Java_eclipse_newproj.png]]
|-
| On the Libraries tab, click Add External JARs and add [https://www.phidgets.com/downloads/phidget22/libraries/any/Phidget22Java.zip phidget22.jar]. to your project as an external jar. Be sure it's being added to the '''Classpath''' and not the module path. || [[Image:java_eclipse_library.png|center|350px|link=https://cdn.phidgets.com/docs/images/1/1b/Java_eclipse_library.png]]
|-
| Create a new Class in your project. || [[Image:java_eclipse_newclass.png|center|350px|link=https://cdn.phidgets.com/docs/images/0/02/Java_eclipse_newclass.png]]
|-
| Name the class, and be sure to check the '''public static void main''' box. Eclipse may require that you add a package name. || [[Image:java_eclipse_newclass2.png|center|350px|link=https://cdn.phidgets.com/docs/images/c/ca/Java_eclipse_newclass2.png]]
|-
| Your project now has access to Phidgets! ||
|-
| Once you're ready to compile your project into a .jar executable, right click on the project in the package explorer and choose '''Export'''. Select '''Runnable JAR file'''. || [[Image:java_eclipse_export.png|center|350px|link=https://cdn.phidgets.com/docs/images/8/8c/Java_eclipse_export.png]]
|-
| Choose the main class and a destination for the .jar file and click finish. || [[Image:java_eclipse_export2.png|center|350px|link=https://cdn.phidgets.com/docs/images/8/8d/Java_eclipse_export2.png]]
|-
| colspan="2"| You can now run the .jar file from the command prompt with:
<syntaxhighlight>
java -jar phidgetTest.jar
</syntaxhighlight>
|}

=== PhidgetSBC Web Interface ===
{| style="margin:auto;" class="table-no-border mw-collapsible mw-collapsed"
|+'''Instructions'''
|<center>{{#ev:youtube|gZmWvWXICIA|rel=0}}</center>
|}

==Example Code==
Navigate to our [https://www.phidgets.com/?view=code_samples&lang=Java Code Sample Generator] to view and download code samples that are tailored to your specific device.

[[Image:Language_java_codesample.png|center|600px|link=https://cdn.phidgets.com/docs/images/a/af/Language_java_codesample.png]]

===Phidget Programming Basics===
{{PhidgetProgrammingBasicsLink}}

== Deploying Applications ==

If you're planning to deploy your application, it should be noted that you don't strictly need the Phidget Drivers installed.

At a minimum, these three files are required:
* phidget22.jar
* phidget22.dll
* phidget22java.dll

All three files can be found in the [https://cdn.phidgets.com/downloads/phidget22/libraries/windows/Phidget22-windevel.zip Development Files]. The .jar file is in lib/java, and the .dll files are in lib/c/x64.

Java will look for these files in several locations, including the classpath and the working folder of the project.

==API==
[{{SERVER}}/?view=api&lang=Python Phidget22 API]

Language - Java

2026-04-02T16:11:15Z

Lmpacent:

{{#seo:|description=Learn how to use Phidget USB devices with Java.}}
[[Category:Language]]

==Get Started==
With the Phidget22 library, it's easy to create Java applications that work with Phidget devices.

==Java Libraries==

We recommend installing the [https://www.phidgets.com/docs/Operating_System_Support Phidget drivers] for your operating system. Installing the drivers will put required .dll files in the proper place where Java will look for them. If you want to run your application on a computer without installing our drivers, see the [[#Deploying Applications|Deploying Applications]] section.

====macOS Considerations====
Legacy Phidgets running a HID USB stack require a driver extension (macOS 10.15 and newer) or a kernel extension (macOS 10.14 and earlier). During development, we recommend downloading the appropriate [https://www.phidgets.com/docs/OS_-_macOS#Quick_Downloads package] which will install the extension. When deploying applications, review the README in the [https://cdn.phidgets.com/downloads/phidget22/libraries/macos/Phidget22_macosdevel.zip macOS Development Files] for information about bundling the extension with your application.

=====Determining USB Stack=====
To determine which USB stack your device is running, navigate to the product page and then to the specification tab, and look for the ''USB Stack'' specification. If you are using a VINT device, navigate to the product page for the VINT Hub you are using.

[[Image:Javascript_networkserver_webusb_spec.png|center|600px|link=https://cdn.phidgets.com/docs/images/8/80/Javascript_networkserver_webusb_spec.png]]

====Linux Considerations====
Linux restricts access to USB devices to the root user. To run your Python application as a regular user, you'll need to [{{SERVER}}/docs/OS_-_Linux#Setting_Udev_Rules set up udev rules] on your system.

==Development Environment Configuration==

Before choosing a development environment, make sure you have the [http://www.oracle.com/technetwork/java/index.html Java Development Kit] installed.

===Visual Studio Code===
{| style="margin:auto;" class="table-no-border mw-collapsible mw-collapsed"
|+ '''Instructions'''
| To start developing with Java in VSCode, open it up and install the '''Extension Pack for Java'''.||[[Image:Language_java_vscode_extension2.png|center|350px|link=https://cdn.phidgets.com/docs/images/b/b4/Language_java_vscode_extension2.png]]
|-
| Next, press '''Ctrl+Shift+P''' to open the command palette, type "java" and select '''Java: Create Java Project'''. || [[Image:Language_java_vscode_createproj.png|center|360px|link=https://cdn.phidgets.com/docs/images/7/78/Language_java_vscode_createproj.png]]
|-
| Select "No Build Tools" and select a directory for the new project. You'll be asked for a project name, and VSCode will create the directory structure. || [[Image:Language_java_vscode_emptyproj.png|center|350px|link=https://cdn.phidgets.com/docs/images/c/c1/Language_java_vscode_emptyproj.png]]
|-
| colspan="2"|You'll need to get a copy of '''phidget22.jar''' to put inside the "lib" folder. [https://www.phidgets.com/downloads/phidget22/libraries/any/Phidget22Java.zip You can download phidget22.jar here].
|-
| colspan="2"| You can now begin writing code in the newly created "App.java" file, or you can download a [[#Example_Code|sample program]] for your device and place it in the "src" folder.
|-
| Compile and run by pressing '''F5''' or by clicking the play button in the top right. || [[Image:Language_java_vscode_run.png|center|350px|link=https://cdn.phidgets.com/docs/images/e/ea/Language_java_vscode_run.png]]
|-
| Once you're ready to compile your project into a .jar executable, click on the '''Java Projects''' section in the explorer. || [[Image:Language_java_vscode_jar.png|center|350px|link=https://cdn.phidgets.com/docs/images/6/65/Language_java_vscode_jar.png]]
|-
| Click on the export icon, and then select your main class and click OK. || [[Image:Language_java_vscode_jar2.png|center|350px|link=https://cdn.phidgets.com/docs/images/7/74/Language_java_vscode_jar2.png]]
|-
| colspan="2"| Now you can run your new .jar file with the following command:
<syntaxhighlight>
java -jar Example.jar
</syntaxhighlight>
|}

===Javac===
{| style="margin:auto;" class="table-no-border mw-collapsible mw-collapsed"
|+ '''Instructions'''
|The easiest way to allow Java to access the Phidgets Java library is to place a copy of '''phidget22.jar''' in the same folder as your .java program. ||[[Image:Language_java_javac_folder.png|center|350px|link=https://cdn.phidgets.com/docs/images/8/89/Language_java_javac_folder.png]]
|-
|[https://www.phidgets.com/downloads/phidget22/libraries/any/Phidget22Java.zip You can download phidget22.jar here].||
|-
|colspan="2"|To run your program, enter the following command in the command prompt or terminal:
<syntaxhighlight>
javac -classpath .;phidget22.jar example.java
</syntaxhighlight>
Then, enter the following command to run the program:
<syntaxhighlight>
java -classpath .;phidget22.jar example
</syntaxhighlight>
||
|-
| colspan="2"| Once you're ready to compile your project into a .jar executable, create a '''manifest.mf''' file with the following contents:
<syntaxhighlight>
Manifest-Version: 1.0
Main-Class: example
Class-Path: phidget22.jar

</syntaxhighlight>
Make sure there's an empty newline at the bottom of the three lines and a space after each colon.
|-
| colspan="2"| Next, create the .jar file with this command:
<syntaxhighlight>
jar cfm example.jar manifest.mf *.class
</syntaxhighlight>
Once the .jar is created, you can execute it with
<syntaxhighlight>
java -jar example.jar
</syntaxhighlight>

|}

===Netbeans===
{| style="margin:auto;" class="table-no-border mw-collapsible mw-collapsed"
|+ '''Instructions'''
|The easiest way to allow Java to access the Phidgets Java library is to place a copy of '''phidget22.jar''' in the same folder as your .java program. ||[[Image:Language_java_javac_folder.png|center|350px|link=https://cdn.phidgets.com/docs/images/8/89/Language_java_javac_folder.png]]
|-
|[https://www.phidgets.com/downloads/phidget22/libraries/any/Phidget22Java.zip You can download phidget22.jar here].||
|-
| To start, open NetBeans and create a new project. Select Java Application and follow the steps as directed by Netbeans.|| [[Image:Windows_netbeans1.jpg|center|350px|link=https://cdn.phidgets.com/docs/images/c/c9/Windows_netbeans1.jpg]]
|-
| Next, add a reference to phidget22.jar by right-clicking on the libraries folder. || [[Image:Windows_netbeans2.jpg|center|350px|link=https://cdn.phidgets.com/docs/images/2/2b/Windows_netbeans2.jpg]]
|-
| Navigate to the folder where you downloaded phidget22.jar, and select it. || [[Image:Windows_netbeans3.jpg|center|350px|link=https://cdn.phidgets.com/docs/images/7/76/Windows_netbeans3.jpg]]
|-
| The project now has access to Phidgets. By default, Netbeans should create an executable .jar file in the '''dist''' folder of the project directory when it's built. If it didn't, go to '''Build -> Packaging''' in the project properties and make sure "Build JAR after compiling" is checked.|| [[Image:Windows_netbeans4.png|center|350px|link=https://cdn.phidgets.com/docs/images/7/78/Windows_netbeans4.png]]
|-
| colspan="2"| You can now run the .jar file from the command prompt with:
<syntaxhighlight>
java -jar phidgetTest.jar
</syntaxhighlight>
|}

===Eclipse===
{| style="margin:auto;" class="table-no-border mw-collapsible mw-collapsed"
|+ '''Instructions'''
| To start, open Eclipse and create a new Java project. Name the project and uncheck the '''create module-info.java file''' box.|| [[Image:java_eclipse_newproj.png|center|350px|link=https://cdn.phidgets.com/docs/images/9/97/Java_eclipse_newproj.png]]
|-
| On the Libraries tab, click Add External JARs and add [https://www.phidgets.com/downloads/phidget22/libraries/any/Phidget22Java.zip phidget22.jar]. to your project as an external jar. Be sure it's being added to the '''Classpath''' and not the module path. || [[Image:java_eclipse_library.png|center|350px|link=https://cdn.phidgets.com/docs/images/1/1b/Java_eclipse_library.png]]
|-
| Create a new Class in your project. || [[Image:java_eclipse_newclass.png|center|350px|link=https://cdn.phidgets.com/docs/images/0/02/Java_eclipse_newclass.png]]
|-
| Name the class, and be sure to check the '''public static void main''' box. Eclipse may require that you add a package name. || [[Image:java_eclipse_newclass2.png|center|350px|link=https://cdn.phidgets.com/docs/images/c/ca/Java_eclipse_newclass2.png]]
|-
| Your project now has access to Phidgets! ||
|-
| Once you're ready to compile your project into a .jar executable, right click on the project in the package explorer and choose '''Export'''. Select '''Runnable JAR file'''. || [[Image:java_eclipse_export.png|center|350px|link=https://cdn.phidgets.com/docs/images/8/8c/Java_eclipse_export.png]]
|-
| Choose the main class and a destination for the .jar file and click finish. || [[Image:java_eclipse_export2.png|center|350px|link=https://cdn.phidgets.com/docs/images/8/8d/Java_eclipse_export2.png]]
|-
| colspan="2"| You can now run the .jar file from the command prompt with:
<syntaxhighlight>
java -jar phidgetTest.jar
</syntaxhighlight>
|}

=== PhidgetSBC Web Interface ===
{| style="margin:auto;" class="table-no-border mw-collapsible mw-collapsed"
|+'''Instructions'''
|<center>{{#ev:youtube|gZmWvWXICIA|rel=0}}</center>
|}

==Example Code==
Navigate to our [https://www.phidgets.com/?view=code_samples&lang=Java Code Sample Generator] to view and download code samples that are tailored to your specific device.

[[Image:Language_java_codesample.png|center|600px|link=https://cdn.phidgets.com/docs/images/a/af/Language_java_codesample.png]]

===Phidget Programming Basics===
{{PhidgetProgrammingBasicsLink}}

== Deploying Applications ==

If you're planning to deploy your application, it should be noted that you don't strictly need the Phidget Drivers installed.

At a minimum, these three files are required:
* phidget22.jar
* phidget22.dll
* phidget22java.dll

All three files can be found in the [https://cdn.phidgets.com/downloads/phidget22/libraries/windows/Phidget22-windevel.zip Development Files]. The .jar file is in lib/java, and the .dll files are in lib/c/x64.

Java will look for these files in several locations, including the classpath and the working folder of the project.

==API==
[{{SERVER}}/?view=api&lang=Python Phidget22 API]

Terms and Conditions

2026-03-13T01:39:25Z

Lmpacent: /* Holidays */

[[Category:Linked From Website]]

==Product Warranty==

All Phidgets products are warranted to be free of defects in material or workmanship under normal use and service for a period of one year from the date of shipment. This warranty does not include damage resulting from accident or misuse. The warranty is also void if the product is modified. This warranty is in lieu of all other warranties expressed or implied including the implied warranties of merchantability of fitness for a particular purpose, whether arising by law, custom or conduct, and the rights and remedies provided under this warranty are exclusive and in lieu of any other rights or remedies. In no event shall Phidgets Incorporated be liable for consequential damages.

If you believe that your product is defective while still under warranty, {{ContactUs|contact us}}. Once the support desk confirms that the product is defective, we will replace your defective product free of charge.

==Shipping==
===Last Call at 12:00PM===
Orders received before 12:00 PM Mountain Time (GMT-07:00) Monday to Friday will be shipped the same day.

Orders containing cut-to-length parts may not ship on the same day due to the additional processing time associated with these orders.

===Shipping Costs===
Shipping costs are calculated at checkout and presented for your review before you confirm your order. If multiple shipping options are available for your destination, all options will be listed so you can choose the one that best suits your needs.

If you have your own UPS or FedEx account, you can use it at checkout and be billed directly by the carrier. This gives you access to a wider range of shipping options.

Note that a $5.00 handling charge is added to all orders that are under $50.00.

===Shipping in Canada===
We offer the following services:
* '''UPS Express Saver'''. 1 - 3 business days.
* '''UPS Expedited'''. 2 - 5 business days. Available for packages over 3 lbs.
* '''UPS Standard'''. 3 - 5 business days ground delivery.

===Shipping to the United States===
We offer the following services:
* '''UPS Express Saver'''. 1 - 3 business days.
* '''UPS Expedited'''. 2 - 5 business days. Available for packages over 3 lbs.
* '''UPS Standard'''. 3 - 5 business days ground delivery.

Effective May 2, 2025, orders shipped to the United States will incur additional duties, tariffs, and brokerage fees, regardless of the order value. For more details, visit our guide about [[U.S._Tariffs | U.S. Tariffs]].

===International Shipments===
We offer the following services:
* '''UPS Worldwide Express Saver'''. 1 - 3 business days.
* '''UPS Worldwide Expedited'''. 2 - 5 business days. Available for packages over 3 lbs.

====European Union====
Effective July 1, 2021, the European Union (EU) updated its Value Added Tax (VAT) regulations. All shipments to EU countries now require formal customs clearance and are subject to VAT based on the destination country.

For goods with an intrinsic value up to €150, VAT must be collected at the time of purchase. This means for orders under $200 USD, we require prepayment of VAT and brokerage fees at checkout to ensure fast, hassle-free delivery.

For orders over $200 USD, we provide the option to prepay all applicable import fees (including VAT and brokerage). If you choose this option, the quoted amount is guaranteed — there will be no additional charges upon delivery.

We use UPS® Global Checkout to collect import fees and taxes based on your product's HS Code and Country of Origin. There is a fee associated with the UPS® Global Checkout service. At Phidgets Inc., we continually monitor and negotiate all fees to ensure our customers receive the best deal possible.

Customs policies vary by country, so we recommend contacting your local customs office for more information.

====Other Countries====
International shipments may be subject to import duties, taxes, and brokerage fees upon arrival in your country. These charges are determined by your local customs authorities and are the responsibility of the recipient.

At checkout, we provide the option to prepay these fees. If you choose this option, the quoted amount is guaranteed — there will be no additional charges upon delivery.

We use UPS® Global Checkout to collect import fees and taxes based on your product's HS Code and Country of Origin. There is a fee associated with the UPS® Global Checkout service. At Phidgets Inc., we continually monitor and negotiate all fees to ensure our customers receive the best deal possible.

Customs policies vary by country, so we recommend contacting your local customs office for more information.

===Tracking Your Order===
You can track your shipment using the tracking number sent to you by email when your order was shipped.

===Refunds on Late Deliveries===

Normally, UPS will offer a service guarantee refund when their deliveries arrive late. However, for companies that apply for shipping discounts, this refund does not apply. Phidgets Inc. has applied for such discounts in order to keep shipping costs down and regrettably cannot offer compensation for late shipments.

===Damaged or Lost Shipment===

'''Shipping on our UPS account''' - Report all damaged or lost shipments to support@phidgets.com and include your order number. According to UPS, in order to be considered lost, a package must be undelivered 24 hours after the expected delivery date and time. Before contacting us, check your shipment status at ups.ca.

Damaged or lost items will be replaced at no charge (including shipping costs).

'''Shipping on your UPS account''' - You must notify your local UPS office. If they confirm that they have lost your shipment, you must repurchase the lost or damaged products from Phidgets and file a claim with your local UPS in order to get reimbursed.

===Refused/Missed Delivery===
If no one is available to accept the package upon delivery, UPS will attempt redelivery two more times, as per their standard procedure. If all delivery attempts fail, UPS will hold the package for 5 days before returning it to us. In such cases, we will issue a refund for your order minus the cost of shipping (both directions) and a flat $50 fee, up to the total value of the package. This policy applies both to deliveries that failed due to no one being present and to packages that were refused at the delivery address.

===Incoterms===

We use the following Incoterms depending on the shipping and payment arrangement:

* '''FCA (Free Carrier):''' Used when shipping on the customer’s carrier account. Risk and responsibility transfer to the customer once the goods are handed over to the carrier at our facility.

* '''DDP (Delivered Duty Paid):''' Used when the customer chooses to pre-pay import fees and taxes at checkout. We handle all import fees and deliver the goods to the destination address.

* '''DAP (Delivered at Place):''' Used when the customer opts to pay import fees and taxes upon delivery. We deliver the goods, but the customer is responsible for paying any import fees directly to the carrier.

==Product Returns==
===All Returns Must Be Authorized===
Before returning a package {{ContactUs|contact us}} and ask for a Return Merchandise Authorization or RMA number. Once you have received it, put the RMA number on the outside of the packaging as well as the packing slip so that it is possible for us to track what the package is supposed to be. Any merchandise returned without an RMA number clearly visible on the packaging will be charged an administrative fee of $25.00 or the value of the returned product, whichever is less ''if we are able to determine what it is''. In the event we are unable to determine what the package is, it will be refused and returned to the sender.

===Unopened Product===
Phidgets accepts returns of unopened products within 30 days of the date of purchase. To initiate a return, please contact us by phone or email to obtain an RMA number. Products must be shipped back to Phidgets Inc. prepaid. A refund will be issued to your credit card once we receive and inspect the returned items. The refund excludes the cost of shipping as well as any duties or brokerage charges incurred.

Returns received after 30 days are subject to a restocking fee of 25% of the package's value (minimum $5.00, maximum $500).

We do '''not''' accept returns beyond 90 days from the date of purchase.

===Cut to Length===
Unfortunately we cannot accept returns on any items which are cut to custom lengths. This includes: cable, wire, roller chain, linear shaft, rotary shaft, and t-slot extrusions.

===We Shipped the Wrong/Incomplete Product===
{{ContactUs|Contact us}}. We will get the correct product sent to you immediately, and will pay all shipping charges.

==Payment Terms==
We accept credit cards, PayPal, and Wire Transfers.

{| style="border:1px solid darkgray;" cellpadding="7px;"
|-style="background: #d1d1d1" align=center
! Payment Method|| Terms
|-
|style="background: #f0f0f0" align=center|Credit Cards
|style="background: #f0f0f0" align=left|Visa, MasterCard, American Express (for order in CAD only)
|-
|style="background: #f0f0f0" align=center|PayPal
|style="background: #f0f0f0" align=left|PayPal is accepted. There are no extra fees for using PayPal
|-
|style="background: #f0f0f0" align=center|Wire Transfers
|style="background: #f0f0f0" align=left|Wire transfers are only accepted for orders over $200.00 USD (excluding shipping charges). There is a $25.00 USD charge for wire transfers under $500.00 USD. Any fees charged by the sending bank are your responsibility.<br />Please make sure that the amount sent to us covers both our invoice and your bank fees. Products are not shipped until the money is deposited in our bank account. We recommend that you e-mail orders@phidgets.com with the amount of the transfer and the invoice you are paying. <br />Any order for which payment is not received within 15 days, will be canceled.
|}

==Security and Privacy==
Phidgets Inc. pledges a safe and worry-free shopping experience. IF you are using the current version of Internet Explorer, on the checkout page where you enter your credit card information, you will notice a a locked padlock icon on the top bar your browser window. If you are using Mozilla Firefox, you will notice a locked padlock icon in the bottom right corner of your browser window. If this icon does not appear, please contact us directly to complete your purchase. These icons tell you that the page you are on is secure. We use Secure Sockets Layer (SSL 128-bit) technology with a digital certificate by GeoTrust, Inc. for Internet security to protect your personal information. This encryption makes it impossible for anyone to read your information in transit. We do not store your credit information and it is deleted once it has been securely transmitted to Moneris for processing.

We use your e-mail address to let you know your shipment's tracking number. Your phone number is required by the Courier Company. We do not sell, rent or give any of your personal information to any unrelated third parties with the exception of Moneris for authorizing credit card payments and the Courier company to let them know where to deliver the shipment and how to contact you if there is any problems.

If you have any questions or concerns about our Security and Privacy policy, call us at 1.403.282.7335 or e-mail us at support@phidgets.com

Phidgets Inc. uses various Google Analytics tools such as conversion tracking in order to improve the effectiveness of the website. These statistics are completely anonymous.

==Holidays==
Phidgets, Inc. will be closed on the following days. During these times, the site will still be accessible and orders can be placed, but they will not ship until the next business day.

{| style="border:1px solid darkgray;" cellpadding="7px;"
|-style="background: #d1d1d1" align=center
! style="text-align:center;"| Holiday
! style="text-align:center;"| Description
! style="text-align:center;"| 2026
! style="text-align:center;"| 2027
|-
|style="background: #f0f0f0" align=center| Alberta Family Day
|style="background: #f0f0f0" align=center| Third Monday in February
|style="background: #f0f0f0" align=center| Feb 16
|style="background: #f0f0f0" align=center| Feb 15
|-
|style="background: #f0f0f0" align=center| Good Friday
|style="background: #f0f0f0" align=center| Friday before Easter Sunday
|style="background: #f0f0f0" align=center| Apr 3
|style="background: #f0f0f0" align=center| Mar 26
|-
|style="background: #f0f0f0" align=center| Victoria Day
|style="background: #f0f0f0" align=center| Monday before May 25
|style="background: #f0f0f0" align=center| May 18
|style="background: #f0f0f0" align=center| May 24
|-
|style="background: #f0f0f0" align=center| Canada Day
|style="background: #f0f0f0" align=center| First day of July (or nearest business day)
|style="background: #f0f0f0" align=center| Jul 1
|style="background: #f0f0f0" align=center| Jul 1
|-
|style="background: #f0f0f0" align=center| Civic Holiday
|style="background: #f0f0f0" align=center| First Monday in August
|style="background: #f0f0f0" align=center| Aug 3
|style="background: #f0f0f0" align=center| Aug 2
|-
|style="background: #f0f0f0" align=center| Labour Day
|style="background: #f0f0f0" align=center| First Monday in September
|style="background: #f0f0f0" align=center| Sept 7
|style="background: #f0f0f0" align=center| Sept 6
|-
|style="background: #f0f0f0" align=center| Thanksgiving
|style="background: #f0f0f0" align=center| Second Monday in October
|style="background: #f0f0f0" align=center| Oct 12
|style="background: #f0f0f0" align=center| Oct 11
|-
|style="background: #f0f0f0" align=center| Remembrance Day
|style="background: #f0f0f0" align=center| November 11 (or nearest business day)
|style="background: #f0f0f0" align=center| Nov 11
|style="background: #f0f0f0" align=center| Nov 11
|-
|style="background: #f0f0f0" align=center| Christmas and New Years
|style="background: #f0f0f0" align=center| Varies
|style="background: #f0f0f0" align=center| TBA
|style="background: #f0f0f0" align=center| TBA
|-
|}

Language - C Sharp

2026-03-06T17:00:43Z

Lmpacent: /* macOS Considerations */

{{#seo:|description=Learn how to use Phidget USB devices with C#.}}
[[Category:Language]]

==Get Started==
With the Phidget22.NET library, it's easy to create C# applications that work with Phidget devices.

==C# Libraries==
===Nuget Package===
The Phidget22.NET library is available as a [https://www.nuget.org/packages/Phidget22.NET/ nuget package]. This is the recommend way to install and manage the Phidget22.NET library.

====macOS Considerations====
Legacy Phidgets running a HID USB stack require a driver extension (macOS 10.15 and newer) or a kernel extension (macOS 10.14 and earlier). During development, we recommend downloading the appropriate [https://www.phidgets.com/docs/OS_-_macOS#Quick_Downloads package] which will install the extension. When deploying applications, review the README in the [https://cdn.phidgets.com/downloads/phidget22/libraries/macos/Phidget22_macosdevel.zip macOS Development Files] for information about bundling the extension with your application.

=====Determining USB Stack=====
To determine which USB stack your device is running, navigate to the product page and then to the specification tab, and look for the ''USB Stack'' specification. If you are using a VINT device, navigate to the product page for the VINT Hub you are using.

[[Image:Javascript_networkserver_webusb_spec.png|center|600px|link=https://cdn.phidgets.com/docs/images/8/80/Javascript_networkserver_webusb_spec.png]]

====Linux Considerations====
Linux restricts access to USB devices to the root user. To run your .NET application as a regular user, you'll need to [{{SERVER}}/docs/OS_-_Linux#Setting_udev_Rules set up udev rules] on your system.

===Library Files===
If you would like to manually manage the Phidget22.NET library files, you can download them [https://cdn.phidgets.com/downloads/phidget22/libraries/windows/Phidget22-windevel.zip here].

==Development Environment Configuration==
===Visual Studio===
{| style="margin:auto;" class="table-no-border mw-collapsible mw-collapsed"
|+ '''Instructions'''
| Create your Visual Studio project, and navigate to the '''Solution Explorer'''. From there, right-click on '''Dependencies''' and select '''Manage NuGet Packages...'''|| [[Image:Language_csharp_vs_managenuget.png|center|350px|link=https://cdn.phidgets.com/docs/images/c/cc/Language_csharp_vs_managenuget.png]]
|-
| Next, click '''Browse''' and enter '''Phidget22.NET''' in the search bar. || [[Image:Language_csharp_vs_browsenuget.png|center|350px|link=https://cdn.phidgets.com/docs/images/6/61/Language_csharp_vs_browsenuget.png]]
|-
| Click on the package and press the '''Install''' button. || [[Image:Language_csharp_vs_installnuget.png|center|350px|link=https://cdn.phidgets.com/docs/images/b/b8/Language_csharp_vs_installnuget.png]]
|-
| Finally, add your C# code and run it using the button at the top of the screen. || [[Image:Language_csharp_vs_run.png|center|350px|link=https://cdn.phidgets.com/docs/images/5/5a/Language_csharp_vs_run.png]]
|-
|}

===Visual Studio Code===
{| style="margin:auto;" class="table-no-border mw-collapsible mw-collapsed"
|+ '''Instructions'''
| Install the [https://marketplace.visualstudio.com/items?itemName=ms-dotnettools.csdevkit C# Dev Kit extension for Visual Studio Code].|| [[Image:Language_csharp_vscode_installext.png|center|350px|link=https://cdn.phidgets.com/docs/images/b/b8/Language_csharp_vscode_installext.png]]
|-
| Next, create a directory and open it in Visual Studio Code. You can do this by opening Visual Studio Code and selecting '''File > Open Folder...''' || [[Image:Language_csharp_vscode_newfolder.png|center|350px|link=https://cdn.phidgets.com/docs/images/4/43/Language_csharp_vscode_newfolder.png]]
|-
| Open the Command Palette (Ctrl + Shift + P), type '''.NET: New Project''', and press Enter. A list of supported project types will appear. || [[Image:Language_csharp_vscode_netnewproject.png|center|350px|link=https://cdn.phidgets.com/docs/images/f/f7/Language_csharp_vscode_netnewproject.png]]
|-
| Select your preferred project type from the list. For this example, we will select '''Console App'''. || [[Image:Language_csharp_vscode_netconsoleapp.png|center|350px|link=https://cdn.phidgets.com/docs/images/b/bc/Language_csharp_vscode_netconsoleapp.png]]
|-
| Next, we need to add the Phidget22.NET library using NuGet. Open the Command Palette again (Ctrl + Shift + P), and enter '''NuGet: Add NuGet package...'''.
|| [[Image:Language_csharp_vscode_addnugetpackage.png|center|350px|link=https://cdn.phidgets.com/docs/images/2/26/Language_csharp_vscode_addnugetpackage.png]]
|-
| When prompted, enter '''Phidget22.NET''' and install the latest package.<br><br>'''Note''': Ensure you are downloading the latest version which can be seen [{{SERVER}}/?view=changelog here]. Visual Studio Code may incorrectly show an older version as the ''latest'' by default.|| [[Image:Language_csharp_vscode_phidget22net.png|center|350px|link=https://cdn.phidgets.com/docs/images/d/d5/Language_csharp_vscode_phidget22net.png]]
|-
|-
| Finally, add your C# code and run it using the button at the top of the screen. || [[Image:Language_csharp_vscode_runcodepng.png|center|350px|link=https://cdn.phidgets.com/docs/images/d/dc/Language_csharp_vscode_runcodepng.png]]
|-
|}

===.NET Command-Line Interface (CLI)===
{| style="margin:auto;" class="table-no-border mw-collapsible mw-collapsed"
|+ '''Instructions'''
| Download and install the latest version of.NET from [https://dotnet.microsoft.com/en-us/download/dotnet Microsoft's .NET download page].|| [[Image:Language_csharp_cli_download.png|center|350px|link=https://cdn.phidgets.com/docs/images/9/90/Language_csharp_cli_download.png]]
|-
| Next, open a command prompt or terminal in a new folder and enter the following command:

<syntaxhighlight lang=bash>
dotnet new console
</syntaxhighlight>

|| [[Image:Language_csharp_cli_newconsole.png|center|350px|link=https://cdn.phidgets.com/docs/images/3/3a/Language_csharp_cli_newconsole.png]]
|-
| This previous command will create a new console application at the folder location. || [[Image:Language_csharp_cli_newproject.png|center|350px|link=https://cdn.phidgets.com/docs/images/c/cb/Language_csharp_cli_newproject.png]]
|-
| Navigate back to the command prompt or terminal, and add the Phidget22.NET package with the following command:

<syntaxhighlight lang=bash>
dotnet add package Phidget22.NET
</syntaxhighlight>

|| [[Image:Language_csharp_cli_addpackage.png|center|350px|link=https://cdn.phidgets.com/docs/images/7/78/Language_csharp_cli_addpackage.png]]
|-
| You can now open the '''Program.cs''' file and add your code. Run the program by entering the following command into your command prompt or terminal:

<syntaxhighlight lang=bash>
dotnet run
</syntaxhighlight>

|| [[Image:Language_csharp_cli_runcode.png|center|350px|link=https://cdn.phidgets.com/docs/images/f/f3/Language_csharp_cli_runcode.png]]
|-
|}

==Example Code==
Navigate to our [https://www.phidgets.com/?view=code_samples&lang=CSharp Code Sample Generator] to view and download code samples that are tailored to your specific device.

[[Image:Language_csharp_codesample.png|center|600px|link=https://cdn.phidgets.com/docs/images/0/03/Language_csharp_codesample.png]]

===Phidget Programming Basics===
{{PhidgetProgrammingBasicsLink}}

==API==
[{{SERVER}}/?view=api&lang=CSharp Phidget22 API]

Language - Python

2026-03-06T17:00:06Z

Lmpacent: /* macOS Considerations */

{{#seo:|description=Learn how to use Phidget USB devices with Python.}}
[[Category:Language]]

==Get Started==
With the Phidget22 Python library, it's easy to create Python applications that work with Phidget devices.

==Python Libraries==
===pip Package===
The Phidget22 Python library is available as a [https://pypi.org/project/phidget22/ pip package]. Most development environments provide built-in tools to manage packages. View the [[#Development Environment Configuration | Development Environment Configuration]] section below for examples.

====macOS Considerations====
Legacy Phidgets running a HID USB stack require a driver extension (macOS 10.15 and newer) or a kernel extension (macOS 10.14 and earlier). During development, we recommend downloading the appropriate [https://www.phidgets.com/docs/OS_-_macOS#Quick_Downloads package] which will install the extension. When deploying applications, review the README in the [https://cdn.phidgets.com/downloads/phidget22/libraries/macos/Phidget22_macosdevel.zip macOS Development Files] for information about bundling the extension with your application.

=====Determining USB Stack=====
To determine which USB stack your device is running, navigate to the product page and then to the specification tab, and look for the ''USB Stack'' specification. If you are using a VINT device, navigate to the product page for the VINT Hub you are using.

[[Image:Javascript_networkserver_webusb_spec.png|center|600px|link=https://cdn.phidgets.com/docs/images/8/80/Javascript_networkserver_webusb_spec.png]]

====Linux Considerations====
Linux restricts access to USB devices to the root user. To run your Python application as a regular user, you'll need to [{{SERVER}}/docs/OS_-_Linux#Setting_Udev_Rules set up udev rules] on your system.

===Source Files===
The Phidget22 Python library source files are available [https://cdn.phidgets.com/downloads/phidget22/libraries/any/Phidget22Python.zip here].

==Development Environment Configuration==
Most development environments provide built-in tools to manage Python interpreters, packages, and virtual environments. See the examples below for more information.
===Installing a Python Interpreter===
If you don't already have a Python interpreter installed, you can download and install one from [https://www.python.org/downloads/ python.org] or through package managers like [https://brew.sh/ Homebrew].

===Visual Studio Code===
{| style="margin:auto;" class="table-no-border mw-collapsible mw-collapsed"
|+ '''Instructions'''
| Install the [https://marketplace.visualstudio.com/items?itemName=ms-python.python Python extension for Visual Studio Code].|| [[Image:Language_python_vscode_install.png|center|350px|link=https://cdn.phidgets.com/docs/images/f/f9/Language_python_vscode_install.png]]
|-
| Next, create a directory and open it in Visual Studio Code. You can do this by opening Visual Studio Code and selecting '''File > Open Folder...''' || [[Image:Language_python_vscode_newfolder.png|center|350px|link=https://cdn.phidgets.com/docs/images/f/f8/Language_python_vscode_newfolder.png]]
|-
| Open the Command Palette (Ctrl + Shift + P), type '''Python: Create Environment''', and press Enter. Select '''Venv''' when prompted. || [[Image:Language_python_vscode_newvenv.png|center|350px|link=https://cdn.phidgets.com/docs/images/a/a6/Language_python_vscode_newvenv.png]]
|-
| Next, select your preferred Python interpreter from the list. You may need to browse to find it. || [[Image:Language_python_vscode_selectinterpreter.png|center|350px|link=https://cdn.phidgets.com/docs/images/2/20/Language_python_vscode_selectinterpreter.png]]
|-
| Open a new terminal. You can do this through the Command Palette again (Ctrl + Shift + P), by typing '''Terminal: Create New Terminal'''. Install the Phidget22 pip package:
<syntaxhighlight lang=bash>
#Windows
py -m pip install phidget22

#macOS
python3 -m pip install phidget22

#Linux (Debian)
python3 -m pip install phidget22
</syntaxhighlight>
|| [[Image:Language_python_vscode_installpackage.png|center|350px|link=https://cdn.phidgets.com/docs/images/a/a8/Language_python_vscode_installpackage.png]]
|-
| Finally, add your Python file and run it using the button in the top right corner.|| [[Image:Language_python_vscode_runcode.png|center|350px|link=https://cdn.phidgets.com/docs/images/9/96/Language_python_vscode_runcode.png]]
|-
|}

===PyCharm===
{| style="margin:auto;" class="table-no-border mw-collapsible mw-collapsed"
|+ '''Instructions'''
| Create your PyCharm project and navigate to '''Settings''': || [[Image:Windows_pycharm_settings.jpg|center|350px|link=https://cdn.phidgets.com/docs/images/7/75/Windows_pycharm_settings.jpg]]
|-
| Next, navigate to '''Project > Project Interpreter''' and click on the '''+''' symbol: || [[Image:Windows_pycharm_addpackage.jpg|center|350px|link=https://cdn.phidgets.com/docs/images/6/6f/Windows_pycharm_addpackage.jpg]]
|-
| Search for '''phidget22''' and install the package: || [[Image:Windows_pycharm_installpackage.jpg|center|350px|link=https://cdn.phidgets.com/docs/images/a/ad/Windows_pycharm_installpackage.jpg]]
|-
| Finally, add your Python file and run it using the button at the top of the screen: || [[Image:Windows_pycharm_run.png|center|350px|link=https://cdn.phidgets.com/docs/images/0/0a/Windows_pycharm_run.png]]
|}

==Example Code==
Navigate to our [https://www.phidgets.com/?view=code_samples&lang=Python Code Sample Generator] to view and download code samples that are tailored to your specific device.

[[Image:Language_python_codesample.png|center|600px|link=https://cdn.phidgets.com/docs/images/2/2d/Language_python_codesample.png]]

===Phidget Programming Basics===
{{PhidgetProgrammingBasicsLink}}

==API==
[{{SERVER}}/?view=api&lang=Python Phidget22 API]

Asynchronous Methods

2026-03-04T23:19:29Z

Lmpacent: /* Multiple Channels Example */

{{#seo:|description=This guide provides information about asynchronous methods with Phidget22.}}
[[Category:IntroGuide]]
__TOC__
==What Are Asynchronous Methods?==
Asynchronous methods allow you to send commands to a device ''without'' waiting for return codes.

When calling a typical non-asynchronous method, your program must wait for the return code, blocking the rest of your program’s operation.
[[Image:Async_methods_typical_flow.png|center|link=]]

When using an asynchronous method, your program can immediately continue executing and handle the return code in an asynchronous handler.
[[Image:Async_methods_async_flow.png|center|link=]]

==When Should I Use Asynchronous Methods?==
There are two situations where asynchronous methods may be beneficial:
# When sending commands to multiple channels on the same device
# When sending commands to multiple channels on different devices

===Multiple Channels Example===
[[Image:1032_0B.jpg|thumb|link=https://cdn.phidgets.com/docs/images/6/6d/1032_0B.jpg|<center>PhidgetLED-64 Advanced(1032_0)</center>]]
The [https://www.phidgets.com/?prodid=1024 PhidgetLED-64 Advanced] features 64 channels, one for each LED. To turn all the LEDs on or off simultaneously, 64 sequential commands are necessary (one for each channel). In this situation, using asynchronous methods can drastically improve the performance of your application.

===Multiple Devices Example===
The [https://www.phidgets.com/?prodid=712 Isolated 12-bit Voltage Output Phidget] is a single-channel device. If two or more of these devices were used in an application, it may be beneficial to use asynchronous methods.

==How Do I Use Asynchronous Methods?==
Asynchronous methods are comprised of two parts:
* Asynchronous API call
* Asynchronous handler

When calling an asynchronous method, you must assign an asynchronous handler. The Phidget22 libraries will then initiate the command and immediately return. The asynchronous handler will be called once the relevant communications have been completed to provide the return code from the device.

===Code Example===
The code below provides a simple demonstration of how asynchronous methods can be used (while avoiding [[#Overloading|overloading]]).

<tabber>
Python=
<syntaxhighlight lang=python>
from Phidget22.Phidget import *
from Phidget22.Devices.DigitalOutput import *
from Phidget22.ErrorCode import *
import time

def main():
digitalOutput0 = DigitalOutput()

digitalOutput0.openWaitForAttachment(5000)

#Assign new variables to track the number of calls made vs completed
digitalOutput0.AsyncCalls = 0
digitalOutput0.AsyncComplete = 0
def AsyncResult(ch, res, details):
ch.AsyncComplete += 1
print("Async Complete:" + str(ch.AsyncComplete))
if res != ErrorCode.EPHIDGET_OK:
print("Async failure: %i : %s" % (res, details))

while(1): #some loop condition
#Here we check if the previous asynchronous call has completed before issuing a new one
#If you had multiple asynchronous calls to make, you could (for example) give each its
#own counter, or call a new batch of them once an entire set completes
if(digitalOutput0.AsyncCalls == digitalOutput0.AsyncComplete):
digitalOutput0.AsyncCalls += 1
digitalOutput0.setDutyCycle_async(1, AsyncResult)
# NOTE: Make sure to wait for async call to complete before closing the channel

#Do other work here...

digitalOutput0.close()

main()
</syntaxhighlight>
|-|
Java=
<syntaxhighlight lang=java>
import com.phidget22.*;
import java.io.IOException;

public class JavaApplication11 {

static int asyncCalls = 0;
static int asyncComplete = 0;

public static void main(String[] args) throws Exception {

Phidget.resetLibrary();
DigitalOutput digitalOutput0 = new DigitalOutput();

digitalOutput0.open(5000);

while(asyncComplete < 1000) { //Some loop condition
//Here we check if the previous asynchronous call has completed before issuing a new one
//If you had multiple asynchronous calls to make, you could (for example) give each its
//own counter, or call a new batch of them once an entire set completes
if(asyncCalls == asyncComplete) {
asyncCalls++;
digitalOutput0.setDutyCycle(1, new AsyncListener() {
public void onAsyncCallback(AsyncResult ar) {
if (ar.getReturnCode() == ErrorCode.SUCCESS) {
asyncComplete++;
System.out.println("Async Complete: " + asyncComplete);
}
else
System.out.println("Async Failure: " + ar);
}
});
// NOTE: Make sure to wait for async call to complete before closing the channel
}

//Do other work here...
Thread.sleep(1);
}

digitalOutput0.close();
}
}
</syntaxhighlight>
|-|
C#=
<syntaxhighlight lang=cSharp>
using System;
using Phidget22;

namespace ConsoleApplication
{
class Program
{
static void Main(string[] args)
{
DigitalOutput digitalOutput0 = new DigitalOutput();

digitalOutput0.Open(5000);

digitalOutput0.DutyCycle = 1;

int asyncCalls = 0;
int asyncComplete = 0;
double dutyCycle = 0.1;
while (true) /* Some loop condition */
{
//Here we check if the previous asynchronous call has completed before issuing a new one
//If you had multiple asynchronous calls to make, you could (for example) give each its
//own counter, or call a new batch of them once an entire set completes
if (asyncCalls == asyncComplete)
{
asyncCalls++;
digitalOutput0.BeginSetDutyCycle(dutyCycle, delegate (IAsyncResult result)
{
try
{
asyncComplete++;
digitalOutput0.EndSetDutyCycle(result);
Console.WriteLine("Async Complete: " + asyncComplete.ToString());
}
catch (PhidgetException ex)
{
Console.WriteLine("Async Failure: " + ex.Message);
}
}, null);
}

/*
* Do other work were
*/
}
digitalOutput0.Close();
}
}
}
</syntaxhighlight>
|-|
C=
<syntaxhighlight lang=c>
#include <phidget22.h>
#include <stdio.h>

void CCONV setDutyCycleDone(PhidgetHandle phid, void *ctx, PhidgetReturnCode res) {
int *asyncComplete = (int*)ctx;
(*asyncComplete)++;
printf("Async Complete : %d\n", *asyncComplete);
}

int main() {
PhidgetDigitalOutputHandle digitalOutput0;
int asyncComplete;
int asyncCalls;

PhidgetDigitalOutput_create(&digitalOutput0);

Phidget_openWaitForAttachment((PhidgetHandle)digitalOutput0, 5000);

PhidgetDigitalOutput_setDutyCycle(digitalOutput0, 1);

asyncComplete = 0;
asyncCalls = 0;
while (1) { //Some loop condition

//Here we check if the previous asynchronous call has completed before issuing a new one
//If you had multiple asynchronous calls to make, you could (for example) give each its
//own counter, or call a new batch of them once an entire set completes
if (asyncCalls == asyncComplete) {
asyncCalls++;
PhidgetDigitalOutput_setDutyCycle_async(digitalOutput0, 1, setDutyCycleDone, &asyncComplete);
}

//Do other work here...

}
Phidget_close((PhidgetHandle)digitalOutput0);

PhidgetDigitalOutput_delete(&digitalOutput0);
}
</syntaxhighlight>
</tabber>

==Other Considerations==
===Overloading===
If asynchronous methods are called faster than they can be dispatched, they will be added to a queue. In extreme cases, if the queue grows large enough, newer calls will be dropped and your async handler will complete with ''Phidget Error 0x10 NoSpace''.

===Single Device, Single Channel===
Asynchronous commands are not recommended when using a single device and a single channel. Multiple asynchronous calls to the same channel will be queued and issued one at a time as return codes are received for each, providing no benefit to your application.

===Network Delays===
If you are accessing your device(s) over a network connection with high latency, you may benefit from using asynchronous methods.

===Callback Handlers===
When programming using the [https://www.phidgets.com/docs/Language_-_C C language], a callback handler is required. If a callback handler is not provided, the method will not run asynchronously. In all other programming languages, a callback handler is recommended but optional.

===VINT Communication Speed===
Asynchronous methods are particularly useful on VINT devices with lower [https://www.phidgets.com/docs/VINT_Communication_Speed_Guide communication speeds]. If you are working with USB devices or higher-speed VINT devices, the impact of asynchronous commands will be less significant.

File:1032 0B.jpg

2026-03-04T23:18:29Z

Lmpacent:

OS - macOS

2026-03-04T17:50:26Z

Lmpacent: /* Phidget Control Panel */

<metadesc>Communicate over USB with sensors, controllers, and relays with Phidgets! Program in macOS using a wide variety of programming languages.</metadesc>
[[Category:OS]]

==Quick Downloads==
Our libraries support macOS 10.11 and newer.
* [https://cdn.phidgets.com/downloads/phidget22/tools/macos/Phidget22ControlPanel.dmg Phidget22 Control Panel (macOS 10.15 and newer)]
* [https://cdn.phidgets.com/downloads/phidget22/libraries/macos/Phidget22.dmg Phidget22 Installer (macOS 10.14 and earlier)]

===Other Resources===
* [https://cdn.phidgets.com/downloads/phidget22/libraries/macos/Phidget22_macosdevel.zip macOS Development Files]
* [{{SERVER}}/downloads/phidget22/libraries/macos/Phidget22/ Previous Releases]

==Getting Started with macOS==
===Install===
To get started, download the appropriate [[#Quick Downloads|package]] for your machine from the list above. This will install the Phidget Control Panel and the Phidget Network Server. These are powerful tools that will help you develop your Phidget applications.

===Phidget Control Panel===
After downloading, drag the application into your Applications folder:
[[Image:Macos_standalone_install.png|link=https://cdn.phidgets.com/docs/images/c/c8/Macos_applications_controlpanel.png|center|600px]]

You can then find the application in the Applications folder by searching for ''Phidget Control Panel''.
[[Image:Macos_applications_controlpanel.png|link=https://cdn.phidgets.com/docs/images/c/c8/Macos_applications_controlpanel.png|600px|center]]

When you open the application for the first time, you will see the following notice:
[[Image:Macos_install_extension.png|link=https://cdn.phidgets.com/docs/images/9/9e/Macos_install_extension.png|300px|center]]

Follow the link in the pop-up, or navigate to ''System Settings > General > Login Items & Extensions > Extensions'', and give permissions:
[[Image:Macos_install_extension_permission.png|link=https://cdn.phidgets.com/docs/images/a/ac/Macos_install_extension_permission.png|600px|center]]
<center>''Note: The driver extension is only required for legacy USB Phidgets running a HID USB stack. Refer to your product’s specifications page for information about its USB stack.''</center>

After running the application, you will see all the Phidgets that are plugged into your machine, as well as any Phidgets that are on your network.
[[Image:Os_macos_controlpanel.png|600px|link=https://cdn.phidgets.com/docs/images/a/a1/Os_macos_controlpanel.png|center]]

Click on the arrow beside a device to expand it so that you can see all available channels. Double-click on one of these channels to open up a window that lets you interact with it.

[[File:Os_macos_controlpanel_example.png‎|link=https://cdn.phidgets.com/docs/images/3/37/Os_macos_controlpanel_example.png|center|600px]]

The Phidget Control Panel can be used for testing devices, updating firmware, enabling a Phidget Network Server, and more. Visit the [[Phidget Control Panel|Phidget Control Panel page]] for more information.

===Programming===
When you are ready to develop your own applications, visit our [{{SERVER}}/docs/Programming_Resources programming resources page] and select your programming language to get started.

==Software License==
By downloading the installer and/or development files, you agree to adhere to the terms of the [{{SERVER}}/documentation/Licenses/Phidgets_EULA.pdf Phidgets End User License Agreement]. The Phidget libraries and development files are covered by the The 3-Clause BSD License.

OS - macOS

2026-03-04T17:10:12Z

Lmpacent:

<metadesc>Communicate over USB with sensors, controllers, and relays with Phidgets! Program in macOS using a wide variety of programming languages.</metadesc>
[[Category:OS]]

==Quick Downloads==
Our libraries support macOS 10.11 and newer.
* [https://cdn.phidgets.com/downloads/phidget22/tools/macos/Phidget22ControlPanel.dmg Phidget22 Control Panel (macOS 10.15 and newer)]
* [https://cdn.phidgets.com/downloads/phidget22/libraries/macos/Phidget22.dmg Phidget22 Installer (macOS 10.14 and earlier)]

===Other Resources===
* [https://cdn.phidgets.com/downloads/phidget22/libraries/macos/Phidget22_macosdevel.zip macOS Development Files]
* [{{SERVER}}/downloads/phidget22/libraries/macos/Phidget22/ Previous Releases]

==Getting Started with macOS==
===Install===
To get started, download the appropriate [[#Quick Downloads|package]] for your machine from the list above. This will install the Phidget Control Panel and the Phidget Network Server. These are powerful tools that will help you develop your Phidget applications.

===Phidget Control Panel===
After downloading, drag the application into your Applications folder:
[[Image:Macos_standalone_install.png|link=https://cdn.phidgets.com/docs/images/c/c8/Macos_applications_controlpanel.png|center|600px]]

You can then find the application in the Applications folder by searching for ''Phidget Control Panel''.
[[Image:Macos_applications_controlpanel.png|link=https://cdn.phidgets.com/docs/images/c/c8/Macos_applications_controlpanel.png|600px|center]]

When you open the application for the first time, you will see the following notice:
[[Image:Macos_install_extension.png|link=https://cdn.phidgets.com/docs/images/9/9e/Macos_install_extension.png|300px|center]]

Follow the link in the pop-up, or navigate to ''System Settings > General > Login Items & Extensions > Extensions'', and give permissions:
[[Image:Macos_install_extension_permission.png|link=https://cdn.phidgets.com/docs/images/a/ac/Macos_install_extension_permission.png|600px|center]]
<center>''Note: The driver extension is only required for legacy USB Phidgets that use a HID USB stack. Refer to your product’s specifications page for information about its USB stack.''</center>

After running the application, you will see all the Phidgets that are plugged into your machine, as well as any Phidgets that are on your network.
[[Image:Os_macos_controlpanel.png|600px|link=https://cdn.phidgets.com/docs/images/a/a1/Os_macos_controlpanel.png|center]]

Click on the arrow beside a device to expand it so that you can see all available channels. Double-click on one of these channels to open up a window that lets you interact with it.

[[File:Os_macos_controlpanel_example.png‎|link=https://cdn.phidgets.com/docs/images/3/37/Os_macos_controlpanel_example.png|center|600px]]

The Phidget Control Panel can be used for testing devices, updating firmware, enabling a Phidget Network Server, and more. Visit the [[Phidget Control Panel|Phidget Control Panel page]] for more information.

===Programming===
When you are ready to develop your own applications, visit our [{{SERVER}}/docs/Programming_Resources programming resources page] and select your programming language to get started.

==Software License==
By downloading the installer and/or development files, you agree to adhere to the terms of the [{{SERVER}}/documentation/Licenses/Phidgets_EULA.pdf Phidgets End User License Agreement]. The Phidget libraries and development files are covered by the The 3-Clause BSD License.

File:Os macos controlpanel.png

2026-03-04T17:08:08Z

Lmpacent:

File:Os macos controlpanel example.png

2026-03-04T17:07:35Z

Lmpacent:

File:Macos install extension permission.png

2026-03-04T17:06:29Z

Lmpacent:

File:Macos install extension.png

2026-03-04T17:05:49Z

Lmpacent:

File:Macos applications controlpanel.png

2026-03-04T17:05:27Z

Lmpacent:

File:Macos standalone install.png

2026-03-04T17:05:10Z

Lmpacent:

OS - Windows

2026-03-03T16:28:33Z

Lmpacent: /* Install */

<metadesc>Communicate over USB with sensors, controllers and relays with Phidgets! Program in Windows using a wide variety of programming languages.</metadesc>
[[Category:OS]]

==Quick Downloads==
Our libraries support Windows 8 and newer.

*[https://cdn.phidgets.com/downloads/phidget22/libraries/windows/Phidget22-x64.exe Installer Download (64-bit)]
*[https://cdn.phidgets.com/downloads/phidget22/libraries/windows/Phidget22-ARM64.exe Installer Download (ARM64)]
*[https://cdn.phidgets.com/downloads/phidget22/libraries/windows/Phidget22-x86.exe Installer Download (32-bit)]

===Other Resources===
* [[OS - Windows Advanced Information|Windows Advanced Information]]
*[https://cdn.phidgets.com/downloads/phidget22/libraries/windows/Phidget22-windevel.zip Windows Development Files]
* [https://www.phidgets.com/downloads/phidget22/libraries/windows/ Previous Releases]

==Getting Started with Windows==
===Install===
To get started, download the appropriate [[#Quick Downloads|installer]] for your machine from the list above. This will install the Phidget Control Panel and the Phidget Network Server. These are powerful tools that will help you develop your Phidget applications.

===Phidget Control Panel===
After installing, you can find the application through your system tray, or by opening the start menu and searching for ''Phidget Control Panel''.

[[Image:Os_windows_systemtray.png|link=|center]]

After opening, you will see all the Phidgets that are plugged into your machine, as well as any Phidgets that are on your network.

[[File:Windows ControlPanel General.PNG|link=|alt=Windows Control Panel General|center]]

Click on the '''+''' beside a device to expand it so that you can see all available channels. Double-click on one of these channels to open up a window that lets you interact with it.

[[File:Controlpanel_openapplication.png|500px|link=https://cdn.phidgets.com/docs/images/b/bd/Controlpanel_openapplication.png|alt=Windows Control Panel General|center]]

The Phidget Control Panel can be used for testing devices, updating firmware, enabling a Phidget Network Server, and more. Visit the [[Phidget Control Panel|Phidget Control Panel page]] for more information.

===Programming===
When you are ready to develop your own applications, visit our [{{SERVER}}/docs/Programming_Resources programming resources page] and select your programming language to get started.

==Software License==
By downloading the installer and/or development files, you agree to adhere to the terms of the [{{SERVER}}/documentation/Licenses/Phidgets_EULA.pdf Phidgets End User License Agreement]. The Phidget libraries and development files are covered by the The 3-Clause BSD License.

OS - Windows

2026-03-02T22:27:56Z

Lmpacent: /* Install */

<metadesc>Communicate over USB with sensors, controllers and relays with Phidgets! Program in Windows using a wide variety of programming languages.</metadesc>
[[Category:OS]]

==Quick Downloads==
Our libraries support Windows 8 and newer.

*[https://cdn.phidgets.com/downloads/phidget22/libraries/windows/Phidget22-x64.exe Installer Download (64-bit)]
*[https://cdn.phidgets.com/downloads/phidget22/libraries/windows/Phidget22-ARM64.exe Installer Download (ARM64)]
*[https://cdn.phidgets.com/downloads/phidget22/libraries/windows/Phidget22-x86.exe Installer Download (32-bit)]

===Other Resources===
* [[OS - Windows Advanced Information|Windows Advanced Information]]
*[https://cdn.phidgets.com/downloads/phidget22/libraries/windows/Phidget22-windevel.zip Windows Development Files]
* [https://www.phidgets.com/downloads/phidget22/libraries/windows/ Previous Releases]

==Getting Started with Windows==
===Install===
To get started, download the appropriate [[#Quick Downloads|installer]] for your machine from the list above. This will install the Phidget Control Panel and the Phidget Network Sever. These are powerful tools that will help you develop your Phidget applications.

===Phidget Control Panel===
After installing, you can find the application through your system tray, or by opening the start menu and searching for ''Phidget Control Panel''.

[[Image:Os_windows_systemtray.png|link=|center]]

After opening, you will see all the Phidgets that are plugged into your machine, as well as any Phidgets that are on your network.

[[File:Windows ControlPanel General.PNG|link=|alt=Windows Control Panel General|center]]

Click on the '''+''' beside a device to expand it so that you can see all available channels. Double-click on one of these channels to open up a window that lets you interact with it.

[[File:Controlpanel_openapplication.png|500px|link=https://cdn.phidgets.com/docs/images/b/bd/Controlpanel_openapplication.png|alt=Windows Control Panel General|center]]

The Phidget Control Panel can be used for testing devices, updating firmware, enabling a Phidget Network Server, and more. Visit the [[Phidget Control Panel|Phidget Control Panel page]] for more information.

===Programming===
When you are ready to develop your own applications, visit our [{{SERVER}}/docs/Programming_Resources programming resources page] and select your programming language to get started.

==Software License==
By downloading the installer and/or development files, you agree to adhere to the terms of the [{{SERVER}}/documentation/Licenses/Phidgets_EULA.pdf Phidgets End User License Agreement]. The Phidget libraries and development files are covered by the The 3-Clause BSD License.

OS - Windows

2026-03-02T16:50:34Z

Lmpacent:

<metadesc>Communicate over USB with sensors, controllers and relays with Phidgets! Program in Windows using a wide variety of programming languages.</metadesc>
[[Category:OS]]

==Quick Downloads==
Our libraries support Windows 8 and newer.

*[https://cdn.phidgets.com/downloads/phidget22/libraries/windows/Phidget22-x64.exe Installer Download (64-bit)]
*[https://cdn.phidgets.com/downloads/phidget22/libraries/windows/Phidget22-ARM64.exe Installer Download (ARM64)]
*[https://cdn.phidgets.com/downloads/phidget22/libraries/windows/Phidget22-x86.exe Installer Download (32-bit)]

===Other Resources===
* [[OS - Windows Advanced Information|Windows Advanced Information]]
*[https://cdn.phidgets.com/downloads/phidget22/libraries/windows/Phidget22-windevel.zip Windows Development Files]
* [https://www.phidgets.com/downloads/phidget22/libraries/windows/ Previous Releases]

==Getting Started with Windows==
===Install===
To get started, download the appropriate [[#Quick Downloads|installer]] for your machine from the list above. This will install the Phidget Control Panel, a powerful tool that will help you develop your Phidget applications.

===Phidget Control Panel===
After installing, you can find the application through your system tray, or by opening the start menu and searching for ''Phidget Control Panel''.

[[Image:Os_windows_systemtray.png|link=|center]]

After opening, you will see all the Phidgets that are plugged into your machine, as well as any Phidgets that are on your network.

[[File:Windows ControlPanel General.PNG|link=|alt=Windows Control Panel General|center]]

Click on the '''+''' beside a device to expand it so that you can see all available channels. Double-click on one of these channels to open up a window that lets you interact with it.

[[File:Controlpanel_openapplication.png|500px|link=https://cdn.phidgets.com/docs/images/b/bd/Controlpanel_openapplication.png|alt=Windows Control Panel General|center]]

The Phidget Control Panel can be used for testing devices, updating firmware, enabling a Phidget Network Server, and more. Visit the [[Phidget Control Panel|Phidget Control Panel page]] for more information.

===Programming===
When you are ready to develop your own applications, visit our [{{SERVER}}/docs/Programming_Resources programming resources page] and select your programming language to get started.

==Software License==
By downloading the installer and/or development files, you agree to adhere to the terms of the [{{SERVER}}/documentation/Licenses/Phidgets_EULA.pdf Phidgets End User License Agreement]. The Phidget libraries and development files are covered by the The 3-Clause BSD License.

File:Os windows systemtray.png

2026-03-02T16:49:11Z

Lmpacent:

Solid State Relay Guide

2025-11-25T22:05:17Z

Lmpacent: /* I need Gradual Dimming */

{{#seo:|description=Interested in learning about solid state relays? This guide explains the basics: what solid state relays are, how solid state relays work, how to choose a solid state relay and more.}}
{{#seo:|keywords=relay}}
[[Category:IntroGuide]]

<div class="toclimit-2">__TOC__</div>

==Introduction==
[[Image:SSR.jpg|thumb|link=|A "hockey puck" SSR, so named because of its thick shape and black color. They are specifically designed to switch either AC loads or DC loads, but never both.]]

Solid state relays (SSRs) turn on or off the power being supplied to other devices, in a similar fashion as a physical switch. However, instead of being switched by human interaction like a physical switch, SSRs are switched electronically.
With SSRs, you can control high-current devices such as lights or appliances with low-current signals, like a standard DC signal from a digital output. Many SSRs will switch on with a voltage of 3V or higher. This makes them perfect for use with the [[InterfaceKit Digital Outputs|Outputs on Phidget InterfaceKits]], or any other device with a digital output, such as the [{{SERVER}}/?prodid=714 OUT1100 - Digital Output Phidget]. Using the ports of a {{VINTHub}} in digital output mode may not work, since they may not provide enough power to activate the SSR. If your digital output is not powerful enough, you may want to connect an external MOSFET to switch a more suitable supply to control the SSR.

SSRs perform the same job as [[Mechanical Relay Guide|Mechanical Relays]], but have the following advantages:
* SSRs produce less electromagnetic interference than mechanical relays during operation. This is mostly due to the absence of a phenomenon called [[Mechanical Relay Guide#Arcing, Interference, and Sticking|contact arcing]] only present in mechanical relays, where the physical contacts of the relay tend to spark internally while switching. The reduced interference can also be attributed to the fact that SSRs do not use electromagnets to switch.
* The switch contacts of a mechanical relay will eventually wear down from arcing. An SSR will have a longer life because its internals are purely digital. Properly used, they will last for millions of cycles.
* SSRs turn on and off faster than mechanical relays (≈1ms compared to ≈10ms).
* SSRs are less susceptible to physical vibrations than mechanical relays.
* Since the switch inside an SSR isn't a mechanical switch, it does not suffer from [[Mechanical_Relay_Guide#Contact_Bounce|contact bounce]] and operates silently.

However, compared to Mechanical Relays, SSRs:
* Are more expensive.
* Will dissipate more energy in the form of heat (1-2% of the energy intended to power the load).

==How SSRs Work==
[[Image:SSR_Internals.png|thumb|link=|A conceptual diagram of the insides of an SSR.<br />]]
The control inputs are connected internally to an LED, which shines across an air gap to light sensors.
The light sensor is connected to the transistors which open or close, supplying the relay's load with power.
When a transistor is '''closed''', current can flow freely through the relay, causing the load and power supply to be connected.
When a transistor is '''open''', almost all current is blocked, causing the load to become disconnected from the power supply.
The pairing of an LED with light sensors is called an optocoupler, and is a common technique to link two parts of a circuit without a direct electrical connection.
<br clear=all>
===Basic Use===
Controlling an SSR is no more complicated than turning an LED on and off. Switch it on, switch it off, it's that easy.

The ability of an SSR to switch a load is very similar to a [[Mechanical Relay Guide|mechanical relay]] or simple switch.
By turning the digital output controlling the relay on and off, you control whether or not the load is connected to its power supply.

The challenge is to pick an appropriate type of SSR for your application. There is no single SSR perfect for all applications. To choose an SSR for your particular application, please follow the [[#Choosing an SSR|Choosing an SSR]] section.
<br clear=all>

===Safety===
[[File:relay_safety.jpg|thumb|500px|link=|Two circuit diagrams showing the improper and proper ways of switching mains electricity with a relay.<br />]]

Since relays switch high currents and voltages, standard electricity safety precautions apply. Make sure you never touch the terminals while the relay is powered. If your SSR came with a plastic cover, use it. Even when the SSR is switched off, a very small amount of current will flow.

When placing a relay in a circuit, it is always a good idea to put it between the power supply and the load, especially when using higher voltages. If the relay is instead placed between the load and ground, the circuit will still work the same, but when the relay is open, the load will still be directly connected to the power supply. This could cause safety concerns because someone might touch the terminals on the load, thinking it's safe because the device appears to be off. If the electricity finds a path to ground through their body, they will be electrocuted. If the relay is placed between the power supply and the ground, electrocution would only be a risk if the live terminal on the relay is touched. Again, the relay terminals should always be properly covered to avoid the risk of electrocution.

When an SSR fails, it most often fails permanently closed. This is because when the transistor inside fails due to excessive current or heat, it will usually short out, allowing current to pass through unimpeded.
This means that as long as the power supply remains on, the load will be powered, possibly creating a fire or safety hazard.

<br clear=all>

==Choosing an SSR==
===Identify your voltage===
First, determine whether you need to switch AC or DC voltage. The electrical grid, and thus your wall outlet, runs AC, whereas batteries and most small power supplies are DC.

Next, determine the maximum number of volts you will be switching. If you are switching DC, particularly with batteries, assume your voltage is at least 25% more than what your battery is rated for. Even larger fluctuations occur on AC, but AC SSRs are designed to handle these surges. Typical AC voltage from a wall socket in North America is 110VAC, whereas in Europe it is usually 220VAC. If you are switching AC voltage from a wall socket, check which standard your country uses, and use that number as your voltage.

===Identify your current===
The current drawn by your load when turned on affects how large of an SSR you need, and how hot it will be when it is in use. If you know how much current, on average, your load draws, this is what we call ''Average Load Current''. If you don't know the average current, but you know the wattage (power rating) of your load, you can calculate Average Load Current by:

<center>
<math>
\text{Average Load Current} =\frac{\text{Watts}}{\text{Operating Voltage}}
</math>
</center>

Next, you need to know the current drawn by your load when it is first turned on. Many loads demand a huge inrush of current when the load is first turned on. This places a significant amount of stress on the electronics inside the SSR. If you've ever noticed the lights dimming in the house for a second when the furnace starts up, this is caused by the fan motor starting up. In the same way that it takes a lot of force to move a heavy object from rest, it initially takes a lot of current to power up a fan or incandescent bulb. It's very difficult to measure the '''Surge Current''' itself, so we use a multiplier based on your device type. Surge Current is also referred to as '''inrush current'''.

{|class="wikitable" style="text-align: center; margin:auto; width: 50%"
|-
|style="background: #f0f0f0"|'''Application '''
|style="background: #f0f0f0"|'''Multiplier '''
|-
| Incandescent Light Bulbs
| 6x
|-
| Motors
| 6x
|-
| LEDs
| 1x
|-
| Complex Electronics i.e., Motor Controllers, Phidgets
| 6x
|-
| Fluorescent Light Fixtures (AC Only)
| 10x
|-
| Transformers
| 20x
|-
| Heaters
| 1x
|-
|}

Multiply your Average Load Current by the multiplier for your device type to calculate the Surge Current.

===I need to switch AC===
Most AC applications will be switching 110 to 240 Volt power coming from the grid. If that's you, go to the [[#Mains Voltage (110 to 240V AC)|Mains Voltage (110 to 240V AC)]] section.

We also cover low voltage AC applications - 28 VAC (Volts AC) or less. For more information, visit the [[#AC/DC SSRs|AC/DC SSRs]] section.

===I need to switch DC===
If you only need to switch a small amount of current - 9 Amps or less, consider our compact, cost effective [[#AC/DC SSRs|AC/DC SSRs]].

If you need to switch more than 9 Amps, you need a serious [[#DC SSRs|DC SSR]].

If you need to switch up to 4 small loads of 8 Amps or less, you can use the open collector (externally powered) digital outputs on a [{{SERVER}}/products.php?product_id=REL1100 REL1100 - 4x Isolated SSR Phidget], which can be wired to behave similarly to relays. If you need even more relays, have a look at the [{{SERVER}}/products.php?product_id=REL1101 REL1101 - 16x Isolated SSR Phidget].

==I Need Gradual Dimming==
Instead of simply turning the load on/off, if you want to dim it gradually, you can use a proportional control SSR. They are able to reduce the average power to the load gradually, in proportion to the strength of the input signal. For more information, you can visit the [[#Proportional Control SSR|Proportional Control SSR Section]].

==Mains Voltage (110 to 240V AC)==
We sell AC SSRs for 120 VAC or 240 VAC operation. If you are unsure what voltages you could eventually need to switch, the 240 VAC relays can be used to switch 120 VAC with no problems. Please note we are very conservative in how we rate SSRs - our 120 VAC relays are rated by the manufacturer for 240 VAC, and the 240 VAC for 480 VAC. We strongly recommend against using them to the manufacturer rated voltage. To understand why, read the [[#AC SSR Protection|AC SSR Protection]] section.

===Load Type - Inductive vs. Resistive===
[[Image:zero cross.png|right|link=|thumb|400px|This graph shows the difference between zero-cross and random turn-on. The blue line represents the oscillating voltage of an AC load, and the shaded areas represent the sections when the relay is turned on and letting current pass through. As you can see, the random turn-on SSR immediately opens when activated, while the zero-cross turn-on SSR waits until the voltage crosses zero before opening.<br />[[Media:zero cross.png|Full-size Image]]]]

If your load is inductive, you need to choose a '''Random Turn On''' relay. If your load is resistive, choose a '''Zero Crossing''' relay.

Your Load will probably be inductive if it is built around a large coil of wire - motors and transformers are typical examples. A load considered resistive may also have loops of wire - for instance, hair dryers, toasters, incandescent bulbs use twisted wire elements to generate the heat. An inductive load will have thousands of loops of wire - it's a matter of scale. There is no such thing as a perfectly resistive load - but a load has to be very inductive to cause the zero crossing SSRs to malfunction.

SSRs are designed to either turn on immediately ('''Random Turn On'''), or wait until the next 'alternation' of the voltage ('''Zero Crossing'''). Zero Crossing SSRs create less electromagnetic 'noise' when they turn on. They are best used with resistive loads - Zero Crossing SSRs are not able to turn off some inductive loads. It's very difficult to determine which inductive loads will create problems - well beyond the scope of this document. If your load is inductive, we recommend buying the '''Random Turn On''' SSRs.

{|class="wikitable" style="text-align: center; margin:auto; width: 50%"
|style="background: #f0f0f0" | '''Application'''
|style="background: #f0f0f0" | '''Load Type'''
|-
| Incandescent Light Bulbs
| Resistive
|-
| Fluorescent Light Fixtures
| Inductive or Resistive <font size=4>'''*'''</font>
|-
| Motors
| Inductive
|-
| Transformers
| Inductive
|-
| Heaters
| Resistive
|-
| Computer / Electronics
| Resistive
|-
| AC/DC power supplies (brick heavy type)
| Inductive
|-
|AC/DC Power supplies (lightweight switchers)
| Resistive
|}

<font size=4>'''<nowiki>*</nowiki>'''</font> ''For fluorescent light fixtures, older units (magnetic ballast) may be inductive, and newer units are often resistive (electronic ballast).''

===Choosing your AC SSR===
Now that you have identified your Operating Voltage, Average and Surge Current, and your load type (inductive or resistive), you can create a short list of relays whose
* '''Maximum Load Voltage''' are greater than or equal to your operating voltage,
* '''Maximum Surge Current''' are greater than or equal to your surge current, and
* '''Load type''' matches what you chose for random turn on/zero crossing.

Now compare the '''Maximum Load Current without Heatsink''' value for the SSRs on your list to your Average Load Current. If your Average Load Current is greater, you may need a heatsink. For selecting a heatsink, please consult [[#Picking a heatsink|Picking a Heatsink]]. Alternatively, look at other SSRs on your list - there may be an SSR that can handle your average load current with no heatsink

At this point, you know the SSR you need.

Instead of simply turning the load on/off, if you want to dim it gradually, you can use a proportional control SSR. They are able to reduce the average power to the load gradually, in proportion to the strength of the input signal. For more information, you can visit the [[#Proportional Control SSR|Proportional Control SSR Section]].

If you are interested in learning more about SSRs in general, check out our [[#Did you know?|"Did you know?"]] section.

===AC SSR Protection===
[[Image:MOV.jpg|thumb|link=|An MOV, which comes packaged with our AC "Hockey Puck" relays. ]]

Your AC SSR from Phidgets comes with a circular disc with two legs (pictured). This is a Metal Oxide Varistor (MOV) and should be installed across the load (larger) terminals of your SSR. MOVs are the classic surge protector - an inexpensive component that absorbs high voltage spikes. High voltage spikes are caused by inductive loads when they are turned off, and also happen very often on the electrical grid, as nearby devices are operated. Even if your load is resistive, use an MOV to protect the SSR.

Matching an MOV to an SSR is not easy - this is why we include an MOV with your SSR. If an MOV is chosen for too low of a voltage spike, it will wear out quickly. If it is chosen for too high of a voltage spike, it will not protect the SSR adequately. To balance SSR protection against MOV lifetime, we have found it necessary to use SSRs built for 240 VAC in 120 VAC applications, and SSRs built for 480 VAC in 240 VAC applications. If you must operate our AC SSRs on higher voltages than we recommend, do not use the included MOV.

As MOVs wear out from use, they will become more sensitive to common voltage spikes, causing them to wear out quicker. When they entirely fail, they will become a short circuit, potentially creating a fire hazard. The MOV included with your SSR has a fuse built in which will disable the MOV when it becomes a hazard. To be on the safe side, avoid mounting your SSR near any flammable material.

For reference, the part number of the MOV shipped with our AC SSRs is '''TMOV20RP200E'''.

===Proportional Control SSR===
Proportional Control Relays (often simply called "Control Relays") are SSRs you can use to control the amount of power to the load. Rather than reduce the voltage, or somehow limit the current - which would be very expensive solutions, the Proportional SSR reduces power by turning the load on/off quickly, feeding full power in short pulses.

Proportional SSRs are controlled by a variable voltage - as the control voltage increases, more power is available to the load. Our PhidgetAnalog product can be used to control Proportional SSRs, since an analog output can output various amounts of voltage, as opposed to a digital output, which only has two states- high and low. We don't sell Proportional SSRs - but they can be purchased from [http://www.digikey.com Digikey], where they are called AC Linear Controlled SSRs.

A quick and dirty solution for dimming with Phidgets is to use an {{LinksNeeded|RC Servo Motor|[[Servo Motor and Controller Guide|RC Servo Motor]]}} with a PhidgetAdvancedServo controller to rotate the knob on a light dimmer. From software, the RC Servo Motor is rotated to the desired position, cranking the knob as it turns. While this may seem like a roundabout way of achieving proportional control, dimmers tend to be much less expensive because they are less specialized and are manufactured in greater quantity.

===Example circuits with AC SSRs===
[[Image:AC SSR Load.png|right|thumb|link=|400px|Schematic of an AC SSR switching a generic load. A metal oxide varistor is added across the load to protect the SSR.<br />[[Media:AC SSR Load.png|Full-size Image]]]]

When wiring up an AC circuit, particularly for long term installation, you may find it helpful to buy a book on residential wiring from your local hardware store. There are many wiring conventions (and often legal codes) which will help you plan your project, and the legal codes are often a great source of wisdom.

<br clear="all">

==DC SSRs (0 to 50V DC)==
We sell DC SSRs for that switch a maximum load of 50 volts. If you are unsure what voltages you could be switching in the future, higher voltage DC SSRs can be used to switch lower voltages. Common engineering practice would be to purchase an SSR rated for 50-100% higher voltage than the voltage you plan to be switching. For instance, if you are switching 24V, a 50V SSR is reasonable.

===Choosing your DC SSR===
Now that you have identified your Operating Voltage, Average and Surge Current, you can create a short list of relays whose
* Maximum Load Voltage are greater than or equal to your operating voltage,
* Maximum Surge Current are greater than or equal to your surge current, and
* Maximum Average Current is greater than or equal to your Average current.

Now compare the '''Max. Load Current without Heatsink''' value for the SSRs on your list to your Average Load Current. If your Average Load Current is greater, you may need a heatsink. For selecting a heatsink, please consult [[#Picking a Heatsink|Picking a Heatsink]]. Alternatively, look at other SSRs on your list - there may be an SSR that can handle your average load current without a heatsink. SSRs rated for a larger load than the load you're using will be more efficient (meaning less energy lost in the form of heat) than an SSR that's being operated at its maximum load.

At this point, you know the SSR you need.

If you are interested in learning more about SSRs in general, check out our [[#Did you know?|"Did you know?"]] section.

===DC SSR Protection===
[[Image:Diode.jpg|thumb|400px|link=| A diode, included with our DC "hockey puck" SSRs. The cathode is marked with a line. The blue symbol shows circuit diagram equivalent of the diode.<br>[[Media:Diode.jpg|Full-Sized Image]]]]
[[Image:relaymotor.jpg|400px|thumb|link=| A DC SSR switching an electric motor. The 1018 Phidget InterfaceKit controls the SSR using its digital outputs. A diode is shown installed across the motor, and a fuse is hooked up between the power supply and the rest of the circuit.<br>[[Media:relaymotor.jpg|Full-Sized Image]]]]

Your DC SSR from Phidgets comes with a diode. This diode should be installed across your load, with the Cathode installed towards the positive terminal of the power supply (as shown in the diagram).

If the diode is installed backwards, as soon as the SSR is turned on, the load will be shorted out, likely destroying the diode, or the SSR, or your power supply.
A fuse protecting your power supply is always a good idea. You can place the fuse in between the positive terminal of the power supply and the positive terminal of the load side of the SSR.

The diode protects the SSR from powerful residual currents after the SSR is turned off. While your load is being driven, inductance builds up magnetic fields around the wiring.
Every load is inductive to some degree, and when the SSR turns off, the magnetic fields will ram current against the now open SSR, easily damaging it. The diode allows these currents to recirculate in the load until they have lost their energy.

For reference, the part number of the diode that comes with our DC SSRs is '''10A02-T'''.

<br clear="all">

===Example circuits with DC SSRs===
[[Image:DC SSR Load.png|right|link=|thumb|400px|Schematic of an DC SSR switching a generic load, which is protected by a diode connected in parallel. The circuit is protected by a fuse in series after the power supply.<br />[[Media:DC SSR Load.png|Full-size Image]]]]

The electrical isolation built into a DC SSR allows them to be placed within a circuit just like a switch. Since it is isolated, you don't have to worry about grounding or voltage offsets.

With a DC SSR, always make sure the positive load terminal (labeled +) is facing towards the positive terminal of the power supply. If the load terminals are reversed, your load will immediately turn on. There is a diode inside of the SSR that allows current to flow freely through it when the SSR is connected incorrectly. This feature is included because this sort of wiring mistake would destroy the transistor in the DC SSR otherwise.

The DC SSR can be installed on either side of the load, and it will work properly, but there is an advantage to installing the SSR between the power supply and the load. If the load is connected to the power supply, it will always have a potentially dangerous voltage on it, even when it is not operating.

<br clear="all">

==AC/DC SSRs (0 to 40V DC / 0 to 28V AC)==
[[Image:AC_DC_SSR.png|thumb|link=|A small, versatile AC/DC SSR mounted on a Phidgets board for easy pin access.]]

Our AC/DC SSRs are built on a small PCB, making them physically smaller than the large "hockey puck" SSRs, and less expensive. They are limited to lower currents, and cannot be mounted on a heatsink.

We sell AC/DC SSRs that can switch up to 40 Volts DC or 28 Volts AC. This is indicated on the SSR Product pages under the Maximum Load Voltage specification. There is no lower limit on the voltages that the AC/DC SSRs can switch. If your voltage is close - be conservative. For instance, a 36 Volt system built from 3 Lead Acid batteries can reach 45 volts when charging.

===Picking your AC/DC SSR===
Now that you have identified your Operating Voltage, Average and Surge Current, you can create a short list of relays whose
* Maximum Load Voltage are greater than or equal to your operating voltage,
* Maximum Surge Current are greater than or equal to your surge current, and
* Maximum Average Current is greater than or equal to your Average current.

If you are interested in minimum cost, you will likely choose the cheapest option that meets these criteria. If you are interested in high efficiency operation and less heat generation, consider buying an SSR with higher current rating.

Your AC/DC SSR from Phidgets has built in protection from static electricity, and dangerous residual currents after the SSR is turned off. If the load you are switching is powered by a DC source, installing a diode across the load will offer even more protection. Refer to the [[#DC SSR Protection|DC SSR Protection]] section for more information.

To learn more about SSRs in general, visit the [[#Did you know?|"Did you know?"]] section.

<br clear="all">

===Example circuits with AC/DC SSRs===
[[Image:Versatile SSR DC Load.png|thumb|link=|A versatile AC/DC SSR switching a DC load. The load terminals are bidirectional, so it doesn't matter which way you hook them up. The optional diode can be added to help protect the SSR when switching DC loads.<br />[[Media:Versatile SSR DC Load.png|Full-size Image]]]]
[[Image:Versatile SSR AC Load.png|thumb|link=|A versatile AC/DC SSR switching an AC load.<br />[[Media:Versatile SSR AC Load.png|Full-size Image]]]]

The electrical isolation built into a AC/DC SSR allows them to be placed within a circuit just like a switch. Circuits without electrical isolation require a lot more care - proper grounding, careful consideration of voltage offsets.

<br clear="all">

==Using heatsinks with Hockey Puck SSRs==
[[Image:3950_0 Accessories Web.jpg|thumb|link=|A "hockey puck" SSR with plastic cover (left), a thermal pad (right). All hockey puck SSRs sold at Phidgets come with both of these accessories plus a diode or varistor to protect the SSR.]]
[[Image:3955_0 Functional Web.jpg|thumb|link=|A "hockey puck" SSR mounted on a small heatsink by two screws. The thermal pad is pressed between the SSR and the heatsink.]]

SSRs will only achieve their promise of reliability and long life if they are kept cool. Cool is relative, of course, but a good rule of thumb is to keep the metal base of the SSR at less than 85°C (185°F). A [[Thermocouple Guide|thermocouple]] can be used to precisely measure the temperature of the metal base.

Excess heat usually comes from too much current and too little heatsinking. A lot of heat can also be generated by frequently turning the relay on and off. If your relay is operated for brief periods of time, you may not need as large of a heatsink - provided the relay is never accidentally left on for extended periods. Unless space is a concern, it's better to err on the side of caution.

Before buying a heatsink, consider if you actually need it. If your application is running at room temperature, and your average current is less than the '''Max. Load Current without Heatsink''' specification of your SSR, then you don't need a heatsink. Alternatively, if your project has a large metal chassis that the SSR can bolt to, this can be used as your heatsink.

Each SSR suitable for use with heatsinks will include a specification of how much current it can switch with each heatsink we sell. This specification assumes a reasonable airflow over the heatsink, and that the flowing air is at room temperature. Our SSRs have a sheet of metal underneath, where the heat is concentrated - this is also where the heat is measured to tell if the SSR is too hot. Phidgets includes a thermal pad with our Hockey Puck SSRs (see pictured). You place this pad under an SSR when mounting it on a heatsink, or on large metal surfaces that can dissipate heat. The pad performs the same function as thermal grease - it helps conduct heat between the base of the SSR and the heatsink. If you prefer to use thermal grease, you can use it instead of the pad. Our heatsinks include screws for mounting SSRs. Use a good size screwdriver when tightening the SSR down on the heatsink to ensure good conduction.

You can see our selection of heatsinks in the [http://www.phidgets.com/products.php?category=9 relays] category of our store.

<br clear="all">

==Hooking up wires to the Hockey Puck SSR==
[[Image:relay_mov.jpg|thumb|link=|An AC SSR with the wires attached normally and an MOV installed across the load side.]]
[[Image:lugs.jpg|thumb|link=|TRM6 wiring lugs connected to a DC SSR.]]

When wiring your load to the SSR, the wire is looped clockwise around the terminal, so when the screw is tightened down, it will draw the wire in tighter. We recommend using wires up to 10 AWG in size - any larger, and the screws will not have enough thread left to tighten down, and they will strip. Larger wires can be attached using a wiring lug. The lug is clamped under the SSR screw, and the wire attaches to the lug.

{|class="wikitable" style="text-align: center;"
|style="background:#f0f0f0;"|'''Terminal Block Width (mm/port)'''
|style="background:#f0f0f0;"|'''Recommended Wire Gauge (AWG)'''
|-
|3.81
| 16 to 26
|-
| 5.0
| 12 to 24
|-
| 9.5
| 10 to 26
|-
|}

Loose wire connections can generate a lot of heat - use a large enough screwdriver when clamping down the load wires to ensure that the screws are on tight enough.

<br clear="all">

==Did you know?==
* Mains Voltage '''AC SSRs''' cannot switch DC. They will never turn the load off. AC SSRs turn off twice per AC Cycle, when the current changes direction and is momentarily zero. For example, AC is 60 Hz in North America, so the AC SSR has 120 opportunities per second to turn off (the SSR will only '''stay''' off if the control signal is low). If the SSR is operating from DC, the current will flow continuously, and the load will not turn off, even when the control input is off.

* An '''AC SSR''' turns off automatically every time the load current reaches zero. It will turn back on almost immediately as long as the signal controlling the SSR is high. An AC SSR will actually have a low, non-zero current value that it regards as 'zero'. This specification is usually called "Minimum Load Current" in the data sheet. If your load requires less than this minimum current, your SSR will never turn on, or will not reliably turn on. The simplest solution to this problem is to connect another load in parallel with the first, increasing the Current required by the load.

* SSR Manufacturers have started adding a simple circuit inside '''AC SSRs''', across the load terminals, called a snubber. The snubber absorbs very fast electrical changes that could normally cause an '''AC SSR''' to turn on accidentally. When the AC SSR is turned on, there is little voltage difference between the terminals, so the snubber has very little effect. When the AC SSR is turned off, the snubber is actively protecting the SSR - but at a cost, as it allows a small current through the SSR, which is wasted.

* An '''AC SSR''' uses bipolar transistors - an old technology that has been replaced by CMOS transistors in modern digital circuits. Bipolar transistors are still superior for handling high voltages. Bipolar transistors, and the more complex transistors built from them, will lose a constant voltage as current flows through them. The collection of transistors in your SSR will lose about 1.7 volts - so on a 120 VAC system, you will lose about 1.5% to the SSR. This energy converts to heat inside the SSR, and the heating from these transistors is the reason SSRs often need heatsinks.

* SSRs, and semiconductors in general, usually fail as a short circuit. A short circuit is a circuit whose internals have been damaged such that current can flow through it freely. This means your load will probably turn on permanently (until you disconnect the power source) - make sure this doesn't cause a safety hazard. For instance, Sauna Heaters have a simple thermally-triggered mechanical shutdown to protect them if control electronics fails.

* '''DC SSRs''' (at least the units we sell) use Metal Oxide Semiconductor Field Effect Transistors (MOSFETs). MOSFETs do not lose a constant voltage - instead, when they turn on, they act as a very slight restriction to the flow of current - a resistor. At low currents, the slight restriction wastes very little power, giving high efficiency and often not requiring a heatsink. This efficiency is lost as the current increases - a doubling of current quadruples the production of heat.

* Normally, a MOSFET can only block current in one direction - as soon as the voltage reverses, the current flows through a diode run in parallel to the MOSFET. If a MOSFET were used to switch AC, the load would be turned on half the time. A common solution is to use two MOSFETs back to back - which is what we do with our '''AC/DC SSRs'''.

Mechanical Relay Guide

2025-11-13T22:28:27Z

Lmpacent: /* Basic Use */

{{#seo:|description=Mechanical relays can switch a power or signal line by physically moving metal contacts with an electromagnet. Learn more here.}}
{{#seo:|keywords=relay}}
[[Category:IntroGuide]]
<div class="toclimit-3">__TOC__</div>

==Introduction==
Mechanical relays are devices that can turn on or turn off the power supplied to another device, like a switch. However, instead of having a person flip the switch, mechanical relays switch when provided with a small amount of power. This allows high-power circuits to be controlled by low-power devices.

They perform the same function as [[Solid State Relay Guide|Solid State Relays]], except they are less expensive and have a shorter lifespan.
You can use them to control [[LED Guide|LEDs]], heaters, appliances, and generally any powered device as long as the power you're switching falls within the limits of the relay you're using.
[[File:1014_3.jpg|link=|center|400px]]

We sell boards with multiple relays on them (such as the [{{SERVER}}/?prodid=1228 PhidgetInterfaceKit 0/0/4], shown above), making it easy to control many separate circuits with your computer.

==How it works==
[[File:Mechanical_relay.jpg|thumb|link=|500px|<center>The switching arm and contacts of a mechanical relay.</center>]]
Mechanical relays use an electromagnetic coil to open or close the circuit. When current runs through the input and energizes the coil, it creates a small magnetic field which either pulls the arm of the switch away from the other contact of the switch, or pushes it down to close the switch depending on the how the switch is made. A relay also serves as an isolator, because the control (input) and load (output) ends of the relay are not electrically connected. This allows you to protect the device you're using to control the relay from power surges in your application.

===Basic Use===
Controlling a mechanical relay is as easy as turning on an LED or light bulb. By simply supplying enough power to energize the electromagnetic coil, you will be able to control a mechanical relay.

A normal digital output will not be powerful enough without external components as described in the [[InterfaceKit Digital Outputs#Controlling a Relay with a N-Channel MOSFET| relay section of the Digital Output Guide]]. A Phidget with open collector digital outputs (such as the [{{SERVER}}/?prodid=720 REL1100] or [{{SERVER}}/?prodid=721 REL1101]), on the other hand, will be able to control a relay on its own.

Relays are often used in large quantities to turn multiple devices on and off in a particular order or timing. For example, a popular trend has been to hook up many strands of Christmas lights to multiple relays and a control system in order to make them flash in rhythm with specific music.

Relays are designed to be controlled by a particular voltage applied to the coil. If you buy a relay product from us, this is taken care of for you. You will be able to switch the relays via USB with the Digital Outputs on a [[InterfaceKit Digital Outputs|Phidget InterfaceKit]] or {{VINTHub}}. If you are integrating your own relay, you'll want to keep an eye on the specifications.

The relay coil is also specified for a particular current. For example, a 5V relay might require 70mA. If you connect this relay to a very weak source of 5V, like a digital output, the output will not be able to provide 70mA, and there will not be enough current to switch the relay.

The load side of the relay also requires a minimum current. This minimum load current (also called "wetting current") is a requirement because the electricity needs to conduct through an oxide layer that forms on the contacts of the relay. If the minimum load current requirement of your relay is too high, you won't be able to use it to switch a signal (such as the data line on an analog sensor), you'll only be able to switch power to a circuit. If you're using a relay to switch a signal, [[#Contact Bounce|contact bounce]] might also be a problem.

====Switching Speed and High-Frequency Switching====
Even though they use moving mechanical parts, mechanical relays switch very quickly. The amount of time it takes for current to begin flowing through the circuit from when the relay's input is activated is in the order of tens of milliseconds. For extremely time-sensitive applications that need to minimize switching delay, [[Solid State Relay Guide|Solid State Relays]] can switch as quickly as 1ms.

You should be careful when using mechanical relays in applications that require very frequent switching. Typically, mechanical relays can only manage one contact every few seconds- any quicker and they may begin to overheat.

===Safety===
[[File:relay_safety.jpg|thumb|450px|link=|Two circuit diagrams showing the improper and proper ways of switching mains electricity with a relay.<br />]]

Since relays switch high currents and voltages, standard electricity safety precautions apply. Make sure you never touch the terminals while the relay is powered.

When placing a relay in a circuit, it is always a good idea to put it between the power supply and the load, especially when using higher voltages. If the relay is instead placed between the load and ground, the circuit will still work the same, but when the relay is open, the load will still be directly connected to the power supply. This could cause safety concerns because someone might touch the terminals on the load, thinking it's safe because the device appears to be off. If the electricity finds a path to ground through their body, they will be electrocuted. If the relay is placed between the power supply and the ground, electrocution would only be a risk if the live terminal on the relay is touched. Again, the relay terminals should always be properly covered to avoid the risk of electrocution.

When an mechanical relay fails, it often fails permanently closed. This is because the contacts can actually weld to each other. See the section on [[#Arcing, Interference, and Sticking|Arcing, Interference, and Sticking]] for more information.
This means that as long as the power supply remains on, the load will be powered, possibly creating a fire or safety hazard.

<br clear=all>

==Choosing a Relay==
Since mechanical relays are nothing more than a controllable switch, they support both AC and DC loads.

The major deciding factor in choosing a mechanical relay is the amount of current it's capable of switching.
For example, the most current you can switch with the largest mechanical relay we sell is 5A DC or 10A AC.
If the load you're switching consumes more current than our mechanical relays can handle, take a look at our [[Solid State Relay Guide|Solid State Relays]].

===Switch Type===
One of the major characteristics of a mechanical relay is the design of the switch inside. A switch can generally be defined by the number of '''poles''' and '''throws''' it has. The number of "poles" refers to the number of individual circuits the switch controls. The number of "throws" refers to the number of positions the switch arm can occupy.

[[File:Switch_types.jpg|border|400px|link=|center]]

====Single Pole, Single Throw (SPST)====
This is a simple switch with only one path for the current to follow. The relay is either designed to be '''normally open (NO)''' or '''normally closed (NC)'''. If it is normally open, the arm of the switch is held away from the contact with a spring when the relay is off and the electromagnet pulls the arm to make contact and close the switch when the relay is turned on. If it is normally closed, the arm of the switch is held to the contact when the relay is off, and the electromagnet pulls the arm away when the relay is turned on.

While the decision to use a normally opened or normally closed relay may seem arbitrary at first, it is actually very important for certain applications. If you choose a normally closed relay, it means your load will remain powered as long as the relay coil is '''not''' powered. If some other part of your system fails, causing your relay to lose power, your load will remain powered even though it should not be. For loads that are potentially dangerous when left on (such as a heater, or a high-power load) it is best to use a normally open relay, so that in the event of a system failure, the load will remain off. On the other hand, circuits that are designed to be powered most of the time but temporarily interrupted will use less power if they use a normally closed relay. An example of this type of circuit is the radio in a car: When the engine is started, the radio circuit is momentarily switched off because the engine needs a large amount of battery power to start.

====Single Pole, Double Throw (SPDT)====
[[File:relay2loads.png|thumb|link=|300px|'''Toggle Between Two Loads'''<br />By connecting the power supply to the common terminal, and connecting a different load to the other two terminals, a relay with a SPDT switch can be used to toggle power between the two loads.<br />[[Media:relay2loads.png|Full-size Image]]]]

This switch has two paths for the current to follow. This type of relay is useful if you want to toggle power between two different loads, as pictured. You can also use a SPDT relay as a single pole, single throw switch, and it can function as '''normally open''' or '''normally closed''' depending on which pins (common and normally open, or common and normally closed) you connect the load to.

<br clear="all">

====Double Pole, Single Throw (DPST)====
This switch functions like two SPST switches, but both switches are controlled by one coil. This type of switch is useful for keeping two loads on separate circuits while still being able to have them turn on and off in unison.

====Double Pole, Double Throw (DPDT)====
This switch functions the same as a SPDT switch, except there are two of them, but are both controlled by a single input on the relay. You can use this type of switch to simultaneously control two separate circuits.

==Troubleshooting==
===Contact Bounce===
As with any mechanical switch, relays are susceptible to contact bounce. This means that when the switch closes, the arm can bounce on the contact, causing the load's power to flicker slightly. This usually only matters when the application is triggered by pulses in the power signal, or for applications where meaningful data is being switched instead of power. For example, a circuit designed to increment a counter every time power is applied to its input could incorrectly interpret a bouncing relay contact as multiple switch events. Or, a circuit that uses a relay to switch an audio signal between two different paths will experience some static noise when switching if there is significant contact bounce. It's worth mentioning that [[Solid State Relay Guide|Solid State Relays]] don't suffer from contact bounce, because they operate without using moving mechanical parts.

===Arcing, Interference, and Sticking===
[[File:contact_arc.jpg|border|link=|center]]
When a mechanical relay opens or closes, for the moment that the arm of the switch is very close (but not connected) to the contact, the electric current can arc through the air between the contacts.
This arc can cause interference with nearby electrical instruments and sensors. For example, if an unshielded cable carrying an audio signal is travelling past some relays whose contacts are arcing when they switch, the audio would contain bursts of static noise.

This arcing can also heat up the contacts of the switch enough that they can slowly degrade away until the relay no longer functions. They could also weld together, causing the relay to stay on permanently, which means your load will be powered constantly. If this imposes safety concerns, you should install a fail-safe of some kind. For example, some sauna heaters are turned on with a mechanical relay. In the event of a relay failure, the sauna heater will remain on and continue heating the room beyond the intended temperature. However, a simple mechanical temperature sensor is installed which cuts power to the heater if the room goes beyond a certain temperature.

Some relays are encased in a clear plastic enclosure (sometimes called "ice cube" relays), so the switch contacts can be easily inspected. By inspecting the contacts periodically, you could tell when the relay is getting near the end of its life.

===Prolonging Relay Lifespan===
In order to prolong the lifespan of your relay, avoid switching loads of higher voltage or current than the relay is built for, and avoid highly inductive loads, which worsen the effects of contact arcing. Your Load will probably be inductive if it is built around a large coil of wire - motors and transformers are typical examples. A load considered resistive may also have loops of wire - for instance, hair dryers, toasters, incandescent bulbs use twisted wire elements to generate the heat. An inductive load will have thousands of loops of wire - it's a matter of scale.

Additionally, you should avoid switching at or near the relay's maximum frequency if possible. You can think of a mechanical relay's lifespan in terms of number times switched rather than the amount of time it's used for. A relay that doesn't need to be switched very often can last a long time. If your application requires constant switching over long periods of time, it might be more cost-effective to use a [[Solid State Relay Guide|Solid State Relay]].

====Arc Suppression ====
[[File:Mechanical_relay_diode.jpg|link=|thumb|300px|'''DC Load Protection'''<br/>A diagram of a mechanical relay switching a DC load. An optional diode and fuse are used to protect the relay and prevent hardware damaged caused by improper wiring.<br/>[[Media:Mechanical_relay_diode.jpg|Full-sized Image]]]]
[[File:Mechanical_relay_mov.jpg|link=|thumb|300px|'''AC Load Protection'''<br/>A diagram of a mechanical relay switching an AC load. An optional MOV or Transil diode is placed in parallel to protect the relay from voltage spikes.<br/>[[Media:Mechanical_relay_mov.jpg|Full-Sized Image]]]]
The main cause of failure for mechanical relays is electricity arcing across the contacts during switching. To lengthen the lifespan of your relay, you can add various circuit elements that mitigate arcing.

For DC powered applications, one simple method of mitigating the effects of contact arcing is to place a feedback diode across the load, as pictured. This will allow some of the residual electricity in the circuit to recirculate through the load instead of contributing to the arc that forms when the switch makes the transition from closed to open. You can buy a suitable diode from any electronics distributor, like this [http://www.digikey.com/product-search/en/discrete-semiconductor-products/diodes-rectifiers-single/1376383?k=10a02 Diode] from Digikey.

For AC powered applications, you can put a Metal Oxide Varistor (MOV) across the load terminals of the relay in order to protect it from voltage spikes. An MOV will not remove the entire arc, but it will be helpful in circuits up to several hundred volts. You can buy an MOV from any electronics distributor, like this [http://www.digikey.com/scripts/dksearch/dksus.dll?keywords=tmov20rp200e MOV] from Digikey.

For low-voltage AC applications, a bi-directional transient voltage suppression diode ("transil diode") that is rated for higher than the AC voltage of the circuit can be placed across the relay terminals in order to protect it from voltage spikes. You can buy one from any electronics distributor, like this [http://www.digikey.com/scripts/dksearch/dksus.dll?keywords=p6ke47carl Transil Diode] from Digikey.

<br clear="all">

==Conclusion==

Mechanical relays are inexpensive and simple devices that allow AC or DC circuits to be switched on and off using a small amount of power.
They come in a variety of switch formats, enabling the user to build some very clever control into a circuit. Phidgets Inc. sells boards with multiple relays that can be connected directly to USB, or indirectly through a {{VINTHub}} so they can be controlled by your program.

Contact arcing and switch bounce can be an obstacle for some applications, but both are common problems and can be worked around fairly easily.
Mechanical relays don't last as long as solid state relays, but if you take care of them, they can be a good cost-effective alternative.

Mechanical Relay Guide

2025-11-13T22:26:08Z

Lmpacent: /* How it works */

{{#seo:|description=Mechanical relays can switch a power or signal line by physically moving metal contacts with an electromagnet. Learn more here.}}
{{#seo:|keywords=relay}}
[[Category:IntroGuide]]
<div class="toclimit-3">__TOC__</div>

==Introduction==
Mechanical relays are devices that can turn on or turn off the power supplied to another device, like a switch. However, instead of having a person flip the switch, mechanical relays switch when provided with a small amount of power. This allows high-power circuits to be controlled by low-power devices.

They perform the same function as [[Solid State Relay Guide|Solid State Relays]], except they are less expensive and have a shorter lifespan.
You can use them to control [[LED Guide|LEDs]], heaters, appliances, and generally any powered device as long as the power you're switching falls within the limits of the relay you're using.
[[File:1014_3.jpg|link=|center|400px]]

We sell boards with multiple relays on them (such as the [{{SERVER}}/?prodid=1228 PhidgetInterfaceKit 0/0/4], shown above), making it easy to control many separate circuits with your computer.

==How it works==
[[File:Mechanical_relay.jpg|thumb|link=|500px|<center>The switching arm and contacts of a mechanical relay.</center>]]
Mechanical relays use an electromagnetic coil to open or close the circuit. When current runs through the input and energizes the coil, it creates a small magnetic field which either pulls the arm of the switch away from the other contact of the switch, or pushes it down to close the switch depending on the how the switch is made. A relay also serves as an isolator, because the control (input) and load (output) ends of the relay are not electrically connected. This allows you to protect the device you're using to control the relay from power surges in your application.

===Basic Use===
Controlling a mechanical relay is as easy as turning on an LED or light bulb. By simply supplying enough power to energize the electromagnetic coil, you will be able to control a mechanical relay. A normal digital output will not be powerful enough without external components as described in the [[InterfaceKit Digital Outputs#Controlling a Relay with a N-Channel MOSFET| relay section of the Digital Output Guide]]. A Phidget with open collector digital outputs, (such as the [{{SERVER}}/?prodid=720 REL1100] or [{{SERVER}}/?prodid=721 REL1101]), on the other hand, will be able to control a relay on its own.
Relays are often used in large quantities to turn multiple devices on and off in a particular order or timing. For example, a popular trend has been to hook up many strands of Christmas lights to multiple relays and a control system in order to make them flash in rhythm with specific music.

Relays are designed to be controlled by a particular voltage applied to the coil. If you buy a relay product from us, this is taken care of for you. You will be able to switch the relays via USB with the Digital Outputs on a [[InterfaceKit Digital Outputs|Phidget InterfaceKit]] or {{VINTHub}}. If you are integrating your own relay, you'll want to keep an eye on the specifications. The relay coil is also specified for a particular current. For example, a 5V relay might require 70mA. If you connect this relay to a very weak source of 5V, like a digital output, the output will not be able to provide 70mA, and there will not be enough current to switch the relay.

The load side of the relay also requires a minimum current. This minimum load current (also called "wetting current") is a requirement because the electricity needs to conduct through an oxide layer that forms on the contacts of the relay. If the minimum load current requirement of your relay is too high, you won't be able to use it to switch a signal (such as the data line on an analog sensor), you'll only be able to switch power to a circuit. If you're using a relay to switch a signal, [[#Contact Bounce|contact bounce]] might also be a problem.

====Switching Speed and High-Frequency Switching====
Even though they use moving mechanical parts, mechanical relays switch very quickly. The amount of time it takes for current to begin flowing through the circuit from when the relay's input is activated is in the order of tens of milliseconds. For extremely time-sensitive applications that need to minimize switching delay, [[Solid State Relay Guide|Solid State Relays]] can switch as quickly as 1ms.

You should be careful when using mechanical relays in applications that require very frequent switching. Typically, mechanical relays can only manage one contact every few seconds- any quicker and they may begin to overheat.

===Safety===
[[File:relay_safety.jpg|thumb|450px|link=|Two circuit diagrams showing the improper and proper ways of switching mains electricity with a relay.<br />]]

Since relays switch high currents and voltages, standard electricity safety precautions apply. Make sure you never touch the terminals while the relay is powered.

When placing a relay in a circuit, it is always a good idea to put it between the power supply and the load, especially when using higher voltages. If the relay is instead placed between the load and ground, the circuit will still work the same, but when the relay is open, the load will still be directly connected to the power supply. This could cause safety concerns because someone might touch the terminals on the load, thinking it's safe because the device appears to be off. If the electricity finds a path to ground through their body, they will be electrocuted. If the relay is placed between the power supply and the ground, electrocution would only be a risk if the live terminal on the relay is touched. Again, the relay terminals should always be properly covered to avoid the risk of electrocution.

When an mechanical relay fails, it often fails permanently closed. This is because the contacts can actually weld to each other. See the section on [[#Arcing, Interference, and Sticking|Arcing, Interference, and Sticking]] for more information.
This means that as long as the power supply remains on, the load will be powered, possibly creating a fire or safety hazard.

<br clear=all>

==Choosing a Relay==
Since mechanical relays are nothing more than a controllable switch, they support both AC and DC loads.

The major deciding factor in choosing a mechanical relay is the amount of current it's capable of switching.
For example, the most current you can switch with the largest mechanical relay we sell is 5A DC or 10A AC.
If the load you're switching consumes more current than our mechanical relays can handle, take a look at our [[Solid State Relay Guide|Solid State Relays]].

===Switch Type===
One of the major characteristics of a mechanical relay is the design of the switch inside. A switch can generally be defined by the number of '''poles''' and '''throws''' it has. The number of "poles" refers to the number of individual circuits the switch controls. The number of "throws" refers to the number of positions the switch arm can occupy.

[[File:Switch_types.jpg|border|400px|link=|center]]

====Single Pole, Single Throw (SPST)====
This is a simple switch with only one path for the current to follow. The relay is either designed to be '''normally open (NO)''' or '''normally closed (NC)'''. If it is normally open, the arm of the switch is held away from the contact with a spring when the relay is off and the electromagnet pulls the arm to make contact and close the switch when the relay is turned on. If it is normally closed, the arm of the switch is held to the contact when the relay is off, and the electromagnet pulls the arm away when the relay is turned on.

While the decision to use a normally opened or normally closed relay may seem arbitrary at first, it is actually very important for certain applications. If you choose a normally closed relay, it means your load will remain powered as long as the relay coil is '''not''' powered. If some other part of your system fails, causing your relay to lose power, your load will remain powered even though it should not be. For loads that are potentially dangerous when left on (such as a heater, or a high-power load) it is best to use a normally open relay, so that in the event of a system failure, the load will remain off. On the other hand, circuits that are designed to be powered most of the time but temporarily interrupted will use less power if they use a normally closed relay. An example of this type of circuit is the radio in a car: When the engine is started, the radio circuit is momentarily switched off because the engine needs a large amount of battery power to start.

====Single Pole, Double Throw (SPDT)====
[[File:relay2loads.png|thumb|link=|300px|'''Toggle Between Two Loads'''<br />By connecting the power supply to the common terminal, and connecting a different load to the other two terminals, a relay with a SPDT switch can be used to toggle power between the two loads.<br />[[Media:relay2loads.png|Full-size Image]]]]

This switch has two paths for the current to follow. This type of relay is useful if you want to toggle power between two different loads, as pictured. You can also use a SPDT relay as a single pole, single throw switch, and it can function as '''normally open''' or '''normally closed''' depending on which pins (common and normally open, or common and normally closed) you connect the load to.

<br clear="all">

====Double Pole, Single Throw (DPST)====
This switch functions like two SPST switches, but both switches are controlled by one coil. This type of switch is useful for keeping two loads on separate circuits while still being able to have them turn on and off in unison.

====Double Pole, Double Throw (DPDT)====
This switch functions the same as a SPDT switch, except there are two of them, but are both controlled by a single input on the relay. You can use this type of switch to simultaneously control two separate circuits.

==Troubleshooting==
===Contact Bounce===
As with any mechanical switch, relays are susceptible to contact bounce. This means that when the switch closes, the arm can bounce on the contact, causing the load's power to flicker slightly. This usually only matters when the application is triggered by pulses in the power signal, or for applications where meaningful data is being switched instead of power. For example, a circuit designed to increment a counter every time power is applied to its input could incorrectly interpret a bouncing relay contact as multiple switch events. Or, a circuit that uses a relay to switch an audio signal between two different paths will experience some static noise when switching if there is significant contact bounce. It's worth mentioning that [[Solid State Relay Guide|Solid State Relays]] don't suffer from contact bounce, because they operate without using moving mechanical parts.

===Arcing, Interference, and Sticking===
[[File:contact_arc.jpg|border|link=|center]]
When a mechanical relay opens or closes, for the moment that the arm of the switch is very close (but not connected) to the contact, the electric current can arc through the air between the contacts.
This arc can cause interference with nearby electrical instruments and sensors. For example, if an unshielded cable carrying an audio signal is travelling past some relays whose contacts are arcing when they switch, the audio would contain bursts of static noise.

This arcing can also heat up the contacts of the switch enough that they can slowly degrade away until the relay no longer functions. They could also weld together, causing the relay to stay on permanently, which means your load will be powered constantly. If this imposes safety concerns, you should install a fail-safe of some kind. For example, some sauna heaters are turned on with a mechanical relay. In the event of a relay failure, the sauna heater will remain on and continue heating the room beyond the intended temperature. However, a simple mechanical temperature sensor is installed which cuts power to the heater if the room goes beyond a certain temperature.

Some relays are encased in a clear plastic enclosure (sometimes called "ice cube" relays), so the switch contacts can be easily inspected. By inspecting the contacts periodically, you could tell when the relay is getting near the end of its life.

===Prolonging Relay Lifespan===
In order to prolong the lifespan of your relay, avoid switching loads of higher voltage or current than the relay is built for, and avoid highly inductive loads, which worsen the effects of contact arcing. Your Load will probably be inductive if it is built around a large coil of wire - motors and transformers are typical examples. A load considered resistive may also have loops of wire - for instance, hair dryers, toasters, incandescent bulbs use twisted wire elements to generate the heat. An inductive load will have thousands of loops of wire - it's a matter of scale.

Additionally, you should avoid switching at or near the relay's maximum frequency if possible. You can think of a mechanical relay's lifespan in terms of number times switched rather than the amount of time it's used for. A relay that doesn't need to be switched very often can last a long time. If your application requires constant switching over long periods of time, it might be more cost-effective to use a [[Solid State Relay Guide|Solid State Relay]].

====Arc Suppression ====
[[File:Mechanical_relay_diode.jpg|link=|thumb|300px|'''DC Load Protection'''<br/>A diagram of a mechanical relay switching a DC load. An optional diode and fuse are used to protect the relay and prevent hardware damaged caused by improper wiring.<br/>[[Media:Mechanical_relay_diode.jpg|Full-sized Image]]]]
[[File:Mechanical_relay_mov.jpg|link=|thumb|300px|'''AC Load Protection'''<br/>A diagram of a mechanical relay switching an AC load. An optional MOV or Transil diode is placed in parallel to protect the relay from voltage spikes.<br/>[[Media:Mechanical_relay_mov.jpg|Full-Sized Image]]]]
The main cause of failure for mechanical relays is electricity arcing across the contacts during switching. To lengthen the lifespan of your relay, you can add various circuit elements that mitigate arcing.

For DC powered applications, one simple method of mitigating the effects of contact arcing is to place a feedback diode across the load, as pictured. This will allow some of the residual electricity in the circuit to recirculate through the load instead of contributing to the arc that forms when the switch makes the transition from closed to open. You can buy a suitable diode from any electronics distributor, like this [http://www.digikey.com/product-search/en/discrete-semiconductor-products/diodes-rectifiers-single/1376383?k=10a02 Diode] from Digikey.

For AC powered applications, you can put a Metal Oxide Varistor (MOV) across the load terminals of the relay in order to protect it from voltage spikes. An MOV will not remove the entire arc, but it will be helpful in circuits up to several hundred volts. You can buy an MOV from any electronics distributor, like this [http://www.digikey.com/scripts/dksearch/dksus.dll?keywords=tmov20rp200e MOV] from Digikey.

For low-voltage AC applications, a bi-directional transient voltage suppression diode ("transil diode") that is rated for higher than the AC voltage of the circuit can be placed across the relay terminals in order to protect it from voltage spikes. You can buy one from any electronics distributor, like this [http://www.digikey.com/scripts/dksearch/dksus.dll?keywords=p6ke47carl Transil Diode] from Digikey.

<br clear="all">

==Conclusion==

Mechanical relays are inexpensive and simple devices that allow AC or DC circuits to be switched on and off using a small amount of power.
They come in a variety of switch formats, enabling the user to build some very clever control into a circuit. Phidgets Inc. sells boards with multiple relays that can be connected directly to USB, or indirectly through a {{VINTHub}} so they can be controlled by your program.

Contact arcing and switch bounce can be an obstacle for some applications, but both are common problems and can be worked around fairly easily.
Mechanical relays don't last as long as solid state relays, but if you take care of them, they can be a good cost-effective alternative.

Mechanical Relay Guide

2025-11-13T22:24:10Z

Lmpacent: /* Introduction */

{{#seo:|description=Mechanical relays can switch a power or signal line by physically moving metal contacts with an electromagnet. Learn more here.}}
{{#seo:|keywords=relay}}
[[Category:IntroGuide]]
<div class="toclimit-3">__TOC__</div>

==Introduction==
Mechanical relays are devices that can turn on or turn off the power supplied to another device, like a switch. However, instead of having a person flip the switch, mechanical relays switch when provided with a small amount of power. This allows high-power circuits to be controlled by low-power devices.

They perform the same function as [[Solid State Relay Guide|Solid State Relays]], except they are less expensive and have a shorter lifespan.
You can use them to control [[LED Guide|LEDs]], heaters, appliances, and generally any powered device as long as the power you're switching falls within the limits of the relay you're using.
[[File:1014_3.jpg|link=|center|400px]]

We sell boards with multiple relays on them (such as the [{{SERVER}}/?prodid=1228 PhidgetInterfaceKit 0/0/4], shown above), making it easy to control many separate circuits with your computer.

==How it works==
[[File:Mechanical_relay.jpg|thumb|link=|500px|'''Mechanical Relay'''<br />The switching arm and contacts of a mechanical relay.]]
Mechanical relays use an electromagnetic coil to open or close the circuit. When current runs through the input and energizes the coil, it creates a small magnetic field which either pulls the arm of the switch away from the other contact of the switch, or pushes it down to close the switch depending on the how the switch is made. A relay also serves as an isolator, because the control (input) and load (output) ends of the relay are not electrically connected. This allows you to protect the device you're using to control the relay from power surges in your application.

===Basic Use===
Controlling a mechanical relay is as easy as turning on an LED or light bulb. By simply supplying enough power to energize the electromagnetic coil, you will be able to control a mechanical relay. A normal digital output will not be powerful enough without external components as described in the [[InterfaceKit Digital Outputs#Controlling a Relay with a N-Channel MOSFET| relay section of the Digital Output Guide]]. A Phidget with open collector digital outputs, (such as the [{{SERVER}}/?prodid=720 REL1100] or [{{SERVER}}/?prodid=721 REL1101]), on the other hand, will be able to control a relay on its own.
Relays are often used in large quantities to turn multiple devices on and off in a particular order or timing. For example, a popular trend has been to hook up many strands of Christmas lights to multiple relays and a control system in order to make them flash in rhythm with specific music.

Relays are designed to be controlled by a particular voltage applied to the coil. If you buy a relay product from us, this is taken care of for you. You will be able to switch the relays via USB with the Digital Outputs on a [[InterfaceKit Digital Outputs|Phidget InterfaceKit]] or {{VINTHub}}. If you are integrating your own relay, you'll want to keep an eye on the specifications. The relay coil is also specified for a particular current. For example, a 5V relay might require 70mA. If you connect this relay to a very weak source of 5V, like a digital output, the output will not be able to provide 70mA, and there will not be enough current to switch the relay.

The load side of the relay also requires a minimum current. This minimum load current (also called "wetting current") is a requirement because the electricity needs to conduct through an oxide layer that forms on the contacts of the relay. If the minimum load current requirement of your relay is too high, you won't be able to use it to switch a signal (such as the data line on an analog sensor), you'll only be able to switch power to a circuit. If you're using a relay to switch a signal, [[#Contact Bounce|contact bounce]] might also be a problem.

====Switching Speed and High-Frequency Switching====
Even though they use moving mechanical parts, mechanical relays switch very quickly. The amount of time it takes for current to begin flowing through the circuit from when the relay's input is activated is in the order of tens of milliseconds. For extremely time-sensitive applications that need to minimize switching delay, [[Solid State Relay Guide|Solid State Relays]] can switch as quickly as 1ms.

You should be careful when using mechanical relays in applications that require very frequent switching. Typically, mechanical relays can only manage one contact every few seconds- any quicker and they may begin to overheat.

===Safety===
[[File:relay_safety.jpg|thumb|450px|link=|Two circuit diagrams showing the improper and proper ways of switching mains electricity with a relay.<br />]]

Since relays switch high currents and voltages, standard electricity safety precautions apply. Make sure you never touch the terminals while the relay is powered.

When placing a relay in a circuit, it is always a good idea to put it between the power supply and the load, especially when using higher voltages. If the relay is instead placed between the load and ground, the circuit will still work the same, but when the relay is open, the load will still be directly connected to the power supply. This could cause safety concerns because someone might touch the terminals on the load, thinking it's safe because the device appears to be off. If the electricity finds a path to ground through their body, they will be electrocuted. If the relay is placed between the power supply and the ground, electrocution would only be a risk if the live terminal on the relay is touched. Again, the relay terminals should always be properly covered to avoid the risk of electrocution.

When an mechanical relay fails, it often fails permanently closed. This is because the contacts can actually weld to each other. See the section on [[#Arcing, Interference, and Sticking|Arcing, Interference, and Sticking]] for more information.
This means that as long as the power supply remains on, the load will be powered, possibly creating a fire or safety hazard.

<br clear=all>

==Choosing a Relay==
Since mechanical relays are nothing more than a controllable switch, they support both AC and DC loads.

The major deciding factor in choosing a mechanical relay is the amount of current it's capable of switching.
For example, the most current you can switch with the largest mechanical relay we sell is 5A DC or 10A AC.
If the load you're switching consumes more current than our mechanical relays can handle, take a look at our [[Solid State Relay Guide|Solid State Relays]].

===Switch Type===
One of the major characteristics of a mechanical relay is the design of the switch inside. A switch can generally be defined by the number of '''poles''' and '''throws''' it has. The number of "poles" refers to the number of individual circuits the switch controls. The number of "throws" refers to the number of positions the switch arm can occupy.

[[File:Switch_types.jpg|border|400px|link=|center]]

====Single Pole, Single Throw (SPST)====
This is a simple switch with only one path for the current to follow. The relay is either designed to be '''normally open (NO)''' or '''normally closed (NC)'''. If it is normally open, the arm of the switch is held away from the contact with a spring when the relay is off and the electromagnet pulls the arm to make contact and close the switch when the relay is turned on. If it is normally closed, the arm of the switch is held to the contact when the relay is off, and the electromagnet pulls the arm away when the relay is turned on.

While the decision to use a normally opened or normally closed relay may seem arbitrary at first, it is actually very important for certain applications. If you choose a normally closed relay, it means your load will remain powered as long as the relay coil is '''not''' powered. If some other part of your system fails, causing your relay to lose power, your load will remain powered even though it should not be. For loads that are potentially dangerous when left on (such as a heater, or a high-power load) it is best to use a normally open relay, so that in the event of a system failure, the load will remain off. On the other hand, circuits that are designed to be powered most of the time but temporarily interrupted will use less power if they use a normally closed relay. An example of this type of circuit is the radio in a car: When the engine is started, the radio circuit is momentarily switched off because the engine needs a large amount of battery power to start.

====Single Pole, Double Throw (SPDT)====
[[File:relay2loads.png|thumb|link=|300px|'''Toggle Between Two Loads'''<br />By connecting the power supply to the common terminal, and connecting a different load to the other two terminals, a relay with a SPDT switch can be used to toggle power between the two loads.<br />[[Media:relay2loads.png|Full-size Image]]]]

This switch has two paths for the current to follow. This type of relay is useful if you want to toggle power between two different loads, as pictured. You can also use a SPDT relay as a single pole, single throw switch, and it can function as '''normally open''' or '''normally closed''' depending on which pins (common and normally open, or common and normally closed) you connect the load to.

<br clear="all">

====Double Pole, Single Throw (DPST)====
This switch functions like two SPST switches, but both switches are controlled by one coil. This type of switch is useful for keeping two loads on separate circuits while still being able to have them turn on and off in unison.

====Double Pole, Double Throw (DPDT)====
This switch functions the same as a SPDT switch, except there are two of them, but are both controlled by a single input on the relay. You can use this type of switch to simultaneously control two separate circuits.

==Troubleshooting==
===Contact Bounce===
As with any mechanical switch, relays are susceptible to contact bounce. This means that when the switch closes, the arm can bounce on the contact, causing the load's power to flicker slightly. This usually only matters when the application is triggered by pulses in the power signal, or for applications where meaningful data is being switched instead of power. For example, a circuit designed to increment a counter every time power is applied to its input could incorrectly interpret a bouncing relay contact as multiple switch events. Or, a circuit that uses a relay to switch an audio signal between two different paths will experience some static noise when switching if there is significant contact bounce. It's worth mentioning that [[Solid State Relay Guide|Solid State Relays]] don't suffer from contact bounce, because they operate without using moving mechanical parts.

===Arcing, Interference, and Sticking===
[[File:contact_arc.jpg|border|link=|center]]
When a mechanical relay opens or closes, for the moment that the arm of the switch is very close (but not connected) to the contact, the electric current can arc through the air between the contacts.
This arc can cause interference with nearby electrical instruments and sensors. For example, if an unshielded cable carrying an audio signal is travelling past some relays whose contacts are arcing when they switch, the audio would contain bursts of static noise.

This arcing can also heat up the contacts of the switch enough that they can slowly degrade away until the relay no longer functions. They could also weld together, causing the relay to stay on permanently, which means your load will be powered constantly. If this imposes safety concerns, you should install a fail-safe of some kind. For example, some sauna heaters are turned on with a mechanical relay. In the event of a relay failure, the sauna heater will remain on and continue heating the room beyond the intended temperature. However, a simple mechanical temperature sensor is installed which cuts power to the heater if the room goes beyond a certain temperature.

Some relays are encased in a clear plastic enclosure (sometimes called "ice cube" relays), so the switch contacts can be easily inspected. By inspecting the contacts periodically, you could tell when the relay is getting near the end of its life.

===Prolonging Relay Lifespan===
In order to prolong the lifespan of your relay, avoid switching loads of higher voltage or current than the relay is built for, and avoid highly inductive loads, which worsen the effects of contact arcing. Your Load will probably be inductive if it is built around a large coil of wire - motors and transformers are typical examples. A load considered resistive may also have loops of wire - for instance, hair dryers, toasters, incandescent bulbs use twisted wire elements to generate the heat. An inductive load will have thousands of loops of wire - it's a matter of scale.

Additionally, you should avoid switching at or near the relay's maximum frequency if possible. You can think of a mechanical relay's lifespan in terms of number times switched rather than the amount of time it's used for. A relay that doesn't need to be switched very often can last a long time. If your application requires constant switching over long periods of time, it might be more cost-effective to use a [[Solid State Relay Guide|Solid State Relay]].

====Arc Suppression ====
[[File:Mechanical_relay_diode.jpg|link=|thumb|300px|'''DC Load Protection'''<br/>A diagram of a mechanical relay switching a DC load. An optional diode and fuse are used to protect the relay and prevent hardware damaged caused by improper wiring.<br/>[[Media:Mechanical_relay_diode.jpg|Full-sized Image]]]]
[[File:Mechanical_relay_mov.jpg|link=|thumb|300px|'''AC Load Protection'''<br/>A diagram of a mechanical relay switching an AC load. An optional MOV or Transil diode is placed in parallel to protect the relay from voltage spikes.<br/>[[Media:Mechanical_relay_mov.jpg|Full-Sized Image]]]]
The main cause of failure for mechanical relays is electricity arcing across the contacts during switching. To lengthen the lifespan of your relay, you can add various circuit elements that mitigate arcing.

For DC powered applications, one simple method of mitigating the effects of contact arcing is to place a feedback diode across the load, as pictured. This will allow some of the residual electricity in the circuit to recirculate through the load instead of contributing to the arc that forms when the switch makes the transition from closed to open. You can buy a suitable diode from any electronics distributor, like this [http://www.digikey.com/product-search/en/discrete-semiconductor-products/diodes-rectifiers-single/1376383?k=10a02 Diode] from Digikey.

For AC powered applications, you can put a Metal Oxide Varistor (MOV) across the load terminals of the relay in order to protect it from voltage spikes. An MOV will not remove the entire arc, but it will be helpful in circuits up to several hundred volts. You can buy an MOV from any electronics distributor, like this [http://www.digikey.com/scripts/dksearch/dksus.dll?keywords=tmov20rp200e MOV] from Digikey.

For low-voltage AC applications, a bi-directional transient voltage suppression diode ("transil diode") that is rated for higher than the AC voltage of the circuit can be placed across the relay terminals in order to protect it from voltage spikes. You can buy one from any electronics distributor, like this [http://www.digikey.com/scripts/dksearch/dksus.dll?keywords=p6ke47carl Transil Diode] from Digikey.

<br clear="all">

==Conclusion==

Mechanical relays are inexpensive and simple devices that allow AC or DC circuits to be switched on and off using a small amount of power.
They come in a variety of switch formats, enabling the user to build some very clever control into a circuit. Phidgets Inc. sells boards with multiple relays that can be connected directly to USB, or indirectly through a {{VINTHub}} so they can be controlled by your program.

Contact arcing and switch bounce can be an obstacle for some applications, but both are common problems and can be worked around fairly easily.
Mechanical relays don't last as long as solid state relays, but if you take care of them, they can be a good cost-effective alternative.

File:1014 3.jpg

2025-11-13T22:22:49Z

Lmpacent:

Phidget Network Server

2025-08-01T19:48:28Z

Lmpacent: /* Phidget Network Server Hosts */

[[Category:Programming]]{{Recommended_Flow_Links|{{Flow Page Number|{{PAGENAME}} }} }}
__NOTOC__
==What Is the Phidget Network Server?==
The Phidget Network Server is a tool that makes it easy to access Phidgets that are connected to '''other computers''' on your network.

It also enables in-browser JavaScript applications with Phidgets, and provides a dictionary manager which can be used to share information between applications.

===Without the Phidget Network Server===
Your application runs on the same computer that your Phidgets are connected to.
[[Image:Networkserver_ex1v2.png|500px|center|link=]]

===With the Phidget Network Server===
Your Phidgets are connected to a computer running the Phidget Network Server. The Phidget Network Server hosts a Phidget Server, which makes your Phidgets available to other computers on your network.
* Your application(s) can run on any computer that has access to the network the host is on.
* Multiple applications can access the Phidgets simultaneously, with some exceptions (e.g. motor controllers).

[[Image:Networkserver_ex2v3.png|600px|center|link=]]

==Phidget Network Server Hosts==
As mentioned above, a computer is required to host the Phidget Network Server. Any Windows, macOS, or Linux machine can act as a host. The Wireless VINT Hub or the PhidgetSBC4 are also excellent, compact choices.
[[Image:HUB5000_0.jpg|200px|thumb|link=]]
===Wireless VINT Hub===
The Wireless VINT Hub (HUB5000) has the Phidget Network Server built-in. Simply connect your Phidgets, power the device, and the Network Server starts automatically.

This device supports both Ethernet and WiFi connections and provides a simple web interface to configure your Phidget Network Server. Check out the [{{SERVER}}/?prodid=1143 product page] for more information.

[[Image:SBC3003_0.jpg|link=|thumb|300px]]

===PhidgetSBC4===
The PhidgetSBC4 (SBC3003) has the Phidget Network Server built-in. Simply connect your Phidgets, power the device, and the Network Server starts automatically.

This device supports both Ethernet and WiFi connections and provides a simple web interface to configure your Phidget Network Server. Additionally, you can connect USB Phidgets directly to this device and run application code on board. Check out the [{{SERVER}}/?prodid=969 product page] for more information.

==Phidget Network Server Clients==
Client applications can run on any [[Operating_System_Support|supported operating system]] and can be written in any [[Programming_Resources|supported programming language]]. The client machine does '''not''' need to run a Phidget Network Server.

==Learn More==
View our [[Network Server Guide|Phidget Network Server Guide]] for more in-depth information.

{{Flow_Navigation_Buttons|{{Flow Page Number|{{PAGENAME}} }} }}

Product Lifecycle

2025-07-31T19:46:48Z

Lmpacent: /* Lifecycle Stages */

{{#seo:|description=Products designed by Phidgets Inc. often have a life span of decades. Learn about our product lifecycle here.}}
__TOC__
[[Category:IntroGuide]]
[[Image:Lifecycle_1014_example.png|400px|link=https://cdn.phidgets.com/docs/images/7/77/Lifecycle_1014_example.png|thumb|<center>The [https://phidgets.com/?prodid=9 PhidgetInterfaceKit 0/0/4 (ID: 1014_0)] was first released over 20 years ago.</center>]]
==Introduction==
Products designed and manufactured by Phidgets Inc. often have a life span of '''decades'''.

Many of our customers integrate our products into their own systems and devices, and they depend on us to continue manufacturing a particular SKU, or a drop-in replacement, for many years.

In this guide, we will provide information about the systems in place at Phidgets Inc. surrounding product lifecycle.
==Lifecycle Example - PhidgetInterfaceKit 0/0/4 ==
As referenced in the image above, the PhidgetInterfaceKit 0/0/4 (ID:1014_0) was first released in 2002, and new revisions are still available today.
[[Image:Lifecycle_1014_functional.jpg|600px|link=https://cdn.phidgets.com/docs/images/7/7c/Lifecycle_1014_functional.jpg|center]]
<center>''The 1014_0 circa 2002''</center>

By examining the [[#Product History|product history]] of this device, we can gain detailed insights into how Phidgets Inc. manages the lifecycle of all products, and how customers are supported and protected along the way.

===Product History===
[[Image:Lifecycle_1014_producthistory.png|400px|link=https://cdn.phidgets.com/docs/images/1/17/Lifecycle_1014_producthistory.png|thumb|<center>1014 Product History ([https://cdn.phidgets.com/docs/images/1/17/Lifecycle_1014_producthistory.png click to expand])</center>]]
By clicking on the ''Specifications'' tab of the latest revision ([https://www.phidgets.com/?prodid=1228#Tab_Specifications ID: 1014_3]), and scrolling down to ''Product History'', we can view the full history of this product.

There have been three revisions to the original board:
* '''1014_1''': Larger terminal blocks were introduced in 2008 which increased the PCB size resulting in a [[#Breaking Changes|breaking change]].
* '''1014_2''': The B-Type connector was changed to a mini-USB connector in 2010 resulting in a [[#Breaking Changes|breaking change]].
* '''1014_3''': A VINT connector was added and support for Phidget21 was dropped in 2023 resulting in a [[#Breaking Changes|breaking change]].

====Breaking Changes====
When a board has changed in a meaningful way, a ''breaking'' change has been made. Here are some examples of breaking changes:
* The shape, size, and/or mounting holes have changed
* Software support has changed (e.g. Phidget21 is no longer supported)
* Major specifications or performance of the product has changed
* Major features or functionality have been modified or removed

When a breaking change is made on a new revision of a product, we protect our customers in the following ways:
* Mark the older revision as [[#Not Recommended for New Design|Not Recommended for New Design (NRND)]] on our website
* Notify any high-volume customers
* Notify any customers who explicitly signed up for [[#Product Notifications|product notifications]]
* Begin protecting the stock of the older revision. Eventually, this revision of the product will be discontinued on our website, and will only be available through purchase orders

This means that even if a breaking change is introduced, existing customers will be taken care of, oftentimes for years, until they can transition to a newer revision.

===Result===
As we can see from the information above, the 1014 has been incredibly stable for over 20 years. This is common for all hardware designed and manufactured by Phidgets Inc.

==Lifecycle Stages==
[[File:NRND_badge_ex3.png | link=https://cdn.phidgets.com/docs/images/a/a9/NRND_badge_ex3.png|thumb|<center>Not recommended for new design (NRND) product labelling.</center>]]
When you are designing a new system that will use products from Phidgets Inc., it is important to understand the lifecycle of our products.
===Products Designed by Phidgets Inc.===
There are two general categories for products designed by Phidgets Inc.:
* Not recommended for new design (NRND)
* All other products

====Not Recommended for New Design (NRND)====
Products labeled ''NRND'' are no longer being actively developed and should be avoided for new designs intended for long-term use, such as OEM applications or multi-year systems.

For existing designs that include a Phidget that has transitioned to NRND, we recommend the following:
* Sign up for [[#Product Notifications|product notifications]] if you haven't already
* [https://www.phidgets.com/?view=contact Contact us] to receive specific information and recommendations about your product

Generally, we aim to continue producing NRND products for as long as possible, though this is dependent on component availability and customer demand.

====All Other Products====
If a product is not labeled ''NRND'', we expect to keep the product in stock or offer a drop-in replacement for 5 to 10 years.

If you are planning a new high-volume design, please [https://www.phidgets.com/?view=contact contact us] to discuss a particular product's roadmap.

===Products From Other Suppliers===
We cannot provide a guarantee or roadmap on products from other suppliers (e.g. load cells, mechanical parts, RFID tags, etc.). We always aim to keep these products in stock, however, if a product is discontinued, [https://www.phidgets.com/?view=contact contact us] and we will help you find alternate sourcing.

[[File:Lifecycle_notifications2.png|thumb|link=https://cdn.phidgets.com/docs/images/d/d0/Lifecycle_notifications.png|<center>Sign up for notifications using the button on a product page</center>|450px]]

==Product Notifications==
We strongly recommend that you subscribe to our product notifications. By doing this, you will receive important information about your chosen product, including:
* Firmware upgrades
* Product revisions and NRND transitions
* Stock alerts

To subscribe, navigate to the product page of your chosen product. Find and click on the ''Sign Up for Notifications'' button and follow the prompts.

File:NRND badge ex3.png

2025-07-31T19:46:29Z

Lmpacent:

Product Lifecycle

2025-07-31T19:42:51Z

Lmpacent: /* Lifecycle Stages */

{{#seo:|description=Products designed by Phidgets Inc. often have a life span of decades. Learn about our product lifecycle here.}}
__TOC__
[[Category:IntroGuide]]
[[Image:Lifecycle_1014_example.png|400px|link=https://cdn.phidgets.com/docs/images/7/77/Lifecycle_1014_example.png|thumb|<center>The [https://phidgets.com/?prodid=9 PhidgetInterfaceKit 0/0/4 (ID: 1014_0)] was first released over 20 years ago.</center>]]
==Introduction==
Products designed and manufactured by Phidgets Inc. often have a life span of '''decades'''.

Many of our customers integrate our products into their own systems and devices, and they depend on us to continue manufacturing a particular SKU, or a drop-in replacement, for many years.

In this guide, we will provide information about the systems in place at Phidgets Inc. surrounding product lifecycle.
==Lifecycle Example - PhidgetInterfaceKit 0/0/4 ==
As referenced in the image above, the PhidgetInterfaceKit 0/0/4 (ID:1014_0) was first released in 2002, and new revisions are still available today.
[[Image:Lifecycle_1014_functional.jpg|600px|link=https://cdn.phidgets.com/docs/images/7/7c/Lifecycle_1014_functional.jpg|center]]
<center>''The 1014_0 circa 2002''</center>

By examining the [[#Product History|product history]] of this device, we can gain detailed insights into how Phidgets Inc. manages the lifecycle of all products, and how customers are supported and protected along the way.

===Product History===
[[Image:Lifecycle_1014_producthistory.png|400px|link=https://cdn.phidgets.com/docs/images/1/17/Lifecycle_1014_producthistory.png|thumb|<center>1014 Product History ([https://cdn.phidgets.com/docs/images/1/17/Lifecycle_1014_producthistory.png click to expand])</center>]]
By clicking on the ''Specifications'' tab of the latest revision ([https://www.phidgets.com/?prodid=1228#Tab_Specifications ID: 1014_3]), and scrolling down to ''Product History'', we can view the full history of this product.

There have been three revisions to the original board:
* '''1014_1''': Larger terminal blocks were introduced in 2008 which increased the PCB size resulting in a [[#Breaking Changes|breaking change]].
* '''1014_2''': The B-Type connector was changed to a mini-USB connector in 2010 resulting in a [[#Breaking Changes|breaking change]].
* '''1014_3''': A VINT connector was added and support for Phidget21 was dropped in 2023 resulting in a [[#Breaking Changes|breaking change]].

====Breaking Changes====
When a board has changed in a meaningful way, a ''breaking'' change has been made. Here are some examples of breaking changes:
* The shape, size, and/or mounting holes have changed
* Software support has changed (e.g. Phidget21 is no longer supported)
* Major specifications or performance of the product has changed
* Major features or functionality have been modified or removed

When a breaking change is made on a new revision of a product, we protect our customers in the following ways:
* Mark the older revision as [[#Not Recommended for New Design|Not Recommended for New Design (NRND)]] on our website
* Notify any high-volume customers
* Notify any customers who explicitly signed up for [[#Product Notifications|product notifications]]
* Begin protecting the stock of the older revision. Eventually, this revision of the product will be discontinued on our website, and will only be available through purchase orders

This means that even if a breaking change is introduced, existing customers will be taken care of, oftentimes for years, until they can transition to a newer revision.

===Result===
As we can see from the information above, the 1014 has been incredibly stable for over 20 years. This is common for all hardware designed and manufactured by Phidgets Inc.

==Lifecycle Stages==
[[File:NRND_badge_ex2.jpg|link=https://cdn.phidgets.com/docs/images/f/f0/NRND_badge_ex2.jpg|thumb|<center>Not recommended for new design (NRND) product labelling.</center>]]
When you are designing a new system that will use products from Phidgets Inc., it is important to understand the lifecycle of our products.
===Products Designed by Phidgets Inc.===
There are two general categories for products designed by Phidgets Inc.:
* Not recommended for new design (NRND)
* All other products

====Not Recommended for New Design (NRND)====
Products labeled ''NRND'' are no longer being actively developed and should be avoided for new designs intended for long-term use, such as OEM applications or multi-year systems.

For existing designs that include a Phidget that has transitioned to NRND, we recommend the following:
* Sign up for [[#Product Notifications|product notifications]] if you haven't already
* [https://www.phidgets.com/?view=contact Contact us] to receive specific information and recommendations about your product

Generally, we aim to continue producing NRND products for as long as possible, though this is dependent on component availability and customer demand.

====All Other Products====
If a product is not labeled ''NRND'', we expect to keep the product in stock or offer a drop-in replacement for 5 to 10 years.

If you are planning a new high-volume design, please [https://www.phidgets.com/?view=contact contact us] to discuss a particular product's roadmap.

===Products From Other Suppliers===
We cannot provide a guarantee or roadmap on products from other suppliers (e.g. load cells, mechanical parts, RFID tags, etc.). We always aim to keep these products in stock, however, if a product is discontinued, [https://www.phidgets.com/?view=contact contact us] and we will help you find alternate sourcing.

[[File:Lifecycle_notifications2.png|thumb|link=https://cdn.phidgets.com/docs/images/d/d0/Lifecycle_notifications.png|<center>Sign up for notifications using the button on a product page</center>|450px]]

==Product Notifications==
We strongly recommend that you subscribe to our product notifications. By doing this, you will receive important information about your chosen product, including:
* Firmware upgrades
* Product revisions and NRND transitions
* Stock alerts

To subscribe, navigate to the product page of your chosen product. Find and click on the ''Sign Up for Notifications'' button and follow the prompts.

File:NRND badge ex2.jpg

2025-07-31T19:41:53Z

Lmpacent:

Product Lifecycle

2025-07-31T19:40:13Z

Lmpacent: /* Not Recommended for New Design (NRND) */

{{#seo:|description=Products designed by Phidgets Inc. often have a life span of decades. Learn about our product lifecycle here.}}
__TOC__
[[Category:IntroGuide]]
[[Image:Lifecycle_1014_example.png|400px|link=https://cdn.phidgets.com/docs/images/7/77/Lifecycle_1014_example.png|thumb|<center>The [https://phidgets.com/?prodid=9 PhidgetInterfaceKit 0/0/4 (ID: 1014_0)] was first released over 20 years ago.</center>]]
==Introduction==
Products designed and manufactured by Phidgets Inc. often have a life span of '''decades'''.

Many of our customers integrate our products into their own systems and devices, and they depend on us to continue manufacturing a particular SKU, or a drop-in replacement, for many years.

In this guide, we will provide information about the systems in place at Phidgets Inc. surrounding product lifecycle.
==Lifecycle Example - PhidgetInterfaceKit 0/0/4 ==
As referenced in the image above, the PhidgetInterfaceKit 0/0/4 (ID:1014_0) was first released in 2002, and new revisions are still available today.
[[Image:Lifecycle_1014_functional.jpg|600px|link=https://cdn.phidgets.com/docs/images/7/7c/Lifecycle_1014_functional.jpg|center]]
<center>''The 1014_0 circa 2002''</center>

By examining the [[#Product History|product history]] of this device, we can gain detailed insights into how Phidgets Inc. manages the lifecycle of all products, and how customers are supported and protected along the way.

===Product History===
[[Image:Lifecycle_1014_producthistory.png|400px|link=https://cdn.phidgets.com/docs/images/1/17/Lifecycle_1014_producthistory.png|thumb|<center>1014 Product History ([https://cdn.phidgets.com/docs/images/1/17/Lifecycle_1014_producthistory.png click to expand])</center>]]
By clicking on the ''Specifications'' tab of the latest revision ([https://www.phidgets.com/?prodid=1228#Tab_Specifications ID: 1014_3]), and scrolling down to ''Product History'', we can view the full history of this product.

There have been three revisions to the original board:
* '''1014_1''': Larger terminal blocks were introduced in 2008 which increased the PCB size resulting in a [[#Breaking Changes|breaking change]].
* '''1014_2''': The B-Type connector was changed to a mini-USB connector in 2010 resulting in a [[#Breaking Changes|breaking change]].
* '''1014_3''': A VINT connector was added and support for Phidget21 was dropped in 2023 resulting in a [[#Breaking Changes|breaking change]].

====Breaking Changes====
When a board has changed in a meaningful way, a ''breaking'' change has been made. Here are some examples of breaking changes:
* The shape, size, and/or mounting holes have changed
* Software support has changed (e.g. Phidget21 is no longer supported)
* Major specifications or performance of the product has changed
* Major features or functionality have been modified or removed

When a breaking change is made on a new revision of a product, we protect our customers in the following ways:
* Mark the older revision as [[#Not Recommended for New Design|Not Recommended for New Design (NRND)]] on our website
* Notify any high-volume customers
* Notify any customers who explicitly signed up for [[#Product Notifications|product notifications]]
* Begin protecting the stock of the older revision. Eventually, this revision of the product will be discontinued on our website, and will only be available through purchase orders

This means that even if a breaking change is introduced, existing customers will be taken care of, oftentimes for years, until they can transition to a newer revision.

===Result===
As we can see from the information above, the 1014 has been incredibly stable for over 20 years. This is common for all hardware designed and manufactured by Phidgets Inc.

==Lifecycle Stages==
[[File:NRND_badge_ex.png|link=https://cdn.phidgets.com/docs/images/a/ad/NRND_badge_ex.png|thumb|<center>Not recommended for new design (NRND) product labelling.</center>]]
When you are designing a new system that will use products from Phidgets Inc., it is important to understand the lifecycle of our products.
===Products Designed by Phidgets Inc.===
There are two general categories for products designed by Phidgets Inc.:
* Not recommended for new design (NRND)
* All other products

====Not Recommended for New Design (NRND)====
Products labeled ''NRND'' are no longer being actively developed and should be avoided for new designs intended for long-term use, such as OEM applications or multi-year systems.

For existing designs that include a Phidget that has transitioned to NRND, we recommend the following:
* Sign up for [[#Product Notifications|product notifications]] if you haven't already
* [https://www.phidgets.com/?view=contact Contact us] to receive specific information and recommendations about your product

Generally, we aim to continue producing NRND products for as long as possible, though this is dependent on component availability and customer demand.

====All Other Products====
If a product is not labeled ''NRND'', we expect to keep the product in stock or offer a drop-in replacement for 5 to 10 years.

If you are planning a new high-volume design, please [https://www.phidgets.com/?view=contact contact us] to discuss a particular product's roadmap.

===Products From Other Suppliers===
We cannot provide a guarantee or roadmap on products from other suppliers (e.g. load cells, mechanical parts, RFID tags, etc.). We always aim to keep these products in stock, however, if a product is discontinued, [https://www.phidgets.com/?view=contact contact us] and we will help you find alternate sourcing.

[[File:Lifecycle_notifications2.png|thumb|link=https://cdn.phidgets.com/docs/images/d/d0/Lifecycle_notifications.png|<center>Sign up for notifications using the button on a product page</center>|450px]]

==Product Notifications==
We strongly recommend that you subscribe to our product notifications. By doing this, you will receive important information about your chosen product, including:
* Firmware upgrades
* Product revisions and NRND transitions
* Stock alerts

To subscribe, navigate to the product page of your chosen product. Find and click on the ''Sign Up for Notifications'' button and follow the prompts.

Product Lifecycle

2025-07-31T19:38:40Z

Lmpacent: /* All Other Products */

{{#seo:|description=Products designed by Phidgets Inc. often have a life span of decades. Learn about our product lifecycle here.}}
__TOC__
[[Category:IntroGuide]]
[[Image:Lifecycle_1014_example.png|400px|link=https://cdn.phidgets.com/docs/images/7/77/Lifecycle_1014_example.png|thumb|<center>The [https://phidgets.com/?prodid=9 PhidgetInterfaceKit 0/0/4 (ID: 1014_0)] was first released over 20 years ago.</center>]]
==Introduction==
Products designed and manufactured by Phidgets Inc. often have a life span of '''decades'''.

Many of our customers integrate our products into their own systems and devices, and they depend on us to continue manufacturing a particular SKU, or a drop-in replacement, for many years.

In this guide, we will provide information about the systems in place at Phidgets Inc. surrounding product lifecycle.
==Lifecycle Example - PhidgetInterfaceKit 0/0/4 ==
As referenced in the image above, the PhidgetInterfaceKit 0/0/4 (ID:1014_0) was first released in 2002, and new revisions are still available today.
[[Image:Lifecycle_1014_functional.jpg|600px|link=https://cdn.phidgets.com/docs/images/7/7c/Lifecycle_1014_functional.jpg|center]]
<center>''The 1014_0 circa 2002''</center>

By examining the [[#Product History|product history]] of this device, we can gain detailed insights into how Phidgets Inc. manages the lifecycle of all products, and how customers are supported and protected along the way.

===Product History===
[[Image:Lifecycle_1014_producthistory.png|400px|link=https://cdn.phidgets.com/docs/images/1/17/Lifecycle_1014_producthistory.png|thumb|<center>1014 Product History ([https://cdn.phidgets.com/docs/images/1/17/Lifecycle_1014_producthistory.png click to expand])</center>]]
By clicking on the ''Specifications'' tab of the latest revision ([https://www.phidgets.com/?prodid=1228#Tab_Specifications ID: 1014_3]), and scrolling down to ''Product History'', we can view the full history of this product.

There have been three revisions to the original board:
* '''1014_1''': Larger terminal blocks were introduced in 2008 which increased the PCB size resulting in a [[#Breaking Changes|breaking change]].
* '''1014_2''': The B-Type connector was changed to a mini-USB connector in 2010 resulting in a [[#Breaking Changes|breaking change]].
* '''1014_3''': A VINT connector was added and support for Phidget21 was dropped in 2023 resulting in a [[#Breaking Changes|breaking change]].

====Breaking Changes====
When a board has changed in a meaningful way, a ''breaking'' change has been made. Here are some examples of breaking changes:
* The shape, size, and/or mounting holes have changed
* Software support has changed (e.g. Phidget21 is no longer supported)
* Major specifications or performance of the product has changed
* Major features or functionality have been modified or removed

When a breaking change is made on a new revision of a product, we protect our customers in the following ways:
* Mark the older revision as [[#Not Recommended for New Design|Not Recommended for New Design (NRND)]] on our website
* Notify any high-volume customers
* Notify any customers who explicitly signed up for [[#Product Notifications|product notifications]]
* Begin protecting the stock of the older revision. Eventually, this revision of the product will be discontinued on our website, and will only be available through purchase orders

This means that even if a breaking change is introduced, existing customers will be taken care of, oftentimes for years, until they can transition to a newer revision.

===Result===
As we can see from the information above, the 1014 has been incredibly stable for over 20 years. This is common for all hardware designed and manufactured by Phidgets Inc.

==Lifecycle Stages==
[[File:NRND_badge_ex.png|link=https://cdn.phidgets.com/docs/images/a/ad/NRND_badge_ex.png|thumb|<center>Not recommended for new design (NRND) product labelling.</center>]]
When you are designing a new system that will use products from Phidgets Inc., it is important to understand the lifecycle of our products.
===Products Designed by Phidgets Inc.===
There are two general categories for products designed by Phidgets Inc.:
* Not recommended for new design (NRND)
* All other products

====Not Recommended for New Design (NRND)====
Products labeled ''NRND'' are no longer being actively developed and should be avoided for new designs.

For existing designs that include a Phidget that has transitioned to NRND, we recommend the following:
* Sign up for [[#Product Notifications|product notifications]] if you haven't already
* [https://www.phidgets.com/?view=contact Contact us] to receive specific information and recommendations about your product

Generally, we aim to continue producing NRND products for as long as possible, though this is dependent on component availability and customer demand.

====All Other Products====
If a product is not labeled ''NRND'', we expect to keep the product in stock or offer a drop-in replacement for 5 to 10 years.

If you are planning a new high-volume design, please [https://www.phidgets.com/?view=contact contact us] to discuss a particular product's roadmap.

===Products From Other Suppliers===
We cannot provide a guarantee or roadmap on products from other suppliers (e.g. load cells, mechanical parts, RFID tags, etc.). We always aim to keep these products in stock, however, if a product is discontinued, [https://www.phidgets.com/?view=contact contact us] and we will help you find alternate sourcing.

[[File:Lifecycle_notifications2.png|thumb|link=https://cdn.phidgets.com/docs/images/d/d0/Lifecycle_notifications.png|<center>Sign up for notifications using the button on a product page</center>|450px]]

==Product Notifications==
We strongly recommend that you subscribe to our product notifications. By doing this, you will receive important information about your chosen product, including:
* Firmware upgrades
* Product revisions and NRND transitions
* Stock alerts

To subscribe, navigate to the product page of your chosen product. Find and click on the ''Sign Up for Notifications'' button and follow the prompts.

Template:DCMotor RescaleFactor

2025-06-23T22:35:48Z

Lmpacent:

{| class="wikitable"
! Controller Type !! Related Video
|-
| DC Motor|| {{#ev:youtube|i_KKu2eQcRw|rel=0}}
|-
| Brushless DC Motor|| {{#ev:youtube|i_KKu2eQcRw|rel=0}}
|-
|}
{{#switch: {{{1}}}
| position = The Rescale Factor allows you to change the units of the following properties:
* Target Position, Position, Expected Position, Deadband
* VelocityLimit, Acceleration
| velocity = The Rescale Factor allows you to change the units of the following properties:
* Target Velocity, Velocity, Expected Velocity, Deadband
* Acceleration
| #default = Unexpected error.
}}

By default, the units will be in encoder pulses which is dictated by your encoder and are often non-intuitive. We recommend utilizing the Rescale Factor so your software is easier to understand.

Template:DCMotor RescaleFactor

2025-06-23T22:32:41Z

Lmpacent:

{| class="wikitable"
! Controller Type !! Related Video
|-
| DC Motor|| {{#ev:youtube|i_KKu2eQcRw|rel=0}}
|-
| BLDC Motor|| {{#ev:youtube|i_KKu2eQcRw|rel=0}}
|-
|}
{{#switch: {{{1}}}
| position = The Rescale Factor allows you to change the units of the following properties:
* Target Position, Position, Expected Position, Deadband
* VelocityLimit, Acceleration
| velocity = The Rescale Factor allows you to change the units of the following properties:
* Target Velocity, Velocity, Expected Velocity, Deadband
* Acceleration
| #default = Unexpected error.
}}

By default, the units will be in encoder pulses which is dictated by your encoder and are often non-intuitive. We recommend utilizing the Rescale Factor so your software is easier to understand.

BLDCMotor API Guide

2025-06-23T22:30:36Z

Lmpacent: /* Rescale Factor */

{{#seo:|description=Get started with your Brushless DC Motor Phidget}}
[[Category:IntroGuide]]
<div class="nonumtoc">
<div class="toclimit-4">
=Introduction=
[[Image:DCC1120_0.png|thumb|link=https://cdn.phidgets.com/docs/images/3/38/DCC1120_0.png|<center>30V 50A Brushless DC Motor Phidget (DCC1120_0)</center>]]
This guide will provide information about the Brushless DC Motor (BLDC) API to get you up and running with your new BLDC Motor Phidget.

Before starting this guide, visit the Quick Start Guide on your BLDC Motor Phidget's product page for information about wiring and power.

==Guide Compatibility==
<tabber>
Info=
''Select your controller for compatibility information relating to this guide.''
|-|
DCC1120=
[[Image:DCC1120_0.png|link=https://cdn.phidgets.com/docs/images/3/38/DCC1120_0.png|thumb|200px|[{{SERVER}}/?prodid=1334 30V 50A Brushless DC Motor Phidget (DCC1120_0)]]]
The [{{SERVER}}/?prodid=1334 30V 50A Brushless DC Motor Phidget (DCC1120_0)] is fully compatible with this guide.
|-|
DCC1100=
[[Image:DCC1100_0.jpg|link=https://cdn.phidgets.com/docs/images/8/87/DCC1100_0.jpg|thumb|200px|[https://www.phidgets.com/?prodid=1013 Brushless DC Motor Phidget (DCC1100_0)]]]
[https://www.phidgets.com/?prodid=1013 Brushless DC Motor Phidget (DCC1100_0)] considerations:
* Stall Velocity is not covered in this guide. Information on this topic is available in the device API.
|-|
</tabber>

=BLDCMotor API Overview=
==Phidget Control Panel==
After wiring your BLDC Motor Phidget, we recommend opening the [https://www.phidgets.com/docs/Phidget_Control_Panel Phidget Control Panel] on a Windows computer to experiment with key features.

[[Image:DCC1120_0_Panel.png|center|link=]]

When the BLDC Motor Phidget is powered, it will appear up on the Phidget Control Panel device list as shown above. Double-click on the ''BLDC Motor Controller'' entry to view the program.

[[Image:DCC1120_0_BLDC.png|800px|center|link=]]

After opening the program, you will see the screen shown above. The program is split into multiple sections to help you get familiar with your motor controller.
#Phidget Info
#Motor Status
#Controls
#Configuration

In this guide, we will focus on the areas that contain important information about controlling your Brushless DC motor. For information about the Phidget Info section, and the Phidget Control Panel in general, visit our [https://www.phidgets.com/docs/Phidget_Control_Panel Phidget Control Panel] Page.

==Controls==
{{DCBLDCMotor_Controls}}

==Configuration==
This area of the program allows you to try out different configurations with your BLDC Motor Phidget to determine the best fit for your application.

===Drive Mode===
{{DCBLDCMotor_DriveMode|bldc}}

===Rescale Factor===
<center>{{#ev:youtube|SbO3hAuYsAE|rel=0}}</center>

The Rescale Factor allows you to change the units of the following properties:
* [[#Position|Position]]

By default, the units will be in commutations which is dictated by the number of poles/phases your motor and are often non-intuitive. We recommend utilizing the Rescale Factor so your software is easier to understand.

====Example Calculations====
Generally, most users will prefer units of degrees or rotations. To determine an appropriate Rescale Factor, you will need to know the following values:
*Commutations per revolution, equivalent to the number of poles multiplied by the number of phases
*Gearbox ratio (if applicable)

These values will be available from manufacturer data sheets, or directly on the motor.

=====Converting to Degrees=====
Specifications of system:
* Motor gear ratio: 10:1
* Motor poles: 2
* Motor phases: 3

Rescale Factor = 360 / (10<nowiki>*</nowiki>2<nowiki>*</nowiki>3) = '''6.0'''

=====Converting to Rotations=====
Specifications of system:
* Motor gear ratio: 10:1
* Motor poles: 2
* Motor phases: 3

Rescale Factor = 1 / (10<nowiki>*</nowiki>2<nowiki>*</nowiki>3) = '''0.016666667'''

===Braking Enabled===
{{DCBLDCMotor_BrakingEnabled}}

===Surge Current Limit===
{{DCBLDCMotor_SurgeCurrentLimit}}

===Acceleration===
{{DCBLDCMotor_Acceleration}}

===Data Interval===
{{DCBLDCMotor_DataInterval}}

==Motor Status==
This area of the program shows information that has been sent back from the BLDC Motor Phidget.
===Velocity===
{{DCMotor_VelocityStatus}}

===Braking Strength===
{{DCMotor_BrakingStrength}}

===Position===
The most recent Position value reported by the controller. The Position is calculated using Hall Effect sensors mounted inside the motor, therefore, the resolution of the position depends on the motor you are using.

====Other Considerations====
* {{DCMotor_RescaleFactorNote}}
* Consider using an encoder for more accurate position information.

===Active Current Limit===
{{DCMotor_ActiveCurrentLimit}}

===Motor Inductance===
{{DCMotor_MotorInductance}}

==Failsafe==
{{DCMotor_Failsafe}}

===E-Stop===
{{DCMotor_ESTOP|bldc}}

==Errors==
{{DCMotor_Errors|bldc}}

Google Apps Script and Phidgets

2025-06-18T22:11:15Z

Lmpacent: /* Introduction */

[[Category: Project]]
{{#seo:|keywords=JavaScript}}
{{#seo:|description=Log data to a Google Sheet with Phidgets and JavaScript.}}
[[Image:Google_Apps_Script.png|400px|link=|thumb|<center>Google Apps Script</center>]]
==Introduction==
Phidgets provides a JavaScript library for browser and Node.js applications. In this project, we'll create a browser application using Google Apps Script and log data from a Light Phidget to a Google Sheets spreadsheet.
===References===
[https://developers.google.com/apps-script/guides/web Apps Script - Web Apps Guide]
<br><br><br><br><br>

==Demonstration==
<center>{{#ev:youtube|V1Q93jao85w|||||rel=0}}</center>

==Connect Phidget Devices==
In this project, we will be using the [{{SERVER}}/?prodid=707 Light Phidget (LUX1000_0)] connected to a [{{SERVER}}/?prodid=1289 VINT Hub Phidget (HUB0002_0)].

[[Image:LUX1000_setup_whitecable.jpg|600px|link=]]

==Prepare Apps Script Environment==
===Start A New Spreadsheet===
Start by creating a new spreadsheet. This spreadsheet will be used to store sensor data.

[[Image:Project_appscript_newspreadsheet.png|center|500px|link=]]

===Create Apps Script===
Name your spreadsheet and then navigate to '''Extensions > Apps Script'''

[[Image:Project_appscript_newappsscript.png|center|500px||link=]]

===Add HTML File===
Name your Apps Script project and click on the '''+''' symbol to add an HTML file.

[[Image:Project_appscript_newhtml.png|center|500px|link=]]

Name the file '''index.html'''.

[[Image:Project_appscript_namehtml.png|center|500px|link=]]

==Modify Code==
===Code.gs===
Navigate to '''Code.gs''' and replace the contents with the following:
<syntaxhighlight lang=js>
function doGet(e) {
var htmlOutput = HtmlService.createHtmlOutputFromFile('index');
return htmlOutput;
}

function writeData(data, location) {
var spreadsheetId = 'spreadsheetID'; // Replace with your spreadsheet ID
var sheetName = 'Sheet1'; // Replace with your sheet name

var spreadsheet = SpreadsheetApp.openById(spreadsheetId);
var sheet = spreadsheet.getSheetByName(sheetName);
sheet.getRange(location).setValue(data)
}
</syntaxhighlight>

====Spreadsheet ID====
You can find the spreadsheet ID by navigating to your spreadsheet and copying the string of letters and numbers between '''/d/''' and '''/edit''' in the URL.

[[Image:Project_appscript_spreadsheetid.png|center|500px|link=https://cdn.phidgets.com/docs/images/3/3f/Project_appscript_spreadsheetid.png]]

===index.html===
Navigate to '''index.html''' and replace the contents with the following.

<syntaxhighlight lang=js>
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<title>Light Sensor Example</title>
</head>
<body>
<button id="grant-usb-access">Connect USB Device</button><br><br>
<button onclick="runExample()">Run Example</button><br><br>
<label>Sensor Data: </label><label id="sensorLabel"></label><br><br>
<input type="checkbox" id="logCheckbox">
<label>Log to File</label><br><br>
<script src="https://unpkg.com/phidget22@3.x/browser/phidget22.min.js"></script>
<script>
(async function () {
const illuminanceChangeDataEl = document.getElementById("sensorLabel");
const checkbox = document.getElementById("logCheckbox");
var index = 0;

function onLightSensor0_IlluminanceChange(illuminance) {
illuminanceChangeDataEl.textContent = illuminance.toString() + 'lx';
if (checkbox.checked) {
google.script.run.writeData(illuminance.toString(), "A" + index++)
}
}

try {
const conn = new phidget22.USBConnection();
await conn.connect();

const grantAccessBtn = document.getElementById('grant-usb-access');
grantAccessBtn.addEventListener('click', () => conn.requestWebUSBDeviceAccess());

const lightSensor0 = new phidget22.LightSensor();

lightSensor0.onIlluminanceChange = onLightSensor0_IlluminanceChange;

await lightSensor0.open(30000);
lightSensor0.setDataInterval(1000);
} catch(err) {
console.error('Phidget error:', err);
}

})();
</script>
</body>
</html>
</syntaxhighlight>

====USB vs Network Server Connection====
When using the Phidgets with JavaScript, you can connect to devices directly via USB or remotely through the Phidget Network Server. Depending on what you choose, this line of code will change:
<syntaxhighlight lang=js>
const conn = new phidget22.USBConnection(); //Use when connecting directly via USB
</syntaxhighlight>

<syntaxhighlight lang=js>
const conn = new phidget22.NetworkConnection(5661, 'localhost'); //Use when connecting through the Phidget Network Server
</syntaxhighlight>

In this example, we are connecting directly via USB, so we use the first option. For more information, visit our [{{SERVER}}/docs/Language_-_JavaScript JavaScript page].

==Deploy Web App==
To deploy the app, find the '''Deploy''' button and select '''New Deployment''':

[[Image:Project_appscript_newdeployment.png|center|500px|link=]]

Select '''Web App''' as the type, provide a description, and press '''Deploy''':

[[Image:Project_appscript_newdeployment2.png|center|500px|link=]]

Authorization is required as the web app will access a Google Sheet:

[[Image:Project_appscript_newdeployment_auth.png|center|500px|link=]]

After authorizing, a URL for your web app will be generated:

[[Image:Project_appscript_newdeployment_url.png|center|500px|link=]]

==Request USB Device Access==
The web app provides a '''Connect USB Device''' button:

[[Image:Project_appscript_webapp.png|center|500px|link=]]

In order to access Phidget devices over a [{{SERVER}}//docs/Language_-_JavaScript#USB_Connection USB Connection], websites must gain permission from the user through an interactive element, like a button.

[[Image:Project_appscript_webapp_usbauth.png|center|500px|link=]]

===Run Example===
After granting access, the '''Run Example''' button can be pressed, and data will stream from the Phidget device to your browser application:

[[Image:Project_appscript_webapp_data.png|center|500px|link=]]

Check the '''Log to File''' box and data will be streamed to your spreadsheet.

Google Apps Script and Phidgets

2025-06-16T23:01:13Z

Lmpacent: /* Connect Phidget Devices */

[[Category: Project]]
{{#seo:|keywords=JavaScript}}
{{#seo:|description=Log data to a Google Sheet with Phidgets and JavaScript.}}
[[Image:Google_Apps_Script.png|400px|link=|thumb|<center>Google Apps Script</center>]]
==Introduction==
Phidgets provides a JavaScript library for browser and Node.js applications. In this project, we'll create a web application using Google Apps Script and log data from a Light Phidget to a Google Sheets spreadsheet.
===References===
[https://developers.google.com/apps-script/guides/web Apps Script - Web Apps Guide]
<br><br><br><br><br>

==Demonstration==
<center>{{#ev:youtube|V1Q93jao85w|||||rel=0}}</center>

==Connect Phidget Devices==
In this project, we will be using the [{{SERVER}}/?prodid=707 Light Phidget (LUX1000_0)] connected to a [{{SERVER}}/?prodid=1289 VINT Hub Phidget (HUB0002_0)].

[[Image:LUX1000_setup_whitecable.jpg|600px|link=]]

==Prepare Apps Script Environment==
===Start A New Spreadsheet===
Start by creating a new spreadsheet. This spreadsheet will be used to store sensor data.

[[Image:Project_appscript_newspreadsheet.png|center|500px|link=]]

===Create Apps Script===
Name your spreadsheet and then navigate to '''Extensions > Apps Script'''

[[Image:Project_appscript_newappsscript.png|center|500px||link=]]

===Add HTML File===
Name your Apps Script project and click on the '''+''' symbol to add an HTML file.

[[Image:Project_appscript_newhtml.png|center|500px|link=]]

Name the file '''index.html'''.

[[Image:Project_appscript_namehtml.png|center|500px|link=]]

==Modify Code==
===Code.gs===
Navigate to '''Code.gs''' and replace the contents with the following:
<syntaxhighlight lang=js>
function doGet(e) {
var htmlOutput = HtmlService.createHtmlOutputFromFile('index');
return htmlOutput;
}

function writeData(data, location) {
var spreadsheetId = 'spreadsheetID'; // Replace with your spreadsheet ID
var sheetName = 'Sheet1'; // Replace with your sheet name

var spreadsheet = SpreadsheetApp.openById(spreadsheetId);
var sheet = spreadsheet.getSheetByName(sheetName);
sheet.getRange(location).setValue(data)
}
</syntaxhighlight>

====Spreadsheet ID====
You can find the spreadsheet ID by navigating to your spreadsheet and copying the string of letters and numbers between '''/d/''' and '''/edit''' in the URL.

[[Image:Project_appscript_spreadsheetid.png|center|500px|link=https://cdn.phidgets.com/docs/images/3/3f/Project_appscript_spreadsheetid.png]]

===index.html===
Navigate to '''index.html''' and replace the contents with the following.

<syntaxhighlight lang=js>
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<title>Light Sensor Example</title>
</head>
<body>
<button id="grant-usb-access">Connect USB Device</button><br><br>
<button onclick="runExample()">Run Example</button><br><br>
<label>Sensor Data: </label><label id="sensorLabel"></label><br><br>
<input type="checkbox" id="logCheckbox">
<label>Log to File</label><br><br>
<script src="https://unpkg.com/phidget22@3.x/browser/phidget22.min.js"></script>
<script>
(async function () {
const illuminanceChangeDataEl = document.getElementById("sensorLabel");
const checkbox = document.getElementById("logCheckbox");
var index = 0;

function onLightSensor0_IlluminanceChange(illuminance) {
illuminanceChangeDataEl.textContent = illuminance.toString() + 'lx';
if (checkbox.checked) {
google.script.run.writeData(illuminance.toString(), "A" + index++)
}
}

try {
const conn = new phidget22.USBConnection();
await conn.connect();

const grantAccessBtn = document.getElementById('grant-usb-access');
grantAccessBtn.addEventListener('click', () => conn.requestWebUSBDeviceAccess());

const lightSensor0 = new phidget22.LightSensor();

lightSensor0.onIlluminanceChange = onLightSensor0_IlluminanceChange;

await lightSensor0.open(30000);
lightSensor0.setDataInterval(1000);
} catch(err) {
console.error('Phidget error:', err);
}

})();
</script>
</body>
</html>
</syntaxhighlight>

====USB vs Network Server Connection====
When using the Phidgets with JavaScript, you can connect to devices directly via USB or remotely through the Phidget Network Server. Depending on what you choose, this line of code will change:
<syntaxhighlight lang=js>
const conn = new phidget22.USBConnection(); //Use when connecting directly via USB
</syntaxhighlight>

<syntaxhighlight lang=js>
const conn = new phidget22.NetworkConnection(5661, 'localhost'); //Use when connecting through the Phidget Network Server
</syntaxhighlight>

In this example, we are connecting directly via USB, so we use the first option. For more information, visit our [{{SERVER}}/docs/Language_-_JavaScript JavaScript page].

==Deploy Web App==
To deploy the app, find the '''Deploy''' button and select '''New Deployment''':

[[Image:Project_appscript_newdeployment.png|center|500px|link=]]

Select '''Web App''' as the type, provide a description, and press '''Deploy''':

[[Image:Project_appscript_newdeployment2.png|center|500px|link=]]

Authorization is required as the web app will access a Google Sheet:

[[Image:Project_appscript_newdeployment_auth.png|center|500px|link=]]

After authorizing, a URL for your web app will be generated:

[[Image:Project_appscript_newdeployment_url.png|center|500px|link=]]

==Request USB Device Access==
The web app provides a '''Connect USB Device''' button:

[[Image:Project_appscript_webapp.png|center|500px|link=]]

In order to access Phidget devices over a [{{SERVER}}//docs/Language_-_JavaScript#USB_Connection USB Connection], websites must gain permission from the user through an interactive element, like a button.

[[Image:Project_appscript_webapp_usbauth.png|center|500px|link=]]

===Run Example===
After granting access, the '''Run Example''' button can be pressed, and data will stream from the Phidget device to your browser application:

[[Image:Project_appscript_webapp_data.png|center|500px|link=]]

Check the '''Log to File''' box and data will be streamed to your spreadsheet.

Google Apps Script and Phidgets

2025-06-16T23:00:20Z

Lmpacent: /* Connect Phidget Devices */

[[Category: Project]]
{{#seo:|keywords=JavaScript}}
{{#seo:|description=Log data to a Google Sheet with Phidgets and JavaScript.}}
[[Image:Google_Apps_Script.png|400px|link=|thumb|<center>Google Apps Script</center>]]
==Introduction==
Phidgets provides a JavaScript library for browser and Node.js applications. In this project, we'll create a web application using Google Apps Script and log data from a Light Phidget to a Google Sheets spreadsheet.
===References===
[https://developers.google.com/apps-script/guides/web Apps Script - Web Apps Guide]
<br><br><br><br><br>

==Demonstration==
<center>{{#ev:youtube|V1Q93jao85w|||||rel=0}}</center>

==Connect Phidget Devices==
In this project, we will be using the [{{SERVER}}/?prodid=707 Light Phidget (LUX1000_0)] connected to a [{{SERVER}}/?prodid=1289 VINT Hub Phidget].

[[Image:LUX1000_setup_whitecable.jpg|600px|link=]]

==Prepare Apps Script Environment==
===Start A New Spreadsheet===
Start by creating a new spreadsheet. This spreadsheet will be used to store sensor data.

[[Image:Project_appscript_newspreadsheet.png|center|500px|link=]]

===Create Apps Script===
Name your spreadsheet and then navigate to '''Extensions > Apps Script'''

[[Image:Project_appscript_newappsscript.png|center|500px||link=]]

===Add HTML File===
Name your Apps Script project and click on the '''+''' symbol to add an HTML file.

[[Image:Project_appscript_newhtml.png|center|500px|link=]]

Name the file '''index.html'''.

[[Image:Project_appscript_namehtml.png|center|500px|link=]]

==Modify Code==
===Code.gs===
Navigate to '''Code.gs''' and replace the contents with the following:
<syntaxhighlight lang=js>
function doGet(e) {
var htmlOutput = HtmlService.createHtmlOutputFromFile('index');
return htmlOutput;
}

function writeData(data, location) {
var spreadsheetId = 'spreadsheetID'; // Replace with your spreadsheet ID
var sheetName = 'Sheet1'; // Replace with your sheet name

var spreadsheet = SpreadsheetApp.openById(spreadsheetId);
var sheet = spreadsheet.getSheetByName(sheetName);
sheet.getRange(location).setValue(data)
}
</syntaxhighlight>

====Spreadsheet ID====
You can find the spreadsheet ID by navigating to your spreadsheet and copying the string of letters and numbers between '''/d/''' and '''/edit''' in the URL.

[[Image:Project_appscript_spreadsheetid.png|center|500px|link=https://cdn.phidgets.com/docs/images/3/3f/Project_appscript_spreadsheetid.png]]

===index.html===
Navigate to '''index.html''' and replace the contents with the following.

<syntaxhighlight lang=js>
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<title>Light Sensor Example</title>
</head>
<body>
<button id="grant-usb-access">Connect USB Device</button><br><br>
<button onclick="runExample()">Run Example</button><br><br>
<label>Sensor Data: </label><label id="sensorLabel"></label><br><br>
<input type="checkbox" id="logCheckbox">
<label>Log to File</label><br><br>
<script src="https://unpkg.com/phidget22@3.x/browser/phidget22.min.js"></script>
<script>
(async function () {
const illuminanceChangeDataEl = document.getElementById("sensorLabel");
const checkbox = document.getElementById("logCheckbox");
var index = 0;

function onLightSensor0_IlluminanceChange(illuminance) {
illuminanceChangeDataEl.textContent = illuminance.toString() + 'lx';
if (checkbox.checked) {
google.script.run.writeData(illuminance.toString(), "A" + index++)
}
}

try {
const conn = new phidget22.USBConnection();
await conn.connect();

const grantAccessBtn = document.getElementById('grant-usb-access');
grantAccessBtn.addEventListener('click', () => conn.requestWebUSBDeviceAccess());

const lightSensor0 = new phidget22.LightSensor();

lightSensor0.onIlluminanceChange = onLightSensor0_IlluminanceChange;

await lightSensor0.open(30000);
lightSensor0.setDataInterval(1000);
} catch(err) {
console.error('Phidget error:', err);
}

})();
</script>
</body>
</html>
</syntaxhighlight>

====USB vs Network Server Connection====
When using the Phidgets with JavaScript, you can connect to devices directly via USB or remotely through the Phidget Network Server. Depending on what you choose, this line of code will change:
<syntaxhighlight lang=js>
const conn = new phidget22.USBConnection(); //Use when connecting directly via USB
</syntaxhighlight>

<syntaxhighlight lang=js>
const conn = new phidget22.NetworkConnection(5661, 'localhost'); //Use when connecting through the Phidget Network Server
</syntaxhighlight>

In this example, we are connecting directly via USB, so we use the first option. For more information, visit our [{{SERVER}}/docs/Language_-_JavaScript JavaScript page].

==Deploy Web App==
To deploy the app, find the '''Deploy''' button and select '''New Deployment''':

[[Image:Project_appscript_newdeployment.png|center|500px|link=]]

Select '''Web App''' as the type, provide a description, and press '''Deploy''':

[[Image:Project_appscript_newdeployment2.png|center|500px|link=]]

Authorization is required as the web app will access a Google Sheet:

[[Image:Project_appscript_newdeployment_auth.png|center|500px|link=]]

After authorizing, a URL for your web app will be generated:

[[Image:Project_appscript_newdeployment_url.png|center|500px|link=]]

==Request USB Device Access==
The web app provides a '''Connect USB Device''' button:

[[Image:Project_appscript_webapp.png|center|500px|link=]]

In order to access Phidget devices over a [{{SERVER}}//docs/Language_-_JavaScript#USB_Connection USB Connection], websites must gain permission from the user through an interactive element, like a button.

[[Image:Project_appscript_webapp_usbauth.png|center|500px|link=]]

===Run Example===
After granting access, the '''Run Example''' button can be pressed, and data will stream from the Phidget device to your browser application:

[[Image:Project_appscript_webapp_data.png|center|500px|link=]]

Check the '''Log to File''' box and data will be streamed to your spreadsheet.

Terms and Conditions

2025-06-16T22:47:36Z

Lmpacent: /* All returns must be authorized by Phidgets Inc. */

[[Category:Linked From Website]]

==Product Warranty==

All Phidgets products are warranted to be free of defects in material or workmanship under normal use and service for a period of one year from the date of shipment. This warranty does not include damage resulting from accident or misuse. The warranty is also void if the product is modified. This warranty is in lieu of all other warranties expressed or implied including the implied warranties of merchantability of fitness for a particular purpose, whether arising by law, custom or conduct, and the rights and remedies provided under this warranty are exclusive and in lieu of any other rights or remedies. In no event shall Phidgets Incorporated be liable for consequential damages.

If you believe that your product is defective while still under warranty, {{ContactUs|contact us}}. Once the support desk confirms that the product is defective, we will replace your defective product free of charge.

==Shipping==
===Last Call at 12:00PM===
Orders received before 12:00 PM Mountain Time (GMT-07:00) Monday to Friday will be shipped the same day.

Orders containing cut-to-length parts may not ship on the same day due to the additional processing time associated with these orders.

===Shipping Costs===
Shipping costs are calculated at checkout and presented for your review before you confirm your order. If multiple shipping options are available for your destination, all options will be listed so you can choose the one that best suits your needs.

If you have your own UPS or FedEx account, you can use it at checkout and be billed directly by the carrier. This gives you access to a wider range of shipping options.

Note that a $5.00 handling charge is added to all orders that are under $50.00.

===Shipping in Canada===
We offer the following services:
* '''UPS Express Saver'''. 1 - 3 business days.
* '''UPS Expedited'''. 2 - 5 business days. Available for packages over 3 lbs.
* '''UPS Standard'''. 3 - 5 business days ground delivery.

===Shipping to the United States===
We offer the following services:
* '''UPS Express Saver'''. 1 - 3 business days.
* '''UPS Expedited'''. 2 - 5 business days. Available for packages over 3 lbs.
* '''UPS Standard'''. 3 - 5 business days ground delivery.

Effective May 2, 2025, orders shipped to the United States will incur additional duties, tariffs, and brokerage fees, regardless of the order value. For more details, visit our guide about [[U.S._Tariffs | U.S. Tariffs]].

===International Shipments===
We offer the following services:
* '''UPS Worldwide Express Saver'''. 1 - 3 business days.
* '''UPS Worldwide Expedited'''. 2 - 5 business days. Available for packages over 3 lbs.

====European Union====
Effective July 1, 2021, the European Union (EU) updated its Value Added Tax (VAT) regulations. All shipments to EU countries now require formal customs clearance and are subject to VAT based on the destination country.

For goods with an intrinsic value up to €150, VAT must be collected at the time of purchase. This means for orders under $200 USD, we require prepayment of VAT and brokerage fees at checkout to ensure fast, hassle-free delivery.

For orders over $200 USD, we provide the option to prepay all applicable import fees (including VAT and brokerage). If you choose this option, the quoted amount is guaranteed — there will be no additional charges upon delivery.

We use UPS® Global Checkout to collect import fees and taxes based on your product's HS Code and Country of Origin. There is a fee associated with the UPS® Global Checkout service. At Phidgets Inc., we continually monitor and negotiate all fees to ensure our customers receive the best deal possible.

Customs policies vary by country, so we recommend contacting your local customs office for more information.

====Other Countries====
International shipments may be subject to import duties, taxes, and brokerage fees upon arrival in your country. These charges are determined by your local customs authorities and are the responsibility of the recipient.

At checkout, we provide the option to prepay these fees. If you choose this option, the quoted amount is guaranteed — there will be no additional charges upon delivery.

We use UPS® Global Checkout to collect import fees and taxes based on your product's HS Code and Country of Origin. There is a fee associated with the UPS® Global Checkout service. At Phidgets Inc., we continually monitor and negotiate all fees to ensure our customers receive the best deal possible.

Customs policies vary by country, so we recommend contacting your local customs office for more information.

===Tracking Your Order===
You can track your shipment using the tracking number sent to you by email when your order was shipped.

===Refunds on Late Deliveries===

Normally, UPS will offer a service guarantee refund when their deliveries arrive late. However, for companies that apply for shipping discounts, this refund does not apply. Phidgets Inc. has applied for such discounts in order to keep shipping costs down and regrettably cannot offer compensation for late shipments.

===Damaged or Lost Shipment===

'''Shipping on our UPS account''' - Report all damaged or lost shipments to support@phidgets.com and include your order number. According to UPS, in order to be considered lost, a package must be undelivered 24 hours after the expected delivery date and time. Before contacting us, check your shipment status at ups.ca.

Damaged or lost items will be replaced at no charge (including shipping costs).

'''Shipping on your UPS account''' - You must notify your local UPS office. If they confirm that they have lost your shipment, you must repurchase the lost or damaged products from Phidgets and file a claim with your local UPS in order to get reimbursed.

===Refused/Missed Delivery===
If no one is available to accept the package upon delivery, UPS will attempt redelivery two more times, as per their standard procedure. If all delivery attempts fail, UPS will hold the package for 5 days before returning it to us. In such cases, we will issue a refund for your order minus the cost of shipping (both directions) and a flat $50 fee, up to the total value of the package. This policy applies both to deliveries that failed due to no one being present and to packages that were refused at the delivery address.

===Incoterms===

We use the following Incoterms depending on the shipping and payment arrangement:

* '''FCA (Free Carrier):''' Used when shipping on the customer’s carrier account. Risk and responsibility transfer to the customer once the goods are handed over to the carrier at our facility.

* '''DDP (Delivered Duty Paid):''' Used when the customer chooses to pre-pay import fees and taxes at checkout. We handle all import fees and deliver the goods to the destination address.

* '''DAP (Delivered at Place):''' Used when the customer opts to pay import fees and taxes upon delivery. We deliver the goods, but the customer is responsible for paying any import fees directly to the carrier.

==Product Returns==
===All Returns Must Be Authorized===
Before returning a package {{ContactUs|contact us}} and ask for a Return Merchandise Authorization or RMA number. Once you have received it, put the RMA number on the outside of the packaging as well as the packing slip so that it is possible for us to track what the package is supposed to be. Any merchandise returned without an RMA number clearly visible on the packaging will be charged an administrative fee of $25.00 or the value of the returned product, whichever is less ''if we are able to determine what it is''. In the event we are unable to determine what the package is, it will be refused and returned to the sender.

===Unopened Product===
Phidgets accepts returns of unopened products within 30 days of the date of purchase. To initiate a return, please contact us by phone or email to obtain an RMA number. Products must be shipped back to Phidgets Inc. prepaid. A refund will be issued to your credit card once we receive and inspect the returned items.

Returns received after 30 days are subject to a restocking fee of 25% of the package's value (minimum $5.00, maximum $500).

We do '''not''' accept returns beyond 90 days from the date of purchase.

===Cut to Length===
Unfortunately we cannot accept returns on any items which are cut to custom lengths. This includes: cable, wire, roller chain, linear shaft, rotary shaft, and t-slot extrusions.

===We Shipped the Wrong/Incomplete Product===
{{ContactUs|Contact us}}. We will get the correct product sent to you immediately, and will pay all shipping charges.

==Payment Terms==
We accept credit cards, PayPal, and Wire Transfers.

{| style="border:1px solid darkgray;" cellpadding="7px;"
|-style="background: #d1d1d1" align=center
! Payment Method|| Terms
|-
|style="background: #f0f0f0" align=center|Credit Cards
|style="background: #f0f0f0" align=left|Visa, MasterCard, American Express (for order in CAD only)
|-
|style="background: #f0f0f0" align=center|PayPal
|style="background: #f0f0f0" align=left|PayPal is accepted. There are no extra fees for using PayPal
|-
|style="background: #f0f0f0" align=center|Wire Transfers
|style="background: #f0f0f0" align=left|Wire transfers are only accepted for orders over $200.00 USD (excluding shipping charges). There is a $25.00 USD charge for wire transfers under $500.00 USD. Any fees charged by the sending bank are your responsibility.<br />Please make sure that the amount sent to us covers both our invoice and your bank fees. Products are not shipped until the money is deposited in our bank account. We recommend that you e-mail orders@phidgets.com with the amount of the transfer and the invoice you are paying. <br />Any order for which payment is not received within 15 days, will be canceled.
|}

==Security and Privacy==
Phidgets Inc. pledges a safe and worry-free shopping experience. IF you are using the current version of Internet Explorer, on the checkout page where you enter your credit card information, you will notice a a locked padlock icon on the top bar your browser window. If you are using Mozilla Firefox, you will notice a locked padlock icon in the bottom right corner of your browser window. If this icon does not appear, please contact us directly to complete your purchase. These icons tell you that the page you are on is secure. We use Secure Sockets Layer (SSL 128-bit) technology with a digital certificate by GeoTrust, Inc. for Internet security to protect your personal information. This encryption makes it impossible for anyone to read your information in transit. We do not store your credit information and it is deleted once it has been securely transmitted to Moneris for processing.

We use your e-mail address to let you know your shipment's tracking number. Your phone number is required by the Courier Company. We do not sell, rent or give any of your personal information to any unrelated third parties with the exception of Moneris for authorizing credit card payments and the Courier company to let them know where to deliver the shipment and how to contact you if there is any problems.

If you have any questions or concerns about our Security and Privacy policy, call us at 1.403.282.7335 or e-mail us at support@phidgets.com

Phidgets Inc. uses various Google Analytics tools such as conversion tracking in order to improve the effectiveness of the website. These statistics are completely anonymous.

==Holidays==
Phidgets, Inc. will be closed on the following days. During these times, the site will still be accessible and orders can be placed, but they will not ship until the next business day.

{| style="border:1px solid darkgray;" cellpadding="7px;"
|-style="background: #d1d1d1" align=center
! style="text-align:center;"| Holiday
! style="text-align:center;"| Description
! style="text-align:center;"| 2025
! style="text-align:center;"| 2026
|-
|style="background: #f0f0f0" align=center| Alberta Family Day
|style="background: #f0f0f0" align=center| Third Monday in February
|style="background: #f0f0f0" align=center| Feb 17
|style="background: #f0f0f0" align=center| Feb 16
|-
|style="background: #f0f0f0" align=center| Good Friday
|style="background: #f0f0f0" align=center| Friday before Easter Sunday
|style="background: #f0f0f0" align=center| Apr 18
|style="background: #f0f0f0" align=center| Apr 3
|-
|style="background: #f0f0f0" align=center| Victoria Day
|style="background: #f0f0f0" align=center| Monday before May 25
|style="background: #f0f0f0" align=center| May 19
|style="background: #f0f0f0" align=center| May 18
|-
|style="background: #f0f0f0" align=center| Canada Day
|style="background: #f0f0f0" align=center| First day of July (or nearest business day)
|style="background: #f0f0f0" align=center| Jul 1
|style="background: #f0f0f0" align=center| Jul 1
|-
|style="background: #f0f0f0" align=center| Heritage Day
|style="background: #f0f0f0" align=center| First Monday in August
|style="background: #f0f0f0" align=center| Aug 4
|style="background: #f0f0f0" align=center| Aug 3
|-
|style="background: #f0f0f0" align=center| Labour Day
|style="background: #f0f0f0" align=center| First Monday in September
|style="background: #f0f0f0" align=center| Sept 1
|style="background: #f0f0f0" align=center| Sept 7
|-
|style="background: #f0f0f0" align=center| Thanksgiving
|style="background: #f0f0f0" align=center| Second Monday in October
|style="background: #f0f0f0" align=center| Oct 13
|style="background: #f0f0f0" align=center| Oct 12
|-
|style="background: #f0f0f0" align=center| Remembrance Day
|style="background: #f0f0f0" align=center| November 11 (or nearest business day)
|style="background: #f0f0f0" align=center| Nov 11
|style="background: #f0f0f0" align=center| Nov 11
|-
|style="background: #f0f0f0" align=center| Christmas and New Years
|style="background: #f0f0f0" align=center| Varies
|style="background: #f0f0f0" align=center| TBA
|style="background: #f0f0f0" align=center| TBA
|-
|}

Terms and Conditions

2025-06-16T22:46:32Z

Lmpacent: /* We shipped the wrong/incomplete product */

[[Category:Linked From Website]]

==Product Warranty==

All Phidgets products are warranted to be free of defects in material or workmanship under normal use and service for a period of one year from the date of shipment. This warranty does not include damage resulting from accident or misuse. The warranty is also void if the product is modified. This warranty is in lieu of all other warranties expressed or implied including the implied warranties of merchantability of fitness for a particular purpose, whether arising by law, custom or conduct, and the rights and remedies provided under this warranty are exclusive and in lieu of any other rights or remedies. In no event shall Phidgets Incorporated be liable for consequential damages.

If you believe that your product is defective while still under warranty, {{ContactUs|contact us}}. Once the support desk confirms that the product is defective, we will replace your defective product free of charge.

==Shipping==
===Last Call at 12:00PM===
Orders received before 12:00 PM Mountain Time (GMT-07:00) Monday to Friday will be shipped the same day.

Orders containing cut-to-length parts may not ship on the same day due to the additional processing time associated with these orders.

===Shipping Costs===
Shipping costs are calculated at checkout and presented for your review before you confirm your order. If multiple shipping options are available for your destination, all options will be listed so you can choose the one that best suits your needs.

If you have your own UPS or FedEx account, you can use it at checkout and be billed directly by the carrier. This gives you access to a wider range of shipping options.

Note that a $5.00 handling charge is added to all orders that are under $50.00.

===Shipping in Canada===
We offer the following services:
* '''UPS Express Saver'''. 1 - 3 business days.
* '''UPS Expedited'''. 2 - 5 business days. Available for packages over 3 lbs.
* '''UPS Standard'''. 3 - 5 business days ground delivery.

===Shipping to the United States===
We offer the following services:
* '''UPS Express Saver'''. 1 - 3 business days.
* '''UPS Expedited'''. 2 - 5 business days. Available for packages over 3 lbs.
* '''UPS Standard'''. 3 - 5 business days ground delivery.

Effective May 2, 2025, orders shipped to the United States will incur additional duties, tariffs, and brokerage fees, regardless of the order value. For more details, visit our guide about [[U.S._Tariffs | U.S. Tariffs]].

===International Shipments===
We offer the following services:
* '''UPS Worldwide Express Saver'''. 1 - 3 business days.
* '''UPS Worldwide Expedited'''. 2 - 5 business days. Available for packages over 3 lbs.

====European Union====
Effective July 1, 2021, the European Union (EU) updated its Value Added Tax (VAT) regulations. All shipments to EU countries now require formal customs clearance and are subject to VAT based on the destination country.

For goods with an intrinsic value up to €150, VAT must be collected at the time of purchase. This means for orders under $200 USD, we require prepayment of VAT and brokerage fees at checkout to ensure fast, hassle-free delivery.

For orders over $200 USD, we provide the option to prepay all applicable import fees (including VAT and brokerage). If you choose this option, the quoted amount is guaranteed — there will be no additional charges upon delivery.

We use UPS® Global Checkout to collect import fees and taxes based on your product's HS Code and Country of Origin. There is a fee associated with the UPS® Global Checkout service. At Phidgets Inc., we continually monitor and negotiate all fees to ensure our customers receive the best deal possible.

Customs policies vary by country, so we recommend contacting your local customs office for more information.

====Other Countries====
International shipments may be subject to import duties, taxes, and brokerage fees upon arrival in your country. These charges are determined by your local customs authorities and are the responsibility of the recipient.

At checkout, we provide the option to prepay these fees. If you choose this option, the quoted amount is guaranteed — there will be no additional charges upon delivery.

We use UPS® Global Checkout to collect import fees and taxes based on your product's HS Code and Country of Origin. There is a fee associated with the UPS® Global Checkout service. At Phidgets Inc., we continually monitor and negotiate all fees to ensure our customers receive the best deal possible.

Customs policies vary by country, so we recommend contacting your local customs office for more information.

===Tracking Your Order===
You can track your shipment using the tracking number sent to you by email when your order was shipped.

===Refunds on Late Deliveries===

Normally, UPS will offer a service guarantee refund when their deliveries arrive late. However, for companies that apply for shipping discounts, this refund does not apply. Phidgets Inc. has applied for such discounts in order to keep shipping costs down and regrettably cannot offer compensation for late shipments.

===Damaged or Lost Shipment===

'''Shipping on our UPS account''' - Report all damaged or lost shipments to support@phidgets.com and include your order number. According to UPS, in order to be considered lost, a package must be undelivered 24 hours after the expected delivery date and time. Before contacting us, check your shipment status at ups.ca.

Damaged or lost items will be replaced at no charge (including shipping costs).

'''Shipping on your UPS account''' - You must notify your local UPS office. If they confirm that they have lost your shipment, you must repurchase the lost or damaged products from Phidgets and file a claim with your local UPS in order to get reimbursed.

===Refused/Missed Delivery===
If no one is available to accept the package upon delivery, UPS will attempt redelivery two more times, as per their standard procedure. If all delivery attempts fail, UPS will hold the package for 5 days before returning it to us. In such cases, we will issue a refund for your order minus the cost of shipping (both directions) and a flat $50 fee, up to the total value of the package. This policy applies both to deliveries that failed due to no one being present and to packages that were refused at the delivery address.

===Incoterms===

We use the following Incoterms depending on the shipping and payment arrangement:

* '''FCA (Free Carrier):''' Used when shipping on the customer’s carrier account. Risk and responsibility transfer to the customer once the goods are handed over to the carrier at our facility.

* '''DDP (Delivered Duty Paid):''' Used when the customer chooses to pre-pay import fees and taxes at checkout. We handle all import fees and deliver the goods to the destination address.

* '''DAP (Delivered at Place):''' Used when the customer opts to pay import fees and taxes upon delivery. We deliver the goods, but the customer is responsible for paying any import fees directly to the carrier.

==Product Returns==
===All returns must be authorized by Phidgets Inc.===
Before returning a package {{ContactUs|contact us}} and ask for a Return Merchandise Authorization or RMA number. Once you have received it, put the RMA number on the outside of the packaging as well as the packing slip so that it is possible for us to track what the package is supposed to be. Any merchandise returned without an RMA number clearly visible on the packaging will be charged an administrative fee of $25.00 or the value of the returned product, whichever is less ''if we are able to determine what it is''. In the event we are unable to determine what the package is, it will be refused and returned to the sender.

===Unopened Product===
Phidgets accepts returns of unopened products within 30 days of the date of purchase. To initiate a return, please contact us by phone or email to obtain an RMA number. Products must be shipped back to Phidgets Inc. prepaid. A refund will be issued to your credit card once we receive and inspect the returned items.

Returns received after 30 days are subject to a restocking fee of 25% of the package's value (minimum $5.00, maximum $500).

We do '''not''' accept returns beyond 90 days from the date of purchase.

===Cut to Length===
Unfortunately we cannot accept returns on any items which are cut to custom lengths. This includes: cable, wire, roller chain, linear shaft, rotary shaft, and t-slot extrusions.

===We Shipped the Wrong/Incomplete Product===
{{ContactUs|Contact us}}. We will get the correct product sent to you immediately, and will pay all shipping charges.

==Payment Terms==
We accept credit cards, PayPal, and Wire Transfers.

{| style="border:1px solid darkgray;" cellpadding="7px;"
|-style="background: #d1d1d1" align=center
! Payment Method|| Terms
|-
|style="background: #f0f0f0" align=center|Credit Cards
|style="background: #f0f0f0" align=left|Visa, MasterCard, American Express (for order in CAD only)
|-
|style="background: #f0f0f0" align=center|PayPal
|style="background: #f0f0f0" align=left|PayPal is accepted. There are no extra fees for using PayPal
|-
|style="background: #f0f0f0" align=center|Wire Transfers
|style="background: #f0f0f0" align=left|Wire transfers are only accepted for orders over $200.00 USD (excluding shipping charges). There is a $25.00 USD charge for wire transfers under $500.00 USD. Any fees charged by the sending bank are your responsibility.<br />Please make sure that the amount sent to us covers both our invoice and your bank fees. Products are not shipped until the money is deposited in our bank account. We recommend that you e-mail orders@phidgets.com with the amount of the transfer and the invoice you are paying. <br />Any order for which payment is not received within 15 days, will be canceled.
|}

==Security and Privacy==
Phidgets Inc. pledges a safe and worry-free shopping experience. IF you are using the current version of Internet Explorer, on the checkout page where you enter your credit card information, you will notice a a locked padlock icon on the top bar your browser window. If you are using Mozilla Firefox, you will notice a locked padlock icon in the bottom right corner of your browser window. If this icon does not appear, please contact us directly to complete your purchase. These icons tell you that the page you are on is secure. We use Secure Sockets Layer (SSL 128-bit) technology with a digital certificate by GeoTrust, Inc. for Internet security to protect your personal information. This encryption makes it impossible for anyone to read your information in transit. We do not store your credit information and it is deleted once it has been securely transmitted to Moneris for processing.

We use your e-mail address to let you know your shipment's tracking number. Your phone number is required by the Courier Company. We do not sell, rent or give any of your personal information to any unrelated third parties with the exception of Moneris for authorizing credit card payments and the Courier company to let them know where to deliver the shipment and how to contact you if there is any problems.

If you have any questions or concerns about our Security and Privacy policy, call us at 1.403.282.7335 or e-mail us at support@phidgets.com

Phidgets Inc. uses various Google Analytics tools such as conversion tracking in order to improve the effectiveness of the website. These statistics are completely anonymous.

==Holidays==
Phidgets, Inc. will be closed on the following days. During these times, the site will still be accessible and orders can be placed, but they will not ship until the next business day.

{| style="border:1px solid darkgray;" cellpadding="7px;"
|-style="background: #d1d1d1" align=center
! style="text-align:center;"| Holiday
! style="text-align:center;"| Description
! style="text-align:center;"| 2025
! style="text-align:center;"| 2026
|-
|style="background: #f0f0f0" align=center| Alberta Family Day
|style="background: #f0f0f0" align=center| Third Monday in February
|style="background: #f0f0f0" align=center| Feb 17
|style="background: #f0f0f0" align=center| Feb 16
|-
|style="background: #f0f0f0" align=center| Good Friday
|style="background: #f0f0f0" align=center| Friday before Easter Sunday
|style="background: #f0f0f0" align=center| Apr 18
|style="background: #f0f0f0" align=center| Apr 3
|-
|style="background: #f0f0f0" align=center| Victoria Day
|style="background: #f0f0f0" align=center| Monday before May 25
|style="background: #f0f0f0" align=center| May 19
|style="background: #f0f0f0" align=center| May 18
|-
|style="background: #f0f0f0" align=center| Canada Day
|style="background: #f0f0f0" align=center| First day of July (or nearest business day)
|style="background: #f0f0f0" align=center| Jul 1
|style="background: #f0f0f0" align=center| Jul 1
|-
|style="background: #f0f0f0" align=center| Heritage Day
|style="background: #f0f0f0" align=center| First Monday in August
|style="background: #f0f0f0" align=center| Aug 4
|style="background: #f0f0f0" align=center| Aug 3
|-
|style="background: #f0f0f0" align=center| Labour Day
|style="background: #f0f0f0" align=center| First Monday in September
|style="background: #f0f0f0" align=center| Sept 1
|style="background: #f0f0f0" align=center| Sept 7
|-
|style="background: #f0f0f0" align=center| Thanksgiving
|style="background: #f0f0f0" align=center| Second Monday in October
|style="background: #f0f0f0" align=center| Oct 13
|style="background: #f0f0f0" align=center| Oct 12
|-
|style="background: #f0f0f0" align=center| Remembrance Day
|style="background: #f0f0f0" align=center| November 11 (or nearest business day)
|style="background: #f0f0f0" align=center| Nov 11
|style="background: #f0f0f0" align=center| Nov 11
|-
|style="background: #f0f0f0" align=center| Christmas and New Years
|style="background: #f0f0f0" align=center| Varies
|style="background: #f0f0f0" align=center| TBA
|style="background: #f0f0f0" align=center| TBA
|-
|}

Terms and Conditions

2025-06-16T22:45:44Z

Lmpacent: /* Tracking your order */

[[Category:Linked From Website]]

==Product Warranty==

All Phidgets products are warranted to be free of defects in material or workmanship under normal use and service for a period of one year from the date of shipment. This warranty does not include damage resulting from accident or misuse. The warranty is also void if the product is modified. This warranty is in lieu of all other warranties expressed or implied including the implied warranties of merchantability of fitness for a particular purpose, whether arising by law, custom or conduct, and the rights and remedies provided under this warranty are exclusive and in lieu of any other rights or remedies. In no event shall Phidgets Incorporated be liable for consequential damages.

If you believe that your product is defective while still under warranty, {{ContactUs|contact us}}. Once the support desk confirms that the product is defective, we will replace your defective product free of charge.

==Shipping==
===Last Call at 12:00PM===
Orders received before 12:00 PM Mountain Time (GMT-07:00) Monday to Friday will be shipped the same day.

Orders containing cut-to-length parts may not ship on the same day due to the additional processing time associated with these orders.

===Shipping Costs===
Shipping costs are calculated at checkout and presented for your review before you confirm your order. If multiple shipping options are available for your destination, all options will be listed so you can choose the one that best suits your needs.

If you have your own UPS or FedEx account, you can use it at checkout and be billed directly by the carrier. This gives you access to a wider range of shipping options.

Note that a $5.00 handling charge is added to all orders that are under $50.00.

===Shipping in Canada===
We offer the following services:
* '''UPS Express Saver'''. 1 - 3 business days.
* '''UPS Expedited'''. 2 - 5 business days. Available for packages over 3 lbs.
* '''UPS Standard'''. 3 - 5 business days ground delivery.

===Shipping to the United States===
We offer the following services:
* '''UPS Express Saver'''. 1 - 3 business days.
* '''UPS Expedited'''. 2 - 5 business days. Available for packages over 3 lbs.
* '''UPS Standard'''. 3 - 5 business days ground delivery.

Effective May 2, 2025, orders shipped to the United States will incur additional duties, tariffs, and brokerage fees, regardless of the order value. For more details, visit our guide about [[U.S._Tariffs | U.S. Tariffs]].

===International Shipments===
We offer the following services:
* '''UPS Worldwide Express Saver'''. 1 - 3 business days.
* '''UPS Worldwide Expedited'''. 2 - 5 business days. Available for packages over 3 lbs.

====European Union====
Effective July 1, 2021, the European Union (EU) updated its Value Added Tax (VAT) regulations. All shipments to EU countries now require formal customs clearance and are subject to VAT based on the destination country.

For goods with an intrinsic value up to €150, VAT must be collected at the time of purchase. This means for orders under $200 USD, we require prepayment of VAT and brokerage fees at checkout to ensure fast, hassle-free delivery.

For orders over $200 USD, we provide the option to prepay all applicable import fees (including VAT and brokerage). If you choose this option, the quoted amount is guaranteed — there will be no additional charges upon delivery.

We use UPS® Global Checkout to collect import fees and taxes based on your product's HS Code and Country of Origin. There is a fee associated with the UPS® Global Checkout service. At Phidgets Inc., we continually monitor and negotiate all fees to ensure our customers receive the best deal possible.

Customs policies vary by country, so we recommend contacting your local customs office for more information.

====Other Countries====
International shipments may be subject to import duties, taxes, and brokerage fees upon arrival in your country. These charges are determined by your local customs authorities and are the responsibility of the recipient.

At checkout, we provide the option to prepay these fees. If you choose this option, the quoted amount is guaranteed — there will be no additional charges upon delivery.

We use UPS® Global Checkout to collect import fees and taxes based on your product's HS Code and Country of Origin. There is a fee associated with the UPS® Global Checkout service. At Phidgets Inc., we continually monitor and negotiate all fees to ensure our customers receive the best deal possible.

Customs policies vary by country, so we recommend contacting your local customs office for more information.

===Tracking Your Order===
You can track your shipment using the tracking number sent to you by email when your order was shipped.

===Refunds on Late Deliveries===

Normally, UPS will offer a service guarantee refund when their deliveries arrive late. However, for companies that apply for shipping discounts, this refund does not apply. Phidgets Inc. has applied for such discounts in order to keep shipping costs down and regrettably cannot offer compensation for late shipments.

===Damaged or Lost Shipment===

'''Shipping on our UPS account''' - Report all damaged or lost shipments to support@phidgets.com and include your order number. According to UPS, in order to be considered lost, a package must be undelivered 24 hours after the expected delivery date and time. Before contacting us, check your shipment status at ups.ca.

Damaged or lost items will be replaced at no charge (including shipping costs).

'''Shipping on your UPS account''' - You must notify your local UPS office. If they confirm that they have lost your shipment, you must repurchase the lost or damaged products from Phidgets and file a claim with your local UPS in order to get reimbursed.

===Refused/Missed Delivery===
If no one is available to accept the package upon delivery, UPS will attempt redelivery two more times, as per their standard procedure. If all delivery attempts fail, UPS will hold the package for 5 days before returning it to us. In such cases, we will issue a refund for your order minus the cost of shipping (both directions) and a flat $50 fee, up to the total value of the package. This policy applies both to deliveries that failed due to no one being present and to packages that were refused at the delivery address.

===Incoterms===

We use the following Incoterms depending on the shipping and payment arrangement:

* '''FCA (Free Carrier):''' Used when shipping on the customer’s carrier account. Risk and responsibility transfer to the customer once the goods are handed over to the carrier at our facility.

* '''DDP (Delivered Duty Paid):''' Used when the customer chooses to pre-pay import fees and taxes at checkout. We handle all import fees and deliver the goods to the destination address.

* '''DAP (Delivered at Place):''' Used when the customer opts to pay import fees and taxes upon delivery. We deliver the goods, but the customer is responsible for paying any import fees directly to the carrier.

==Product Returns==
===All returns must be authorized by Phidgets Inc.===
Before returning a package {{ContactUs|contact us}} and ask for a Return Merchandise Authorization or RMA number. Once you have received it, put the RMA number on the outside of the packaging as well as the packing slip so that it is possible for us to track what the package is supposed to be. Any merchandise returned without an RMA number clearly visible on the packaging will be charged an administrative fee of $25.00 or the value of the returned product, whichever is less ''if we are able to determine what it is''. In the event we are unable to determine what the package is, it will be refused and returned to the sender.

===Unopened Product===
Phidgets accepts returns of unopened products within 30 days of the date of purchase. To initiate a return, please contact us by phone or email to obtain an RMA number. Products must be shipped back to Phidgets Inc. prepaid. A refund will be issued to your credit card once we receive and inspect the returned items.

Returns received after 30 days are subject to a restocking fee of 25% of the package's value (minimum $5.00, maximum $500).

We do '''not''' accept returns beyond 90 days from the date of purchase.

===Cut to Length===
Unfortunately we cannot accept returns on any items which are cut to custom lengths. This includes: cable, wire, roller chain, linear shaft, rotary shaft, and t-slot extrusions.

===We shipped the wrong/incomplete product===
{{ContactUs|Contact us}}. We will get the correct product sent to you immediately, and will pay all shipping charges.

==Payment Terms==
We accept credit cards, PayPal, and Wire Transfers.

{| style="border:1px solid darkgray;" cellpadding="7px;"
|-style="background: #d1d1d1" align=center
! Payment Method|| Terms
|-
|style="background: #f0f0f0" align=center|Credit Cards
|style="background: #f0f0f0" align=left|Visa, MasterCard, American Express (for order in CAD only)
|-
|style="background: #f0f0f0" align=center|PayPal
|style="background: #f0f0f0" align=left|PayPal is accepted. There are no extra fees for using PayPal
|-
|style="background: #f0f0f0" align=center|Wire Transfers
|style="background: #f0f0f0" align=left|Wire transfers are only accepted for orders over $200.00 USD (excluding shipping charges). There is a $25.00 USD charge for wire transfers under $500.00 USD. Any fees charged by the sending bank are your responsibility.<br />Please make sure that the amount sent to us covers both our invoice and your bank fees. Products are not shipped until the money is deposited in our bank account. We recommend that you e-mail orders@phidgets.com with the amount of the transfer and the invoice you are paying. <br />Any order for which payment is not received within 15 days, will be canceled.
|}

==Security and Privacy==
Phidgets Inc. pledges a safe and worry-free shopping experience. IF you are using the current version of Internet Explorer, on the checkout page where you enter your credit card information, you will notice a a locked padlock icon on the top bar your browser window. If you are using Mozilla Firefox, you will notice a locked padlock icon in the bottom right corner of your browser window. If this icon does not appear, please contact us directly to complete your purchase. These icons tell you that the page you are on is secure. We use Secure Sockets Layer (SSL 128-bit) technology with a digital certificate by GeoTrust, Inc. for Internet security to protect your personal information. This encryption makes it impossible for anyone to read your information in transit. We do not store your credit information and it is deleted once it has been securely transmitted to Moneris for processing.

We use your e-mail address to let you know your shipment's tracking number. Your phone number is required by the Courier Company. We do not sell, rent or give any of your personal information to any unrelated third parties with the exception of Moneris for authorizing credit card payments and the Courier company to let them know where to deliver the shipment and how to contact you if there is any problems.

If you have any questions or concerns about our Security and Privacy policy, call us at 1.403.282.7335 or e-mail us at support@phidgets.com

Phidgets Inc. uses various Google Analytics tools such as conversion tracking in order to improve the effectiveness of the website. These statistics are completely anonymous.

==Holidays==
Phidgets, Inc. will be closed on the following days. During these times, the site will still be accessible and orders can be placed, but they will not ship until the next business day.

{| style="border:1px solid darkgray;" cellpadding="7px;"
|-style="background: #d1d1d1" align=center
! style="text-align:center;"| Holiday
! style="text-align:center;"| Description
! style="text-align:center;"| 2025
! style="text-align:center;"| 2026
|-
|style="background: #f0f0f0" align=center| Alberta Family Day
|style="background: #f0f0f0" align=center| Third Monday in February
|style="background: #f0f0f0" align=center| Feb 17
|style="background: #f0f0f0" align=center| Feb 16
|-
|style="background: #f0f0f0" align=center| Good Friday
|style="background: #f0f0f0" align=center| Friday before Easter Sunday
|style="background: #f0f0f0" align=center| Apr 18
|style="background: #f0f0f0" align=center| Apr 3
|-
|style="background: #f0f0f0" align=center| Victoria Day
|style="background: #f0f0f0" align=center| Monday before May 25
|style="background: #f0f0f0" align=center| May 19
|style="background: #f0f0f0" align=center| May 18
|-
|style="background: #f0f0f0" align=center| Canada Day
|style="background: #f0f0f0" align=center| First day of July (or nearest business day)
|style="background: #f0f0f0" align=center| Jul 1
|style="background: #f0f0f0" align=center| Jul 1
|-
|style="background: #f0f0f0" align=center| Heritage Day
|style="background: #f0f0f0" align=center| First Monday in August
|style="background: #f0f0f0" align=center| Aug 4
|style="background: #f0f0f0" align=center| Aug 3
|-
|style="background: #f0f0f0" align=center| Labour Day
|style="background: #f0f0f0" align=center| First Monday in September
|style="background: #f0f0f0" align=center| Sept 1
|style="background: #f0f0f0" align=center| Sept 7
|-
|style="background: #f0f0f0" align=center| Thanksgiving
|style="background: #f0f0f0" align=center| Second Monday in October
|style="background: #f0f0f0" align=center| Oct 13
|style="background: #f0f0f0" align=center| Oct 12
|-
|style="background: #f0f0f0" align=center| Remembrance Day
|style="background: #f0f0f0" align=center| November 11 (or nearest business day)
|style="background: #f0f0f0" align=center| Nov 11
|style="background: #f0f0f0" align=center| Nov 11
|-
|style="background: #f0f0f0" align=center| Christmas and New Years
|style="background: #f0f0f0" align=center| Varies
|style="background: #f0f0f0" align=center| TBA
|style="background: #f0f0f0" align=center| TBA
|-
|}

Language - C Sharp

2025-06-13T19:47:25Z

Lmpacent: /* Visual Studio Code */

{{#seo:|description=Learn how to use Phidget USB devices with C#.}}
[[Category:Language]]

==Get Started==
With the Phidget22.NET library, it's easy to create C# applications that work with Phidget devices.

==C# Libraries==
===Nuget Package===
The Phidget22.NET library is available as a [https://www.nuget.org/packages/Phidget22.NET/ nuget package]. This is the recommend way to install and manage the Phidget22.NET library.

====macOS Considerations====
Phidget devices running a HID USB stack require the installation of the macOS libraries or the standalone Phidget Control Panel ([{{SERVER}}/docs/OS_-_macOS download here]).

To determine what USB stack your Phidget device is on, navigate to the product page and then to the specification tab, and look for the ''USB Stack'' specification. If you are using a VINT device, navigate to the product page for the VINT Hub you are using.

[[Image:Javascript_networkserver_webusb_spec.png|center|600px|link=https://cdn.phidgets.com/docs/images/8/80/Javascript_networkserver_webusb_spec.png]]

====Linux Considerations====
Linux restricts access to USB devices to the root user. To run your .NET application as a regular user, you'll need to [{{SERVER}}/docs/OS_-_Linux#Setting_udev_Rules set up udev rules] on your system.

===Library Files===
If you would like to manually manage the Phidget22.NET library files, you can download them [https://cdn.phidgets.com/downloads/phidget22/libraries/windows/Phidget22-windevel.zip here].

==Development Environment Configuration==
===Visual Studio===
{| style="margin:auto;" class="table-no-border mw-collapsible mw-collapsed"
|+ '''Instructions'''
| Create your Visual Studio project, and navigate to the '''Solution Explorer'''. From there, right-click on '''Dependencies''' and select '''Manage NuGet Packages...'''|| [[Image:Language_csharp_vs_managenuget.png|center|350px|link=https://cdn.phidgets.com/docs/images/c/cc/Language_csharp_vs_managenuget.png]]
|-
| Next, click '''Browse''' and enter '''Phidget22.NET''' in the search bar. || [[Image:Language_csharp_vs_browsenuget.png|center|350px|link=https://cdn.phidgets.com/docs/images/6/61/Language_csharp_vs_browsenuget.png]]
|-
| Click on the package and press the '''Install''' button. || [[Image:Language_csharp_vs_installnuget.png|center|350px|link=https://cdn.phidgets.com/docs/images/b/b8/Language_csharp_vs_installnuget.png]]
|-
| Finally, add your C# code and run it using the button at the top of the screen. || [[Image:Language_csharp_vs_run.png|center|350px|link=https://cdn.phidgets.com/docs/images/5/5a/Language_csharp_vs_run.png]]
|-
|}

===Visual Studio Code===
{| style="margin:auto;" class="table-no-border mw-collapsible mw-collapsed"
|+ '''Instructions'''
| Install the [https://marketplace.visualstudio.com/items?itemName=ms-dotnettools.csdevkit C# Dev Kit extension for Visual Studio Code].|| [[Image:Language_csharp_vscode_installext.png|center|350px|link=https://cdn.phidgets.com/docs/images/b/b8/Language_csharp_vscode_installext.png]]
|-
| Next, create a directory and open it in Visual Studio Code. You can do this by opening Visual Studio Code and selecting '''File > Open Folder...''' || [[Image:Language_csharp_vscode_newfolder.png|center|350px|link=https://cdn.phidgets.com/docs/images/4/43/Language_csharp_vscode_newfolder.png]]
|-
| Open the Command Palette (Ctrl + Shift + P), type '''.NET: New Project''', and press Enter. A list of supported project types will appear. || [[Image:Language_csharp_vscode_netnewproject.png|center|350px|link=https://cdn.phidgets.com/docs/images/f/f7/Language_csharp_vscode_netnewproject.png]]
|-
| Select your preferred project type from the list. For this example, we will select '''Console App'''. || [[Image:Language_csharp_vscode_netconsoleapp.png|center|350px|link=https://cdn.phidgets.com/docs/images/b/bc/Language_csharp_vscode_netconsoleapp.png]]
|-
| Next, we need to add the Phidget22.NET library using NuGet. Open the Command Palette again (Ctrl + Shift + P), and enter '''NuGet: Add NuGet package...'''.
|| [[Image:Language_csharp_vscode_addnugetpackage.png|center|350px|link=https://cdn.phidgets.com/docs/images/2/26/Language_csharp_vscode_addnugetpackage.png]]
|-
| When prompted, enter '''Phidget22.NET''' and install the latest package.<br><br>'''Note''': Ensure you are downloading the latest version which can be seen [{{SERVER}}/?view=changelog here]. Visual Studio Code may incorrectly show an older version as the ''latest'' by default.|| [[Image:Language_csharp_vscode_phidget22net.png|center|350px|link=https://cdn.phidgets.com/docs/images/d/d5/Language_csharp_vscode_phidget22net.png]]
|-
|-
| Finally, add your C# code and run it using the button at the top of the screen. || [[Image:Language_csharp_vscode_runcodepng.png|center|350px|link=https://cdn.phidgets.com/docs/images/d/dc/Language_csharp_vscode_runcodepng.png]]
|-
|}

===.NET Command-Line Interface (CLI)===
{| style="margin:auto;" class="table-no-border mw-collapsible mw-collapsed"
|+ '''Instructions'''
| Download and install the latest version of.NET from [https://dotnet.microsoft.com/en-us/download/dotnet Microsoft's .NET download page].|| [[Image:Language_csharp_cli_download.png|center|350px|link=https://cdn.phidgets.com/docs/images/9/90/Language_csharp_cli_download.png]]
|-
| Next, open a command prompt or terminal in a new folder and enter the following command:

<syntaxhighlight lang=bash>
dotnet new console
</syntaxhighlight>

|| [[Image:Language_csharp_cli_newconsole.png|center|350px|link=https://cdn.phidgets.com/docs/images/3/3a/Language_csharp_cli_newconsole.png]]
|-
| This previous command will create a new console application at the folder location. || [[Image:Language_csharp_cli_newproject.png|center|350px|link=https://cdn.phidgets.com/docs/images/c/cb/Language_csharp_cli_newproject.png]]
|-
| Navigate back to the command prompt or terminal, and add the Phidget22.NET package with the following command:

<syntaxhighlight lang=bash>
dotnet add package Phidget22.NET
</syntaxhighlight>

|| [[Image:Language_csharp_cli_addpackage.png|center|350px|link=https://cdn.phidgets.com/docs/images/7/78/Language_csharp_cli_addpackage.png]]
|-
| You can now open the '''Program.cs''' file and add your code. Run the program by entering the following command into your command prompt or terminal:

<syntaxhighlight lang=bash>
dotnet run
</syntaxhighlight>

|| [[Image:Language_csharp_cli_runcode.png|center|350px|link=https://cdn.phidgets.com/docs/images/f/f3/Language_csharp_cli_runcode.png]]
|-
|}

==Example Code==
Navigate to our [https://www.phidgets.com/?view=code_samples&lang=CSharp Code Sample Generator] to view and download code samples that are tailored to your specific device.

[[Image:Language_csharp_codesample.png|center|600px|link=https://cdn.phidgets.com/docs/images/0/03/Language_csharp_codesample.png]]

===Phidget Programming Basics===
{{PhidgetProgrammingBasicsLink}}

==API==
[{{SERVER}}/?view=api&lang=CSharp Phidget22 API]

Programming Resources

2025-06-11T19:24:22Z

Lmpacent:

[[Category:Overview]]

We support a variety of programming languages, each with code samples and a detailed API to help you get started. If you're unsure which language to choose, consider [[Language - Python|Python]]. It's easy to set up and beginner friendly.

<div class="LangTableFull">
{|class="table-no-border"
|style="text-align:center;"|[[Image:Logo-Python.png|alt=Python|link=Language - Python|120px]]
|style="text-align:center;"|[[Image:Logo-Javascript.png|alt=JavaScript|link=Language - JavaScript|120px]]
|style="text-align:center;"|[[Image:Logo-CSharp.png|alt=C#|link=Language - C Sharp|120px]]
|style="text-align:center;"|[[Image:Logo-C.png|alt=C|link=Language - C|120px]]
|style="text-align:center;"|[[Image:Logo-Java.png|alt=Java|link=Language - Java|120px]]
|-
|style="text-align:center;"| [[Language - Python|Python]]
|style="text-align:center;"| [[Language - JavaScript|JavaScript]]
|style="text-align:center;"| [[Language - C Sharp|C#]]
|style="text-align:center;"| [[Language - C|C]]
|style="text-align:center;"| [[Language - Java|Java]]
|}
{|class="table-no-border"
|style="text-align:center;"|[[Image:Logo-Swift.png|alt=Swift|link=Language - Swift|120px]]
|style="text-align:center;"|[[Image:Logo-ObjC.png|alt=Objective C|link=Language - Objective C|120px]]
|style="text-align:center;"|[[Image:Logo-VBNet.png|alt=VB|link=Language_-_Visual_Basic|120px]]
|style="text-align:center;"|[[Image:Logo-LabVIEW.png|alt=LabVIEW|link=Language - LabVIEW|120px]]
|style="text-align:center;"|[[Image:Logo-MaxMSP.png|alt=Max|link=Language_-_Max|120px]]
|-
|style="text-align:center;"| [[Language - Swift|Swift]]
|style="text-align:center;"| [[Language - Objective C|Objective C]]
|style="text-align:center;"| [[Language - Visual Basic|VB]]
|style="text-align:center;"| [[Language - LabVIEW|LabVIEW]]
|style="text-align:center;"| [[Language_-_Max|Max]]
|}
</div>
<div class="LangTableSmall">
{|class="table-no-border"
|style="width:50px;"|[[Image:Logo-C.png|alt=C|link=Language - C|30px]]||[[Language - C|C]]
|-
|[[Image:Logo-CSharp.png|alt=C#|link=Language - C Sharp|30px]]||[[Language - C Sharp|C#]]
|-
|[[Image:Logo-Python.png|alt=Python|link=Language - Python|30px]]||[[Language - Python|Python]]
|-
|[[Image:Logo-Java.png|alt=Java|link=Language - Java|30px]]||[[Language - Java|Java]]
|-
|[[Image:Logo-Javascript.png|alt=JavaScript|link=Language - JavaScript|30px]]||[[Language - JavaScript|JavaScript]]
|-
|[[Image:Logo-Swift.png|alt=Swift|link=Language - Swift|30px]]||[[Language - Swift|Swift]]
|-
|[[Image:Logo-ObjC.png|alt=Objective C|link=Language - Objective C|30px]]||[[Language - Objective C|Objective C]]
|-
|style="width:50px;"|[[Image:Logo-VBNet.png|alt=VB|link=Language_-_Visual_Basic|30px]]||[[Language - Visual Basic|VB]]
|-
|[[Image:Logo-LabVIEW.png|alt=LabVIEW|link=Language - LabVIEW|30px]]||[[Language - LabVIEW|LabVIEW]]
|-
|[[Image:Logo-MaxMSP.png|alt=Max|link=Language_-_Max|30px]]||[[Language_-_Max|Max]]
|}
</div>

Programming Resources

2025-06-11T19:22:11Z

Lmpacent:

[[Category:Overview]]

We support a variety of programming languages, each with code samples and a detailed API to help you get started. If you're unsure which language to choose, consider [[Language - Python|Python]]. It's easy to set up and beginner friendly.

<div class="LangTableFull">
{|class="table-no-border"
|style="text-align:center;"|[[Image:Logo-C.png|alt=C|link=Language - C|120px]]
|style="text-align:center;"|[[Image:Logo-CSharp.png|alt=C#|link=Language - C Sharp|120px]]
|style="text-align:center;"|[[Image:Logo-Python.png|alt=Python|link=Language - Python|120px]]
|style="text-align:center;"|[[Image:Logo-Java.png|alt=Java|link=Language - Java|120px]]
|style="text-align:center;"|[[Image:Logo-Javascript.png|alt=JavaScript|link=Language - JavaScript|120px]]
|-
|style="text-align:center;"| [[Language - C|C]]
|style="text-align:center;"| [[Language - C Sharp|C#]]
|style="text-align:center;"| [[Language - Python|Python]]
|style="text-align:center;"| [[Language - Java|Java]]
|style="text-align:center;"| [[Language - JavaScript|JavaScript]]
|}
{|class="table-no-border"
|style="text-align:center;"|[[Image:Logo-Swift.png|alt=Swift|link=Language - Swift|120px]]
|style="text-align:center;"|[[Image:Logo-ObjC.png|alt=Objective C|link=Language - Objective C|120px]]
|style="text-align:center;"|[[Image:Logo-VBNet.png|alt=VB|link=Language_-_Visual_Basic|120px]]
|style="text-align:center;"|[[Image:Logo-LabVIEW.png|alt=LabVIEW|link=Language - LabVIEW|120px]]
|style="text-align:center;"|[[Image:Logo-MaxMSP.png|alt=Max|link=Language_-_Max|120px]]
|-
|style="text-align:center;"| [[Language - Swift|Swift]]
|style="text-align:center;"| [[Language - Objective C|Objective C]]
|style="text-align:center;"| [[Language - Visual Basic|VB]]
|style="text-align:center;"| [[Language - LabVIEW|LabVIEW]]
|style="text-align:center;"| [[Language_-_Max|Max]]
|}
</div>
<div class="LangTableSmall">
{|class="table-no-border"
|style="width:50px;"|[[Image:Logo-C.png|alt=C|link=Language - C|30px]]||[[Language - C|C]]
|-
|[[Image:Logo-CSharp.png|alt=C#|link=Language - C Sharp|30px]]||[[Language - C Sharp|C#]]
|-
|[[Image:Logo-Python.png|alt=Python|link=Language - Python|30px]]||[[Language - Python|Python]]
|-
|[[Image:Logo-Java.png|alt=Java|link=Language - Java|30px]]||[[Language - Java|Java]]
|-
|[[Image:Logo-Javascript.png|alt=JavaScript|link=Language - JavaScript|30px]]||[[Language - JavaScript|JavaScript]]
|-
|[[Image:Logo-Swift.png|alt=Swift|link=Language - Swift|30px]]||[[Language - Swift|Swift]]
|-
|[[Image:Logo-ObjC.png|alt=Objective C|link=Language - Objective C|30px]]||[[Language - Objective C|Objective C]]
|-
|style="width:50px;"|[[Image:Logo-VBNet.png|alt=VB|link=Language_-_Visual_Basic|30px]]||[[Language - Visual Basic|VB]]
|-
|[[Image:Logo-LabVIEW.png|alt=LabVIEW|link=Language - LabVIEW|30px]]||[[Language - LabVIEW|LabVIEW]]
|-
|[[Image:Logo-MaxMSP.png|alt=Max|link=Language_-_Max|30px]]||[[Language_-_Max|Max]]
|}
</div>

Language - C Sharp

2025-06-11T19:10:29Z

Lmpacent:

{{#seo:|description=Learn how to use Phidget USB devices with C#.}}
[[Category:Language]]

==Get Started==
With the Phidget22.NET library, it's easy to create C# applications that work with Phidget devices.

==C# Libraries==
===Nuget Package===
The Phidget22.NET library is available as a [https://www.nuget.org/packages/Phidget22.NET/ nuget package]. This is the recommend way to install and manage the Phidget22.NET library.

====macOS Considerations====
Phidget devices running a HID USB stack require the installation of the macOS libraries or the standalone Phidget Control Panel ([{{SERVER}}/docs/OS_-_macOS download here]).

To determine what USB stack your Phidget device is on, navigate to the product page and then to the specification tab, and look for the ''USB Stack'' specification. If you are using a VINT device, navigate to the product page for the VINT Hub you are using.

[[Image:Javascript_networkserver_webusb_spec.png|center|600px|link=https://cdn.phidgets.com/docs/images/8/80/Javascript_networkserver_webusb_spec.png]]

====Linux Considerations====
Linux restricts access to USB devices to the root user. To run your .NET application as a regular user, you'll need to [{{SERVER}}/docs/OS_-_Linux#Setting_Udev_Rules set up udev rules] on your system.

===Library Files===
If you would like to manually manage the Phidget22.NET library files, you can download them [https://cdn.phidgets.com/downloads/phidget22/libraries/windows/Phidget22-windevel.zip here].

==Development Environment Configuration==
===Visual Studio===
{| style="margin:auto;" class="table-no-border mw-collapsible mw-collapsed"
|+ '''Instructions'''
| Create your Visual Studio project, and navigate to the '''Solution Explorer'''. From there, right-click on '''Dependencies''' and select '''Manage NuGet Packages...'''|| [[Image:Language_csharp_vs_managenuget.png|center|350px|link=https://cdn.phidgets.com/docs/images/c/cc/Language_csharp_vs_managenuget.png]]
|-
| Next, click '''Browse''' and enter '''Phidget22.NET''' in the search bar. || [[Image:Language_csharp_vs_browsenuget.png|center|350px|link=https://cdn.phidgets.com/docs/images/6/61/Language_csharp_vs_browsenuget.png]]
|-
| Click on the package and press the '''Install''' button. || [[Image:Language_csharp_vs_installnuget.png|center|350px|link=https://cdn.phidgets.com/docs/images/b/b8/Language_csharp_vs_installnuget.png]]
|-
| Finally, add your C# code and run it using the button at the top of the screen. || [[Image:Language_csharp_vs_run.png|center|350px|link=https://cdn.phidgets.com/docs/images/5/5a/Language_csharp_vs_run.png]]
|-
|}

===Visual Studio Code===
{| style="margin:auto;" class="table-no-border mw-collapsible mw-collapsed"
|+ '''Instructions'''
| Install the [https://marketplace.visualstudio.com/items?itemName=ms-dotnettools.csdevkit C# Dev Kit extension for Visual Studio Code].|| [[Image:Language_csharp_vscode_installext.png|center|350px|link=https://cdn.phidgets.com/docs/images/b/b8/Language_csharp_vscode_installext.png]]
|-
| Next, create a directory and open it in Visual Studio Code. You can do this by opening Visual Studio Code and selecting '''File > Open Folder...''' || [[Image:Language_csharp_vscode_newfolder.png|center|350px|link=https://cdn.phidgets.com/docs/images/4/43/Language_csharp_vscode_newfolder.png]]
|-
| Open the Command Palette (Ctrl + Shift + P), type '''.NET: New Project''', and press Enter. A list of supported project types will appear. || [[Image:Language_csharp_vscode_netnewproject.png|center|350px|link=https://cdn.phidgets.com/docs/images/f/f7/Language_csharp_vscode_netnewproject.png]]
|-
| Select your preferred project type from the list. For this example, we will select '''Console App'''. || [[Image:Language_csharp_vscode_netconsoleapp.png|center|350px|link=https://cdn.phidgets.com/docs/images/b/bc/Language_csharp_vscode_netconsoleapp.png]]
|-
| Next, we need to add the Phidget22.NET library using NuGet. Open the Command Palette again (Ctrl + Shift + P), and enter '''NuGet: Add NuGet package...'''.
|| [[Image:Language_csharp_vscode_addnugetpackage.png|center|350px|link=https://cdn.phidgets.com/docs/images/2/26/Language_csharp_vscode_addnugetpackage.png]]
|-
| When prompted, enter '''Phidget22.NET''' and install the package.|| [[Image:Language_csharp_vscode_phidget22net.png|center|350px|link=https://cdn.phidgets.com/docs/images/d/d5/Language_csharp_vscode_phidget22net.png]]
|-
|-
| Finally, add your C# code and run it using the button at the top of the screen. || [[Image:Language_csharp_vscode_runcodepng.png|center|350px|link=https://cdn.phidgets.com/docs/images/d/dc/Language_csharp_vscode_runcodepng.png]]
|-
|}

===.NET Command-Line Interface (CLI)===
{| style="margin:auto;" class="table-no-border mw-collapsible mw-collapsed"
|+ '''Instructions'''
| Download and install the latest version of.NET from [https://dotnet.microsoft.com/en-us/download/dotnet Microsoft's .NET download page].|| [[Image:Language_csharp_cli_download.png|center|350px|link=https://cdn.phidgets.com/docs/images/9/90/Language_csharp_cli_download.png]]
|-
| Next, open a command prompt or terminal in a new folder and enter the following command:

<syntaxhighlight lang=bash>
dotnet new console
</syntaxhighlight>

|| [[Image:Language_csharp_cli_newconsole.png|center|350px|link=https://cdn.phidgets.com/docs/images/3/3a/Language_csharp_cli_newconsole.png]]
|-
| This previous command will create a new console application at the folder location. || [[Image:Language_csharp_cli_newproject.png|center|350px|link=https://cdn.phidgets.com/docs/images/c/cb/Language_csharp_cli_newproject.png]]
|-
| Navigate back to the command prompt or terminal, and add the Phidget22.NET package with the following command:

<syntaxhighlight lang=bash>
dotnet add package Phidget22.NET
</syntaxhighlight>

|| [[Image:Language_csharp_cli_addpackage.png|center|350px|link=https://cdn.phidgets.com/docs/images/7/78/Language_csharp_cli_addpackage.png]]
|-
| You can now open the '''Program.cs''' file and add your code. Run the program by entering the following command into your command prompt or terminal:

<syntaxhighlight lang=bash>
dotnet run
</syntaxhighlight>

|| [[Image:Language_csharp_cli_runcode.png|center|350px|link=https://cdn.phidgets.com/docs/images/f/f3/Language_csharp_cli_runcode.png]]
|-
|}

==Example Code==
Navigate to our [https://www.phidgets.com/?view=code_samples&lang=CSharp Code Sample Generator] to view and download code samples that are tailored to your specific device.

[[Image:Language_csharp_codesample.png|center|600px|link=https://cdn.phidgets.com/docs/images/0/03/Language_csharp_codesample.png]]

===Phidget Programming Basics===
{{PhidgetProgrammingBasicsLink}}

==API==
[{{SERVER}}/?view=api&lang=CSharp Phidget22 API]