trungkiena6

Post up if you see any good deals! 
Also feel free to create your own thread with the deal. I'll link to your threads from this post.
 

Hi everyone!
 
We

Thanks for sharing!

*expires after 50 uses.

im back, been really busy with life and work. (the quick update, lost a job, got a job, had a baby, adopted a family, moved...etc, basicly went from me to having me and 4 others in my household)
 
 
looks like I missed a lot. now time to catch up on all the new posts.......
 
 

Hi 43oh!
 
Some of you may have seen me over at c2kcentral, but I'm mostly a lurker here.  For a while now, I've been working on developing a low cost quadcopter.  Well that quadcopter is nearly done!  Boards are being manufactured as I type this, and I plan to have it flying at the Bay Area MakerFaire in May.
 
Here's a picture of the top of the motor driver board:

 
Personally, I would like to see this manufactured and sold, but before I invest the effort to do that I need to ensure there is a demand for such a board.  The finished quad will be about 1 square foot in size, will cost ~$200, and will be able to carry a small payload (I've got my fingers crossed we'll have enough thrust for a Go Pro).  If you would please take a second to answer the poll as to whether or not you would be interested in purchasing one.
 
This is all very preliminary, but I appreciate any feedback you may have.
 
Thanks!
 
Edit:
Moving some of the information regarding the setup up here:
 
4x TMS320F28027F + DRV8312 make up the ESC.  That is the bulk of what is on the board which you can see on the first post.
1x C2000 LP acts as the brain.  This board decodes the control signals and sends torque commands to each of the ESCs via a PWM signal.  This LaunchPad runs the open source AeroQuad firmware on top of Energia...which also means other LaunchPads could be used as the brain.
Control Inputs come via a standard RC 2.4GHz radio and receiver.  Because the LaunchPad doesn't have 1 million capture inputs I am using a receiver which supports S.Bus.
3 axis accelerometer, gyro, magnetometer, barometer and GPS
 
Update 4/16:
Got the IMU board in today.  Here's a picture:

 
Yellow - TC6000GN - CC4000 based GPS
Red - MPU6000 - 6 axis IMU
Blue - HMC5983 - 3 axis Mag
Purple - MS5611 Barometer
 
Update 4/21:
Got in a car accident and have been dealing with insurance, so instead of working on this I've been dealing with BS.  Good news is that all that is finally taken care of and the motor boards are here!  These are by far the most complex and visually appealing boards I've even designed.  Take a look:

 
I'm still waiting on a few structural pieces to arrive which are being water cut.  I expect I'll have them later this week.  I'll post some more pictures once I get the boards assembled.
 
Update 4/22:
Motor boards are assembled and basic functionality checks out.  Next checks will include JTAG connectivity, and then motor drive capability.  The design is based off an earlier prototype that was proven out, so I expect everything to work splendidly on this board.

 
 
If you're not already, follow me on twitter for up to the minute project updates! @yertnamreg1218
 
Update 4/24:
The 4 InstaSpin Piccolos are all in a JTAG chain.  Initially I had a little trouble getting CCS to connect, but after a little re-soldering of the ICs JTAG started working.  I now have all 4 device programmed with the motor control software.  I was also able to verify operating on a battery and the serial data link between the receiver and main microcontroller.

 
Yes, I'm aware my desk is a mess right now. :-P
 
Update 5/6:
Lots of work has been going into the AeroQuad firmware I'll be running on the LaunchPad.  The two main contenders for firmware were Arducopter and Aeroquad.  The reason Aeroquad was chosen over Arducopter was their use of the standard Arduino IDE to build their firmware.  Arducopter uses a hacked together one off build system.  Since Energia is based off Arduino, getting the AeroQuad project to build was much easier than Arducopter would have been.  
 
With that said, I'm happy to announce that today I was able to compile AeroQuad successfully for the C2k LaunchPad in Energia.  This is a huge milestone!

 
As you can see it didn't link, but that's an easy problem to fix.  With MakerFaire less than 2 week away, the pressure is on!  Will Trey get the quadcopter flying in time or will Murphy raise his evil head and sabotage the project?  Stay tuned to find out!
 
Update 5/23:
After my last update I had to really focus on getting the thing done in time for MakerFaire, so I slacked off on project updates.  Sadly, Murphy paid me a visit and threw a few wrenches into my plan.
 
Problem #1: Everything on the motor drive boards appears to be working as planned with the exception of the current feedback circuitry for the motors.  The old board can spin the motors just fine, but on the new board the current feedback isn't behaving nicely which is causing us problems with the motor control software.  The boards are based on the same schematic, but the original developer changed some of the components in the feedback circuitry.  I have a list of the changes and the new board has incorporated those changes, but still has problems.  I'm unsure if the issue is layout or component related and will be doing some experiments in the coming weeks to determine and fix the cause.
 
Problem #2: I pulled a special favor to get the structural materials (i.e. frame) for the quadcopter cut on a waterjet.  I kicked this off in early April, but because it was a favor and there were other users of this machine my parts didn't end up getting cut in time.  I'm currently looking for a place in town that can do CNC routing and drilling to get these parts cut.
 
MakerFaire was still a big success and I was able to talk to a ton of people about LaunchPad, Energia, and the quadcopter.  I even met a few 43oh members while I was there!  I also talked to the creators of the Aeroquad firmware and they are very excited about this project.  Once the C2000 port is more stable I will be merging my changes upstream to the main Aeroquad repository.  
 
I also talked to them about structural materials for the frame.  The Aeroquad guys use a material called DiBond.  Its a composite aluminum/polyethylene laminate which is less dense than FR4 with comparable material properties.  It is commonly used in signage applications, but also makes for an excellent quadcopter frame.  At MakerFaire the AeroQuad team participated in an event called the "Game of Drones".  This event pitted two quadcopters against eachother in air to air combat.  Take a look at this video showing off some of the fights: 
 

http://youtu.be/91OCQ-1KP08
 
After seeing how well they performed in the competition I am considering switching to use DiBond as the structural material in my quadcopter as well.
 
Update 8/19
It took me a while to find someone to cut the frame at a reasonable price, but I finally did.  I just received the frame back from the fabricator and it looks great.  I'll still need to tweak the design a bit due to machining tolerances, but that's something that's easily accomplished.  Without further ado, here are the pics:

 

 
There are some spars that connect the two pieces together that should also be here, but the fabricator was confused and thought they were scrap.  I should be able to fully assembled the quad after I get back the tweaked version of the frame.
 
I also was lucky enough to be a guest on "The Amp Hour" this week.  Be sure to tune in!  I talk about my experience in college at Rose-Hulman, my first job after college with Simma Software, and I reveal a new job I've accepted at TI!!!!

Only an hour left in 2013. Here's wishing you all a Happy New Year!
 
Thanks for all your contributions and support. Have a wonderful new year.

Thanksgiving is here! Now is a good time to accessorize your Launchpad with Boosterpacks from The 43oh Store. Get 15% off on any order placed between now and December 2nd, 2013 using the coupon code below. To top it off, your order ships free!(US Only*). Our stock is limited, so clamor on and don't hold back! Your purchase keeps our community running.

Gifting someone a kit? The IV-18 VFD Clock Kit is a perfect gift, even if you are purchasing it for yourself. The LPB Protoboard and Robg's Protopad are perfect for prototyping projects on your Launchpad.

Also, do not forget to enter your projects in the November-December Project of the Month Contest. We have prizes from Panavise, Saleae, Saelig, Total Phase, CircuitCo, Pervasive Displays, DLP Design, Robot Shop, Elecrow and ourmembers. There is a big chance that you might win a prize!

 

Code(US) : GIVETHANKS

Code(International) : ITHANK

 

Thanks and Happy Thanksgiving!

 

* We apologize for not being unable to ship international orders for free. If you do order, please use code ITHANK for 15% off your order.

You have a PM.

I spotted this over on the Stellarisiti forum. TI have a $25 coupon valid until 30 Sept. It seems to be valid for Launchpads and maybe more. (I ordered a Tiva and F5529 LP and all seemed OK.) Just enter National-1yr at the checkout.
 
A quick Google mentions something about National customers, so if this shouldn't be valid for everyone then please delete this thread. TI are good enough with low priced LaunchPads, free shipping and generous samples - I wouldn't want to be encouraging any misuse.

forum.43oh.com went down today at ~18:00 EST. With @@GeekDoc's help, we found that a php error was constantly being logged into an error_log file which when reached the 2GB file limit brought the site down. File has been deleted, but the error keeps getting generated. 
 
I've contacted our hosting to see if they can help identify the root cause of the error. Will keep you posted.
Thanks for all those who contacted us.

The following are the winners of the raffle C5000 Audio Capacitive Touch BoosterPack:
 

1. Place: C5000 Audio Capacitive Touch BoosterPack @pyrosster

 
Congratulations!

Hi all!
 
Just wanted to share my led cube boosterpack with everyone.
 
This is basically a sized reduced version of my last led cube that was built using the ek-lm4f232 and a hand built protoboard:
 
http://forum.stellarisiti.com/topic/268-8x8x8-led-cube/
 
That took way too much time so a sized reduced PCB was the next goal. The code now supports both the ek-lm4f232 and ek-lm4f120xl LaunchPad. In addition, there's no reason why the MSP430 or C2000 and all future LaunchPads couldn't be used as the BoosterPack only makes use of the outside pins.
 
I'll be posting updates here periodically:
 
https://code.google.com/p/stellaris-led-cube-v2/
 
 

 

 

 

I think you should use CCS. Because all example you can get at TI web. Write code by CCS

This is example code

#include "inc/hw_memmap.h" #include "inc/hw_types.h" #include "inc/hw_timer.h" #include "inc/hw_ints.h" #include "driverlib/timer.h" #include "driverlib/interrupt.h" #include "driverlib/sysctl.h" #include "driverlib/gpio.h" #include "utils/uartstdio.h" //***************************************************************************** // //! \addtogroup timer_examples_list //! 16-Bit Periodic Timer (periodic_16bit) //! //! This example shows how to configure Timer0B as a periodic timer with an //! interrupt triggering every 1ms. After a certain number of interrupts, the //! Timer0B interrupt will be disabled. //! //! This example uses the following peripherals and I/O signals. You must //! review these and change as needed for your own board: //! - TIMER0 peripheral //! //! The following UART signals are configured only for displaying console //! messages for this example. These are not required for operation of //! Timer0. //! - UART0 peripheral //! - GPIO Port A peripheral (for UART0 pins) //! - UART0RX - PA0 //! - UART0TX - PA1 //! //! This example uses the following interrupt handlers. To use this example //! in your own application you must add these interrupt handlers to your //! vector table. //! - INT_TIMER0B - Timer0BIntHandler //! // //***************************************************************************** //***************************************************************************** // // Number of interrupts before the timer gets turned off. // //***************************************************************************** #define NUMBER_OF_INTS 1000 //***************************************************************************** // // Counter to count the number of interrupts that have been called. // //***************************************************************************** unsigned long g_ulCounter = 0; //***************************************************************************** // // This function sets up UART0 to be used for a console to display information // as the example is running. // //***************************************************************************** void InitConsole(void) { // // Enable GPIO port A which is used for UART0 pins. // TODO: change this to whichever GPIO port you are using. // SysCtlPeripheralEnable(SYSCTL_PERIPH_GPIOA); // // Configure the pin muxing for UART0 functions on port A0 and A1. // This step is not necessary if your part does not support pin muxing. // TODO: change this to select the port/pin you are using. // GPIOPinConfigure(GPIO_PA0_U0RX); GPIOPinConfigure(GPIO_PA1_U0TX); // // Select the alternate (UART) function for these pins. // TODO: change this to select the port/pin you are using. // GPIOPinTypeUART(GPIO_PORTA_BASE, GPIO_PIN_0 | GPIO_PIN_1); // // Initialize the UART for console I/O. // UARTStdioInit(0); } //***************************************************************************** // // The interrupt handler for the Timer0B interrupt. // //***************************************************************************** void Timer0BIntHandler(void) { // // Clear the timer interrupt flag. // TimerIntClear(TIMER0_BASE, TIMER_TIMB_TIMEOUT); // // Update the periodic interrupt counter. // g_ulCounter++; // // Once NUMBER_OF_INTS interrupts have been received, turn off the // TIMER0B interrupt. // if(g_ulCounter == NUMBER_OF_INTS) { // // Disable the Timer0B interrupt. // IntDisable(INT_TIMER0B); // // Turn off Timer0B interrupt. // TimerIntDisable(TIMER0_BASE, TIMER_TIMB_TIMEOUT); // // Clear any pending interrupt flag. // TimerIntClear(TIMER0_BASE, TIMER_TIMB_TIMEOUT); } } //***************************************************************************** // // Configure Timer0B as a 16-bit periodic counter with an interrupt // every 1ms. // //***************************************************************************** int main(void) { unsigned long ulPrevCount = 0; // // Set the clocking to run directly from the external crystal/oscillator. // TODO: The SYSCTL_XTAL_ value must be changed to match the value of the // crystal on your board. // SysCtlClockSet(SYSCTL_SYSDIV_1 | SYSCTL_USE_OSC | SYSCTL_OSC_MAIN | SYSCTL_XTAL_16MHZ); // // The Timer0 peripheral must be enabled for use. // SysCtlPeripheralEnable(SYSCTL_PERIPH_TIMER0); // // Set up the serial console to use for displaying messages. This is // just for this example program and is not needed for Timer operation. // InitConsole(); // // Display the example setup on the console. // UARTprintf("16-Bit Timer Interrupt ->"); UARTprintf("\n Timer = Timer0B"); UARTprintf("\n Mode = Periodic"); UARTprintf("\n Number of interrupts = %d", NUMBER_OF_INTS); UARTprintf("\n Rate = 1ms\n\n"); // // Configure Timer0B as a 16-bit periodic timer. // TimerConfigure(TIMER0_BASE, TIMER_CFG_16_BIT_PAIR | TIMER_CFG_B_PERIODIC); // // Set the Timer0B load value to 1ms. // TimerLoadSet(TIMER0_BASE, TIMER_B, SysCtlClockGet() / 1000); // // Enable processor interrupts. // IntMasterEnable(); // // Configure the Timer0B interrupt for timer timeout. // TimerIntEnable(TIMER0_BASE, TIMER_TIMB_TIMEOUT); // // Enable the Timer0B interrupt on the processor (NVIC). // IntEnable(INT_TIMER0B); // // Initialize the interrupt counter. // g_ulCounter = 0; // // Enable Timer0B. // TimerEnable(TIMER0_BASE, TIMER_; // // Loop forever while the Timer0B runs. // while(1) { // // If the interrupt count changed, print the new value // if(ulPrevCount != g_ulCounter) { // // Print the periodic interrupt counter. // UARTprintf("Number of interrupts: %d\r", g_ulCounter); ulPrevCount = g_ulCounter; } } }
When i debug. what i can see. Sr about my question. Because i try to know about stellaris. This is the first MCU ARM i had studied.
Thanks all
 

What do use as a serial terminal?

Hi Trungkiena6,
 
You could download EK-LM4F120XL LaunchPad Workshop Student Guide and Lab Manual from TI site.
 
It includes a nice tutorial for interrupts and the timers.
 
Cheers
 
Bernard
 
 
 
 
 

It would be easier of you could tell us what you know first. That way we can guide you. If you are trying to implement one, there are a few simple  timer examples in the StellarisWare boards folder. Also read the datasheet of the chip and the driver library pdf in the Stellarisware docs library.

I am confused - what specifies the 2.5 divisor? 
The code sample looks like it specifies a divisor of 2.  Wouldn't you need to use (SYSCTL_SYSDIV_2_5 to get PLL/2.5 )
 
For instance project0.c uses SYSCTL_SYSDIV_4 and comments say the resulting clock is 50 MHz (200 MHz / 4 = 50 MHz)
So I would have thought that the code given here would specify a 100 MHz clock?
(Of course not all parts can reach a 100 MHz clock).

I'm sorry for late reply.
As bluehash said, first install stellarisware and add Uartstdio.c

You can download that folder from TI.
http://www.ti.com/tool/sw-ek-lm4f120xl

You need to add or link the following  files to your project. You can find them in the utils folder of Stellarisware. Right click on your project and click add files.
 
- Uartstdio.c

Hi,
 
Thank You for your question. 
I'm a beginner too with Stellaris. I can debug UARTprintf function.
 
Possible sources of the problem:
 
Case 1: Because I used the StellarisWare library files:
"If you are playing around with the code and get the message “No source available for 
…”, close that editor tab. The source code for that function is not present in our project. It  is only present as a library file." /Stellaris WorkShop WorkBook, page 3-18/   Case 2: After the MCU has entered to hibernation mode, CCS loses connection with the LaunchPad, because the MCU is not powered. When it wakes again, CCS can't connect again. "Note: Code Composer Studio has some issues connecting to hibernating devices (and re- connecting) since they essentially power off in the middle of the debugging process.  We’ll try to step around those issues, but you may see CCS terminate abruptly. If this  happens, you can restart CCS and try again, or you can use the LM Flash Programmer to  reprogram the device with the qs-rgb (non-hibernation) program. In either case, you need  to hold SW2 down to keep the LM4F device awake in order for either tool to connect." /Stellaris WorkShop WorkBook, page 6-10/  

Since you are using the PLL which is at 400Mhz and then that is divided by 2. It is further divided by the divisor you specified which is 2.5
400Mhz/2/2.5 = 80Mhz
 
You can also get the current clock by issuing the following code after the above:
unsigned long SysCtlClockGet(void)