hvontres

Just found 100 20 pin headders for $5:
 
http://www.goldmine-elec-products.com/prodinfo.asp?number=G19546
 
Perfect for mounting boosterpacks to the bottom of the launchpad

I have attached a simple spreadsheet I am using to plan out how to use the resources on a 430g2553 for a project. It is simply all of the functions for each pin in a seprate cell with a symbolic representation of the chip in the center. The color coding is completely up the the user. This way one can try to make decisions on which peripheral can be used and how it might need to be shared by other functions. I hope this helps

The .zip file has both a OpenOffice and an excel version, since I couldn't attache the sheets directly
 
430G2553_pin_plan.zip

My sister sent me this, thought you guys would enjoy this

I have attached a simple spreadsheet I am using to plan out how to use the resources on a 430g2553 for a project. It is simply all of the functions for each pin in a seprate cell with a symbolic representation of the chip in the center. The color coding is completely up the the user. This way one can try to make decisions on which peripheral can be used and how it might need to be shared by other functions. I hope this helps

The .zip file has both a OpenOffice and an excel version, since I couldn't attache the sheets directly
 
430G2553_pin_plan.zip

I have attached a simple spreadsheet I am using to plan out how to use the resources on a 430g2553 for a project. It is simply all of the functions for each pin in a seprate cell with a symbolic representation of the chip in the center. The color coding is completely up the the user. This way one can try to make decisions on which peripheral can be used and how it might need to be shared by other functions. I hope this helps

The .zip file has both a OpenOffice and an excel version, since I couldn't attache the sheets directly
 
430G2553_pin_plan.zip

I realize this is kind of an old thread, but I finally got around to re-organizing my space in the garage.
 
Here is the Before Picture, kind of my Bob Pease Memorial Shrine on a desk:
 

 
Here is the new improved Setup:
 

 
Note, I have not moved over all of the parts and tools from the old pile yet. I am hoping to keep most of my stuff in the big black cabinet. Most of the stuff here is surplus stuff from work. We are moving to a smaller building, so I scored the ESD safe bench, the cabinet, the two standard monitors, the chair and the magnifier. The scope I got off of Ebay for ~$400 bucks and the supply is an old AT (not ATX ) supply in a custom wood box. The 15" Monitor on the left is for the scope and was originaly a custom monitor in a STEEL box for one of our machines. we decided to go with regular displays instead, so it wound up in the boneyard until we cleaned that out about a year ago Someday it might end up as a display on a mill or somthing more industrial, but I don't know yet. The Computer and the SCSI enclosure were leftovers from IT, as were the tape drive and all of the Hard Drives inside. I am in the middle of upgrading the disk layout since I got a hold of a couple more 18 and 34 GB SCSI drives from the IT pile. The Computer is an old HP workstation with dual PIII 600's inside... I know it's kind of underpowered, but it has two isa slots for my GPIB card and the interface to the universal programmer. And the price was right. I still need to move over my microscope, but I need to figure out exactly where to mount it.

I realize this is kind of an old thread, but I finally got around to re-organizing my space in the garage.
 
Here is the Before Picture, kind of my Bob Pease Memorial Shrine on a desk:
 

 
Here is the new improved Setup:
 

 
Note, I have not moved over all of the parts and tools from the old pile yet. I am hoping to keep most of my stuff in the big black cabinet. Most of the stuff here is surplus stuff from work. We are moving to a smaller building, so I scored the ESD safe bench, the cabinet, the two standard monitors, the chair and the magnifier. The scope I got off of Ebay for ~$400 bucks and the supply is an old AT (not ATX ) supply in a custom wood box. The 15" Monitor on the left is for the scope and was originaly a custom monitor in a STEEL box for one of our machines. we decided to go with regular displays instead, so it wound up in the boneyard until we cleaned that out about a year ago Someday it might end up as a display on a mill or somthing more industrial, but I don't know yet. The Computer and the SCSI enclosure were leftovers from IT, as were the tape drive and all of the Hard Drives inside. I am in the middle of upgrading the disk layout since I got a hold of a couple more 18 and 34 GB SCSI drives from the IT pile. The Computer is an old HP workstation with dual PIII 600's inside... I know it's kind of underpowered, but it has two isa slots for my GPIB card and the interface to the universal programmer. And the price was right. I still need to move over my microscope, but I need to figure out exactly where to mount it.

A DC motor (either brushed or brushless) will need some kind of feed back to control position. With a stepper, the encoder can be used for servo like control, or it can be used to detect missed steps after the motion is done. This way, the motor is run in open loop and if there were any missing steps during the move, you could command a couple of extra steps at the end. With a stepper, you are more likely to loose steps at higher speeds, since motor torque falls off pretty rapidly.
 
Having worked around servo systems for the last 18 years, I would not reccomend them for the uninitiated. Proper tuning and hookups can be a real pain without the propper tools. Also, the effects of feedback failures can be very spectacular and dangerous (imagine an axis flying towards you with full torque applied after the encoder fails and then hitting the end stops with a loud bang... that'll wake you up) But for the really adventurous, they do offer the potential for more performance. One of these days I should set up some articles on how a servo system works and can be tuned.... but that would be a bit too much like work

I would suggest a shaft encoder, especially once the new Tiva Launch pads get out. That one will have TWO quadarature counters on board, so interfacing to the encoder should be very simple. As far as controlling the position of a Hydraulic cylinder, you might be better off getting your feedback from the rod itself. One way that I played with years ago while working on the animation system for a Rose Parade Float (http://www.csupomona.edu/~library/specialcollections/rosefloat/floatimages/1993photo.html) is to use a 10 turn pot with a torstion spring, a large wheel and some steel cable. As the rod extends, the pot turns and you get absolute position feedback from the cylinder. I think if you try to just measure the flow, you will integrate up large errors.

Until then, try using ' spi' or ' i2c' as a workaround

Until then, try using ' spi' or ' i2c' as a workaround

There may be licensing issues. The peripheral driver is licensed under a BSD license, but the Grlib and USBlib fall under the "Ti Clickwrap license". this license includes the following clause:
This might be keeping that library out of Energia.

Well, I think I know what happened here... you need to add the Tiva board to your wishlist and then order it. I think I saw the picture at the bottom of the page and added it to the cart not realizing that that was a link to the old EK120XL... so now what will I do with two more

Well, I think I know what happened here... you need to add the Tiva board to your wishlist and then order it. I think I saw the picture at the bottom of the page and added it to the cart not realizing that that was a link to the old EK120XL... so now what will I do with two more

This project attempts to control a surplus LCD (http://www.goldmine-elec-products.com/prodinfo.asp?number=G18246) using a MSP430 and the Stellaris Launchpad.
 
Brief Description:
 
This project is designed to run a 320x240 monochrome LCD with minimal CPU overhead.
A seprate controller board supplies the VEE for the display, controls the Backlight and has a MSP430G2542 running as a SPI Master. The MSP also controls the clocks for moving the data to the display.
The Stellaris side sets up a 1BPP offscreen display for Grlib and also sets up a UDMA job that transfers the display buffer to the SPI port for the MSP to collect.
The SPI connection is set up to transfer 16 bits at a time, allowing for 4 pixel updates for each transfer. With the SPI clock running at 8Mhz, the display can update at ~51 Hz.
 
I had the first PCBs made by OSH park and am currently trying to iron out some bugs in the bias voltage section. As soon as that is done, I will be adding schematics and the board layout on github.
 
Code and documentation can be found here:
 
https://github.com/hvontres/LCD-Controller
 
 
Here is a picture of the current project:
 

 
Here is the first prototype:

 
a picture of just the controller:

 
controller mounted below launchpad:

 
 
Here is a video demo showing the different modes of the main application:
 

 
The video starts with the splash screen, inverts the display, animates the splashscreen using grlib, displays text using grlib functions and finally shows some test images downloaded in 8 pixel chunks from the host. The current code allows for 30 chunks per transfer, so that is why the screen updates are a little slow. I'll try to get some better video soon.
 

Also, one other thing to keep in mind is that one of the configurations for the SPI pins confilicts with the pins used for the on-board RGB LED. So in order to use all four SPI ports, you would need to remove some 0-ohm resistors.

Actually the display is really dumb. The MSP is in charge of doing the refresh and fetching the data. The Stellaris mostly supplies the memory needed to hold the display data. The Driver chips on the display have enough memory to hold one LINE of data at a time. So the max refresh rate is limited by how fast the MSP can process the data. This display was originaly meant to be driven by something like a SED1335 controller chip. But that would have been too easy
 
By having the MSP handle all of the display timing and refresh, the Stellaris only needs to use ~4% CPU time to manage the display, leaving plenty of CPU time for generating the Data to display.
 
Here is some more info on how to drive this particular display: http://tinyurl.com/8j9jkvv

This project attempts to control a surplus LCD (http://www.goldmine-elec-products.com/prodinfo.asp?number=G18246) using a MSP430 and the Stellaris Launchpad.
 
Brief Description:
 
This project is designed to run a 320x240 monochrome LCD with minimal CPU overhead.
A seprate controller board supplies the VEE for the display, controls the Backlight and has a MSP430G2542 running as a SPI Master. The MSP also controls the clocks for moving the data to the display.
The Stellaris side sets up a 1BPP offscreen display for Grlib and also sets up a UDMA job that transfers the display buffer to the SPI port for the MSP to collect.
The SPI connection is set up to transfer 16 bits at a time, allowing for 4 pixel updates for each transfer. With the SPI clock running at 8Mhz, the display can update at ~51 Hz.
 
I had the first PCBs made by OSH park and am currently trying to iron out some bugs in the bias voltage section. As soon as that is done, I will be adding schematics and the board layout on github.
 
Code and documentation can be found here:
 
https://github.com/hvontres/LCD-Controller
 
 
Here is a picture of the current project:
 

 
Here is the first prototype:

 
a picture of just the controller:

 
controller mounted below launchpad:

 
 
Here is a video demo showing the different modes of the main application:
 

 
The video starts with the splash screen, inverts the display, animates the splashscreen using grlib, displays text using grlib functions and finally shows some test images downloaded in 8 pixel chunks from the host. The current code allows for 30 chunks per transfer, so that is why the screen updates are a little slow. I'll try to get some better video soon.
 

Nope, no memory on the LCD, other than the shift registers in the controllers. The chips on the controller are a MSP4302542 to handle the data transfers between the stellaris and the lcd, a 74HCT245 used as a level shifter from 3.3V to 5V, a 4N29 isolator to turn the display on and off and a Max774 to supply the bias voltage. The framebuffer for the lcd is actually in the stellaris.
 
https://github.com/hvontres/LCD-Controller/blob/master/Docs/Controller%20Design.pdf has a more detailed description on how this thing works

Nope, no memory on the LCD, other than the shift registers in the controllers. The chips on the controller are a MSP4302542 to handle the data transfers between the stellaris and the lcd, a 74HCT245 used as a level shifter from 3.3V to 5V, a 4N29 isolator to turn the display on and off and a Max774 to supply the bias voltage. The framebuffer for the lcd is actually in the stellaris.
 
https://github.com/hvontres/LCD-Controller/blob/master/Docs/Controller%20Design.pdf has a more detailed description on how this thing works

This project attempts to control a surplus LCD (http://www.goldmine-elec-products.com/prodinfo.asp?number=G18246) using a MSP430 and the Stellaris Launchpad.
 
Brief Description:
 
This project is designed to run a 320x240 monochrome LCD with minimal CPU overhead.
A seprate controller board supplies the VEE for the display, controls the Backlight and has a MSP430G2542 running as a SPI Master. The MSP also controls the clocks for moving the data to the display.
The Stellaris side sets up a 1BPP offscreen display for Grlib and also sets up a UDMA job that transfers the display buffer to the SPI port for the MSP to collect.
The SPI connection is set up to transfer 16 bits at a time, allowing for 4 pixel updates for each transfer. With the SPI clock running at 8Mhz, the display can update at ~51 Hz.
 
I had the first PCBs made by OSH park and am currently trying to iron out some bugs in the bias voltage section. As soon as that is done, I will be adding schematics and the board layout on github.
 
Code and documentation can be found here:
 
https://github.com/hvontres/LCD-Controller
 
 
Here is a picture of the current project:
 

 
Here is the first prototype:

 
a picture of just the controller:

 
controller mounted below launchpad:

 
 
Here is a video demo showing the different modes of the main application:
 

 
The video starts with the splash screen, inverts the display, animates the splashscreen using grlib, displays text using grlib functions and finally shows some test images downloaded in 8 pixel chunks from the host. The current code allows for 30 chunks per transfer, so that is why the screen updates are a little slow. I'll try to get some better video soon.
 

This project attempts to control a surplus LCD (http://www.goldmine-elec-products.com/prodinfo.asp?number=G18246) using a MSP430 and the Stellaris Launchpad.
 
Brief Description:
 
This project is designed to run a 320x240 monochrome LCD with minimal CPU overhead.
A seprate controller board supplies the VEE for the display, controls the Backlight and has a MSP430G2542 running as a SPI Master. The MSP also controls the clocks for moving the data to the display.
The Stellaris side sets up a 1BPP offscreen display for Grlib and also sets up a UDMA job that transfers the display buffer to the SPI port for the MSP to collect.
The SPI connection is set up to transfer 16 bits at a time, allowing for 4 pixel updates for each transfer. With the SPI clock running at 8Mhz, the display can update at ~51 Hz.
 
I had the first PCBs made by OSH park and am currently trying to iron out some bugs in the bias voltage section. As soon as that is done, I will be adding schematics and the board layout on github.
 
Code and documentation can be found here:
 
https://github.com/hvontres/LCD-Controller
 
 
Here is a picture of the current project:
 

 
Here is the first prototype:

 
a picture of just the controller:

 
controller mounted below launchpad:

 
 
Here is a video demo showing the different modes of the main application:
 

 
The video starts with the splash screen, inverts the display, animates the splashscreen using grlib, displays text using grlib functions and finally shows some test images downloaded in 8 pixel chunks from the host. The current code allows for 30 chunks per transfer, so that is why the screen updates are a little slow. I'll try to get some better video soon.
 

What is the input capacitance for your scope probes? For fast square waves, I built one of these: http://koti.mbnet.fi/jahonen/Electronics/DIY%201k%20probe/
For this to work, your scope needs to either have a 50 Ohm input mode or you need to use an inline 50 Ohm terminator. This will give you ~1Ghz response for only a couple of $

What is the input capacitance for your scope probes? For fast square waves, I built one of these: http://koti.mbnet.fi/jahonen/Electronics/DIY%201k%20probe/
For this to work, your scope needs to either have a 50 Ohm input mode or you need to use an inline 50 Ohm terminator. This will give you ~1Ghz response for only a couple of $