Jump to content


  • Content Count

  • Joined

  • Last visited

  1. Yes, our racing car was very successful. We finished on second place at formula student event in czech republic in summer. CAN with Launchpads was working very good, no problems.
  2. Nice project! If you add one more phase current measurement you could easily go for sensorless field oriented control with space vector pwm...
  3. Please note that this statement does not allocate any memory for your received string: char stringrecv[]=""; There could be strange effects when your code gets more complex since the memory area of your stringrecv array is not protected and could be overwritten by other variables. An common solution is to define a fixed buffer size: #define UART0_BUFFER_SIZE 32 ... char stringrecv[uART0_BUFFER_SIZE]; //32 bytes will be reserved for this array ...
  4. Hey Yosef, some hints: 1) in your systick.c file FPCU define is missing a zero. Your FCPU is 5Mhz but should be 50MHz. 2) You have to pull RS low before writing a instruction, so that the instruction register is selected. RS Low --> Put Instruction Data on 4 Data Pins --> Enable High --> Wait >42us --> Enable Low --> Wait >42us Your Enable Pulse is just some Instruction cycles long, on 50Mhz these are just a few nanoseconds. That's way too short.
  5. There are some CAN examples in the StellarisWare\examples\peripherals\can folder. Thats a better point to start with CAN.
  6. Hi and welcome to the world of easy programming and not-caring-about-register-bits! ;-) A big advantage of the Stellaris controllers is the driverlib, which makes it very easy to use peripherals like timers. This is an example of how to configure a periodic 100ms-timer with Timer0A with the driverlib. You can easily switch to 1s timer by changing the divider in the TimerLoadSet function call. You have to install StellarisWare to use this code http://www.ti.com/tool/sw-lm3s #include "driverlib/timer.h" #include"inc/hw_timer.h" //******************************************************
  7. Short update: Gyro and Acceleration Sensors are working, CAN and external power supply is not tested yet.
  8. Hi! This is a cool project, lots of work! I like that you share your iteration steps, very interesting to see. Why do you use a seperate 3.3V supply? TI Hercules should have a 3.3V supply on board. Your reverse voltage protection is a good idea with this mosfet but might be a little oversized. In most cases a reverse protection diode will do the job. For the relay drivers I can reccomend just simple MOSFET switched controlled by 3.3V - BSS123 is a good type to start. With DC motor half bridge driving you can use regenerative braking by activating the upper MOSFET, energy flows
  9. Hi Oldie, what do you think about this one: It has same size as the launchpad, features a STMicro Gyro and Acc-Sensor (no need to place these if you dont need them). The voltage regulator is a standard 7805 type, so you can drive the supply with a input voltage up to 35V (but you should avoid high currents due to high power loss at the regulator). The 120 Ohm terminator is removable by a solder jumper, all connectors are 90 degrees types. Board is not tested yet, will be tested in february. Some other features: -5V digital output, swithced with mosfet -UART3 routed to
  10. Hi! At these high currents you should consider using a switched power supply. You can create designs easily with TI Webbench http://www.ti.com/lsds/ti/analog/webench/overview.page Maybe you should just check, how much 5V power you really need. It might be a good idea to use 12V relays and switch them with 3.3V driven MOSFETs.
  11. Hi! Prescaler (in simple words) means that the clock driving your Timer is divided by 500 - your timer counts 500 times slower than the system clock speed. Let's assume a system clock of 80Mhz: 80Mhz / 500 = 160kHz --> 1/160kHz = 6,25µs for one counter step. Your Timer is loaded with a start value of 60000 and counts down to 0. So you have 60000 steps * 6,25µs = 0.375s - that is your timer period for one full count from 60000 downto 0. Or as equation - easy to adapt for different values of Prescaler, TimerLoad and System Clock: TimerPeriod = 60000 * 500 / 80MHz.
  12. Uploading the BareMinimum Sketch helped, upload was succesful. Every other project works after uploading BarMinimum once. Thanks a lot for your help!
  13. Any news about this problem? I get this error on Win8.1 x64, on USB2 and USB3 Ports. Erasing LM4F Flash doesn't help, Restart doesn't help. Uploading was working once, then never again.
  14. hehe our mechanical engineers say you are wrong. ;-) Engine maximum torque is 240Nm per engine, we have 2 engines (seperated for left and right rear wheel) and a gear ratio of 1:1.8. So final maximum torqe at the wheel is (in theory ;-) ) 864Nm (637lbft). This torque is only used when accelerating to maximum speed
  15. Yeah it's beast. Top speed will not be that high, it's not required in the formula student contests. Top speed is 130km/h (80mph). Acceleration is what this car is made for: 0-100km/h (0-60mph) in under 4 seconds. Engine torque has to be controlled at any time, especially while starting to accelerate. At the moment we produce the steel frame, our drivetrain is already running on a test setup at our university. I'll put some updates here, especially when the launchpad stuff gets implemented.
  • Create New...