USB Communication Board - Revision history

DavidMeyer: /* Micro-controller Side */

2012-10-01T18:52:05Z

Micro-controller Side

← Older revision		Revision as of 13:52, 1 October 2012
Line 39:		Line 39:
	=== SPI ===		=== SPI ===

			In development
	Not yet implemented

	=== I2C ===		=== I2C ===

			In development
	Not yet implemented

	== PC Side ==		== PC Side ==

DavidMeyer: /* Overview */

2012-09-09T16:49:43Z

Overview

← Older revision		Revision as of 11:49, 9 September 2012
Line 3:		Line 3:
	= Overview =		= Overview =

	The NU USB Communication Board is a universal communication board which serves as an interface between PCs and embedded systems. Using a PIC32MX250 chip, the board translates between USB HID communication and low-level microcontroller communication protocols, including RS232, I2C, and SPI. This board is useful in circumstances when fast, reliable communication is desired between a microcontroller and PC, but resources are not available on the microcontroller to run a full USB stack.		The NU USB Communication Board is a universal communication board which serves as an interface between PCs and embedded systems. Using a PIC32MX250 chip, the board translates between USB HID communication and low-level microcontroller communication protocols, including RS232, I2C, and SPI. This board is useful in circumstances when fast, reliable communication is desired between a microcontroller and PC, but resources are not available on the microcontroller to run a full USB stack. The schematic and images of the copper traces are shown below.

			{\|
	[[image:All-actuators-captions-small.jpg\|thumb\|300px\|Available Actuators\|right]]
			\|-
			\| [[image:USB_Board_Schematic.png\|thumb\|400px\|Board Schematic\|none]]
			\| [[image:USB_Board_Top.png\|thumb\|160px\|Top Copper\|none]]
			\| [[image:USB_Board_Bottom.png\|thumb\|160px\|Bottom Copper\|none]]
			\|}

			<br clear=all>

	= Using the USB Communication Board =		= Using the USB Communication Board =

DavidMeyer at 16:31, 9 September 2012

2012-09-09T16:31:24Z

← Older revision		Revision as of 11:31, 9 September 2012
Line 4:		Line 4:

	The NU USB Communication Board is a universal communication board which serves as an interface between PCs and embedded systems. Using a PIC32MX250 chip, the board translates between USB HID communication and low-level microcontroller communication protocols, including RS232, I2C, and SPI. This board is useful in circumstances when fast, reliable communication is desired between a microcontroller and PC, but resources are not available on the microcontroller to run a full USB stack.		The NU USB Communication Board is a universal communication board which serves as an interface between PCs and embedded systems. Using a PIC32MX250 chip, the board translates between USB HID communication and low-level microcontroller communication protocols, including RS232, I2C, and SPI. This board is useful in circumstances when fast, reliable communication is desired between a microcontroller and PC, but resources are not available on the microcontroller to run a full USB stack.

			[[image:All-actuators-captions-small.jpg\|thumb\|300px\|Available Actuators\|right]]

	= Using the USB Communication Board =		= Using the USB Communication Board =

DavidMeyer: /* Processing */

2012-09-07T20:11:31Z

Processing

← Older revision		Revision as of 15:11, 7 September 2012
Line 42:		Line 42:
	To send and receive USB packets in Processing on the computer, we use a Java Native Interface library which uses C libraries to communicate via USB. We have included the library in an example processing sketch for you, but if you're interested in using the Java library for something else, documentation and downloads for this library can be found [http://code.google.com/p/javahidapi/ here]. This is the template [[Media:USB_Processing_Template.zip\|Processing sketch]] which simply listens for characters and prints them out in the text pane, and sends them back to the device. The code directory contains the .jar file containing the Java library. These files need to be here, but do not require editing.		To send and receive USB packets in Processing on the computer, we use a Java Native Interface library which uses C libraries to communicate via USB. We have included the library in an example processing sketch for you, but if you're interested in using the Java library for something else, documentation and downloads for this library can be found [http://code.google.com/p/javahidapi/ here]. This is the template [[Media:USB_Processing_Template.zip\|Processing sketch]] which simply listens for characters and prints them out in the text pane, and sends them back to the device. The code directory contains the .jar file containing the Java library. These files need to be here, but do not require editing.

	In the sketch itself, the '''USBListener''' file defines a Thread which listens to the USB port. The function pic.read() will wait until the USB buffer is not empty, and then place the first-in data into the specified variable. This thread is also a good place to update all state variables and send out data to the PIC using pic.write(). The '''HIDManager''' file contains the code to connect and set up the . ~~This~~ ~~class~~ ~~defines~~ ~~callback~~ ~~functions~~ ~~which~~ ~~are~~ ~~called~~ ~~whenever~~ a ~~device~~ is ~~added~~ or ~~removed.~~		In the sketch itself, the '''USBListener''' file defines a Thread which listens to the USB port. The function pic.read() will wait until the USB buffer is not empty, and then place the first-in data into the specified variable. This thread is also a good place to update all state variables and send out data to the PIC using pic.write(). The '''HIDManager''' file contains the code to connect and set up the USB communication with the PIC device. The NU USB Communication Board has product ID: 0, so the proper function call to open the pic is openPic(0);

	Here is the API [[Media:Hidapi-1.1-javadoc.zip\|documentation]], which explains what each function does.		Here is the API [[Media:Hidapi-1.1-javadoc.zip\|documentation]], which explains what each function does.

DavidMeyer: /* Processing */

2012-09-07T20:10:41Z

Processing

← Older revision		Revision as of 15:10, 7 September 2012
Line 44:		Line 44:
	In the sketch itself, the '''USBListener''' file defines a Thread which listens to the USB port. The function pic.read() will wait until the USB buffer is not empty, and then place the first-in data into the specified variable. This thread is also a good place to update all state variables and send out data to the PIC using pic.write(). The '''HIDManager''' file contains the code to connect and set up the . This class defines callback functions which are called whenever a device is added or removed.		In the sketch itself, the '''USBListener''' file defines a Thread which listens to the USB port. The function pic.read() will wait until the USB buffer is not empty, and then place the first-in data into the specified variable. This thread is also a good place to update all state variables and send out data to the PIC using pic.write(). The '''HIDManager''' file contains the code to connect and set up the . This class defines callback functions which are called whenever a device is added or removed.

	Here is the API [[~~Nope~~\|documentation]], which explains what each function does.		Here is the API [[Media:Hidapi-1.1-javadoc.zip\|documentation]], which explains what each function does.

	=== Matlab ===		=== Matlab ===

DavidMeyer: /* Processing */

2012-09-07T20:03:39Z

Processing

← Older revision		Revision as of 15:03, 7 September 2012
Line 40:		Line 40:
	=== Processing ===		=== Processing ===

	To send and receive USB packets in Processing on the computer, we use a Java Native Interface library which uses C libraries to communicate via USB. We have included the library in an example processing sketch for you, but if you're interested in using the Java library for something else, documentation and downloads for this library can be found [http://code.google.com/p/javahidapi/ here]. This is the template [[~~Nope~~\|Processing sketch]] which simply listens for characters and prints them out in the text pane, and sends them back to the device. The code directory contains the .jar file containing the Java library. These files need to be here, but do not require editing.		To send and receive USB packets in Processing on the computer, we use a Java Native Interface library which uses C libraries to communicate via USB. We have included the library in an example processing sketch for you, but if you're interested in using the Java library for something else, documentation and downloads for this library can be found [http://code.google.com/p/javahidapi/ here]. This is the template [[Media:USB_Processing_Template.zip\|Processing sketch]] which simply listens for characters and prints them out in the text pane, and sends them back to the device. The code directory contains the .jar file containing the Java library. These files need to be here, but do not require editing.

	In the sketch itself, the '''USBListener''' file defines a Thread which listens to the USB port. The function pic.read() will wait until the USB buffer is not empty, and then place the first-in data into the specified variable. This thread is also a good place to update all state variables and send out data to the PIC using pic.write(). The '''HIDManager''' file contains the code to connect and set up the . This class defines callback functions which are called whenever a device is added or removed.		In the sketch itself, the '''USBListener''' file defines a Thread which listens to the USB port. The function pic.read() will wait until the USB buffer is not empty, and then place the first-in data into the specified variable. This thread is also a good place to update all state variables and send out data to the PIC using pic.write(). The '''HIDManager''' file contains the code to connect and set up the . This class defines callback functions which are called whenever a device is added or removed.

DavidMeyer: /* Processing */

2012-09-07T20:01:41Z

Processing

← Older revision		Revision as of 15:01, 7 September 2012
Line 40:		Line 40:
	=== Processing ===		=== Processing ===

	To send and receive USB packets in Processing on the computer, we use a Java Native Interface library which uses C libraries to communicate via USB. We have included the library in ~~the~~ processing sketch for you, but if you're interested in using the Java library for something else, documentation and downloads for this library can be found [http://code.google.com/p/javahidapi/ here]. This is the template [[Nope\|Processing sketch]] which simply listens for characters and prints them out in the text pane. ~~Any~~ ~~character~~ ~~that is typed into the box will be sent to over USB~~ to the ~~connected~~ device. The code directory contains the .jar file containing the Java library. These files need to be here, but do not require editing.		To send and receive USB packets in Processing on the computer, we use a Java Native Interface library which uses C libraries to communicate via USB. We have included the library in an example processing sketch for you, but if you're interested in using the Java library for something else, documentation and downloads for this library can be found [http://code.google.com/p/javahidapi/ here]. This is the template [[Nope\|Processing sketch]] which simply listens for characters and prints them out in the text pane, and sends them back to the device. The code directory contains the .jar file containing the Java library. These files need to be here, but do not require editing.

	In the sketch itself, the '''USBListener''' file defines a Thread which listens to the USB port. The function pic.read() will wait until the USB buffer is not empty, and then place the first-in data into the specified variable. This thread is also a good place to update all state variables and send out data to the PIC using pic.write(). The '''HIDManager''' file contains the code to connect and set up the . This class defines callback functions which are called whenever a device is added or removed.		In the sketch itself, the '''USBListener''' file defines a Thread which listens to the USB port. The function pic.read() will wait until the USB buffer is not empty, and then place the first-in data into the specified variable. This thread is also a good place to update all state variables and send out data to the PIC using pic.write(). The '''HIDManager''' file contains the code to connect and set up the . This class defines callback functions which are called whenever a device is added or removed.

DavidMeyer at 19:54, 7 September 2012

2012-09-07T19:54:32Z

← Older revision		Revision as of 14:54, 7 September 2012
Line 1:		Line 1:
	''' *Under Construction* '''		''' *Under Construction* '''

	== Overview ==		= Overview =

	The NU USB Communication Board is a universal communication board which serves as an interface between PCs and embedded systems. Using a PIC32MX250 chip, the board translates between USB HID communication and low-level microcontroller communication protocols, including RS232, I2C, and SPI. This board is useful in circumstances when fast, reliable communication is desired between a microcontroller and PC, but resources are not available on the microcontroller to run a full USB stack.		The NU USB Communication Board is a universal communication board which serves as an interface between PCs and embedded systems. Using a PIC32MX250 chip, the board translates between USB HID communication and low-level microcontroller communication protocols, including RS232, I2C, and SPI. This board is useful in circumstances when fast, reliable communication is desired between a microcontroller and PC, but resources are not available on the microcontroller to run a full USB stack.

	== Using the USB Communication Board ==		= Using the USB Communication Board =

			The USB protocol used on this board operates in the HID class. This is beneficial because no drivers are required for any operating system, and low latency is guaranteed. The USB in operation on this board delivers 64 byte packets every millisecond in both directions. For this reason, all streaming data coming from the embedded side will be "packetized" by the board into 63 byte packets, using the first byte as a descriptor.

			== Micro-controller Side ==

	The board operates in one of four modes: RS232, RS232 with Hardware Flow Control, SPI, or I2C. This mode is selected upon board power-up by the CommSelect jumpers on board. The selection criteria are shown below		The board operates in one of four modes: RS232, RS232 with Hardware Flow Control, SPI, or I2C. This mode is selected upon board power-up by the CommSelect jumpers on board. The selection criteria are shown below
Line 31:		Line 35:

	Not yet implemented		Not yet implemented

			== PC Side ==

			=== Processing ===

			To send and receive USB packets in Processing on the computer, we use a Java Native Interface library which uses C libraries to communicate via USB. We have included the library in the processing sketch for you, but if you're interested in using the Java library for something else, documentation and downloads for this library can be found [http://code.google.com/p/javahidapi/ here]. This is the template [[Nope\|Processing sketch]] which simply listens for characters and prints them out in the text pane. Any character that is typed into the box will be sent to over USB to the connected device. The code directory contains the .jar file containing the Java library. These files need to be here, but do not require editing.

			In the sketch itself, the '''USBListener''' file defines a Thread which listens to the USB port. The function pic.read() will wait until the USB buffer is not empty, and then place the first-in data into the specified variable. This thread is also a good place to update all state variables and send out data to the PIC using pic.write(). The '''HIDManager''' file contains the code to connect and set up the . This class defines callback functions which are called whenever a device is added or removed.

			Here is the API [[Nope\|documentation]], which explains what each function does.

			=== Matlab ===

			In development

	== Source Code ==		== Source Code ==

DavidMeyer: /* Source Code */

2012-09-04T22:55:03Z

Source Code

← Older revision		Revision as of 17:55, 4 September 2012
Line 34:		Line 34:
	== Source Code ==		== Source Code ==

			9/4/2012 - [[Media:USB_COMM.X.zip\|Source Project]]
	9/4/2012 -

DavidMeyer at 22:45, 4 September 2012

2012-09-04T22:45:25Z

@@ Line 3: / Line 3: @@
 == Overview ==
-The NU USB Communication Board is a universal communication board which serves as an interface between PCs and embedded systems.  The board translates between USB HID communication and low-level microcontroller communication protocols, including RS232, I2C, and SPI.  This board is useful in circumstances when fast, reliable communication is desired between a microcontroller and PC, but resources are not available on the microcontroller to run a full USB stack.
+The NU USB Communication Board is a universal communication board which serves as an interface between PCs and embedded systems.  Using a PIC32MX250 chip, the board translates between USB HID communication and low-level microcontroller communication protocols, including RS232, I2C, and SPI.  This board is useful in circumstances when fast, reliable communication is desired between a microcontroller and PC, but resources are not available on the microcontroller to run a full USB stack.
 == Using the USB Communication Board ==
@@ Line 16: / Line 16: @@
 === RS232 ===
 == Source Code ==