Phidgets Support - User contributions [en]

Terms and Conditions

2025-07-31T13:18:10Z

Burley:

[[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;"| 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-01-09T15:19:08Z

Burley:

[[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===
Unless we are unusually busy most orders received before 12:00 PM Mountain Time - Canada (GMT-07:00) Monday to Friday will be shipped on the same day.

Orders which contain cut to length parts may not necessarily ship same day as there is significant processing time associated with these orders.

===Shipping Costs===
The shipping cost is calculated at Checkout and submitted for your review before you confirm your order. When multiple shipping options are available for your destination, we will list all available options and let you choose.

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

If you have your own account with UPS, you can use it and be billed directly by them. In that case you have more shipping options available to you.

===Shipping in Canada===
We use UPS Express Saver™ - Overnight delivery, and UPS Standard - 3 to 5 business days ground delivery.

===Shipping to the EU===

Effective July 1, 2021, there were significant changes to the European Union’s Value Added Tax (VAT) rules.

# All goods will now require formal customs clearance and are now subject to the VAT related to the country of entry.
# Online market places are required to charge the VAT upfront for all goods valued intrinsically up to '''€150'''.

These requirements prevent Phidgets Inc. from shipping directly into the EU for goods less than this value.

EU customers ordering goods on our website with a total value less the '''$200 USD''' are now encouraged to either:
* Increase the value of their order to over '''$200 USD''' or,
* Follow the link to our [[Dealers|distributors]] page and place an order through them.

Customers within the EU can still place orders above $200USD and have them shipped directly to them within
the EU without going through a distributor.
Please note in these cases customers within the EU are responsible for the VAT. UPS will collect it upon delivery or by invoice after delivery.

===Shipping to the United States===

====UPS Express Saver™ - Overnight====

'''Shipments under $800.00USD''': we pay all costs in bringing the goods to you including import duties and taxes. In other words your shipping costs are what we put on our invoice. Contact us if you are getting any extra invoices from UPS.

'''Shipments over $800.00USD''': you are responsible for duty and taxes if applicable and will have to pay UPS directly on top of the shipping cost we put on our invoice.

====UPS Standard - Ground 3 to 5 business days====
'''Shipments under $800.00USD''': we pay all costs in bringing the goods to you including import duties and taxes. In other words your shipping costs are what we put on our invoice. Contact us if you are getting any extra invoices from UPS.

'''Shipment over $800.00USD''' UPS will collect Entry Preparation Fees directly from you when delivering the package, and for duty and taxes if applicable.

:'''Entry Preparation Fees'''
:*All rates are in U.S. funds
:*Rates do not include applicable duties or taxes

{| style="border:1px solid darkgray;" cellpadding="7px;"
|-style="background: #d1d1d1" align=center
! Value for duty|| UPS Standard Service
|-
|style="background: #f0f0f0" align=center|$0.00 to $800.00
|style="background: #f0f0f0" align=center|No Charge
|-
|style="background: #f0f0f0" align=center|$800.01 to $1,250.00
|style="background: #f0f0f0" align=center|$28.75
|-
|style="background: #f0f0f0" align=center|$1,250.01 to $2,500.00
|style="background: #f0f0f0" align=center|$40.50
|-
|style="background: #f0f0f0" align=center|Each Additional $1,000.00
|style="background: #f0f0f0" align=center|$1.95
|}

===International Shipments===
We use UPS Worldwide Express Saver™, and UPS Worldwide Expedited for international locations that cannot be reached with Express Saver.

Goods shipped to an international destination may be subject to import duties and taxes, which are levied once the goods reach your country. Additional charges for customs clearance must be borne by you; we have no control over these charges and cannot predict what they may be. Since customs policies vary widely from country to country, you should contact your local customs office for further information.

===Tracking your order===
You can track your shipment by going to www.UPS.ca and using the tracking number that was e-mailed to you when your order 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, when the package arrives there is no one to accept delivery UPS will redeliver 2 more times. This is standard UPS protocol. If delivery fails they will keep the package for 5 days and then return it to us. We will then refund you the cost you paid minus the cost of shipping (both directions) and a flat $50 charge to a maximum of the total cost of the package. This applies to packages which failed delivery due to no one being present as well as packages which were refused delivery by a person at the delivery location.

===Import Restrictions to Russia===
If you are wanting to ship an order to Russia you MUST have a valid business license number in order to complete the shipment. This must be added to your account on our website. To modify the business number, you can go to your account page and edit the "Account Information" section. This number will then be applied to all orders placed with that account. The reason for this is best explained by UPS:

"Customs authorities in Russia have tightened restrictions on import shipments to Russia, in particular on dutiable shipments sent to private individuals. These shipments are currently under extraordinary scrutiny in an effort to improve accuracy of the accompanying shipping documentation. These additional requirements lead to an unprecedented number of customs holds and delays in delivery. UPS has therefore temporarily suspended the acceptance of dutiable shipments sent to private individuals in Russia until further notice. We regret this step and are confident that, together with the Russian customs authorities, a solution can be found. UPS continues to accept all non-dutiable document shipments to private individuals in Russia and all commercial shipments addressed to businesses." [http://www.ups.com/content/hr/en/about/news/service_updates/20100526_restrictions.html]

==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 will take back any unopened product for a period of 30 days from the date of purchase. Just call or e-mail us for a RMA number and ship the product back to Phidgets prepaid and we will refund your credit card as soon as we receive and inspect the returned goods.

Products that are returned after 30 days are subject to a re-stocking charge of 25% of the package's value (minimum $5.00) to a maximum of $500.

We do '''not''' accept returns after 90 days.

===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

2023-08-03T15:12:02Z

Burley:

[[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===
Unless we are unusually busy most orders received before 12:00 PM Mountain Time - Canada (GMT-07:00) Monday to Friday will be shipped on the same day.

Orders which contain cut to length parts may not necessarily ship same day as there is significant processing time associated with these orders.

===Shipping Costs===
The shipping cost is calculated at Checkout and submitted for your review before you confirm your order. When multiple shipping options are available for your destination, we will list all available options and let you choose.

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

If you have your own account with UPS, you can use it and be billed directly by them. In that case you have more shipping options available to you.

===Shipping in Canada===
We use UPS Express Saver™ - Overnight delivery, and UPS Standard - 3 to 5 business days ground delivery.

===Shipping to the EU===

Effective July 1, 2021, there were significant changes to the European Union’s Value Added Tax (VAT) rules.

# All goods will now require formal customs clearance and are now subject to the VAT related to the country of entry.
# Online market places are required to charge the VAT upfront for all goods valued intrinsically up to '''€150'''.

These requirements prevent Phidgets Inc. from shipping directly into the EU for goods less than this value.

EU customers ordering goods on our website with a total value less the '''$200 USD''' are now encouraged to either:
* Increase the value of their order to over '''$200 USD''' or,
* Follow the link to our [[Dealers|distributors]] page and place an order through them.

Customers within the EU can still place orders above $200USD and have them shipped directly to them within
the EU without going through a distributor.
Please note in these cases customers within the EU are responsible for the VAT. UPS will collect it upon delivery or by invoice after delivery.

===Shipping to the United States===

====UPS Express Saver™ - Overnight====

'''Shipments under $800.00USD''': we pay all costs in bringing the goods to you including import duties and taxes. In other words your shipping costs are what we put on our invoice. Contact us if you are getting any extra invoices from UPS.

'''Shipments over $800.00USD''': you are responsible for duty and taxes if applicable and will have to pay UPS directly on top of the shipping cost we put on our invoice.

====UPS Standard - Ground 3 to 5 business days====
'''Shipments under $800.00USD''': we pay all costs in bringing the goods to you including import duties and taxes. In other words your shipping costs are what we put on our invoice. Contact us if you are getting any extra invoices from UPS.

'''Shipment over $800.00USD''' UPS will collect Entry Preparation Fees directly from you when delivering the package, and for duty and taxes if applicable.

:'''Entry Preparation Fees'''
:*All rates are in U.S. funds
:*Rates do not include applicable duties or taxes

{| style="border:1px solid darkgray;" cellpadding="7px;"
|-style="background: #d1d1d1" align=center
! Value for duty|| UPS Standard Service
|-
|style="background: #f0f0f0" align=center|$0.00 to $800.00
|style="background: #f0f0f0" align=center|No Charge
|-
|style="background: #f0f0f0" align=center|$800.01 to $1,250.00
|style="background: #f0f0f0" align=center|$28.75
|-
|style="background: #f0f0f0" align=center|$1,250.01 to $2,500.00
|style="background: #f0f0f0" align=center|$40.50
|-
|style="background: #f0f0f0" align=center|Each Additional $1,000.00
|style="background: #f0f0f0" align=center|$1.95
|}

===International Shipments===
We use UPS Worldwide Express Saver™, and UPS Worldwide Expedited for international locations that cannot be reached with Express Saver.

Goods shipped to an international destination may be subject to import duties and taxes, which are levied once the goods reach your country. Additional charges for customs clearance must be borne by you; we have no control over these charges and cannot predict what they may be. Since customs policies vary widely from country to country, you should contact your local customs office for further information.

===Tracking your order===
You can track your shipment by going to www.UPS.ca and using the tracking number that was e-mailed to you when your order 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, when the package arrives there is no one to accept delivery UPS will redeliver 2 more times. This is standard UPS protocol. If delivery fails they will keep the package for 5 days and then return it to us. We will then refund you the cost you paid minus the cost of shipping (both directions) and a flat $50 charge to a maximum of the total cost of the package. This applies to packages which failed delivery due to no one being present as well as packages which were refused delivery by a person at the delivery location.

===Import Restrictions to Russia===
If you are wanting to ship an order to Russia you MUST have a valid business license number in order to complete the shipment. This must be added to your account on our website. To modify the business number, you can go to your account page and edit the "Account Information" section. This number will then be applied to all orders placed with that account. The reason for this is best explained by UPS:

"Customs authorities in Russia have tightened restrictions on import shipments to Russia, in particular on dutiable shipments sent to private individuals. These shipments are currently under extraordinary scrutiny in an effort to improve accuracy of the accompanying shipping documentation. These additional requirements lead to an unprecedented number of customs holds and delays in delivery. UPS has therefore temporarily suspended the acceptance of dutiable shipments sent to private individuals in Russia until further notice. We regret this step and are confident that, together with the Russian customs authorities, a solution can be found. UPS continues to accept all non-dutiable document shipments to private individuals in Russia and all commercial shipments addressed to businesses." [http://www.ups.com/content/hr/en/about/news/service_updates/20100526_restrictions.html]

==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 will take back any unopened product for a period of 30 days from the date of purchase. Just call or e-mail us for a RMA number and ship the product back to Phidgets prepaid and we will refund your credit card as soon as we receive and inspect the returned goods.

Products that are returned after 30 days are subject to a re-stocking charge of 25% of the package's value (minimum $5.00) to a maximum of $500.

We do '''not''' accept returns after 90 days.

===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;"| 2023
! style="text-align:center;"| 2024
|-
|style="background: #f0f0f0" align=center| Alberta Family Day
|style="background: #f0f0f0" align=center| Third Monday in February
|style="background: #f0f0f0" align=center| Feb 20
|style="background: #f0f0f0" align=center| Feb 19
|-
|style="background: #f0f0f0" align=center| Good Friday
|style="background: #f0f0f0" align=center| Friday before Easter Sunday
|style="background: #f0f0f0" align=center| Apr 7
|style="background: #f0f0f0" align=center| March 29
|-
|style="background: #f0f0f0" align=center| Victoria Day
|style="background: #f0f0f0" align=center| Monday before May 25
|style="background: #f0f0f0" align=center| May 22
|style="background: #f0f0f0" align=center| May 20
|-
|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 3
|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 7
|style="background: #f0f0f0" align=center| Aug 5
|-
|style="background: #f0f0f0" align=center| Labour Day
|style="background: #f0f0f0" align=center| First Monday in September
|style="background: #f0f0f0" align=center| Sept 4
|style="background: #f0f0f0" align=center| Sept 2
|-
|style="background: #f0f0f0" align=center| Thanksgiving
|style="background: #f0f0f0" align=center| Second Monday in October
|style="background: #f0f0f0" align=center| Oct 16
|style="background: #f0f0f0" align=center| Oct 14
|-
|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
|-
|}

Phidget Manager

2022-03-24T16:41:16Z

Burley:

[[Category:Overview]]
==General Overview==

The Phidget Manager is an interface into the device channels available to the Phidget library. The API is strictly asynchronous, and continuously monitors channels as they attach and detach.

Each Phidget exports one or more device channels, and when a Phidget is plugged into a system (or becomes available over the network), a manager attach event is fired for each channel available from the Phidget. When the Phidget is removed from the system, a manger detach event is fired for each channel that is no longer available.

It is important to understand the concepts of '''attach''' and '''detach''' as the they relate to the manager. A manager attach does not imply that a user channel has attached to a device channel, but that the device channel has ''appeared'', and the device channel is now ready to be attached to a user channel. When a user channel closes and detaches from a device channel, a manager event is not fired. A manager '''detach''' event is fired when the Phidget is removed from the system.

==Purpose==

The primary function of a Phidget Manager is to fire an attach event for each new device channel when a Phidget becomes available to a system, and to fire a detach event for each device channel that is no longer available when the Phidget is removed from the system. For example, when a 1044_0 - PhidgetSpatial is connected, a Phidget Manager would fire three attach events, one for each device channel, as illustrated below:

[[Image:manager22.jpg|link=|850px|alt=]]

==Using the Phidget Manager==

Much like a Phidget channel, a Phidget Manager must be created and opened. Refer to the {{Phidget22API}} for details.

As soon as a manager is opened the Phidget library will fire an event for each device channel that is currently know to the system. After those initial events, '''attach''' and '''detach''' events will be fired when new Phidgets become available or existing Phidget are removed.

In the C programming language, it is not safe to refer to a {{Code|PhidgetHandle}} after an event handler returns, unless {{Code|Phidget_retain()}} is first called ({{Code|Phidget_open()}} and {{Code|Phidget_close()}} retain and release handlers automatically). The {{Code|PhidgetHandle}} must be released with {{Code|Phidget_release()}} if it has been retained. The object oriented languages supported in the {{Phidget22API}} automatically retain and release handles.

What follows is an example of how to use a manager in C:

<div class="source">
<syntaxhighlight lang=c>

static void CCONV
mgrAttachHandler(PhidgetManagerHandle mgr, void *ctx, PhidgetHandle mgrch) {

PhidgetLog_log("%P attached", mgrch);
}

static void CCONV
mgrDetachHandler(PhidgetManagerHandle mgr, void *ctx, PhidgetHandle mgrch) {

PhidgetLog_log("%P detached", mgrch);
}

int
main(int argc, char **argv) {
PhidgetManagerHandle mgr;

PhidgetManager_create(&mgr);

PhidgetManager_setOnAttachHandler(mgr, mgrAttachHandler, NULL);
PhidgetManager_setOnDetachHandler(mgr, mgrDetachHandler, NULL);

PhidgetManager_open(mgr);

/* Do something long running, like run a GUI threads */

/* Now close and delete the manager */
PhidgetManager_close(mgr);
PhidgetManager_delete(&mgr);
exit(0);
}
</syntaxhighlight>
</div>

A further example would be "HelloWorld" for most [[Programming_Resources|supported languages]] uses the Phidget Manager.

==Opening a Manager Channel==

A manager channel passed to a Phidget Manager attach handler is assigned all of the matching parameters for the Phidget device and the device channel the manager channel refers to; however, the manager channel is not attached to the device channel, and is not receiving data and status information from the device.

User code may {{Code|Open()}} a manager channel, and just like a channel created by the user code, the Phidget library will begin trying to match the manager channel with a device channel. User code may also set attach and detach handlers on the manager channel, and set change event handlers. The manager channel can be treated exactly the same as a user channel.

Operating System Support

2021-11-26T15:38:38Z

Burley: updated windows support

[[Category:Overview]]
We provide support for all major operating systems. Select your operating system from the table below and follow the ''Getting Started'' guide in order to set up your machine. If you need to access non-current versions of our drivers you can find them [{{SERVER}}/downloads/phidget22/libraries/ here]. You can find the driver changelog [{{SERVER}}/?view=changelog here].

{| style="border:1px solid darkgray;" cellpadding="7px;"
|-style="background: #f0f0f0" align=center
! Operating System || Drivers and Libraries || Direct USB Control || Remote Network Control || Supported Version
|-

|colspan="5"|'''Desktop OSes'''
|-

|[[Image:Icon-Windows.png|alt=OS - Windows|24x24px|link=OS - Windows]][[OS - Windows|Windows]]
|style="background: #f0f0ff" align=center| [[OS - Windows#Quick Downloads|Quick Downloads]]
|style="background: #ade6ab" align=center| [[Image:Checkmark.png|link=]]
|style="background: #ade6ab" align=center| [[Image:Checkmark.png|link=]]
| Windows 8 or Newer
|-

|[[Image:Icon-Mac-OS.png|alt=OS - macOS|24x24px|link=OS - macOS]][[OS - macOS|macOS]]
|style="background: #f0f0ff" align=center| [[OS - macOS#Quick Downloads|Quick Downloads]]
|style="background: #ade6ab" align=center| [[Image:Checkmark.png|link=]]
|style="background: #ade6ab" align=center| [[Image:Checkmark.png|link=]]
| OS X 10.5 or newer
|-

|[[Image:Icon-Linux.png|alt=OS - Linux|24x24px|link=OS - Linux]][[OS - Linux|Linux]]
|style="background: #f0f0ff" align=center| [[OS - Linux#Quick Downloads|Quick Downloads]]
|style="background: #ade6ab" align=center| [[Image:Checkmark.png|link=]]
|style="background: #ade6ab" align=center| [[Image:Checkmark.png|link=]]
| Kernel 2.6 or newer
|-

|colspan="5"|'''Mobile/Wireless OSes'''
|-

|[[Image:Icon-Phidgets.png|alt=OS - Phidget SBC|24x24px|link=OS - Phidget SBC]][[OS - Phidget SBC|Phidget SBC]]
|style="background: #f0f0ff" align=center| [[OS - Phidget SBC#Quick Downloads|Quick Downloads]]
|style="background: #ade6ab" align=center| [[Image:Checkmark.png|link=]]
|style="background: #ade6ab" align=center| [[Image:Checkmark.png|link=]]
| All versions
|-

|[[Image:Icon-iOS.png|alt=OS - iOS|link=OS - iOS|24x24px]][[OS - iOS|iOS]]
|style="background: #f0f0ff" align=center| [[OS - iOS#Quick Downloads|Quick Downloads]]
|style="background: #E28585" align=center| X
|style="background: #ade6ab" align=center| [[Image:Checkmark.png|link=]]
| 8.0 or newer
|-

|[[Image:Icon-Android.png|alt=OS - Android|24x24px|link=OS_-_Android]] [[OS_-_Android|Android]]
|style="background: #f0f0ff" align=center| [[OS_-_Android#Quick Downloads|Quick Downloads]]
|style="background: #ade6ab" align=center| [[Image:Checkmark.png|link=]]
|style="background: #ade6ab" align=center| [[Image:Checkmark.png|link=]]
| 4.1 (Jellybean) or newer
|}

Phidget Dictionary

2019-03-06T17:53:09Z

Burley:

[[Category:Overview]]
==General Overview==

[[Image:Dictionary-networkserver.jpg|600px|link=|alt=]]

The Dictionary is a Phidget channel class that exports a key-value pair database. Dictionaries are created and made accessible by the [[Phidget Network Server]]. A Dictionary channel is created and opened like any other Phidget channel. Matching is done using either the serial number or the label assigned to the dictionary.

The backing pseudo-device that exports the Dictionary device channel is maintained by the [[Phidget Network Server]], and is created when the server starts. When the server exits, the pseudo-device is deleted, and any changes made to a dictionary are lost.

The basic functionality of a Dictionary is to maintain configuration information in a central location. Multiple clients can attach to the same dictionary, and set handlers for ''add'', ''update'' and ''delete'' events, making the dictionary useful for monitoring and communicating state.

==Creating a Dictionary==
Dictionaries are managed by the [[Phidget Network Server]]. To create a dictionary, go to the [[Phidget Control Panel]] and click on the '''Network Server''' tab. There are options to create and manage dictionaries. The server must be enabled for clients to access dictionaries.

On Linux, refer to the README for information on how to enable the dictionary feature in the [[Phidget Network Server]], and for the syntax of dictionary configuration files.

==Using The Dictionary==

To access a dictionary, create a channel, set the serial number or the label, and open the channel.
To "listen" for changes to the Dictionary, {{Code|onAdd()}}, {{Code|onRemove()}}, and {{Code|onUpdate()}} event handlers can be set. Refer to the {{Phidget22API}} to see the methods supported by Dictionary.

Here's an example of how you might use the dictionary in a C program:

<div class="source">
<syntaxhighlight lang=c>

PhidgetDictionaryHandle dict;
char val[32];

PhidgetDictionary_create(&dict);

// Open connection to the dictionary using the serial number
Phidget_setDeviceSerialNumber(dict, 5000);
Phidget_open(dict);

PhidgetDictionary_add(dict, "my_key", "my_value"); // add a key that does not already exist
PhidgetDictionary_get(dict, "my_key", val, sizeof (val)); // get the value back
printf("Value: %s\n",newValue);

PhidgetDictionary_remove(dict, "my_key"); // remove the key

Phidget_close(dict);
PhidgetDictionary_delete(&dict);

</syntaxhighlight>
</div>

==Notes==

A common mistake is to assume an event will be delivered to the channel that triggered the event. This is not the case. For example, when a channel adds a key, that channel's add event handler is not called.

It is an error to {{Code|Add()}} a key that already exists in the dictionary. {{Code|Set()}} should be used to update existing keys, creating the key if it does not already exist.

There is no way to directly list all of the keys in a dictionary. The {{Code|Scan()}} method allows code to access the existing keys, but only returns the number of keys that can be held in a limited sized buffer. This interface was chosen as the dictionary could contain more keys than could reasonably be returned in a single network request.

Phidget Dictionary

2019-03-06T17:50:38Z

Burley:

Handling Errors and Logging

2019-03-06T17:35:57Z

Burley:

[[Category:Programming]]{{Recommended_Flow_Links|{{Flow Page Number|{{PAGENAME}} }} }}
__NOTOC__
You've written your code, fixed the compiler errors, and yet, the program still isn't behaving as intended. The tools described on this page will help you further debug your program and figure out where in the code things are going wrong.

==Errors and Error Events==

The Phidget library uses errors and error events to communicate information about potential problems in your program. These can happen in-line in the form of an exception or error code (which generally indicate a problem in the code), and as Error Events (which generally indicate a problem with the Phidget's environment).

===Errors from Function Calls===

When a call to a Phidgets function fails it will throw an exception (or return an error code, depending on the language). It is important to check each function call for errors, and to catch and handle any errors.

Common causes of this type of error are the Phidget not being attached, or one of the values provided to the function being outside the valid range.

You can handle exceptions and return codes as follows:

<tabber>
Python=<syntaxhighlight lang=python>
try:
ch.openWaitForAttachment(5000);
except PhidgetException as e:
print("Failed to open: " + e.details)
</syntaxhighlight>
|-|
Java=<syntaxhighlight lang=java>
try {
ch.open(5000);
} catch (PhidgetException ex) {
System.out.println("Failed to open: " + ex.getMessage());
}
</syntaxhighlight>
|-|
C#=<syntaxhighlight lang=cSharp>
try
{
ch.Open(); //open the device
}
catch (PhidgetException ex)
{
Console.WriteLine("Failed to open: " + ex.Description)
}
</syntaxhighlight>
|-|
C=<syntaxhighlight lang=c>
PhidgetDigitalInputHandle ch;
PhidgetReturnCode res;
...
res = Phidget_openWaitForAttachment((PhidgetHandle)ch, 5000);
if (res != EPHIDGET_OK) {
char* desc;
Phidget_getErrorDescription(res, &desc);
printf("Failed to open: (%d) %s\n", res, desc);
}
</syntaxhighlight>
</tabber>

The consequences of not handling errors correctly ranges from improper behavior, to the program crashing due to an unhandled exception. Programs should check for errors on each function call, and handle any errors.

====Error Codes====

A list of error codes can be found in the {{Phidget22API}}.

===Error Events===

Error events are asynchronously generated by Phidget devices, and by the Phidget library itself.

These do not necessarily indicate a problem with your program, and often serve as a status update from your device that your program should know. For example, a DistanceSensor might send an OutOfRange error if it does not detect anything in its field of view, or a TemperatureSensor could send a Saturation error indicating its temperature reading is outside the valid range for the sensor.

Error events are also fired when network errors occur, or when the library is unable to handle incoming change events quickly enough (event handlers could be too slow).

We strongly recommend setting up an error event handler for your channels so your program can keep track of these error conditions.

<tabber>
Python=<syntaxhighlight lang=python>
#Declare the event handler
def onErrorHandler(self, code, description):
print("Code: " + str(code))
print("Description: " + description)
...
#Declare your object. Replace "DigitalInput" with the object for your Phidget
ch = DigitalInput()
...
#Assign the handler that will be called when the event occurs
ch.setOnErrorHandler(onErrorHandler)
</syntaxhighlight>
|-|
Java=<syntaxhighlight lang=java>
//Declare the event listener
public static ErrorListener onError = new ErrorListener() {
@Override
public void onError(ErrorEvent e) {
System.out.println("Code: " + e.getCode());
System.out.println("Description: " + e.getDescription());
}
};
...
//Declare your object. Replace "DigitalInput" with the object for your Phidget.
DigitalInput ch;
...
//Assign the event listener that will be called when the event occurs
ch.addErrorListener(onError);
</syntaxhighlight>
|-|
C#=<syntaxhighlight lang=cSharp>
//Declare the event handler
void error(object sender, Phidget22.Events.ErrorEventArgs e) {
Console.WriteLine("Code: " + e.Code.ToString());
Console.WriteLine("Description: " + e.Description);
}
...
//Declare your object. Replace "DigitalInput" with the object for your Phidget.
DigitalInput ch;
...
//Assign the handler that will be called when the event occurs
ch.Error += error;
</syntaxhighlight>
|-|
C=<syntaxhighlight lang=c>
//Declare the event handler
static void CCONV onErrorHandler(PhidgetHandle ph, void *ctx, Phidget_ErrorEventCode code, const char* description) {
printf("Code: %d\n", code);
printf("Description: %s\n", description);
}
...
//Declare your object. Replace "PhidgetDigitalInputHandle" with the handle for your Phidget object.
PhidgetDigitalInputHandle ch;
...
//Assign the handler that will be called when the event occurs
Phidget_setOnErrorHandler((PhidgetHandle)ch, onErrorHandler, NULL);
</syntaxhighlight>
</tabber>

Full descriptions of all error event codes can be found in the [[Error Event Code List]] page.

==Logging==
You can enable logging to get more debugging information. This would happen at the very start of your program, before even initializing your software object or opening it. Logging lets you get feedback from the Phidget libraries about things happening behind the scenes.

<tabber>
Python=<syntaxhighlight lang=python>
Log.enable(Phidget22.LogLevel.LogLevel.PHIDGET_LOG_INFO, "path/to/log/file.log")
</syntaxhighlight>
|-|
Java=<syntaxhighlight lang=java>
Log.enable(LogLevel.INFO, null);
</syntaxhighlight>
|-|
C#=<syntaxhighlight lang=cSharp>
Log.Enable(LogLevel.Info, null);
</syntaxhighlight>
|-|
C=<syntaxhighlight lang=c>
PhidgetLog_enable(PHIDGET_LOG_INFO, NULL);
</syntaxhighlight>
</tabber>

When <code>NULL</code> is passed to <code>enable()</code> in the above examples, the logging system will output to <code>STDERR</code>.

For a more comprehensive look at the logging system in Phidget22, you can check out the [[Logging Details]] page.

== Other Problems ==

If your Phidget is still not behaving as expected after handling errors and exceptions, have a look at our [[General Troubleshooting]] guide to track down the problem.

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

Handling Errors and Logging

2019-03-06T17:35:19Z

Burley:

[[Category:Programming]]{{Recommended_Flow_Links|{{Flow Page Number|{{PAGENAME}} }} }}
__NOTOC__
You've written your code, fixed the compiler errors, and yet, the program still isn't behaving as intended. The tools described on this page will help you further debug your program and figure out where in the code things are going wrong.

==Errors and Error Events==

The Phidget library uses errors and error events to communicate information about potential problems in your program. These can happen in-line in the form of an exception or error code (which generally indicate a problem in the code), and as Error Events (which generally indicate a problem with the Phidget's environment).

===Errors from Function Calls===

When a call to a Phidgets function fails it will throw an exception (or return an error code, depending on the language). It is important to check each function call for errors, and to catch and handle any errors.

Common causes of these type of errors are the Phidget not being attached, or one of the values provided to the function being outside the valid range.

You can handle exceptions and return codes as follows:

<tabber>
Python=<syntaxhighlight lang=python>
try:
ch.openWaitForAttachment(5000);
except PhidgetException as e:
print("Failed to open: " + e.details)
</syntaxhighlight>
|-|
Java=<syntaxhighlight lang=java>
try {
ch.open(5000);
} catch (PhidgetException ex) {
System.out.println("Failed to open: " + ex.getMessage());
}
</syntaxhighlight>
|-|
C#=<syntaxhighlight lang=cSharp>
try
{
ch.Open(); //open the device
}
catch (PhidgetException ex)
{
Console.WriteLine("Failed to open: " + ex.Description)
}
</syntaxhighlight>
|-|
C=<syntaxhighlight lang=c>
PhidgetDigitalInputHandle ch;
PhidgetReturnCode res;
...
res = Phidget_openWaitForAttachment((PhidgetHandle)ch, 5000);
if (res != EPHIDGET_OK) {
char* desc;
Phidget_getErrorDescription(res, &desc);
printf("Failed to open: (%d) %s\n", res, desc);
}
</syntaxhighlight>
</tabber>

The consequences of not handling errors correctly ranges from improper behavior, to the program crashing due to an unhandled exception. Programs should check for errors on each function call, and handle any errors.

====Error Codes====

A list of error codes can be found in the {{Phidget22API}}.

===Error Events===

Error events are asynchronously generated by Phidget devices, and by the Phidget library itself.

These do not necessarily indicate a problem with your program, and often serve as a status update from your device that your program should know. For example, a DistanceSensor might send an OutOfRange error if it does not detect anything in its field of view, or a TemperatureSensor could send a Saturation error indicating its temperature reading is outside the valid range for the sensor.

Error events are also fired when network errors occur, or when the library is unable to handle incoming change events quickly enough (event handlers could be too slow).

We strongly recommend setting up an error event handler for your channels so your program can keep track of these error conditions.

<tabber>
Python=<syntaxhighlight lang=python>
#Declare the event handler
def onErrorHandler(self, code, description):
print("Code: " + str(code))
print("Description: " + description)
...
#Declare your object. Replace "DigitalInput" with the object for your Phidget
ch = DigitalInput()
...
#Assign the handler that will be called when the event occurs
ch.setOnErrorHandler(onErrorHandler)
</syntaxhighlight>
|-|
Java=<syntaxhighlight lang=java>
//Declare the event listener
public static ErrorListener onError = new ErrorListener() {
@Override
public void onError(ErrorEvent e) {
System.out.println("Code: " + e.getCode());
System.out.println("Description: " + e.getDescription());
}
};
...
//Declare your object. Replace "DigitalInput" with the object for your Phidget.
DigitalInput ch;
...
//Assign the event listener that will be called when the event occurs
ch.addErrorListener(onError);
</syntaxhighlight>
|-|
C#=<syntaxhighlight lang=cSharp>
//Declare the event handler
void error(object sender, Phidget22.Events.ErrorEventArgs e) {
Console.WriteLine("Code: " + e.Code.ToString());
Console.WriteLine("Description: " + e.Description);
}
...
//Declare your object. Replace "DigitalInput" with the object for your Phidget.
DigitalInput ch;
...
//Assign the handler that will be called when the event occurs
ch.Error += error;
</syntaxhighlight>
|-|
C=<syntaxhighlight lang=c>
//Declare the event handler
static void CCONV onErrorHandler(PhidgetHandle ph, void *ctx, Phidget_ErrorEventCode code, const char* description) {
printf("Code: %d\n", code);
printf("Description: %s\n", description);
}
...
//Declare your object. Replace "PhidgetDigitalInputHandle" with the handle for your Phidget object.
PhidgetDigitalInputHandle ch;
...
//Assign the handler that will be called when the event occurs
Phidget_setOnErrorHandler((PhidgetHandle)ch, onErrorHandler, NULL);
</syntaxhighlight>
</tabber>

Full descriptions of all error event codes can be found in the [[Error Event Code List]] page.

==Logging==
You can enable logging to get more debugging information. This would happen at the very start of your program, before even initializing your software object or opening it. Logging lets you get feedback from the Phidget libraries about things happening behind the scenes.

<tabber>
Python=<syntaxhighlight lang=python>
Log.enable(Phidget22.LogLevel.LogLevel.PHIDGET_LOG_INFO, "path/to/log/file.log")
</syntaxhighlight>
|-|
Java=<syntaxhighlight lang=java>
Log.enable(LogLevel.INFO, null);
</syntaxhighlight>
|-|
C#=<syntaxhighlight lang=cSharp>
Log.Enable(LogLevel.Info, null);
</syntaxhighlight>
|-|
C=<syntaxhighlight lang=c>
PhidgetLog_enable(PHIDGET_LOG_INFO, NULL);
</syntaxhighlight>
</tabber>

When <code>NULL</code> is passed to <code>enable()</code> in the above examples, the logging system will output to <code>STDERR</code>.

For a more comprehensive look at the logging system in Phidget22, you can check out the [[Logging Details]] page.

== Other Problems ==

If your Phidget is still not behaving as expected after handling errors and exceptions, have a look at our [[General Troubleshooting]] guide to track down the problem.

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

Using Multiple Phidgets

2019-03-06T17:30:18Z

Burley:

[[Category:Programming]]{{Recommended_Flow_Links|{{Flow Page Number|{{PAGENAME}} }} }}
__NOTOC__
Chances are your project with Phidgets is going to involve more than one Phidget channel. Luckily, making a program that deals with multiple Phidgets is done in much the same way as making a program that only deals with one.

This video explains the process of using multiple Phidgets in your program:
<center>{{#ev:youtube|c3M8d0nBP4c}}</center>

==The Basics==

To use more than one Phidget channel in you program, simply repeat the ''Create'', ''Address'', and, ''Open'' process for each channel, and remember to ''Close'' them all when done.

===Addressing Channels===

When you are using more than one Phidget channel in your program, you are going to have to specify some addressing parameters to ensure each software channel connects to the right Phidget.

Full descriptions of all the addressing parameters can be found on the [[Addressing Phidgets]] page.

===Example===

For example, to open two Phidgets, the code might be:
<tabber>
Python=<syntaxhighlight lang=python>
#Set up the first channel as normal
ch = TemperatureSensor()
ch.setDeviceSerialNumber(12345)
ch.setHubPort(4)
ch.setChannel(0)
ch.openWaitForAttachment(5000)

#For a second channel, simply repeat the process with different addressing information
ch1 = TemperatureSensor()
ch1.setDeviceSerialNumber(12345)
ch1.setHubPort(3)
ch1.setChannel(0)
ch1.openWaitForAttachment(5000)

#Do stuff with your Phidgets here...

#Remember to close the channels when done
ch.close()
ch1.close()
</syntaxhighlight>
|-|
Java=<syntaxhighlight lang=java>
//Set up the first channel as normal
TemperatureSensor ch = new TemperatureSensor();
ch.setDeviceSerialNumber(12345);
ch.setHubPort(4);
ch.setChannel(0);
ch.open(5000);

//For a second channel, simply repeat the process with different addressing information
TemperatureSensor ch1 = new TemperatureSensor();
ch1.setDeviceSerialNumber(12345);
ch1.setHubPort(3);
ch1.setChannel(0);
ch1.open(5000);

//Do stuff with your Phidgets here...

//Remember to close the channels when done
ch.close();
ch1.close();
</syntaxhighlight>
|-|
C#=<syntaxhighlight lang=cSharp>
//Set up the first channel as normal
TemperatureSensor ch = new TemperatureSensor();
ch.DeviceSerialNumber = 12345;
ch.HubPort = 4;
ch.Channel = 0;
ch.Open(5000);

//For a second channel, simply repeat the process with different addressing information
TemperatureSensor ch1 = new TemperatureSensor();
ch1.DeviceSerialNumber = 12345;
ch1.HubPort = 3;
ch1.Channel = 0;
ch1.Open(5000);

//Do stuff with your Phidgets here...

//Remember to close the channels when done
ch.Close();
ch1.Close();
</syntaxhighlight>
|-|
C=<syntaxhighlight lang=c>
//Set up the first channel as normal
PhidgetTemperatureSensorHandle ch;
PhidgetTemperatureSensor_create(&ch);

Phidget_setDeviceSerialNumber((PhidgetHandle)ch, 12345);
Phidget_setHubPort((PhidgetHandle)ch, 4);
Phidget_setChannel((PhidgetHandle)ch, 0);
Phidget_openWaitForAttachment((PhidgetHandle)ch, 5000);

//For a second channel, simply repeat the process with different addressing information
PhidgetTemperatureSensorHandle ch1;
PhidgetTemperatureSensor_create(&ch1);

Phidget_setDeviceSerialNumber((PhidgetHandle)ch1, 12345);
Phidget_setHubPort((PhidgetHandle)ch1, 4);
Phidget_setChannel((PhidgetHandle)ch1, 0);
Phidget_openWaitForAttachment((PhidgetHandle)ch1, 5000);

//Do stuff with your Phidgets here...

//Remember to close the channels when done
Phidget_close((PhidgetHandle)ch);
Phidget_close((PhidgetHandle)ch1);
PhidgetTemperatureSensor_delete(&ch);
PhidgetTemperatureSensor_delete(&ch1);
</syntaxhighlight>
</tabber>

==Similar Phidgets==

If you have a large number of the same Phidget channel and want an easier way to keep track of them all, consider using an array to keep them all together.

<tabber>
Python=<syntaxhighlight lang=python>
#Create the array of Phidget channels
ch = [DigitalOutput() for i in range (0, 8)]

for i in range (0, 8):
#Address, then open the channels
ch[i].openWaitForAttachment(5000)

#Now you can access each channel by its position in the array
ch[0].setState(True)
ch[1].setState(False)
ch[2].setState(False)
ch[3].setState(True)

for i in range (0, 8):
ch[i].close()
</syntaxhighlight>
|-|
Java=<syntaxhighlight lang=java>
//Create an array for your Phidget channels
DigitalOutput[] ch = new DigitalOutput[8];

for(int i = 0; i < 8; i++) {
//Create the channels
ch[i] = new DigitalOutput();
//Address, then open the channels
ch[i].open(5000);
}

//Now you can access each channel by its position in the array
ch[0].setState(true);
ch[1].setState(false);
ch[2].setState(false);
ch[3].setState(true);

//Close all channels when done
for(int i=0; i<8; i++) {
ch[i].close();
}

</syntaxhighlight>
|-|
C#=<syntaxhighlight lang=cSharp>
//Create an array for your Phidget channels
DigitalOutput[] ch = new DigitalOutput[8];

//Open the channels
for(int i=0; i<8; i++)
{
//Create the channels
ch[i] = new DigitalOutput();
//Address, then open the channels
ch[i].Open(5000);
}

//Now you can access each channel by its position in the array
ch[0].State = true;
ch[1].State = false;
ch[2].State = false;
ch[3].State = true;

//Close the channels when done
for(int i=0; i<8; i++)
{
ch[i].Close();
}
</syntaxhighlight>
|-|
C=<syntaxhighlight lang=c>
//Create an array for your Phidget channels
PhidgetDigitalOutputHandle ch[8];

for (int i = 0; i < 8; i++) {
//Create the channels
PhidgetDigitalOutput_create(&ch[i]);
//Address, then open the channels
Phidget_openWaitForAttachment((PhidgetHandle)ch[i], 5000);
}

PhidgetDigitalOutput_setState(ch[0], true);
PhidgetDigitalOutput_setState(ch[1], false);
PhidgetDigitalOutput_setState(ch[2], false);
PhidgetDigitalOutput_setState(ch[3], true);

//Close the channels when done
for (int i = 0; i < 8; i++) {
Phidget_close((PhidgetHandle)ch[i]);
}
</syntaxhighlight>
</tabber>

==Distinguishing Events==

When using [[Polling vs. Events|events]], you can either create separate events for each device, or handle multiple devices with the same event (or some combination of both). If multiple devices use the same event handler, you can use the addressing properties of the channel to determine which Phidget channel caused the event.

For example, for an Attach Event handler:

<tabber>
Python=
In Python, the channel that fired the event can be accessed from the event handler using the {{code|self}} parameter (the first parameter in the list).
<syntaxhighlight lang=python>
#Declare the event handler
def onAttachHandler(self):
#You can access the Phidget that fired the event using the "self" parameter
ph = self
deviceSerialNumber = ph.getDeviceSerialNumber()
...
#Declare your object. Replace "DigitalInput" with the object for your Phidgetch = DigitalInput()
...
#Assign the handler that will be called when the event occurs
ch.setOnAttachHandler(onAttachHandler)
</syntaxhighlight>
|-|
Java=
In Java, you can call {{code|getSource()}} on the event parameter to get the Phidget that caused the event.
<syntaxhighlight lang=java>
//Declare the event listener
public static DigitalInputAttachListener onAttach = new DigitalInputAttachListener() {
@Override
public void onAttach(AttachEvent e) {
//You can access the Phidget that fired the event by calling "getSource()"
//on the event parameter.
//Replace "DigitalInput" with the object for your Phidget.
DigitalInput ph = (DigitalInput) e.getSource();
int deviceSerialNumber = ph.getDeviceSerialNumber();
}
};
...
//Declare your object. Replace "DigitalInput" with the object for your Phidget.
DigitalInput ch;
...
//Assign the event listener that will be called when the event occurs
ch.addAttachListener(onAttach);
</syntaxhighlight>
|-|
C#=
In C#, you can access the Phidget that fired the event by typecasting the {{code|sender}} parameter to the appropriate Phidget object type.
<syntaxhighlight lang=cSharp>
//Declare the event handler
void attach(object sender, Phidget22.Events.AttachEventArgs e) {
//You can access the Phidget that fired the event by typecasting "sender"
//to the appropriate Phidget object type.
//Replace "DigitalInput" with the object for your Phidget.
DigitalInput ph = ((DigitalInput)sender);
int deviceSerial = ph.DeviceSerialNumber;
}
...
//Declare your object. Replace "DigitalInput" with the object for your Phidget.
DigitalInput ch;
...
//Assign the handler that will be called when the event occurs
ch.Attach += attach;
</syntaxhighlight>
|-|
C=
In C, you can access the Phidget that fired the event using the first parameter of the event handler.
<syntaxhighlight lang=c>
//Declare the event handler
static void CCONV onAttachHandler(PhidgetHandle ph, void *ctx) {
//You can access the Phidget that fired the event by using the first parameter
//of the event handler
int deviceSerialNumber;
Phidget_getDeviceSerialNumber(ph, &deviceSerialNumber);
}
...
//Declare your object. Replace "PhidgetDigitalInputHandle" with the handle for your Phidget object.
PhidgetDigitalInputHandle ch;
...
//Assign the handler that will be called when the event occurs
Phidget_setOnAttachHandler((PhidgetHandle)ch, onAttachHandler, NULL);
</syntaxhighlight>
</tabber>

==Referencing Other Phidgets from Events==

When using multiple Phidgets in the same program, you may want to access one Phidget from the within an event caused by another. There are simple ways of doing this for all languages, though the specifics depend on the programming language you are using:

<tabber>
Python=
Python is dynamically interpreted, and objects follow a less rigid structure than in other languages. To access another Phidget from an event handler, you can add the second Phidget's handle as an attribute of the Phidget object that will be triggering the event. Then, you can access the second Phidget using the corresponding attribute from the {{code|self}} parameter of the event.

For example, if we wanted to make a Digital Output channel follow the state of a button:
<syntaxhighlight lang=python>
def onStateChangeHandler(self, state):
#Be sure the other Phidget you are trying to access is attached before using it
if(self.linkedOutput.getAttached()):
self.linkedOutput.setState(state)

button = DigitalInput()
output = DigitalOutput()

#Addressing info here

#Here we create an attribute of input called "linkedOutput", and assign it the handle for output
button.linkedOutput = output
button.setOnStateChangeHandler(onStateChangeHandler)

output.openWaitForAttachment(5000)
button.openWaitForAttachment(5000)

# The rest of your code here....
</syntaxhighlight>
|-|
Java=
In Java, chances are your event handlers are defined in the same class as the Phidget handles. In this case, you can simply reference Phidgets in the event handlers the same way as you would in the rest of your code.

For example, if we wanted to make a Digital Output channel follow the state of a button:
<syntaxhighlight lang=java>
public class MultiPhidgetExample {

private static DigitalInput button = null;
private static DigitalOutput output = null;

public static DigitalInputStateChangeListener onStateChange =
new DigitalInputStateChangeListener() {
@Override
public void onStateChange(DigitalInputStateChangeEvent e) {

//Be sure the other Phidget you are trying to access is attached before using it
if(output.getAttached() == true)
output.setState(e.getState());
}
};

public static void main(String[] args) throws Exception {
try {
button = new DigitalInput();
output = new DigitalOutput();

//Set Any Addressing Parameters Here

button.addStateChangeListener(onStateChange);

output.open(5000);
button.open(5000);

// The rest of your code here...

} catch (PhidgetException ex) {
System.out.println(ex.getDescription());
}
}
}
</syntaxhighlight>
|-|
C#=
In C#, chances are your event handlers are defined in the same class as the Phidget handles. In this case, you can simply reference Phidgets in the event handlers the same way as you would in the rest of your code.

For example, if we wanted to make a Digital Output channel follow the state of a button:
<syntaxhighlight lang=cSharp>
namespace ConsoleApplication
{
class Program
{
private static DigitalInput button = null;
private static DigitalOutput output = null;

private static void onStateChange(object sender,
DigitalInputStateChangeEventArgs e)
{
//Be sure the other Phidget you are trying to access is attached before using it
if (output.Attached == true)
output.State = e.State;
}

static void Main(string[] args)
{
button = new DigitalInput();
output = new DigitalOutput();

//Set Any Addressing Parameters Here

button.StateChange += onStateChange;

output.Open(5000);
button.Open(5000);

//The rest of your code here...
}
}
}
</syntaxhighlight>
|-|
C=
In C, all event handler declarations have a context pointer that can be pointed at any object you choose. This can be a set of relevant data, or even a Phidget handle. If you pass a Phidget handle as the context pointer for an event, you can access the passed Phidget from the event as follows:

For example, if we wanted to make a Digital Output channel follow the state of a button:
<syntaxhighlight lang=C>
static void CCONV onStateChangeHandler(PhidgetDigitalInputHandle pdih, void *ctx, int state) {
int attached;
//Extract our output handle from the context pointer
PhidgetDigitalOutputHandle linkedOutput = (PhidgetDigitalOutputHandle)ctx;

//Be sure the other Phidget you are trying to access is attached before using it
Phidget_getAttached((PhidgetHandle)linkedOutput, &attached);

if(attached)
PhidgetDigitalOutput_setState(linkedOutput, state);

}

int main() {
PhidgetDigitalInputHandle button = NULL;
PhidgetDigitalOutputHandle output = NULL;

PhidgetDigitalInput_create(&button);
PhidgetDigitalOutput_create(&output);

//Addressing info here

//Here we pass the handle for "output" as the context pointer so we can access it from the event
PhidgetDigitalInput_setOnStateChangeHandler(ch, onStateChangeHandler, output);

Phidget_openWaitForAttachment((PhidgetHandle)output, 5000);
Phidget_openWaitForAttachment((PhidgetHandle)button, 5000);

//The rest of your code here...

}
</syntaxhighlight>
|-|
JavaScript=
JavaScript is dynamically interpreted, and objects follow a less rigid structure than in other languages. To access another Phidget from an event handler, you can add the second Phidget's handle as a property of the Phidget object that will be triggering the event. Then, you can access the second Phidget using the corresponding property from the {{code|this}} parameter of the event.

For example, if we wanted to make a Digital Output channel follow the state of a button:
<syntaxhighlight lang=javaScript>
function stateChange(state) {
//Be sure the other Phidget you are trying to access is attached before using it
if(this.linkedOutput.getAttached())
this.linkedOutput.setState(state);
}
...
var button = new phidget22.DigitalInput();
var output = new phidget22.DigitalOutput();
...
//Here we create an attribute of input called "linkedOutput", and assign it the handle for output
button.linkedOutput = output;
button.onStateChange = stateChange;

output.open();
button.open();

//The rest of your code here...
</syntaxhighlight>
</tabber>

==What's Next?==
Now that you know how to use multiple Phidgets in your program, we should discuss how to find the features available to you by using the Phidget22 API.

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

Using Multiple Phidgets

2019-03-06T17:27:35Z

Burley:

Using Events

2019-03-06T17:12:04Z

Burley:

[[Category:Programming]]{{Recommended_Flow_Links|{{Flow Page Number|{{PAGENAME}} }} }}
__NOTOC__

If you are new to Phidgets, or event-driven programming, chances are your first instinct will be to poll for everything. Polling is the action of repeatedly checking a variable or property to see if it has changed, and is generally done in-line from the main body of your application. While this can be effective in smaller applications, this quickly becomes inefficient. You also risk missing a change your program is waiting for, if it polls for data too slowly.

==Events==
[[Image:Event_Explanation_Flowchart.png|200px|right|link={{Server}}/docs/images/2/21/Event_Explanation_Flowchart.png|thumb|'''Click to Enlarge''']]
The Phidget library allows for the use of '''event-driven programming'''. This allows your program to react to certain stimuli as they happen, rather than having to constantly check for changes. By setting up event handlers, you are setting up functions that run every time the event associated with them occurs. Once they have been assigned, these functions run '''''independently from the main body of code'''''. For example, a '''State Change''' event handler for a {{code|DigitalInput}} channel will run every time the input state changes. Similarly, '''Attach''' and '''Detach''' events will occur when a device channel attaches to and detaches from your program (e.g. is plugged in and unplugged).

Using events can be very useful for tasks such as recording every data point from a Phidget sensor, reacting to a button being pressed, or initializing a channel as soon as it is attached. This frees up the main body of your program from having to constantly check the status of the Phidget, which can significantly clean up many applications.
<br clear="all">

==Special Considerations==
When using events, you must be mindful of keeping the code handling the event running as quickly as possible. If the event handler takes longer than the interval between events, this will cause the events to pile up and fall out of sync with the time they occur, and eventually start being lost.

When using events, you will need to be careful about what you share between the event and your main code. This is because '''events can happen at any time''', so any variables shared with them could change unexpectedly.

==Recommendations==
We recommend all but the simplest program should set handlers that will be called when a channel '''attaches''', '''detaches''', sends an '''error''', or receives new sensor data.

Initializing a channel should be done from the '''attach''' event handler, so it will always be configured as intended, even if something causes it to be unplugged and plugged back in.

===Error Events===
Make sure not to ignore using the Phidget error event handler, as many Phidgets will send critical information to the program using error events, such as when a sensor takes a measurement outside of its valid range, or activates some safety feature.

==Linking Data to Events==
When you're using events in your program, it may become useful to link certain information to the event for a given Phidget channel. Some programming languages provide a convenient way of doing exactly that, though the specifics depend on the programming language you are using:

<tabber>
Python=
Python is dynamically interpreted, and objects follow a less rigid structure than in other languages. To link a variable with a given Phidget object to have it available from the event, you can add it to the Phidget object that will be triggering the event. Then, you can access the information using the {{code|self}} parameter of the event.

For example, if we wanted to group a number with a Phidget channel to be used in an event:
<syntaxhighlight lang=python>
def onStateChangeHandler(self, state):
#We can now access and even change "myVariable" from the event
print(self.myVariable)
self.myVariable += 1

ch = DigitalInput()

#Addressing info here

#Here we create an attribute of ch called "myVariable", and assign it the information to store
#We'll use an integer here for simplicity, but this could be anything, even a second Phidget Handle
ch.myVariable = 0
ch.setOnStateChangeHandler(onStateChangeHandler)

ch.openWaitForAttachment(5000)

# The rest of your code here....
</syntaxhighlight>
|-|
C=
In C, all event handler declarations have a context pointer that can be pointed at any object you choose. This can be a set of relevant data, or even a Phidget handle.

For example, if we wanted to link a number with a specific event for a Phidget channel:

<syntaxhighlight lang=C>
static void CCONV onStateChangeHandler(PhidgetDigitalInputHandle pdih, void *ctx, int state) {

//We can now access the information at the pointer from the event
int* myIntPtr = (int*)ctx;
printf("Int: %d\n", *myIntPtr);
(*myIntPtr) ++;
}

int main() {
PhidgetDigitalInputHandle ch = NULL;
int myIntMain = 0;

PhidgetDigitalInput_create(&ch);

//Addressing info here

//Here we pass "myStringMain" as the context pointer so we can access it from the event
//This can be a pointer to any variable or structure, or even a second Phidget handle
PhidgetDigitalInput_setOnStateChangeHandler(ch, onStateChangeHandler, &myIntMain);

Phidget_openWaitForAttachment((PhidgetHandle)ch, 5000);

//The rest of your code here...

}
</syntaxhighlight>
|-|
JavaScript=
JavaScript is dynamically interpreted, and objects follow a less rigid structure than in other languages. To link a variable with a given Phidget object to have it available from the event, you can add it to the Phidget object that will be triggering the event. Then, you may access the information using the {{code|self}} parameter of the event.

For example, if we wanted to group a number with a Phidget channel to be used in an event:
<syntaxhighlight lang=javaScript>
function stateChange(state) {
//We can now access and even change "myVariable" from the event
console.log(this.myVariable);
this.myVariable += 1;
}
...
var ch = new phidget22.DigitalInput();
...
//Here we create a property of ch called "myVariable", with the information to store
//We'll use an integer here for simplicity, but this could be anything,
//even a second Phidget Handle
ch.myVariable = 0
ch.onStateChange = stateChange;

ch.open();

//The rest of your code here...
</syntaxhighlight>
</tabber>

==When should I poll?==
If all you need is a simple program that reads a small amount of data from a device, it is possible to open a channel, wait for attachment, read the data, and close the channel. In that case, the code to implement and set event handlers might not be worth the effort. When polling, '''error checking becomes very important''', as accessing some channel properties while the channel is detached, or before any data comes back from the Phidget, will result in an error or exception that could kill the program. There will always be a race between checking the {{Code|Attached}} property and accessing a data or state property.

When in doubt, use event handlers.

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

Using Events

2019-03-06T17:11:30Z

Burley:

[[Category:Programming]]{{Recommended_Flow_Links|{{Flow Page Number|{{PAGENAME}} }} }}
__NOTOC__

If you are new to Phidgets, or event-driven programming, chances are your first instinct will be to poll for everything. Polling is the action of repeatedly checking a variable or property to see if it has changed, and is generally done in-line from the main body of your application. While this can be effective in smaller applications, this quickly becomes inefficient. You also risk missing a change your program is waiting for, if it polls for data too slowly.

==Events==
[[Image:Event_Explanation_Flowchart.png|200px|right|link={{Server}}/docs/images/2/21/Event_Explanation_Flowchart.png|thumb|'''Click to Enlarge''']]
The Phidget library allows for the use of '''event-driven programming'''. This allows your program to react to certain stimuli as they happen, rather than having to constantly check for changes. By setting up event handlers, you are setting up functions that run every time the event associated with them occurs. Once they have been assigned, these functions run '''''independently from the main body of code'''''. For example, a '''State Change''' event handler for a {{code|DigitalInput}} channel will run every time the input state changes. Similarly, '''Attach''' and '''Detach''' events will occur when a device channel attaches to and detaches from your program (e.g. is plugged in and unplugged).

Using events can be very useful for tasks such as recording every data point from a Phidget sensor, reacting to a button being pressed, or initializing a channel as soon as it is attached. This frees up the main body of your program from having to constantly check the status of the Phidget, which can significantly clean up many applications.
<br clear="all">

==Special Considerations==
When using events, you must be mindful of keeping the code handling the event running as quickly as possible. If the event handler takes longer than the interval between events, this will cause the events to pile up and fall out of sync with the time they occur, and eventually start being lost.

When using events, you will need to be careful about what you share between the event and your main code. This is because '''events can happen at any time''', so any variables shared with them could change unexpectedly.

==Recommendations==
We recommend all but the simplest program should set handlers that will be called when a channel '''attaches''', '''detaches''', sends an '''error''', or receives new sensor data.

Initializing a channel should be done from the '''attach''' event handler, so it will always be configured as intended, even if something causes it to be unplugged and plugged back in.

===Error Events===
Make sure not to ignore using the Phidget error event handler, as many Phidgets will send critical information to the program using error events, such as when a sensor takes a measurement outside of its valid range, or activates some safety feature.

==Linking Data to Events==
When you're using events in your program, it may become useful to link certain information to the event for a given Phidget channel. Some programming languages provide a convenient way of doing exactly that, though the specifics depend on the programming language you are using:

<tabber>
Python=
Python is dynamically interpreted, and objects follow a less rigid structure than in other languages. To link a variable with a given Phidget object to have it available from the event, you can add it to the Phidget object that will be triggering the event. Then, you can access the information using the {{code|self}} parameter of the event.

For example, if we wanted to group a number with a Phidget channel to be used in an event:
<syntaxhighlight lang=python>
def onStateChangeHandler(self, state):
#We can now access and even change "myVariable" from the event
print(self.myVariable)
self.myVariable += 1

ch = DigitalInput()

#Addressing info here

#Here we create an attribute of ch called "myVariable", and assign it the information to store
#We'll use an integer here for simplicity, but this could be anything, even a second Phidget Handle
ch.myVariable = 0
ch.setOnStateChangeHandler(onStateChangeHandler)

ch.openWaitForAttachment(5000)

# The rest of your code here....
</syntaxhighlight>
|-|
C=
In C, all event handler declarations have a context pointer that can be pointed at any object you choose. This can be a set of relevant data, or even a Phidget handle.

For example, if we wanted to link a number with a specific event for a Phidget channel:

<syntaxhighlight lang=C>
static void CCONV onStateChangeHandler(PhidgetDigitalInputHandle pdih, void *ctx, int state) {

//We can now access the information at the pointer from the event
int* myIntPtr = (int*)ctx;
printf("Int: %d\n", *myIntPtr);
(*myIntPtr) ++;
}

int main() {
PhidgetDigitalInputHandle ch = NULL;
int myIntMain = 0;

PhidgetDigitalInput_create(&ch);

//Addressing info here

//Here we pass "myStringMain" as the context pointer so we can access it from the event
//This can be a pointer to any variable or structure, or even a second Phidget handle
PhidgetDigitalInput_setOnStateChangeHandler(ch, onStateChangeHandler, &myIntMain);

Phidget_openWaitForAttachment((PhidgetHandle)ch, 5000);

//The rest of your code here...

}
</syntaxhighlight>
|-|
JavaScript=
JavaScript is dynamically interpreted, and objects follow a less rigid structure than in other languages. To link a variable with a given Phidget object to have it available from the event, you can add it to the Phidget object that will be triggering the event. Then, you may access the information using the {{code|self}} parameter of the event.

For example, if we wanted to group a number with a Phidget channel to be used in an event:
<syntaxhighlight lang=javaScript>
function stateChange(state) {
//We can now access and even change "myVariable" from the event
console.log(this.myVariable);
this.myVariable += 1;
}
...
var ch = new phidget22.DigitalInput();
...
//Here we create a property of ch called "myVariable", with the information to store
//We'll use an integer here for simplicity, but this could be anything,
//even a second Phidget Handle
ch.myVariable = 0
ch.onStateChange = stateChange;

ch.open();

//The rest of your code here...
</syntaxhighlight>
</tabber>

==When should I poll?==
If all you need is a simple program that reads a small amount of data from a device, it is possible to write a program that opens a channel, waits for attachment, reads the data, and closes the channel. In that case, the code to implement and set event handlers might not be worth the effort. When polling, '''error checking becomes very important''', as accessing some channel properties while the channel is detached, or before any data comes back from the Phidget, will result in an error or exception that could kill the program. There will always be a race between checking the {{Code|Attached}} property and accessing a data or state property.

When in doubt, use event handlers.

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

Phidget Channels

2019-03-06T15:57:29Z

Burley:

{{Recommended_Flow_Links|{{Flow Page Number|{{PAGENAME}} }} }}

To program with Phidgets, it is important to understand how the physical input and output channels of Phidget devices correspond to the software controlling them.

==What are Phidget channels?==

Each part of a Phidget's behaviour is split into individual parts called '''Channels'''. Each channel represents a '''single part''' of a device, such as a single input on a digital input Phidget, the humidity sensor on a humidity Phidget, or one motor on a DC motor controller.

Each channel has a '''Channel Class''', corresponding to the type of function the channel performs. For example, a {{code|DCMotor}} channel will control a DC motor, a {{code|TemperatureSensor}} channel will measure temperature, and an {{code|RFID}} channel will deal with an RFID reader.

[[File:Phidget_Channels_w_Panel.png|center|link=]]

Each channel class is designed to make using channels of that class '''as similar as possible''', regardless of the Phidget they are a part of. For example, every {{Code|VoltageInput}} channel has functions to set the data interval and read the voltage on the input.

Each channel class also provides settings unique to devices in that class, such as the ability to set a {{code|QuietMode}} on sonar sensors, which use the {{code|DistanceSensor}} class.

You can find out what channel classes are available to your Phidget by looking at its [[Product Page Links|'''User Guide''']].

{{Flow Navigation Buttons|{{Flow Page Number|{{PAGENAME}} }} }}

Rotary Motion Guide

2019-01-30T17:37:47Z

Burley:

<metadesc>Rotary systems involve rotating mechanical parts such as motors, sprockets, and pulleys. Learn more at Phidgets.com.</metadesc>
[[Category:Primer]]
==Introduction==
In rotary systems, you have a rotating shaft which applies torque to do work. Typically this shaft is turned by an electric motor of some kind and then, through a series of belts/chains/couplers transmits that power to a final output shaft or arm or wheel which accomplishes the desired task. Why not just use the output shaft of the motor directly? There are two main reasons:

*You might want to gear the motor down further to increase the torque available by using pulleys or sprockets of differing sizes.
*The shaft on the motor itself isn't really designed for forces other than torque. It is difficult to put anything of significant size on the shaft without putting too much overhung (radial) load on the shaft which will stall the motor.

As a result, the base of any rotary system is the rotating shaft. We have 4 sizes of shaft available: 8mm, 12mm, 17mm, and 25mm. The 12, 17, and 25mm shafts also have a variant available with a keyway machined in the length of the shaft if you don't want to machine it yourself. These shafts need to be suspended on bearings, we do not sell any bearings currently but they are commonly available components that you can find locally. For the larger shaft sizes (17 and 25mm) we recommend using steel bearing housings.

==Motors==
Every system will need a motor or else there will be no motion (without external input). We offer a wide selection of motors of a number of different types that would all be suitable for rotary systems. For more information on this you can check out our primers for [[DC Motor and Controller Primer|DC motors]] and [[Stepper Motor and Controller Primer|Stepper motors]].

==Pulleys/Timing belts==
A belt is simply a loop of tough, flexible material such as rubber and kevlar with a series of teeth that mesh with the teeth on specially designed pulley wheels to synchronize two (or more) rotating shafts. Belts are a cheap option for shafts that are not axially aligned and tend to run quietly and smoothly. Belts are typically tensioned either by adjusting center to center distance between pulleys or via a tensioner/idler pulley. This leads to very low backlash and a high efficiency (as high as 98%).

We have two types of belts available, 2GT (6mm wide) and 5GT (15mm wide). Each comes in loops of varying circumferences. The 2GT belts are rated for 6lbs of working tension while the 5GT are rated for 100lbs. Belt systems are fairly simple, you have 2 or more pulleys and a belt that goes around all of them. One of the pulleys is driven by your motor and the other(s) are either connected to your load or in the case of an idler pulley are simply free spinning to act as a tensioner for the belt. For example, here is a system that uses a belt to transmit power form a stepper motor to a ball screw:

[[image:Belt driven ball screw.JPG|500px|center|link=]]

==Chain/Sprockets==
Pretty much everyone has at least seen a chain system in their life in the form of a bicycle. This system of course is driven by human input rather than a motor. Automated systems behave no differently though, you have several sprockets, and chain that wraps around them. One sprocket is driven and the others perform work on the load. Chain tends to be noisier than belts and cannot be tensioned as tightly meaning there is a bit more backlash inherent in the system. In exchange though, chain can move much heavier loads for their size.

We sell ANSI#25 and #40 chain and sprockets (that is 0.25" pitch and 0.5" pitch). The #25 is rated for 100lbs of working tension while the #40 is rated for 800lbs. Chain is sold by the meter and you can form closed loops of any length you'd like with the link kits that we sell. To calculate how many links you will need for a particular sprocket spacing you can use [http://www.botlanta.org/converters/dale-calc/sprocket.html this calculator], just enter in the number of teeth on each sprocket, the chain pitch, and the center to center distance between the sprockets to get the number of links you will need. If the number is not whole, you should always round up (and probably even add one). Once you know how many links you will require you will need to use the link kit to connect your chain up. This is where it gets a bit fiddly.

There are two ways to connect chain, you can either use a hammer and a pin of some kind to knock out one of the pins which you can then connect up with an offset link:

The other way is if you have a chain breaker tool you can remove an entire link properly and can use a normal split link. This process is a bit more tricky but it is stronger over all and will increase the length of the chain by a standard amount unlike the offset link which adds a sort of half link to your total length. To use a split link you must remove the snap ring and the top plate, then slot it into the chain and replace them both. For example:
[[image:Chain_link_insert_wiki.png|link=|center|800px]]

A good example of a chain system is our MURVV robot. Here is how it's drive mechanism works:
[[Image:Murvv_chain.jpg|link=|center|500px]]

==Worm Gearboxes==
In general, worm gearboxes are just another type of gearbox that can be fitted to a motor. The main benefit of a worm drive is that it is all but impossible to back drive even when not powered. This is due to the steep angle used by the gears as they mesh together. As a result, this type of gearbox is not the most efficient. There is a lot of frictional loss at the mesh point and they will tend to run hot. That being said, in the context of the worm drives we sell, they are a means to substantially increase the output torque of our larger motors for applications where maximum strength is required. All our worm gearboxes have a 30:1 gear ratio and since the bearings built into the gearbox can handle much higher axial and radial loads that motors themselves you can easily direct drive very large loads from these gearboxes without having to set up an external mechanism.

==Bearings==
For the smaller bearings, installation is fairly straight forward. Simply mount the bearing onto your surface, slot the shaft in and tighten the set screws. However, for our larger bearings (12mm, 17mm and 25mm) there is a different system used known as an eccentric locking collar or eccentric collar lock. This is relatively simply to set up but you may not have seen this style of attachment before so lets have a look quickly at how it works and how to install it.

The locking mechanism works by putting a slightly eccentric hole in the bearing and using a collar with a matching hole. This way, when the collar is twisted on the shaft it will bind. Step by step:
[[image:empty_bearing.jpg|center|500px|link=]]

Notice how the wall of the bore is thinner on the right side than the left. This is also true of the collar which slides over the top of the shaft once it is in position. Insert the shaft in the bearing unit to the desired position:

[[image:uncollared_shaft.jpg|center|500px|link=]]

Next, put the collar onto the shaft and slide it down to the bearing. Turn the collar slowly until it seats on the lip of the bearing (i.e. the eccentricity of the holes lines up). Now you will want to tighten the collar by hand by turning it like you would a threaded cap. You will notice that it will bind by turning it in either direction within 180°. Be sure to turn the collar in the same direction the primary direction of rotation for the shaft in operation will be. Once the collar is tight, you will need to use a punch and a hammer to tighten it the last bit. Find the dead hole in the collar (not the set screw) and insert your punch. Angle the punch against the wall of the direction you have tightened the collar and give it a few solid taps with the hammer:

[[image:punch_collar.jpg|center|500px|link=]]

Now just tighten the set screw to ensure it doesn't loosen up with use and you are finished. To quickly demonstrate here is a video, note that I do not tighten the set screw in this video but that is straight forward enough so it was left out:

<center>
{{#ev:youtube|0v6NOY7aRbg}}
</center>

Operating System Support

2019-01-18T16:59:53Z

Burley:

[[Category:Overview]]
We provide support for all major operating systems. Select your operating system from the table below and follow the ''Getting Started'' guide in order to set up your machine. If you need to access non-current versions of our drivers you can find them [{{SERVER}}/downloads/phidget22/libraries/ here]. You can find the driver changelog [{{SERVER}}/?view=changelog here].

{| style="border:1px solid darkgray;" cellpadding="7px;"
|-style="background: #f0f0f0" align=center
! Operating System || Drivers and Libraries || Direct USB Control || Remote Network Control || Supported Version
|-

|colspan="5"|'''Desktop OSes'''
|-

|[[Image:Icon-Windows.png|alt=OS - Windows|24x24px|link=OS - Windows]][[OS - Windows|Windows]]
|style="background: #f0f0ff" align=center| [[OS - Windows#Quick Downloads|Quick Downloads]]
|style="background: #ade6ab" align=center| [[Image:Checkmark.png|link=]]
|style="background: #ade6ab" align=center| [[Image:Checkmark.png|link=]]
| Vista or Newer
|-

|[[Image:Icon-Mac-OS.png|alt=OS - macOS|24x24px|link=OS - macOS]][[OS - macOS|macOS]]
|style="background: #f0f0ff" align=center| [[OS - macOS#Quick Downloads|Quick Downloads]]
|style="background: #ade6ab" align=center| [[Image:Checkmark.png|link=]]
|style="background: #ade6ab" align=center| [[Image:Checkmark.png|link=]]
| OS X 10.5 or newer
|-

|[[Image:Icon-Linux.png|alt=OS - Linux|24x24px|link=OS - Linux]][[OS - Linux|Linux]]
|style="background: #f0f0ff" align=center| [[OS - Linux#Quick Downloads|Quick Downloads]]
|style="background: #ade6ab" align=center| [[Image:Checkmark.png|link=]]
|style="background: #ade6ab" align=center| [[Image:Checkmark.png|link=]]
| Kernel 2.6 or newer
|-

|colspan="5"|'''Mobile/Wireless OSes'''
|-

|[[Image:Icon-Phidgets.png|alt=OS - Phidget SBC|24x24px|link=OS - Phidget SBC]][[OS - Phidget SBC|Phidget SBC]]
|style="background: #f0f0ff" align=center| [[OS - Phidget SBC#Quick Downloads|Quick Downloads]]
|style="background: #ade6ab" align=center| [[Image:Checkmark.png|link=]]
|style="background: #ade6ab" align=center| [[Image:Checkmark.png|link=]]
| All versions
|-

|[[Image:Icon-iOS.png|alt=OS - iOS|link=OS - iOS|24x24px]][[OS - iOS|iOS]]
|style="background: #f0f0ff" align=center| [[OS - iOS#Quick Downloads|Quick Downloads]]
|style="background: #E28585" align=center| X
|style="background: #ade6ab" align=center| [[Image:Checkmark.png|link=]]
| 8.0 or newer
|-

|[[Image:Icon-Android.png|alt=OS - Android|24x24px|link=OS_-_Android]] [[OS_-_Android|Android]]
|style="background: #f0f0ff" align=center| [[OS_-_Android#Quick Downloads|Quick Downloads]]
|style="background: #ade6ab" align=center| [[Image:Checkmark.png|link=]]
|style="background: #ade6ab" align=center| [[Image:Checkmark.png|link=]]
| 4.1 (Jellybean) or newer
|}

Best Phidgets Practices

2019-01-04T16:42:01Z

Burley:

[[Category:Programming]]
The purpose of this page is to provide a list of "Best Practices" to follow when writing code that uses Phidgets. These "Best Practices" are designed to eliminate common mistakes made when using the {{Phidget22API}}, and to help maintain an stable structure while build more complicated systems.

== Check Results ==
Almost every method in the {{Phidget22API}} returns a result code, or throws an exception if the language supports exceptions. The result code must be checked, and any exception caught, to ensure each operation is successful. Ignoring results will in the best case cause programs to crash, and in the worst, lead to invalid or unexpected behavior.

== Use Event Handlers ==
The Phidget library supports both polling channel properties to determine state and to get current data values, and the library supports firing events when states change and data is received. Reading channel properties directly is useful to determine the state or current data value at a point in time, but is difficult to implement correctly. Event handlers are more predicable and easier to implement correctly. Unless a program has a specific and obvious reason to access properties directly, event handlers should be used.

== Set Properties in the Attach Handler ==

An attach event will occur each time a channel is matched. This makes the attach handler the perfect place to initialize properties such as {{Code|DataInterval}}, {{Code|ChangeTrigger}}, gain values, and ranges. If properties are initialize elsewhere, in a situation where the channel detaches temporarily, those properties will revert to defaults during the next attach. Setting properties within the attach handler ensures they are always the expected values.

== Keep Event Handlers Short ==

Events handlers are called from special dispatch threads within the Phidget library. Each channel maintains its own queue of events, and these events are processed in order and one at a time. If a user event handler blocks, or takes longer than the <code>DataInterval</code> of the channel, events will become 'stale', and eventually the system will begin throwing away events.

For example, if an Accelerometer channel has been configured to receive data every 20 milliseconds and the event handler averages 21ms to execute, the next change event will be ready before the previous one is finished being processed. Eventually the channel's event queue will fill and the library will begin throwing away events.

A common mistake is to update a GUI, or wait for user input from within an event handler. Most GUI APIs have support for dispatching updates to the GUI thread, and those should be used. Waiting for user input will block the event handler, and should never be done. Instead, a flag should be set and a loop in another thread should wait for the input.

== Be Specific With Addressing ==

When you open a Phidget channel, the library tries to attach a channel matching all the addressing properties that have been set. If none of the matching properties are set, the Phidget library will match the first channel of the same class. In simple cases this will be fine. If your program deals with multiple Phidgets, it is always wise to be specific.

For example, if a Phidget temperature sensor is the only device connected to a computer, opening a {{Code|TemperatureSensor}} channel without setting any addressing properties will attach to that temperature sensor; however, if a DC motor controller is connected to the computer, the on-board temperature sensor on the motor controller might attach to the channel instead. This could be prevented by setting a {{code|DeviceSerialNumber}} or {{code|HubPort}}.

Since there's no way to predict what other Phidgets may be plugged into a computer (or become available over the network), you should be as specific as possible before opening a channel.

== Don't Forget to Close() ==

Calling {{Code|Close()}} on a channel releases the channel so that it can be matched again, and to ensure your Phidget has stopped. For example, certain motor controllers will maintain speed or continue trying to track the last position they were sent to, if they are not stopped or closed before the program ends. In [[Language_-_LabVIEW|LabVIEW]], the runtime environment executes a program internally, so if {{Code|Close()}} is not called, the LabVIEW environment will continue to tie up the channel despite the program having been stopped.

== When In Doubt, Open Remotely ==
When the [[Phidget Network Server|Network Server]] is enabled, a channel can match both a local device channel and a remote channel. The end result would be functionally the same; however, most remote channels support being attached to multiple clients, while a local device channel can only be attached once. Unless the desire is to only allow the device channel to be attached once, or performance is critical, it is more flexible to match the network channel as other clients will still be able to attach to the device channel.

See the <code>IsRemote</code> and <code>IsLocal</code> Phidget properties in the {{Phidget22API}}.

== Further Reading ==

[[Phidget Programming Basics]] - Here you can find the basic concepts to help you get started with making your own programs that use Phidgets.

[[Data Interval/Change Trigger]] - Learn about these two properties that control how much data comes in from your sensors.

[[Using Multiple Phidgets]] - It can be difficult to figure out how to use more than one Phidget in your program. This page will guide you through the steps.

[[Polling vs. Events]] - Your program can gather data in either a polling-driven or event-driven manner. Learn the difference to determine which is best for your application.

[[Logging, Exceptions, and Errors]] - Learn about all the tools you can use to debug your program.

[[Phidget Network Server]] - Phidgets can be controlled and communicated with over your network- either wirelessly or over ethernet.

File:3334+3323.jpg

2018-11-27T15:59:06Z

Burley:

File:Unknown measurement.png

2018-11-27T15:58:57Z

Burley:

File:Linear regression.png

2018-11-27T15:58:44Z

Burley:

File:Initial data.png

2018-11-27T15:58:33Z

Burley:

File:Loadcell scale 2.jpg

2018-11-27T15:58:11Z

Burley:

File:Loadcell scale.jpg

2018-11-27T15:57:55Z

Burley:

OS - macOS

2018-01-03T17:55:30Z

Burley:

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

==Quick Downloads==
Already know what you're doing? Here you go:
*[{{SERVER}}/downloads/phidget22/libraries/macos/Phidget22.dmg macOS Installer Download]
*[[Software License]]

If you need older versions of the Phidget22 macOS libraries, [{{SERVER}}/downloads/phidget22/libraries/macos/Phidget22/ click here].

If you need Phidget21 macOS libraries, [{{SERVER}}/downloads/phidget21/libraries/macos/Phidget/ click here].

==Getting Started with macOS==
Welcome to using Phidgets with macOS. If you are ready to go, the first step in creating macOS applications with Phidgets is installing our libraries!

===Install===
To install our libraries, download the installer for your machine:
*[{{SERVER}}/downloads/phidget22/libraries/macos/Phidget22.dmg macOS installer download]

Next, open up the installer, and double click on ''Phidgets.pkg'' to install the libraries:
[[File:OSX Install 1.png|link=|alt=macOS Install|center]]

When prompted, continue with the installation:
[[File:OSX Install 2.png|link=|alt=macOS Install|center]]

If you are using OS X 10.13 or newer you will also need to give explicit permission for the driver to function. You can read about this here[https://developer.apple.com/library/content/technotes/tn2459/_index.html].

The libraries are now installed on your machine. Next, let's verify that they are working properly.

===Verify===
The best way to verify that your libraries are working properly is to use the Phidget Control Panel. The control panel is a powerful tool that will help you develop your Phidgets applications. Get started by following the instructions below:

Open Finder and navigate to the Phidget Control Panel in the Applications list:
[[File:OSX Finder Apps.png|link=|900px|alt=macOS Finder Apps|center]]

Double-click on the Phidgets icon to bring up the Phidget Control Panel. You can now see all the Phidgets that are plugged into your machine, as well as any Phidgets that are on the network:
[[File:OSX ControlPanel General.png|link=|alt=macOS Control Panel General|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:OSX Control Panel Channel.png ‎|link=|alt=macOS Control Panel Channel|center]]

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

Your Phidget is now able to communicate with your development machine. The next step is selecting a programming language so you can start to write some code!

==Programming==
Ready to write some code? Select one of the programming languages below:

''Great choices for beginners:''
* [[Language - C|C]]
* [[Language - C Sharp|C#]]
* [[Language - Python | Python]]
* [[Language - Java | Java]]
''Also supported:''
* [[Language - Objective C | Objective-C]]
* [[Language - JavaScript | JavaScript]]
* [[Language - Swift | Swift]]
* [[Language - Max/MSP|Max/MSP]]

==Phidget Network Server==
The Phidget Network Server is an extremely useful tool that allows you to remotely control Phidgets over your network. If you haven't already, check out the [[Phidget Network Server]] page for a complete overview.

===Try it Out!===
In order to try the Phidget Network Server out, you will need a host computer, and a client computer:
*'''Host computer:''' the computer that is physically connected to the Phidgets via USB and is running the Phidget Network Server.
*'''Client computer:''' a computer running a Phidgets application that accesses Phidgets connected to the host computer.
If you only have one computer, don't worry, your machine can act as both a host and a client.

Next, open the Phidget Control Panel on your host computer. Do this by double-clicking on the [[File:Ph.jpg|link=]] icon in your applications folder. Navigate to the Network Server tab, you will see the following:
[[File:macos_networkserver.png|link=|center]]

From here, you can start or stop the Network Server. You can also decide when the Network Server will start.
[[File:macos_networkserver_run.png|link=|center]]

Check the automatic start box and enter a server name. By enabling automatic startup, the Network Server will run immediately after macOS boots, so you won't have to manually start it again. You can verify the Network Server is running by looking at the label beside the start/stop button.

Now that you have the Network Server running on your host computer, the next step will be accessing the Phidgets connected to your host computer from your client computer. Follow the steps below:

Open the Phidget Control Panel on your client computer. You will see something like this:
[[File:macos_controlpanel_remote.png|link=|center]]

As you can see from the image above, Phidget servers are listed under the following heading:
*Remote Server: Servername

You now have access to the Phidgets that are connected to your host computer. Try double-clicking one of them to bring up an example:
[[File:macos_controlpanel_remoteexample.png|link=|center]]

Note the label in the example indicating a remote connection. This means the example is using the Phidget Network Server in order to communicate with the device.

===What's Next?===
Now that you have seen the Phidget Network Server in action, you may be interested in implementing an application that takes advantage of all it's features. Luckily, every programming language we support comes with example code on how to do this! Jump to [[#Programming|programming languages]] above.

For more information about the Network Server tab on the Phidget Control Panel, visit the Visit the [[Phidget Control Panel|Phidget Control Panel]] page.

==Advanced Information==
===Installed Files===
These files were placed onto your system as part of the installation process:
{| class="wikitable"
|-
| align="center" style="background:#f0f0f0;"|'''File'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Location'''
|-
|Phidget22.framework||contains our library, which is used at run-time.||/Library/Frameworks
|-
|Phidget.kext||kernel extension.||/System/Library/Extensions
|-
|phidgetnetworkserver22||Phidget Network Server||/usr/local/bin
|-
|}

OS - macOS

2018-01-03T17:55:10Z

Burley:

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

==Quick Downloads==
Already know what you're doing? Here you go:
*[{{SERVER}}/downloads/phidget22/libraries/macos/Phidget22.dmg macOS Installer Download]
*[[Software License]]

If you need older versions of the Phidget22 macOS libraries, [{{SERVER}}/downloads/phidget22/libraries/macos/Phidget22/ click here].

If you need Phidget21 macOS libraries, [{{SERVER}}/downloads/phidget21/libraries/macos/Phidget/ click here].

==Getting Started with macOS==
Welcome to using Phidgets with macOS. If you are ready to go, the first step in creating macOS applications with Phidgets is installing our libraries!

===Install===
To install our libraries, download the installer for your machine:
*[{{SERVER}}/downloads/phidget22/libraries/macos/Phidget22.dmg macOS installer download]

Next, open up the installer, and double click on ''Phidgets.pkg'' to install the libraries:
[[File:OSX Install 1.png|link=|alt=macOS Install|center]]

When prompted, continue with the installation:
[[File:OSX Install 2.png|link=|alt=macOS Install|center]]

If you are using OS X 10.13 or newer you will also need to give explicit permission for the driver to function. You can read about this [here|https://developer.apple.com/library/content/technotes/tn2459/_index.html].

The libraries are now installed on your machine. Next, let's verify that they are working properly.

===Verify===
The best way to verify that your libraries are working properly is to use the Phidget Control Panel. The control panel is a powerful tool that will help you develop your Phidgets applications. Get started by following the instructions below:

Open Finder and navigate to the Phidget Control Panel in the Applications list:
[[File:OSX Finder Apps.png|link=|900px|alt=macOS Finder Apps|center]]

Double-click on the Phidgets icon to bring up the Phidget Control Panel. You can now see all the Phidgets that are plugged into your machine, as well as any Phidgets that are on the network:
[[File:OSX ControlPanel General.png|link=|alt=macOS Control Panel General|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:OSX Control Panel Channel.png ‎|link=|alt=macOS Control Panel Channel|center]]

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

Your Phidget is now able to communicate with your development machine. The next step is selecting a programming language so you can start to write some code!

==Programming==
Ready to write some code? Select one of the programming languages below:

''Great choices for beginners:''
* [[Language - C|C]]
* [[Language - C Sharp|C#]]
* [[Language - Python | Python]]
* [[Language - Java | Java]]
''Also supported:''
* [[Language - Objective C | Objective-C]]
* [[Language - JavaScript | JavaScript]]
* [[Language - Swift | Swift]]
* [[Language - Max/MSP|Max/MSP]]

==Phidget Network Server==
The Phidget Network Server is an extremely useful tool that allows you to remotely control Phidgets over your network. If you haven't already, check out the [[Phidget Network Server]] page for a complete overview.

===Try it Out!===
In order to try the Phidget Network Server out, you will need a host computer, and a client computer:
*'''Host computer:''' the computer that is physically connected to the Phidgets via USB and is running the Phidget Network Server.
*'''Client computer:''' a computer running a Phidgets application that accesses Phidgets connected to the host computer.
If you only have one computer, don't worry, your machine can act as both a host and a client.

Next, open the Phidget Control Panel on your host computer. Do this by double-clicking on the [[File:Ph.jpg|link=]] icon in your applications folder. Navigate to the Network Server tab, you will see the following:
[[File:macos_networkserver.png|link=|center]]

From here, you can start or stop the Network Server. You can also decide when the Network Server will start.
[[File:macos_networkserver_run.png|link=|center]]

Check the automatic start box and enter a server name. By enabling automatic startup, the Network Server will run immediately after macOS boots, so you won't have to manually start it again. You can verify the Network Server is running by looking at the label beside the start/stop button.

Now that you have the Network Server running on your host computer, the next step will be accessing the Phidgets connected to your host computer from your client computer. Follow the steps below:

Open the Phidget Control Panel on your client computer. You will see something like this:
[[File:macos_controlpanel_remote.png|link=|center]]

As you can see from the image above, Phidget servers are listed under the following heading:
*Remote Server: Servername

You now have access to the Phidgets that are connected to your host computer. Try double-clicking one of them to bring up an example:
[[File:macos_controlpanel_remoteexample.png|link=|center]]

Note the label in the example indicating a remote connection. This means the example is using the Phidget Network Server in order to communicate with the device.

===What's Next?===
Now that you have seen the Phidget Network Server in action, you may be interested in implementing an application that takes advantage of all it's features. Luckily, every programming language we support comes with example code on how to do this! Jump to [[#Programming|programming languages]] above.

For more information about the Network Server tab on the Phidget Control Panel, visit the Visit the [[Phidget Control Panel|Phidget Control Panel]] page.

==Advanced Information==
===Installed Files===
These files were placed onto your system as part of the installation process:
{| class="wikitable"
|-
| align="center" style="background:#f0f0f0;"|'''File'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Location'''
|-
|Phidget22.framework||contains our library, which is used at run-time.||/Library/Frameworks
|-
|Phidget.kext||kernel extension.||/System/Library/Extensions
|-
|phidgetnetworkserver22||Phidget Network Server||/usr/local/bin
|-
|}

OS - macOS

2018-01-03T17:54:37Z

Burley:

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

==Quick Downloads==
Already know what you're doing? Here you go:
*[{{SERVER}}/downloads/phidget22/libraries/macos/Phidget22.dmg macOS Installer Download]
*[[Software License]]

If you need older versions of the Phidget22 macOS libraries, [{{SERVER}}/downloads/phidget22/libraries/macos/Phidget22/ click here].

If you need Phidget21 macOS libraries, [{{SERVER}}/downloads/phidget21/libraries/macos/Phidget/ click here].

==Getting Started with macOS==
Welcome to using Phidgets with macOS. If you are ready to go, the first step in creating macOS applications with Phidgets is installing our libraries!

===Install===
To install our libraries, download the installer for your machine:
*[{{SERVER}}/downloads/phidget22/libraries/macos/Phidget22.dmg macOS installer download]

Next, open up the installer, and double click on ''Phidgets.pkg'' to install the libraries:
[[File:OSX Install 1.png|link=|alt=macOS Install|center]]

When prompted, continue with the installation:
[[File:OSX Install 2.png|link=|alt=macOS Install|center]]

If you are using OS X 10.13 or newer you will also need to give explicit permission for the driver to function. You can read about this here:

[https://developer.apple.com/library/content/technotes/tn2459/_index.html]

The libraries are now installed on your machine. Next, let's verify that they are working properly.

===Verify===
The best way to verify that your libraries are working properly is to use the Phidget Control Panel. The control panel is a powerful tool that will help you develop your Phidgets applications. Get started by following the instructions below:

Open Finder and navigate to the Phidget Control Panel in the Applications list:
[[File:OSX Finder Apps.png|link=|900px|alt=macOS Finder Apps|center]]

Double-click on the Phidgets icon to bring up the Phidget Control Panel. You can now see all the Phidgets that are plugged into your machine, as well as any Phidgets that are on the network:
[[File:OSX ControlPanel General.png|link=|alt=macOS Control Panel General|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:OSX Control Panel Channel.png ‎|link=|alt=macOS Control Panel Channel|center]]

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

Your Phidget is now able to communicate with your development machine. The next step is selecting a programming language so you can start to write some code!

==Programming==
Ready to write some code? Select one of the programming languages below:

''Great choices for beginners:''
* [[Language - C|C]]
* [[Language - C Sharp|C#]]
* [[Language - Python | Python]]
* [[Language - Java | Java]]
''Also supported:''
* [[Language - Objective C | Objective-C]]
* [[Language - JavaScript | JavaScript]]
* [[Language - Swift | Swift]]
* [[Language - Max/MSP|Max/MSP]]

==Phidget Network Server==
The Phidget Network Server is an extremely useful tool that allows you to remotely control Phidgets over your network. If you haven't already, check out the [[Phidget Network Server]] page for a complete overview.

===Try it Out!===
In order to try the Phidget Network Server out, you will need a host computer, and a client computer:
*'''Host computer:''' the computer that is physically connected to the Phidgets via USB and is running the Phidget Network Server.
*'''Client computer:''' a computer running a Phidgets application that accesses Phidgets connected to the host computer.
If you only have one computer, don't worry, your machine can act as both a host and a client.

Next, open the Phidget Control Panel on your host computer. Do this by double-clicking on the [[File:Ph.jpg|link=]] icon in your applications folder. Navigate to the Network Server tab, you will see the following:
[[File:macos_networkserver.png|link=|center]]

From here, you can start or stop the Network Server. You can also decide when the Network Server will start.
[[File:macos_networkserver_run.png|link=|center]]

Check the automatic start box and enter a server name. By enabling automatic startup, the Network Server will run immediately after macOS boots, so you won't have to manually start it again. You can verify the Network Server is running by looking at the label beside the start/stop button.

Now that you have the Network Server running on your host computer, the next step will be accessing the Phidgets connected to your host computer from your client computer. Follow the steps below:

Open the Phidget Control Panel on your client computer. You will see something like this:
[[File:macos_controlpanel_remote.png|link=|center]]

As you can see from the image above, Phidget servers are listed under the following heading:
*Remote Server: Servername

You now have access to the Phidgets that are connected to your host computer. Try double-clicking one of them to bring up an example:
[[File:macos_controlpanel_remoteexample.png|link=|center]]

Note the label in the example indicating a remote connection. This means the example is using the Phidget Network Server in order to communicate with the device.

===What's Next?===
Now that you have seen the Phidget Network Server in action, you may be interested in implementing an application that takes advantage of all it's features. Luckily, every programming language we support comes with example code on how to do this! Jump to [[#Programming|programming languages]] above.

For more information about the Network Server tab on the Phidget Control Panel, visit the Visit the [[Phidget Control Panel|Phidget Control Panel]] page.

==Advanced Information==
===Installed Files===
These files were placed onto your system as part of the installation process:
{| class="wikitable"
|-
| align="center" style="background:#f0f0f0;"|'''File'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Location'''
|-
|Phidget22.framework||contains our library, which is used at run-time.||/Library/Frameworks
|-
|Phidget.kext||kernel extension.||/System/Library/Extensions
|-
|phidgetnetworkserver22||Phidget Network Server||/usr/local/bin
|-
|}

Terms and Conditions

2017-10-25T16:28:42Z

Burley:

[[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 issue you an RMA number and will replace your defective product free of charge.

==Shipping==
===Last Call at 12:00PM===
Unless we are unusually busy most orders received before 12:00 PM Mountain Time - Canada (GMT-07:00) Monday to Friday will be shipped on the same day.

Orders which contain cut to length parts may not necessarily ship same day as there is significant processing time associated with these orders.

===Shipping Costs===
The shipping cost is calculated at Checkout and submitted for your review before you confirm your order. When multiple shipping options are available for your destination, we will list all available options and let you choose.

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

If you have your own account with UPS, you can use it and be billed directly by them. In that case you have more shipping options available to you.

===Shipping in Canada===
We use UPS Express Saver™ - Overnight delivery, and UPS Standard - 3 to 5 business days ground delivery.

===Shipping to the United States===

====UPS Express Saver™ - Overnight====

'''Shipments under $2000.00USD''': we pay all costs in bringing the goods to you including import duties and taxes. In other words your shipping costs are what we put on our invoice. Contact us if you are getting any extra invoices from UPS.

'''Shipments over $2000.00USD''': you are responsible for duty and taxes if applicable and will have to pay UPS directly on top of the shipping cost we put on our invoice.

====UPS Standard - Ground 3 to 5 business days====
'''Shipments under $800.00USD''': we pay all costs in bringing the goods to you including import duties and taxes. In other words your shipping costs are what we put on our invoice. Contact us if you are getting any extra invoices from UPS.

'''Shipment over $800.00USD''' UPS will collect Entry Preparation Fees directly from you when delivering the package, and for duty and taxes if applicable.

:'''Entry Preparation Fees'''
:*All rates are in U.S. funds
:*Rates do not include applicable duties or taxes

{| style="border:1px solid darkgray;" cellpadding="7px;"
|-style="background: #d1d1d1" align=center
! Value for duty|| UPS Standard Service
|-
|style="background: #f0f0f0" align=center|$0.00 to $800.00
|style="background: #f0f0f0" align=center|No Charge
|-
|style="background: #f0f0f0" align=center|$800.01 to $1,250.00
|style="background: #f0f0f0" align=center|$28.75
|-
|style="background: #f0f0f0" align=center|$1,250.01 to $2,500.00
|style="background: #f0f0f0" align=center|$40.50
|-
|style="background: #f0f0f0" align=center|Each Additional $1,000.00
|style="background: #f0f0f0" align=center|$1.95
|}

===International Shipments===
We use UPS Worldwide Express Saver™, and UPS Worldwide Expedited for international locations that cannot be reached with Express Saver.

Goods shipped to an international destination may be subject to import duties and taxes, which are levied once the goods reach your country. Additional charges for customs clearance must be borne by you; we have no control over these charges and cannot predict what they may be. Since customs policies vary widely from country to country, you should contact your local customs office for further information.

===Tracking your order===
You can track your shipment by going to www.UPS.ca and using the tracking number that was e-mailed to you when your order 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, when the package arrives there is no one to accept delivery UPS will redeliver 2 more times. This is standard UPS protocol. If delivery fails they will keep the package for 5 days and then return it to us. We will then refund you the cost you paid minus the cost of shipping (both directions) and a flat $50 charge to a maximum of the total cost of the package. This applies to packages which failed delivery due to no one being present as well as packages which were refused delivery by a person at the delivery location.

===Import Restrictions to Russia===
If you are wanting to ship an order to Russia you MUST have a valid business license number in order to complete the shipment. This must be added to your account on our website. To modify the business number, you can go to your account page and edit the "Account Information" section. This number will then be applied to all orders placed with that account. The reason for this is best explained by UPS:

"Customs authorities in Russia have tightened restrictions on import shipments to Russia, in particular on dutiable shipments sent to private individuals. These shipments are currently under extraordinary scrutiny in an effort to improve accuracy of the accompanying shipping documentation. These additional requirements lead to an unprecedented number of customs holds and delays in delivery. UPS has therefore temporarily suspended the acceptance of dutiable shipments sent to private individuals in Russia until further notice. We regret this step and are confident that, together with the Russian customs authorities, a solution can be found. UPS continues to accept all non-dutiable document shipments to private individuals in Russia and all commercial shipments addressed to businesses." [http://www.ups.com/content/hr/en/about/news/service_updates/20100526_restrictions.html]

==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 will take back any unopened product for a period of 30 days from the date of purchase. Just call or e-mail us for a RMA number and ship the product back to Phidgets prepaid and we will refund your credit card as soon as we receive and inspect the returned goods.

Products that are returned after 30 days are subject to a re-stocking charge of 25% of the package's value (minimum $5.00) to a maximum of $500.

We do '''not''' accept returns after 90 days.

===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
|+'''Phidgets Inc. Holidays'''
! Holiday || Description || 2016 || 2017
|-
|style="background: #f0f0f0" align=center| New Year's Holiday
|style="background: #f0f0f0" align=center| First two days of January
|style="background: #f0f0f0" align=center| Jan 1
|style="background: #f0f0f0" align=center| Jan 1
|-
|style="background: #f0f0f0" align=center| Alberta Family Day
|style="background: #f0f0f0" align=center| Third Monday in February
|style="background: #f0f0f0" align=center| Feb 15
|style="background: #f0f0f0" align=center| Feb 20
|-
|style="background: #f0f0f0" align=center| Good Friday
|style="background: #f0f0f0" align=center| Friday before Easter Sunday
|style="background: #f0f0f0" align=center| Mar 25
|style="background: #f0f0f0" align=center| Apr 14
|-
|style="background: #f0f0f0" align=center| Victoria Day
|style="background: #f0f0f0" align=center| Monday before May 25
|style="background: #f0f0f0" align=center| May 23
|style="background: #f0f0f0" align=center| May 22
|-
|style="background: #f0f0f0" align=center| Canada Day
|style="background: #f0f0f0" align=center| First day of July
|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 1
|style="background: #f0f0f0" align=center| Aug 7
|-
|style="background: #f0f0f0" align=center| Labour Day
|style="background: #f0f0f0" align=center| First Monday in September
|style="background: #f0f0f0" align=center| Sept 4
|style="background: #f0f0f0" align=center| Sept 4
|-
|style="background: #f0f0f0" align=center| Thanksgiving
|style="background: #f0f0f0" align=center| Second Monday in October
|style="background: #f0f0f0" align=center| Oct 10
|style="background: #f0f0f0" align=center| Oct 9
|-
|style="background: #f0f0f0" align=center| Remembrance Day
|style="background: #f0f0f0" align=center| November 11
|style="background: #f0f0f0" align=center| Nov 11
|style="background: #f0f0f0" align=center| Nov 11
|-
|style="background: #f0f0f0" align=center| Christmas Holiday
|style="background: #f0f0f0" align=center| Dec 22 to the New Year
|style="background: #f0f0f0" align=center| Dec 22 to the New Year
|style="background: #f0f0f0" align=center| TBA
|-
|}

Using Multiple Phidgets

2017-09-27T14:23:32Z

Burley:

[[Category:Programming]]

When only one Phidget is connected to a computer, it is pretty easy for a simple program to open and attach to the channels on that one Phidget; however, when the program becomes more complicated or more than one Phidget is connected, attaching to the correct channel can be more difficult.

Before opening a channel, it is important to set enough of the matching properties to ensure the desired device channel is matched. By default, the matching code in the Phidget library will match the first available device channel that is of the correct class. For example, if two temperature sensor devices are connected to a computer, it is undefined which will attach when the device serial number is not specified before the channel is opened.

The best practice is to always specify at least the device serial number and the channel ID of the device channel that should be attached to the user channel. Even when not strictly necessary, setting as many matching properties as possible can ensure that code will not break in the future.

===Using the Channel ID===

Each channel exported by a Phidget device has an id, normally starting at 0. The {{Code|channel}} property must be set to ensure the device channel the Phidget software library matches is right one. If a 4-channel temperature sensor is connected, and the {{Code|channel}} property is not specified, the matching code will attach to channel 0 if available, and the next available channel if not.

Set the '''channel id''' with the {{Code|Channel}} property.

===Using the Hub Port===

VINT hubs have a number of ports that VINT devices can be connected to. To ensure the correct VINT device is attached, the hub port must be specified. If two temperature sensors are attached to the same hub, and the hub port is not specified prior to opening a channel, it is undefined which temperature sensor will be attached.

Set the '''hub port''' with the {{Code|HubPort}} property.

===Using the Serial Number===

Each Phidget has a unique serial number (VINT devices inherit the serial number of the hub). When there is more than one device that exports the same channel class, the device serial number must be specified to ensure the channel on the desired device is matched. The device serial number can be found on a label on the bottom of the Phidget, or determined by reading the {{Code|DeviceSerialNumber}} property.

Set the '''device serial number''' with the {{Code|DeviceSerialNumber}} property.

===Using the Label===

Most Phidgets can be assigned a label that may be used as a human-readable way to reference them (VINT devices inherit the serial number of the hub). In software that will be distributed, or cannot easily be modified it is useful to attach to channels based on the label of the device. This way, the device can be labelled prior to running the software, and the new device will be matched

Set the '''device label''' with the {{Code|DeviceLabel}} property.

Some limitations are:
* In [[OS - Windows|Windows]], label can be read on any Phidget that has a serial number, but label can only be written for Phidgets that support firmware upgrading.
* Some programming languages do not support writing to labels. See the {{Phidget22API}}.

===Code Examples===

For example, in Java, this would be:
<div class="source">
<syntaxhighlight lang=java>
ch.setDeviceSerialNumber(12345); // match device 12345
ch.setHubPort(4); // match hub port 4
ch.setChannel(1); // match channel 1 port 4 dev 12345
ch.open(); // start matching

//for a second device simply repeat this process
ch1.setDeviceSerialNumber(12345);
ch1.setHubPort(3);
ch1.setChannel(1);
ch1.open();
//and so on
.
.
.
</syntaxhighlight>
</div>

Or in C:
<div class="source">
<syntaxhighlight lang=c>
Phidget_setDeviceSerialNumber((PhidgetHandle)ch, 12345); // match device 12345
Phidget_setHubPort((PhidgetHandle)ch, 4); // match hub port 4
Phidget_setChannel((PhidgetHandle)ch, 1); // match channel 1 port 4 dev 12345
Phidget_open((PhidgetHandle)ch); // start matching

//for a second device simply repeat this process
Phidget_setDeviceSerialNumber((PhidgetHandle)ch1, 12345);
Phidget_setHubPort((PhidgetHandle)ch1, 2);
Phidget_setChannel((PhidgetHandle)ch1, 1);
Phidget_open((PhidgetHandle)ch1);
//and so on
.
.
.
</syntaxhighlight>
</div>

===Distinguishing Events===

When using [[Polling vs. Events|events]], it is recommended that a different event handler be used for each channel to simplify the code and prevent programming errors. In the case where it is not practical to write an individual handler for each channel, the matching properties of the channel can be read to determine what device channel the event is from.

Prior to the channel being attached to a device channel, the matching properties will return the values that will be used to perform the match; however, once the channel is attached, the matching properties will return the physical values from the device channel. For example, if '''serial number''' has not been specified, {{Code|DeviceSerialNumber}} would be {{Code|PHIDGET_SERIALNUMBER_ANY}}, but once attached {{Code|DeviceSerialNumber}} would be the serial number of the attached device.

=== Further Reading ===

[[Phidget Programming Basics]] - Here you can find the basic concepts to help you get started with making your own programs that use Phidgets.

[[Data Interval/Change Trigger]] - Learn about these two properties that control how much data comes in from your sensors.

[[Polling vs. Events]] - Your program can gather data in either a polling-driven or event-driven manner. Learn the difference to determine which is best for your application.

[[Logging, Exceptions, and Errors]] - Learn about all the tools you can use to debug your program.

[[Phidget Network Server]] - Phidgets can be controlled and communicated with over your network- either wirelessly or over ethernet.

[[Best Phidgets Practices]] - Good programming habits that will save you from common problems when writing code for your Phidgets.

Language - Visual Basic

2017-09-06T14:18:16Z

Burley:

[[Category:Language]]
__TOC__

== Quick Downloads ==

=== Documentation ===

*{{Phidget22API}} (Select C#/VB.Net from drop-down menu)

=== Example Code ===

*{{SampleCode|VBNET|VB.Net Examples}}

=== Libraries ===

{{WindowsQuickDownloads}}

== Getting Started with VB.NET ==
Welcome to using Phidgets with VB.NET! By using VB.NET, you will have access to the complete {{Phidget22API}}, including events. We also provide example code in VB.NET for all Phidget devices.

== Windows ==
{{Windows_Languages}}

===Visual Studio===
====Use our examples====
One of the best ways to start programming with Phidgets is to use our example code as a guide. In order to run the examples, you will need to download and install [https://www.visualstudio.com/ Microsoft Visual Studio].

Now that you have Microsoft Visual Studio installed, select an example that will work with your Phidget:
*{{SampleCode|VBNET|VB.NET Examples}}

Open the example project and start the example by pressing the ''Start'' button:

[[File:Csharp_visualstudio_run.png ‎|link=|center]]

The application will open the Phidget, list basic information about the Phidget, and demonstrate the Phidget's functionality. Here is an example of a Digital Output channel on a RFID Phidget:

[[File:Csharp_visualstudio_rfid.PNG|link=|center]]

You should now have the example up and running for your device. Play around with the device and experiment with some of the functionality. When you are ready, the next step is configuring your project and writing your own code!

=====VINT Hub=====
If you are trying to connect to one of the VINT hub ports directly rather than to a VINT device connected through a VINT hub then there is one additional step. There is a isHubPort property of the Phidget class that must be set before calling open. It defaults to false but in this case it will need to be set to true. In our examples this is done via command line though in practice you can just set it before calling open. To add command line parameters to your project in Visual Studio, you can go to the Project->Properties screen. Under the Debug section there is a field to enter command line parameters for startup. Use "-h" to make sure isHubPort is set before open is called and then you should be good to go.

[[File:Csharp_visualstudio_commandLineParameters.png|link=|center]]

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

Create a new Windows Forms Application project:

[[Image:Vbnet_newproject.PNG|link=|center]]

Next, right-click to add a reference to the Phidget .NET library:

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

On the following screen, click ''Browse...'' and navigate to the location of Phidget22.NET.dll:
*C:\Program Files\Phidgets\Phidget22\Phidget22.NET.dll

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

Finally, to include the Phidget .NET library, add the following lines to main window class file:

<syntaxhighlight lang="csharp">
Imports Phidget22
Imports Phidget22.Events
</syntaxhighlight>

Success! The project now has access to Phidgets. Next, view the [[#Write Code | write your own code]] section located below.

===Mono===
====Use Our Examples====
One of the best ways to start programming with Phidgets is to use our example code as a guide. In order to run the examples, you will need to download and install [http://www.mono-project.com/download/ Mono] for Windows.

Now that you have Mono installed, download and unpack the HelloWorld example for C#:
*[{{SERVER}}/downloads/phidget22/examples/dotnet/csharp/Manager/Phidget22_HelloWorld_CSharp_Windows_Ex.zip HelloWorld example]
Note: The HelloWorld example is compatible with Mono because it does not use Windows Forms. All other C# examples use Windows Forms.

Next, copy Phidget22.NET.dll from type the following location:
*C:\Program Files\Phidgets\Phidget22\Phidget22.NET.dll

Place both the HelloWorld example and the Phidget22.NET.dll file in the same location. Your folder should now look something like this:
[[File:Vbnet_folder.PNG|link=|center]]

Open the command prompt at the folder location and enter the following command:
<syntaxhighlight lang='bash'>
vbnc /r:Phidget22.NET.dll Module1.vb
</syntaxhighlight>

This will create an executable file called ''Module1.exe''. Type in the following command to run the example:
<syntaxhighlight lang='bash'>
mono Module1.exe
</syntaxhighlight>

[[File:Vbnet_mono.PNG|link=|center]]

You should now have the example up and running. When you are ready, the next step is configuring your project and writing your own code!

====Configure your project====
When you are building a project from scratch, or adding Phidget functionality to an exisiting project, you'll need to configure your development environment to properly link the Phidget .NET library.

To include the Phidget .NET library, simply add the following lines to your code:
<syntaxhighlight lang='CSharp'>
Imports Phidget22
Imports Phidget22.Events
</syntaxhighlight>

The project now has access to Phidgets. Next, view the [[#Write Code | write your own code]] section located below.

==Write Code==
{{WriteCode_Intro}}

=== Step One: Initialize and Open ===
You will need to declare your Phidget object in your code. For example, we can declare a digital input object like this:
<syntaxhighlight lang='vbnet'>
ch = New Phidget22.DigitalInput()
</syntaxhighlight>

Next, we can open the Phidget object like this:
<syntaxhighlight lang='vbnet'>
ch.Open()
</syntaxhighlight>

Although we are not including it on this page, you should include error handling for all Phidget functions. Here is an example of the previous code with error handling:
<syntaxhighlight lang='vbnet'>
Try
ch = New Phidget22.DigitalInput()
ch.Open()
Catch ex As PhidgetException
errorBox.addMessage("Error initializing: " + ex.Message)
End Try
</syntaxhighlight>

=== Step Two: Wait for Attachment (plugging in) of the Phidget ===
Simply calling open does not guarantee you can use the Phidget immediately. To use a Phidget, it must be plugged in (attached). We can handle this by using event driven programming and tracking the attach events. Alternatively, we can modify our code so we wait for an attachment:
<syntaxhighlight lang='vbnet'>
ch = New Phidget22.DigitalInput()
ch.Open(5000);
</syntaxhighlight>
Waiting for attachment will block indefinitely until a connection is made, or until the timeout value is exceeded

To use events to handle attachments, we have to add the following code:
<syntaxhighlight lang='vbnet'>
Private Sub device_Attach(ByVal sender As Object, ByVal e As Phidget22.Events.AttachEventArgs) Handles ch.Attach
Console.WriteLine("Phidget Attached!");
End Sub
</syntaxhighlight>

=== Step Three: Do Things with the Phidget ===
We recommend the use of event driven programming when working with Phidgets. In a similar way to handling an attach event as described above, we can also add an event handler for a state change event:
<syntaxhighlight lang=vbnet>
Private Sub device_DigitalInputChange(ByVal sender As Object, ByVal e As Phidget22.Events.DigitalInputStateChangeEventArgs) Handles ch.StateChange
stateText.Text = "State: " + e.State;
End Sub
</syntaxhighlight>

If events do not suit your needs, you can also poll the device directly for data using code like this:
<syntaxhighlight lang=vbnet>
state= device.State;
stateText.Text = "State: " + e.State;
</syntaxhighlight>

=== Step Four: Close and Delete ===
At the end of your program, be sure to close and delete your device:
<syntaxhighlight lang=vbnet>
device.Close();
</syntaxhighlight>

== Further Reading ==

[[Phidget Programming Basics]] - Here you can find the basic concepts to help you get started with making your own programs that use Phidgets.

[[Data Interval/Change Trigger]] - Learn about these two properties that control how much data comes in from your sensors.

[[Using Multiple Phidgets]] - It can be difficult to figure out how to use more than one Phidget in your program. This page will guide you through the steps.

[[Polling vs. Events]] - Your program can gather data in either a polling-driven or event-driven manner. Learn the difference to determine which is best for your application.

[[Logging, Exceptions, and Errors]] - Learn about all the tools you can use to debug your program.

[[Phidget Network Server]] - Phidgets can be controlled and communicated with over your network- either wirelessly or over ethernet.

Language - C Sharp

2017-09-06T14:17:03Z

Burley:

[[Category:Language]]
__TOC__

== Quick Downloads ==
=== Documentation ===

*{{Phidget22API}} (Select C# from drop-down menu)

=== Example Code ===

*{{SampleCode|CSharp|C# Examples}}

===Libraries===

{{AllQuickDownloads}}

== Getting started with C# ==
Welcome to using Phidgets with C#! By using C#, you will have access to the complete {{Phidget22API}}, including events. We also provide example code in C# for all Phidget devices.

If you are developing for Windows, keep reading. Otherwise, select your operating system to jump ahead:
*[[#macOS | macOS]]
*[[#Linux | Linux]]

== Windows ==
{{Windows_Languages}}
===Visual Studio===
====Use our examples====
One of the best ways to start programming with Phidgets is to use our example code as a guide. In order to run the examples, you will need to download and install [https://www.visualstudio.com/ Microsoft Visual Studio].

Now that you have Microsoft Visual Studio installed, select an example that will work with your Phidget:
*{{SampleCode|CSharp|C# Examples}}

Open the example project and start the example by pressing the ''Start'' button:

[[File:Csharp_visualstudio_run.png ‎|link=|center]]

The application will open the Phidget, list basic information about the Phidget, and demonstrate the Phidget's functionality. Here is an example of a Digital Output channel on a RFID Phidget:

[[File:Csharp_visualstudio_rfid.PNG|link=|center]]

You should now have the example up and running for your device. Play around with the device and experiment with some of the functionality. When you are ready, the next step is configuring your project and writing your own code!

=====VINT Hub=====
If you are trying to connect to one of the VINT hub ports directly rather than to a VINT device connected through a VINT hub then there is one additional step. There is a isHubPort property of the Phidget class that must be set before calling open. It defaults to false but in this case it will need to be set to true. In our examples this is done via command line though in practice you can just set it before calling open. To add command line parameters to your project in Visual Studio, you can go to the Project->Properties screen. Under the Debug section there is a field to enter command line parameters for startup. Use "-h" to make sure isHubPort is set before open is called and then you should be good to go.

[[File:Csharp_visualstudio_commandLineParameters.png|link=|center]]

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

Create a new Windows Forms Application project:

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

Next, right-click to add a reference to the Phidget .NET library:

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

On the following screen, click ''Browse...'' and navigate to the location of Phidget22.NET.dll:
*C:\Program Files\Phidgets\Phidget22\Phidget22.NET.dll

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

Finally, to include the Phidget .NET library, add the following lines to main window class file:

<syntaxhighlight lang="csharp">
using Phidget22;
using Phidget22.Events;
</syntaxhighlight>

Success! The project now has access to Phidgets. Next, view the [[#Write Code | write your own code]] section located below.

===Mono===
====Use our examples====
One of the best ways to start programming with Phidgets is to use our example code as a guide. In order to run the examples, you will need to download and install [http://www.mono-project.com/download/ Mono] for Windows.

Now that you have Mono installed, download and unpack the HelloWorld example for C#:
*[{{SERVER}}/downloads/phidget22/examples/dotnet/csharp/Manager/Phidget22_HelloWorld_CSharp_Windows_Ex.zip HelloWorld example]
Note: The HelloWorld example is compatible with Mono because it does not use Windows Forms. All other C# examples use Windows Forms.

Next, copy Phidget22.NET.dll from type the following location:
*C:\Program Files\Phidgets\Phidget22\Phidget22.NET.dll

Place both the HelloWorld example and the Phidget22.NET.dll file in the same location. Your folder should now look something like this:
[[File:Csharp_mono_folder.PNG|link=|center]]

Open the command prompt at the folder location and enter the following command:
<syntaxhighlight lang='bash'>
mcs /r:Phidget22.NET.dll Program.cs
</syntaxhighlight>

This will create an executable file called ''Program.exe''. Type in the following command to run the example:
<syntaxhighlight lang='bash'>
mono Program.exe
</syntaxhighlight>

[[File:Csharp_mono.PNG|link=|center]]

You should now have the example up and running. When you are ready, the next step is configuring your project and writing your own code!

====Configure your project====
When you are building a project from scratch, or adding Phidget functionality to an exisiting project, you'll need to configure your development environment to properly link the Phidget .NET library.

To include the Phidget .NET library, simply add the following lines to your code:
<syntaxhighlight lang='CSharp'>
using Phidget22;
using Phidget22.Events;
</syntaxhighlight>
You can now compile the file as shown in the previous section.

The project now has access to Phidgets. Next, view the [[#Write Code | write your own code]] section located below.

===MonoDevelop/Xamarin Studio===
====Use our examples====
One of the best ways to start programming with Phidgets is to use our example code as a guide. In order to run the examples, you will need to download and install [http://www.monodevelop.com/download/ Xamarin Studio] for Windows.

Now that you have Xamarin Studio installed, select an example that will work with your Phidget:
*{{SampleCode|CSharp|C# Examples}}

Next, open the example project:

[[Image: Csharp_xamarin.PNG|link=|center]]

Right click the project, and click Run Item:

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

The application will open the Phidget, list basic information about the Phidget, and demonstrate the Phidget's functionality. Here is an example of a Digital Output channel on a RFID Phidget:

[[File:Csharp_visualstudio_rfid.PNG|link=|center]]

You should now have the example up and running for your device. Play around with the device and experiment with some of the functionality. When you are ready, the next step is configuring your project and writing your own code!

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

Create a new .NET project:

[[Image:Csharp_xamarin_newproject.PNG|link=|center]]

[[Image:Csharp_xamarin_nameproject.PNG|link=|center]]

Next, add a reference to the Phidget .NET library:

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

On the following screen, select Phidget22.NET.dll:

[[Image:Csharp_xamarin_addreference.PNG|link=|center]]

Finally, to include the Phidget .NET library, add the following lines to main window class file:

<syntaxhighlight lang='CSharp'>
using Phidget22;
using Phidget22.Events;
</syntaxhighlight>

Success! The project now has access to Phidgets. Next, view the [[#Write Code | write your own code]] section located below.

==macOS==
{{macOS_Languages}}
===Mono===
====Use our examples====
One of the best ways to start programming with Phidgets is to use our example code as a guide. In order to run the examples, you will need to download and install [http://www.mono-project.com/download/ Mono] for macOS. You will also need a copy of [{{SERVER}}/downloads/phidget22/libraries/windows/Phidget22-windevel.zip Phidget22.NET.dll].

Now that you have Mono installed and Phidget22.NET.dll on hand, download and unpack the HelloWorld example for C#:
*[{{SERVER}}/downloads/phidget22/examples/dotnet/csharp/Manager/Phidget22_HelloWorld_CSharp_Windows_Ex.zip HelloWorld example download]
Note: The HelloWorld example is compatible with Mono because it does not use Windows Forms. All other C# examples use Windows Forms.

Finally, you need to create a configuration file. Create a new file in the same directory as the example you wish to compile and name it Phidget22.NET.dll.config. Copy the content below to the file.

<syntaxhighlight lang='xml'>
<configuration>
<dllmap dll="phidget22.dll" target="/Library/Frameworks/Phidget22.framework/Versions/Current/Phidget22" />
</configuration>
</syntaxhighlight>

Your project folder should now look like this:

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

To compile the program, enter the following command in the terminal:

<syntaxhighlight lang='bash'>
mcs Program.cs -r:Phidget22.NET.dll
</syntaxhighlight>

An executable file will be created. Run the program using mono:
<syntaxhighlight lang='bash'>
mono Program.exe
</syntaxhighlight>

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

You should now have the example up and running for your device. Play around with the device and experiment with some of the functionality. When you are ready, the next step is configuring your project and writing your own code!

====Configure your project====
When you are building a project from scratch, or adding Phidget functionality to an exisiting project, you'll need to configure your development environment to properly link the Phidget .NET library.

To include the Phidget .NET library, simply add the following lines to your code:
<syntaxhighlight lang='CSharp'>
using Phidget22;
using Phidget22.Events;
</syntaxhighlight>
You can now compile the file as shown in the previous section.

The project now has access to Phidgets. Next, view the [[#Write Code | write your own code]] section located below.

== Linux ==
{{Linux_Languages}}
===Mono===
====Use our examples====
One of the best ways to start programming with Phidgets is to use our example code as a guide. In order to run the examples, you will need to download and install Mono. You can do this by entering the following command in the terminal:

<syntaxhighlight lang='bash'>
apt-get install mono-complete
</syntaxhighlight>

You will also need a copy of [{{SERVER}}/downloads/phidget22/libraries/windows/Phidget22-windevel.zip Phidget22.NET.dll].

Now that you have Mono installed and Phidget22.NET.dll on hand, download and unpack the HelloWorld example for C#:
*[{{SERVER}}/downloads/phidget22/examples/dotnet/csharp/Manager/Phidget22_HelloWorld_CSharp_Windows_Ex.zip HelloWorld example download]
Note: The HelloWorld example is compatible with Mono because it does not use Windows Forms. All other C# examples use Windows Forms.

Your project folder should now look like this:

[[Image:Csharp_linux_folder.PNG|link=|center]]

Finally, to compile the program, enter the following command in the terminal:
<syntaxhighlight lang='bash'>
mcs Program.cs -r:Phidget22.NET.dll
</syntaxhighlight>

An executable file will be created. Run the program using mono:

<syntaxhighlight lang='bash'>
mono Program.exe
</syntaxhighlight>

[[Image:Csharp_linux_mono_run.PNG|link=|center]]

You should now have the example up and running for your device. Play around with the device and experiment with some of the functionality. When you are ready, the next step is configuring your project and writing your own code!

====Configure your project====
When you are building a project from scratch, or adding Phidget functionality to an exisiting project, you'll need to configure your development environment to properly link the Phidget .NET library.

To include the Phidget .NET library, simply add the following lines to your code:
<syntaxhighlight lang='CSharp'>
using Phidget22;
using Phidget22.Events;
</syntaxhighlight>
You can now compile the file as shown in the previous section.

The project now has access to Phidgets. Next, view the [[#Write Code | write your own code]] section located below.

==Write Code==
{{WriteCode_Intro}}

==== Step One: Initialize and open ====
You will need to declare your Phidget object in your code. For example, we can declare a digital input object like this:
<syntaxhighlight lang=csharp>
DigitalInput ch;
</syntaxhighlight>

Next, the Phidget object needs to be initialized and opened:
<syntaxhighlight lang=cSharp>
ch = new DigitalInput();
ch.Open();
</syntaxhighlight>

Although we are not including it on this page, you should include error handling for all Phidget functions. Here is an example of the previous code with error handling:
<syntaxhighlight lang=cSharp>
try{
ch = new DigitalInput();
ch.Open();
}catch(PhidgetException ex){
Console.WriteLine("Error: " + ex.Description);
}
</syntaxhighlight>

==== Step Two: Wait for attachment of the Phidget ====
Simply calling open does not guarantee you can use the Phidget immediately. To use a Phidget, it must be plugged in (attached). We can handle this by using event driven programming and tracking the attach events. Alternatively, we can modify our code so we wait for an attachment:
<syntaxhighlight lang=CSharp>
ch = new DigitalInput();
ch.Open(5000); //wait for attach for 5 seconds, if not time out
</syntaxhighlight>

Waiting for attachment will block indefinitely until a connection is made, or until the timeout value is exceeded.

To use events, we have to modify our code slightly:
<syntaxhighlight lang=CSharp>
ch = new DigitalInput();
ch.Attach += onAttachHandler;
ch.Open();
</syntaxhighlight>

Next, we have to declare the function that will be called when an attach event is fired - in this case the function ''onAttachHandler'' will be called.
<syntaxhighlight lang=CSharp>
void onAttachHandler (object sender, Phidget22.Events.AttachEventArgs e){
attachedText.Text = "Attached";
}
</syntaxhighlight>

==== Step Three: Do things with the Phidget ====
We recommend the use of event driven programming when working with Phidgets. In a similar way to handling an attach event as described above, we can also add an event handler for a state change event:
<syntaxhighlight lang=csharp>
ch = new DigitalInput();
ch.Attach += onAttachHandler;
ch.StateChange += onStateChangeHandler;
ch.Open();
</syntaxhighlight>

This code will connect a function and an event. In this case, the ''onStateChangeHandler'' function will be called when there has been a change to the devices input. Next, we need to create the ''onStateChangeHandler'' function:
<syntaxhighlight lang=cSharp>
void onStateChangeHandler(object sender, Phidget22.Events.DigitalInputStateChangeEventArgs e) {
stateText.Text = "State: " + e.State;
}
</syntaxhighlight>

If events do not suit your needs, you can also poll the device directly for data using code like this:
<syntaxhighlight lang=cSharp>
stateText.Text = "State: " + ch.State;
</syntaxhighlight>

==== Step Four: Close and delete ====
At the end of your program, be sure to close your device.
<syntaxhighlight lang=cSharp>
ch.Close()
</syntaxhighlight>

== Further Reading ==

[[Phidget Programming Basics]] - Here you can find the basic concepts to help you get started with making your own programs that use Phidgets.

[[Data Interval/Change Trigger]] - Learn about these two properties that control how much data comes in from your sensors.

[[Using Multiple Phidgets]] - It can be difficult to figure out how to use more than one Phidget in your program. This page will guide you through the steps.

[[Polling vs. Events]] - Your program can gather data in either a polling-driven or event-driven manner. Learn the difference to determine which is best for your application.

[[Logging, Exceptions, and Errors]] - Learn about all the tools you can use to debug your program.

[[Phidget Network Server]] - Phidgets can be controlled and communicated with over your network- either wirelessly or over ethernet.

File:Csharp visualstudio commandLineParameters.png

2017-09-06T14:16:59Z

Burley:

Terms and Conditions

2017-08-21T18:53:31Z

Burley:

[[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 issue you an RMA number and will replace your defective product free of charge.

==Shipping==
===Last Call at 12:00PM===
Unless we are unusually busy most orders received before 12:00 PM Mountain Time - Canada (GMT-07:00) Monday to Friday will be shipped on the same day.

Orders which contain cut to length parts may not necessarily ship same day as there is significant processing time associated with these orders.

===Shipping Costs===
The shipping cost is calculated at Checkout and submitted for your review before you confirm your order. When multiple shipping options are available for your destination, we will list all available options and let you choose.

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

If you have your own account with UPS, you can use it and be billed directly by them. In that case you have more shipping options available to you.

===Shipping in Canada===
We use UPS Express Saver™ - Overnight delivery, and UPS Standard - 3 to 5 business days ground delivery.

===Shipping to the United States===

====UPS Express Saver™ - Overnight====

'''Shipments under $2000.00USD''': we pay all costs in bringing the goods to you including import duties and taxes. In other words your shipping costs are what we put on our invoice. Contact us if you are getting any extra invoices from UPS.

'''Shipments over $2000.00USD''': you are responsible for duty and taxes if applicable and will have to pay UPS directly on top of the shipping cost we put on our invoice.

====UPS Standard - Ground 3 to 5 business days====
'''Shipments under $800.00USD''': we pay all costs in bringing the goods to you including import duties and taxes. In other words your shipping costs are what we put on our invoice. Contact us if you are getting any extra invoices from UPS.

'''Shipment over $800.00USD''' UPS will collect Entry Preparation Fees directly from you when delivering the package, and for duty and taxes if applicable.

:'''Entry Preparation Fees'''
:*All rates are in U.S. funds
:*Rates do not include applicable duties or taxes

{| style="border:1px solid darkgray;" cellpadding="7px;"
|-style="background: #d1d1d1" align=center
! Value for duty|| UPS Standard Service
|-
|style="background: #f0f0f0" align=center|$0.00 to $800.00
|style="background: #f0f0f0" align=center|No Charge
|-
|style="background: #f0f0f0" align=center|$800.01 to $1,250.00
|style="background: #f0f0f0" align=center|$28.75
|-
|style="background: #f0f0f0" align=center|$1,250.01 to $2,500.00
|style="background: #f0f0f0" align=center|$40.50
|-
|style="background: #f0f0f0" align=center|Each Additional $1,000.00
|style="background: #f0f0f0" align=center|$1.95
|}

===International Shipments===
We use UPS Worldwide Express Saver™, and UPS Worldwide Expedited for international locations that cannot be reached with Express Saver.

Goods shipped to an international destination may be subject to import duties and taxes, which are levied once the goods reach your country. Additional charges for customs clearance must be borne by you; we have no control over these charges and cannot predict what they may be. Since customs policies vary widely from country to country, you should contact your local customs office for further information.

===Tracking your order===
You can track your shipment by going to www.UPS.ca and using the tracking number that was e-mailed to you when your order 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, when the package arrives there is no one to accept delivery UPS will redeliver 2 more times. This is standard UPS protocol. If delivery fails they will keep the package for 5 days and then return it to us. We will then refund you the cost you paid minus the cost of shipping (both directions) and a flat $50 charge to a maximum of the total cost of the package. This applies to packages which failed delivery due to no one being present as well as packages which were refused delivery by a person at the delivery location.

===Import Restrictions to Russia===
If you are wanting to ship an order to Russia you MUST have a valid business license number in order to complete the shipment. You can include this number in the comments field of the order form. The reason for this is best explained by UPS:

"Customs authorities in Russia have tightened restrictions on import shipments to Russia, in particular on dutiable shipments sent to private individuals. These shipments are currently under extraordinary scrutiny in an effort to improve accuracy of the accompanying shipping documentation. These additional requirements lead to an unprecedented number of customs holds and delays in delivery. UPS has therefore temporarily suspended the acceptance of dutiable shipments sent to private individuals in Russia until further notice. We regret this step and are confident that, together with the Russian customs authorities, a solution can be found. UPS continues to accept all non-dutiable document shipments to private individuals in Russia and all commercial shipments addressed to businesses." [http://www.ups.com/content/hr/en/about/news/service_updates/20100526_restrictions.html]

==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 will take back any unopened product for a period of 30 days from the date of purchase. Just call or e-mail us for a RMA number and ship the product back to Phidgets prepaid and we will refund your credit card as soon as we receive and inspect the returned goods.

Products that are returned after 30 days are subject to a re-stocking charge of 25% of the package's value (minimum $5.00) to a maximum of $500.

We do '''not''' accept returns after 90 days.

===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
|+'''Phidgets Inc. Holidays'''
! Holiday || Description || 2016 || 2017
|-
|style="background: #f0f0f0" align=center| New Year's Holiday
|style="background: #f0f0f0" align=center| First two days of January
|style="background: #f0f0f0" align=center| Jan 1
|style="background: #f0f0f0" align=center| Jan 1
|-
|style="background: #f0f0f0" align=center| Alberta Family Day
|style="background: #f0f0f0" align=center| Third Monday in February
|style="background: #f0f0f0" align=center| Feb 15
|style="background: #f0f0f0" align=center| Feb 20
|-
|style="background: #f0f0f0" align=center| Good Friday
|style="background: #f0f0f0" align=center| Friday before Easter Sunday
|style="background: #f0f0f0" align=center| Mar 25
|style="background: #f0f0f0" align=center| Apr 14
|-
|style="background: #f0f0f0" align=center| Victoria Day
|style="background: #f0f0f0" align=center| Monday before May 25
|style="background: #f0f0f0" align=center| May 23
|style="background: #f0f0f0" align=center| May 22
|-
|style="background: #f0f0f0" align=center| Canada Day
|style="background: #f0f0f0" align=center| First day of July
|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 1
|style="background: #f0f0f0" align=center| Aug 7
|-
|style="background: #f0f0f0" align=center| Labour Day
|style="background: #f0f0f0" align=center| First Monday in September
|style="background: #f0f0f0" align=center| Sept 4
|style="background: #f0f0f0" align=center| Sept 4
|-
|style="background: #f0f0f0" align=center| Thanksgiving
|style="background: #f0f0f0" align=center| Second Monday in October
|style="background: #f0f0f0" align=center| Oct 10
|style="background: #f0f0f0" align=center| Oct 9
|-
|style="background: #f0f0f0" align=center| Remembrance Day
|style="background: #f0f0f0" align=center| November 11
|style="background: #f0f0f0" align=center| Nov 11
|style="background: #f0f0f0" align=center| Nov 11
|-
|style="background: #f0f0f0" align=center| Christmas Holiday
|style="background: #f0f0f0" align=center| Dec 22 to the New Year
|style="background: #f0f0f0" align=center| Dec 22 to the New Year
|style="background: #f0f0f0" align=center| TBA
|-
|}

Dealers

2017-08-03T14:24:25Z

Burley:

[[Category:Linked_From_Website]]

Select your Region:

{{TOClimit|2}}

==North America==

===Canada===

{{Dealerbox|{{Dealer
|RobotShop
|{{DealerURL|www.robotshop.com/ca/en/phidgets-en.html}}
|Tel: 450 420 1446
|Fax: 450 420 1447
|{{DealerMail|sales@robotshop.ca}}
}}

|{{Dealer
|Solarbotics Ltd.
|{{DealerURL|www.solarbotics.com}}
|North America Toll Free: 1-866-276-2687
|Local/International: 1-403-232-6268
|{{DealerMail|info@solarbotics.com}}
}}
||||}}

===Mexico===
{{Dealerbox|{{Dealer
|5Hz Electronica
|{{DealerURL|www.5hz-electronica.com}}
|Tel: (81) 1341.4109
|{{DealerMail|ventas@5hertz.com}}
|
}}

|{{Dealer
|Electronica Estudio
|{{DealerURL|www.electronicaestudio.com}}
|Tel: 55 12 79 75
|{{DealerMail|wgb@electronicaestudio.com}}
|
}}
||||}}

===USA===
{{Dealerbox|{{Dealer
|TrossenRobotics
|{{DealerURL|www.trossenrobotics.com}}
|Tel: 877 898 1005
|{{DealerMail|trsupport@trossenrobotics.com}}
|
}}

|{{Dealer
|USBStuff
|{{DealerURL|www.usbstuff.com}}
|Tel: 877 446 8947
|{{DealerMail|orders@industrialcomponent.com}}
|
}}

|{{Dealer
|RobotShop
|{{DealerURL|www.robotshop.com/en/phidgets-en.html}}
|Tel: 866-627-3178
|Fax: 420-420-1447
|{{DealerMail|supportcenter@robotshop.com}}
}}

|{{Dealer
|Green Energy Research, Inc.
|{{DealerURL|www.gerelectronics.com}}
|Tel: 1-866-625-8492
|{{DealerMail|info@greenenergyresearch.com}}
|
}}
||}}

==South America==

===Colombia===
{{Dealerbox|{{Dealer
|EDU-SOLUTIONS
|{{DealerURL|www.edusolutions.ws}}
|(571)600 7526
|(571) 606 8268
|{{DealerMail|ventas@edusolutions.ws}}
}}
|||||}}

==Europe==

===France===
{{Dealerbox|{{Dealer
|GO TRONIC
|{{DealerURL|www.gotronic.fr}}
|Tel: +33.324.27.93.42
|Fax: +33.324.27.93.50
|{{DealerMail|commandes@gotronic.fr}}
}}
|{{Dealer
|RobotShop Europe
|{{DealerURL|www.robotshop.com/eu/fr/phidgets-en.html}}
|Tel: +33 (0) 8 00 00 18 37
|{{DealerMail|supportcenter@robotshop.com}}
|
}}
||||}}

===Germany===
{{Dealerbox|{{Dealer
|noDNA GmbH
|{{DealerURL|www.nodna.com}}
|Tel: +49 89 1222375-50
|Fax: +49 89 1222375-59
|{{DealerMail|sales@nodna.com}}
}}
|{{Dealer
|Böcker Systemelektronik
|{{DealerURL|www.boecker-systemelektronik.de}}
|Tel: +49-2381-974280
|Fax: +49-2381-377463
|{{DealerMail|info@boecker-systemelektronik.de}}
|
}}
||||}}

===Italy===
{{Dealerbox|{{Dealer
|Emmeshop srl
|{{DealerURL|www.emmeshop.eu}}
|Tel: +39 0544 1766265
|Fax: +39 0544 1960281
|{{DealerMail|sales@emmeshop.eu}}
|
}}
|{{Dealer
|Robot Italy srl
|{{DealerURL|www.robot-italy.com}}
|Tel: +39 06 414 011 01
|Fax: +39 06 233 243 440
|Please use the contact form on our web site
}}
||||}}

===Sweden===
{{Dealerbox|{{Dealer
|CLC SYSTEMS AB
|{{DealerURL|clcsystems.nordicshops.com}}
|Tel: +46 171 411030
|Fax: +46 171 411090
|{{DealerMail|info@clcsystems.se}}
}}
|{{Dealer
|EZtronics
|{{DealerURL|www.eztronics.se}}
|Tel: +46 708342567
|{{DealerMail|info@eztronics.se}}
|
}}
||||}}

===The Netherlands===
{{Dealerbox|{{Dealer
|EZtronics
|{{DealerURL|www.eztronics.nl}}
|Tel: +31 302421478
|
|{{DealerMail|info@eztronics.nl}}
}}
|||||}}

===United Kingdom===
{{Dealerbox|{{Dealer
|Active Robots Inc.
|{{DealerURL|www.active-robots.com}}
|Tel: +44 (0)176 123 9267
|Fax: +44 (0)176 123 3162
|Please use the contact form on our web site
}}
|||||}}

==Asia==

===India===
{{Dealerbox|{{Dealer
|MG Automation Technologies
|{{DealerURL|http://www.mgsuperlabs.com/}}
|Tel: (+91)7721933328
|{{DealerMail|estore@mgsuperlabs.co.in}}
|
}}
||||||}}

===Japan===
{{Dealerbox|{{Dealer
|RobotShop Japan
|{{DealerURL|www.robotshop.com/jp/ja/}}
|Tel: 088-635-0277
|Fax: 088-635-0278
|Email form on website
|
}}
||||||}}

===Singapore===
{{Dealerbox|{{Dealer
|sgBOTIC
|{{DealerURL|www.sgbotic.com}}
|Tel: +65-65701125
|{{DealerMail|sales@sgbotic.com}}
|
}}
|{{Dealer
|Amicus Engineering
|{{DealerURL|www.amicus.com.sg}}
|Tel: +65-684 55558
|{{DealerMail|sales@amicus.com.sg}}
|
}}
|||||}}

===South Korea===
{{Dealerbox|{{Dealer
|SEED Technology
|{{DealerURL|seedtech.co.kr}}
|Tel: 82-32-623-6220
|Fax: 82-32-623-5267
|{{DealerMail|info@seedtech.co.kr}}
}}
|{{Dealer
|VCTEC
|{{DealerURL|vctec.co.kr}}
|Tel: 070-7770-6256
|Fax: 031-696-6258
|{{DealerMail|cs@vctec.co.kr}}
}}
||||}}

===Taiwan===
{{Dealerbox|{{Dealer
|IDM Store
|{{DealerURL|www.idmstore.com}}
|Tel: 886-2-2362-9896
|{{DealerMail|inquiry@idmstore.com}}
|
}}
|||||}}

==Middle East & Africa==

===Algeria===

{{Dealerbox|{{Dealer|Dzduino Electronics
|{{DealerURL|dzduino.com}}
|Tel: 00213 540 265 592
|Fax: 00213 45 366 373
|{{DealerMail|contact@dzduino.com}}
}}
|
|
|
|
|}}

===Israel===
{{Dealerbox|{{Dealer|Testview
|{{DealerURL|shop.testview.co.il/}}
|Tel: +972-54-5376124
|Fax: +972-773457377
|{{DealerMail|info@testview.co.il}}
}}
|
|
|
|
|}}

===South Africa===
{{Dealerbox|{{Dealer|AutomationBuyer
|{{DealerURL|www.automationbuyer.co.za/}}
|Tel: +27-41-451-2712
|
|{{DealerMail|Support@automationbuyer.co.za}}
}}
|
|
|
|
|}}

==Australia==
{{Dealerbox|{{Dealer|IoT Store Australia
|{{DealerURL|iot-store.com.au}}
|Tel: +61424742772
|
|{{DealerMail|info@iot-store.com.au}}
}}
|
|
|
|
|}}

Main Page

2017-07-11T13:54:48Z

Burley:

[[Category:Linked From Website]]__NOTOC__
<div class="wikimain-ctn">
<h1>Phidgets Support</h1>

<div class="cat-ctn">
<h3>Hardware</h3>
*'''[[What_is_VINT%3F|What is VINT?]]'''
*'''[[Phidgets Connectors]]'''
*'''[[Solid State Relay Primer|Solid State Relays]]'''
*'''[[Stepper Motor and Controller Primer |Stepper Motors]]'''
*'''[[RFID Primer|RFIDs]]'''
<hr />
<p>For information about a specific class of products check our '''[[:Category:Primer|Phidget Primers]]'''</p>
</div>

<div class="cat-ctn">
<h3>Software</h3>
*'''[[Software Overview#Language Support|Supported Languages]]'''
*'''[[Software Overview#Operating System Support|Operating Systems]]'''
*'''{{Phidget22API}}'''
*'''[[General Phidget Programming]]'''
<hr />
Use Phidgets over a network with our '''[[Phidget Network Server|Network Server]]''' and '''[[Phidget Dictionary|Dictionary]]'''
</div>

<div class="cat-ctn">
<h3>Help</h3>
*'''[[General Troubleshooting]]'''
*'''[[Phidget Control Panel]]'''
*'''[[What is a Phidget?|What is a Phidget?]]'''
*'''[[:Category:UserGuide|User Guides]]'''
*'''[[Upgrading_Code_from_Phidget21_to_Phidget22|Upgrading from Phidget21 to Phidget22]]
<hr />
If you can't find the solution to your problem, feel free to {{ContactUs|Contact Us}}
</div>

<div class="cat-ctn">
<h3>Inspiration</h3>
*'''[http://www.pinterest.com/phidgets/phidgets/ Customer Projects]'''
*'''[{{SERVER}}/?view=articles Articles]'''
*'''[http://www.phidgets.com/phorum/ Forums]'''
</div>

<div class="cat-ctn">
<h3>Phidgets Inc.</h3>
*'''[[About Phidgets Inc.]]'''
*'''[[Dealers]]'''
*'''[[Policies|Shipping Policies]]'''
*'''{{ContactUs|Contact Us}}'''

</div>

</div>

Language - Max

2017-07-07T14:31:34Z

Burley:

[[Category:Language]]
__TOC__

== Quick Downloads ==

=== Documentation ===

*{{Phidget22API}} (select Max/MSP from the drop-down menu)

=== Example Code ===
* [{{SERVER}}/downloads/phidget22/libraries/windows/Phidget22MaxMSP.zip Max/MSP Examples]

=== Libraries ===
*[{{SERVER}}/downloads/phidget22/libraries/windows/Phidget22MaxMSP.zip Phidget Max/MSP library - Windows]
*[{{SERVER}}/downloads/phidget22/libraries/macos/Phidget22MaxMSP.zip Phidget Max/MSP library - macOS]
{{WindowsQuickDownloads}}
{{MacQuickDownloads}}

== Getting Started with Max/MSP ==
Welcome to using Phidgets with Max/MSP! By using Max/MSP, you will have access to the complete {{Phidget22API}}, including events. We also provide example code in Max/MSP for all Phidget devices.

Phidget22 supports Max/MSP versions 6 and up.

If you are developing for Windows, keep reading. Otherwise, jump ahead to [[#macOS | macOS]].

== Windows ==
{{Windows_Languages}}
===Use our examples===
One of the best ways to start programming with Phidgets is to use our example code as a guide. In order to run the examples, you will need to download and install Max/MSP from [https://cycling74.com/downloads Cycling '74].

Next, download and unpack the Phidgets Max/MSP library:
*[{{SERVER}}/downloads/phidget22/libraries/windows/Phidget22MaxMSP.zip Phidget Max/MSP library]

After unpacking the download, navigate to the ''externals'' folder. Copy the following folder to your clipboard:
*32-bit Max/MSP -> copy the ''x86'' folder
*64-bit Max/MSP -> copy the ''x64'' folder

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

The folder you copied needs to be placed in a specific location for Max/MSP to reference it. We will find this location in in the next step.

Open Max/MSP and navigate to ''Options'' -> ''File Preferences''.
[[Image:Max_filepreferences.png|link=|center]]

You will see something similar to this:
[[Image:Max_filepreferences_locations.PNG|link=|center]]

The folder that you copied earlier needs to be placed in any of the locations listed in ''File Preferences''. Navigate to one of the locations and paste the folder:
[[Image:Max_folder.PNG|link=|center]]

The Phidget Max/MSP library is now being referenced. Next, navigate to the ''examples'' folder located within the Phidget22MaxMSP folder you previously unpacked:
[[Image:Max_examples.PNG|link=|center]]

From here, select an example that will work with your Phidget and open it in Max/MSP. You can run the example by simply pressing the ''start'' button:
[[Image:Max_run.png|link=|center]]

You should now have the example up and running for your device. Play around with the device and experiment with some of the functionality. When you are ready, the next step is configuring your project and writing your own code!

===Configure your project===
When you are building a project from scratch, or adding Phidget function calls to an existing project, you'll need to configure the Max/MSP environment to properly link the Phidget Max/MSP library.

Ensure the Phidget library files are moved to a location in the Max/MSP search path. This procedure is covered in detail above in the [[#Use our examples | use our examples]] section.

After moving the library files into the correct location your project will have access to Phidgets. Next, view the [[#Write Code | write your own code]] section below.

==macOS==
{{macOS_Languages}}
===Use our examples===
One of the best ways to start programming with Phidgets is to use our example code as a guide. In order to run the examples, you will need to download and install Max/MSP from [https://cycling74.com/downloads Cycling '74].

Next, download and unpack the Phidgets Max/MSP library:
*[{{SERVER}}/downloads/phidget22/libraries/macos/Phidget22.dmg Phidget Max/MSP library]

After unpacking the download, navigate to the ''externals'' folder and copy it to your clipboard:
[[Image:Max_mac_externals.png|link=|center]]

The folder you copied needs to be placed in a specific location for Max/MSP to reference it. We will find this location in in the next step.

Open Max/MSP and navigate to ''Options'' -> ''File Preferences''.
[[Image:Max_mac_filepreferences.png|link=|center]]

You will see something similar to this:
[[Image:Max_mac_filepreferences_locations.png|link=|center]]

The folder that you copied earlier needs to be placed in any of the locations listed in ''File Preferences''. Navigate to one of the locations and paste the folder:
[[Image:Max_mac_folder.png|link=|center]]

The Phidget Max/MSP library is now being referenced. Next, navigate to the ''examples'' folder located within the Phidget22MaxMSP folder you previously unpacked:
[[Image:Max_mac_examples.png|link=|center]]

From here, select an example that will work with your Phidget and open it in Max/MSP. You can run the example by simply pressing the ''start'' button:
[[Image:Max_mac_run.png|link=|center]]

You should now have the example up and running for your device. Play around with the device and experiment with some of the functionality. When you are ready, the next step is configuring your project and writing your own code!

===Configure your project===
When you are building a project from scratch, or adding Phidget function calls to an existing project, you'll need to configure the Max/MSP environment to properly link the Phidget Max/MSP library.

Ensure the Phidget library files are moved to a location in the Max/MSP search path. This procedure is covered in detail above in the [[#Use our examples 2 | use our examples]] section.

After moving the library files into the correct location your project will have access to Phidgets. Next, view the [[#Write Code | write your own code]] section below.

== Write Code ==
{{WriteCode_Intro}}

=== Example Flow ===
First, let's explain how to operate the examples. We will take a look at the PhidgetVoltageInput example:
[[Image: MSP Example.png|link=|center]]

For this particular example, the Max object is called PhidgetVoltageInput, which is located near the bottom left of the screen. Objects/message boxes are connected to the inputs and outputs of the PhidgetVoltageInput object. The input objects will either cause a property of the device to change or request for a property to be retrieved. The output objects return the retrieved information. All the supported functions for Max/MSP will be documented in the {{Phidget22API}} for your device.

Try it for yourself! Click on the getDeviceSerialNumber message box to request the Phidget to retrieve the serial number of the device. You should see the a message in the Max window denoting the serial number of your device. All devices support the getDeviceSerialNumber message, making it an easy way to determine if the Phidget libraries are correctly set up, and whether the Max/MSP application is connected to your device.
[[Image: MaxMSP_GetSerial.png|link=|center]]

If your example contains a get[DataType] message box, click on it to cause the associated data to be output with a relevant prefix. [DataType] can denote any data the object may offer, such as Voltage for a voltage input. A list of available messages and their associated outputs is outlined in the {{Phidget22API}} for your device.
[[Image: MaxMSP_GetVoltage.png|link=|center]]

If your example contains the start message box, you can continuously poll for events. Just press the start message box to start sampling. When an event occurs on a Phidget (i.e. when a sensor detects a change in the measured data), associated data will be output with related prefixes. Press the stop message box to stop sampling.

For the PhidgetDigitalOutput example, there are setDutyCycle and setState message boxes. Changing the numbers will cause the digital output to change. Your example may contain device specific message boxes to click on. Click them to see what they do!

=== Code Snippets ===
Your best resource to program code in MaxMSP will be our examples.

If you aren't familiar with concepts in Phidget programming, you may find our General Phidget Programming page helpful. It provides a very generic overview of what traditional languages follow when using Phidgets. For setup 'syntax', your main resource will of course be this MaxMSP page, the {{Phidget22API}}, and the examples. But for conceptual details about particular actions - opening a Phidget, for example - the General Phidget Programming page is a more in-depth resource.

Keep in mind when reading these general resources that the Max/MSP libraries may not implement the full {{Phidget22API}} - some function calls and Phidget classes may not be supported.

In general, Phidget objects can be placed inside the patcher, and functions can be called on them using appropriately connected messages. We go over a basic setup for this below.

==== Step One: Initialize and Open ====
This tutorial uses a Phidget Voltage Input, and thus the object we use will be called PhidgetVoltageInput. Initializing and opening the device is be done by placing a new object. Other objects handle different Phidgets - a Spatial, a Temperature Sensor, a Motor Controller, etc. Only the name of the object changes. You can find the name for the object in the .maxhelp file for your device. The help file will be named the same as the software object for your device. If you are not sure what the software object for your device is, find your Phidget on our [http://www.phidgets.com webpage], and then check the API documentation for it.

In the case of a Voltage Input, we name it PhidgetVoltageInput:
[[Image: MaxMSP_VoltageInput_generic.png|link=|center]]

'''Important:''' a local connection will reserve the device until closed. This prevents any other instances from retrieving data from the Phidget, including other programs. Every Phidget object in Max will automatically try to connect to and reserve a Phidget for itself. As long as a MaxMSP Phidget object is running, it will continuously try to connect to a Phidget, even trying to reconnect if it gets disconnected.

When the instance is created as with the Voltage Input above, normally it will make a connection to the first device of its type it can find. The Phidget object can also be declared with a serial number, among other specifiers, to open a specific Phidget instead. To view a full list of available device specifiers and what they do, see the readme.txt included with the Phidget22 Max/MSP library.
[[Image: MaxMSP VoltageInput specific.png|link=|center]]

=====Using a Phidget Over a Network=====

To use the Network Server, first the Phidget needs to be plugged in to a computer that has the Network Server turned on within your local network. (For information on how to do this, see the Phidget Network Server page in the section on how to use the Network Server for your operating system).

Next, in your patch you need a PhidgetNet object. To automatically find local networks, send it a message saying enableServerDiscovery.
[[Image: MaxMSP Enable Server Discovery.png|link=|center]]

Then, to connect a Phidget over the network, change the object text to specify it is to connect to a Phidget on a remote server, as per the following example.
[[Image: MaxMSP Remote.png|link=|center]]

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

Although this is a required step in many of our other languages (and therefore you may be expecting this if coming from another Phidget language), in MaxMSP you do not have to add a specific waitForAttachment block.

Keep in mind, however, that if your Phidget is not responding within your MaxMSP program, it may simply not be plugged in! Send a getAttached message to a Phidget object at any time to see if it's attached.

==== Step Three: Do Things with the Phidget ====

There are two main approaches for retrieving data when working with Phidgets. Data is accessed either by one-time polling or at a fixed rate via on-board timers for some devices.

Getting or setting values directly via polling on the Phidget is done through messages linked to the inlet. The object’s inlet can be wired to send commands to the device, and the outlet used to retrieve the results. Setting values on the Phidget is achieved by using the set messages, and some properties can be read with get messages:
[[Image: MaxMSP_get_and_set.png|link=|center]]

To sample at a fixed rate, use the start and stop messages to start and stop the data flow, respectively.
[[Image: MaxMSP_Start_Stop.png|link=|center]]

Data from the outlet of a Phidget object is always given a prefix to allow for routing. For instance, the digital input state state change event data is given the prefix “stateChange”, and the voltage input voltage change event similarly use “voltageChange”. The specific prefixes used for each set of outlet data is listed under the API page for their class in the {{Phidget22API}}.
[[Image: MaxMSP_Routing.png|link=|center]]

The rightmost outlet on the Phidget object outputs error event data. This will send information on error events such as saturation events. To see which error events may apply to your device, check its API page in the {{Phidget22API}}.
[[Image: MaxMSP_Error_Event.png|link=|center]]

==== Step Four: Close and Delete ====

Although this is a required step in many of our other languages (and therefore you may be expecting this if coming from another Phidget language), in MaxMSP you do not have to add a specific close and delete block.

====Special Case: Multiple Phidgets====

Multiple Phidgets of the same type can easily be used inside a single program, it only requires another Phidget object placed. If two of the same type of Phidget object are placed, the serial number and channel arguments should always be specified (as well as hub port, if applicable) to ensure that the correct Phidget gets associated with the correct object.

== Further Reading ==

[[Phidget Programming Basics]] - Here you can find the basic concepts to help you get started with making your own programs that use Phidgets.

[[Data Interval/Change Trigger]] - Learn about these two properties that control how much data comes in from your sensors.

[[Using Multiple Phidgets]] - It can be difficult to figure out how to use more than one Phidget in your program. This page will guide you through the steps.

[[Polling vs. Events]] - Your program can gather data in either a polling-driven or event-driven manner. Learn the difference to determine which is best for your application.

[[Logging, Exceptions, and Errors]] - Learn about all the tools you can use to debug your program.

[[Phidget Network Server]] - Phidgets can be controlled and communicated with over your network- either wirelessly or over ethernet.

Language - LabVIEW

2017-06-29T14:22:42Z

Burley:

[[Category:Language]]
__TOC__

== Quick Downloads ==
=== Documentation ===
* Documentation is included in the LabVIEW examples in the form of vi trees. See the [[#Use_our_examples|next]] section for details.
=== Example Code ===
* [{{SERVER}}/downloads/phidget22/libraries/any/Phidget22Labview.zip LabVIEW Examples]

=== Libraries ===

{{WindowsQuickDownloads}}

== Getting Started with LabVIEW ==
Welcome to using Phidgets with LabVIEW! By using LabVIEW, you will have access to the complete {{Phidget22API}}, including events. We also provide example code in LabVIEW for all Phidget devices.

== Windows ==
{{Windows_Languages}}
====Use our examples====
One of the best ways to start programming with Phidgets is to use our example code as a guide. In order to run the examples, you will need to download and install the LabVIEW from [http://www.ni.com/en-ca/shop/labview.html National Instruments].

Next, download and unpack the Phidgets LabVIEW library:
*[{{SERVER}}/downloads/phidget22/libraries/any/Phidget22Labview.zip Phidget LabVIEW library]

Rename the unpacked folder to ''Phidgets''
[[Image:Labview_rename.png|link=|center]]

Navigate to the following directory:
*For 32-bit LabVIEW -> C:/Program Files (x86)/National Instruments/LabVIEW 20xx/instr.lib
*For 64-bit LabVIEW -> C:/Program Files/National Instruments/LabVIEW 20xx/instr.lib

Place the renamed folder at this location:
[[Image:Labview_copy.png|link=|center]]

Next, open LabVIEW and create a new VI:
[[Image:Labview_newvi.png|link=|center]]

Navigate to the block diagram window that was generated and open the functions palette (''View'' -> ''Functions Palette''). Next, navigate to the Phidgets palette (''Instrument I/O'' -> ''Instrument Drivers'' -> ''Phidgets''):
[[Image:Labview_functionspalette.PNG|link=|center]]

Next, select a palette that will work for your Phidget and drag the ''VI Tree.vi'' onto your block diagram:
[[Image:Labview_vitree.png|link=|center]]

Right-click on ''VI Tree.vi'' and select ''Open Front Panel'':
[[Image:Labview_openfrontpanel.png|link=|center]]

From the front panel, navigate to the block diagram (''Window'' -> ''Block Diagram''):
[[Image:Labview_showblock.png|link=|center]]

The examples are located near the bottom of the block diagram. Right-click the example you would like to use and select ''Open Front Panel'':
[[Image:Labview_runexample.png|link=|center]]

When you are ready, press run and the application will demonstrate the Phidget's functionality. Here is an example of an Accelerometer channel on a Spatial Phidget:
[[Image:Labview_run.PNG|link=|center]]

You should now have the example up and running for your device. Play around with the device and experiment with some of the functionality. When you are ready, the next step is configuring your environment and writing your own code!

====Configure your environment====
If you haven't already, jump back and take a look at the [[#Use our examples | use our examples]] section above. There you will be instructed on how to properly set up LabVIEW so you can follow the guides below. If you are ready, keep reading.

To begin configuring your environment, we recommend enabling the ''Show constant labels'' setting in LabVIEW . This setting will reduce complexity when developing, and is especially recommended for beginners. To enable the setting, first navigate to ''Tools'' -> ''Options'' on your block diagram:
[[Image:Labview_options.png|link=|center]]

Select the ''Environment'' category and enable ''Show created constant labels'' located at the bottom of the screen:
[[Image:Labview_showconstantlabels.png|link=|center]]

To begin working with Phidgets, you will need both a ''StartPhidget'' VI and a ''ClosePhidget'' VI:
[[Image:Labview_startclose.png|link=|center]]

Select a class that will work with your Phidget from the drop-down menu:
[[Image:Labview_selectclass.png|link=|center]]

You can now add device information or any initialization parameters to the ''StartPhidget'' VI. Using your mouse, hover over the connections to see information about it:
[[Image:Labview_hover.png|link=|center]]

If you would like to add device information or initialization parameters, right-click the connection and navigate to one of the following:
*''Create'' -> ''Constant''
*''Create'' -> ''Control''

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

Creating a constant will allow you to modify device information from the block diagram:
[[Image:Labview_constant.PNG|link=|center]]

Creating a control will allow you to modify device information from the front panel:
[[Image:Labview_control.png|link=|center]]

The environment now has access to Phidgets. Next, view the write your own code section located below.

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

Your main reference for writing LabVIEW code will be this page, the examples, the {{Phidget22API}}, and the VI help files.

Examples of more complex general topics such as using multiple Phidgets and connecting to a Phidget over the Network Server can be found under the VI Tree for the '''Phidget Common''' palette.

=== Example Flow ===
Most LabVIEW examples follow the same basic flow: starting a Phidget, reading some data, and closing the Phidget.
[[Image: Digital Input Example.png|link=|center]]

=== Step One: Initialize, Open and Wait for Attachment of the Phidget ===
The entire process of opening and initializing a Phidget can be done by using the version of ''StartPhidget.vi'' that corresponds to your device. In most cases, ''StartPhidget.vi'' will also attempt to wait for the first data to become available from the device for 5 seconds after initialization.
[[Image:StartPhidget VI.png|link=|center]]

If you'd prefer to initialize the device manually, you can use ''OpenPhidget.vi'' for your device and call the individual functions to set up the device.
[[Image: OpenPhidgetVI.png|link=|center]]

=== Step Two: Do Things with the Phidget ===
You can read data and interact with your Phidget both by polling it for its current state (or to set a state), or by catching events that trigger when the data changes.

To poll devices, simply place the corresponding blocks:
[[Image:LabVIEW_polling.png|link=|center]]

To use events, there are three main blocks for each type, to create, execute, and close the event handler. When creating the event, all devices using an event of the same type must be grouped into an array to ensure the events get processed correctly.
[[Image: Event Array grouping.png|link=|center]]

Once created, the events will be processed by [Name]EventExe.vi. When an event occurs, the pertinent information will be output, as well as information to reference which device caused it.
[[Image: Event Exe.png|link=|center]]

After a program has run its course, the event handler must be closed.
[[Image: Event Close.png|link=|center]]

=== Step Three: Close and Delete ===
Closing a Phidget is done by using the appropriate version of ClosePhidget.vi
[[Image:Close Phidget VI.png|link=|center]]

== Further Reading ==

[[Phidget Programming Basics]] - Here you can find the basic concepts to help you get started with making your own programs that use Phidgets.

[[Data Interval/Change Trigger]] - Learn about these two properties that control how much data comes in from your sensors.

[[Using Multiple Phidgets]] - It can be difficult to figure out how to use more than one Phidget in your program. This page will guide you through the steps.

[[Polling vs. Events]] - Your program can gather data in either a polling-driven or event-driven manner. Learn the difference to determine which is best for your application.

[[Logging, Exceptions, and Errors]] - Learn about all the tools you can use to debug your program.

[[Phidget Network Server]] - Phidgets can be controlled and communicated with over your network- either wirelessly or over ethernet.

Load Cell Guide

2017-06-20T21:02:19Z

Burley:

[[Category: Primer]]
[[Image:loadcells.jpg|link=|400px]]
__TOC__

==Introduction==
A load cell is a force sensing module - a carefully designed metal structure, with small elements called strain gauges mounted in precise locations on the structure. Load cells are designed to measure a specific force, and ignore other forces being applied. The electrical signal output by the load cell is very small and requires specialized amplification. Fortunately, the [{{SERVER}}/products.php?product_id=DAQ1500 DAQ1500 - Wheatstone Bridge Phidget] will perform all the amplification and measurement of the electrical output.Load cells are designed to measure force in one direction.

They will often measure force in other directions, but the sensor sensitivity will be different, since parts of the load cell operating under compression are now in tension, and vice versa.

==How they work==
[[image:wheatstone.png|thumb|250px|Generic Wheatstone bridge configuration]]
Strain-gauge load cells convert the load acting on them into electrical signals. The measuring is done with very small resistor patterns called strain gauges - effectively small, flexible circuit boards. The gauges are bonded onto a beam or structural member that deforms when weight is applied, in turn deforming the strain-gauge. As the strain gauge is deformed, it’s electrical resistance changes in proportion to the load.

The changes to the circuit caused by force is much smaller than the changes caused by variation in temperature. Higher quality load cells cancel out the effects of temperature using two techniques. By matching the expansion rate of the strain gauge to the expansion rate of the metal it’s mounted on, undue strain on the gauges can be avoided as the load cell warms up and cools down. The most important method of temperature compensation involves using multiple strain gauges, which all respond to the change in temperature with the same change in resistance. Some load cell designs use gauges which are never subjected to any force, but only serve to counterbalance the temperature effects on the gauges that measuring force. Most designs use 4 strain gauges, some in compression, some under tension, which maximizes the sensitivity of the load cell, and automatically cancels the effect of temperature.

Other types of load cell exist which have half bridges (2 strain gauges) or quarter bridges but they require additional hardware to operate since you must complete the bridge to get the most accurate readings.

===What is a Wheatstone bridge?===
A Wheatstone bridge is an electrical circuit used to measure and unknown resistance by balancing 2 legs of a bridge circuit. One leg of which contains the unknown value. Wheatstone bridges are made up of 4 resistors or loads in a square with a voltage meter bridging 2 corners of the square and power/ground connected to the other corners. In the case of a load cell, these resistors are strain gauges.

<br clear=all>

==Installation==

===Single-Point Load Cells===

[[File:singlecell.jpg|link=|thumb|200px|A single-point load cell. Applying force to one end creates stress in the bar, causing the strain gauge encased in the white plastic to flex.]]

This Single Point Load Cell is used in small jewelry scales and kitchen scales. It’s mounted by bolting down the end of the load cell where the wires are attached, and applying force on the other end in the direction of the arrow. Where the force is applied is not critical, as this load cell measures a shearing effect on the beam, not the bending of the beam. If you mount a small platform on the load cell, as would be done in a small scale, this load cell provides accurate readings regardless of the position of the load on the platform.

<br clear=all>

===Button Load Cells===

[[File:buttoncell.jpg|link=|thumb|200px|A button load cell. Applying force to the bump in the middle of the cell causes a change in the output.]]

This Button Load Cell is used in applications that require a thin form factor. The bottom of the load cell is bolted, and force applied to the button on the top. By loading only the button, which is slightly rounded, the load cell is less sensitive to errors resulting from the load not pushing down exactly straight on the load cell.

[[File:button_cell_diagram.jpg|link=]]

<br clear=all>

===S-Type Load Cells===

[[File:scell.jpg|link=|thumb|200px|An S-type load cell. By pulling on both ends or pushing on both ends, the stress in the S changes and the cell's output changes.]]

This S-Type load cell can be operated in compression or tension, as illustrated below.

[[File:s_cell_diagram.jpg|link=]]
<br clear=all>

==Calibration==
You can use this simple formula to convert the measured mv/V output from the load cell to the measured force:

:<math>
\text{Expected Force or Weight} = K \times \text{(Measured mV/V} - \text{Offset)}
</math>

Where K is gain value that will change depending on what unit of force or weight you want to measure. Since the offset varies between individual load cells, it’s necessary to measure it for each sensor. Record the output of the load cell at rest on a flat surface with no force on it. The mv/V output measured by the Bridge is the offset.

From there we just need to determine the K factor. Take another measurement at some non-zero load (which you know the weight of). Now it's just a matter of solving the above equation for K. From that point forward we can apply the formula to new measured values to determine the force applied.

The K and offset values are something you could then include in your program to perform this calculation automatically.

===Multiple Load Cells===

For arrays of load cells there are two different configurations you can use:

*The first is to connect each load cell to different channels on your Phidgets. With this setup you would need to calibrate each load cell separately and then you would average the values from all the load cells together.
*The second configuration is to put all the load cells together in parallel on a single channel. This configuration allows you to calibrate all the load cells simultaneously and requires no extra math to work. The downside is that this configuration would not allow you to determine where on the weighing surface an object is resting (which may or may not be important in your application).

==Load Cell Specification Glossary==

When comparing load cells, there are a number of specifications to consider. This section lists and defines the properties commonly listed on load cells.

{{hiddenh3|Capacity}}
The maximum load the load cell is designed to measure within its specifications.

{{hiddenh3|Creep}}
The change in sensor output occurring over 30 minutes, while under load at or near capacity and with all environmental conditions and other variables remaining constant.

{{hiddenh3|FULL SCALE or FS}}
Used to qualify error - FULL SCALE is the change in output when the sensor is fully loaded. If a particular error (for example, Non-Linearity) is expressed as 0.1% F.S., and the output is 1.0mV/V, the maximum non-linearity that will be seen over the operating range of the sensor will be 0.001 mV/V. An important distinction is that this error doesn’t have to only occur at the maximum load. If you are operating the sensor at a maximum of 10% of capacity, for this example, the non-linearity would still be 0.001mV/V, or 1% of the operating range that you are actually using.

{{hiddenh3|Hysteresis}}
If a force equal to 50% of capacity is applied to a load cell which has been at no load, a given output will be measured. The same load cell is at full capacity, and some of the force is removed, resulting in the load cell operating at 50% capacity. The difference in output between the two test scenarios is called hysteresis.

{{hiddenh3|Excitation Voltage}}
Specifies the voltage that can be applied to the power/ground terminals on the load cell. In practice, if you are using the load cell with a Phidget, you don’t have to worry about this spec.

{{hiddenh3|Input Impedance}}
Determines the power that will be consumed by the load cell. The lower this number is, the more current will be required, and the more heating will occur when the load cell is powered. In very noisy environments, a lower input impedance will reduce the effect of Electromagnetic interference on long wires between the load cell and Phidget.

{{hiddenh3|Insulation Resistance}}
The electrical resistance measured between the metal structure of the load cell, and the wiring. The practical result
of this is the metal structure of the load cells should not be energized with a voltage, particularly higher voltages, as
it can arc into the Phidget. Commonly the load cell and the metal framework it is part of will be grounded to
earth or to your system ground.

{{hiddenh3|Maximum Overload}}
The maximum load which can be applied without producing a structural failure.

{{hiddenh3|Non-Linearity}}
Ideally, the output of the sensor will be perfectly linear, and a simple 2-point calibration will exactly describe the behaviour of the sensor at other loads. In practice, the sensor is not perfect, and Non-linearity describes the maximum deviation from the linear curve. Theoretically, if a more complex calibration is used, some of the non-linearity can be calibrated out, but this will require a very high accuracy calibration with multiple points.

{{hiddenh3|Non-Repeatability}}
The maximum difference the sensor will report when exactly the same weight is applied, at the same temperature, over multiple test runs.

{{hiddenh3|Operating Temperature}}
The extremes of ambient temperature within which the load cell will operate without permanent adverse change to any of its performance characteristics.

{{hiddenh3|Output Impedance}}
Roughly corresponds to the input impedance. If the Output Impedance is very high, measuring the bridge will distort the results. The Phidget carefully buffers the signals coming from the load cell, so in practice this is not a concern.

{{hiddenh3|Rated Output}}
Is the difference in the output of the sensor between when it is fully loaded to its rated capacity, and when it’s unloaded. Effectively, it’s how sensitive the sensor is, and corresponds to the gain calculated when calibrating the sensor. More expensive sensors have an exact rated output based on an individual calibration done at the factory.

{{hiddenh3|Resolution}}
Resolution is somewhat misleading when it comes to load cells. People often ask why we don't specify the resolution for our load cells. The fact of the matter is, resolution isn't really a property of the load cells. Rather, it is based on the equipment you are using to measure from the load cell instead. For example, the [[DAQ1500 User Guide|DAQ1500]] has a 24 bit ADC on board. This means that the resolution of a load cell connected to it is 24 bits. Since the excitation voltage for the DAQ1500 is 5V, your expected resolution is:

:<math>\text{Resolution} = \frac{5}{2^{24}}</math>

This is affected by the chosen gain as well. In general, noise means you won't be able to achieve this reliably but the point is that resolution is not a useful spec for a load cell to have.

{{hiddenh3|Safe Overload}}
The maximum axial load which can be applied without producing a permanent shift in performance characteristics beyond those specified.

{{hiddenh3|Compensated Temperature}}
The range of temperature over which the load cell is compensated to maintain output and zero balance within specified limits.

{{hiddenh3|Temperature Effect on Span}}
Span is also called rated output. This value is the change in output due to a 1-degree Celsius change in ambient temperature.
{{hiddenh3|Temperature Effect on Zero}}
The change in zero balance due to a 1-degree Celsius change in ambient temperature.

{{hiddenh3|Zero Balance}}
Zero Balance defines the maximum difference between the +/- output wires when no load is applied. Realistically, each sensor will be individually calibrated, at least for the output when no load is applied. Zero Balance is more of a concern if the load cell is being interfaced to an amplification circuit - the Phidget can easily handle enormous differences between +/-. If the difference is very large, the Phidget will not be able to use the higher Gain settings.

Load Cell Guide

2017-06-20T21:01:13Z

Burley:

[[Category: Primer]]
[[Image:loadcells.jpg|link=|400px]]
__TOC__

==Introduction==
A load cell is a force sensing module - a carefully designed metal structure, with small elements called strain gauges mounted in precise locations on the structure. Load cells are designed to measure a specific force, and ignore other forces being applied. The electrical signal output by the load cell is very small and requires specialized amplification. Fortunately, the [{{SERVER}}/products.php?product_id=DAQ1500 DAQ1500 - Wheatstone Bridge Phidget] will perform all the amplification and measurement of the electrical output.Load cells are designed to measure force in one direction.

They will often measure force in other directions, but the sensor sensitivity will be different, since parts of the load cell operating under compression are now in tension, and vice versa.

==How they work==
[[image:wheatstone.png|thumb|250px|Generic Wheatstone bridge configuration]]
Strain-gauge load cells convert the load acting on them into electrical signals. The measuring is done with very small resistor patterns called strain gauges - effectively small, flexible circuit boards. The gauges are bonded onto a beam or structural member that deforms when weight is applied, in turn deforming the strain-gauge. As the strain gauge is deformed, it’s electrical resistance changes in proportion to the load.

The changes to the circuit caused by force is much smaller than the changes caused by variation in temperature. Higher quality load cells cancel out the effects of temperature using two techniques. By matching the expansion rate of the strain gauge to the expansion rate of the metal it’s mounted on, undue strain on the gauges can be avoided as the load cell warms up and cools down. The most important method of temperature compensation involves using multiple strain gauges, which all respond to the change in temperature with the same change in resistance. Some load cell designs use gauges which are never subjected to any force, but only serve to counterbalance the temperature effects on the gauges that measuring force. Most designs use 4 strain gauges, some in compression, some under tension, which maximizes the sensitivity of the load cell, and automatically cancels the effect of temperature.

Other types of load cell exist which have half bridges (2 strain gauges) or quarter bridges but they require additional hardware to operate since you must complete the bridge to get the most accurate readings.

===What is a Wheatstone bridge?===
A Wheatstone bridge is an electrical circuit used to measure and unknown resistance by balancing 2 legs of a bridge circuit. One leg of which contains the unknown value. Wheatstone bridges are made up of 4 resistors or loads in a square with a voltage meter bridging 2 corners of the square and power/ground connected to the other corners. In the case of a load cell, these resistors are strain gauges.

<br clear=all>

==Installation==

===Single-Point Load Cells===

[[File:singlecell.jpg|link=|thumb|200px|A single-point load cell. Applying force to one end creates stress in the bar, causing the strain gauge encased in the white plastic to flex.]]

This Single Point Load Cell is used in small jewelry scales and kitchen scales. It’s mounted by bolting down the end of the load cell where the wires are attached, and applying force on the other end in the direction of the arrow. Where the force is applied is not critical, as this load cell measures a shearing effect on the beam, not the bending of the beam. If you mount a small platform on the load cell, as would be done in a small scale, this load cell provides accurate readings regardless of the position of the load on the platform.

<br clear=all>

===Button Load Cells===

[[File:buttoncell.jpg|link=|thumb|200px|A button load cell. Applying force to the bump in the middle of the cell causes a change in the output.]]

This Button Load Cell is used in applications that require a thin form factor. The bottom of the load cell is bolted, and force applied to the button on the top. By loading only the button, which is slightly rounded, the load cell is less sensitive to errors resulting from the load not pushing down exactly straight on the load cell.

[[File:button_cell_diagram.jpg|link=]]

<br clear=all>

===S-Type Load Cells===

[[File:scell.jpg|link=|thumb|200px|An S-type load cell. By pulling on both ends or pushing on both ends, the stress in the S changes and the cell's output changes.]]

This S-Type load cell can be operated in compression or tension, as illustrated below.

[[File:s_cell_diagram.jpg|link=]]
<br clear=all>

==Calibration==
You can use this simple formula to convert the measured mv/V output from the load cell to the measured force:

:<math>
\text{Expected Force or Weight} = K \times \text{(Measured mV/V} - \text{Offset)}
</math>

Where K is gain value that will change depending on what unit of force or weight you want to measure. Since the offset varies between individual load cells, it’s necessary to measure it for each sensor. Record the output of the load cell at rest on a flat surface with no force on it. The mv/V output measured by the Bridge is the offset.

From there we just need to determine the K factor. Take another measurement at some non-zero load (which you know the weight of). Now it's just a matter of solving the above equation for K. From that point forward we can apply the formula to new measured values to determine the force applied.

===Multiple Load Cells===

For arrays of load cells there are two different configurations you can use:

*The first is to connect each load cell to different channels on your Phidgets. With this setup you would need to calibrate each load cell separately and then you would average the values from all the load cells together.
*The second configuration is to put all the load cells together in parallel on a single channel. This configuration allows you to calibrate all the load cells simultaneously and requires no extra math to work. The downside is that this configuration would not allow you to determine where on the weighing surface an object is resting (which may or may not be important in your application).

==Load Cell Specification Glossary==

When comparing load cells, there are a number of specifications to consider. This section lists and defines the properties commonly listed on load cells.

{{hiddenh3|Capacity}}
The maximum load the load cell is designed to measure within its specifications.

{{hiddenh3|Creep}}
The change in sensor output occurring over 30 minutes, while under load at or near capacity and with all environmental conditions and other variables remaining constant.

{{hiddenh3|FULL SCALE or FS}}
Used to qualify error - FULL SCALE is the change in output when the sensor is fully loaded. If a particular error (for example, Non-Linearity) is expressed as 0.1% F.S., and the output is 1.0mV/V, the maximum non-linearity that will be seen over the operating range of the sensor will be 0.001 mV/V. An important distinction is that this error doesn’t have to only occur at the maximum load. If you are operating the sensor at a maximum of 10% of capacity, for this example, the non-linearity would still be 0.001mV/V, or 1% of the operating range that you are actually using.

{{hiddenh3|Hysteresis}}
If a force equal to 50% of capacity is applied to a load cell which has been at no load, a given output will be measured. The same load cell is at full capacity, and some of the force is removed, resulting in the load cell operating at 50% capacity. The difference in output between the two test scenarios is called hysteresis.

{{hiddenh3|Excitation Voltage}}
Specifies the voltage that can be applied to the power/ground terminals on the load cell. In practice, if you are using the load cell with a Phidget, you don’t have to worry about this spec.

{{hiddenh3|Input Impedance}}
Determines the power that will be consumed by the load cell. The lower this number is, the more current will be required, and the more heating will occur when the load cell is powered. In very noisy environments, a lower input impedance will reduce the effect of Electromagnetic interference on long wires between the load cell and Phidget.

{{hiddenh3|Insulation Resistance}}
The electrical resistance measured between the metal structure of the load cell, and the wiring. The practical result
of this is the metal structure of the load cells should not be energized with a voltage, particularly higher voltages, as
it can arc into the Phidget. Commonly the load cell and the metal framework it is part of will be grounded to
earth or to your system ground.

{{hiddenh3|Maximum Overload}}
The maximum load which can be applied without producing a structural failure.

{{hiddenh3|Non-Linearity}}
Ideally, the output of the sensor will be perfectly linear, and a simple 2-point calibration will exactly describe the behaviour of the sensor at other loads. In practice, the sensor is not perfect, and Non-linearity describes the maximum deviation from the linear curve. Theoretically, if a more complex calibration is used, some of the non-linearity can be calibrated out, but this will require a very high accuracy calibration with multiple points.

{{hiddenh3|Non-Repeatability}}
The maximum difference the sensor will report when exactly the same weight is applied, at the same temperature, over multiple test runs.

{{hiddenh3|Operating Temperature}}
The extremes of ambient temperature within which the load cell will operate without permanent adverse change to any of its performance characteristics.

{{hiddenh3|Output Impedance}}
Roughly corresponds to the input impedance. If the Output Impedance is very high, measuring the bridge will distort the results. The Phidget carefully buffers the signals coming from the load cell, so in practice this is not a concern.

{{hiddenh3|Rated Output}}
Is the difference in the output of the sensor between when it is fully loaded to its rated capacity, and when it’s unloaded. Effectively, it’s how sensitive the sensor is, and corresponds to the gain calculated when calibrating the sensor. More expensive sensors have an exact rated output based on an individual calibration done at the factory.

{{hiddenh3|Resolution}}
Resolution is somewhat misleading when it comes to load cells. People often ask why we don't specify the resolution for our load cells. The fact of the matter is, resolution isn't really a property of the load cells. Rather, it is based on the equipment you are using to measure from the load cell instead. For example, the [[DAQ1500 User Guide|DAQ1500]] has a 24 bit ADC on board. This means that the resolution of a load cell connected to it is 24 bits. Since the excitation voltage for the DAQ1500 is 5V, your expected resolution is:

:<math>\text{Resolution} = \frac{5}{2^{24}}</math>

This is affected by the chosen gain as well. In general, noise means you won't be able to achieve this reliably but the point is that resolution is not a useful spec for a load cell to have.

{{hiddenh3|Safe Overload}}
The maximum axial load which can be applied without producing a permanent shift in performance characteristics beyond those specified.

{{hiddenh3|Compensated Temperature}}
The range of temperature over which the load cell is compensated to maintain output and zero balance within specified limits.

{{hiddenh3|Temperature Effect on Span}}
Span is also called rated output. This value is the change in output due to a 1-degree Celsius change in ambient temperature.
{{hiddenh3|Temperature Effect on Zero}}
The change in zero balance due to a 1-degree Celsius change in ambient temperature.

{{hiddenh3|Zero Balance}}
Zero Balance defines the maximum difference between the +/- output wires when no load is applied. Realistically, each sensor will be individually calibrated, at least for the output when no load is applied. Zero Balance is more of a concern if the load cell is being interfaced to an amplification circuit - the Phidget can easily handle enormous differences between +/-. If the difference is very large, the Phidget will not be able to use the higher Gain settings.

Terms and Conditions

2017-06-07T19:18:25Z

Burley:

[[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 issue you an RMA number and will replace your defective product free of charge.

==Shipping==
===Last Call at 12:00PM===
Unless we are unusually busy most orders received before 12:00 PM Mountain Time - Canada (GMT-07:00) Monday to Friday will be shipped on the same day.

Orders which contain cut to length parts may not necessarily ship same day as there is significant processing time associated with these orders.

===Shipping Costs===
The shipping cost is calculated at Checkout and submitted for your review before you confirm your order. When multiple shipping options are available for your destination, we will list all available options and let you choose.

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

If you have your own account with UPS, you can use it and be billed directly by them. In that case you have more shipping options available to you.

===Shipping in Canada===
We use UPS Express Saver™ - Overnight delivery, and UPS Standard - 3 to 5 business days ground delivery.

===Shipping to the United States===
====UPS Express Saver™ - Overnight====

'''Shipments under $2000.00USD''' we pay all costs in bringing the goods to you including import duties and taxes. In other words your shipping costs are what we put on our invoice. Contact us if you are getting any extra invoices from UPS.

'''Shipments over $2000.00USD''', you are responsible for duty and taxes if applicable and will have to pay UPS directly on top of the shipping cost we put on our invoice.

====UPS Standard - Ground 3 to 5 business days====
'''Shipment under $800.00USD''', we pay all costs in bringing the goods to you including import duties and taxes. In other words your shipping costs are what we put on our invoice. Contact us if you are getting any extra invoices from UPS.

'''Shipment over $800.00USD''' UPS will collect Entry Preparation Fees directly from you when delivering the package, and for duty and taxes if applicable.

:'''Entry Preparation Fees'''
:*All rates are in U.S. funds
:*Rates do not include applicable duties or taxes

{| style="border:1px solid darkgray;" cellpadding="7px;"
|-style="background: #d1d1d1" align=center
! Value for duty|| UPS Standard Service
|-
|style="background: #f0f0f0" align=center|$0.00 to $800.00
|style="background: #f0f0f0" align=center|No Charge
|-
|style="background: #f0f0f0" align=center|$800.01 to $1,250.00
|style="background: #f0f0f0" align=center|$28.75
|-
|style="background: #f0f0f0" align=center|$1,250.01 to $2,500.00
|style="background: #f0f0f0" align=center|$40.50
|-
|style="background: #f0f0f0" align=center|Each Additional $1,000.00
|style="background: #f0f0f0" align=center|$1.95
|}

===International Shipments===
We use UPS Worldwide Express Saver™, and UPS Worldwide Expedited for international locations that cannot be reached with Express Saver.

Goods shipped to an international destination may be subject to import duties and taxes, which are levied once the goods reach your country. Additional charges for customs clearance must be borne by you; we have no control over these charges and cannot predict what they may be. Since customs policies vary widely from country to country, you should contact your local customs office for further information.

===Tracking your order===
You can track your shipment by going to www.UPS.ca and using the tracking number that was e-mailed to you when your order 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, when the package arrives there is no one to accept delivery UPS will redeliver 2 more times. This is standard UPS protocol. If delivery fails they will keep the package for 5 days and then return it to us. We will then refund you the cost you paid minus the cost of shipping (both directions) and a flat $50 charge to a maximum of the total cost of the package. This applies to packages which failed delivery due to no one being present as well as packages which were refused delivery by a person at the delivery location.

===Import Restrictions to Russia===
If you are wanting to ship an order to Russia you MUST have a valid business license number in order to complete the shipment. You can include this number in the comments field of the order form. The reason for this is best explained by UPS:

"Customs authorities in Russia have tightened restrictions on import shipments to Russia, in particular on dutiable shipments sent to private individuals. These shipments are currently under extraordinary scrutiny in an effort to improve accuracy of the accompanying shipping documentation. These additional requirements lead to an unprecedented number of customs holds and delays in delivery. UPS has therefore temporarily suspended the acceptance of dutiable shipments sent to private individuals in Russia until further notice. We regret this step and are confident that, together with the Russian customs authorities, a solution can be found. UPS continues to accept all non-dutiable document shipments to private individuals in Russia and all commercial shipments addressed to businesses." [http://www.ups.com/content/hr/en/about/news/service_updates/20100526_restrictions.html]

==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 will take back any unopened product for a period of 30 days from the date of purchase. Just call or e-mail us for a RMA number and ship the product back to Phidgets prepaid and we will refund your credit card as soon as we receive and inspect the returned goods.

Products that are returned after 30 days are subject to a re-stocking charge of 25% of the package's value (minimum $5.00) to a maximum of $500.

We do '''not''' accept returns after 90 days.

===Product under 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 purchase date. This warranty does not include damage resulting from accident or misuse. The warranty is also void if the product has been modified.

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, you will be given a RMA number and we will replace the defective product.

===We shipped the wrong/incomplete product===
{{ContactUs|Contact us}}, we will get the correct product sent to you immediately, we 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
|+'''Phidgets Inc. Holidays'''
! Holiday || Description || 2015 || 2016
|-
|style="background: #f0f0f0" align=center| New Year's Holiday
|style="background: #f0f0f0" align=center| First two days of January
|style="background: #f0f0f0" align=center| Jan 1
|style="background: #f0f0f0" align=center| Jan 1
|-
|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 25
|-
|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 23
|-
|style="background: #f0f0f0" align=center| Canada Day
|style="background: #f0f0f0" align=center| First day of July
|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 3
|style="background: #f0f0f0" align=center| Aug 1
|-
|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 5
|-
|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 10
|-
|style="background: #f0f0f0" align=center| Remembrance Day
|style="background: #f0f0f0" align=center| November 11
|style="background: #f0f0f0" align=center| Nov 11
|style="background: #f0f0f0" align=center| Nov 11
|-
|style="background: #f0f0f0" align=center| Christmas Holiday
|style="background: #f0f0f0" align=center| Dec 24 to the New Year
|style="background: #f0f0f0" align=center| Dec 24-31
|style="background: #f0f0f0" align=center| TBA
|-
|}

Terms and Conditions

2017-06-07T19:12:18Z

Burley:

[[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 issue you an RMA number and will replace your defective product free of charge.

==Shipping==
===Last Call at 12:00PM===
Unless we are unusually busy most orders received before 12:00 PM Mountain Time - Canada (GMT-07:00) Monday to Friday will be shipped on the same day.

Orders which contain cut to length parts may not necessarily ship same day as there is significant processing time associated with these orders.

===Shipping Costs===
The shipping cost is calculated at Checkout and submitted for your review before you confirm your order. When multiple shipping options are available for your destination, we will list all available options and let you choose.

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

If you have your own account with UPS, you can use it and be billed directly by them. In that case you have more shipping options available to you.

===Shipping in Canada===
We use UPS Express Saver™ - Overnight delivery, and UPS Standard - 3 to 5 business days ground delivery.

===Shipping to the United States===
====UPS Express Saver™ - Overnight====

'''Shipments under $2000.00USD''' we pay all costs in bringing the goods to you including import duties and taxes. In other words your shipping costs are what we put on our invoice. Contact us if you are getting any extra invoices from UPS.

'''Shipments over $2000.00USD''', you are responsible for duty and taxes if applicable and will have to pay UPS directly on top of the shipping cost we put on our invoice.

====UPS Standard - Ground 3 to 5 business days====
'''Shipment under $800.00USD''', we pay all costs in bringing the goods to you including import duties and taxes. In other words your shipping costs are what we put on our invoice. Contact us if you are getting any extra invoices from UPS.

'''Shipment over $800.00USD''' UPS will collect Entry Preparation Fees directly from you when delivering the package, and for duty and taxes if applicable.

:'''Entry Preparation Fees'''
:*All rates are in U.S. funds
:*Rates do not include applicable duties or taxes

{| style="border:1px solid darkgray;" cellpadding="7px;"
|-style="background: #d1d1d1" align=center
! Value for duty|| UPS Standard Service
|-
|style="background: #f0f0f0" align=center|$0.00 to $800.00
|style="background: #f0f0f0" align=center|No Charge
|-
|style="background: #f0f0f0" align=center|$800.01 to $1,250.00
|style="background: #f0f0f0" align=center|$28.75
|-
|style="background: #f0f0f0" align=center|$1,250.01 to $2,500.00
|style="background: #f0f0f0" align=center|$40.50
|-
|style="background: #f0f0f0" align=center|Each Additional $1,000.00
|style="background: #f0f0f0" align=center|$1.95
|}

===International Shipments===
We use UPS Worldwide Express Saver™, and UPS Worldwide Expedited for international locations that cannot be reached with Express Saver.

Goods shipped to an international destination may be subject to import duties and taxes, which are levied once the goods reach your country. Additional charges for customs clearance must be borne by you; we have no control over these charges and cannot predict what they may be. Since customs policies vary widely from country to country, you should contact your local customs office for further information.

===Tracking your order===
You can track your shipment by going to www.UPS.ca and using the tracking number that was e-mailed to you when your order 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 orders@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, when the package arrives there is no one to accept delivery UPS will redeliver 2 more times. This is standard UPS protocol. If delivery fails they will keep the package for 5 days and then return it to us. We will then refund you the cost you paid minus the cost of shipping (both directions) and a flat $50 charge to a maximum of the total cost of the package. This applies to packages which failed delivery due to no one being present as well as packages which were refused delivery by a person at the delivery location.

===Import Restrictions to Russia===
If you are wanting to ship an order to Russia you MUST have a valid business license number in order to complete the shipment. You can include this number in the comments field of the order form. The reason for this is best explained by UPS:

"Customs authorities in Russia have tightened restrictions on import shipments to Russia, in particular on dutiable shipments sent to private individuals. These shipments are currently under extraordinary scrutiny in an effort to improve accuracy of the accompanying shipping documentation. These additional requirements lead to an unprecedented number of customs holds and delays in delivery. UPS has therefore temporarily suspended the acceptance of dutiable shipments sent to private individuals in Russia until further notice. We regret this step and are confident that, together with the Russian customs authorities, a solution can be found. UPS continues to accept all non-dutiable document shipments to private individuals in Russia and all commercial shipments addressed to businesses." [http://www.ups.com/content/hr/en/about/news/service_updates/20100526_restrictions.html]

==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. In the event we are unable to determine what the package is, it will be refused and returned to the sender.

===Unopened Product===
Phidgets will take back any unopened product for a period of 30 days from the date of purchase. Just call or e-mail us for a RMA number and ship the product back to Phidgets prepaid and we will refund your credit card as soon as we receive and inspect the returned goods.

Products that are returned after 30 days are subject to a re-stocking charge of 25% of the package's value (minimum $5.00) to a maximum of $500.

We do '''not''' accept returns after 90 days.

===Product under 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 purchase date. This warranty does not include damage resulting from accident or misuse. The warranty is also void if the product has been modified.

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, you will be given a RMA number and we will replace the defective product.

===We shipped the wrong/incomplete product===
{{ContactUs|Contact us}}, we will get the correct product sent to you immediately, we 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
|+'''Phidgets Inc. Holidays'''
! Holiday || Description || 2015 || 2016
|-
|style="background: #f0f0f0" align=center| New Year's Holiday
|style="background: #f0f0f0" align=center| First two days of January
|style="background: #f0f0f0" align=center| Jan 1
|style="background: #f0f0f0" align=center| Jan 1
|-
|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 25
|-
|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 23
|-
|style="background: #f0f0f0" align=center| Canada Day
|style="background: #f0f0f0" align=center| First day of July
|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 3
|style="background: #f0f0f0" align=center| Aug 1
|-
|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 5
|-
|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 10
|-
|style="background: #f0f0f0" align=center| Remembrance Day
|style="background: #f0f0f0" align=center| November 11
|style="background: #f0f0f0" align=center| Nov 11
|style="background: #f0f0f0" align=center| Nov 11
|-
|style="background: #f0f0f0" align=center| Christmas Holiday
|style="background: #f0f0f0" align=center| Dec 24 to the New Year
|style="background: #f0f0f0" align=center| Dec 24-31
|style="background: #f0f0f0" align=center| TBA
|-
|}

1002 User Guide

2017-05-11T16:57:50Z

Burley:

[[Category:UserGuide]]

===Required Hardware===

* A 1002 Voltage Output Phidget
* A device that requires or measures a 0-10V signal
* A USB Cable
* A computer

===Connecting the Pieces===
[[Image:1002_0_Connecting_the_Hardware.jpg|300px|right|link=]]
# Connect the device to a pair of terminals on the 1002. Check the underside of the board to see which one is positive and which is negative.
# Connect the Phidget to your computer using the USB cable

<br clear="all">
==Testing Using Windows==

{{UGcontrolpanel|1002}}

{{ugVoltageOutput}}

{{UGotheros}}

==Technical Details==

===General===
Produces a voltage over -10V to +10V. This voltage will be asserted up to +-20mA (short-circuit). An error will be reported when this current is exceeded, and the voltage the customer is getting is no longer accurate. The voltage is produced with 12 bit resolution (4.8mV). The update rate or frequency of the outputs is dependant on the speed of your system.

===Connections===

The terminal blocks on this board are labelled on the underside to save space:

[[File:1002_0_Under.jpg|link=|400px]]

===Isolation===
The 1002 is not isolated. All 4 channels use the same ground.

===Current===
The PhidgetAnalog board will limit the available current per channel at approximately 20mA. For reliable results, don’t approach this limit, as it will vary from channel to channel. For maximum accuracy, limit the current to 5mA. If more than +- 20mA of current is drawn, the device goes into a constant current supply mode. When this happens, the current will be held constant at it’s maximum value, and the output voltage will depend on the value of the load that the device is trying to drive.

If your application requires a larger current source / sink, the analog output can be used as an input to a larger external amplifier circuit.

All the power is supplied by the USB bus.

===Further Reading===
For more information on analog outputs, see the [[Analog Output Primer]].

{{UGnext|}}

1002 User Guide

2017-05-11T16:57:32Z

Burley:

[[Category:UserGuide]]

===Required Hardware===

* A 1002 Voltage Output Phidget
* A device that requires or measures a 0-10V signal
* A USB Cable
* A computer

===Connecting the Pieces===
[[Image:1002_0_Connecting_the_Hardware.jpg|300px|right|link=|alt=Test]]
# Connect the device to a pair of terminals on the 1002. Check the underside of the board to see which one is positive and which is negative.
# Connect the Phidget to your computer using the USB cable

<br clear="all">
==Testing Using Windows==

{{UGcontrolpanel|1002}}

{{ugVoltageOutput}}

{{UGotheros}}

==Technical Details==

===General===
Produces a voltage over -10V to +10V. This voltage will be asserted up to +-20mA (short-circuit). An error will be reported when this current is exceeded, and the voltage the customer is getting is no longer accurate. The voltage is produced with 12 bit resolution (4.8mV). The update rate or frequency of the outputs is dependant on the speed of your system.

===Connections===

The terminal blocks on this board are labelled on the underside to save space:

[[File:1002_0_Under.jpg|link=|400px]]

===Isolation===
The 1002 is not isolated. All 4 channels use the same ground.

===Current===
The PhidgetAnalog board will limit the available current per channel at approximately 20mA. For reliable results, don’t approach this limit, as it will vary from channel to channel. For maximum accuracy, limit the current to 5mA. If more than +- 20mA of current is drawn, the device goes into a constant current supply mode. When this happens, the current will be held constant at it’s maximum value, and the output voltage will depend on the value of the load that the device is trying to drive.

If your application requires a larger current source / sink, the analog output can be used as an input to a larger external amplifier circuit.

All the power is supplied by the USB bus.

===Further Reading===
For more information on analog outputs, see the [[Analog Output Primer]].

{{UGnext|}}

OS - Linux

2017-02-14T17:56:27Z

Burley:

[[Category:OS]]
{{OSLang|[[File:icon-Linux.png|64x64px|left|link=OS - Linux]]|On Linux, Phidgets can be either plugged directly into a USB Port or run over a network using the [[#WebService | Network Service]].}}
__TOC__

You need kernel '''version 2.6''' (released in 2003) or later.

==Quick Downloads==

Linux has complete support for all Phidgets and their software APIs; the only thing it lacks when compared to Windows and OS X is a graphical user interface. We walk you through all steps for download, installation, checking, and starting to write code below.

If you are already a pro, and just want the downloads:
*[{{SERVER}}/downloads/libraries/libphidget.tar.gz Phidget Libraries for Linux]
*[{{SERVER}}/downloads/libraries/phidgetwebservice.tar.gz Phidget Network Service for Linux]
*[[Software License]]

==Getting Started with Linux==

{{#ev:youtube|6pXWhGzX4Fg}}

===Installing===

To install the libraries, follow these steps:

#Install libusb-1.0 development libraries - {{Code|libusb-1.0-0-dev}}.
#*Note that libusb-1.0 may be already on your system, but the development libraries probably aren't.
#*Search for {{Code|libusb-1.0-0-dev}} or similar in your distribution package directory via {{Code|sudo apt-get install libusb-1.0-0-dev}}
#*Or install [http://www.libusb.org/ from source].
#Unpack and install the [{{SERVER}}/downloads/libraries/libphidget.tar.gz Phidget Libraries]
#*From the main unpacked libraries directory, run:
#*:{{Code|./configure}}
#*:{{Code|make}}
#*:{{Code|sudo make install}}
#*This will compile phidget22.h and place the library into your gcc path

'''Note:''' Although these libraries are written in C, the additional libraries for Python, Java, and most other Phidget-supported languages depend on them so they must be installed no matter what else you want to do.

===Checking===

To confirm the libraries were installed and work correctly, you can check both the hardware and software sides of the interface. It is worth checking the software side first, because if it works then you know the hardware side is also okay.

====Software====

To confirm that the libraries were installed correctly and can be used in code, you can use the [{{SERVER}}/downloads/examples/phidget21-c-examples.tar.gz C examples].

The easiest way to confirm correct installation will be to compile and run the {{Code|HelloWorld}} C example, included in the examples download. This does not involve writing any C code, but it does involve compiling the example and running it, which is a quick process as we show below. If you feel more comfortable running the {{Code|HelloWorld}} example for your specific language, you can skip below and pick your language, but keep in mind that any problems could be with the C library installation and not necessarily with your language.

To compile and run the basic C example for checking your installation:

1. Unpack the Phidget Generic C Examples<br>
2. Open a terminal (often Ctrl-Alt-T) and go to the directory where the examples are unpacked<br>
3. Compile the {{Code|HelloWorld.c}} example:<br>
<div class="source">
<syntaxhighlight lang=bash>

gcc HelloWorld.c -o HelloWorld -lphidget21

</syntaxhighlight>
</div>
4. Run the {{Code|HelloWorld}} example:<br>
<div class="source">
<syntaxhighlight lang=bash>

sudo ./HelloWorld

</syntaxhighlight>
</div>
(The sudo is needed for USB access for now, see the [[#Setting udev Rules|Setting udev Rules]] section for how to change this)

The {{Code|-lphidget22}} will look in the standard library location for your Linux distribution (usually {{Code|/usr/lib/}}) for the Phidget 21 library file. Generally, libraries to be linked on Linux through {{Code|gcc}} have a naming convention. For example, {{Code|-lphidget22}} looks for the binary files '''{{Code|libphidget22.a}}''' and '''{{Code|libphidget22.so}}''' in the library location. These files are automatically put in the library location during the {{Code|make install}} step of [[#Installing | installing the libraries]].

The HelloWorld program will simply print out basic information for any device you plug in, and print a message upon unplugging the device. For example, starting the program, plugging in an Interface Kit Phidget, unplugging the Interface Kit, and pressing Enter displays:

<div class="source">
<syntaxhighlight lang=bash>

$ sudo ./HelloWorld

Opening...
Press Enter to end

Hello to Device Phidget InterfaceKit 8/8/8, Serial Number: 37299
Goodbye Device Phidget InterfaceKit 8/8/8, Serial Number: 37299

Closing...

</syntaxhighlight>
</div>

=CLEARED TO HERE=
====Hardware====

If the out-of-the-box examples do not work, make sure the Phidget is seen by your USB interface. To check this, you can use the kernel log reader {{Code|dmesg}}. Pipe the output of {{Code|dmesg}} into the utility {{Code|tail}} to read the last ten lines of the log:

<div class="source">
<syntaxhighlight lang=bash>

$> dmesg | tail
....(9 lines)....
[24344.013638] usb 2-1.2: new low speed USB device number 5 using ehci_hcd

</syntaxhighlight>
</div>

The number between the [ ] is the system time in seconds since the last boot up, so you can tell whether the event was recent or not. (This will also tell you the interrupt type of Phidget that is registered by the USB interface, see the [[#Common Problems and Solutions | common problems section below]] for more information on what this means.)

The Phidget should both connect and disconnect properly, so unplugging it should result in an additional line at the tail:

<div class="source">
<syntaxhighlight lang=bash>

$> dmesg | tail
....(8 lines)....
[24344.013638] usb 2-1.2: new low speed USB device number 5 using ehci_hcd
[25094.809328] usb 2-1.2: USB disconnect, device number 5

</syntaxhighlight>
</div>

If you don't see similar lines to these at the tail of your kernel log, take a look at the [[#Troubleshooting|troubleshooting]] section below, as well as the '''Communications''' section of our [[General Troubleshooting#Communications Troubleshooting|general troubleshooting page]].

====Troubleshooting====

If the examples '''do not''' work but USB '''does''' work (i.e. your computer can consistently see the device in the [[#Hardware|hardware]]), take a moment to check the basics:
* No other programs, drivers, or processes are using that USB port in software
* You are running the example program as root (or your udev rules have been set properly)
* You are using libusb 1.0 (not the older 0.1 release)
* You have compiled versions of libphidget21.a and libphidget21.so in your system library location (usually {{Code|/usr/lib}})
* The Phidget libraries are the latest version (visit the [[#Quick Downloads| quick downloads section]] to download them)
* Your Linux kernel version is 2.6 or later (type {{Code|uname -r}} in a terminal to get your kernel version)
* Check the [[#Common Problems and Solutions|common problems]] section below, some specific combinations can cause problems

If your problem doesn't seem to be fixed by these steps, make sure that the Phidget is seen '''consistently''' by USB (if it is erratic, try our [[General Troubleshooting|general troubleshooting guide]]). If you are still having problems after using the troubleshooting guide, please {{ContactUs|ask us}}!

==Programming Languages==

Now that you have the basic libraries installed, you can pick your language and begin programming!

If you are not using the [[#WebService | webservice]] (discussed below) to control a Phidget over a network, your next step will be to delve into the use of your specific language. Each page has its own set of specific libraries, code examples, and setup instructions.

On Linux, we recommend the following languages:

*[[Language - C/C++|C/C++]]
*[[Language - Java | Java]]
*[[Language - Python | Python]]
*[[Language - Ruby | Ruby]]
*[[Language - C Sharp | C#]] (Using [[Language - C Sharp#Mono|Mono]])
*[[Language - Flash AS3 | Flash AS3]]

You can also use these languages, but they do not support [[General Phidget Programming#Event Driven Code | event driven code]], and must use [[General Phidget Programming#Logic Code | logic code]] only:

*[[Language - MATLAB|MATLAB]]
*[[Language - Simulink|Simulink]]

==WebService==

The Phidget WebService allows you to remotely control a Phidget over a network.<br>This section helps you install, check, and use the WebService on Linux, but we also have an overview of the [[Phidget WebService]] in general.

===Installing the WebService===

To install the webservice, you must first have the [[#Installing|Phidget libraries installed]]. Then, follow these steps:

#Download '''avahi''' and its development libraries (mdnsresponder/bonjour is also an option, see the [[#WebService with mDNSResponder|webservice with mDNSResponder]] section)
#*Try {{Code|apt-cache search avahi}} in a terminal to find current packages
#*Often, this is installed in a default system, you may already have it
#Unpack and install the [{{SERVER}}/downloads/libraries/phidgetwebservice.tar.gz Phidgets WebService] source code tarball for Linux
#*From the unpacked WebService source code directory, run:
#*:{{Code|./configure}}
#*:{{Code|make}}
#*:{{Code|sudo make install}}
#*This will compile the executable {{Code|phidgetwebservice21}} and place it into {{Code|/usr/bin/phidgetwebservice21}}

====WebService with BSD====

For '''BSD''', the webservice has been found to work (BSD 8+) but requires a special configuration at the {{Code|./configure}} step:

<div class="source">
<syntaxhighlight lang=bash>
./configure LIBS=/usr/lib/libphidget21.so CFLAGS=-pthread
</syntaxhighlight>
</div>

Then {{Code|make}} and {{Code|sudo make install}} are the same.
<br>
The {{Code|LIBS}} argument may not be necessary, but sometimes BSD has trouble finding the library install location. The {{Code|CFLAGS}} argument is needed because BSD needs explicit linking for using threads.

====WebService with mDNSResponder====

To use '''mdnsresponder''' instead of avahi, change the configure script to be:

<div class="source">
<syntaxhighlight lang=bash>
./configure --enable-zeroconf=bonjour
</syntaxhighlight>
</div>

(To see all options, use {{Code|./configure --help}} like you would any configure script)

===Setting Up the WebService===

To set up and use the webservice, it helps to have [[#Setting udev Rules|set your udev rules]]. Otherwise, you must run the webservice as root.

You can get command line help with {{Code|phidgetwebservice21}} by using the {{Code|-h}} option:

<div class="source">
<syntaxhighlight lang=bash>
$ phidgetwebservice21 -h
</syntaxhighlight>

<syntaxhighlight lang=text>
'phidgetwebservice21' is a Phidget and Dictionary server from Phidgets Inc. See www.phidgets.com for more information.
Usage: phidgetwebservice21 [OPTION]
All parameters are optional. The default parameters are: port=5001, ServerName=(Computer Name) and no password

Options:
-p Port
-n Server Name
-P Password
-v Debug mode
-h Display this help
</syntaxhighlight>
</div>

You will see this help regardless of whether the webservice was correctly hooked in to avahi. In fact, you will see it even if you explicitly disabled mDNS in the {{Code|./configure}} step at compile:

<div class="source">
<syntaxhighlight lang=bash>
./configure --disable-zeroconf
</syntaxhighlight>
</div>

(To see all options, use {{Code|./configure --help}} like you would any configure script)

To find the defaults used by {{Code|phidget21webservice}}, the command line is the fastest way to learn the default server name and IP address of your computer:
*For the default server name, use {{Code|hostname}} on the command line.
*For your IP address, use {{Code|ifconfig -a}} on the command line.
**A line in the return text, under your main internet connection (usually {{Code|eth0}}) will say something like {{Code|inet addr:192.168.3.178}}, which is your IP.

Using a server name to connect would not be an option without avahi or some other mDNS service; in this case you would only have the option to use an IP address.

===Using the WebService===

To use a Phidget over the webservice, you'll want to:
* Obtain code you can use to open a Phidget remotely
* Start the webservice on the computer that directly connects to the Phidget
* Run your program on the remote computer that will control the Phidget over the network

The easiest way to test these steps on Linux is simply to set up the webservice and run the Phidget program on the same computer, using the loopback interface. Later, you can replace one of the two ends with a different computer and/or operating system.

To quickly create code to run remotely, in our examples we include commented out lines with openRemote() function calls of different types. In the C example for your device, find the line that says:

{{Code|CPhidget_open((CPhidgetHandle) device, -1)}}

and change it to be:

<div class="source">
<syntaxhighlight lang=bash>
int serial_number = 37299
CPhidget_openRemoteIP ((CPhidgetHandle) device, serial_number, "127.0.0.1", 5001, NULL)
</syntaxhighlight>
</div>

Except that you should replace '''37299''' with the serial number of your Phidget, which you can obtain from either the Phidget board itself, or from when you [[#Checking|ran the HelloWorld example code]]. The IP address "127.0.0.1" simply loops back to the same computer, and 5001 is the default port as found from using {{Code|phidget21webservice -h}} in [[#Setting Up the WebService|the Setting Up the WebService]] section. The NULL is used to not specify a password.

Save the changed example under a different filename. In the walkthrough here, we are using the {{Code|InterfaceKit.c}} example, and we rename it to be {{Code|InterfaceKitRemote.c}}

Compile your new C file. In our {{Code|InterfaceKitRemote.c}} case, this would be by:

<div class="source">
<syntaxhighlight lang=bash>
gcc InterfaceKitRemote.c -o InterfaceKitRemote -lphidget21
</syntaxhighlight>
</div>

1. Start two terminals to run this test, usually opened via Ctrl-Alt-T. Your [[#Setting udev Rules|udev rules]] need to be set up or you should use sudo for every command. First, start the webservice in Terminal #1:

[[Image:Linux_ws_start.png|link=]]

This will broadcast any Phidget events, and receive any Phidget requests, both over the network.

2. Start the InterfaceKitRemote program that you just compiled which will open the remote Phidget. In this case, it is {{Code|InterfaceKitRemote}}:

[[Image:Linux_ws_step2.png|link=]]

3. Now, plug in the Phidget! The {{Code|phidget21webservice}} program captures the attach and other events and sends them out over the network (in the background in Terminal #1) and the Phidget software objected opened with openRemote in Terminal #2 receives them:

[[Image:Linux_ws_step3.png|link=]]

4. You can confirm that the webservice was indeed behind this exchange by killing the webservice process while still allowing the remote program to run:

[[Image:Linux_ws_step4.png|link=]]

===Debugging the WebService===

In addition to enabling [[General Phidget Programming#Logging|logging]] in your Phidget code, you can get additional debugging information from the WebService itself. This additional debugging is enabled via a re-compile of the webservice. From the webservice source code directory, do:

<div class="source">
<syntaxhighlight lang=bash>
make clean

./configure --enable-debug

make

sudo make install
</syntaxhighlight>
</div>

If you suspect multicast DNS (mDNS) may be the problem, you can:
* Try compiling the webservice with mDNSResponder, as described in [[#Installing the WebService|Installing the WebService]], or
* Try compiling the webservice completely without mDNS, as described in [[#Setting Up the WebService|Setting Up the WebService]]

==Advanced Uses==

===Setting udev Rules===

If you don't want to be using {{Code|sudo}} to run Phidget programs (including the webservice) forever, you will want to create a {{Code|udev}} rule to allow yourself access to the Phidget when you are not root.

Udev has an easy way to set the owner and permissions of the USB interface of the Phidget - it finds all devices that match a given set of rules, and applies new traits to them. But you need to give udev something to match in order to apply the new settings. Here, we will tell udev to match the vendor code for Phidgets, Inc.

We recommend that you use the rules file included in the library download you have already installed. Check the README file included in that download for information on how exactly to install it.

The rules for udev are kept in files in {{Code|/etc/udev/rules.d/}} and are traditionally grouped into order of running (10 runs before 20, 30, etc) and device type (cd, network, etc). There should be one or more files in there already - if this is your first time editing udev rules take a look at them to see the syntax to use:
* Commas separate each pair with == or =
* One rule on each line, no line breaks
* Quotes around the value to be matched or changed
* Comments can be added on lines starting with #

Strictly speaking, the files run in lexical order (i.e. the order they're listed when you use {{Code|ls}}). A device can match many rules, and all will apply (if possible). If conflicting rules are found, the first rule found is followed.

===Starting the WebService at Boot===

If you are tired of starting the webservice on the command line all the time, you can have the webservice start when your system starts, every time.

====User Space====

If you are running a standard Linux machine with an X-server (Unity, KDE) the easiest way to do this is to have the Phidget WebService start when your x server starts.

In this case, the webservice will be running in user space, so your [[#Setting udev Rules|udev rules need to be set up]] for the your user permissions to be able to access the USB ports using libusb.

Within the X-windowing system, there is usually some sort of {{Code|System → Settings/Preferences → Startup}} that you can choose to add programs that start when a user session starts. On Ubuntu you can use Unity to find programs listing "startup" in their names to accomplish the same thing. This will eventually lead you to a graphical tool like this to simply add the {{Code|/usr/bin/phidgetwebservice21}} program:

[[Image:linux_ws_boot.png|400px|link=]]

====As A Service====

You would want to set the boot start of {{Code|phidgetwebservice21}} to be a service if you are running a server, or a headless machine. It is handy any time you need the webservice to be started as a booted, respawning service with a presence in different run levels and for all users.

A service is essentially a program that hangs out in the background, waiting to be used by some incoming task. When the service is needed, the service forks a program to handle that need. Most services that run on your Linux computer already have the ability to fork themselves.

The webservice, however, is just a binary on Linux - {{Code|phidgetwebservice21}} - and so we need a program that handles the forking for us. For this, we use the {{Code|start-stop-daemon}} program to spawn a standalone process for us, or kill it, based on our service-like start, stop, and restart commands.

To do this, we need:
# A script that tells the boot process how to start and handle the webservice (i.e. by using {{Code|start-stop-daemon}})
# A link from that script to the boot list
# An initialization file for the script

First, the script. We will walk through Debian here, both because it is such a common distribution and because it is the distribution that our [{{SERVER}}products.php?product_id=1073 Single Board Computer] runs. But {{Code|init}} is surprisingly diverse on Linux, including everything from a different boot order, to different initialization programs and structure, and even different runlevels.

On Debian (including Ubuntu), the initialization script covers:
* Runlevels that the service should be present on
* Dependencies of the service
* Name of the service and other informative data
* The location of the PIDFILE, which stores the process ID (pid) for later dealing with a spawned instance
* Any configuration file locations
* What to do when the service is given instructions to '''start''', '''stop''', or '''reload'''.

The Debian script we use to start the webservice on the [{{SERVER}}products.php?product_id=1073 Single Board Computer]:

<div class="source">
<syntaxhighlight line start="1" lang=bash>

#!/bin/sh

### BEGIN INIT INFO
# Provides: phidgetwebservice
# Required-Start: $network $remote_fs
# Required-Stop: $network $remote_fs
# Should-Start: avahi
# Should-Stop: avahi
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Phidget WebService
# Description: Phidget WebService for controlling Phidgets over the network.
### END INIT INFO

DESC="Phidget WebService"
NAME=phidgetwebservice
BIN=phidgetwebservice21
DAEMON=/usr/bin/$BIN
PIDFILE=/var/run/$NAME.pid
CFG=/etc/default/$NAME

# Gracefully exit if the package has been removed.
test -x $DAEMON || exit 0

# load config
pws_port="5001"
pws_serverid=""
pws_password=""
[ -f $CFG ] && . $CFG

start() {
[ -z "$pws_port" ] || OPTIONS="-p $pws_port "
[ -z "$pws_password" ] || OPTIONS="$OPTIONS-P $pws_password "

if [ -z "$pws_serverid" ]; then
OPTIONS="$OPTIONS -n $( hostname )"
else
OPTIONS="$OPTIONS -n $pws_serverid"
fi

echo -n "Starting $DESC: "
start-stop-daemon -S -b -q -p $PIDFILE -m -x $DAEMON -- $OPTIONS && echo "OK" || echo "ALREADY RUNNING"
}

stop() {
echo -n "Stopping $DESC: "
start-stop-daemon -K -q -p $PIDFILE -x $DAEMON && echo "OK" || echo "NOT RUNNING"
}

case "$1" in
start)
start
;;
stop)
stop
;;
restart|force-reload)
stop
sleep 1
start
;;
*)
echo "Usage: $0 {start|stop|restart}"
esac

exit 0
</syntaxhighlight>
</div>

Save the script into a file called {{Code|phidgetwebservice}}, and use {{Code|chmod 755}} to make it executable.

Also on Debian, startup service scripts should go in {{Code|/etc/init.d}}, and then put within the appropriate runlevel-numbered folder - by symbolic link. There is a handy tool to do this for you, called {{Code|insserv}}:

<div class="source">
<syntaxhighlight lang=bash>
sudo insserv -d phidgetwebservice
</syntaxhighlight>
</div>

The {{Code|insserv}} program is the program that makes use of the {{Code|### BEGIN INIT INFO...### END INIT INFO}} that appears at the top of the {{Code|phidgetwebservice}} script. Use {{Code|man insserv}} for more information. The {{Code|insserv}} tool handles the mess of finding the right runlevel folders (i.e. the {{Code|rc.d}} numbered folders) and making the appropriate links. You can see what links would be updated by running {{Code|insserv}} with the {{Code|-n}} option, for a dry run.

'''Note:''' When you run {{Code|insserv}}, all of the dependencies for the boot order are re-written. This means that all of the initialization scripts in {{Code|/etc/init.d}} are re-examined. So, you'll probably get a lot of output when you run the command.

Then, you can check that {{Code|phidgetwebservice}} is on the service list with:

<div class="source">
<syntaxhighlight lang=bash>
service --status-all
</syntaxhighlight>
</div>

And you can start it right now without rebooting like this:

[[Image:linux_system_service_start.png|link=]]

The {{Code|service}} command has many options to start and stop services like the phidgetwebservice, try {{Code|man service}} for more information.

At this point, you can follow the client instructions on [[#Using the WebService|using the webservice]] to create a loopback test for the new webservice service that should now be running.

The final piece, for future configuration changes, is that the {{Code|/etc/init.d}} script looks for the file {{Code|/etc/default/phidgetwebservice}} upon starting up. The file is expected to contain the port, server ID, and password for the server side of the webservice. These are also set in the {{Code|phidgetwebservice}} script in {{Code|init.d}}, as you can see from reading the code above, but if you want to change them a lot, you can edit the configuration file rather than changing the {{Code|phidgetwebservice}} script and re-installing by {{Code|insserv}} every time. The configuration file in {{Code|/etc/default/}} should contain the same syntax as that used in the script source above:

<div class="source">
<syntaxhighlight lang=bash>
pws_port="5001"
pws_serverid=""
pws_password=""
</syntaxhighlight>
</div>

===Cross-Compiling with a Custom Toolchain===

This would allow you to have the Phidget libraries compiled to include in code for an embedded device. When developing for an embedded device, you will often write code for it on your 'normal' computer, and then build the code to binary with a different target than the processor in your computer. Many microcontrollers do not have the ability to run a full operating system, and hence cannot compile code natively.

The collection of tools used to create binary code for a separate system is called a ''toolchain''. Compiling the Phidget libraries specifically for an embedded system, and placing them into the path for writing code on top of the libraries is like adding another link in this chain.

You can use the typical {{Code|./configure}} setup for custom build targets:

<div class="source">
<syntaxhighlight lang=bash>
./configure --prefix=toolchain_location --build=this_system --host=target_system
</syntaxhighlight>
</div>

For the Phidget libraries, the {{Code|./configure}} tool works this way as well. You'd use this in the [[#Installing|install the libraries section]] setup. For example, let's say you're building the libraries to develop code for the [{{SERVER}}products.php?product_id=1073 Single Board Computer] as a target. Your system is a standard Linux system (i686-pc-linux-gnu) and the target system for the SBC is {{Code|arm-linux-gnueabi}}. For this target, you'll need the base of the GNU embedded Debian chain:

<div class="source">
<syntaxhighlight lang=bash>
sudo apt-get install gcc-arm-linux-gnueabi
</syntaxhighlight>
</div>

Then, download the Phidget libraries [[#Quick Downloads|above]] and unpack them into a folder {{Code|phidget_libraries}}. If {{Code|/usr/arm-linux-gnueabi}} is the location of your ARM toolchain (downloaded above in {{Code|gcc-arm-linux-gnueabi}}), type:

<div class="source">
<syntaxhighlight lang=bash>
~/phidget_libraries $> ./configure --prefix=/usr/arm-linux-gnueabi --build=i686-pc-linux-gnu --host=arm-linux-gnueabi
</syntaxhighlight>
</div>

===Linux on Non-Standard Systems===

We occasionally get requests to use Phidgets on Linux systems other than a standard laptop or desktop. One example is the Raspberry Pi system. Often these systems include USB ports, so the combination makes sense.

Our libraries are installed by building from source, and their main dependency is the {{Code|libusb-1.0-0-dev}} library, so if you can get gcc on your machine (or set up a cross compiler for it) and you can also install the libusb-1.0 development headers, you can probably get Phidgets to work. Of course, we don't offer much support for these systems, so - depending on your system - expect to spend some raw time getting it up and going.

If you're new to the embedded computer thing, keep in mind that for these super basic systems, once you've gotten a power supply, and storage, and put the kernel you want on it, and then spent a couple of days of time getting things working, and more time getting your drivers going, costs add up pretty quickly. If you want a compact system that works right out of the box (and which can use all of our analog sensors in addition to our USB Phidgets), check out our [{{SERVER}}products.php?product_id=1073 Single Board Computer]. Our SBC3:
* Has many more USB ports than super-stripped devices, and also has digital and analog ports
* Includes a power supply and can run on batteries easily
* Has a nice amount of RAM, a decent embedded processor, and built-in onboard storage (we've run R, GRASS, and X11 on it)
* Includes installed Debian, working Phidget drivers, and [[Phidget WebService|networked Phidget drivers]] from the moment it ships
* Has access to the full Debian repository including Python, Mono .NET, Ruby, and gcc
* Has a kernel development kit with patch file and instructions for adding new drivers (bluetooth, wireless, and so on)
* Comes with very in-depth documentation and technical support by phone and email
* Etc, etc.
The [[Phidget WebService|networked support]] in particular allows it to work with your cell phone and more.

But if you really do want a raw hobbyist system to tinker with, go for it! We're all nerds here - we've been there too and we certainly understand!

==Common Problems and Solutions==

{{ProblemSolution|Low Speed Phidgets (Max of 8)|Linux will only schedule one low-speed interrupt transfer per millisecond.}}

You can find out the type of your Phidget by attaching it and then running <code><font size=3>dmesg | tail</font></code>, which will display the type of Phidget from your kernel logs, as described above in the [[#Hardware|hardware section]]. The practical consequence of this is if your system has many low speed Phidgets attached, they will each be throttled down. Low speed Phidgets require an interrupt transfer as often as every 8 milliseconds. A Linux system could only have up to 8 of these Phidgets attached.

{{ProblemSolution|Sample Overrun Error|The data read from a program, or the first packet on the WebService, can give a sample overrun error (EEPHIDGET_OVERRUN).}}

Linux only polls data from the analog inputs on Phidgets when you ask it to. So there is some delay between when you open the device and when it actually attaches when data from those inputs are accumulating...and overrunning the buffer. This is simply in the nature of how Linux polls USB - we recommend catching (but ignoring) this one-time initial error.

{{ProblemSolution|Raspberry Pi USB Current|Your device doesn't seem to run as expected on a Raspberry Pi.}}

The USB ports on the standard Raspberry Pi are only capable of supplying around 100mA reliably. Since USB specification dictates 500mA of current maximum, many USB devices require several hundred mA to run smoothly. Since the Pi cannot supply this much current it is common to see buggy performance or complete failure to run at all. The get around this you should use a USB hub connected to the Pi that has it's own external power supply. This will allow the devices connected to have as much power as they require.

Linear Motion Guide

2017-01-11T17:15:00Z

Burley:

[[Category:Primer]]
The goal of a linear system is to have an object or other subsystem move along a linear track with a controllable velocity and position. The key features of a linear system are the efficiency with which you can move the load, the speed you can move it at, and the accuracy with which you can position the load along the track. Typically a linear system will consist of 1 or more rails/shafts with linear bearings which support the load. The bearing surface is machined to be extremely smooth and is case hardened so it doesn't deform whatsoever under rated load. Then you will also need a drive mechanism so that you can actually control the position along your track. There are a number of options for this such as belt drives, chain drives, and ball screws. Which you use will depend on your specific requirements so lets briefly discuss why and how you would use each.

==Slides==
The first choice is for the type of track you use. The two options available are linear shaft and rail.

[[Image:Linear_slides.png|link=|700px|center]]

In most cases using rail is preferable. The continuous support under the shaft minimizes deflection under load and it also has many mounting holes along the track which makes for easier and more secure installation in your system. Rail also has the potential for longer travel distances as the shaft won't experience any deflection due to it's own weight. Of course, using rail isn't practical for all applications. In cases where you need to span a gap of some kind or the surface you are travelling along isn't easy to mount to then using suspended shaft is a suitable alternative to rail. There are also flange mount blocks for the shaft so you can mount to a perpendicular surface rather than the pillow blocks shown in the image above.

==Drive Systems==
There are three main ways to drive your system available from Phidgets:

===Ball Screws===
Ball screws allow for very precise positioning with very little backlash. They are also very efficient, meaning they don't require very much force to move a sizeable load in comparison to other methods. A ball screw system typically consists of 4 or 5 elements plus something to turn the screw. To support the screw you need a drive bearing and a support bearing. To apply force to your object you need a nut that will move along the screw (you can also have a housing for the nut depending on how you want to attach your load). Then you of course need the screw itself. Here is an example of a ball screw assembly using a stepper motor to direct drive the screw:

[[image:Ball_screw_assembly_wiki.png|link=|center|1000px]]

Since the ball screw isn't designed to apply force that is ''not'' in the direction of travel we want to use a sliding support system like the rails or shafts mentioned in the slide section. Ideally we should use 2 rails with 1 or more bearings on each. For example:

{|align="center"
|[[image:Ball_screw_drive_full.JPG|center|600px|link=]]||[[image:Belt_driven_ball_screw.JPG|center|600px|link=]]
|}

Note that here we used a belt to drive the ball screw rather than direct drive off the motor. This was just so that we could simplify the chassis. Belt drives allow for more misalignment than shaft couplers do. Here is a demonstration of how it looks and sounds:

{{#ev:youtube|_brx8IxYSik}}

===Belt Drive===
A sufficiently tensioned belt will move linearly between the 2 pulleys it is circulating on. We can take advantage of this by attaching something to the belt to have it get pulled along as well. Belt drives are not as precise as ball screws and can have some additional error if there is any slack in the belt. However, they are easier to set up than a ball screw, are more practical for long distance runs, are cheaper, and they can generally move things more quickly.

All you need for a belt drive system is a belt, and 2 pulleys. Similarly to a ball screw system the drive mechanism (your belt) won't be supporting any load other than in the axis of travel. This means that you will need a sliding track made from shaft or rail on which to rest your load. To attach the belt to your load we recommend using some specially designed belt clamps such as the [{{SERVER}}/products.php?product_id=TRM4226_0 TRM4226] and [{{SERVER}}/products.php?product_id=TRM4227_0 TRM4227]. They can be used to mount a belt to a flat surface on either side for example:

[[image:Belt_clamp.png|link=|750px|center]]

This style of clamping does reduce the maximum strength of the belt somewhat so you should factor that into your design. Here is an example of a functional single stage belt drive system:

[[image:Belt_drive_assembly_wiki.png|link=|1500px|center]]

This is all in reference to linear systems. If you want more information about belt systems in rotary systems you can refer to our [[Rotary Motion Primer]] here.

{{#ev:youtube|BAnt21tCL8I}}

===Chain Drive===
Chain drives work in an identical fashion to belt drives. They are a bit more complicated to work with but they have the advantage that they can handle much more load than a belt of similar size.

Just replace the pulleys with chain sprockets and the belt with a chain and you are done. Attaching chain to your load is a matter of putting a screw through a hole between chain pitches. For example:

[[image:Chain_mount.png|link=|center|700px]]

For more information on setting up chain systems you should have a look at our [[Rotary Motion Primer]] which goes into more depth about the specifics of working with roller chains.

Rotary Motion Guide

2017-01-11T17:08:54Z

Burley:

[[Category:Primer]]
In rotary systems, you have a rotating shaft which applies torque to do work. Typically this shaft is turned by an electric motor of some kind and then, through a series of belts/chains/couplers transmits that power to a final output shaft or arm or wheel which accomplishes the desired task. Why not just use the output shaft of the motor directly? There are two main reasons:

*You might want to gear the motor down further to increase the torque available by using pulleys or sprockets of differing sizes.
*The shaft on the motor itself isn't really designed for forces other than torque. It is difficult to put anything of significant size on the shaft without putting too much overhung (radial) load on the shaft which will stall the motor.

As a result, the base of any rotary system is the rotating shaft. Phidgets has 4 sizes of shaft available: 8mm, 12mm, 17mm, and 25mm. The 12, 17, and 25mm shafts also have a variant available with a keyway machined in the length of the shaft if you don't want to machine it yourself. These shafts need to be suspended on bearings, we do not sell any bearings currently but they are commonly available components that you can find locally. For the larger shaft sizes (17 and 25mm) we recommend using steel bearing housings.

==Motors==
Every system will need a motor or else there will be no motion (without external input). Phidgets offers a wide selection of motors of a number of different types that would all be suitable for rotary systems. For more information on this you can check out our primers for [[DC Motor and Controller Primer|DC motors]] and [[Stepper Motor and Controller Primer|Stepper motors]].
==Pulleys/Timing belts==
A belt is simply a loop of tough, flexible material such as rubber and kevlar with a series of teeth that mesh with the teeth on specially designed pulley wheels to synchronize two (or more) rotating shafts. Belts are a cheap options for shafts that are not axially aligned and tend to run quietly and smoothly. Belts are typically tensioned either by adjusting center to center distance between pulleys or via a tensioner/idler pulley. This leads to very low backlash and a high efficiency (as high as 98%).

We have two types of belts available, 2GT (6mm wide) and 5GT (15mm wide). Each comes in loops of varying circumferences. The 2GT belts are rated for 6lbs of working tension while the 5GT are rated for 100lbs. Belt systems are fairly simple, you have 2 or more pulleys and a belt that goes around all of them. One of the pulleys is driven by your motor and the other(s) are either connected to your load or in the case of an idler pulley are simply free spinning to act as a tensioner for the belt. For example, here is a system that uses a belt to transmit power form a stepper motor to a ball screw:

[[image:Belt driven ball screw.JPG|700px|center|link=]]

==Chain/Sprockets==
Pretty much everyone has at least seen a chain system in their life in the form of a bicycle. This system of course is driven by human input rather than a motor. Automated systems behave no differently though, you have several sprockets, and chain that wraps around them. One sprocket is driven and the others perform work on the load. Chain tends to be noisier than belts and cannot be tensioned as tightly meaning there is a bit more backlash inherent in the system. In exchange though, chain can move much heavier loads for their size.

We sell ANSI#25 and #40 chain and sprockets (that is 0.25" pitch and 0.5" pitch). The #25 is rated for 100lbs of working tension while the #40 is rated for 800lbs. Chain is sold by the meter and you can form closed loops of any length you'd like with the link kits that we sell. To calculate how many links you will need for a particular sprocket spacing you can use [http://www.botlanta.org/converters/dale-calc/sprocket.html this calculator], just enter in the number of teeth on each sprocket, the chain pitch, and the center to center distance between the sprockets to get the number of links you will need. If the number is not whole, you should always round up (and probably even add one). Once you know how many links you will require you will need to use the link kit to connect your chain up. This is where it gets a bit fiddly.

There are two ways to connect chain, you can either use a hammer and a pin of some kind to knock out one of the pins which you can then connect up with an offset link:

The other way is if you have a chain breaker tool you can remove an entire link properly and can use a normal split link. This process is a bit more tricky but it is stronger over all and will increase the length of the chain by a standard amount unlike the offset link which adds a sort of half link to your total length. To use a split link you must remove the snap ring and the top plate, then slot it into the chain and replace them both. For example:

[[image:Chain_link_insert_wiki.png|link=|center|1200px]]

A good example of a chain system is our MURVV robot. Here is how it's drive mechanism works:

[[Image:Murvv_chain.jpg|link=|center|700px]]

==Worm Gearboxes==
In general, worm gearboxes are just another type of gearbox that can be fitted to a motor. The main benefit of a worm drive is that it is all but impossible to back drive even when not powered. This is due to the steep angle used by the gears as they mesh together. As a result, this type of gearbox is not the most efficient. There is a lot of frictional loss at the mesh point and they will tend to run hot. That being said, in the context of the worm drives Phidget's sells, they are a means to substantially increase the output torque of our larger motors for applications where maximum strength is required. All our worm gearboxes have a 30:1 gear ratio and since the bearings built into the gearbox can handle much higher axial and radial loads that motors themselves you can easily direct drive very large loads from these gearboxes without having to set up an external mechanism.

==Bearings==
For the smaller bearings, installation is fairly straight forward. Simply mount the bearing onto your surface, slot the shaft in and tighten the set screws. However, for our larger bearings (12mm, 17mm and 25mm) there is a different system used known as an eccentric locking collar or eccentric collar lock. This is relatively simply to set up but you may not have seen this style of attachment before so lets have a look quickly at how it works and how to install it.

The locking mechanism works by putting a slightly eccentric hole in the bearing and using a collar with a matching hole. This way, when the collar is twisted on the shaft it will bind. Step by step:

[[image:empty_bearing.jpg|center|700px|link=]]

Notice how the wall of the bore is thinner on the right side than the left. This is also true of the collar which slides over the top of the shaft once it is in position. Insert the shaft in the bearing unit to the desired position:

[[image:uncollared_shaft.jpg|center|700px|link=]]

Next, put the collar onto the shaft and slide it down to the bearing. Turn the collar slowly until it seats on the lip of the bearing (i.e. the eccentricity of the holes lines up). Now you will want to tighten the collar by hand by turning it like you would a threaded cap. You will notice that it will bind by turning it in either direction within 180°. Be sure to turn the collar in the same direction the primary direction of rotation for the shaft in operation will be. Once the collar is tight, you will need to use a punch and a hammer to tighten it the last bit. Find the dead hole in the collar (not the set screw) and insert your punch. Angle the punch against the wall of the direction you have tightened the collar and give it a few solid taps with the hammer:

[[image:punch_collar.jpg|center|700px|link=]]

Now just tighten the set screw to ensure it doesn't loosen up with use and you are finished. To quickly demonstrate here is a video, note that I do not tighten the set screw in this video but that is straight forward enough so it was left out:

{{#ev:youtube|0v6NOY7aRbg}}

Linear Motion Guide

2016-11-09T14:49:35Z

Burley:

[[Category:Primer]]
The goal of a linear system is to have an object or other subsystem move along a linear track with a controllable velocity and position. The key features of a linear system are the efficiency with which you can move the load, the speed you can move it at, and the accuracy with which you can position the load along the track. Typically a linear system will consist of 1 or more rails/shafts with linear bearings which support the load. The bearing surface is machined to be extremely smooth and is case hardened so it doesn't deform whatsoever under rated load. Then you will also need a drive mechanism so that you can actually control the position along your track. There are a number of options for this such as belt drives, chain drives, and ball screws. Which you use will depend on your specific requirements so lets briefly discuss why and how you would use each.

==Slides==
The first choice is for the type of track you use. The two options available are linear shaft and rail.

[[Image:Linear_slides.png|link=|700px|center]]

In most cases using rail is preferable. The continuous support under the shaft minimizes deflection under load and it also has many mounting holes along the track which makes for easier and more secure installation in your system. Rail also has the potential for longer travel distances as the shaft won't experience any deflection due to it's own weight. Of course, using rail isn't practical for all applications. In cases where you need to span a gap of some kind or the surface you are travelling along isn't easy to mount to then using suspended shaft is a suitable alternative to rail. There are also flange mount blocks for the shaft so you can mount to a perpendicular surface rather than the pillow blocks shown in the image above.

==Drive Systems==
There are three main ways to drive your system available from Phidgets:

===Ball Screws===
Ball screws allow for very precise positioning with very little backlash. They are also very efficient, meaning they don't require very much force to move a sizeable load in comparison to other methods. A ball screw system typically consists of 4 or 5 elements plus something to turn the screw. To support the screw you need a drive bearing and a support bearing. To apply force to your object you need a nut that will move along the screw (you can also have a housing for the nut depending on how you want to attach your load). Then you of course need the screw itself. Here is an example of a ball screw assembly using a stepper motor to direct drive the screw:

[[image:Ball_screw_assembly_wiki.png|link=|center|1000px]]

Since the ball screw isn't designed to apply force that is ''not'' in the direction of travel we want to use a sliding support system like the rails or shafts mentioned in the slide section. Ideally we should use 2 rails with 1 or more bearings on each. For example:

{|align="center"
|[[image:Ball_screw_drive_full.JPG|center|600px|link=]]||[[image:Belt_driven_ball_screw.JPG|center|600px|link=]]
|}

Note that here we used a belt to drive the ball screw rather than direct drive off the motor. This was just so that we could simplify the chassis. Belt drives allow for more misalignment than shaft couplers do. Here is a demonstration of how it looks and sounds:

{{#ev:youtube|_brx8IxYSik}}

===Belt Drive===
A sufficiently tensioned belt will move linearly between the 2 pulleys it is circulating on. We can take advantage of this by attaching something to the belt to have it get pulled along as well. Belt drives are not as precise as ball screws and can have some additional error if there is any slack in the belt. However, they are easier to set up than a ball screw, are more practical for long distance runs, are cheaper, and they can generally move things more quickly.

All you need for a belt drive system is a belt, and 2 pulleys. Similarly to a ball screw system the drive mechanism (your belt) won't be supporting any load other than in the axis of travel. This means that you will need a sliding track made from shaft or rail on which to rest your load. There are a bunch of fancy ways to attach the belt to your load but the reality is it doesn't take much. A small metal plate and some screws is really all that is required. For example:

[[image:Belt_clamp.png|link=|600px|center]]

This style of clamping does reduce the maximum strength of the belt somewhat so you should factor that into your design. Here is an example of a functional single stage belt drive system:

[[image:Belt_drive_assembly_wiki.png|link=|1500px|center]]

This is all in reference to linear systems. If you want more information about belt systems in rotary systems you can refer to our rotary primer here INSERT LINK HERE.

{{#ev:youtube|BAnt21tCL8I}}

===Chain Drive===
Chain drives work in an identical fashion to belt drives. They are a bit more complicated to work with but they have the advantage that they can handle much more load than a belt of similar size.

Just replace the pulleys with chain sprockets and the belt with a chain and you are done. Attaching chain to your load is a matter of putting a screw through a hole between chain pitches. For example:

[[image:Chain_mount.png|link=|center|700px]]

For more information on setting up chain systems you should have a look at our [[Rotary Motion Primer]] which goes into more depth about the specifics of working with roller chains.

Rotary Motion Guide

2016-11-09T14:49:15Z

Burley:

T-Slot Guide

2016-11-09T14:48:49Z

Burley:

{|
|- valign=middle
| align=center width=300px| __TOC__
| [[Image:tsl_header.jpg|500px|link=]]
|}

[[Category:Primer]]

T-Slot is a framing system composed of extruded aluminum profiles which use the namesake slot as a mounting point for various hardware components. Phidgets carries three different series of T-Slot extrusions. A 20mm, 30mm, and 40mm standard. For each series we carry a single (20x20mm, 30x30mm, 40x40mm) and double (20x40mm, 30x60mm, 40x80mm) wide extrusion. The series you end up using depends where on the weight vs. strength scale your project ends up falling. Obviously the smaller extrusions will not be as strong and rigid as the larger extrusions. The manufacturer provides equations for calculating how strong the extrusions are on pages 11 and 12 of their catalogue which can be found [{{SERVER}}/documentation/Modular_Assembly_System.pdf here]. The modulus of elasticity is listed as approximately 70,000N/mm². The moment of inertia is listed under the specifications for the specific extrusion profile you are using. With those two parameters you should be able to calculate with reasonable accuracy the relationship between force applied and resultant beam deflection.

The first thing you will need to do is cut the extrusions to length. There are 2 ways to do with. Either with a band saw or a chop saw with an appropriate blade (there are carbide blades designed for cutting aluminum). Once your extrusions are cut down to size you will want to connect them together:

==Connecting Extrusions Together==
In order for this whole system to be useful you need a way to combine individual extrusions into a more complicated structure. There are a number of options available for this, each better suited for different situations.

===Screw Connectors===
These are the most basic form of connection. A simple bolt that goes from one extrusion to the next. In order to use a screw connector there are 2 prerequisite steps you must do before installing. You need to tap the first extrusion with an appropriate tap for the series you are using (check the product page for the screw connector for which tap is required), and you need to drill a hole in the second extrusion big enough to allow Allen key access to the head of the screw connector. For example, here is a piece of 30x60mm extrusion prepped for connecting:

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

Once this is done you can screw the connector into the newly tapped extrusion. When you get close to the end, slide the head of the connector into the slot on the other extrusion and tighten the rest of the way through the hole you drilled.

[[image:Screw_connections.png|center|link=|1200px]]

===Brackets===
The diecast aluminum as well as the T and L plate steel brackets allow you to strengthen joints that will experience particularly heavy loads. You should always use them to reinforce joints which already use another type of connector rather than connecting the extrusions ''purely'' via the brackets. For all three styles of bracket you will need a few nuts. We recommend preset or square, the T nuts won't work well for this application. Installation is fairly simple, you don't have to drill and preliminary holes or anything. Just insert the nuts and bolt the brackets on. For example:

[[image:Tsl_brackets.png|link=|center|1000px]]

===Inner Brackets===
The inner brackets are a special variant of bracket that are different enough from the other brackets that they deserve their own section. These brackets do not need to be used with other connection methods. They are suitable by themselves (though you could use a reinforcement as well if you wanted to). The one important distinction to make with these brackets is that there are two models of bracket, A and B. The difference is that the set screw hole is slightly canted so that the set screw pushes the bracketed extrusion into the other extrusion to tighten the hold. For example:

[[image:inner_bracket_ab.jpg|center|700px|link=]]

Notice how both brackets have the set screws canted towards the extrusion. This way the extrusion you are connecting to this one will be pulled in towards it when the set screws are tightened. The effect is small but important. The left-hand bracket in this case is the A series while the right-hand one is the B series. Here is a diagram showing which series is appropriate for which connection a bit more clearly:

[[image:Inner_bracket_ab_diagram.png|center|600px|link=]]

You should always use 2 inner brackets to connect 2 extrusions together.

[[image:TSL_90deg01_Small.jpg|center|link=]]

===Butt Connectors===
These connectors are ideally suited to connecting an extrusion to the middle of another extrusion in a T junction. They have a similar effect to the screw connectors but don't require access to the other side of the perpendicular extrusion (for example if you had another extrusion there already for a + configuration). They can also be used with the plate brackets if you want an even stronger connection (but not the diecast brackets). They do require that you drill a hole into the extrusion to use however. Specifically 13mm hole, 11mm deep and 16mm in from the end of the extrusion for the PG30 variant and a 17mm hole, 14mm deep and 22mm in from the end of the extrusion for the PG40 variant. These connectors should always be used in pairs (on opposite sides of an extrusion) so you will need to drill 2 such holes. Once done, you can insert the connectors and bolt the extrusions together using preset nuts or square nuts.

[[image:Butt_connector.png|center|link=|1200px]]

Notice that because of the way these connectors line up with the nuts they won't make a clean 90° corner. This is why they are better suited for use in the middle of an extrusion somewhere to make a T junction. For cleaner corners, we recommend you use the screw connectors instead.

===Cubic Connectors===
In addition to making 2D right angle corners, you may want to connect 3 extrusions together like in the corner of a cube. For this, you will want to use the cubic connectors. These connectors behave very much like screw connectors in that you must tap out the central hole on the end of the extrusion. You will then also need to insert a bore reducing sleeve (included with the connector) into the hole which will allow you to bolt the connector on. The PG30 variant requires an M12 tap while the PG40 variant requires an M14 tap.

[[image:Cubic_connector.png|center|link=|1200px]]

===Linear Bar Connectors===
To join two extrusions together to make a longer extrusion you can use linear bar connectors. They come in packages of 4 so that you can connect all 4 slots for strength but you could get away with just using 2 and it will be plenty strong. We recommend not using 2 at the minimum though. Nothing special needs to be done to prep the extrusions, you can simply slot the bar into the extrusions and tighten the set screws.

[[image:linear_connector.jpg|link=|center|700px]]

===Anchor Connectors===
Anchor connectors are the only real option available for connecting extrusions at ''non''-right angles. While they can also connect extrusions at right angles, there are other connection methods that are better suited for this case. To use an anchor connector you will need to drill a hole in the extrusion being butted up against the other. For the PG30 variant it will need to be a 12mm hole, 21mm deep and 30mm from the end of the extrusions (measure from the center of the extrusion if you have cut it at an angle) and for the PG40 variant it will need to be a 15mm hole, 27mm deep and 32mm from the end of the extrusion. Then, back out the hex head on the anchor so that it comes apart into two pieces:

[[image:anchor_disassembled.png|center|link=|700px]]

The half with the hex head will insert into the hole you have drilled while the half with the actual anchor slides into the central hole in the profile of the extrusion. Slide the pieces back together and tighten the hex head just enough that it bites and holds the halves together again. You can now slide the pivoting head into the slot on your other extrusion and tighten the hex head to clamp the extrusions together.

[[image:Anchor_install.png|center|1000px|link=]]

==Connecting Things to Extrusions==
T-Slot offers a convenient way to build frames for all manner of different applications. None of that is useful of course if you can't easily mount things to that frame. There are two main methods for attaching things to a frame. You can either bolt it directly to the frame with a small bracket or plate that is bolted on with some form of nut, or alternatively use the slot profile reducers to insert a panel into the frame which you can then mount to.

===Preset/Square/T Nuts===
Bolting something directly to the frame is the easiest method for attaching things to T-Slot structures. There are 3 options for nuts that work with each series (PG20, 30, 40).

====Preset nuts====
The preset nut is shaped to fit loosely into the slot so it can slide back and forth into position but not turn. This allows you to tighten the bolts to it with no fuss. These are the fastest possible option, with a good combination of strength and ease of use. Here is an example of an acrylic plate mounted to an extrusion with some preset nuts.

[[image:Preset_nut.png|center|link=|700px]]

One note on the bolts: The size of bolt required is dictated by the size of hole in the nut being used obviously. We have several bore sizes for each series of nut (20,30,40). The length of the bolt though is the tricky part. The bolt should ''not'' touch the extrusion at all, you want to make sure that the bolt is long enough to go through the object you are mounting on and sink into the nut far enough to get a strong connection but not so long that it sticks out the far side of the nut and digs into the aluminum as this will cause some wiggle in the mounting point. For example, for the 5mm thick acrylic plate above M6x10mm bolts were used. Since the nuts are about 6mm thick in the case of PG30 (which is what was used for this example) that lets the bolt go deep enough into the nut to be secure while still leaving about 1mm of clearance plus the distance between the nut and the extrusion.

====Square nuts====
Square nuts behave in almost exactly the same way as preset nuts except that they require you to put the tension spring on them and slid into the profile a bit more carefully. Technically the tensioner isn't totally necessary but it helps keep the nut in place while you are bolting to it. It also allows you to bolt things to a vertical surface more easily. See the preset nut section about the size and length of bolts you should use.

[[image:Square_nut.png|center|link=|1200px]]

====T nuts====
T nuts are the trickiest to use as well as the least secure of the 3 nut variants but in return they are the only one that can be used after the fact or on extrusions where the ends are not accessible for one reason or another. The ability to install T nuts directly on the side of an extrusion is very useful. They also allow you to disconnect a component quickly. To use a T nut you should start by screwing it on to the object loosely. Then orient the nuts so they are aligned and slot them into the extrusion. Finally, carefully turn the bolt heads until the nut is turned 90 degrees and is seated in the extrusion. Then tighten the bolts the rest of the way and you are done. See the preset nut section about the size and length of bolts you should use.

[[image:T_nut.png|link=|center|1200px]]

===Profile Reducers and Panel Mounts===
The profile reducers are plastic inserts for the T-slot slots which allow you to put panels in your structure. While the profile reducers grip surprisingly strong we still recommend you border the panel on at least 2 sides to ensure a secure hold though you could border the panel on all 4 sides if you wanted to be extra secure. The profile reducers are simple to cut to length with side cutters or even a sharp utility knife and they slot into the extrusions with minimal effort. They accept panels anywhere from 3-5mm in width. Here is an example of an acrylic panel being used but you could use anything you'd like (steel or aluminum plate, other types of plastic, even cardboard if you do desired).

[[image:Slot_reducers.png|center|link=|700px]]

===Feet and Castors===
In order to connect feet or castor wheels to your structure you will first have to install an adapter end plate. This requires tapping the face of the extrusion with an M6 tap or M14 tap for the 40x40mm and 40x80mm profiles respectively. These plates are only available for the PG40 series extrusions. Once the plate it installed, the foot or castor will screw into the central hole.

[[image:End_cap.png|center|link=|1200px]]

T-Slot Guide

2016-11-09T14:48:33Z

Burley:

{|
|- valign=middle
| align=center width=300px| __TOC__
| [[Image:tsl_header.jpg|500px|link=]]
|}

[[Category:Primer]]

T-Slot is a framing system composed of extruded aluminum profiles which use the namesake slot as a mounting point for various hardware components. Phidgets carries three different series of T-Slot extrusions. A 20mm, 30mm, and 40mm standard. For each series we carry a single (20x20mm, 30x30mm, 40x40mm) and double (20x40mm, 30x60mm, 40x80mm) wide extrusion. The series you end up using depends where on the weight vs. strength scale your project ends up falling. Obviously the smaller extrusions will not be as strong and rigid as the larger extrusions. The manufacturer provides equations for calculating how strong the extrusions are on pages 11 and 12 of their catalogue which can be found [{{SERVER}}/documentation/Modular_Assembly_System.pdf here]. The modulus of elasticity is listed as approximately 70,000N/mm². The moment of inertia is listed under the specifications for the specific extrusion profile you are using. With those two parameters you should be able to calculate with reasonable accuracy the relationship between force applied and resultant beam deflection.

The first thing you will need to do is cut the extrusions to length. There are 2 ways to do with. Either with a band saw or a chop saw with an appropriate blade (there are carbide blades designed for cutting aluminum). Once your extrusions are cut down to size you will want to connect them together:

==Connecting Extrusions Together==
In order for this whole system to be useful you need a way to combine individual extrusions into a more complicated structure. There are a number of options available for this, each better suited for different situations.

===Screw Connectors===
These are the most basic form of connection. A simple bolt that goes from one extrusion to the next. In order to use a screw connector there are 2 prerequisite steps you must do before installing. You need to tap the first extrusion with an appropriate tap for the series you are using (check the product page for the screw connector for which tap is required), and you need to drill a hole in the second extrusion big enough to allow Allen key access to the head of the screw connector. For example, here is a piece of 30x60mm extrusion prepped for connecting:

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

Once this is done you can screw the connector into the newly tapped extrusion. When you get close to the end, slide the head of the connector into the slot on the other extrusion and tighten the rest of the way through the hole you drilled.

[[image:Screw_connections.png|center|link=|1200px]]

===Brackets===
The diecast aluminum as well as the T and L plate steel brackets allow you to strengthen joints that will experience particularly heavy loads. You should always use them to reinforce joints which already use another type of connector rather than connecting the extrusions ''purely'' via the brackets. For all three styles of bracket you will need a few nuts. We recommend preset or square, the T nuts won't work well for this application. Installation is fairly simple, you don't have to drill and preliminary holes or anything. Just insert the nuts and bolt the brackets on. For example:

[[image:Tsl_brackets.png|link=|center|1000px]]

===Inner Brackets===
The inner brackets are a special variant of bracket that are different enough from the other brackets that they deserve their own section. These brackets do not need to be used with other connection methods. They are suitable by themselves (though you could use a reinforcement as well if you wanted to). The one important distinction to make with these brackets is that there are two models of bracket, A and B. The difference is that the set screw hole is slightly canted so that the set screw pushes the bracketed extrusion into the other extrusion to tighten the hold. For example:

[[image:inner_bracket_ab.jpg|center|700px|link=]]

Notice how both brackets have the set screws canted towards the extrusion. This way the extrusion you are connecting to this one will be pulled in towards it when the set screws are tightened. The effect is small but important. The left-hand bracket in this case is the A series while the right-hand one is the B series. Here is a diagram showing which series is appropriate for which connection a bit more clearly:

[[image:Inner_bracket_ab_diagram.png|center|600px|link=]]

You should always use 2 inner brackets to connect 2 extrusions together.

[[image:TSL_90deg01_Small.jpg|center|link=]]

===Butt Connectors===
These connectors are ideally suited to connecting an extrusion to the middle of another extrusion in a T junction. They have a similar effect to the screw connectors but don't require access to the other side of the perpendicular extrusion (for example if you had another extrusion there already for a + configuration). They can also be used with the plate brackets if you want an even stronger connection (but not the diecast brackets). They do require that you drill a hole into the extrusion to use however. Specifically 13mm hole, 11mm deep and 16mm in from the end of the extrusion for the PG30 variant and a 17mm hole, 14mm deep and 22mm in from the end of the extrusion for the PG40 variant. These connectors should always be used in pairs (on opposite sides of an extrusion) so you will need to drill 2 such holes. Once done, you can insert the connectors and bolt the extrusions together using preset nuts or square nuts.

[[image:Butt_connector.png|center|link=|1200px]]

Notice that because of the way these connectors line up with the nuts they won't make a clean 90° corner. This is why they are better suited for use in the middle of an extrusion somewhere to make a T junction. For cleaner corners, we recommend you use the screw connectors instead.

===Cubic Connectors===
In addition to making 2D right angle corners, you may want to connect 3 extrusions together like in the corner of a cube. For this, you will want to use the cubic connectors. These connectors behave vary much like screw connectors in that you must tap out the central hole on the end of the extrusion. You will then also need to insert a bore reducing sleeve (included with the connector) into the hole which will allow you to bolt the connector on. The PG30 variant requires an M12 tap while the PG40 variant requires an M14 tap.

[[image:Cubic_connector.png|center|link=|1200px]]

===Linear Bar Connectors===
To join two extrusions together to make a longer extrusion you can use linear bar connectors. They come in packages of 4 so that you can connect all 4 slots for strength but you could get away with just using 2 and it will be plenty strong. We recommend not using 2 at the minimum though. Nothing special needs to be done to prep the extrusions, you can simply slot the bar into the extrusions and tighten the set screws.

[[image:linear_connector.jpg|link=|center|700px]]

===Anchor Connectors===
Anchor connectors are the only real option available for connecting extrusions at ''non''-right angles. While they can also connect extrusions at right angles, there are other connection methods that are better suited for this case. To use an anchor connector you will need to drill a hole in the extrusion being butted up against the other. For the PG30 variant it will need to be a 12mm hole, 21mm deep and 30mm from the end of the extrusions (measure from the center of the extrusion if you have cut it at an angle) and for the PG40 variant it will need to be a 15mm hole, 27mm deep and 32mm from the end of the extrusion. Then, back out the hex head on the anchor so that it comes apart into two pieces:

[[image:anchor_disassembled.png|center|link=|700px]]

The half with the hex head will insert into the hole you have drilled while the half with the actual anchor slides into the central hole in the profile of the extrusion. Slide the pieces back together and tighten the hex head just enough that it bites and holds the halves together again. You can now slide the pivoting head into the slot on your other extrusion and tighten the hex head to clamp the extrusions together.

[[image:Anchor_install.png|center|1000px|link=]]

==Connecting Things to Extrusions==
T-Slot offers a convenient way to build frames for all manner of different applications. None of that is useful of course if you can't easily mount things to that frame. There are two main methods for attaching things to a frame. You can either bolt it directly to the frame with a small bracket or plate that is bolted on with some form of nut, or alternatively use the slot profile reducers to insert a panel into the frame which you can then mount to.

===Preset/Square/T Nuts===
Bolting something directly to the frame is the easiest method for attaching things to T-Slot structures. There are 3 options for nuts that work with each series (PG20, 30, 40).

====Preset nuts====
The preset nut is shaped to fit loosely into the slot so it can slide back and forth into position but not turn. This allows you to tighten the bolts to it with no fuss. These are the fastest possible option, with a good combination of strength and ease of use. Here is an example of an acrylic plate mounted to an extrusion with some preset nuts.

[[image:Preset_nut.png|center|link=|700px]]

One note on the bolts: The size of bolt required is dictated by the size of hole in the nut being used obviously. We have several bore sizes for each series of nut (20,30,40). The length of the bolt though is the tricky part. The bolt should ''not'' touch the extrusion at all, you want to make sure that the bolt is long enough to go through the object you are mounting on and sink into the nut far enough to get a strong connection but not so long that it sticks out the far side of the nut and digs into the aluminum as this will cause some wiggle in the mounting point. For example, for the 5mm thick acrylic plate above M6x10mm bolts were used. Since the nuts are about 6mm thick in the case of PG30 (which is what was used for this example) that lets the bolt go deep enough into the nut to be secure while still leaving about 1mm of clearance plus the distance between the nut and the extrusion.

====Square nuts====
Square nuts behave in almost exactly the same way as preset nuts except that they require you to put the tension spring on them and slid into the profile a bit more carefully. Technically the tensioner isn't totally necessary but it helps keep the nut in place while you are bolting to it. It also allows you to bolt things to a vertical surface more easily. See the preset nut section about the size and length of bolts you should use.

[[image:Square_nut.png|center|link=|1200px]]

====T nuts====
T nuts are the trickiest to use as well as the least secure of the 3 nut variants but in return they are the only one that can be used after the fact or on extrusions where the ends are not accessible for one reason or another. The ability to install T nuts directly on the side of an extrusion is very useful. They also allow you to disconnect a component quickly. To use a T nut you should start by screwing it on to the object loosely. Then orient the nuts so they are aligned and slot them into the extrusion. Finally, carefully turn the bolt heads until the nut is turned 90 degrees and is seated in the extrusion. Then tighten the bolts the rest of the way and you are done. See the preset nut section about the size and length of bolts you should use.

[[image:T_nut.png|link=|center|1200px]]

===Profile Reducers and Panel Mounts===
The profile reducers are plastic inserts for the T-slot slots which allow you to put panels in your structure. While the profile reducers grip surprisingly strong we still recommend you border the panel on at least 2 sides to ensure a secure hold though you could border the panel on all 4 sides if you wanted to be extra secure. The profile reducers are simple to cut to length with side cutters or even a sharp utility knife and they slot into the extrusions with minimal effort. They accept panels anywhere from 3-5mm in width. Here is an example of an acrylic panel being used but you could use anything you'd like (steel or aluminum plate, other types of plastic, even cardboard if you do desired).

[[image:Slot_reducers.png|center|link=|700px]]

===Feet and Castors===
In order to connect feet or castor wheels to your structure you will first have to install an adapter end plate. This requires tapping the face of the extrusion with an M6 tap or M14 tap for the 40x40mm and 40x80mm profiles respectively. These plates are only available for the PG40 series extrusions. Once the plate it installed, the foot or castor will screw into the central hole.

[[image:End_cap.png|center|link=|1200px]]

T-Slot Guide

2016-11-09T14:48:07Z

Burley:

{|
|- valign=middle
| align=center width=300px| __TOC__
| [[Image:tsl_header.jpg|500px|link=]]
|}

{{category:Primer}}

T-Slot is a framing system composed of extruded aluminum profiles which use the namesake slot as a mounting point for various hardware components. Phidgets carries three different series of T-Slot extrusions. A 20mm, 30mm, and 40mm standard. For each series we carry a single (20x20mm, 30x30mm, 40x40mm) and double (20x40mm, 30x60mm, 40x80mm) wide extrusion. The series you end up using depends where on the weight vs. strength scale your project ends up falling. Obviously the smaller extrusions will not be as strong and rigid as the larger extrusions. The manufacturer provides equations for calculating how strong the extrusions are on pages 11 and 12 of their catalogue which can be found [{{SERVER}}/documentation/Modular_Assembly_System.pdf here]. The modulus of elasticity is listed as approximately 70,000N/mm². The moment of inertia is listed under the specifications for the specific extrusion profile you are using. With those two parameters you should be able to calculate with reasonable accuracy the relationship between force applied and resultant beam deflection.

The first thing you will need to do is cut the extrusions to length. There are 2 ways to do with. Either with a band saw or a chop saw with an appropriate blade (there are carbide blades designed for cutting aluminum). Once your extrusions are cut down to size you will want to connect them together:

==Connecting Extrusions Together==
In order for this whole system to be useful you need a way to combine individual extrusions into a more complicated structure. There are a number of options available for this, each better suited for different situations.

===Screw Connectors===
These are the most basic form of connection. A simple bolt that goes from one extrusion to the next. In order to use a screw connector there are 2 prerequisite steps you must do before installing. You need to tap the first extrusion with an appropriate tap for the series you are using (check the product page for the screw connector for which tap is required), and you need to drill a hole in the second extrusion big enough to allow Allen key access to the head of the screw connector. For example, here is a piece of 30x60mm extrusion prepped for connecting:

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

Once this is done you can screw the connector into the newly tapped extrusion. When you get close to the end, slide the head of the connector into the slot on the other extrusion and tighten the rest of the way through the hole you drilled.

[[image:Screw_connections.png|center|link=|1200px]]

===Brackets===
The diecast aluminum as well as the T and L plate steel brackets allow you to strengthen joints that will experience particularly heavy loads. You should always use them to reinforce joints which already use another type of connector rather than connecting the extrusions ''purely'' via the brackets. For all three styles of bracket you will need a few nuts. We recommend preset or square, the T nuts won't work well for this application. Installation is fairly simple, you don't have to drill and preliminary holes or anything. Just insert the nuts and bolt the brackets on. For example:

[[image:Tsl_brackets.png|link=|center|1000px]]

===Inner Brackets===
The inner brackets are a special variant of bracket that are different enough from the other brackets that they deserve their own section. These brackets do not need to be used with other connection methods. They are suitable by themselves (though you could use a reinforcement as well if you wanted to). The one important distinction to make with these brackets is that there are two models of bracket, A and B. The difference is that the set screw hole is slightly canted so that the set screw pushes the bracketed extrusion into the other extrusion to tighten the hold. For example:

[[image:inner_bracket_ab.jpg|center|700px|link=]]

Notice how both brackets have the set screws canted towards the extrusion. This way the extrusion you are connecting to this one will be pulled in towards it when the set screws are tightened. The effect is small but important. The left-hand bracket in this case is the A series while the right-hand one is the B series. Here is a diagram showing which series is appropriate for which connection a bit more clearly:

[[image:Inner_bracket_ab_diagram.png|center|600px|link=]]

You should always use 2 inner brackets to connect 2 extrusions together.

[[image:TSL_90deg01_Small.jpg|center|link=]]

===Butt Connectors===
These connectors are ideally suited to connecting an extrusion to the middle of another extrusion in a T junction. They have a similar effect to the screw connectors but don't require access to the other side of the perpendicular extrusion (for example if you had another extrusion there already for a + configuration). They can also be used with the plate brackets if you want an even stronger connection (but not the diecast brackets). They do require that you drill a hole into the extrusion to use however. Specifically 13mm hole, 11mm deep and 16mm in from the end of the extrusion for the PG30 variant and a 17mm hole, 14mm deep and 22mm in from the end of the extrusion for the PG40 variant. These connectors should always be used in pairs (on opposite sides of an extrusion) so you will need to drill 2 such holes. Once done, you can insert the connectors and bolt the extrusions together using preset nuts or square nuts.

[[image:Butt_connector.png|center|link=|1200px]]

Notice that because of the way these connectors line up with the nuts they won't make a clean 90° corner. This is why they are better suited for use in the middle of an extrusion somewhere to make a T junction. For cleaner corners, we recommend you use the screw connectors instead.

===Cubic Connectors===
In addition to making 2D right angle corners, you may want to connect 3 extrusions together like in the corner of a cube. For this, you will want to use the cubic connectors. These connectors behave vary much like screw connectors in that you must tap out the central hole on the end of the extrusion. You will then also need to insert a bore reducing sleeve (included with the connector) into the hole which will allow you to bolt the connector on. The PG30 variant requires an M12 tap while the PG40 variant requires an M14 tap.

[[image:Cubic_connector.png|center|link=|1200px]]

===Linear Bar Connectors===
To join two extrusions together to make a longer extrusion you can use linear bar connectors. They come in packages of 4 so that you can connect all 4 slots for strength but you could get away with just using 2 and it will be plenty strong. We recommend not using 2 at the minimum though. Nothing special needs to be done to prep the extrusions, you can simply slot the bar into the extrusions and tighten the set screws.

[[image:linear_connector.jpg|link=|center|700px]]

===Anchor Connectors===
Anchor connectors are the only real option available for connecting extrusions at ''non''-right angles. While they can also connect extrusions at right angles, there are other connection methods that are better suited for this case. To use an anchor connector you will need to drill a hole in the extrusion being butted up against the other. For the PG30 variant it will need to be a 12mm hole, 21mm deep and 30mm from the end of the extrusions (measure from the center of the extrusion if you have cut it at an angle) and for the PG40 variant it will need to be a 15mm hole, 27mm deep and 32mm from the end of the extrusion. Then, back out the hex head on the anchor so that it comes apart into two pieces:

[[image:anchor_disassembled.png|center|link=|700px]]

The half with the hex head will insert into the hole you have drilled while the half with the actual anchor slides into the central hole in the profile of the extrusion. Slide the pieces back together and tighten the hex head just enough that it bites and holds the halves together again. You can now slide the pivoting head into the slot on your other extrusion and tighten the hex head to clamp the extrusions together.

[[image:Anchor_install.png|center|1000px|link=]]

==Connecting Things to Extrusions==
T-Slot offers a convenient way to build frames for all manner of different applications. None of that is useful of course if you can't easily mount things to that frame. There are two main methods for attaching things to a frame. You can either bolt it directly to the frame with a small bracket or plate that is bolted on with some form of nut, or alternatively use the slot profile reducers to insert a panel into the frame which you can then mount to.

===Preset/Square/T Nuts===
Bolting something directly to the frame is the easiest method for attaching things to T-Slot structures. There are 3 options for nuts that work with each series (PG20, 30, 40).

====Preset nuts====
The preset nut is shaped to fit loosely into the slot so it can slide back and forth into position but not turn. This allows you to tighten the bolts to it with no fuss. These are the fastest possible option, with a good combination of strength and ease of use. Here is an example of an acrylic plate mounted to an extrusion with some preset nuts.

[[image:Preset_nut.png|center|link=|700px]]

One note on the bolts: The size of bolt required is dictated by the size of hole in the nut being used obviously. We have several bore sizes for each series of nut (20,30,40). The length of the bolt though is the tricky part. The bolt should ''not'' touch the extrusion at all, you want to make sure that the bolt is long enough to go through the object you are mounting on and sink into the nut far enough to get a strong connection but not so long that it sticks out the far side of the nut and digs into the aluminum as this will cause some wiggle in the mounting point. For example, for the 5mm thick acrylic plate above M6x10mm bolts were used. Since the nuts are about 6mm thick in the case of PG30 (which is what was used for this example) that lets the bolt go deep enough into the nut to be secure while still leaving about 1mm of clearance plus the distance between the nut and the extrusion.

====Square nuts====
Square nuts behave in almost exactly the same way as preset nuts except that they require you to put the tension spring on them and slid into the profile a bit more carefully. Technically the tensioner isn't totally necessary but it helps keep the nut in place while you are bolting to it. It also allows you to bolt things to a vertical surface more easily. See the preset nut section about the size and length of bolts you should use.

[[image:Square_nut.png|center|link=|1200px]]

====T nuts====
T nuts are the trickiest to use as well as the least secure of the 3 nut variants but in return they are the only one that can be used after the fact or on extrusions where the ends are not accessible for one reason or another. The ability to install T nuts directly on the side of an extrusion is very useful. They also allow you to disconnect a component quickly. To use a T nut you should start by screwing it on to the object loosely. Then orient the nuts so they are aligned and slot them into the extrusion. Finally, carefully turn the bolt heads until the nut is turned 90 degrees and is seated in the extrusion. Then tighten the bolts the rest of the way and you are done. See the preset nut section about the size and length of bolts you should use.

[[image:T_nut.png|link=|center|1200px]]

===Profile Reducers and Panel Mounts===
The profile reducers are plastic inserts for the T-slot slots which allow you to put panels in your structure. While the profile reducers grip surprisingly strong we still recommend you border the panel on at least 2 sides to ensure a secure hold though you could border the panel on all 4 sides if you wanted to be extra secure. The profile reducers are simple to cut to length with side cutters or even a sharp utility knife and they slot into the extrusions with minimal effort. They accept panels anywhere from 3-5mm in width. Here is an example of an acrylic panel being used but you could use anything you'd like (steel or aluminum plate, other types of plastic, even cardboard if you do desired).

[[image:Slot_reducers.png|center|link=|700px]]

===Feet and Castors===
In order to connect feet or castor wheels to your structure you will first have to install an adapter end plate. This requires tapping the face of the extrusion with an M6 tap or M14 tap for the 40x40mm and 40x80mm profiles respectively. These plates are only available for the PG40 series extrusions. Once the plate it installed, the foot or castor will screw into the central hole.

[[image:End_cap.png|center|link=|1200px]]