1032 User Guide: Difference between revisions

From Phidgets Support
No edit summary
 
(28 intermediate revisions by 3 users not shown)
Line 1: Line 1:
__NOINDEX__
<metadesc>The PhidgetLED-64 controls the brightness, forward voltage, and current limit of up to 64 LEDs. Connects to your computer via USB.</metadesc>
[[Category:UserGuide]]
[[Category:UserGuide]]
{{UserguideTOC|1032.jpg|1032}}
==Getting Started==
==Getting Started==
{{UGIntro|1032}}
*[{{SERVER}}/products.php?product_id=1032 1032 LED Phidget]
*USB cable and computer
*power supply
*{{CT|LED|LEDs}} and {{CT|LEDCable|cables}}


===Checking the Contents===
{{UGbox|
'''You should have received:'''
* A PhidgetLED-64 Advanced board
* A 12VDC 2 Amps power supply
* 16 4-wire cables (for LEDs)
* A Mini-USB Cable
|
'''In order to test your new Phidget you will also need:'''
* Some LEDs
||}}


===Connecting the Pieces===
Next, you will need to connect the pieces:
{{UGbox|
[[Image:1031_0_Connecting_The_Hardware.jpg|500px|right|link=]]
#Connect the power supply to the PhidgetLED using the barrel connector or the power terminal block.
# Connect LEDs to the LED cables. Connect the red wire to the positive side and the black wire to the negative side.
# Cut one of the 4-wire cables to an appropriate length. Strip the wire ends and solder on 2 LEDs.  The longer lead of the LED (the anode) is connected to the red wire, and the shorter lead of the LED (the cathode, also marked with a notch in the base of the plastic case) is connected to the black wire. Insert the end of the 4-wire LED cable into the board connector.
# Connect your device to your computer using the USB cable.
# Connect the PhidgetLED to your computer using the MiniUSB cable.
# Plug the power supply into the barrel jack (or if your supply has no jack, screw the loose leads into the green terminal block- The ground wire in the "G" side and the positive wire in the "+" side).
|
[[File:1031_0_Connecting_The_Hardware.jpg|400px|link=]]
||}}


===Testing Using Windows 2000 / XP / Vista / 7===
<br clear="all">
{{UGIntroDone|1032}}


{{UGwin}}
==Using the 1032==
{{UGcontrolpanel|1032}}


===Running Phidgets Sample Program===
{{ugDigitalOutputLED|1032}}


{{UGwin2|'''LED-full'''}}
{{ugAddressingInformation}}


{{UGbox|
{{ugUsingYourOwnProgram|1032}}
Double Click on the [[File:Ph.jpg|link=]] icon to activate the Phidget Control Panel and make sure that the  '''Phidget LED 64 Advanced''' is properly attached  to your PC.
|[[File:1032_0_Control_Panel_Screen.jpg|400px|link=]]
|
# Double Click on Phidget LED 64 Advanced in the Phidget Control Panel to bring up LED-full and check that the box labelled Attached contains the word True.
# Select the LED Index.  If you connected your LEDs at the same position as the ones in the picture above, select 18, 19, 22 or 23.
# Use the LED Brightness slider to increase or decrease the LED brightness using pulse-width modulation.
# Select from the drop-down menu an appropriate anode voltage: 1.7V, 2.75V, 3.9V, or 5V.
# Use the current limit slider to choose an appropriate current limit up to a maximum of 80mA.
'''Note:''' Using the current slider could cause false temperature warnings and errors to be reported. To avoid seeing these warnings, set the current limit once and use the brightness slider to change the brightness of the LEDs rather than changing the current limit.
|[[File:1032_0_LED_Screen.jpg|400px|link=]]
}}
 
===Testing Using Mac OS X===
 
{{UGmac|Phidget LED 64 Advanced |LED-full}}
 
===Using Linux===
 
{{UGlinux}}
 
===Using Windows Mobile / CE 5.0 / CE 6.0===
 
{{UGce}}


==Technical Details==
==Technical Details==
 
===General===
The 1032 uses four controller chips that allow you to vary the current and voltage supplied to each channel. It uses pulse-width modulation to vary the brightness of each LED.
The 1032 uses four controller chips that allow you to vary the current and voltage supplied to each channel. It uses pulse-width modulation to vary the brightness of each LED.


===Multiple LEDs on a Single Channel===
===Multiple LEDs on a Single Channel===
You can have multiple LEDs hooked up to a single channel on the 1032, (for example, a short string of LEDs) to reduce the amount of wiring, although keep in mind that you'll lose control of the individual lights, and can only toggle or dim the entire string. When using multiple LEDs on a single channel, you'll need to increase the voltage limit for that channel. If the LEDs are too dim at the maximum voltage, you should spread them out to other channels.  
You can have multiple LEDs hooked up to a single channel on the 1032, (for example, a short string of LEDs) to reduce the amount of wiring, although keep in mind that you'll lose control of the individual lights, and can only toggle or dim the entire string. When using multiple LEDs on a single channel, you'll need to increase the voltage limit for that channel. If the LEDs are too dim at the maximum voltage, you should spread them out to other channels.  


===High-Current Considerations===
===High-Current Considerations===
If you're using high-current LEDs, you should spread your load evenly across the board to avoid having one of the controller chips overheat. There are four controller chips, each controlling the channels on a quarter of the board.  
If you're using high-current LEDs, you should spread your load evenly across the board to avoid having one of the controller chips overheat. There are four controller chips, each controlling the channels on a quarter of the board.  


'''Controller 1:''' 0, 1, 2, 3, 4, 5, 6, 7, 24, 25, 26, 27, 28, 29, 30, 31
{| class ="wikitable"
 
| align="center" style="background:#f0f0f0;"|'''Controller'''
'''Controller 2:''' 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23
| align="center" style="background:#f0f0f0;"|'''Channels '''
 
|-
'''Controller 3:''' 32, 33, 34, 35, 36, 37, 38, 39, 56, 57, 58, 59, 60, 61, 62, 63
|align=center| 1
 
|align=center| 0, 1, 2, 3, 4, 5, 6, 7, 24, 25, 26, 27, 28, 29, 30, 31
'''Controller 4:''' 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55
|-
|align=center| 2
|align=center| 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23
|-
|align=center| 3
|align=center| 32, 33, 34, 35, 36, 37, 38, 39, 56, 57, 58, 59, 60, 61, 62, 63
|-
|align=center| 4
|align=center| 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55
|}


===Board Connector Diagram===
===Board Connector Diagram===
[[File:1031_0_Connector_Drawing.jpg|400px|link=|center]]


[[File:1031_0_Connector_Drawing.jpg|400px|link=]]


The connector used on the 1032 LED board is a Molex 70543-0003. The mating connector used on our sensor cables is the Molex 50-57-9404.
The connector used on the 1032 LED board is a Molex 70543-0003. The mating connector used on our LED cables is the Molex 50-57-9404.


===Heat Dissipation and Thermal Protection===
===Heat Dissipation and Thermal Protection===
 
Projects that require a high supply voltage, or have a lot of heat being produced from over voltage settings, will have temperature problems. This can be mitigated somewhat by understanding how channels are grouped and how the heat is distributed around the controller. On the 1032 channels are split into four groups: (0-7,24-31), (8-23), (32-39, 56-63) and (40-55); each controlled by their own individual IC. Evenly distributing the LEDs that may produce a lot of heat across these groups will balance the load on the ICs and reduce the risk of thermal overload. When thermal overload occurs, the integrated circuit (IC) controlling the involved LEDs will disable the output of all the channels it controls. For example, if thermal overload occurs due to channel 12, all of the channels 8 through 23 will be disabled by the IC until the temperature back within the operating range. Thermal protection is activated when the die of the IC reaches approximately 160 degrees Celsius. Once the thermal overload has been corrected (i.e. the IC has cooled down), the output channels will be re-enabled with the same settings as before the thermal shutdown. An error message will be produced during thermal overload.
Projects that require a high supply voltage, or have a lot of heat being produced from over voltage settings, will have over-temperature problems. This can be mitigated somewhat by understanding how channels are grouped and how the heat is distributed around the controller. On the 1032 channels are split into four groups: (0-7,24-31), (8-23), (32-39, 56-63) and (40-55); each controlled by their own individual IC. Evenly distributing the LEDs that may produce a lot of heat across these groups will balance the load on the ICs and reduce the risk of thermal overload. When thermal overload occurs, the integrated circuit (IC) controlling the involved LEDs will disable the output of all the channels it controls. For example, if an over-temperature occurs due to channel 12, all of the channels 8 through 23 will be disabled by the IC until the temperature back within the operating range. Thermal protection is activated when the die of the IC reaches approximately 160 degrees Celsius. Once the over-temperature fault has been corrected (ie, the IC has cooled down), the output channels will be re-enabled with the same settings as before the thermal shutdown. An error message will be produced during an over-temperature.


===Further Reading===
===Further Reading===
For more information, take a look at the [[LED Guide]].


For more information, take a look at the [[LED Primer]].
{{UGnext|}}
 
==API==
{{UGapih}}
 
===Functions===
{{UGapi|int LEDCount() [get] : Constant
|Returns the number of LEDs that this board can drive. This may not correspond to the actual number of LEDs attached.
}}
 
{{UGapi|double Brightness(int LEDIndex) [get,set]
|Sets/Gets the brightness of an LED. Valid values are 0-100, with 0 being off and 100 being the brightest. This 0-100 value is converted internally to an 12-bit value (0-4095).
}}
 
{{UGapi|int CurrentLimitIndexed(int LEDIndex) [get,set]
|Sets/Gets the current limit of an LED. Valid current limits range from 0 to 80mA. The default current limit is 20mA.
}}
 
{{UGapi|int Voltage() [get,set]
|Sets/Gets the output voltage. Valid voltages are 1.7V, 2.75V, 3.9V and 5V, these will generally be delimited with an enumerator where possible, or an integer where not. The default voltage is 2.75V.
}}
 
===Events===
{{UGapi|Error(String errorDescription, int errorCode) [event]
|1032 uses the generic error event to stream back fault conditions. The fault can be identified by the errorDescriptionstring. The only fault currently reported is Thermal Shutdown (TSD).
}}
 
==Product History==
{{UGhist}}
{{UGrow|January 2013|0|200|Product Release}}

Latest revision as of 16:30, 1 June 2023


Getting Started

Welcome to the 1032 user guide! In order to get started, make sure you have the following hardware on hand:


Next, you will need to connect the pieces:

1031 0 Connecting The Hardware.jpg
  1. Connect LEDs to the LED cables. Connect the red wire to the positive side and the black wire to the negative side.
  2. Connect your device to your computer using the USB cable.
  3. Plug the power supply into the barrel jack (or if your supply has no jack, screw the loose leads into the green terminal block- The ground wire in the "G" side and the positive wire in the "+" side).


Now that you have everything together, let's start using the 1032!

Using the 1032

Phidget Control Panel

In order to demonstrate the functionality of the 1032, the Phidget Control Panel running on a Windows machine will be used.


The Phidget Control Panel is available for use on both macOS and Windows machines.

Windows

To open the Phidget Control Panel on Windows, find the Ph.jpg icon in the taskbar. If it is not there, open up the start menu and search for Phidget Control Panel

Windows PhidgetTaskbar.PNG

macOS

To open the Phidget Control Panel on macOS, open Finder and navigate to the Phidget Control Panel in the Applications list. Double click on the Ph.jpg icon to bring up the Phidget Control Panel.


For more information, take a look at the getting started guide for your operating system:


Linux users can follow the getting started with Linux guide and continue reading here for more information about the 1032.

First Look

After plugging the 1032 into your computer and opening the Phidget Control Panel, you will see something like this:

1032 Panel.jpg


The Phidget Control Panel will list all connected Phidgets and associated objects, as well as the following information:

  • Serial number: allows you to differentiate between similar Phidgets.
  • Channel: allows you to differentiate between similar objects on a Phidget.
  • Version number: corresponds to the firmware version your Phidget is running. If your Phidget is listed in red, your firmware is out of date. Update the firmware by double-clicking the entry.


The Phidget Control Panel can also be used to test your device. Double-clicking on an object will open an example.

Digital Output (LED)

Double-click on a Digital Output object, labelled LED Driver, in order to run the example:

1032 DigitalOutputLED Example.jpg


General information about the selected object will be displayed at the top of the window. You can also experiment with the following functionality:

  • From the Forward Voltage drop-down menu, select the appropriate voltage for your LED. It is recommended to set the forward voltage to the first setting above the maximum voltage specified by your LED's datasheet.
  • Use the Current Limit slider to set an appropriate limit for your LED. The current limit will be specified in your LED's datasheet.
  • Use the large button to toggle power to the LED.
  • Use the Duty Cycle slider to precisely control the amount of power supplied to the LED.


Finding The Addressing Information

Before you can access the device in your own code, and from our examples, you'll need to take note of the addressing parameters for your Phidget. These will indicate how the Phidget is physically connected to your application. For simplicity, these parameters can be found by clicking the button at the top of the Control Panel example for that Phidget.

The locate Phidget button is found in the device information box

In the Addressing Information window, the section above the line displays information you will need to connect to your Phidget from any application. In particular, note the Channel Class field as this will be the API you will need to use with your Phidget, and the type of example you should use to get started with it. The section below the line provides information about the network the Phidget is connected on if it is attached remotely. Keep track of these parameters moving forward, as you will need them once you start running our examples or your own code.

All the information you need to address your Phidget

Using Your Own Program

You are now ready to start writing your own code for the device. The best way to do that is to start from our Code Samples.

Select your programming language of choice from the drop-down list to get an example for your device. You can use the options provided to further customize the example to best suit your needs.

Code Sample Choose Language.png


Once you have your example, you will need to follow the instructions on the page for your programming language to get it running. To find these instructions, select your programming language from the Programming Languages page.

Technical Details

General

The 1032 uses four controller chips that allow you to vary the current and voltage supplied to each channel. It uses pulse-width modulation to vary the brightness of each LED.

Multiple LEDs on a Single Channel

You can have multiple LEDs hooked up to a single channel on the 1032, (for example, a short string of LEDs) to reduce the amount of wiring, although keep in mind that you'll lose control of the individual lights, and can only toggle or dim the entire string. When using multiple LEDs on a single channel, you'll need to increase the voltage limit for that channel. If the LEDs are too dim at the maximum voltage, you should spread them out to other channels.

High-Current Considerations

If you're using high-current LEDs, you should spread your load evenly across the board to avoid having one of the controller chips overheat. There are four controller chips, each controlling the channels on a quarter of the board.

Controller Channels
1 0, 1, 2, 3, 4, 5, 6, 7, 24, 25, 26, 27, 28, 29, 30, 31
2 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23
3 32, 33, 34, 35, 36, 37, 38, 39, 56, 57, 58, 59, 60, 61, 62, 63
4 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55

Board Connector Diagram

1031 0 Connector Drawing.jpg


The connector used on the 1032 LED board is a Molex 70543-0003. The mating connector used on our LED cables is the Molex 50-57-9404.

Heat Dissipation and Thermal Protection

Projects that require a high supply voltage, or have a lot of heat being produced from over voltage settings, will have temperature problems. This can be mitigated somewhat by understanding how channels are grouped and how the heat is distributed around the controller. On the 1032 channels are split into four groups: (0-7,24-31), (8-23), (32-39, 56-63) and (40-55); each controlled by their own individual IC. Evenly distributing the LEDs that may produce a lot of heat across these groups will balance the load on the ICs and reduce the risk of thermal overload. When thermal overload occurs, the integrated circuit (IC) controlling the involved LEDs will disable the output of all the channels it controls. For example, if thermal overload occurs due to channel 12, all of the channels 8 through 23 will be disabled by the IC until the temperature back within the operating range. Thermal protection is activated when the die of the IC reaches approximately 160 degrees Celsius. Once the thermal overload has been corrected (i.e. the IC has cooled down), the output channels will be re-enabled with the same settings as before the thermal shutdown. An error message will be produced during thermal overload.

Further Reading

For more information, take a look at the LED Guide.

What to do Next

  • Programming Languages - Find your preferred programming language here and learn how to write your own code with Phidgets!
  • Phidget Programming Basics - Once you have set up Phidgets to work with your programming environment, we recommend you read our page on to learn the fundamentals of programming with Phidgets.


Retrieved from "https://www.phidgets.com/docs/index.php?title=1032_User_Guide&oldid=33653"