You can use P1.1 (A1) to P1.4 (A4) But for P1.1, P1.2 you cannot use the UART RX/TX functions when using it for ADC. And P1.3 is connected to the pushbutton on the launchpad. The only ADC without any other function that can be used in combination with the CC110L boosterpack is P1.4.
You can easily check this by looking at the pinmap of the G2553
and the CC110L
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.
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
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
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.
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
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
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!
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:
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.
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!!!!
How are you only reading through P1.3? My understanding is that for ADC10, Sequence Mode reads each channel from Ax to A0 (x corresponds to INCH_x in ADC10CTL0), so if you've started it at P1.7, it will read all 8 channels for the ADC. If that's correct, it would explain the UART issue, since it's conflicting with your UART channels on P1.1 and P1.2.
The good news is that you can do this, if you're willing to put software UART in. Use the timer output on P1.5 instead; I've just finished an experiment (using G2231) that will be posted to my blog in the next couple of days that gives an example of doing this-- I'm reading two channels in ADC10, which prevents me from using P1.1 for UART, so I moved the software UART to P1.5. It would be just as easy to change to the same on yours, using P1.4-P1.0 for the ADC channels. Or you could use TA1 on P2 instead.
Quick answer, the channels must be in sequence, so you will have to change P1.3 with P1.6.
Keep in mind that there is a hardware de-bouncer (RC) on P1.3, so you will get false readings.
P1.0 and P1.6 can be used as ADC channels, just remove LED jumpers.