gadgeteer Wiki Rss Feed

Updated Wiki: Socket Type S

JanKuceraMSFT — Fri, 19 Apr 2013 20:37:46 GMT

Socket Type S

Serial peripheral interface (SPI). Pin 7 is the master-out/slave-in (MOSI) line, pin 8 is the master-in/slave-out (MISO) line, and pin 9 is the clock (SCK) line. In addition, pins 3, 4 and 5 are general-purpose input/outputs, with pin 3 supporting interrupt capabilities.

Pinout

Pin 1	Pin 2	Pin 3	Pin 4	Pin 5	Pin 6	Pin 7	Pin 8	Pin 9	Pin 10
+3.3V	+5V	GPIO!	GPIO	GPIO	GPIO	MOSI	MISO	SCK	GND

Legend:

GPIO	A general-purpose digital input/output pin, operating at 3.3 Volts.
!	Interrupt-capable and software pull-up capable GPIO (the pull-up is switchable and in the range of 10,000 to 100,000 Ω).
+3.3V	Connection to the +3.3V power net.
+5V	Connection to the +5V power net.
GND	Connection the power ground net.

Connector Pin Numbering

Pins numbers for the male 10-pin connector standard Gadgeteer socket, as seen from above. In most cases, the ribbon cables will have the pin 1 conductor marked in red.

Updated Wiki: HOWTO: Get the directory structure right with new modules

JanKuceraMSFT — Fri, 19 Apr 2013 20:36:09 GMT

Adding new modules/mainboards/kits to the repository

These instructions are targeted a module/mainboard/kit manufacturers who want to write software/installers for their hardware and are using this repository's directory structure.
It is slightly tricky to get the directory structure right when adding a new module/mainboard/kit. The instructions below are for a new module but they should translate to mainboard or kit.
NB this assumes you've installed the GadgeteerBuilderTemplates msi.

You will also need WiX 3.5 or newer installed.

1) Create a new project in Visual Studio using Gadgeteer/ModuleTemplate
- choose the precise location $/Main/Modules/<ManufacturerName>/<ModuleName> (create those directories if they don't exist)
- Set the project name as <ModuleName> and the solution name also as <ModuleName>
- Tick "Create directory for Solution"
- Untick "Add To Source Control"
2) Right click on the solution and "Open Folder in Windows Explorer"
3) Close the solution!
4) At the moment, the structure is $/Main/Modules/<ManufacturerName>/<ModuleNamedir1>/<ModuleNamedir2>/<ModuleName>.sln etc. Rename <ModuleName_dir2> to "Software", so it ends up being $/Main/Modules/<ManufacturerName>/<ModuleName>/Software/<ModuleName>.sln.

Done! Now you can reopen the SLN and edit your project - do read the Readme.txt file in the project for detailed help on using the template. To add to source control, right click on the solution, and "Add Solution to Source Control".

Updated Wiki: DaisyLink Manufacturer Codes

JanKuceraMSFT — Fri, 19 Apr 2013 20:35:26 GMT

DaisyLink Manufacturer Codes

These are hexadecimal format, single byte values.
Please see the Module Builder's Guide for more information on the DaisyLink protocol.

0x00 To be used for prototyping new modules - if you want to distribute modules outside your organisation, please get in touch at gadgeteer@microsoft.com to get a manufacturer code assigned (and don't use 0x00!)
0x01 Microsoft Research
0x10 GHIElectronics
0x11 Oberon Microsystems
0x12 DFRobot
0x13 BreakContinue
0x14 SolderMonkey
0x15 dotnetwarrior

Updated Wiki: .NET Gadgeteer Socket Types

JanKuceraMSFT — Fri, 19 Apr 2013 20:34:42 GMT

.NET Gadgeteer Socket Types

Socket types allow mainboards and modules to specify how they connect to one another, and are a key concept in .NET Gadgeteer.

Socket Types on a Mainboard

Every socket on a Gadgeteer mainboard is labelled with a number that uniquely identifies it. It is also labelled with one or more letters, and each letter corresponds to a different socket type.

Taken together, the letters describe the electrical and communication capabilities of the individual pins on that socket. (This is sometimes referred to as the pinout of the socket). Each socket type letter is simply a shorthand description of what each of the pins on the socket can do. The image on the right shows a mainboard socket - socket number 10 - that supports socket types A, I, T and X.

The socket type A definition, for example, specifies that pin 1 is connected to the +3.3V supply, that pin 2 is connected to the +5V supply and that pin 10 is connected to system ground. Pins 3, 4 and 5 are specified as analog inputs, with pins number 3 and 4 doubling as general-purpose input/output. In addition, pin number 6 is a general-purpose input/output, and pin number 3 supports interrupt capabilities. Pins 7, 8 and 9 are marked as undefined, which means that for a socket that supports only socket type A they will be left unconnected.

Pin 1	Pin 2	Pin 3	Pin 4	Pin 5	Pin 6	Pin 7	Pin 8	Pin 9	Pin 10
+3.3V	+5V	AIN (G!)	AIN (G)	AIN	GPIO	[UN]	[UN]	[UN]	GND

Pinout specified by the socket type A definition.

A mainboard socket can support multiple types, in which case the pinouts for multiple socket types are combined. This works as long as each pin is actually capable of supporting the various combinations of functionality that may be required.

Pin 1

Pin 2

Pin 3

Pin 4

Pin 5

Pin 6

Pin 7

Pin 8

Pin 9

Pin 10

+3.3V

+5V

AIN (G!)

GPIO!

AIN (G)

GPIO

AIN

GPIO

SDA

SCL

GND

Pinout for a single mainboard socket that supports types A, I, T and X.

Socket Types on a Module

Gadgeteer modules are also labelled with one or more letters, which are usually found close to the socket itself. The picture on the right shows a close-up of a Gadgeteer module socket, labelled XY. This means that the module can be connected to a mainboard socket that supports either socket type X or type Y. It is also possible, although rare, that a module is labelled by letters joined by an ampersand (for example, A&I), in which case it must be connected to a socket that supports both types A and I.

A module might use all or only some of the pins and capabilities offered by the socket types it is labelled with. In order to understand the exact pinout of a module, it is often necessary to consult either its schematic or source code for its accompanying library.

List of Current Socket Types

This list may grow over time. For pinout details, click on the socket type letter on the list below.

A	Three analog inputs, with pins number 3 and 4 doubling as general-purpose input/output. In addition, pin number 6 is a general-purpose input/output, and pin number 3 supports interrupt capabilities.
B	Display (LCD) interface, carrying the blue component on pins 3 to 7, as well as the LCD enable line on pin 8 and the clock signal on pin 9.
C	Controller-area network (CAN, or CAN-Bus). Pins number 4 and 5 serve as the CAN transmit (TD) and receive (RD) pins, and double as general-purpose input/outputs. In addition, pins number 3 and 6 are general-purpose input/outputs, and pin number 3 supports interrupt capabilities.
D	A USB device interface for the mainboard to connect to a PC, usually for programming. Pins 4 and 5 are used as the dedicated USB data pins (D- and D+). In addition, pins 3, 6 and 7 are general-purpose input/outputs, with pin 3 supporting interrupt capabilities.
E	Ethernet PHY connection. Pins 6 to 9 are the dedicated transmit/receive lines to an Ethernet connector with integrated magnetics. Pins 4 and 5 are optional connections to the LEDs on the Ethernet connector.
F	Secure Digital Card (SD) or MMC (Multi Media Card) interface. Pins 4 to 9 are the dedicated data and control lines for this interface. In addition, pin 3 is a general-purpose digital input/output with interrupt capabilities.
G	Display (LCD) interface, carrying the green component on pins 3 to 8, as well as the backlight control line on pin 9.
H	USB host interface to connect USB peripherals to the mainboard. Pins 4 and 5 are used as the dedicated USB data pins (D- and D+). In addition, pins 3 is a general-purpose input/output with interrupt capabilities.
I	I2C interface. Pins 8 and 9 are the dedicated I2C data (SDA) and clock (SCL) lines. Note that a mainboard should include pull-up resistors for these pins, in the region of 2.2K Ohms. Modules must not include their own pull-ups on these lines. In addition, pins 3 and 6 are general-purpose input/outputs, with pin 3 supporting interrupt capabilities.
K	UART (serial line) interface operating at TTL levels, with hardware flow control capabilities. Pin 4 (TX) is data from the mainboard to the module, and pin 5 (RX) is data from the module to the mainboard. These lines are idle high (3.3V), and can double as general-purpose input/outputs. Pin 6 (RTS) is an output from the mainboard to the module, indicating that the module may send data. Pin 7 (CTS) is an output from the module to the mainboard indicating that the mainboard may send data. The RTS/CTS are 'not ready' if high (3.3V) and 'ready' if low (0V). In addition, pins 3 is a general-purpose input/output, supporting interrupt capabilities.
O	Analog output on pin 5. In addition, pins 3 and 4 are general-purpose input/outputs, and pin 3 includes interrupt capabilities.
P	Three pulse-with modulated (PWM) outputs on pins 7, 8 and 9. Pins 7 and 9 double as GPIOs. In addition, pin 3 is an interrupt-capable GPIO, and pin 6 is a GPIO.
R	Display (LCD) interface, carrying the red component on pins 3 to 7, as well as the VSYNC line on pin 8 and the HSYNC line on pin 9.
S	Serial peripheral interface (SPI). Pin 7 is the master-out/slave-in (MOSI) line, pin 8 is the master-in/slave-out (MISO) line, and pin 9 is the clock (SCK) line. In addition, pins 3, 4 and 5 are general-purpose input/outputs, with pin 3 supporting interrupt capabilities.
T	Four-wire touch screen interface.
U	UART (serial line) interface operating at TTL levels. Pin 4 (TX) is data from the mainboard to the module, and pin 5 (RX) is data from the module to the mainboard. These lines are idle high (3.3V), and can double as general-purpose input/outputs. In addition, pins 3 and 6 are general-purpose input/outputs, with pin 3 supporting interrupt capabilities.
X	Three general-purpose input/output (GPIO) pins, with pin number 3 supporting interrupt capabilities.
Y	Seven general-purpose input/output (GPIO) pins, with pin number 3 supporting interrupt capabilities.
Z	Manufacturer specific. The pinout for this socket will vary between mainboards. Please refer to the individual mainboard's documentation for details.
*(DaisyLink)	DaisyLink downstream interface. Pin 3 is used for the DaisyLink neighbour bus, pin 4 is used for I2C SDA, pin 5 is used for I2C SCL. Note that this socket type should not appear on a mainboard, only on DaisyLink modules. The [MS] pins on this socket type can optionally support reflashing the firmware on the module.

Updated Wiki: Documentation

JanKuceraMSFT — Fri, 19 Apr 2013 20:33:53 GMT

Project Structure

.NET Gadgeteer is an open collaboration between Microsoft, hardware manufacturers, and end users. To understand how it all fits together, it is important to know that a .NET Gadgeteer device is composed of a mainboard and peripheral modules. The architecture of .NET Gadgeteer allows for many types of hardware modules to be built, by different manufacturers, which are compatible with different mainboards. In software, every .NET Gadgeteer end user app is based on the .NET Gadgeteer Core libraries as well as a module library for each hardware module used, and a mainboard library for the mainboard. Detailed documentation on the software and hardware interfaces is available.

Microsoft released and continues to maintain the .NET Gadgeteer Core libraries (found in $\Main\GadgeteerCore in the source code), as well as Visual Studio templates for Apps, Modules, Mainboards and Kits. Contributions are welcome; please use the discussions and issue tracker to share your thoughts for the future of GadgeteerCore. Microsoft also released and maintains a number of example module designs under $\Main\Modules\MSR (MSR ="Microsoft Research"), which comprise open source for software (using the Module template), firmware and hardware.

Microsoft provides two binary releases related to the .NET Gadgeteer Core (GadgeteerCore.msi and GadgeteerBuilderTemplates.msi). However, Microsoft does not provide releases for module/mainboard/kit libraries since these are maintained by the respective hardware manufacturers. Typically, an end user will receive a kit installer from the manufacturer of the hardware kit they purchase, and they will also need to install GadgeteerCore.msi released by Microsoft (which may be included by the kit manufacturer along with their kit installer).

Manufacturers of .NET Gadgeteer-compatible hardware are also welcome to open source their software/hardware designs using this repository. These are located under manufacturer-specific subdirectories under $\Main\Modules, $\Main\Mainboards and $\Main\Kits, and the contents of these subdirectories are maintained by the respective manufacturers.

Repository Structure

$\Main 
\ GadgeteerCore - .NET Gadgeteer core libraries maintained and released by Microsoft

\ Modules 
   \ ManufacturerName - This is the maintainer/releaser of the code in this subdirectory
      \ ModuleName
         \ Software - Created using Module Template (found in GadgeteerBuilderTemplates installer)
         \ Hardware - Hardware designs/schematics

\ Mainboards - similar to modules

\ Kits 
   \ DistributorName - This is the maintainer/releaser of the code in this subdirectory
      \ KitName
         \ Software - Created using Kit Template (found in GadgeteerBuilderTemplates installer)

Reference Notes/Lists

.NET Gadgeteer Socket Types
DaisyLink Manufacturer Codes
HOWTO: Get the directory structure right with new modules
Gadgeteer PCB Graphic in .ai format

Open Source License

The software source code available on this site is subject to the Apache License, version 2.0. All other files on this site, including hardware designs/source files and end user documentation, are licensed under the Creative Commons Attribution 3.0 license. As per the CodePlex terms of use, the copyright remains the property of the submitter for each file (or portion of a file/patch).

Updated Wiki: Home

JanKuceraMSFT — Fri, 19 Apr 2013 11:33:50 GMT

Introducing .NET Gadgeteer!

Microsoft .NET Gadgeteer is an open-source toolkit for building small electronic devices using the .NET Micro Framework and Visual Studio or Visual Studio Express. .NET Gadgeteer combines the advantages of object-oriented programming, solderless assembly of electronics with a kit of peripherals, and support for quick form-factor construction using computer-aided design. This powerful combination allows embedded and handheld devices to be iteratively designed, built and programmed in a matter of hours rather than days or weeks. Here is a video description of the platform - http://channel9.msdn.com/Blogs/Clint/NET-Gadgeteer.

The .NET Gadgeteer project is an open collaboration between Microsoft, hardware manufactuers, and end users. This website is targeted at those interested in developing .NET Gadgeteer-compatible mainboards and modules. If you are interested in buying and using .NET Gadgeteer compatible hardware, have a look at our website at http://netmf.com/gadgeteer/. If you already have hardware and are looking for support or installers, then please visit the hardware vendor's website.

What can I find on this website?

This site http://gadgeteer.codeplex.com/ is an open source repository for all aspects of the .NET Gadgeteer ecosystem. It is primarily intended to support hardware designers to build and release .NET Gadgeteer-compatible products, though we also expect the site to be useful for advanced end users who want to look at (and suggest changes to!) the core library and hardware sources/documentation.

The site includes source code and binary releases of the core .NET Gadgeteer libraries and templates, and detailed documentation on the hardware interface between mainboards and modules - these are maintained by Microsoft.

There are also software and hardware source files for .NET Gadgeteer compatible hardware modules (under $\Main\Modules in source control) and mainboards (under $\Main\Mainboards). While some of these are examples published by Microsoft (under the "MSR" subdirectory, short for "Microsoft Research"), others (under other subdirectory names) are maintained by individual hardware manufacturers and, except where expressly indicated, the contents of such subdirectories are not owned, maintained or released by Microsoft.

What is the history of this project?

.NET Gadgeteer started out in Microsoft Research Cambridge, where the Sensors and Devices group created it as a way to iterate quickly on device ideas. It quickly generated a great deal of interest from hobbyists, teachers and developers who wanted a platform that enables them to build exciting gadgets in a very short time. In order to get the project out of the lab and into the hands of others, we have set up this open source project to allow different hardware designers to create, build and provide .NET Gadgeteer-compatible mainboards and modules. For more details on the history of the project, check out this article.

Will Microsoft stay involved?

Let's deal with this question directly. It is not unheard of for corporations to open source technology while they walk away from it. This is not the case with .NET Gadgeteer. Just as we continue to make investments in the underlying .NET Micro Framework platform, we are planning continued support and investment in .NET Gadgeteer. In fact, we plan to be very proactive in helping partners get their products to market in the shortest time possible. In addition, we are maintaining the http://netmf.com/gadgeteer web site to support .NET Gadgeteer and to assist our partners in promoting their products to the user community. We plan to do what we can to develop an active ecosystem for .NET Gadgeteer where a number of companies are making compatible kits and modules for a variety of markets. For example, we will be hosting educational materials (lesson plans, etc) for a variety of ages on this site.

Who can I contact to ask questions about .NET Gadgeteer?

If you are an end user interested in getting .NET Gadgeteer hardware or have questions about existing hardware, please visit our end user website at http://netmf.com/gadgeteer. If you have any questions about building hardware compatible with .NET Gadgeteer or about the Core libraries and templates provided on this website, please either use the our discussion forums to ask any questions, or contact us directly at gadgeteer@microsoft.com.

Open source license

The software source code available on this site is subject to the Apache License, version 2.0. All other files on this site, including hardware designs/source files and end user documentation, are licensed under the Creative Commons Attribution 3.0 license. The copyright remains the property of the submitter for each file (or portion of a file/patch), and the respective licenses are provided by the copyright owners.

Updated Wiki: DaisyLink Manufacturer Codes

kerryh — Thu, 07 Feb 2013 17:40:03 GMT

DaisyLink Manufacturer Codes

Updated Wiki: Documentation

jamesscott — Fri, 11 May 2012 08:45:31 GMT

Project Structure

Repository Structure

$\Main 
\ GadgeteerCore - .NET Gadgeteer core libraries maintained and released by Microsoft

\ Modules 
   \ ManufacturerName - This is the maintainer/releaser of the code in this subdirectory
      \ ModuleName
         \ Software - Created using Module Template (found in GadgeteerBuilderTemplates installer)
         \ Hardware - Hardware designs/schematics

\ Mainboards - similar to modules

\ Kits 
   \ DistributorName - This is the maintainer/releaser of the code in this subdirectory
      \ KitName
         \ Software - Created using Kit Template (found in GadgeteerBuilderTemplates installer)

Reference Notes/Lists

.NET Gadgeteer Socket Types
DaisyLink Manufacturer Codes
HOWTO: Get the directory structure right with new modules
Gadgeteer PCB Graphic in .ai format

Open Source License

Updated Wiki: DaisyLink Manufacturer Codes

kerryh — Tue, 17 Apr 2012 20:43:13 GMT

DaisyLink Manufacturer Codes

Updated Wiki: DaisyLink Manufacturer Codes

kerryh — Tue, 17 Apr 2012 20:43:00 GMT

DaisyLink Manufacturer Codes

Updated Wiki: Documentation

jamesscott — Thu, 15 Mar 2012 16:57:53 GMT

Project Structure

.NET Gadgeteer is an open collaboration between Microsoft, hardware manufacturers, and end users. To understand how it all fits together, it is important to know that a .NET Gadgeteer device is composed of a mainboard and peripheral modules. The architecture of .NET Gadgeteer allows for many types of hardware modules to be built, by different manufacturers, which are compatible with different mainboards. In software, every .NET Gadgeteer end user app is based on the .NET Gadgeteer Core libraries as well as a module library for each hardware module used, and a mainboard library for the mainboard. Detailed documentation on the software and hardware interfaces is available.

Microsoft released and continues to maintain the .NET Gadgeteer Core libraries (found in $\Main\GadgeteerCore in the source code), as well as Visual Studio templates for Apps, Modules, Mainboards and Kits. Contributions are welcome; please use the discussions and issue tracker to share your thoughts for the future of GadgeteerCore. Microsoft also released and maintains a number of example module designs under $\Main\Modules\MSR (MSR ="Microsoft Research"), which comprise open source for software (using the Module template), firmware and hardware.

Microsoft provides two binary releases related to the .NET Gadgeteer Core (GadgeteerCore.msi and GadgeteerBuilderTemplates.msi). However, Microsoft does not provide releases for module/mainboard/kit libraries since these are maintained by the respective hardware manufacturers. Typically, an end user will receive a kit installer from the manufacturer of the hardware kit they purchase, and they will also need to installer GadgeteerCore.msi released by Microsoft (which may be included by the kit manufacturer along with their kit installer).

Manufacturers of .NET Gadgeteer-compatible hardware are also welcome to open source their software/hardware designs using this repository. These are located under manufacturer-specific subdirectories under $\Main\Modules, $\Main\Mainboards and $\Main\Kits, and the contents of these subdirectories are maintained by the respective manufacturers.

Repository Structure

$\Main 
\ GadgeteerCore - .NET Gadgeteer core libraries maintained and released by Microsoft

\ Modules 
   \ ManufacturerName - This is the maintainer/releaser of the code in this subdirectory
      \ ModuleName
         \ Software - Created using Module Template (found in GadgeteerBuilderTemplates installer)
         \ Hardware - Hardware designs/schematics

\ Mainboards - similar to modules

\ Kits 
   \ DistributorName - This is the maintainer/releaser of the code in this subdirectory
      \ KitName
         \ Software - Created using Kit Template (found in GadgeteerBuilderTemplates installer)

Reference Notes/Lists

.NET Gadgeteer Socket Types
DaisyLink Manufacturer Codes
HOWTO: Get the directory structure right with new modules
Gadgeteer PCB Graphic in .ai format

Open Source License

New Comment on "Socket Type K"

nvillar — Thu, 01 Mar 2012 23:46:59 GMT

Well spotted, and thanks for pointing this out. The text has been corrected.

Updated Wiki: Socket Type K

nvillar — Thu, 01 Mar 2012 23:46:23 GMT

Socket Type K

A UART serial line interface operating at TTL levels, with hardware flow control capabilities. Pin 4 (TX) is data from the mainboard to the module, and pin 5 (RX) is data from the module to the mainboard. These lines are idle high (3.3V), and can double as general-purpose input/outputs. Pin 6 (RTS) is an output from the mainboard to the module, indicating that the module may send data. Pin 7 (CTS) is an output from the module to the mainboard indicating that the mainboard may send data. The RTS/CTS are 'not ready' if high (3.3V) and 'ready' if low (0V). In addition, pins 3 is a general-purpose input/output, supporting interrupt capabilities.

Pinout

Pin 1	Pin 2	Pin 3	Pin 4	Pin 5	Pin 6	Pin 7	Pin 8	Pin 9	Pin 10
+3.3V	+5V	GPIO!	TX (G)	RX (G)	RTS	CTS	[UN]	[UN]	GND

Legend:

GPIO	A general-purpose digital input/output pin, operating at 3.3 Volts.
!	Interrupt-capable and software pull-up capable GPIO (the pull-up is switchable and in the range of 10,000 to 100,000 ohms).
[UN]	Modules must not connect to this pin if using this socket type. Mainboards can support multiple socket types on one socket, as long as individual pin functionalities overlap in a compatible manner, so that a pin from one socket type can overlap with a [UN] pin of another.
+3.3V	Connection to the +3.3V power net.
+5V	Connection to the +5V power net.
GND	Connection the power ground net.

Connector Pin Numbering

Pins numbers for the male 10-pin connector standard Gadgeteer socket, as seen from above. In most cases, the ribbon cables will have the pin 1 conductor marked in red.

Updated Wiki: .NET Gadgeteer Socket Types

nvillar — Thu, 01 Mar 2012 23:45:56 GMT

.NET Gadgeteer Socket Types

Socket types allow mainboards and modules to specify how they connect to one another, and are a key concept in .NET Gadgeteer.

Socket Types on a Mainboard

Every socket on a Gadgeteer mainboard is labelled with a number that uniquely identifies it. It is also labelled with one or more letters, and each letter corresponds to a different socket type.

Pin 1	Pin 2	Pin 3	Pin 4	Pin 5	Pin 6	Pin 7	Pin 8	Pin 9	Pin 10
+3.3V	+5V	AIN (G!)	AIN (G)	AIN	GPIO	[UN]	[UN]	[UN]	GND

Pinout specified by the socket type A definition.

Pin 1

Pin 2

Pin 3

Pin 4

Pin 5

Pin 6

Pin 7

Pin 8

Pin 9

Pin 10

+3.3V

+5V

AIN (G!)

GPIO!

AIN (G)

GPIO

AIN

GPIO

SDA

SCL

GND

Pinout for a single mainboard socket that supports types A, I, T and X.

Socket Types on a Module

List of Current Socket Types

This list may grow over time. For pinout details, click on the socket type letter on the list below.

A	Three analog inputs, with pins number 3 and 4 doubling as general-purpose input/output. In addition, pin number 6 is a general-purpose input/output, and pin number 3 supports interrupt capabilities.
B	Display (LCD) interface, carrying the blue component on pins 3 to 7, as well as the LCD enable line on pin 8 and the clock signal on pin 9.
C	Controller-area network (CAN, or CAN-Bus). Pins number 4 and 5 serve as the CAN transmit (TD) and receive (RD) pins, and double as general-purpose input/outputs. In addition, pins number 3 and 6 are general-purpose input/outputs, and pin number 3 supports interrupt capabilities.
D	A USB device interface for the mainboard to connect to a PC, usually for programming. Pins 4 and 5 are used as the dedicated USB data pins (D- and D+). In addition, pins 3, 6 and 7 are general-purpose input/outputs, with pin 3 supporting interrupt capabilities.
E	Ethernet PHY connection. Pins 6 to 9 are the dedicated transmit/receive lines to an Ethernet connector with integrated magnetics. Pins 4 and 5 are optional connections to the LEDs on the Ethernet connector.
F	Secure Digital Card (SD) or MMC (Multi Media Card) interface. Pins 4 to 9 are the dedicated data and control lines for this interface. In addition, pin 3 is a general-purpose digital input/output with interrupt capabilities.
G	Display (LCD) interface, carrying the green component on pins 3 to 8, as well as the backlight control line on pin 9.
H	USB host interface to connect USB peripherals to the mainboard. Pins 4 and 5 are used as the dedicated USB data pins (D- and D+). In addition, pins 3 is a general-purpose input/output with interrupt capabilities.
I	I2C interface. Pins 8 and 9 are the dedicated I2C data (SDA) and clock (SCL) lines. Note that a mainboard should include pull-up resistors for these pins, in the region of 2.2K Ohms. Modules must not include their own pull-ups on these lines. In addition, pins 3 and 6 are general-purpose input/outputs, with pin 3 supporting interrupt capabilities.
K	UART (serial line) interface operating at TTL levels, with hardware flow control capabilities. Pin 4 (TX) is data from the mainboard to the module, and pin 5 (RX) is data from the module to the mainboard. These lines are idle high (3.3V), and can double as general-purpose input/outputs. Pin 6 (RTS) is an output from the mainboard to the module, indicating that the module may send data. Pin 7 (CTS) is an output from the module to the mainboard indicating that the mainboard may send data. The RTS/CTS are 'not ready' if high (3.3V) and 'ready' if low (0V). In addition, pins 3 is a general-purpose input/output, supporting interrupt capabilities.
O	Analog output on pin 5. In addition, pins 3 and 4 are general-purpose input/outputs, and pin 3 includes interrupt capabilities.
P	Three pulse-with modulated (PWM) outputs on pins 7, 8 and 9. Pins 7 and 9 double as GPIOs. In addition, pin 3 is an interrupt-capable GPIO, and pin 6 is a GPIO.
R	Display (LCD) interface, carrying the red component on pins 3 to 7, as well as the VSYNC line on pin 8 and the HSYNC line on pin 9.
S	Serial peripheral interface (SPI). Pin 6 is the chip-select (CS) line, pin 7 is the master-out/slave-in (MOSI) line, pin 8 is the master-in/slave-out (MISO) line, and pin 9 is the clock (SCK) line. In addition, pins 3, 4 and 5 are general-purpose input/outputs, with pin 3 supporting interrupt capabilities.
T	Four-wire touch screen interface.
U	UART (serial line) interface operating at TTL levels. Pin 4 (TX) is data from the mainboard to the module, and pin 5 (RX) is data from the module to the mainboard. These lines are idle high (3.3V), and can double as general-purpose input/outputs. In addition, pins 3 and 6 are general-purpose input/outputs, with pin 3 supporting interrupt capabilities.
X	Three general-purpose input/output (GPIO) pins, with pin number 3 supporting interrupt capabilities.
Y	Seven general-purpose input/output (GPIO) pins, with pin number 3 supporting interrupt capabilities.
Z	Manufacturer specific. The pinout for this socket will vary between mainboards. Please refer to the individual mainboard's documentation for details.
*(DaisyLink)	DaisyLink downstream interface. Pin 3 is used for the DaisyLink neighbour bus, pin 4 is used for I2C SDA, pin 5 is used for I2C SCL. Note that this socket type should not appear on a mainboard, only on DaisyLink modules. The [MS] pins on this socket type can optionally support reflashing the firmware on the module.

New Comment on "Socket Type U"

nvillar — Thu, 01 Mar 2012 23:40:55 GMT

Well-spotted! Fixed. Thanks for pointing this out.

Updated Wiki: Socket Type U

nvillar — Thu, 01 Mar 2012 23:40:22 GMT

Socket Type U

A UART serial line interface operating at TTL levels. Pin 4 (TX) is data from the mainboard to the module, and pin 5 (RX) is data from the module to the mainboard. These lines are idle high (3.3V), and can double as general-purpose input/outputs. In addition, pins 3 and 6 are general-purpose input/outputs, with pin 3 supporting interrupt capabilities.

Pinout

Pin 1	Pin 2	Pin 3	Pin 4	Pin 5	Pin 6	Pin 7	Pin 8	Pin 9	Pin 10
+3.3V	+5V	GPIO!	TX (G)	RX (G)	GPIO	[UN]	[UN]	[UN]	GND

Legend:

GPIO	A general-purpose digital input/output pin, operating at 3.3 Volts.
!	Interrupt-capable and software pull-up capable GPIO (the pull-up is switchable and in the range of 10,000 to 100,000 ohms).
[UN]	Modules must not connect to this pin if using this socket type. Mainboards can support multiple socket types on one socket, as long as individual pin functionalities overlap in a compatible manner, so that a pin from one socket type can overlap with a [UN] pin of another.
+3.3V	Connection to the +3.3V power net.
+5V	Connection to the +5V power net.
GND	Connection the power ground net.

Connector Pin Numbering

Pins numbers for the male 10-pin connector standard Gadgeteer socket, as seen from above. In most cases, the ribbon cables will have the pin 1 conductor marked in red.

Updated Wiki: .NET Gadgeteer Socket Types

nvillar — Thu, 01 Mar 2012 23:37:33 GMT

.NET Gadgeteer Socket Types

Socket types allow mainboards and modules to specify how they connect to one another, and are a key concept in .NET Gadgeteer.

Socket Types on a Mainboard

Every socket on a Gadgeteer mainboard is labelled with a number that uniquely identifies it. It is also labelled with one or more letters, and each letter corresponds to a different socket type.

Pin 1	Pin 2	Pin 3	Pin 4	Pin 5	Pin 6	Pin 7	Pin 8	Pin 9	Pin 10
+3.3V	+5V	AIN (G!)	AIN (G)	AIN	GPIO	[UN]	[UN]	[UN]	GND

Pinout specified by the socket type A definition.

Pin 1

Pin 2

Pin 3

Pin 4

Pin 5

Pin 6

Pin 7

Pin 8

Pin 9

Pin 10

+3.3V

+5V

AIN (G!)

GPIO!

AIN (G)

GPIO

AIN

GPIO

SDA

SCL

GND

Pinout for a single mainboard socket that supports types A, I, T and X.

Socket Types on a Module

List of Current Socket Types

This list may grow over time. For pinout details, click on the socket type letter on the list below.

A	Three analog inputs, with pins number 3 and 4 doubling as general-purpose input/output. In addition, pin number 6 is a general-purpose input/output, and pin number 3 supports interrupt capabilities.
B	Display (LCD) interface, carrying the blue component on pins 3 to 7, as well as the LCD enable line on pin 8 and the clock signal on pin 9.
C	Controller-area network (CAN, or CAN-Bus). Pins number 4 and 5 serve as the CAN transmit (TD) and receive (RD) pins, and double as general-purpose input/outputs. In addition, pins number 3 and 6 are general-purpose input/outputs, and pin number 3 supports interrupt capabilities.
D	A USB device interface for the mainboard to connect to a PC, usually for programming. Pins 4 and 5 are used as the dedicated USB data pins (D- and D+). In addition, pins 3, 6 and 7 are general-purpose input/outputs, with pin 3 supporting interrupt capabilities.
E	Ethernet PHY connection. Pins 6 to 9 are the dedicated transmit/receive lines to an Ethernet connector with integrated magnetics. Pins 4 and 5 are optional connections to the LEDs on the Ethernet connector.
F	Secure Digital Card (SD) or MMC (Multi Media Card) interface. Pins 4 to 9 are the dedicated data and control lines for this interface. In addition, pin 3 is a general-purpose digital input/output with interrupt capabilities.
G	Display (LCD) interface, carrying the green component on pins 3 to 8, as well as the backlight control line on pin 9.
H	USB host interface to connect USB peripherals to the mainboard. Pins 4 and 5 are used as the dedicated USB data pins (D- and D+). In addition, pins 3 is a general-purpose input/output with interrupt capabilities.
I	I2C interface. Pins 8 and 9 are the dedicated I2C data (SDA) and clock (SCL) lines. Note that a mainboard should include pull-up resistors for these pins, in the region of 2.2K Ohms. Modules must not include their own pull-ups on these lines. In addition, pins 3 and 6 are general-purpose input/outputs, with pin 3 supporting interrupt capabilities.
K	UART (serial line) interface operating at TTL levels, with hardware flow control capabilities. Pin 3 (TX) is data from the mainboard to the module, and pin 4 (RX) is data from the module to the mainboard. These lines are idle high (3.3V), and can double as general-purpose input/outputs. Pin 6 (RTS) is an output from the mainboard to the module, indicating that the module may send data. Pin 7 (CTS) is an output from the module to the mainboard indicating that the mainboard may send data. The RTS/CTS are 'not ready' if high (3.3V) and 'ready' if low (0V). In addition, pins 3 is a general-purpose input/output, supporting interrupt capabilities.
O	Analog output on pin 5. In addition, pins 3 and 4 are general-purpose input/outputs, and pin 3 includes interrupt capabilities.
P	Three pulse-with modulated (PWM) outputs on pins 7, 8 and 9. Pins 7 and 9 double as GPIOs. In addition, pin 3 is an interrupt-capable GPIO, and pin 6 is a GPIO.
R	Display (LCD) interface, carrying the red component on pins 3 to 7, as well as the VSYNC line on pin 8 and the HSYNC line on pin 9.
S	Serial peripheral interface (SPI). Pin 6 is the chip-select (CS) line, pin 7 is the master-out/slave-in (MOSI) line, pin 8 is the master-in/slave-out (MISO) line, and pin 9 is the clock (SCK) line. In addition, pins 3, 4 and 5 are general-purpose input/outputs, with pin 3 supporting interrupt capabilities.
T	Four-wire touch screen interface.
U	UART (serial line) interface operating at TTL levels. Pin 4 (TX) is data from the mainboard to the module, and pin 5 (RX) is data from the module to the mainboard. These lines are idle high (3.3V), and can double as general-purpose input/outputs. In addition, pins 3 and 6 are general-purpose input/outputs, with pin 3 supporting interrupt capabilities.
X	Three general-purpose input/output (GPIO) pins, with pin number 3 supporting interrupt capabilities.
Y	Seven general-purpose input/output (GPIO) pins, with pin number 3 supporting interrupt capabilities.
Z	Manufacturer specific. The pinout for this socket will vary between mainboards. Please refer to the individual mainboard's documentation for details.
*(DaisyLink)	DaisyLink downstream interface. Pin 3 is used for the DaisyLink neighbour bus, pin 4 is used for I2C SDA, pin 5 is used for I2C SCL. Note that this socket type should not appear on a mainboard, only on DaisyLink modules. The [MS] pins on this socket type can optionally support reflashing the firmware on the module.

New Comment on "Socket Type K"

kennyspade — Wed, 15 Feb 2012 01:32:26 GMT

The opening paragraph incorrectly lists Pin 3 as (TX) and Pin 4 as (RX). The table has the correct listing, with Pin 4 as (TX) and Pin 5 as (RX).

New Comment on "Socket Type U"

kennyspade — Wed, 15 Feb 2012 01:32:03 GMT

The opening paragraph incorrectly lists Pin 3 as (TX) and Pin 4 as (RX). The table has the correct listing, with Pin 4 as (TX) and Pin 5 as (RX).

Updated Wiki: DaisyLink Manufacturer Codes

kerryh — Tue, 31 Jan 2012 21:35:10 GMT

DaisyLink Manufacturer Codes