From: Ash C. <as...@gu...> - 2010-05-18 19:43:52
|
Hi All, I've been working on a robostix-equivalent board for Overo and was hoping to get suggestions on what this board should look like. There have been some very interesting post related to such a board in the last week so having feedback would be fantastic. *** Desired Features*** - I2C bus - CAN bus (notably missing from all our boards) - at least 6 PWM lines ( makes servo control easy, steppers are nice too) - at least 20 GPIOs ('cause people like to do lots of crazy things with GPIOs; these should be 5V tolerant) - SPI bus breakout - at least 2xUARTs - battery powerable (charging & battery monitoring circuit would be nice but haven't spec'ed it) - a few on-board leds and switches ('cause this makes debugging so much easier) - a USB host interface (from Overo; 'cause this gives easy extensibility) - a usb console port ( from Overo) - an ADC (there is already an ADC on the Overo but it is useful to have access to analog data on real-time chip) - accel, gyro, and/or digital compass (these parts enable lots of cool project but are a pain to put on your own daughter board) - a microcontroller (>20MHz, >32kB flash, >32kB ram) - interface to the Overo on SPI0 An interesting option exists: 1) Get rid of the FTDI chip; use the CDC device class on the microcontroller to provide from-boot console access to the overo. This means a UART connection from microcontroller->Overo. Does this require reflashing the boot rom for the microcontroller? 2) Put a USB Hub controller (like http://www2.renesas.com/usb/en/product/upd720114.html) on board with the Overo as the host and the microcontroller as one of the USB devices. Provide the other three (powered) USB ports for direct keyboard, mouse, memory etc. 3) If using the board standalone, then use the microcontroller as the USB host. OVERO<----uart---->MICRO<---usb--->USB jack \----usb host--->USB Hub Chip---usb client--->MICRO \-------> 3x powered usb ports Proposed Overo Interface board: 1xLM3S2793 (http://www.luminarymicro.com/products/lm3s2793.html): - 3.3V chip (pins are 5V tolerant and can drive 5V TTL...anyone need 5V CMOS?) - 80MHz - 128kB Flash (some probably used for pre-flashed drivers & bootloader) - 64kB RAM - 8 x PWM (expose all) - 2 x quad encoders (expose all) - 2 x CAN (expose one of these) - 2 x I2C (we'll use one bus on board for the gyros, accels, battery monitoring) - 2 x SPI (use one to connect to overo) - 3 x UARTS (expose all) - 1 x I2S (does anyone use this?) - 16ch 10-bit ADC (more bits is nice but is this really actually useful?) - up-to 60 GPIOs ( expose as many as possible ) 1xTPS62111 (or similar 3.3V LDO) 1xFT232RQ (or similar USB-Serial interface chip; same interface to Overo as other boards) 4xLEDs (1 for power; 3 bits gives 8 debugging states) 3xpushbuttons|switches ( 1xpower, 2x controls) 1xLSM303DLH (http://www.st.com/stonline/products/literature/ds/16941.pdf) **connectors** 1x 5V power jack 1x 5V battery hookup (support 3A on PWM traces) 1x full-size USB A connector (USB host) 1x mini-USB (console port) 2x 70 connectors for Overo 1x 3 by 20 pin breakout (first 3 by 8 are PWM, 5V and Unfiltered GND for standard servos, 6 pins for 3.3V and filtered Gnd, 3x2pins for 3 UARTS, 2pins I2C, 16 pins for ADC, 2 pins for CAN...what do people actually need here?, 2 pins for encoders) Okay---that's a lot to digest. Any feedback and suggestions are welcome. -Ash |
From: Victhor <vic...@gm...> - 2010-05-18 20:17:20
|
I know this is self-promotion... but... I made a board that takes a LiPo/Li-ion battery and provides battery charging via USB and AC adapter, as well as battery charge information via I2C. It has some issues, namely: 1. Board is EAGLE autorouted, and was optimized as much as possible to make it fit in a single layer; 2. Has through-hole components; 3. Has an unnecessary jumper onboard for USB charge current selection(before I learnt how easy it was to control GPIOs :) ); 4. Has "power good" LED pins, one for each external power source. While there is no footprint for the LEDs as my wish was to install them off the battery board(and only if I wished to use the LEDs); 5. Has never been built/tested/evaluated. The board in question was posted here a while ago(http://www.box.net/shared/udlps3ux26 ), I wanted some opinions on the design as well, as many people have downloaded it(Box.net alerts me when someone downloads shared files). It uses two Texas Instrument ICs, the BQ27200 for battery monitoring(there is a driver for it with the Linux kernel, I made sure that it was available before I included it into the board, so far I checked 2.6.32 and 2.6.33 and it's there on both), and the BQ24032A for battery charging. The board has all features of both chips made available as scattered pins around the board. > Hi All, > > I've been working on a robostix-equivalent board for Overo and was > hoping to get suggestions on what this board should look like. There > have been some very interesting post related to such a board in the > last week so having feedback would be fantastic. > > *** Desired Features*** > - I2C bus > - CAN bus (notably missing from all our boards) > - at least 6 PWM lines ( makes servo control easy, steppers are nice too) > - at least 20 GPIOs ('cause people like to do lots of crazy things > with GPIOs; these should be 5V tolerant) > - SPI bus breakout > - at least 2xUARTs > - battery powerable (charging & battery monitoring circuit would be > nice but haven't spec'ed it) > - a few on-board leds and switches ('cause this makes debugging so much easier) > - a USB host interface (from Overo; 'cause this gives easy extensibility) > - a usb console port ( from Overo) > - an ADC (there is already an ADC on the Overo but it is useful to > have access to analog data on real-time chip) > - accel, gyro, and/or digital compass (these parts enable lots of > cool project but are a pain to put on your own daughter board) > - a microcontroller (>20MHz, >32kB flash, >32kB ram) > - interface to the Overo on SPI0 > > An interesting option exists: > 1) Get rid of the FTDI chip; use the CDC device class on the > microcontroller to provide from-boot console access to the overo. This > means a UART connection from microcontroller->Overo. Does this > require reflashing the boot rom for the microcontroller? > 2) Put a USB Hub controller (like > http://www2.renesas.com/usb/en/product/upd720114.html) on board with > the Overo as the host and the microcontroller as one of the USB > devices. Provide the other three (powered) USB ports for direct > keyboard, mouse, memory etc. > 3) If using the board standalone, then use the microcontroller as the USB host. > > OVERO<----uart---->MICRO<---usb--->USB jack > \----usb host--->USB Hub Chip---usb client--->MICRO > \-------> > 3x powered usb ports > > Proposed Overo Interface board: > 1xLM3S2793 (http://www.luminarymicro.com/products/lm3s2793.html): > - 3.3V chip (pins are 5V tolerant and can drive 5V TTL...anyone > need 5V CMOS?) > - 80MHz > - 128kB Flash (some probably used for pre-flashed drivers & bootloader) > - 64kB RAM > - 8 x PWM (expose all) > - 2 x quad encoders (expose all) > - 2 x CAN (expose one of these) > - 2 x I2C (we'll use one bus on board for the gyros, accels, > battery monitoring) > - 2 x SPI (use one to connect to overo) > - 3 x UARTS (expose all) > - 1 x I2S (does anyone use this?) > - 16ch 10-bit ADC (more bits is nice but is this really actually useful?) > - up-to 60 GPIOs ( expose as many as possible ) > 1xTPS62111 (or similar 3.3V LDO) > 1xFT232RQ (or similar USB-Serial interface chip; same interface to > Overo as other boards) > 4xLEDs (1 for power; 3 bits gives 8 debugging states) > 3xpushbuttons|switches ( 1xpower, 2x controls) > 1xLSM303DLH (http://www.st.com/stonline/products/literature/ds/16941.pdf) > > **connectors** > 1x 5V power jack > 1x 5V battery hookup (support 3A on PWM traces) > 1x full-size USB A connector (USB host) > 1x mini-USB (console port) > 2x 70 connectors for Overo > 1x 3 by 20 pin breakout (first 3 by 8 are PWM, 5V and Unfiltered GND > for standard servos, 6 pins for 3.3V and filtered Gnd, 3x2pins for 3 > UARTS, 2pins I2C, 16 pins for ADC, 2 pins for CAN...what do people > actually need here?, 2 pins for encoders) > > Okay---that's a lot to digest. Any feedback and suggestions are welcome. > > -Ash > > ------------------------------------------------------------------------------ > > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Dave H. <dhy...@gm...> - 2010-05-18 21:24:29
|
Hi Ash, On Tue, May 18, 2010 at 12:43 PM, Ash Charles <as...@gu...> wrote: > Hi All, > > I've been working on a robostix-equivalent board for Overo and was > hoping to get suggestions on what this board should look like. There > have been some very interesting post related to such a board in the > last week so having feedback would be fantastic. ...snip... > Proposed Overo Interface board: > 1xLM3S2793 (http://www.luminarymicro.com/products/lm3s2793.html): > - 3.3V chip (pins are 5V tolerant and can drive 5V TTL...anyone > need 5V CMOS?) Looks pretty nice. I've played with some of the other luminary micro chips, and I quite like the feature set. If you can drive 5v TTL you can drive 5v CMOS. For the busses that are going to connect to the overo, I'd recommend using jumpers (or some of those tiny little switches) so that they can be disconnected. > *** Desired Features*** > - I2C bus > - CAN bus (notably missing from all our boards) > - at least 6 PWM lines ( makes servo control easy, steppers are nice too) > - at least 20 GPIOs ('cause people like to do lots of crazy things > with GPIOs; these should be 5V tolerant) > - SPI bus breakout > - at least 2xUARTs > - battery powerable (charging & battery monitoring circuit would be > nice but haven't spec'ed it) > - a few on-board leds and switches ('cause this makes debugging so much easier) > - a USB host interface (from Overo; 'cause this gives easy extensibility) > - a usb console port ( from Overo) > - an ADC (there is already an ADC on the Overo but it is useful to > have access to analog data on real-time chip) > - accel, gyro, and/or digital compass (these parts enable lots of > cool project but are a pain to put on your own daughter board) I just picked up one of these: <http://www.sparkfun.com/commerce/product_info.php?products_id=9623> to play with, which has your 3-axis gyro, 3-axiss accelerometer, and 3-axis magnetometer. > - a microcontroller (>20MHz, >32kB flash, >32kB ram) > - interface to the Overo on SPI0 > > An interesting option exists: > 1) Get rid of the FTDI chip; use the CDC device class on the > microcontroller to provide from-boot console access to the overo. This > means a UART connection from microcontroller->Overo. Does this > require reflashing the boot rom for the microcontroller? I probably wouldn't get rid of the FTDI unless you're really crammed for space. It seems like quite an imposition to ensure that the microcontroller be running the USB stuff properly in order to use the console on the gumstix. This makes things really tough when you're developing code for the microcontroller. > 2) Put a USB Hub controller (like > http://www2.renesas.com/usb/en/product/upd720114.html) on board with > the Overo as the host and the microcontroller as one of the USB > devices. Provide the other three (powered) USB ports for direct > keyboard, mouse, memory etc. I think that would a wonderful idea. > 3) If using the board standalone, then use the microcontroller as the USB host. > > OVERO<----uart---->MICRO<---usb--->USB jack > \----usb host--->USB Hub Chip---usb client--->MICRO > \-------> > 3x powered usb ports > > - 80MHz > - 128kB Flash (some probably used for pre-flashed drivers & bootloader) > - 64kB RAM > - 8 x PWM (expose all) > - 2 x quad encoders (expose all) > - 2 x CAN (expose one of these) > - 2 x I2C (we'll use one bus on board for the gyros, accels, > battery monitoring) > - 2 x SPI (use one to connect to overo) > - 3 x UARTS (expose all) > - 1 x I2S (does anyone use this?) > - 16ch 10-bit ADC (more bits is nice but is this really actually useful?) > - up-to 60 GPIOs ( expose as many as possible ) > 1xTPS62111 (or similar 3.3V LDO) > 1xFT232RQ (or similar USB-Serial interface chip; same interface to > Overo as other boards) > 4xLEDs (1 for power; 3 bits gives 8 debugging states) > 3xpushbuttons|switches ( 1xpower, 2x controls) > 1xLSM303DLH (http://www.st.com/stonline/products/literature/ds/16941.pdf) > > **connectors** > 1x 5V power jack > 1x 5V battery hookup (support 3A on PWM traces) I'm assuming that you're putting a set of 3-pin headers for connecting up servos? In which case, I would probably want to allow the servo voltage to go upto around 9v - yeah most servos are only rated up to 6v, but lots of people overvoltage them. This was accomodated on the robostix by having a removable jumper. If you're going to allow all 8 servos to be connected, then I would allow at least 0.5A per servo, so 4A for the power and ground traces. The PWM traces don't need to be high current. > 1x full-size USB A connector (USB host) > 1x mini-USB (console port) > 2x 70 connectors for Overo > 1x 3 by 20 pin breakout (first 3 by 8 are PWM, 5V and Unfiltered GND > for standard servos, 6 pins for 3.3V and filtered Gnd, 3x2pins for 3 > UARTS, 2pins I2C, 16 pins for ADC, 2 pins for CAN...what do people > actually need here?, 2 pins for encoders) Encoders typically need power ground, and A/B signals (per encoder). I2C needs a ground. I know on the robostix it was really nice to have power/ground/signal for each ADC since it allowed your sensors to be interchangable. -- Dave Hylands Shuswap, BC, Canada http://www.DaveHylands.com/ |
From: Alex G. <al...@al...> - 2010-05-19 01:47:55
|
Make it completely 5V tolerant ? Or have configurable level shifters 3.3/5V via switch spi/i2c/can would be great. Make it so it can take screw terminals as well as usual pin headers. (e.g like this board http://www.bdmicro.com/include/display_image.php?img=/mavric-iib/mav2b_t1_vsm.jpg ) Makes it very easy when protoyping. rtc with battery back up. polarity protection/diodes on the power and battery connectors to prevent those doh moments when tired/in a rush. 3 pins for encoders (x,y and z) but probably not need by most people. Is there a need for the accelerometer and gyros on board ? The breakout boards from sparkfun are pretty handy and easy to use. Or have them removable via a jumper or few. http://www.sparkfun.com/commerce/product_info.php?products_id=9801 gyro accelerometers http://www.sparkfun.com/commerce/categories.php?c=163 http://www.sparkfun.com/commerce/product_info.php?products_id=9652 http://www.sparkfun.com/commerce/product_info.php?products_id=8791 Alex On 19/05/2010 5:43 AM, Ash Charles wrote: > Hi All, > > I've been working on a robostix-equivalent board for Overo and was > hoping to get suggestions on what this board should look like. There > have been some very interesting post related to such a board in the > last week so having feedback would be fantastic. > > *** Desired Features*** > - I2C bus > - CAN bus (notably missing from all our boards) > - at least 6 PWM lines ( makes servo control easy, steppers are nice too) > - at least 20 GPIOs ('cause people like to do lots of crazy things > with GPIOs; these should be 5V tolerant) > - SPI bus breakout > - at least 2xUARTs > - battery powerable (charging& battery monitoring circuit would be > nice but haven't spec'ed it) > - a few on-board leds and switches ('cause this makes debugging so much easier) > - a USB host interface (from Overo; 'cause this gives easy extensibility) > - a usb console port ( from Overo) > - an ADC (there is already an ADC on the Overo but it is useful to > have access to analog data on real-time chip) > - accel, gyro, and/or digital compass (these parts enable lots of > cool project but are a pain to put on your own daughter board) > - a microcontroller (>20MHz,>32kB flash,>32kB ram) > - interface to the Overo on SPI0 > > An interesting option exists: > 1) Get rid of the FTDI chip; use the CDC device class on the > microcontroller to provide from-boot console access to the overo. This > means a UART connection from microcontroller->Overo. Does this > require reflashing the boot rom for the microcontroller? > 2) Put a USB Hub controller (like > http://www2.renesas.com/usb/en/product/upd720114.html) on board with > the Overo as the host and the microcontroller as one of the USB > devices. Provide the other three (powered) USB ports for direct > keyboard, mouse, memory etc. > 3) If using the board standalone, then use the microcontroller as the USB host. > > OVERO<----uart---->MICRO<---usb--->USB jack > \----usb host--->USB Hub Chip---usb client--->MICRO > \-------> > 3x powered usb ports > > Proposed Overo Interface board: > 1xLM3S2793 (http://www.luminarymicro.com/products/lm3s2793.html): > - 3.3V chip (pins are 5V tolerant and can drive 5V TTL...anyone > need 5V CMOS?) > - 80MHz > - 128kB Flash (some probably used for pre-flashed drivers& bootloader) > - 64kB RAM > - 8 x PWM (expose all) > - 2 x quad encoders (expose all) > - 2 x CAN (expose one of these) > - 2 x I2C (we'll use one bus on board for the gyros, accels, > battery monitoring) > - 2 x SPI (use one to connect to overo) > - 3 x UARTS (expose all) > - 1 x I2S (does anyone use this?) > - 16ch 10-bit ADC (more bits is nice but is this really actually useful?) > - up-to 60 GPIOs ( expose as many as possible ) > 1xTPS62111 (or similar 3.3V LDO) > 1xFT232RQ (or similar USB-Serial interface chip; same interface to > Overo as other boards) > 4xLEDs (1 for power; 3 bits gives 8 debugging states) > 3xpushbuttons|switches ( 1xpower, 2x controls) > 1xLSM303DLH (http://www.st.com/stonline/products/literature/ds/16941.pdf) > > **connectors** > 1x 5V power jack > 1x 5V battery hookup (support 3A on PWM traces) > 1x full-size USB A connector (USB host) > 1x mini-USB (console port) > 2x 70 connectors for Overo > 1x 3 by 20 pin breakout (first 3 by 8 are PWM, 5V and Unfiltered GND > for standard servos, 6 pins for 3.3V and filtered Gnd, 3x2pins for 3 > UARTS, 2pins I2C, 16 pins for ADC, 2 pins for CAN...what do people > actually need here?, 2 pins for encoders) > > Okay---that's a lot to digest. Any feedback and suggestions are welcome. > > -Ash > > ------------------------------------------------------------------------------ > > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > -- UTS CRICOS Provider Code: 00099F DISCLAIMER: This email message and any accompanying attachments may contain confidential information. If you are not the intended recipient, do not read, use, disseminate, distribute or copy this message or attachments. If you have received this message in error, please notify the sender immediately and delete this message. Any views expressed in this message are those of the individual sender, except where the sender expressly, and with authority, states them to be the views the University of Technology, Sydney. Before opening any attachments, please check them for viruses and defects. |
From: Ryan M. <ke...@gm...> - 2010-05-19 03:21:40
|
I'm not sure it's worth having on-board sensors either - people will probably have different needs (accuracy, response time, type of sensing). Seems to make more sense to provide the I/O and leave the sensing hardware to the user. -Ryan On Tue, May 18, 2010 at 8:47 PM, Alex Gibson <al...@al...> wrote: > Make it completely 5V tolerant ? > Or have configurable level shifters 3.3/5V via switch > > spi/i2c/can would be great. > > Make it so it can take screw terminals as well as usual pin headers. > (e.g like this board > > http://www.bdmicro.com/include/display_image.php?img=/mavric-iib/mav2b_t1_vsm.jpg > ) > Makes it very easy when protoyping. > > rtc with battery back up. > > polarity protection/diodes on the power and battery connectors to > prevent those doh moments > when tired/in a rush. > > 3 pins for encoders (x,y and z) but probably not need by most people. > > Is there a need for the accelerometer and gyros on board ? > The breakout boards from sparkfun are pretty handy and easy to use. > Or have them removable via a jumper or few. > > http://www.sparkfun.com/commerce/product_info.php?products_id=9801 gyro > > accelerometers > http://www.sparkfun.com/commerce/categories.php?c=163 > http://www.sparkfun.com/commerce/product_info.php?products_id=9652 > http://www.sparkfun.com/commerce/product_info.php?products_id=8791 > > > > > > Alex > > On 19/05/2010 5:43 AM, Ash Charles wrote: > > Hi All, > > > > I've been working on a robostix-equivalent board for Overo and was > > hoping to get suggestions on what this board should look like. There > > have been some very interesting post related to such a board in the > > last week so having feedback would be fantastic. > > > > *** Desired Features*** > > - I2C bus > > - CAN bus (notably missing from all our boards) > > - at least 6 PWM lines ( makes servo control easy, steppers are nice too) > > - at least 20 GPIOs ('cause people like to do lots of crazy things > > with GPIOs; these should be 5V tolerant) > > - SPI bus breakout > > - at least 2xUARTs > > - battery powerable (charging& battery monitoring circuit would be > > nice but haven't spec'ed it) > > - a few on-board leds and switches ('cause this makes debugging so much > easier) > > - a USB host interface (from Overo; 'cause this gives easy extensibility) > > - a usb console port ( from Overo) > > - an ADC (there is already an ADC on the Overo but it is useful to > > have access to analog data on real-time chip) > > - accel, gyro, and/or digital compass (these parts enable lots of > > cool project but are a pain to put on your own daughter board) > > - a microcontroller (>20MHz,>32kB flash,>32kB ram) > > - interface to the Overo on SPI0 > > > > An interesting option exists: > > 1) Get rid of the FTDI chip; use the CDC device class on the > > microcontroller to provide from-boot console access to the overo. This > > means a UART connection from microcontroller->Overo. Does this > > require reflashing the boot rom for the microcontroller? > > 2) Put a USB Hub controller (like > > http://www2.renesas.com/usb/en/product/upd720114.html) on board with > > the Overo as the host and the microcontroller as one of the USB > > devices. Provide the other three (powered) USB ports for direct > > keyboard, mouse, memory etc. > > 3) If using the board standalone, then use the microcontroller as the USB > host. > > > > OVERO<----uart---->MICRO<---usb--->USB jack > > \----usb host--->USB Hub Chip---usb client--->MICRO > > \-------> > > 3x powered usb ports > > > > Proposed Overo Interface board: > > 1xLM3S2793 (http://www.luminarymicro.com/products/lm3s2793.html): > > - 3.3V chip (pins are 5V tolerant and can drive 5V TTL...anyone > > need 5V CMOS?) > > - 80MHz > > - 128kB Flash (some probably used for pre-flashed drivers& > bootloader) > > - 64kB RAM > > - 8 x PWM (expose all) > > - 2 x quad encoders (expose all) > > - 2 x CAN (expose one of these) > > - 2 x I2C (we'll use one bus on board for the gyros, accels, > > battery monitoring) > > - 2 x SPI (use one to connect to overo) > > - 3 x UARTS (expose all) > > - 1 x I2S (does anyone use this?) > > - 16ch 10-bit ADC (more bits is nice but is this really actually > useful?) > > - up-to 60 GPIOs ( expose as many as possible ) > > 1xTPS62111 (or similar 3.3V LDO) > > 1xFT232RQ (or similar USB-Serial interface chip; same interface to > > Overo as other boards) > > 4xLEDs (1 for power; 3 bits gives 8 debugging states) > > 3xpushbuttons|switches ( 1xpower, 2x controls) > > 1xLSM303DLH (http://www.st.com/stonline/products/literature/ds/16941.pdf > ) > > > > **connectors** > > 1x 5V power jack > > 1x 5V battery hookup (support 3A on PWM traces) > > 1x full-size USB A connector (USB host) > > 1x mini-USB (console port) > > 2x 70 connectors for Overo > > 1x 3 by 20 pin breakout (first 3 by 8 are PWM, 5V and Unfiltered GND > > for standard servos, 6 pins for 3.3V and filtered Gnd, 3x2pins for 3 > > UARTS, 2pins I2C, 16 pins for ADC, 2 pins for CAN...what do people > > actually need here?, 2 pins for encoders) > > > > Okay---that's a lot to digest. Any feedback and suggestions are welcome. > > > > -Ash > > > > > ------------------------------------------------------------------------------ > > > > _______________________________________________ > > gumstix-users mailing list > > gum...@li... > > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > > -- > UTS CRICOS Provider Code: 00099F > DISCLAIMER: This email message and any accompanying attachments may contain > confidential information. If you are not the intended recipient, do not > read, use, disseminate, distribute or copy this message or attachments. If > you have received this message in error, please notify the sender > immediately and delete this message. Any views expressed in this message > are those of the individual sender, except where the sender expressly, and > with authority, states them to be the views the University of Technology, > Sydney. Before opening any attachments, please check them for viruses and > defects. > > > ------------------------------------------------------------------------------ > > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Ash C. <ash...@gm...> - 2010-05-20 01:27:13
|
Hi Alex, Thanks for the feedback. On Tue, May 18, 2010 at 6:47 PM, Alex Gibson <al...@al...> wrote: > Make it completely 5V tolerant ? > Or have configurable level shifters 3.3/5V via switch > > spi/i2c/can would be great. > > Make it so it can take screw terminals as well as usual pin headers. > (e.g like this board > http://www.bdmicro.com/include/display_image.php?img=/mavric-iib/mav2b_t1_vsm.jpg > ) > Makes it very easy when protoyping. Hmm---this increases the package size substantially! Would packaging|selling pin-header to screw terminal adapters be an acceptable compromise? > > rtc with battery back up. Can you give me a use case? > > polarity protection/diodes on the power and battery connectors to > prevent those doh moments > when tired/in a rush. Agreed. It is way too easy to make such errors the night before a final project is due ;-) > > 3 pins for encoders (x,y and z) but probably not need by most people. Is anyone else using 3 axis encoders? > > Is there a need for the accelerometer and gyros on board ? > The breakout boards from sparkfun are pretty handy and easy to use. > Or have them removable via a jumper or few. > > http://www.sparkfun.com/commerce/product_info.php?products_id=9801 gyro > > accelerometers > http://www.sparkfun.com/commerce/categories.php?c=163 > http://www.sparkfun.com/commerce/product_info.php?products_id=9652 > http://www.sparkfun.com/commerce/product_info.php?products_id=8791 > This is a good question. The Sparkfun boards are admittedly very handy--I've certainly used them before. But I get frustrated sometimes when I'm building devices and find myself glueing together 15 components because no single board had everything I needed. Does this board solve the problem? Not by a long shot! However, I think accelerometers, gyros, and magnetometers are pretty generically useful devices that are relatively cheap for Gumstix to buy in bulk but are expensive for individuals building cool things (and we definitely want people to build cool thing :D ). One option would be to make these a optional components---you can choose to buy the board with or without them. I'm very eager for feedback on this particular point: should we include an accel, gyro, and mag and if so, what are users requirements? Thanks again Alex, -Ash > > > > > Alex > > On 19/05/2010 5:43 AM, Ash Charles wrote: >> Hi All, >> >> I've been working on a robostix-equivalent board for Overo and was >> hoping to get suggestions on what this board should look like. There >> have been some very interesting post related to such a board in the >> last week so having feedback would be fantastic. >> >> *** Desired Features*** >> - I2C bus >> - CAN bus (notably missing from all our boards) >> - at least 6 PWM lines ( makes servo control easy, steppers are nice too) >> - at least 20 GPIOs ('cause people like to do lots of crazy things >> with GPIOs; these should be 5V tolerant) >> - SPI bus breakout >> - at least 2xUARTs >> - battery powerable (charging& battery monitoring circuit would be >> nice but haven't spec'ed it) >> - a few on-board leds and switches ('cause this makes debugging so much easier) >> - a USB host interface (from Overo; 'cause this gives easy extensibility) >> - a usb console port ( from Overo) >> - an ADC (there is already an ADC on the Overo but it is useful to >> have access to analog data on real-time chip) >> - accel, gyro, and/or digital compass (these parts enable lots of >> cool project but are a pain to put on your own daughter board) >> - a microcontroller (>20MHz,>32kB flash,>32kB ram) >> - interface to the Overo on SPI0 >> >> An interesting option exists: >> 1) Get rid of the FTDI chip; use the CDC device class on the >> microcontroller to provide from-boot console access to the overo. This >> means a UART connection from microcontroller->Overo. Does this >> require reflashing the boot rom for the microcontroller? >> 2) Put a USB Hub controller (like >> http://www2.renesas.com/usb/en/product/upd720114.html) on board with >> the Overo as the host and the microcontroller as one of the USB >> devices. Provide the other three (powered) USB ports for direct >> keyboard, mouse, memory etc. >> 3) If using the board standalone, then use the microcontroller as the USB host. >> >> OVERO<----uart---->MICRO<---usb--->USB jack >> \----usb host--->USB Hub Chip---usb client--->MICRO >> \-------> >> 3x powered usb ports >> >> Proposed Overo Interface board: >> 1xLM3S2793 (http://www.luminarymicro.com/products/lm3s2793.html): >> - 3.3V chip (pins are 5V tolerant and can drive 5V TTL...anyone >> need 5V CMOS?) >> - 80MHz >> - 128kB Flash (some probably used for pre-flashed drivers& bootloader) >> - 64kB RAM >> - 8 x PWM (expose all) >> - 2 x quad encoders (expose all) >> - 2 x CAN (expose one of these) >> - 2 x I2C (we'll use one bus on board for the gyros, accels, >> battery monitoring) >> - 2 x SPI (use one to connect to overo) >> - 3 x UARTS (expose all) >> - 1 x I2S (does anyone use this?) >> - 16ch 10-bit ADC (more bits is nice but is this really actually useful?) >> - up-to 60 GPIOs ( expose as many as possible ) >> 1xTPS62111 (or similar 3.3V LDO) >> 1xFT232RQ (or similar USB-Serial interface chip; same interface to >> Overo as other boards) >> 4xLEDs (1 for power; 3 bits gives 8 debugging states) >> 3xpushbuttons|switches ( 1xpower, 2x controls) >> 1xLSM303DLH (http://www.st.com/stonline/products/literature/ds/16941.pdf) >> >> **connectors** >> 1x 5V power jack >> 1x 5V battery hookup (support 3A on PWM traces) >> 1x full-size USB A connector (USB host) >> 1x mini-USB (console port) >> 2x 70 connectors for Overo >> 1x 3 by 20 pin breakout (first 3 by 8 are PWM, 5V and Unfiltered GND >> for standard servos, 6 pins for 3.3V and filtered Gnd, 3x2pins for 3 >> UARTS, 2pins I2C, 16 pins for ADC, 2 pins for CAN...what do people >> actually need here?, 2 pins for encoders) >> >> Okay---that's a lot to digest. Any feedback and suggestions are welcome. >> >> -Ash >> >> ------------------------------------------------------------------------------ >> >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > > > -- > UTS CRICOS Provider Code: 00099F > DISCLAIMER: This email message and any accompanying attachments may contain > confidential information. If you are not the intended recipient, do not > read, use, disseminate, distribute or copy this message or attachments. If > you have received this message in error, please notify the sender > immediately and delete this message. Any views expressed in this message > are those of the individual sender, except where the sender expressly, and > with authority, states them to be the views the University of Technology, > Sydney. Before opening any attachments, please check them for viruses and > defects. > > ------------------------------------------------------------------------------ > > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Ash C. <as...@gu...> - 2010-05-20 01:07:25
|
Hi Dave, Thanks for the comments :). On Tue, May 18, 2010 at 2:24 PM, Dave Hylands <dhy...@gm...> wrote: > Hi Ash, > > On Tue, May 18, 2010 at 12:43 PM, Ash Charles <as...@gu...> wrote: >> Hi All, >> >> I've been working on a robostix-equivalent board for Overo and was >> hoping to get suggestions on what this board should look like. There >> have been some very interesting post related to such a board in the >> last week so having feedback would be fantastic. > ...snip... >> Proposed Overo Interface board: >> 1xLM3S2793 (http://www.luminarymicro.com/products/lm3s2793.html): >> - 3.3V chip (pins are 5V tolerant and can drive 5V TTL...anyone >> need 5V CMOS?) > > Looks pretty nice. > > I've played with some of the other luminary micro chips, and I quite > like the feature set. Luminary looks like they've actually done the work ensure their firmware works as well. > > If you can drive 5v TTL you can drive 5v CMOS. Hmm....I thought the >2.4V was considered high for 5V TTL whereas 5V CMOS requires a >4.44V level for a high (source: http://focus.ti.com/lit/an/scea035a/scea035a.pdf). Am I getting something backwards? > > For the busses that are going to connect to the overo, I'd recommend > using jumpers (or some of those tiny little switches) so that they can > be disconnected. And connected directly to the microcontroller instead? I'm very interested in making this act as a standalone board as well if that is what you meant. > >> *** Desired Features*** >> - I2C bus >> - CAN bus (notably missing from all our boards) >> - at least 6 PWM lines ( makes servo control easy, steppers are nice too) >> - at least 20 GPIOs ('cause people like to do lots of crazy things >> with GPIOs; these should be 5V tolerant) >> - SPI bus breakout >> - at least 2xUARTs >> - battery powerable (charging & battery monitoring circuit would be >> nice but haven't spec'ed it) >> - a few on-board leds and switches ('cause this makes debugging so much easier) >> - a USB host interface (from Overo; 'cause this gives easy extensibility) >> - a usb console port ( from Overo) >> - an ADC (there is already an ADC on the Overo but it is useful to >> have access to analog data on real-time chip) >> - accel, gyro, and/or digital compass (these parts enable lots of >> cool project but are a pain to put on your own daughter board) > > I just picked up one of these: > <http://www.sparkfun.com/commerce/product_info.php?products_id=9623> > to play with, which has your 3-axis gyro, 3-axiss accelerometer, and > 3-axis magnetometer. What are the advantages of having both a gyro and a magnetometer rather than just one of the two? This looks like a very nice part but seems a bit expensive to put on more than one robot. > >> - a microcontroller (>20MHz, >32kB flash, >32kB ram) >> - interface to the Overo on SPI0 >> >> An interesting option exists: >> 1) Get rid of the FTDI chip; use the CDC device class on the >> microcontroller to provide from-boot console access to the overo. This >> means a UART connection from microcontroller->Overo. Does this >> require reflashing the boot rom for the microcontroller? > > I probably wouldn't get rid of the FTDI unless you're really crammed > for space. It seems like quite an imposition to ensure that the > microcontroller be running the USB stuff properly in order to use the > console on the gumstix. This makes things really tough when you're > developing code for the microcontroller. Agreed. This seemed like a lovely idea in my head and certainly seems possible but a basic FTDI console is just too useful to not include despite the expense and increased package size. > >> 2) Put a USB Hub controller (like >> http://www2.renesas.com/usb/en/product/upd720114.html) on board with >> the Overo as the host and the microcontroller as one of the USB >> devices. Provide the other three (powered) USB ports for direct >> keyboard, mouse, memory etc. > > I think that would a wonderful idea. > >> 3) If using the board standalone, then use the microcontroller as the USB host. >> >> OVERO<----uart---->MICRO<---usb--->USB jack >> \----usb host--->USB Hub Chip---usb client--->MICRO >> \-------> >> 3x powered usb ports >> >> - 80MHz >> - 128kB Flash (some probably used for pre-flashed drivers & bootloader) >> - 64kB RAM >> - 8 x PWM (expose all) >> - 2 x quad encoders (expose all) >> - 2 x CAN (expose one of these) >> - 2 x I2C (we'll use one bus on board for the gyros, accels, >> battery monitoring) >> - 2 x SPI (use one to connect to overo) >> - 3 x UARTS (expose all) >> - 1 x I2S (does anyone use this?) >> - 16ch 10-bit ADC (more bits is nice but is this really actually useful?) >> - up-to 60 GPIOs ( expose as many as possible ) >> 1xTPS62111 (or similar 3.3V LDO) >> 1xFT232RQ (or similar USB-Serial interface chip; same interface to >> Overo as other boards) >> 4xLEDs (1 for power; 3 bits gives 8 debugging states) >> 3xpushbuttons|switches ( 1xpower, 2x controls) >> 1xLSM303DLH (http://www.st.com/stonline/products/literature/ds/16941.pdf) >> >> **connectors** >> 1x 5V power jack >> 1x 5V battery hookup (support 3A on PWM traces) > > I'm assuming that you're putting a set of 3-pin headers for connecting > up servos? In which case, I would probably want to allow the servo > voltage to go upto around 9v - yeah most servos are only rated up to > 6v, but lots of people overvoltage them. This was accomodated on the > robostix by having a removable jumper. > > If you're going to allow all 8 servos to be connected, then I would > allow at least 0.5A per servo, so 4A for the power and ground traces. > The PWM traces don't need to be high current. Yes. The intention is to have a 3 by 8 pin header. The bottom (or top) row is 4A unfiltered ground, the second is unfiltered battery V+ (at whatever voltage you like...good point about overvoltaging), and the third is the PWM signal. > >> 1x full-size USB A connector (USB host) >> 1x mini-USB (console port) >> 2x 70 connectors for Overo >> 1x 3 by 20 pin breakout (first 3 by 8 are PWM, 5V and Unfiltered GND >> for standard servos, 6 pins for 3.3V and filtered Gnd, 3x2pins for 3 >> UARTS, 2pins I2C, 16 pins for ADC, 2 pins for CAN...what do people >> actually need here?, 2 pins for encoders) > > Encoders typically need power ground, and A/B signals (per encoder). > I2C needs a ground. > I know on the robostix it was really nice to have power/ground/signal > for each ADC since it allowed your sensors to be interchangable. Okay---I think the way to do this is to carry ground right across one row of the header and then put the appropriate signals above it e.g. a single set of three pins would be {SDA, SDL, GND}. This might cut down on the number of GPIOs and ADC lines but getting the interface right is probably more important in terms of making things easy to use. > > -- > Dave Hylands > Shuswap, BC, Canada > http://www.DaveHylands.com/ > Thanks again, Ash |
From: Charles M. <man...@ac...> - 2010-05-20 01:20:01
|
On Thursday 20 May 2010 13:06:58 Ash Charles wrote: > What are the advantages of having both a gyro and a magnetometer > rather than just one of the two? This looks like a very nice part but > seems a bit expensive to put on more than one robot. Gyros are rate devices. The signal you get out of them indicates a rate of rotation. You need to integrate that over time to get an attitude (ie angle you're facing). Since gyros are imperfect and have some offset in the voltage, the gyro will look as if it is turning slowly and and when you integrate that the gyro looks like it is slowly rolling when in fact it is sitting right way up and not moving. To correct for that you need some sort of reference that is not a rate device. examples are accelerometers and magnetometers. These have their own deficiencies: * accelerometers can't tell the difference between tilt and acceleration. * magnetometers go crazy when they move past ferrous objects. Thus, you take these different kinds of sensors and mash them through some sort of fusion filter (eg. http://en.wikipedia.org/wiki/Kalman_filter). The idea being that you're getting all the good properties of the sensors and none of the bad. |
From: Ash C. <as...@gu...> - 2010-05-20 01:41:00
|
Hi Charles, Thanks for the clarification. Would providing this http://www.st.com/stonline/products/literature/ds/16941.pdf and this http://www.st.com/stonline/products/literature/ds/17116.pdf be sufficient then? I picked these two as they are relatively cheap, give digital output and are spec'd for what I would consider to be a pretty generic range of operation. How do they look to you? The corresponding Honeywell parts that are so common seem to be comparably expensive. -Ash @Charles: sorry for the double e-mail. I meant to reply to the list, not just directly to you. On Wed, May 19, 2010 at 6:19 PM, Charles Manning <man...@ac...> wrote: > On Thursday 20 May 2010 13:06:58 Ash Charles wrote: > >> What are the advantages of having both a gyro and a magnetometer >> rather than just one of the two? This looks like a very nice part but >> seems a bit expensive to put on more than one robot. > > Gyros are rate devices. The signal you get out of them indicates a rate of > rotation. You need to integrate that over time to get an attitude (ie angle > you're facing). Since gyros are imperfect and have some offset in the > voltage, the gyro will look as if it is turning slowly and and when you > integrate that the gyro looks like it is slowly rolling when in fact it is > sitting right way up and not moving. > > To correct for that you need some sort of reference that is not a rate device. > examples are accelerometers and magnetometers. These have their own > deficiencies: > * accelerometers can't tell the difference between tilt and acceleration. > * magnetometers go crazy when they move past ferrous objects. > > > Thus, you take these different kinds of sensors and mash them through some > sort of fusion filter (eg. http://en.wikipedia.org/wiki/Kalman_filter). The > idea being that you're getting all the good properties of the sensors and > none of the bad. > > > > > > |
From: Dave H. <dhy...@gm...> - 2010-05-20 05:13:51
|
Hi Ash, ...snip... >> If you can drive 5v TTL you can drive 5v CMOS. > Hmm....I thought the >2.4V was considered high for 5V TTL whereas 5V > CMOS requires a >4.44V level for a high (source: > http://focus.ti.com/lit/an/scea035a/scea035a.pdf). Am I getting > something backwards? Hmmm. Here's a chart showing the various voltages: <http://www.interfacebus.com/voltage_threshold.html> I was under the impression that 3.3v would be considered a logic high by 5v CMOS, but it seems I'm wrong. I even went and checked a few data sheets for some CMOS parts. >> For the busses that are going to connect to the overo, I'd recommend >> using jumpers (or some of those tiny little switches) so that they can >> be disconnected. > And connected directly to the microcontroller instead? I'm very > interested in making this act as a standalone board as well if that is > what you meant. For example, on the robostix, the i2c bus and the SPI bus are connected from the ATMega128 to the verdex. It would be nice to be able to disconnect them. Obvioulsy, when used in standalone mode, the wires just goto the 70-pin headers. >>> *** Desired Features*** >>> - I2C bus >>> - CAN bus (notably missing from all our boards) >>> - at least 6 PWM lines ( makes servo control easy, steppers are nice too) >>> - at least 20 GPIOs ('cause people like to do lots of crazy things >>> with GPIOs; these should be 5V tolerant) >>> - SPI bus breakout >>> - at least 2xUARTs >>> - battery powerable (charging & battery monitoring circuit would be >>> nice but haven't spec'ed it) >>> - a few on-board leds and switches ('cause this makes debugging so much easier) >>> - a USB host interface (from Overo; 'cause this gives easy extensibility) >>> - a usb console port ( from Overo) >>> - an ADC (there is already an ADC on the Overo but it is useful to >>> have access to analog data on real-time chip) >>> - accel, gyro, and/or digital compass (these parts enable lots of >>> cool project but are a pain to put on your own daughter board) >> >> I just picked up one of these: >> <http://www.sparkfun.com/commerce/product_info.php?products_id=9623> >> to play with, which has your 3-axis gyro, 3-axiss accelerometer, and >> 3-axis magnetometer. > What are the advantages of having both a gyro and a magnetometer > rather than just one of the two? This looks like a very nice part but > seems a bit expensive to put on more than one robot. A magnetometer gives you an absolute reference, however it has a flaw in that if the Z-axis exactly lined up with the magnetic flux lines you'll get the exact same readings if you rotate about the axis that forms the flux lines. The accelerometer lets you know which way is down, but that changes as you start moving around (i.e. accelerating) The gyro helps you measure changes in acceleration, but suffers from drift issues. You can put all 3 together and each one can help to overcome the deficiencies of the others. -- Dave Hylands Shuswap, BC, Canada http://www.DaveHylands.com/ |
From: Ash C. <as...@gu...> - 2010-05-22 00:02:46
|
Afternoon, We've looked through the pin-muxing for this board and we propose the following 3 by 8 pin right-angle 0.1"pitch male headers: =====HEADER #1===== PWM0 PWM1 PWM2 PWM3 PWM4 PWM5 PWM6 PWM7 Vbat Vbat Vbat Vbat Vbat Vbat Vbat Vbat GND GND GND GND GND GND GND GND =====HEADER #2===== UART-TX0 UART-TX1 UART-TX3 5V CAN-TX SPI-MOSI SPI-CLK I2C-SDA UART-RX0 UART-RX1 UART-RX3 3.3V CAN-RX SPI-MISO SPI-CS I2C-SCL GND GND GND GND GND GND GND GND =====HEADER #3===== 5V AIN0 AIN2 AIN4 AIN6 AIN8|PHA1 AIN14|PHA0 5V 3.3V AIN1 AIN3 AIN5 AIN7 AIN9|PHB1 PHB0 3.3V GND AGND AVREF AGND AGND AGND AIN15 GND (The three banks will be on the same side of the board at a multiple of 0.1" spacing so you can connect one large header if you so desire.) This should yield something along the lines of... 12xADC (in differential pairs) 34xGPIO 3xUARTS 1xI2C 1xSPI 1xCAN 2xQuadrature Encoders 8xPWM. The motivation for this layout was to make it as easy as possible to connect just what you need (hence the GND and power pins everywhere) without needing headers connected to every pin. Firstly: does this strike the right balance of outputs? Secondly: is the arrangement of pins correct? -- on Header #2, should the UARTS be four pins each (RX, V+, TX, GND) with all three stacked on top of each other? e.g. RX0 5V TX0 GND RX1 5V TX1 GND RX2 5V TX2 GND Thanks, Ash On Wed, May 19, 2010 at 10:13 PM, Dave Hylands <dhy...@gm...> wrote: > Hi Ash, > > ...snip... >>> If you can drive 5v TTL you can drive 5v CMOS. >> Hmm....I thought the >2.4V was considered high for 5V TTL whereas 5V >> CMOS requires a >4.44V level for a high (source: >> http://focus.ti.com/lit/an/scea035a/scea035a.pdf). Am I getting >> something backwards? > > Hmmm. > > Here's a chart showing the various voltages: > <http://www.interfacebus.com/voltage_threshold.html> > > I was under the impression that 3.3v would be considered a logic high > by 5v CMOS, but it seems I'm wrong. > I even went and checked a few data sheets for some CMOS parts. > >>> For the busses that are going to connect to the overo, I'd recommend >>> using jumpers (or some of those tiny little switches) so that they can >>> be disconnected. >> And connected directly to the microcontroller instead? I'm very >> interested in making this act as a standalone board as well if that is >> what you meant. > > For example, on the robostix, the i2c bus and the SPI bus are > connected from the ATMega128 to the verdex. It would be nice to be > able to disconnect them. > > Obvioulsy, when used in standalone mode, the wires just goto the 70-pin headers. > >>>> *** Desired Features*** >>>> - I2C bus >>>> - CAN bus (notably missing from all our boards) >>>> - at least 6 PWM lines ( makes servo control easy, steppers are nice too) >>>> - at least 20 GPIOs ('cause people like to do lots of crazy things >>>> with GPIOs; these should be 5V tolerant) >>>> - SPI bus breakout >>>> - at least 2xUARTs >>>> - battery powerable (charging & battery monitoring circuit would be >>>> nice but haven't spec'ed it) >>>> - a few on-board leds and switches ('cause this makes debugging so much easier) >>>> - a USB host interface (from Overo; 'cause this gives easy extensibility) >>>> - a usb console port ( from Overo) >>>> - an ADC (there is already an ADC on the Overo but it is useful to >>>> have access to analog data on real-time chip) >>>> - accel, gyro, and/or digital compass (these parts enable lots of >>>> cool project but are a pain to put on your own daughter board) >>> >>> I just picked up one of these: >>> <http://www.sparkfun.com/commerce/product_info.php?products_id=9623> >>> to play with, which has your 3-axis gyro, 3-axiss accelerometer, and >>> 3-axis magnetometer. >> What are the advantages of having both a gyro and a magnetometer >> rather than just one of the two? This looks like a very nice part but >> seems a bit expensive to put on more than one robot. > > A magnetometer gives you an absolute reference, however it has a flaw > in that if the Z-axis exactly lined up with the magnetic flux lines > you'll get the exact same readings if you rotate about the axis that > forms the flux lines. > > The accelerometer lets you know which way is down, but that changes as > you start moving around (i.e. accelerating) > > The gyro helps you measure changes in acceleration, but suffers from > drift issues. > > You can put all 3 together and each one can help to overcome the > deficiencies of the others. > > -- > Dave Hylands > Shuswap, BC, Canada > http://www.DaveHylands.com/ > > ------------------------------------------------------------------------------ > > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Dave H. <dhy...@gm...> - 2010-05-22 01:47:29
|
Hi Ash, On Fri, May 21, 2010 at 5:01 PM, Ash Charles <as...@gu...> wrote: > Afternoon, > > We've looked through the pin-muxing for this board and we propose the > following 3 by 8 pin right-angle 0.1"pitch male headers: > > =====HEADER #1===== > PWM0 PWM1 PWM2 PWM3 PWM4 PWM5 PWM6 PWM7 > Vbat Vbat Vbat Vbat Vbat Vbat Vbat Vbat > GND GND GND GND GND GND GND GND Hopefully, these will be Vmotor, which is jumpered to Vbat. > =====HEADER #2===== > UART-TX0 UART-TX1 UART-TX3 5V CAN-TX SPI-MOSI SPI-CLK I2C-SDA > UART-RX0 UART-RX1 UART-RX3 3.3V CAN-RX SPI-MISO SPI-CS I2C-SCL > GND GND GND GND GND GND > GND GND > > =====HEADER #3===== > 5V AIN0 AIN2 AIN4 AIN6 AIN8|PHA1 AIN14|PHA0 5V > 3.3V AIN1 AIN3 AIN5 AIN7 AIN9|PHB1 PHB0 3.3V > GND AGND AVREF AGND AGND AGND AIN15 GND > > (The three banks will be on the same side of the board at a multiple > of 0.1" spacing so you can connect one large header if you so desire.) > > This should yield something along the lines of... > 12xADC (in differential pairs) > 34xGPIO > 3xUARTS > 1xI2C > 1xSPI > 1xCAN > 2xQuadrature Encoders > 8xPWM. > > The motivation for this layout was to make it as easy as possible to > connect just what you need (hence the GND and power pins everywhere) > without needing headers connected to every pin. > > Firstly: does this strike the right balance of outputs? How will the luminary micro be programmed? Will a JTAG interface be available? > Secondly: is the arrangement of pins correct? > -- on Header #2, should the UARTS be four pins each (RX, V+, TX, > GND) with all three stacked on top of each other? e.g. > RX0 5V TX0 GND > RX1 5V TX1 GND > RX2 5V TX2 GND The Arduino stuff seems to have standardized on using: the same pinout as the FTDI USB-to-logic level serial connectors which is 1 - GND 2 - CTS 3 - VCC 4 - TXD 5 - RXD 6 - RTS <http://www.ftdichip.com/Products/EvaluationKits/TTL-232R-3V3.htm> On the Arduino, the RTS pin is tied into the reset circuitry so that the board can be reset (and serial downloaded to) from the host. Having the 4 pin layout which is compatible with the robostix also makes sense. I just wanted to throw out the Arduino thing since it's quite popular. -- Dave Hylands Shuswap, BC, Canada http://www.DaveHylands.com/ |
From: Ash C. <ash...@gm...> - 2010-05-22 07:40:46
|
On Fri, May 21, 2010 at 6:40 PM, Dave Hylands <dhy...@gm...> wrote: > Hi Ash, > > On Fri, May 21, 2010 at 5:01 PM, Ash Charles <as...@gu...> wrote: >> Afternoon, >> >> We've looked through the pin-muxing for this board and we propose the >> following 3 by 8 pin right-angle 0.1"pitch male headers: >> >> =====HEADER #1===== >> PWM0 PWM1 PWM2 PWM3 PWM4 PWM5 PWM6 PWM7 >> Vbat Vbat Vbat Vbat Vbat Vbat Vbat Vbat >> GND GND GND GND GND GND GND GND > > Hopefully, these will be Vmotor, which is jumpered to Vbat. To make sure I understand what you meant in your previous post, the jumper on the Robostix allowed people to use either a battery or a wall wart to supply power to the board? For the new board, the 'Vbat' signal (definitely a misnomer on my part) would be the V+ line taken directly from the power source be it a wall wart or a battery. > >> =====HEADER #2===== >> UART-TX0 UART-TX1 UART-TX3 5V CAN-TX SPI-MOSI SPI-CLK I2C-SDA >> UART-RX0 UART-RX1 UART-RX3 3.3V CAN-RX SPI-MISO SPI-CS I2C-SCL >> GND GND GND GND GND GND >> GND GND >> >> =====HEADER #3===== >> 5V AIN0 AIN2 AIN4 AIN6 AIN8|PHA1 AIN14|PHA0 5V >> 3.3V AIN1 AIN3 AIN5 AIN7 AIN9|PHB1 PHB0 3.3V >> GND AGND AVREF AGND AGND AGND AIN15 GND >> >> (The three banks will be on the same side of the board at a multiple >> of 0.1" spacing so you can connect one large header if you so desire.) >> >> This should yield something along the lines of... >> 12xADC (in differential pairs) >> 34xGPIO >> 3xUARTS >> 1xI2C >> 1xSPI >> 1xCAN >> 2xQuadrature Encoders >> 8xPWM. >> >> The motivation for this layout was to make it as easy as possible to >> connect just what you need (hence the GND and power pins everywhere) >> without needing headers connected to every pin. >> >> Firstly: does this strike the right balance of outputs? > > How will the luminary micro be programmed? Will a JTAG interface be available? I hadn't included the JTAG interface; I think this requires an additional four pins which is not impossible but board space would start to get tight. One option would be putting contact pads for JTAG...does this seem useful? The device can be accessed via I2C0, UART0, or SSI0. > >> Secondly: is the arrangement of pins correct? >> -- on Header #2, should the UARTS be four pins each (RX, V+, TX, >> GND) with all three stacked on top of each other? e.g. >> RX0 5V TX0 GND >> RX1 5V TX1 GND >> RX2 5V TX2 GND > > The Arduino stuff seems to have standardized on using: > the same pinout as the FTDI USB-to-logic level serial connectors which is > > 1 - GND > 2 - CTS > 3 - VCC > 4 - TXD > 5 - RXD > 6 - RTS > > <http://www.ftdichip.com/Products/EvaluationKits/TTL-232R-3V3.htm> > > On the Arduino, the RTS pin is tied into the reset circuitry so that > the board can be reset (and serial downloaded to) from the host. > > Having the 4 pin layout which is compatible with the robostix also > makes sense. I just wanted to throw out the Arduino thing since it's > quite popular. Thanks for pointing out the Arduino connector; I'd been hunting around to see if there was such a standard earlier today and hadn't found anything. Is there a strong motivation for including the CTS and RTS lines? I don't recall using them before so I found it hard to justify extra pins but perhaps this is more a reflection on my inexperience than on the utility of these pins. Thanks, Ash |
From: vwyodapink <vwy...@gm...> - 2010-05-22 08:47:05
|
Have you thought of possibly having it interface with an ArduIMU V.2 or a UAVDev Board? Just thought I would throw that out there since someone brought up the 9D IMU from SF. There is a similar one to that called the ArduIMU but its clocked higher than the one sparkfun sells. Also there is a few boards the guys at pixhawk have the designs for that are for the overo that sound similar. Right now I am adding a overo fire and summit to both my ardupilot and UDB set-ups as an on board computer for on board video/tracking and some other things. By no means am I experienced in any of this but just figured it might add some food for thought to your project and future possibilities or expandability. J Ash Charles wrote: > > On Fri, May 21, 2010 at 6:40 PM, Dave Hylands <dhy...@gm...> wrote: >> Hi Ash, >> >> On Fri, May 21, 2010 at 5:01 PM, Ash Charles <as...@gu...> wrote: >>> Afternoon, >>> >>> We've looked through the pin-muxing for this board and we propose the >>> following 3 by 8 pin right-angle 0.1"pitch male headers: >>> >>> =====HEADER #1===== >>> PWM0 PWM1 PWM2 PWM3 PWM4 PWM5 PWM6 PWM7 >>> Vbat Vbat Vbat Vbat Vbat Vbat Vbat Vbat >>> GND GND GND GND GND GND GND GND >> >> Hopefully, these will be Vmotor, which is jumpered to Vbat. > To make sure I understand what you meant in your previous post, the > jumper on the Robostix allowed people to use either a battery or a > wall wart to supply power to the board? > For the new board, the 'Vbat' signal (definitely a misnomer on my > part) would be the V+ line taken directly from the power source be it > a wall wart or a battery. >> >>> =====HEADER #2===== >>> UART-TX0 UART-TX1 UART-TX3 5V CAN-TX SPI-MOSI SPI-CLK >>> I2C-SDA >>> UART-RX0 UART-RX1 UART-RX3 3.3V CAN-RX SPI-MISO SPI-CS >>> I2C-SCL >>> GND GND GND GND GND GND >>> GND GND >>> >>> =====HEADER #3===== >>> 5V AIN0 AIN2 AIN4 AIN6 AIN8|PHA1 AIN14|PHA0 5V >>> 3.3V AIN1 AIN3 AIN5 AIN7 AIN9|PHB1 PHB0 >>> 3.3V >>> GND AGND AVREF AGND AGND AGND AIN15 GND >>> >>> (The three banks will be on the same side of the board at a multiple >>> of 0.1" spacing so you can connect one large header if you so desire.) >>> >>> This should yield something along the lines of... >>> 12xADC (in differential pairs) >>> 34xGPIO >>> 3xUARTS >>> 1xI2C >>> 1xSPI >>> 1xCAN >>> 2xQuadrature Encoders >>> 8xPWM. >>> >>> The motivation for this layout was to make it as easy as possible to >>> connect just what you need (hence the GND and power pins everywhere) >>> without needing headers connected to every pin. >>> >>> Firstly: does this strike the right balance of outputs? >> >> How will the luminary micro be programmed? Will a JTAG interface be >> available? > I hadn't included the JTAG interface; I think this requires an > additional four pins which is not impossible but board space would > start to get tight. One option would be putting contact pads for > JTAG...does this seem useful? > The device can be accessed via I2C0, UART0, or SSI0. >> >>> Secondly: is the arrangement of pins correct? >>> -- on Header #2, should the UARTS be four pins each (RX, V+, TX, >>> GND) with all three stacked on top of each other? e.g. >>> RX0 5V TX0 GND >>> RX1 5V TX1 GND >>> RX2 5V TX2 GND >> >> The Arduino stuff seems to have standardized on using: >> the same pinout as the FTDI USB-to-logic level serial connectors which is >> >> 1 - GND >> 2 - CTS >> 3 - VCC >> 4 - TXD >> 5 - RXD >> 6 - RTS >> >> <http://www.ftdichip.com/Products/EvaluationKits/TTL-232R-3V3.htm> >> >> On the Arduino, the RTS pin is tied into the reset circuitry so that >> the board can be reset (and serial downloaded to) from the host. >> >> Having the 4 pin layout which is compatible with the robostix also >> makes sense. I just wanted to throw out the Arduino thing since it's >> quite popular. > Thanks for pointing out the Arduino connector; I'd been hunting around > to see if there was such a standard earlier today and hadn't found > anything. > Is there a strong motivation for including the CTS and RTS lines? I > don't recall using them before so I found it hard to justify extra > pins but perhaps this is more a reflection on my inexperience than on > the utility of these pins. > > Thanks, > > Ash > > ------------------------------------------------------------------------------ > > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -- View this message in context: http://old.nabble.com/Robostix-for-Overo-tp28600551p28641961.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Dave H. <dhy...@gm...> - 2010-05-22 15:56:55
|
Hi Ash, On Sat, May 22, 2010 at 12:40 AM, Ash Charles <ash...@gm...> wrote: > On Fri, May 21, 2010 at 6:40 PM, Dave Hylands <dhy...@gm...> wrote: >> Hi Ash, >> >> On Fri, May 21, 2010 at 5:01 PM, Ash Charles <as...@gu...> wrote: >>> Afternoon, >>> >>> We've looked through the pin-muxing for this board and we propose the >>> following 3 by 8 pin right-angle 0.1"pitch male headers: >>> >>> =====HEADER #1===== >>> PWM0 PWM1 PWM2 PWM3 PWM4 PWM5 PWM6 PWM7 >>> Vbat Vbat Vbat Vbat Vbat Vbat Vbat Vbat >>> GND GND GND GND GND GND GND GND >> >> Hopefully, these will be Vmotor, which is jumpered to Vbat. > To make sure I understand what you meant in your previous post, the > jumper on the Robostix allowed people to use either a battery or a > wall wart to supply power to the board? > For the new board, the 'Vbat' signal (definitely a misnomer on my > part) would be the V+ line taken directly from the power source be it > a wall wart or a battery. I guess by battery you really mean a dedicated 2-pin power connector. >> How will the luminary micro be programmed? Will a JTAG interface be available? > I hadn't included the JTAG interface; I think this requires an > additional four pins which is not impossible but board space would > start to get tight. One option would be putting contact pads for > JTAG...does this seem useful? > The device can be accessed via I2C0, UART0, or SSI0. I just wanted to make sure that you address how the device will be programmed. I see that it does indeed have a ROM based bootloader which can be programmed as you indicated, which somewhat alleviates the need for a JTAG. Although having the JTAG allows a debugger to be used, which I think will be important. If you put the pads somewhere that a 10-pin JTAG mini connector could be used <http://www.luminarymicro.com/products/mdl-ada2.html> This could be a surface mount connector. It looks like its a 2x5 0.050" header (see the schematics and BOM for this eval board: <http://www.luminarymicro.com/index.php?option=com_remository&func=download&id=983&chk=d1a772ed2075b69e938af114b279083b&Itemid=591> >>> Secondly: is the arrangement of pins correct? >>> -- on Header #2, should the UARTS be four pins each (RX, V+, TX, >>> GND) with all three stacked on top of each other? e.g. >>> RX0 5V TX0 GND >>> RX1 5V TX1 GND >>> RX2 5V TX2 GND >> >> The Arduino stuff seems to have standardized on using: >> the same pinout as the FTDI USB-to-logic level serial connectors which is >> >> 1 - GND >> 2 - CTS >> 3 - VCC >> 4 - TXD >> 5 - RXD >> 6 - RTS >> >> <http://www.ftdichip.com/Products/EvaluationKits/TTL-232R-3V3.htm> >> >> On the Arduino, the RTS pin is tied into the reset circuitry so that >> the board can be reset (and serial downloaded to) from the host. >> >> Having the 4 pin layout which is compatible with the robostix also >> makes sense. I just wanted to throw out the Arduino thing since it's >> quite popular. > Thanks for pointing out the Arduino connector; I'd been hunting around > to see if there was such a standard earlier today and hadn't found > anything. > Is there a strong motivation for including the CTS and RTS lines? I > don't recall using them before so I found it hard to justify extra > pins but perhaps this is more a reflection on my inexperience than on > the utility of these pins. Being able to reset the microcontroller through the download interface is nice. It means that the SW can do the reset and send the appropriate bytes with appropriate timings, rather than relying on a particular sequence of events by the user. Although looking at the protocol, it seems pretty easy to just start the host side program and then hit reset on the micro. So I think you could eliminate the extra lines if you need the space. It would be nice, especially in standalone mode to be able to connect up the FTDI chip normally used for the overo console to the micro, perhaps using some switches, or DNI resistors. -- Dave Hylands Shuswap, BC, Canada http://www.DaveHylands.com/ |
From: Ash C. <as...@gu...> - 2010-06-15 23:40:00
|
Hi, A preliminary schematic (http://www.gumstix.net/other/B30019.sch) and board design (http://www.gumstix.net/other/B30019.brd) for this Overo-robostix board are available in Eagle format. As before, we welcome your feedback---it is really helpful to know what features are useful for users. Hope you like it :). -Ash On Sat, May 22, 2010 at 8:56 AM, Dave Hylands <dhy...@gm...> wrote: > Hi Ash, > > On Sat, May 22, 2010 at 12:40 AM, Ash Charles <ash...@gm...> wrote: >> On Fri, May 21, 2010 at 6:40 PM, Dave Hylands <dhy...@gm...> wrote: >>> Hi Ash, >>> >>> On Fri, May 21, 2010 at 5:01 PM, Ash Charles <as...@gu...> wrote: >>>> Afternoon, >>>> >>>> We've looked through the pin-muxing for this board and we propose the >>>> following 3 by 8 pin right-angle 0.1"pitch male headers: >>>> >>>> =====HEADER #1===== >>>> PWM0 PWM1 PWM2 PWM3 PWM4 PWM5 PWM6 PWM7 >>>> Vbat Vbat Vbat Vbat Vbat Vbat Vbat Vbat >>>> GND GND GND GND GND GND GND GND >>> >>> Hopefully, these will be Vmotor, which is jumpered to Vbat. >> To make sure I understand what you meant in your previous post, the >> jumper on the Robostix allowed people to use either a battery or a >> wall wart to supply power to the board? >> For the new board, the 'Vbat' signal (definitely a misnomer on my >> part) would be the V+ line taken directly from the power source be it >> a wall wart or a battery. > > I guess by battery you really mean a dedicated 2-pin power connector. > >>> How will the luminary micro be programmed? Will a JTAG interface be available? >> I hadn't included the JTAG interface; I think this requires an >> additional four pins which is not impossible but board space would >> start to get tight. One option would be putting contact pads for >> JTAG...does this seem useful? >> The device can be accessed via I2C0, UART0, or SSI0. > > I just wanted to make sure that you address how the device will be > programmed. I see that it does indeed have a ROM based bootloader > which can be programmed as you indicated, which somewhat alleviates > the need for a JTAG. > > Although having the JTAG allows a debugger to be used, which I think > will be important. > > If you put the pads somewhere that a 10-pin JTAG mini connector could be used > <http://www.luminarymicro.com/products/mdl-ada2.html> This could be a > surface mount connector. It looks like its a 2x5 0.050" header (see > the schematics and BOM for this eval board: > <http://www.luminarymicro.com/index.php?option=com_remository&func=download&id=983&chk=d1a772ed2075b69e938af114b279083b&Itemid=591> > >>>> Secondly: is the arrangement of pins correct? >>>> -- on Header #2, should the UARTS be four pins each (RX, V+, TX, >>>> GND) with all three stacked on top of each other? e.g. >>>> RX0 5V TX0 GND >>>> RX1 5V TX1 GND >>>> RX2 5V TX2 GND >>> >>> The Arduino stuff seems to have standardized on using: >>> the same pinout as the FTDI USB-to-logic level serial connectors which is >>> >>> 1 - GND >>> 2 - CTS >>> 3 - VCC >>> 4 - TXD >>> 5 - RXD >>> 6 - RTS >>> >>> <http://www.ftdichip.com/Products/EvaluationKits/TTL-232R-3V3.htm> >>> >>> On the Arduino, the RTS pin is tied into the reset circuitry so that >>> the board can be reset (and serial downloaded to) from the host. >>> >>> Having the 4 pin layout which is compatible with the robostix also >>> makes sense. I just wanted to throw out the Arduino thing since it's >>> quite popular. >> Thanks for pointing out the Arduino connector; I'd been hunting around >> to see if there was such a standard earlier today and hadn't found >> anything. >> Is there a strong motivation for including the CTS and RTS lines? I >> don't recall using them before so I found it hard to justify extra >> pins but perhaps this is more a reflection on my inexperience than on >> the utility of these pins. > > Being able to reset the microcontroller through the download interface > is nice. It means that the SW can do the reset and send the > appropriate bytes with appropriate timings, rather than relying on a > particular sequence of events by the user. > > Although looking at the protocol, it seems pretty easy to just start > the host side program and then hit reset on the micro. So I think you > could eliminate the extra lines if you need the space. > > It would be nice, especially in standalone mode to be able to connect > up the FTDI chip normally used for the overo console to the micro, > perhaps using some switches, or DNI resistors. > > -- > Dave Hylands > Shuswap, BC, Canada > http://www.DaveHylands.com/ > > ------------------------------------------------------------------------------ > > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: vwyodapink <vwy...@gm...> - 2010-06-16 00:30:30
|
What about adding a connector on the board for a GPS like the Ublock or EM406 Though I am sure not useful to everyone but a absolute pressure sensor with temp would be nice. I have heard there are a bunch of vibration issues with the gyro you have listed you are using, Invensense is making a vibration resistant gyro that has been used in a few projects that I have seen and has had really great results. I am by no means an expert at all, just remember reading a bunch about those gyros on a different message board and they were ditched because of horrible performance. Ash Charles-2 wrote: > > Hi, > > A preliminary schematic (http://www.gumstix.net/other/B30019.sch) and > board design (http://www.gumstix.net/other/B30019.brd) for this > Overo-robostix board are available in Eagle format. As before, we > welcome your feedback---it is really helpful to know what features are > useful for users. > > Hope you like it :). > > -Ash > > On Sat, May 22, 2010 at 8:56 AM, Dave Hylands <dhy...@gm...> wrote: >> Hi Ash, >> >> On Sat, May 22, 2010 at 12:40 AM, Ash Charles <ash...@gm...> >> wrote: >>> On Fri, May 21, 2010 at 6:40 PM, Dave Hylands <dhy...@gm...> >>> wrote: >>>> Hi Ash, >>>> >>>> On Fri, May 21, 2010 at 5:01 PM, Ash Charles <as...@gu...> wrote: >>>>> Afternoon, >>>>> >>>>> We've looked through the pin-muxing for this board and we propose the >>>>> following 3 by 8 pin right-angle 0.1"pitch male headers: >>>>> >>>>> =====HEADER #1===== >>>>> PWM0 PWM1 PWM2 PWM3 PWM4 PWM5 PWM6 PWM7 >>>>> Vbat Vbat Vbat Vbat Vbat Vbat Vbat Vbat >>>>> GND GND GND GND GND GND GND GND >>>> >>>> Hopefully, these will be Vmotor, which is jumpered to Vbat. >>> To make sure I understand what you meant in your previous post, the >>> jumper on the Robostix allowed people to use either a battery or a >>> wall wart to supply power to the board? >>> For the new board, the 'Vbat' signal (definitely a misnomer on my >>> part) would be the V+ line taken directly from the power source be it >>> a wall wart or a battery. >> >> I guess by battery you really mean a dedicated 2-pin power connector. >> >>>> How will the luminary micro be programmed? Will a JTAG interface be >>>> available? >>> I hadn't included the JTAG interface; I think this requires an >>> additional four pins which is not impossible but board space would >>> start to get tight. One option would be putting contact pads for >>> JTAG...does this seem useful? >>> The device can be accessed via I2C0, UART0, or SSI0. >> >> I just wanted to make sure that you address how the device will be >> programmed. I see that it does indeed have a ROM based bootloader >> which can be programmed as you indicated, which somewhat alleviates >> the need for a JTAG. >> >> Although having the JTAG allows a debugger to be used, which I think >> will be important. >> >> If you put the pads somewhere that a 10-pin JTAG mini connector could be >> used >> <http://www.luminarymicro.com/products/mdl-ada2.html> This could be a >> surface mount connector. It looks like its a 2x5 0.050" header (see >> the schematics and BOM for this eval board: >> <http://www.luminarymicro.com/index.php?option=com_remository&func=download&id=983&chk=d1a772ed2075b69e938af114b279083b&Itemid=591> >> >>>>> Secondly: is the arrangement of pins correct? >>>>> -- on Header #2, should the UARTS be four pins each (RX, V+, TX, >>>>> GND) with all three stacked on top of each other? e.g. >>>>> RX0 5V TX0 GND >>>>> RX1 5V TX1 GND >>>>> RX2 5V TX2 GND >>>> >>>> The Arduino stuff seems to have standardized on using: >>>> the same pinout as the FTDI USB-to-logic level serial connectors which >>>> is >>>> >>>> 1 - GND >>>> 2 - CTS >>>> 3 - VCC >>>> 4 - TXD >>>> 5 - RXD >>>> 6 - RTS >>>> >>>> <http://www.ftdichip.com/Products/EvaluationKits/TTL-232R-3V3.htm> >>>> >>>> On the Arduino, the RTS pin is tied into the reset circuitry so that >>>> the board can be reset (and serial downloaded to) from the host. >>>> >>>> Having the 4 pin layout which is compatible with the robostix also >>>> makes sense. I just wanted to throw out the Arduino thing since it's >>>> quite popular. >>> Thanks for pointing out the Arduino connector; I'd been hunting around >>> to see if there was such a standard earlier today and hadn't found >>> anything. >>> Is there a strong motivation for including the CTS and RTS lines? I >>> don't recall using them before so I found it hard to justify extra >>> pins but perhaps this is more a reflection on my inexperience than on >>> the utility of these pins. >> >> Being able to reset the microcontroller through the download interface >> is nice. It means that the SW can do the reset and send the >> appropriate bytes with appropriate timings, rather than relying on a >> particular sequence of events by the user. >> >> Although looking at the protocol, it seems pretty easy to just start >> the host side program and then hit reset on the micro. So I think you >> could eliminate the extra lines if you need the space. >> >> It would be nice, especially in standalone mode to be able to connect >> up the FTDI chip normally used for the overo console to the micro, >> perhaps using some switches, or DNI resistors. >> >> -- >> Dave Hylands >> Shuswap, BC, Canada >> http://www.DaveHylands.com/ >> >> ------------------------------------------------------------------------------ >> >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > > ------------------------------------------------------------------------------ > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > ----- Just a beginner trying to learn his way around. -- View this message in context: http://old.nabble.com/Robostix-for-Overo-tp28600551p28897886.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Nathaniel D. <de...@gm...> - 2010-06-16 02:41:39
|
Can you please detail a bit more about what the board does? I do not have Eagle to view the boards with. Thanks On Jun 15, 2010, at 7:39 PM, Ash Charles wrote: > Hi, > > A preliminary schematic (http://www.gumstix.net/other/B30019.sch) and > board design (http://www.gumstix.net/other/B30019.brd) for this > Overo-robostix board are available in Eagle format. As before, we > welcome your feedback---it is really helpful to know what features are > useful for users. > > Hope you like it :). > > -Ash > > On Sat, May 22, 2010 at 8:56 AM, Dave Hylands <dhy...@gm...> > wrote: >> Hi Ash, >> >> On Sat, May 22, 2010 at 12:40 AM, Ash Charles >> <ash...@gm...> wrote: >>> On Fri, May 21, 2010 at 6:40 PM, Dave Hylands <dhy...@gm...> >>> wrote: >>>> Hi Ash, >>>> >>>> On Fri, May 21, 2010 at 5:01 PM, Ash Charles <as...@gu...> >>>> wrote: >>>>> Afternoon, >>>>> >>>>> We've looked through the pin-muxing for this board and we >>>>> propose the >>>>> following 3 by 8 pin right-angle 0.1"pitch male headers: >>>>> >>>>> =====HEADER #1===== >>>>> PWM0 PWM1 PWM2 PWM3 PWM4 PWM5 PWM6 PWM7 >>>>> Vbat Vbat Vbat Vbat Vbat Vbat Vbat >>>>> Vbat >>>>> GND GND GND GND GND GND GND GND >>>> >>>> Hopefully, these will be Vmotor, which is jumpered to Vbat. >>> To make sure I understand what you meant in your previous post, the >>> jumper on the Robostix allowed people to use either a battery or a >>> wall wart to supply power to the board? >>> For the new board, the 'Vbat' signal (definitely a misnomer on my >>> part) would be the V+ line taken directly from the power source be >>> it >>> a wall wart or a battery. >> >> I guess by battery you really mean a dedicated 2-pin power connector. >> >>>> How will the luminary micro be programmed? Will a JTAG interface >>>> be available? >>> I hadn't included the JTAG interface; I think this requires an >>> additional four pins which is not impossible but board space would >>> start to get tight. One option would be putting contact pads for >>> JTAG...does this seem useful? >>> The device can be accessed via I2C0, UART0, or SSI0. >> >> I just wanted to make sure that you address how the device will be >> programmed. I see that it does indeed have a ROM based bootloader >> which can be programmed as you indicated, which somewhat alleviates >> the need for a JTAG. >> >> Although having the JTAG allows a debugger to be used, which I think >> will be important. >> >> If you put the pads somewhere that a 10-pin JTAG mini connector >> could be used >> <http://www.luminarymicro.com/products/mdl-ada2.html> This could be a >> surface mount connector. It looks like its a 2x5 0.050" header (see >> the schematics and BOM for this eval board: >> <http://www.luminarymicro.com/index.php?option=com_remository&func=download&id=983&chk=d1a772ed2075b69e938af114b279083b&Itemid=591 >> > >> >>>>> Secondly: is the arrangement of pins correct? >>>>> -- on Header #2, should the UARTS be four pins each (RX, V+, TX, >>>>> GND) with all three stacked on top of each other? e.g. >>>>> RX0 5V TX0 GND >>>>> RX1 5V TX1 GND >>>>> RX2 5V TX2 GND >>>> >>>> The Arduino stuff seems to have standardized on using: >>>> the same pinout as the FTDI USB-to-logic level serial connectors >>>> which is >>>> >>>> 1 - GND >>>> 2 - CTS >>>> 3 - VCC >>>> 4 - TXD >>>> 5 - RXD >>>> 6 - RTS >>>> >>>> <http://www.ftdichip.com/Products/EvaluationKits/TTL-232R-3V3.htm> >>>> >>>> On the Arduino, the RTS pin is tied into the reset circuitry so >>>> that >>>> the board can be reset (and serial downloaded to) from the host. >>>> >>>> Having the 4 pin layout which is compatible with the robostix also >>>> makes sense. I just wanted to throw out the Arduino thing since >>>> it's >>>> quite popular. >>> Thanks for pointing out the Arduino connector; I'd been hunting >>> around >>> to see if there was such a standard earlier today and hadn't found >>> anything. >>> Is there a strong motivation for including the CTS and RTS lines? I >>> don't recall using them before so I found it hard to justify extra >>> pins but perhaps this is more a reflection on my inexperience than >>> on >>> the utility of these pins. >> >> Being able to reset the microcontroller through the download >> interface >> is nice. It means that the SW can do the reset and send the >> appropriate bytes with appropriate timings, rather than relying on a >> particular sequence of events by the user. >> >> Although looking at the protocol, it seems pretty easy to just start >> the host side program and then hit reset on the micro. So I think you >> could eliminate the extra lines if you need the space. >> >> It would be nice, especially in standalone mode to be able to connect >> up the FTDI chip normally used for the overo console to the micro, >> perhaps using some switches, or DNI resistors. >> >> -- >> Dave Hylands >> Shuswap, BC, Canada >> http://www.DaveHylands.com/ >> >> ------------------------------------------------------------------------------ >> >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > > ------------------------------------------------------------------------------ > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Ash C. <as...@gu...> - 2010-06-16 07:47:56
|
Hi Nathaniel, I've added in a PDF version of the schematic and board layout here: www.gumstix.net/other/ Looking further up this thread should give a more complete idea of the discussions that went on in selecting the board features: http://old.nabble.com/Robostix-for-Overo-td28600551.html In brief: -> Cortex M3 micro -> GPIOs, PWMs, ADCs, CAN bus, SPI bus , I2C bus, and UARTs breakout -> 3-axis Accel, Magnetometer, and gyro (for now, the gyro part is not available for purchase) -> powered USB hub HTH, -Ash On Tue, Jun 15, 2010 at 7:41 PM, Nathaniel Delp <de...@gm...> wrote: > Can you please detail a bit more about what the board does? > > I do not have Eagle to view the boards with. > > Thanks > > On Jun 15, 2010, at 7:39 PM, Ash Charles wrote: > >> Hi, >> >> A preliminary schematic (http://www.gumstix.net/other/B30019.sch) and >> board design (http://www.gumstix.net/other/B30019.brd) for this >> Overo-robostix board are available in Eagle format. As before, we >> welcome your feedback---it is really helpful to know what features are >> useful for users. >> >> Hope you like it :). >> >> -Ash >> >> On Sat, May 22, 2010 at 8:56 AM, Dave Hylands <dhy...@gm...> >> wrote: >>> Hi Ash, >>> >>> On Sat, May 22, 2010 at 12:40 AM, Ash Charles >>> <ash...@gm...> wrote: >>>> On Fri, May 21, 2010 at 6:40 PM, Dave Hylands <dhy...@gm...> >>>> wrote: >>>>> Hi Ash, >>>>> >>>>> On Fri, May 21, 2010 at 5:01 PM, Ash Charles <as...@gu...> >>>>> wrote: >>>>>> Afternoon, >>>>>> >>>>>> We've looked through the pin-muxing for this board and we >>>>>> propose the >>>>>> following 3 by 8 pin right-angle 0.1"pitch male headers: >>>>>> >>>>>> =====HEADER #1===== >>>>>> PWM0 PWM1 PWM2 PWM3 PWM4 PWM5 PWM6 PWM7 >>>>>> Vbat Vbat Vbat Vbat Vbat Vbat Vbat >>>>>> Vbat >>>>>> GND GND GND GND GND GND GND GND >>>>> >>>>> Hopefully, these will be Vmotor, which is jumpered to Vbat. >>>> To make sure I understand what you meant in your previous post, the >>>> jumper on the Robostix allowed people to use either a battery or a >>>> wall wart to supply power to the board? >>>> For the new board, the 'Vbat' signal (definitely a misnomer on my >>>> part) would be the V+ line taken directly from the power source be >>>> it >>>> a wall wart or a battery. >>> >>> I guess by battery you really mean a dedicated 2-pin power connector. >>> >>>>> How will the luminary micro be programmed? Will a JTAG interface >>>>> be available? >>>> I hadn't included the JTAG interface; I think this requires an >>>> additional four pins which is not impossible but board space would >>>> start to get tight. One option would be putting contact pads for >>>> JTAG...does this seem useful? >>>> The device can be accessed via I2C0, UART0, or SSI0. >>> >>> I just wanted to make sure that you address how the device will be >>> programmed. I see that it does indeed have a ROM based bootloader >>> which can be programmed as you indicated, which somewhat alleviates >>> the need for a JTAG. >>> >>> Although having the JTAG allows a debugger to be used, which I think >>> will be important. >>> >>> If you put the pads somewhere that a 10-pin JTAG mini connector >>> could be used >>> <http://www.luminarymicro.com/products/mdl-ada2.html> This could be a >>> surface mount connector. It looks like its a 2x5 0.050" header (see >>> the schematics and BOM for this eval board: >>> <http://www.luminarymicro.com/index.php?option=com_remository&func=download&id=983&chk=d1a772ed2075b69e938af114b279083b&Itemid=591 >>> > >>> >>>>>> Secondly: is the arrangement of pins correct? >>>>>> -- on Header #2, should the UARTS be four pins each (RX, V+, TX, >>>>>> GND) with all three stacked on top of each other? e.g. >>>>>> RX0 5V TX0 GND >>>>>> RX1 5V TX1 GND >>>>>> RX2 5V TX2 GND >>>>> >>>>> The Arduino stuff seems to have standardized on using: >>>>> the same pinout as the FTDI USB-to-logic level serial connectors >>>>> which is >>>>> >>>>> 1 - GND >>>>> 2 - CTS >>>>> 3 - VCC >>>>> 4 - TXD >>>>> 5 - RXD >>>>> 6 - RTS >>>>> >>>>> <http://www.ftdichip.com/Products/EvaluationKits/TTL-232R-3V3.htm> >>>>> >>>>> On the Arduino, the RTS pin is tied into the reset circuitry so >>>>> that >>>>> the board can be reset (and serial downloaded to) from the host. >>>>> >>>>> Having the 4 pin layout which is compatible with the robostix also >>>>> makes sense. I just wanted to throw out the Arduino thing since >>>>> it's >>>>> quite popular. >>>> Thanks for pointing out the Arduino connector; I'd been hunting >>>> around >>>> to see if there was such a standard earlier today and hadn't found >>>> anything. >>>> Is there a strong motivation for including the CTS and RTS lines? I >>>> don't recall using them before so I found it hard to justify extra >>>> pins but perhaps this is more a reflection on my inexperience than >>>> on >>>> the utility of these pins. >>> >>> Being able to reset the microcontroller through the download >>> interface >>> is nice. It means that the SW can do the reset and send the >>> appropriate bytes with appropriate timings, rather than relying on a >>> particular sequence of events by the user. >>> >>> Although looking at the protocol, it seems pretty easy to just start >>> the host side program and then hit reset on the micro. So I think you >>> could eliminate the extra lines if you need the space. >>> >>> It would be nice, especially in standalone mode to be able to connect >>> up the FTDI chip normally used for the overo console to the micro, >>> perhaps using some switches, or DNI resistors. >>> >>> -- >>> Dave Hylands >>> Shuswap, BC, Canada >>> http://www.DaveHylands.com/ >>> >>> ------------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> gumstix-users mailing list >>> gum...@li... >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>> >> >> ------------------------------------------------------------------------------ >> ThinkGeek and WIRED's GeekDad team up for the Ultimate >> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the >> lucky parental unit. See the prize list and enter to win: >> http://p.sf.net/sfu/thinkgeek-promo >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > ------------------------------------------------------------------------------ > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Ash C. <as...@gu...> - 2010-06-16 07:56:48
|
Hi, The gyro part is actually not yet released so I would be surprised if people were discussing it; even if the part is not exactly the same, could you point me to the forum? I had looked at the Invensense part as one of the few 3-axis digital gyros on the market but as yet weren't able to get appropriate pricing on the part. To keep the price down and the size requirements for the board reasonable, we elected not to add a GPS (and, by consquence, not a pressure sensor). I would have to double-check but I think the ADC on the micro. actually has temperature built-in although this is probably not super useful. Thanks for the feedback, -Ash On Tue, Jun 15, 2010 at 5:30 PM, vwyodapink <vwy...@gm...> wrote: > > What about adding a connector on the board for a GPS like the Ublock or EM406 > > Though I am sure not useful to everyone but a absolute pressure sensor with > temp would be nice. > > I have heard there are a bunch of vibration issues with the gyro you have > listed you are using, Invensense is making a vibration resistant gyro that > has been used in a few projects that I have seen and has had really great > results. I am by no means an expert at all, just remember reading a bunch > about those gyros on a different message board and they were ditched because > of horrible performance. > > > > Ash Charles-2 wrote: >> >> Hi, >> >> A preliminary schematic (http://www.gumstix.net/other/B30019.sch) and >> board design (http://www.gumstix.net/other/B30019.brd) for this >> Overo-robostix board are available in Eagle format. As before, we >> welcome your feedback---it is really helpful to know what features are >> useful for users. >> >> Hope you like it :). >> >> -Ash >> >> On Sat, May 22, 2010 at 8:56 AM, Dave Hylands <dhy...@gm...> wrote: >>> Hi Ash, >>> >>> On Sat, May 22, 2010 at 12:40 AM, Ash Charles <ash...@gm...> >>> wrote: >>>> On Fri, May 21, 2010 at 6:40 PM, Dave Hylands <dhy...@gm...> >>>> wrote: >>>>> Hi Ash, >>>>> >>>>> On Fri, May 21, 2010 at 5:01 PM, Ash Charles <as...@gu...> wrote: >>>>>> Afternoon, >>>>>> >>>>>> We've looked through the pin-muxing for this board and we propose the >>>>>> following 3 by 8 pin right-angle 0.1"pitch male headers: >>>>>> >>>>>> =====HEADER #1===== >>>>>> PWM0 PWM1 PWM2 PWM3 PWM4 PWM5 PWM6 PWM7 >>>>>> Vbat Vbat Vbat Vbat Vbat Vbat Vbat Vbat >>>>>> GND GND GND GND GND GND GND GND >>>>> >>>>> Hopefully, these will be Vmotor, which is jumpered to Vbat. >>>> To make sure I understand what you meant in your previous post, the >>>> jumper on the Robostix allowed people to use either a battery or a >>>> wall wart to supply power to the board? >>>> For the new board, the 'Vbat' signal (definitely a misnomer on my >>>> part) would be the V+ line taken directly from the power source be it >>>> a wall wart or a battery. >>> >>> I guess by battery you really mean a dedicated 2-pin power connector. >>> >>>>> How will the luminary micro be programmed? Will a JTAG interface be >>>>> available? >>>> I hadn't included the JTAG interface; I think this requires an >>>> additional four pins which is not impossible but board space would >>>> start to get tight. One option would be putting contact pads for >>>> JTAG...does this seem useful? >>>> The device can be accessed via I2C0, UART0, or SSI0. >>> >>> I just wanted to make sure that you address how the device will be >>> programmed. I see that it does indeed have a ROM based bootloader >>> which can be programmed as you indicated, which somewhat alleviates >>> the need for a JTAG. >>> >>> Although having the JTAG allows a debugger to be used, which I think >>> will be important. >>> >>> If you put the pads somewhere that a 10-pin JTAG mini connector could be >>> used >>> <http://www.luminarymicro.com/products/mdl-ada2.html> This could be a >>> surface mount connector. It looks like its a 2x5 0.050" header (see >>> the schematics and BOM for this eval board: >>> <http://www.luminarymicro.com/index.php?option=com_remository&func=download&id=983&chk=d1a772ed2075b69e938af114b279083b&Itemid=591> >>> >>>>>> Secondly: is the arrangement of pins correct? >>>>>> -- on Header #2, should the UARTS be four pins each (RX, V+, TX, >>>>>> GND) with all three stacked on top of each other? e.g. >>>>>> RX0 5V TX0 GND >>>>>> RX1 5V TX1 GND >>>>>> RX2 5V TX2 GND >>>>> >>>>> The Arduino stuff seems to have standardized on using: >>>>> the same pinout as the FTDI USB-to-logic level serial connectors which >>>>> is >>>>> >>>>> 1 - GND >>>>> 2 - CTS >>>>> 3 - VCC >>>>> 4 - TXD >>>>> 5 - RXD >>>>> 6 - RTS >>>>> >>>>> <http://www.ftdichip.com/Products/EvaluationKits/TTL-232R-3V3.htm> >>>>> >>>>> On the Arduino, the RTS pin is tied into the reset circuitry so that >>>>> the board can be reset (and serial downloaded to) from the host. >>>>> >>>>> Having the 4 pin layout which is compatible with the robostix also >>>>> makes sense. I just wanted to throw out the Arduino thing since it's >>>>> quite popular. >>>> Thanks for pointing out the Arduino connector; I'd been hunting around >>>> to see if there was such a standard earlier today and hadn't found >>>> anything. >>>> Is there a strong motivation for including the CTS and RTS lines? I >>>> don't recall using them before so I found it hard to justify extra >>>> pins but perhaps this is more a reflection on my inexperience than on >>>> the utility of these pins. >>> >>> Being able to reset the microcontroller through the download interface >>> is nice. It means that the SW can do the reset and send the >>> appropriate bytes with appropriate timings, rather than relying on a >>> particular sequence of events by the user. >>> >>> Although looking at the protocol, it seems pretty easy to just start >>> the host side program and then hit reset on the micro. So I think you >>> could eliminate the extra lines if you need the space. >>> >>> It would be nice, especially in standalone mode to be able to connect >>> up the FTDI chip normally used for the overo console to the micro, >>> perhaps using some switches, or DNI resistors. >>> >>> -- >>> Dave Hylands >>> Shuswap, BC, Canada >>> http://www.DaveHylands.com/ >>> >>> ------------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> gumstix-users mailing list >>> gum...@li... >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>> >> >> ------------------------------------------------------------------------------ >> ThinkGeek and WIRED's GeekDad team up for the Ultimate >> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the >> lucky parental unit. See the prize list and enter to win: >> http://p.sf.net/sfu/thinkgeek-promo >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> > > > ----- > Just a beginner trying to learn his way around. > -- > View this message in context: http://old.nabble.com/Robostix-for-Overo-tp28600551p28897886.html > Sent from the Gumstix mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: vwyodapink <vwy...@gm...> - 2010-06-16 08:25:05
|
I wasnt actually meaning having the GPS as part of the board but actually putting a plus like this: http://www.sparkfun.com/commerce/product_info.php?products_id=579 So people who want a GPS can easily add one and not have it be USB based. I would much rather see the GPS as not having to go through a hub or similar. Plus the plugs are tiny. I understand about the pressure sensor, I have been trying to get a breakout board with an absolute pressure sensor with temp to work with my fire. Though the bosh absolute pressure sensor is another very small foot print. You were correct about the gyro that was my mistake and I did not read the model number correctly. http://forums.parallax.com/forums/default.aspx?m=436063&f=25&p=6 Is where I thought I saw that just in case you want to see it. But this was the gyro I was thinking of that had the issues LPR530AL, sorry about that I think its a great board though from what I can tell its some really great work, is there a ballpark price yet or possible release on it? Ash Charles-2 wrote: > > Hi, > > The gyro part is actually not yet released so I would be surprised if > people were discussing it; even if the part is not exactly the same, > could you point me to the forum? > > I had looked at the Invensense part as one of the few 3-axis digital > gyros on the market but as yet weren't able to get appropriate pricing > on the part. > > To keep the price down and the size requirements for the board > reasonable, we elected not to add a GPS (and, by consquence, not a > pressure sensor). I would have to double-check but I think the ADC on > the micro. actually has temperature built-in although this is probably > not super useful. > > Thanks for the feedback, > > -Ash > > On Tue, Jun 15, 2010 at 5:30 PM, vwyodapink <vwy...@gm...> wrote: >> >> What about adding a connector on the board for a GPS like the Ublock or >> EM406 >> >> Though I am sure not useful to everyone but a absolute pressure sensor >> with >> temp would be nice. >> >> I have heard there are a bunch of vibration issues with the gyro you have >> listed you are using, Invensense is making a vibration resistant gyro >> that >> has been used in a few projects that I have seen and has had really great >> results. I am by no means an expert at all, just remember reading a bunch >> about those gyros on a different message board and they were ditched >> because >> of horrible performance. >> >> >> >> Ash Charles-2 wrote: >>> >>> Hi, >>> >>> A preliminary schematic (http://www.gumstix.net/other/B30019.sch) and >>> board design (http://www.gumstix.net/other/B30019.brd) for this >>> Overo-robostix board are available in Eagle format. As before, we >>> welcome your feedback---it is really helpful to know what features are >>> useful for users. >>> >>> Hope you like it :). >>> >>> -Ash >>> >>> On Sat, May 22, 2010 at 8:56 AM, Dave Hylands <dhy...@gm...> >>> wrote: >>>> Hi Ash, >>>> >>>> On Sat, May 22, 2010 at 12:40 AM, Ash Charles <ash...@gm...> >>>> wrote: >>>>> On Fri, May 21, 2010 at 6:40 PM, Dave Hylands <dhy...@gm...> >>>>> wrote: >>>>>> Hi Ash, >>>>>> >>>>>> On Fri, May 21, 2010 at 5:01 PM, Ash Charles <as...@gu...> wrote: >>>>>>> Afternoon, >>>>>>> >>>>>>> We've looked through the pin-muxing for this board and we propose >>>>>>> the >>>>>>> following 3 by 8 pin right-angle 0.1"pitch male headers: >>>>>>> >>>>>>> =====HEADER #1===== >>>>>>> PWM0 PWM1 PWM2 PWM3 PWM4 PWM5 PWM6 PWM7 >>>>>>> Vbat Vbat Vbat Vbat Vbat Vbat Vbat Vbat >>>>>>> GND GND GND GND GND GND GND GND >>>>>> >>>>>> Hopefully, these will be Vmotor, which is jumpered to Vbat. >>>>> To make sure I understand what you meant in your previous post, the >>>>> jumper on the Robostix allowed people to use either a battery or a >>>>> wall wart to supply power to the board? >>>>> For the new board, the 'Vbat' signal (definitely a misnomer on my >>>>> part) would be the V+ line taken directly from the power source be it >>>>> a wall wart or a battery. >>>> >>>> I guess by battery you really mean a dedicated 2-pin power connector. >>>> >>>>>> How will the luminary micro be programmed? Will a JTAG interface be >>>>>> available? >>>>> I hadn't included the JTAG interface; I think this requires an >>>>> additional four pins which is not impossible but board space would >>>>> start to get tight. One option would be putting contact pads for >>>>> JTAG...does this seem useful? >>>>> The device can be accessed via I2C0, UART0, or SSI0. >>>> >>>> I just wanted to make sure that you address how the device will be >>>> programmed. I see that it does indeed have a ROM based bootloader >>>> which can be programmed as you indicated, which somewhat alleviates >>>> the need for a JTAG. >>>> >>>> Although having the JTAG allows a debugger to be used, which I think >>>> will be important. >>>> >>>> If you put the pads somewhere that a 10-pin JTAG mini connector could >>>> be >>>> used >>>> <http://www.luminarymicro.com/products/mdl-ada2.html> This could be a >>>> surface mount connector. It looks like its a 2x5 0.050" header (see >>>> the schematics and BOM for this eval board: >>>> <http://www.luminarymicro.com/index.php?option=com_remository&func=download&id=983&chk=d1a772ed2075b69e938af114b279083b&Itemid=591> >>>> >>>>>>> Secondly: is the arrangement of pins correct? >>>>>>> -- on Header #2, should the UARTS be four pins each (RX, V+, TX, >>>>>>> GND) with all three stacked on top of each other? e.g. >>>>>>> RX0 5V TX0 GND >>>>>>> RX1 5V TX1 GND >>>>>>> RX2 5V TX2 GND >>>>>> >>>>>> The Arduino stuff seems to have standardized on using: >>>>>> the same pinout as the FTDI USB-to-logic level serial connectors >>>>>> which >>>>>> is >>>>>> >>>>>> 1 - GND >>>>>> 2 - CTS >>>>>> 3 - VCC >>>>>> 4 - TXD >>>>>> 5 - RXD >>>>>> 6 - RTS >>>>>> >>>>>> <http://www.ftdichip.com/Products/EvaluationKits/TTL-232R-3V3.htm> >>>>>> >>>>>> On the Arduino, the RTS pin is tied into the reset circuitry so that >>>>>> the board can be reset (and serial downloaded to) from the host. >>>>>> >>>>>> Having the 4 pin layout which is compatible with the robostix also >>>>>> makes sense. I just wanted to throw out the Arduino thing since it's >>>>>> quite popular. >>>>> Thanks for pointing out the Arduino connector; I'd been hunting around >>>>> to see if there was such a standard earlier today and hadn't found >>>>> anything. >>>>> Is there a strong motivation for including the CTS and RTS lines? I >>>>> don't recall using them before so I found it hard to justify extra >>>>> pins but perhaps this is more a reflection on my inexperience than on >>>>> the utility of these pins. >>>> >>>> Being able to reset the microcontroller through the download interface >>>> is nice. It means that the SW can do the reset and send the >>>> appropriate bytes with appropriate timings, rather than relying on a >>>> particular sequence of events by the user. >>>> >>>> Although looking at the protocol, it seems pretty easy to just start >>>> the host side program and then hit reset on the micro. So I think you >>>> could eliminate the extra lines if you need the space. >>>> >>>> It would be nice, especially in standalone mode to be able to connect >>>> up the FTDI chip normally used for the overo console to the micro, >>>> perhaps using some switches, or DNI resistors. >>>> >>>> -- >>>> Dave Hylands >>>> Shuswap, BC, Canada >>>> http://www.DaveHylands.com/ >>>> >>>> ------------------------------------------------------------------------------ >>>> >>>> _______________________________________________ >>>> gumstix-users mailing list >>>> gum...@li... >>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>> >>> >>> ------------------------------------------------------------------------------ >>> ThinkGeek and WIRED's GeekDad team up for the Ultimate >>> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the >>> lucky parental unit. See the prize list and enter to win: >>> http://p.sf.net/sfu/thinkgeek-promo >>> _______________________________________________ >>> gumstix-users mailing list >>> gum...@li... >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>> >>> >> >> >> ----- >> Just a beginner trying to learn his way around. >> -- >> View this message in context: >> http://old.nabble.com/Robostix-for-Overo-tp28600551p28897886.html >> Sent from the Gumstix mailing list archive at Nabble.com. >> >> >> ------------------------------------------------------------------------------ >> ThinkGeek and WIRED's GeekDad team up for the Ultimate >> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the >> lucky parental unit. See the prize list and enter to win: >> http://p.sf.net/sfu/thinkgeek-promo >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > > ------------------------------------------------------------------------------ > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > ----- Just a beginner trying to learn his way around. -- View this message in context: http://old.nabble.com/Robostix-for-Overo-tp28600551p28900186.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Ash C. <as...@gu...> - 2010-06-17 16:08:20
|
Hi, Is there a major advantage not to use a USB-based GPS dongle or a UART GPS? I can't confirm pricing information yet; we are working to get these details figured out. Most likely, we will have several different population options (and therefore prices) depending on users' needs. Thanks for the forum link. -Ash On Wed, Jun 16, 2010 at 1:24 AM, vwyodapink <vwy...@gm...> wrote: > > I wasnt actually meaning having the GPS as part of the board but actually > putting a plus like this: > http://www.sparkfun.com/commerce/product_info.php?products_id=579 > So people who want a GPS can easily add one and not have it be USB based. I > would much rather see the GPS as not having to go through a hub or similar. > Plus the plugs are tiny. > > I understand about the pressure sensor, I have been trying to get a breakout > board with an absolute pressure sensor with temp to work with my fire. > Though the bosh absolute pressure sensor is another very small foot print. > > You were correct about the gyro that was my mistake and I did not read the > model number correctly. > http://forums.parallax.com/forums/default.aspx?m=436063&f=25&p=6 Is where I > thought I saw that just in case you want to see it. But this was the gyro I > was thinking of that had the issues LPR530AL, sorry about that > > I think its a great board though from what I can tell its some really great > work, is there a ballpark price yet or possible release on it? > > > > Ash Charles-2 wrote: >> >> Hi, >> >> The gyro part is actually not yet released so I would be surprised if >> people were discussing it; even if the part is not exactly the same, >> could you point me to the forum? >> >> I had looked at the Invensense part as one of the few 3-axis digital >> gyros on the market but as yet weren't able to get appropriate pricing >> on the part. >> >> To keep the price down and the size requirements for the board >> reasonable, we elected not to add a GPS (and, by consquence, not a >> pressure sensor). I would have to double-check but I think the ADC on >> the micro. actually has temperature built-in although this is probably >> not super useful. >> >> Thanks for the feedback, >> >> -Ash >> >> On Tue, Jun 15, 2010 at 5:30 PM, vwyodapink <vwy...@gm...> wrote: >>> >>> What about adding a connector on the board for a GPS like the Ublock or >>> EM406 >>> >>> Though I am sure not useful to everyone but a absolute pressure sensor >>> with >>> temp would be nice. >>> >>> I have heard there are a bunch of vibration issues with the gyro you have >>> listed you are using, Invensense is making a vibration resistant gyro >>> that >>> has been used in a few projects that I have seen and has had really great >>> results. I am by no means an expert at all, just remember reading a bunch >>> about those gyros on a different message board and they were ditched >>> because >>> of horrible performance. >>> >>> >>> >>> Ash Charles-2 wrote: >>>> >>>> Hi, >>>> >>>> A preliminary schematic (http://www.gumstix.net/other/B30019.sch) and >>>> board design (http://www.gumstix.net/other/B30019.brd) for this >>>> Overo-robostix board are available in Eagle format. As before, we >>>> welcome your feedback---it is really helpful to know what features are >>>> useful for users. >>>> >>>> Hope you like it :). >>>> >>>> -Ash >>>> >>>> On Sat, May 22, 2010 at 8:56 AM, Dave Hylands <dhy...@gm...> >>>> wrote: >>>>> Hi Ash, >>>>> >>>>> On Sat, May 22, 2010 at 12:40 AM, Ash Charles <ash...@gm...> >>>>> wrote: >>>>>> On Fri, May 21, 2010 at 6:40 PM, Dave Hylands <dhy...@gm...> >>>>>> wrote: >>>>>>> Hi Ash, >>>>>>> >>>>>>> On Fri, May 21, 2010 at 5:01 PM, Ash Charles <as...@gu...> wrote: >>>>>>>> Afternoon, >>>>>>>> >>>>>>>> We've looked through the pin-muxing for this board and we propose >>>>>>>> the >>>>>>>> following 3 by 8 pin right-angle 0.1"pitch male headers: >>>>>>>> >>>>>>>> =====HEADER #1===== >>>>>>>> PWM0 PWM1 PWM2 PWM3 PWM4 PWM5 PWM6 PWM7 >>>>>>>> Vbat Vbat Vbat Vbat Vbat Vbat Vbat Vbat >>>>>>>> GND GND GND GND GND GND GND GND >>>>>>> >>>>>>> Hopefully, these will be Vmotor, which is jumpered to Vbat. >>>>>> To make sure I understand what you meant in your previous post, the >>>>>> jumper on the Robostix allowed people to use either a battery or a >>>>>> wall wart to supply power to the board? >>>>>> For the new board, the 'Vbat' signal (definitely a misnomer on my >>>>>> part) would be the V+ line taken directly from the power source be it >>>>>> a wall wart or a battery. >>>>> >>>>> I guess by battery you really mean a dedicated 2-pin power connector. >>>>> >>>>>>> How will the luminary micro be programmed? Will a JTAG interface be >>>>>>> available? >>>>>> I hadn't included the JTAG interface; I think this requires an >>>>>> additional four pins which is not impossible but board space would >>>>>> start to get tight. One option would be putting contact pads for >>>>>> JTAG...does this seem useful? >>>>>> The device can be accessed via I2C0, UART0, or SSI0. >>>>> >>>>> I just wanted to make sure that you address how the device will be >>>>> programmed. I see that it does indeed have a ROM based bootloader >>>>> which can be programmed as you indicated, which somewhat alleviates >>>>> the need for a JTAG. >>>>> >>>>> Although having the JTAG allows a debugger to be used, which I think >>>>> will be important. >>>>> >>>>> If you put the pads somewhere that a 10-pin JTAG mini connector could >>>>> be >>>>> used >>>>> <http://www.luminarymicro.com/products/mdl-ada2.html> This could be a >>>>> surface mount connector. It looks like its a 2x5 0.050" header (see >>>>> the schematics and BOM for this eval board: >>>>> <http://www.luminarymicro.com/index.php?option=com_remository&func=download&id=983&chk=d1a772ed2075b69e938af114b279083b&Itemid=591> >>>>> >>>>>>>> Secondly: is the arrangement of pins correct? >>>>>>>> -- on Header #2, should the UARTS be four pins each (RX, V+, TX, >>>>>>>> GND) with all three stacked on top of each other? e.g. >>>>>>>> RX0 5V TX0 GND >>>>>>>> RX1 5V TX1 GND >>>>>>>> RX2 5V TX2 GND >>>>>>> >>>>>>> The Arduino stuff seems to have standardized on using: >>>>>>> the same pinout as the FTDI USB-to-logic level serial connectors >>>>>>> which >>>>>>> is >>>>>>> >>>>>>> 1 - GND >>>>>>> 2 - CTS >>>>>>> 3 - VCC >>>>>>> 4 - TXD >>>>>>> 5 - RXD >>>>>>> 6 - RTS >>>>>>> >>>>>>> <http://www.ftdichip.com/Products/EvaluationKits/TTL-232R-3V3.htm> >>>>>>> >>>>>>> On the Arduino, the RTS pin is tied into the reset circuitry so that >>>>>>> the board can be reset (and serial downloaded to) from the host. >>>>>>> >>>>>>> Having the 4 pin layout which is compatible with the robostix also >>>>>>> makes sense. I just wanted to throw out the Arduino thing since it's >>>>>>> quite popular. >>>>>> Thanks for pointing out the Arduino connector; I'd been hunting around >>>>>> to see if there was such a standard earlier today and hadn't found >>>>>> anything. >>>>>> Is there a strong motivation for including the CTS and RTS lines? I >>>>>> don't recall using them before so I found it hard to justify extra >>>>>> pins but perhaps this is more a reflection on my inexperience than on >>>>>> the utility of these pins. >>>>> >>>>> Being able to reset the microcontroller through the download interface >>>>> is nice. It means that the SW can do the reset and send the >>>>> appropriate bytes with appropriate timings, rather than relying on a >>>>> particular sequence of events by the user. >>>>> >>>>> Although looking at the protocol, it seems pretty easy to just start >>>>> the host side program and then hit reset on the micro. So I think you >>>>> could eliminate the extra lines if you need the space. >>>>> >>>>> It would be nice, especially in standalone mode to be able to connect >>>>> up the FTDI chip normally used for the overo console to the micro, >>>>> perhaps using some switches, or DNI resistors. >>>>> >>>>> -- >>>>> Dave Hylands >>>>> Shuswap, BC, Canada >>>>> http://www.DaveHylands.com/ >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> >>>>> _______________________________________________ >>>>> gumstix-users mailing list >>>>> gum...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> ThinkGeek and WIRED's GeekDad team up for the Ultimate >>>> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the >>>> lucky parental unit. See the prize list and enter to win: >>>> http://p.sf.net/sfu/thinkgeek-promo >>>> _______________________________________________ >>>> gumstix-users mailing list >>>> gum...@li... >>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>> >>>> >>> >>> >>> ----- >>> Just a beginner trying to learn his way around. >>> -- >>> View this message in context: >>> http://old.nabble.com/Robostix-for-Overo-tp28600551p28897886.html >>> Sent from the Gumstix mailing list archive at Nabble.com. >>> >>> >>> ------------------------------------------------------------------------------ >>> ThinkGeek and WIRED's GeekDad team up for the Ultimate >>> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the >>> lucky parental unit. See the prize list and enter to win: >>> http://p.sf.net/sfu/thinkgeek-promo >>> _______________________________________________ >>> gumstix-users mailing list >>> gum...@li... >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>> >> >> ------------------------------------------------------------------------------ >> ThinkGeek and WIRED's GeekDad team up for the Ultimate >> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the >> lucky parental unit. See the prize list and enter to win: >> http://p.sf.net/sfu/thinkgeek-promo >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> > > > ----- > Just a beginner trying to learn his way around. > -- > View this message in context: http://old.nabble.com/Robostix-for-Overo-tp28600551p28900186.html > Sent from the Gumstix mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: vwyodapink <vwy...@gm...> - 2010-06-17 18:08:32
|
The major advantage would be weight savings as you dont have another huge USB plug which also in turn saves you a spot as well. I know lots of people use the style of connector I showed you its a common way to run GPS for UAV's. Functionality wise there is not real difference, though I showed some people on my UAV forum and they were stoked to see something like this coming out but. as it sits now would still take more addons to be fully useful for myself others into similar projects to where it would be worth ditching whats already being used. Which I would like to do as I think this way would be much cleaner if everything was all on one board. The way I use things now is the Overo is attached to the summit and by i2c connection I connect either the UAVDev Board, which is very similar to your robostix, and I have also another one setup by i2c using a Ardupilot Mega and ArduIMU Mega. The arduimu mega is by far the best IMU AHRS I have tried to date, granted I have only tried the 6d0f from sparkfun, standard ardu IMU+, and the UAVDevBoard. I was wondering about the motor controlers you have on there is that similar to using an electronic speed controller? If so what kind of amps can it handle? Or is to control small and not very powerful elec engines? Sorry if that was stated or a really basic question. Here are a list of links just in case you would like to see the things I am talking about if your not familiar with them. http://www.sparkfun.com/commerce/product_info.php?products_id=9038 -- UAV Dev Board http://store.diydrones.com/product_p/br-0012-01.htm -- ArduIMU Mega Hope this helps you out some, Thanks again for the hard work you have done so far. If I can be of any more use or put more links to things let me know :) Jeremy If Ash Charles-2 wrote: > > Hi, > > Is there a major advantage not to use a USB-based GPS dongle or a UART > GPS? > > I can't confirm pricing information yet; we are working to get these > details figured out. Most likely, we will have several different > population options (and therefore prices) depending on users' needs. > > Thanks for the forum link. > > -Ash > > On Wed, Jun 16, 2010 at 1:24 AM, vwyodapink <vwy...@gm...> wrote: >> >> I wasnt actually meaning having the GPS as part of the board but actually >> putting a plus like this: >> http://www.sparkfun.com/commerce/product_info.php?products_id=579 >> So people who want a GPS can easily add one and not have it be USB based. >> I >> would much rather see the GPS as not having to go through a hub or >> similar. >> Plus the plugs are tiny. >> >> I understand about the pressure sensor, I have been trying to get a >> breakout >> board with an absolute pressure sensor with temp to work with my fire. >> Though the bosh absolute pressure sensor is another very small foot >> print. >> >> You were correct about the gyro that was my mistake and I did not read >> the >> model number correctly. >> http://forums.parallax.com/forums/default.aspx?m=436063&f=25&p=6 Is where >> I >> thought I saw that just in case you want to see it. But this was the gyro >> I >> was thinking of that had the issues LPR530AL, sorry about that >> >> I think its a great board though from what I can tell its some really >> great >> work, is there a ballpark price yet or possible release on it? >> >> >> >> Ash Charles-2 wrote: >>> >>> Hi, >>> >>> The gyro part is actually not yet released so I would be surprised if >>> people were discussing it; even if the part is not exactly the same, >>> could you point me to the forum? >>> >>> I had looked at the Invensense part as one of the few 3-axis digital >>> gyros on the market but as yet weren't able to get appropriate pricing >>> on the part. >>> >>> To keep the price down and the size requirements for the board >>> reasonable, we elected not to add a GPS (and, by consquence, not a >>> pressure sensor). I would have to double-check but I think the ADC on >>> the micro. actually has temperature built-in although this is probably >>> not super useful. >>> >>> Thanks for the feedback, >>> >>> -Ash >>> >>> On Tue, Jun 15, 2010 at 5:30 PM, vwyodapink <vwy...@gm...> >>> wrote: >>>> >>>> What about adding a connector on the board for a GPS like the Ublock or >>>> EM406 >>>> >>>> Though I am sure not useful to everyone but a absolute pressure sensor >>>> with >>>> temp would be nice. >>>> >>>> I have heard there are a bunch of vibration issues with the gyro you >>>> have >>>> listed you are using, Invensense is making a vibration resistant gyro >>>> that >>>> has been used in a few projects that I have seen and has had really >>>> great >>>> results. I am by no means an expert at all, just remember reading a >>>> bunch >>>> about those gyros on a different message board and they were ditched >>>> because >>>> of horrible performance. >>>> >>>> >>>> >>>> Ash Charles-2 wrote: >>>>> >>>>> Hi, >>>>> >>>>> A preliminary schematic (http://www.gumstix.net/other/B30019.sch) and >>>>> board design (http://www.gumstix.net/other/B30019.brd) for this >>>>> Overo-robostix board are available in Eagle format. As before, we >>>>> welcome your feedback---it is really helpful to know what features are >>>>> useful for users. >>>>> >>>>> Hope you like it :). >>>>> >>>>> -Ash >>>>> >>>>> On Sat, May 22, 2010 at 8:56 AM, Dave Hylands <dhy...@gm...> >>>>> wrote: >>>>>> Hi Ash, >>>>>> >>>>>> On Sat, May 22, 2010 at 12:40 AM, Ash Charles <ash...@gm...> >>>>>> wrote: >>>>>>> On Fri, May 21, 2010 at 6:40 PM, Dave Hylands <dhy...@gm...> >>>>>>> wrote: >>>>>>>> Hi Ash, >>>>>>>> >>>>>>>> On Fri, May 21, 2010 at 5:01 PM, Ash Charles <as...@gu...> >>>>>>>> wrote: >>>>>>>>> Afternoon, >>>>>>>>> >>>>>>>>> We've looked through the pin-muxing for this board and we propose >>>>>>>>> the >>>>>>>>> following 3 by 8 pin right-angle 0.1"pitch male headers: >>>>>>>>> >>>>>>>>> =====HEADER #1===== >>>>>>>>> PWM0 PWM1 PWM2 PWM3 PWM4 PWM5 PWM6 PWM7 >>>>>>>>> Vbat Vbat Vbat Vbat Vbat Vbat Vbat >>>>>>>>> Vbat >>>>>>>>> GND GND GND GND GND GND GND GND >>>>>>>> >>>>>>>> Hopefully, these will be Vmotor, which is jumpered to Vbat. >>>>>>> To make sure I understand what you meant in your previous post, the >>>>>>> jumper on the Robostix allowed people to use either a battery or a >>>>>>> wall wart to supply power to the board? >>>>>>> For the new board, the 'Vbat' signal (definitely a misnomer on my >>>>>>> part) would be the V+ line taken directly from the power source be >>>>>>> it >>>>>>> a wall wart or a battery. >>>>>> >>>>>> I guess by battery you really mean a dedicated 2-pin power connector. >>>>>> >>>>>>>> How will the luminary micro be programmed? Will a JTAG interface be >>>>>>>> available? >>>>>>> I hadn't included the JTAG interface; I think this requires an >>>>>>> additional four pins which is not impossible but board space would >>>>>>> start to get tight. One option would be putting contact pads for >>>>>>> JTAG...does this seem useful? >>>>>>> The device can be accessed via I2C0, UART0, or SSI0. >>>>>> >>>>>> I just wanted to make sure that you address how the device will be >>>>>> programmed. I see that it does indeed have a ROM based bootloader >>>>>> which can be programmed as you indicated, which somewhat alleviates >>>>>> the need for a JTAG. >>>>>> >>>>>> Although having the JTAG allows a debugger to be used, which I think >>>>>> will be important. >>>>>> >>>>>> If you put the pads somewhere that a 10-pin JTAG mini connector could >>>>>> be >>>>>> used >>>>>> <http://www.luminarymicro.com/products/mdl-ada2.html> This could be a >>>>>> surface mount connector. It looks like its a 2x5 0.050" header (see >>>>>> the schematics and BOM for this eval board: >>>>>> <http://www.luminarymicro.com/index.php?option=com_remository&func=download&id=983&chk=d1a772ed2075b69e938af114b279083b&Itemid=591> >>>>>> >>>>>>>>> Secondly: is the arrangement of pins correct? >>>>>>>>> -- on Header #2, should the UARTS be four pins each (RX, V+, TX, >>>>>>>>> GND) with all three stacked on top of each other? e.g. >>>>>>>>> RX0 5V TX0 GND >>>>>>>>> RX1 5V TX1 GND >>>>>>>>> RX2 5V TX2 GND >>>>>>>> >>>>>>>> The Arduino stuff seems to have standardized on using: >>>>>>>> the same pinout as the FTDI USB-to-logic level serial connectors >>>>>>>> which >>>>>>>> is >>>>>>>> >>>>>>>> 1 - GND >>>>>>>> 2 - CTS >>>>>>>> 3 - VCC >>>>>>>> 4 - TXD >>>>>>>> 5 - RXD >>>>>>>> 6 - RTS >>>>>>>> >>>>>>>> <http://www.ftdichip.com/Products/EvaluationKits/TTL-232R-3V3.htm> >>>>>>>> >>>>>>>> On the Arduino, the RTS pin is tied into the reset circuitry so >>>>>>>> that >>>>>>>> the board can be reset (and serial downloaded to) from the host. >>>>>>>> >>>>>>>> Having the 4 pin layout which is compatible with the robostix also >>>>>>>> makes sense. I just wanted to throw out the Arduino thing since >>>>>>>> it's >>>>>>>> quite popular. >>>>>>> Thanks for pointing out the Arduino connector; I'd been hunting >>>>>>> around >>>>>>> to see if there was such a standard earlier today and hadn't found >>>>>>> anything. >>>>>>> Is there a strong motivation for including the CTS and RTS lines? I >>>>>>> don't recall using them before so I found it hard to justify extra >>>>>>> pins but perhaps this is more a reflection on my inexperience than >>>>>>> on >>>>>>> the utility of these pins. >>>>>> >>>>>> Being able to reset the microcontroller through the download >>>>>> interface >>>>>> is nice. It means that the SW can do the reset and send the >>>>>> appropriate bytes with appropriate timings, rather than relying on a >>>>>> particular sequence of events by the user. >>>>>> >>>>>> Although looking at the protocol, it seems pretty easy to just start >>>>>> the host side program and then hit reset on the micro. So I think you >>>>>> could eliminate the extra lines if you need the space. >>>>>> >>>>>> It would be nice, especially in standalone mode to be able to connect >>>>>> up the FTDI chip normally used for the overo console to the micro, >>>>>> perhaps using some switches, or DNI resistors. >>>>>> >>>>>> -- >>>>>> Dave Hylands >>>>>> Shuswap, BC, Canada >>>>>> http://www.DaveHylands.com/ >>>>>> >>>>>> ------------------------------------------------------------------------------ >>>>>> >>>>>> _______________________________________________ >>>>>> gumstix-users mailing list >>>>>> gum...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> ThinkGeek and WIRED's GeekDad team up for the Ultimate >>>>> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the >>>>> lucky parental unit. See the prize list and enter to win: >>>>> http://p.sf.net/sfu/thinkgeek-promo >>>>> _______________________________________________ >>>>> gumstix-users mailing list >>>>> gum...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>>> >>>>> >>>> >>>> >>>> ----- >>>> Just a beginner trying to learn his way around. >>>> -- >>>> View this message in context: >>>> http://old.nabble.com/Robostix-for-Overo-tp28600551p28897886.html >>>> Sent from the Gumstix mailing list archive at Nabble.com. >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> ThinkGeek and WIRED's GeekDad team up for the Ultimate >>>> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the >>>> lucky parental unit. See the prize list and enter to win: >>>> http://p.sf.net/sfu/thinkgeek-promo >>>> _______________________________________________ >>>> gumstix-users mailing list >>>> gum...@li... >>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>> >>> >>> ------------------------------------------------------------------------------ >>> ThinkGeek and WIRED's GeekDad team up for the Ultimate >>> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the >>> lucky parental unit. See the prize list and enter to win: >>> http://p.sf.net/sfu/thinkgeek-promo >>> _______________________________________________ >>> gumstix-users mailing list >>> gum...@li... >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>> >>> >> >> >> ----- >> Just a beginner trying to learn his way around. >> -- >> View this message in context: >> http://old.nabble.com/Robostix-for-Overo-tp28600551p28900186.html >> Sent from the Gumstix mailing list archive at Nabble.com. >> >> >> ------------------------------------------------------------------------------ >> ThinkGeek and WIRED's GeekDad team up for the Ultimate >> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the >> lucky parental unit. See the prize list and enter to win: >> http://p.sf.net/sfu/thinkgeek-promo >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > > ------------------------------------------------------------------------------ > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > ----- Just a beginner trying to learn his way around. -- View this message in context: http://old.nabble.com/Robostix-for-Overo-tp28600551p28917818.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: vwyodapink <vwy...@gm...> - 2010-06-19 17:50:15
|
Here is a link to the arduImu schematic and board http://docs.google.com/leaf?id=0ByI4WbhJsiyqODFiZmJmYjItMjg1Zi00NWU2LTljYzYtMDFjM2YxZWU0MWUx&hl=en http://docs.google.com/leaf?id=0ByI4WbhJsiyqODRkNTUwZWQtNTYwMC00MjA3LTg0YTUtMDc5NTg0M2YyMzRl&hl=en vwyodapink wrote: > > The major advantage would be weight savings as you dont have another huge > USB plug which also in turn saves you a spot as well. I know lots of > people use the style of connector I showed you its a common way to run GPS > for UAV's. Functionality wise there is not real difference, though I > showed some people on my UAV forum and they were stoked to see something > like this coming out but. as it sits now would still take more addons to > be fully useful for myself others into similar projects to where it would > be worth ditching whats already being used. Which I would like to do as I > think this way would be much cleaner if everything was all on one board. > > The way I use things now is the Overo is attached to the summit and by i2c > connection I connect either the UAVDev Board, which is very similar to > your robostix, and I have also another one setup by i2c using a Ardupilot > Mega and ArduIMU Mega. The arduimu mega is by far the best IMU AHRS I have > tried to date, granted I have only tried the 6d0f from sparkfun, standard > ardu IMU+, and the UAVDevBoard. > > I was wondering about the motor controlers you have on there is that > similar to using an electronic speed controller? If so what kind of amps > can it handle? Or is to control small and not very powerful elec engines? > Sorry if that was stated or a really basic question. > > Here are a list of links just in case you would like to see the things I > am talking about if your not familiar with them. > http://www.sparkfun.com/commerce/product_info.php?products_id=9038 -- UAV > Dev Board > http://store.diydrones.com/product_p/br-0012-01.htm -- ArduIMU Mega > > Hope this helps you out some, Thanks again for the hard work you have done > so far. If I can be of any more use or put more links to things let me > know :) > > Jeremy > > If > > Ash Charles-2 wrote: >> >> Hi, >> >> Is there a major advantage not to use a USB-based GPS dongle or a UART >> GPS? >> >> I can't confirm pricing information yet; we are working to get these >> details figured out. Most likely, we will have several different >> population options (and therefore prices) depending on users' needs. >> >> Thanks for the forum link. >> >> -Ash >> >> On Wed, Jun 16, 2010 at 1:24 AM, vwyodapink <vwy...@gm...> wrote: >>> >>> I wasnt actually meaning having the GPS as part of the board but >>> actually >>> putting a plus like this: >>> http://www.sparkfun.com/commerce/product_info.php?products_id=579 >>> So people who want a GPS can easily add one and not have it be USB >>> based. I >>> would much rather see the GPS as not having to go through a hub or >>> similar. >>> Plus the plugs are tiny. >>> >>> I understand about the pressure sensor, I have been trying to get a >>> breakout >>> board with an absolute pressure sensor with temp to work with my fire. >>> Though the bosh absolute pressure sensor is another very small foot >>> print. >>> >>> You were correct about the gyro that was my mistake and I did not read >>> the >>> model number correctly. >>> http://forums.parallax.com/forums/default.aspx?m=436063&f=25&p=6 Is >>> where I >>> thought I saw that just in case you want to see it. But this was the >>> gyro I >>> was thinking of that had the issues LPR530AL, sorry about that >>> >>> I think its a great board though from what I can tell its some really >>> great >>> work, is there a ballpark price yet or possible release on it? >>> >>> >>> >>> Ash Charles-2 wrote: >>>> >>>> Hi, >>>> >>>> The gyro part is actually not yet released so I would be surprised if >>>> people were discussing it; even if the part is not exactly the same, >>>> could you point me to the forum? >>>> >>>> I had looked at the Invensense part as one of the few 3-axis digital >>>> gyros on the market but as yet weren't able to get appropriate pricing >>>> on the part. >>>> >>>> To keep the price down and the size requirements for the board >>>> reasonable, we elected not to add a GPS (and, by consquence, not a >>>> pressure sensor). I would have to double-check but I think the ADC on >>>> the micro. actually has temperature built-in although this is probably >>>> not super useful. >>>> >>>> Thanks for the feedback, >>>> >>>> -Ash >>>> >>>> On Tue, Jun 15, 2010 at 5:30 PM, vwyodapink <vwy...@gm...> >>>> wrote: >>>>> >>>>> What about adding a connector on the board for a GPS like the Ublock >>>>> or >>>>> EM406 >>>>> >>>>> Though I am sure not useful to everyone but a absolute pressure sensor >>>>> with >>>>> temp would be nice. >>>>> >>>>> I have heard there are a bunch of vibration issues with the gyro you >>>>> have >>>>> listed you are using, Invensense is making a vibration resistant gyro >>>>> that >>>>> has been used in a few projects that I have seen and has had really >>>>> great >>>>> results. I am by no means an expert at all, just remember reading a >>>>> bunch >>>>> about those gyros on a different message board and they were ditched >>>>> because >>>>> of horrible performance. >>>>> >>>>> >>>>> >>>>> Ash Charles-2 wrote: >>>>>> >>>>>> Hi, >>>>>> >>>>>> A preliminary schematic (http://www.gumstix.net/other/B30019.sch) and >>>>>> board design (http://www.gumstix.net/other/B30019.brd) for this >>>>>> Overo-robostix board are available in Eagle format. As before, we >>>>>> welcome your feedback---it is really helpful to know what features >>>>>> are >>>>>> useful for users. >>>>>> >>>>>> Hope you like it :). >>>>>> >>>>>> -Ash >>>>>> >>>>>> On Sat, May 22, 2010 at 8:56 AM, Dave Hylands <dhy...@gm...> >>>>>> wrote: >>>>>>> Hi Ash, >>>>>>> >>>>>>> On Sat, May 22, 2010 at 12:40 AM, Ash Charles <ash...@gm...> >>>>>>> wrote: >>>>>>>> On Fri, May 21, 2010 at 6:40 PM, Dave Hylands <dhy...@gm...> >>>>>>>> wrote: >>>>>>>>> Hi Ash, >>>>>>>>> >>>>>>>>> On Fri, May 21, 2010 at 5:01 PM, Ash Charles <as...@gu...> >>>>>>>>> wrote: >>>>>>>>>> Afternoon, >>>>>>>>>> >>>>>>>>>> We've looked through the pin-muxing for this board and we propose >>>>>>>>>> the >>>>>>>>>> following 3 by 8 pin right-angle 0.1"pitch male headers: >>>>>>>>>> >>>>>>>>>> =====HEADER #1===== >>>>>>>>>> PWM0 PWM1 PWM2 PWM3 PWM4 PWM5 PWM6 PWM7 >>>>>>>>>> Vbat Vbat Vbat Vbat Vbat Vbat Vbat >>>>>>>>>> Vbat >>>>>>>>>> GND GND GND GND GND GND GND GND >>>>>>>>> >>>>>>>>> Hopefully, these will be Vmotor, which is jumpered to Vbat. >>>>>>>> To make sure I understand what you meant in your previous post, the >>>>>>>> jumper on the Robostix allowed people to use either a battery or a >>>>>>>> wall wart to supply power to the board? >>>>>>>> For the new board, the 'Vbat' signal (definitely a misnomer on my >>>>>>>> part) would be the V+ line taken directly from the power source be >>>>>>>> it >>>>>>>> a wall wart or a battery. >>>>>>> >>>>>>> I guess by battery you really mean a dedicated 2-pin power >>>>>>> connector. >>>>>>> >>>>>>>>> How will the luminary micro be programmed? Will a JTAG interface >>>>>>>>> be >>>>>>>>> available? >>>>>>>> I hadn't included the JTAG interface; I think this requires an >>>>>>>> additional four pins which is not impossible but board space would >>>>>>>> start to get tight. One option would be putting contact pads for >>>>>>>> JTAG...does this seem useful? >>>>>>>> The device can be accessed via I2C0, UART0, or SSI0. >>>>>>> >>>>>>> I just wanted to make sure that you address how the device will be >>>>>>> programmed. I see that it does indeed have a ROM based bootloader >>>>>>> which can be programmed as you indicated, which somewhat alleviates >>>>>>> the need for a JTAG. >>>>>>> >>>>>>> Although having the JTAG allows a debugger to be used, which I think >>>>>>> will be important. >>>>>>> >>>>>>> If you put the pads somewhere that a 10-pin JTAG mini connector >>>>>>> could >>>>>>> be >>>>>>> used >>>>>>> <http://www.luminarymicro.com/products/mdl-ada2.html> This could be >>>>>>> a >>>>>>> surface mount connector. It looks like its a 2x5 0.050" header (see >>>>>>> the schematics and BOM for this eval board: >>>>>>> <http://www.luminarymicro.com/index.php?option=com_remository&func=download&id=983&chk=d1a772ed2075b69e938af114b279083b&Itemid=591> >>>>>>> >>>>>>>>>> Secondly: is the arrangement of pins correct? >>>>>>>>>> -- on Header #2, should the UARTS be four pins each (RX, V+, TX, >>>>>>>>>> GND) with all three stacked on top of each other? e.g. >>>>>>>>>> RX0 5V TX0 GND >>>>>>>>>> RX1 5V TX1 GND >>>>>>>>>> RX2 5V TX2 GND >>>>>>>>> >>>>>>>>> The Arduino stuff seems to have standardized on using: >>>>>>>>> the same pinout as the FTDI USB-to-logic level serial connectors >>>>>>>>> which >>>>>>>>> is >>>>>>>>> >>>>>>>>> 1 - GND >>>>>>>>> 2 - CTS >>>>>>>>> 3 - VCC >>>>>>>>> 4 - TXD >>>>>>>>> 5 - RXD >>>>>>>>> 6 - RTS >>>>>>>>> >>>>>>>>> <http://www.ftdichip.com/Products/EvaluationKits/TTL-232R-3V3.htm> >>>>>>>>> >>>>>>>>> On the Arduino, the RTS pin is tied into the reset circuitry so >>>>>>>>> that >>>>>>>>> the board can be reset (and serial downloaded to) from the host. >>>>>>>>> >>>>>>>>> Having the 4 pin layout which is compatible with the robostix also >>>>>>>>> makes sense. I just wanted to throw out the Arduino thing since >>>>>>>>> it's >>>>>>>>> quite popular. >>>>>>>> Thanks for pointing out the Arduino connector; I'd been hunting >>>>>>>> around >>>>>>>> to see if there was such a standard earlier today and hadn't found >>>>>>>> anything. >>>>>>>> Is there a strong motivation for including the CTS and RTS lines? >>>>>>>> I >>>>>>>> don't recall using them before so I found it hard to justify extra >>>>>>>> pins but perhaps this is more a reflection on my inexperience than >>>>>>>> on >>>>>>>> the utility of these pins. >>>>>>> >>>>>>> Being able to reset the microcontroller through the download >>>>>>> interface >>>>>>> is nice. It means that the SW can do the reset and send the >>>>>>> appropriate bytes with appropriate timings, rather than relying on a >>>>>>> particular sequence of events by the user. >>>>>>> >>>>>>> Although looking at the protocol, it seems pretty easy to just start >>>>>>> the host side program and then hit reset on the micro. So I think >>>>>>> you >>>>>>> could eliminate the extra lines if you need the space. >>>>>>> >>>>>>> It would be nice, especially in standalone mode to be able to >>>>>>> connect >>>>>>> up the FTDI chip normally used for the overo console to the micro, >>>>>>> perhaps using some switches, or DNI resistors. >>>>>>> >>>>>>> -- >>>>>>> Dave Hylands >>>>>>> Shuswap, BC, Canada >>>>>>> http://www.DaveHylands.com/ >>>>>>> >>>>>>> ------------------------------------------------------------------------------ >>>>>>> >>>>>>> _______________________________________________ >>>>>>> gumstix-users mailing list >>>>>>> gum...@li... >>>>>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>>>>> >>>>>> >>>>>> ------------------------------------------------------------------------------ >>>>>> ThinkGeek and WIRED's GeekDad team up for the Ultimate >>>>>> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the >>>>>> lucky parental unit. See the prize list and enter to win: >>>>>> http://p.sf.net/sfu/thinkgeek-promo >>>>>> _______________________________________________ >>>>>> gumstix-users mailing list >>>>>> gum...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>>>> >>>>>> >>>>> >>>>> >>>>> ----- >>>>> Just a beginner trying to learn his way around. >>>>> -- >>>>> View this message in context: >>>>> http://old.nabble.com/Robostix-for-Overo-tp28600551p28897886.html >>>>> Sent from the Gumstix mailing list archive at Nabble.com. >>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> ThinkGeek and WIRED's GeekDad team up for the Ultimate >>>>> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the >>>>> lucky parental unit. See the prize list and enter to win: >>>>> http://p.sf.net/sfu/thinkgeek-promo >>>>> _______________________________________________ >>>>> gumstix-users mailing list >>>>> gum...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> ThinkGeek and WIRED's GeekDad team up for the Ultimate >>>> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the >>>> lucky parental unit. See the prize list and enter to win: >>>> http://p.sf.net/sfu/thinkgeek-promo >>>> _______________________________________________ >>>> gumstix-users mailing list >>>> gum...@li... >>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>> >>>> >>> >>> >>> ----- >>> Just a beginner trying to learn his way around. >>> -- >>> View this message in context: >>> http://old.nabble.com/Robostix-for-Overo-tp28600551p28900186.html >>> Sent from the Gumstix mailing list archive at Nabble.com. >>> >>> >>> ------------------------------------------------------------------------------ >>> ThinkGeek and WIRED's GeekDad team up for the Ultimate >>> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the >>> lucky parental unit. See the prize list and enter to win: >>> http://p.sf.net/sfu/thinkgeek-promo >>> _______________________________________________ >>> gumstix-users mailing list >>> gum...@li... >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>> >> >> ------------------------------------------------------------------------------ >> ThinkGeek and WIRED's GeekDad team up for the Ultimate >> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the >> lucky parental unit. See the prize list and enter to win: >> http://p.sf.net/sfu/thinkgeek-promo >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> > > ----- Just a beginner trying to learn his way around. -- View this message in context: http://old.nabble.com/Robostix-for-Overo-tp28600551p28936122.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: antoine d. <po...@gm...> - 2010-07-09 11:10:26
|
Hello World Looks like we've done something quite similar : http://paparazzi.enac.fr/wiki/Lisa I'm using a STM32 instead of the luminarymicro and the main purpose of this board is to be an autopilot, though I'm convinced it has applications in other robotics fields. My board has onboard pressure sensors ( absolute and differential ) but the inertial ones are external to allow a choice of commercial IMUs ( xsense, cloudcap, vectornav) or the one we've designed ( http://paparazzi.enac.fr/wiki/BoozIMU ) The board runs Paparazzi ( http://paparazzi.enac.fr/wiki/Main_Page ) and the STM32 has enough processing power to run the autopilot on its own, leaving the Overo available for payload processing. We use SPI with DMA on both ends between the OMAP and the STM32, thus providing ample bandwith and flexibility in the repartition of tasks between processors. The board has an onboard FT2232H USB chip. One of its channels is used for JTAG on the STM32 and the second one for the Overo's console. The board features two switching supply modules and all the connectors are Molex picoblades with locking mechanism. Best Regards Antoine Drouin On Sat, Jun 19, 2010 at 7:50 PM, vwyodapink <vwy...@gm...> wrote: > > Here is a link to the arduImu schematic and board > > http://docs.google.com/leaf?id=0ByI4WbhJsiyqODFiZmJmYjItMjg1Zi00NWU2LTljYzYtMDFjM2YxZWU0MWUx&hl=en > > http://docs.google.com/leaf?id=0ByI4WbhJsiyqODRkNTUwZWQtNTYwMC00MjA3LTg0YTUtMDc5NTg0M2YyMzRl&hl=en > > > > > vwyodapink wrote: >> >> The major advantage would be weight savings as you dont have another huge >> USB plug which also in turn saves you a spot as well. I know lots of >> people use the style of connector I showed you its a common way to run GPS >> for UAV's. Functionality wise there is not real difference, though I >> showed some people on my UAV forum and they were stoked to see something >> like this coming out but. as it sits now would still take more addons to >> be fully useful for myself others into similar projects to where it would >> be worth ditching whats already being used. Which I would like to do as I >> think this way would be much cleaner if everything was all on one board. >> >> The way I use things now is the Overo is attached to the summit and by i2c >> connection I connect either the UAVDev Board, which is very similar to >> your robostix, and I have also another one setup by i2c using a Ardupilot >> Mega and ArduIMU Mega. The arduimu mega is by far the best IMU AHRS I have >> tried to date, granted I have only tried the 6d0f from sparkfun, standard >> ardu IMU+, and the UAVDevBoard. >> >> I was wondering about the motor controlers you have on there is that >> similar to using an electronic speed controller? If so what kind of amps >> can it handle? Or is to control small and not very powerful elec engines? >> Sorry if that was stated or a really basic question. >> >> Here are a list of links just in case you would like to see the things I >> am talking about if your not familiar with them. >> http://www.sparkfun.com/commerce/product_info.php?products_id=9038 -- UAV >> Dev Board >> http://store.diydrones.com/product_p/br-0012-01.htm -- ArduIMU Mega >> >> Hope this helps you out some, Thanks again for the hard work you have done >> so far. If I can be of any more use or put more links to things let me >> know :) >> >> Jeremy >> >> If >> >> Ash Charles-2 wrote: >>> >>> Hi, >>> >>> Is there a major advantage not to use a USB-based GPS dongle or a UART >>> GPS? >>> >>> I can't confirm pricing information yet; we are working to get these >>> details figured out. Most likely, we will have several different >>> population options (and therefore prices) depending on users' needs. >>> >>> Thanks for the forum link. >>> >>> -Ash >>> >>> On Wed, Jun 16, 2010 at 1:24 AM, vwyodapink <vwy...@gm...> wrote: >>>> >>>> I wasnt actually meaning having the GPS as part of the board but >>>> actually >>>> putting a plus like this: >>>> http://www.sparkfun.com/commerce/product_info.php?products_id=579 >>>> So people who want a GPS can easily add one and not have it be USB >>>> based. I >>>> would much rather see the GPS as not having to go through a hub or >>>> similar. >>>> Plus the plugs are tiny. >>>> >>>> I understand about the pressure sensor, I have been trying to get a >>>> breakout >>>> board with an absolute pressure sensor with temp to work with my fire. >>>> Though the bosh absolute pressure sensor is another very small foot >>>> print. >>>> >>>> You were correct about the gyro that was my mistake and I did not read >>>> the >>>> model number correctly. >>>> http://forums.parallax.com/forums/default.aspx?m=436063&f=25&p=6 Is >>>> where I >>>> thought I saw that just in case you want to see it. But this was the >>>> gyro I >>>> was thinking of that had the issues LPR530AL, sorry about that >>>> >>>> I think its a great board though from what I can tell its some really >>>> great >>>> work, is there a ballpark price yet or possible release on it? >>>> >>>> >>>> >>>> Ash Charles-2 wrote: >>>>> >>>>> Hi, >>>>> >>>>> The gyro part is actually not yet released so I would be surprised if >>>>> people were discussing it; even if the part is not exactly the same, >>>>> could you point me to the forum? >>>>> >>>>> I had looked at the Invensense part as one of the few 3-axis digital >>>>> gyros on the market but as yet weren't able to get appropriate pricing >>>>> on the part. >>>>> >>>>> To keep the price down and the size requirements for the board >>>>> reasonable, we elected not to add a GPS (and, by consquence, not a >>>>> pressure sensor). I would have to double-check but I think the ADC on >>>>> the micro. actually has temperature built-in although this is probably >>>>> not super useful. >>>>> >>>>> Thanks for the feedback, >>>>> >>>>> -Ash >>>>> >>>>> On Tue, Jun 15, 2010 at 5:30 PM, vwyodapink <vwy...@gm...> >>>>> wrote: >>>>>> >>>>>> What about adding a connector on the board for a GPS like the Ublock >>>>>> or >>>>>> EM406 >>>>>> >>>>>> Though I am sure not useful to everyone but a absolute pressure sensor >>>>>> with >>>>>> temp would be nice. >>>>>> >>>>>> I have heard there are a bunch of vibration issues with the gyro you >>>>>> have >>>>>> listed you are using, Invensense is making a vibration resistant gyro >>>>>> that >>>>>> has been used in a few projects that I have seen and has had really >>>>>> great >>>>>> results. I am by no means an expert at all, just remember reading a >>>>>> bunch >>>>>> about those gyros on a different message board and they were ditched >>>>>> because >>>>>> of horrible performance. >>>>>> >>>>>> >>>>>> >>>>>> Ash Charles-2 wrote: >>>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> A preliminary schematic (http://www.gumstix.net/other/B30019.sch) and >>>>>>> board design (http://www.gumstix.net/other/B30019.brd) for this >>>>>>> Overo-robostix board are available in Eagle format. As before, we >>>>>>> welcome your feedback---it is really helpful to know what features >>>>>>> are >>>>>>> useful for users. >>>>>>> >>>>>>> Hope you like it :). >>>>>>> >>>>>>> -Ash >>>>>>> >>>>>>> On Sat, May 22, 2010 at 8:56 AM, Dave Hylands <dhy...@gm...> >>>>>>> wrote: >>>>>>>> Hi Ash, >>>>>>>> >>>>>>>> On Sat, May 22, 2010 at 12:40 AM, Ash Charles <ash...@gm...> >>>>>>>> wrote: >>>>>>>>> On Fri, May 21, 2010 at 6:40 PM, Dave Hylands <dhy...@gm...> >>>>>>>>> wrote: >>>>>>>>>> Hi Ash, >>>>>>>>>> >>>>>>>>>> On Fri, May 21, 2010 at 5:01 PM, Ash Charles <as...@gu...> >>>>>>>>>> wrote: >>>>>>>>>>> Afternoon, >>>>>>>>>>> >>>>>>>>>>> We've looked through the pin-muxing for this board and we propose >>>>>>>>>>> the >>>>>>>>>>> following 3 by 8 pin right-angle 0.1"pitch male headers: >>>>>>>>>>> >>>>>>>>>>> =====HEADER #1===== >>>>>>>>>>> PWM0 PWM1 PWM2 PWM3 PWM4 PWM5 PWM6 PWM7 >>>>>>>>>>> Vbat Vbat Vbat Vbat Vbat Vbat Vbat >>>>>>>>>>> Vbat >>>>>>>>>>> GND GND GND GND GND GND GND GND >>>>>>>>>> >>>>>>>>>> Hopefully, these will be Vmotor, which is jumpered to Vbat. >>>>>>>>> To make sure I understand what you meant in your previous post, the >>>>>>>>> jumper on the Robostix allowed people to use either a battery or a >>>>>>>>> wall wart to supply power to the board? >>>>>>>>> For the new board, the 'Vbat' signal (definitely a misnomer on my >>>>>>>>> part) would be the V+ line taken directly from the power source be >>>>>>>>> it >>>>>>>>> a wall wart or a battery. >>>>>>>> >>>>>>>> I guess by battery you really mean a dedicated 2-pin power >>>>>>>> connector. >>>>>>>> >>>>>>>>>> How will the luminary micro be programmed? Will a JTAG interface >>>>>>>>>> be >>>>>>>>>> available? >>>>>>>>> I hadn't included the JTAG interface; I think this requires an >>>>>>>>> additional four pins which is not impossible but board space would >>>>>>>>> start to get tight. One option would be putting contact pads for >>>>>>>>> JTAG...does this seem useful? >>>>>>>>> The device can be accessed via I2C0, UART0, or SSI0. >>>>>>>> >>>>>>>> I just wanted to make sure that you address how the device will be >>>>>>>> programmed. I see that it does indeed have a ROM based bootloader >>>>>>>> which can be programmed as you indicated, which somewhat alleviates >>>>>>>> the need for a JTAG. >>>>>>>> >>>>>>>> Although having the JTAG allows a debugger to be used, which I think >>>>>>>> will be important. >>>>>>>> >>>>>>>> If you put the pads somewhere that a 10-pin JTAG mini connector >>>>>>>> could >>>>>>>> be >>>>>>>> used >>>>>>>> <http://www.luminarymicro.com/products/mdl-ada2.html> This could be >>>>>>>> a >>>>>>>> surface mount connector. It looks like its a 2x5 0.050" header (see >>>>>>>> the schematics and BOM for this eval board: >>>>>>>> <http://www.luminarymicro.com/index.php?option=com_remository&func=download&id=983&chk=d1a772ed2075b69e938af114b279083b&Itemid=591> >>>>>>>> >>>>>>>>>>> Secondly: is the arrangement of pins correct? >>>>>>>>>>> -- on Header #2, should the UARTS be four pins each (RX, V+, TX, >>>>>>>>>>> GND) with all three stacked on top of each other? e.g. >>>>>>>>>>> RX0 5V TX0 GND >>>>>>>>>>> RX1 5V TX1 GND >>>>>>>>>>> RX2 5V TX2 GND >>>>>>>>>> >>>>>>>>>> The Arduino stuff seems to have standardized on using: >>>>>>>>>> the same pinout as the FTDI USB-to-logic level serial connectors >>>>>>>>>> which >>>>>>>>>> is >>>>>>>>>> >>>>>>>>>> 1 - GND >>>>>>>>>> 2 - CTS >>>>>>>>>> 3 - VCC >>>>>>>>>> 4 - TXD >>>>>>>>>> 5 - RXD >>>>>>>>>> 6 - RTS >>>>>>>>>> >>>>>>>>>> <http://www.ftdichip.com/Products/EvaluationKits/TTL-232R-3V3.htm> >>>>>>>>>> >>>>>>>>>> On the Arduino, the RTS pin is tied into the reset circuitry so >>>>>>>>>> that >>>>>>>>>> the board can be reset (and serial downloaded to) from the host. >>>>>>>>>> >>>>>>>>>> Having the 4 pin layout which is compatible with the robostix also >>>>>>>>>> makes sense. I just wanted to throw out the Arduino thing since >>>>>>>>>> it's >>>>>>>>>> quite popular. >>>>>>>>> Thanks for pointing out the Arduino connector; I'd been hunting >>>>>>>>> around >>>>>>>>> to see if there was such a standard earlier today and hadn't found >>>>>>>>> anything. >>>>>>>>> Is there a strong motivation for including the CTS and RTS lines? >>>>>>>>> I >>>>>>>>> don't recall using them before so I found it hard to justify extra >>>>>>>>> pins but perhaps this is more a reflection on my inexperience than >>>>>>>>> on >>>>>>>>> the utility of these pins. >>>>>>>> >>>>>>>> Being able to reset the microcontroller through the download >>>>>>>> interface >>>>>>>> is nice. It means that the SW can do the reset and send the >>>>>>>> appropriate bytes with appropriate timings, rather than relying on a >>>>>>>> particular sequence of events by the user. >>>>>>>> >>>>>>>> Although looking at the protocol, it seems pretty easy to just start >>>>>>>> the host side program and then hit reset on the micro. So I think >>>>>>>> you >>>>>>>> could eliminate the extra lines if you need the space. >>>>>>>> >>>>>>>> It would be nice, especially in standalone mode to be able to >>>>>>>> connect >>>>>>>> up the FTDI chip normally used for the overo console to the micro, >>>>>>>> perhaps using some switches, or DNI resistors. >>>>>>>> >>>>>>>> -- >>>>>>>> Dave Hylands >>>>>>>> Shuswap, BC, Canada >>>>>>>> http://www.DaveHylands.com/ >>>>>>>> >>>>>>>> ------------------------------------------------------------------------------ >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> gumstix-users mailing list >>>>>>>> gum...@li... >>>>>>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>>>>>> >>>>>>> >>>>>>> ------------------------------------------------------------------------------ >>>>>>> ThinkGeek and WIRED's GeekDad team up for the Ultimate >>>>>>> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the >>>>>>> lucky parental unit. See the prize list and enter to win: >>>>>>> http://p.sf.net/sfu/thinkgeek-promo >>>>>>> _______________________________________________ >>>>>>> gumstix-users mailing list >>>>>>> gum...@li... >>>>>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> ----- >>>>>> Just a beginner trying to learn his way around. >>>>>> -- >>>>>> View this message in context: >>>>>> http://old.nabble.com/Robostix-for-Overo-tp28600551p28897886.html >>>>>> Sent from the Gumstix mailing list archive at Nabble.com. >>>>>> >>>>>> >>>>>> ------------------------------------------------------------------------------ >>>>>> ThinkGeek and WIRED's GeekDad team up for the Ultimate >>>>>> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the >>>>>> lucky parental unit. See the prize list and enter to win: >>>>>> http://p.sf.net/sfu/thinkgeek-promo >>>>>> _______________________________________________ >>>>>> gumstix-users mailing list >>>>>> gum...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> ThinkGeek and WIRED's GeekDad team up for the Ultimate >>>>> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the >>>>> lucky parental unit. See the prize list and enter to win: >>>>> http://p.sf.net/sfu/thinkgeek-promo >>>>> _______________________________________________ >>>>> gumstix-users mailing list >>>>> gum...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>>> >>>>> >>>> >>>> >>>> ----- >>>> Just a beginner trying to learn his way around. >>>> -- >>>> View this message in context: >>>> http://old.nabble.com/Robostix-for-Overo-tp28600551p28900186.html >>>> Sent from the Gumstix mailing list archive at Nabble.com. >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> ThinkGeek and WIRED's GeekDad team up for the Ultimate >>>> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the >>>> lucky parental unit. See the prize list and enter to win: >>>> http://p.sf.net/sfu/thinkgeek-promo >>>> _______________________________________________ >>>> gumstix-users mailing list >>>> gum...@li... >>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>> >>> >>> ------------------------------------------------------------------------------ >>> ThinkGeek and WIRED's GeekDad team up for the Ultimate >>> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the >>> lucky parental unit. See the prize list and enter to win: >>> http://p.sf.net/sfu/thinkgeek-promo >>> _______________________________________________ >>> gumstix-users mailing list >>> gum...@li... >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>> >>> >> >> > > > ----- > Just a beginner trying to learn his way around. > -- > View this message in context: http://old.nabble.com/Robostix-for-Overo-tp28600551p28936122.html > Sent from the Gumstix mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |