Talk:Wishlist/Sensorbox - Revision history

Thomasgruebler: /* AVR/PIC */

2009-01-03T10:12:49Z

‎AVR/PIC

Thomasgruebler: /* AVR/PIC */ new section

2009-01-03T10:10:41Z

‎AVR/PIC: new section

Glenn: /* User:Hns */ To Rene

2008-11-03T17:41:43Z

‎User:Hns: To Rene

Relei at 10:26, 3 November 2008

2008-11-03T10:26:42Z

Glenn: /* User:Hns */

2008-11-02T15:53:14Z

‎User:Hns

Glenn: /* User:Hns */ +signature

2008-11-02T15:45:10Z

‎User:Hns: +signature

Glenn: Universal (PIC, ARM) USB driver information

2008-11-02T15:44:39Z

Universal (PIC, ARM) USB driver information

Glenn: /* User:Hns */ -some

2008-11-02T15:23:13Z

‎User:Hns: -some

Glenn: /* User:Hns */ -some

2008-11-02T15:22:01Z

‎User:Hns: -some

Glenn: /* User:Hns */

2008-11-02T15:21:01Z

‎User:Hns

@@ Line 81: / Line 81: @@
 Every AVR has an integrated I²C, SPI and UART (Serial) Interface. You can connect 8 analog sensors, you have some Hardware Interrupts, Timers, PWM-Outputs,...
-http://www.roboternetz.de/wissen/index.php/AVR
+http://www.roboternetz.de/wissen/index.php/AVR <br>
 http://www.roboternetz.de/wissen/index.php/USB#USB_Interface-Bausteine_.28ICs.29

← Older revision		Revision as of 10:10, 3 January 2009
Line 71:		Line 71:

	:Hi Rene - That is fine solution using a ftdi usb<->seriel chip. I use it myself. --[[User:Glenn\|Glenn]] 17:41, 3 November 2008 (UTC)		:Hi Rene - That is fine solution using a ftdi usb<->seriel chip. I use it myself. --[[User:Glenn\|Glenn]] 17:41, 3 November 2008 (UTC)
		+
		+	== AVR/PIC ==
		+
		+	I recommend an AVR or PIC.
		+	Since they have no USB Interface, they are both very cheap and are easy to use.
		+	For programming an AVR all needed tools are in the most distros repositorys (gcc-avr, binutils-avr, avrlibc, avrdude).
		+	As USB interface, i recommend using an FTDI USB/Serial changer. They work very fine also with 1MBit Baud.
		+
		+	Every AVR has an integrated I²C, SPI and UART (Serial) Interface. You can connect 8 analog sensors, you have some Hardware Interrupts, Timers, PWM-Outputs,...
		+
		+	http://www.roboternetz.de/wissen/index.php/AVR
		+	http://www.roboternetz.de/wissen/index.php/USB#USB_Interface-Bausteine_.28ICs.29

← Older revision		Revision as of 17:41, 3 November 2008
Line 69:		Line 69:

	Rene		Rene
		+
		+	:Hi Rene - That is fine solution using a ftdi usb<->seriel chip. I use it myself. --[[User:Glenn\|Glenn]] 17:41, 3 November 2008 (UTC)

← Older revision		Revision as of 10:26, 3 November 2008
Line 59:		Line 59:
	*[http://wiki.sikken.nl/index.php?title=LPCUSB#USB_virtual_COM_port USB virtual COM port]		*[http://wiki.sikken.nl/index.php?title=LPCUSB#USB_virtual_COM_port USB virtual COM port]
	--[[User:Glenn\|Glenn]] 15:45, 2 November 2008 (UTC)		--[[User:Glenn\|Glenn]] 15:45, 2 November 2008 (UTC)
		+
		+	Hello,
		+
		+	I have found this:
		+
		+	http://www.ianstedman.co.uk/Projects/PIC_USB_Interface/pic_usb_interface.html
		+
		+	Greetings
		+
		+	Rene

@@ Line 46: / Line 46: @@
 More:
-*[http://www.iay.org.uk/blog/2003/07/my_very_first_u.html July 25, 2003 My Very First USB Peripheral] Quote: "...For example, I wanted to change the number of buttons and add a couple of LEDs. To do this, you need to build new HID report descriptors and there you run into problems with incomprehensible standards documentation and inconsistent operating systems implementations...One last item that fits in under "firmware" better than anywhere else is the issue of vendor IDs. Like PCI and other "plug and pray" bus systems, your device presents a vendor ID and a product ID so that the host operating system can locate appropriate drivers. Unlike those other systems, there is no "experimental" vendor ID or apparently any way to get a legitimate vendor ID other than paying the USB Implementers Forum a minimum of $1500 every couple of years...If you want a host application of your own talking to a collection of custom peripherals you've designed, though, things are much harder..."
+*PIC16C745: [http://www.iay.org.uk/blog/2003/07/my_very_first_u.html July 25, 2003 My Very First USB Peripheral] Quote: "...For example, I wanted to change the number of buttons and add a couple of LEDs. To do this, you need to build new HID report descriptors and there you run into problems with incomprehensible standards documentation and inconsistent operating systems implementations...One last item that fits in under "firmware" better than anywhere else is the issue of vendor IDs. Like PCI and other "plug and pray" bus systems, your device presents a vendor ID and a product ID so that the host operating system can locate appropriate drivers. Unlike those other systems, there is no "experimental" vendor ID or apparently any way to get a legitimate vendor ID other than paying the USB Implementers Forum a minimum of $1500 every couple of years...If you want a host application of your own talking to a collection of custom peripherals you've designed, though, things are much harder..."
 *[http://www.embedds.com/pic18f4550-usb-prototyping-board/ PIC18F4550 USB prototyping board]
 *[http://www.embedds.com/pic18f2550-development-board-with-usb-port/  PIC18F2550 development board with USB port]

← Older revision		Revision as of 15:45, 2 November 2008
Line 58:		Line 58:
	Universal (PIC, ARM) USB driver information:		Universal (PIC, ARM) USB driver information:
	*[http://wiki.sikken.nl/index.php?title=LPCUSB#USB_virtual_COM_port USB virtual COM port]		*[http://wiki.sikken.nl/index.php?title=LPCUSB#USB_virtual_COM_port USB virtual COM port]
		+	--[[User:Glenn\|Glenn]] 15:45, 2 November 2008 (UTC)

← Older revision		Revision as of 15:44, 2 November 2008
Line 53:		Line 53:

	--[[User:Glenn\|Glenn]] 14:23, 2 November 2008 (UTC)		--[[User:Glenn\|Glenn]] 14:23, 2 November 2008 (UTC)
		+
		+	----
		+
		+	Universal (PIC, ARM) USB driver information:
		+	*[http://wiki.sikken.nl/index.php?title=LPCUSB#USB_virtual_COM_port USB virtual COM port]

@@ Line 43: / Line 43: @@
 *[http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail?name=PIC18F2550-I/SP-ND pic18f2550 US$ 8.2]
 *[http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail?name=PIC18F4550-I/P-ND pic18f4550 US$ 8.5]
-But for almost the same or a little more, you get much more with ARM (e.g. LPC2144, LPC2148). PS: [http://www.standardics.nxp.com/products/lpc2000/lpc214x/ LPC214x] quote: "...The LPC214x series is the only ARM7® microcontroller family with full USB 2.0 compliance and USB.org certification..."
+But for almost the same or a little more, you get much more with ARM.
 More:

@@ Line 50: / Line 50: @@
 *[http://www.embedds.com/pic18f4550-usb-prototyping-board/ PIC18F4550 USB prototyping board]
 *[http://www.embedds.com/pic18f2550-development-board-with-usb-port/  PIC18F2550 development board with USB port]
-**[http://www.holger-klabunde.de/usb/18f2550.htm PIC18F2550 Experimentierboard] Quote: "...Es gibt bei Microchip mehrere Code-Beispiele wie man Programme für den PIC schreibt. Als HID (Human Interface Device), über eine spezielle DLL von Microchip oder als CDC-Device (Communication Device Class). Letzteres habe ich hier benutzt. CDC arbeitet über einen virtuellen COM-Port. Man schreibt seine Programme so als würde man eine serielle Schnittstelle ansprechen. Für CDC ist kein spezieller Treiber erforderlich..."
+**[http://www.holger-klabunde.de/usb/18f2550.htm PIC18F2550 Experimentierboard] Quote: "...Es gibt bei Microchip mehrere Code-Beispiele wie man Programme für den PIC schreibt. Als HID (Human Interface Device), über eine spezielle DLL von Microchip oder als CDC-Device (Communication Device Class). Letzteres habe ich hier benutzt. CDC arbeitet [=works] über einen virtuellen COM-Port. Man schreibt seine Programme so als würde man eine serielle Schnittstelle [=interface] ansprechen. Für CDC ist kein spezieller Treiber[=driver] erforderlich..."
 *[http://www.semifluid.com/?p=24 PIC18F2550 USB HID Oscilloscope] Quote: "...Using HID means that this oscilloscope does not require drivers (only the oscilloscope software)..."
 --[[User:Glenn|Glenn]] 14:23, 2 November 2008 (UTC)