Jump to content

msptest6

Members
  • Content Count

    152
  • Joined

  • Last visited

  • Days Won

    1

Reputation Activity

  1. Like
    msptest6 reacted to FrostyTheDadMan in Hello from The Show Me State   
    Hello All
    My name is Jeff Lampe.
    I go by Frosty for short,, I got the name FrostyTheDadMan from one of my best friends 6 months after my Son was born, He is still my Pride and Joy 11 years later. ;o)
    Just in case anyone was woundering.
     
    I am also FrostyTheDadMan on WWW.Laserholics.com
    Here is a link to a simulataion I did for Phil Dixon of the FAA that was a 50mW 532nm laser at 1000 feet. We also had a major hand in the new Laser Laws the post after the phone call from phil Dixon
     
    My 40 Watt 808nm and a laser Vortex. the Vortex Laser is a 445nm at 1.4 Watt. The driver is my design and is small enough to fit on the end of your finger but it can push up to 3 Amp @ 5.5 Volt and pulses from 5Mhz to 200Mhz the XJA-140 445nm diodes like 40 to 50 Mhz.
    I call it the Mighty Micro Drive.
     
    I have been playing with Electronics sence my father got his Bell & Howell's Heath Kit GR-2000 TV. Yes I am almost as old as dirt. LOL
     
    We have come a long way sence then,,, Now I am trying my hand programing.
    I have a lot to learn,, I hope you all can teach an Old Dog new tricks. LOL
     
    I have a C2K launchpad and I want to program it to control a Laser Projector.
     
    Red 650nm 1.8 Watt, Blue 445nm 1 watt, and green 532nm 1 Watt
     
    The total power output will be close to 3.5 Watt to 4 Watt depending on the proper color mix.
     
    The Mirrors will be X & Y Galvos.
    I will save the rest for the proper time and place.
     
    anyway
    I'm Jeff or Frosty which ever you prefer.
  2. Like
    msptest6 reacted to TI_Trey in Protecting inputs from high voltage   
    You could potentially add some clamp diodes between the analog input and the two supply rails. We do this on the larger controlCARDs but space was limited so we omitted these on the LaunchPad. The part we use on the F2802x controlCARD is NUP4201MR6:
    http://www.onsemi.com/PowerSolutions/product.do?id=NUP4201MR6
     
    These will stand up to a little abuse, but they are really designed to protect the pins from ESD. If you put 50 volts on one of the LaunchPad pins you WILL fry the board.
  3. Like
    msptest6 reacted to oPossum in [Closed]Tell us your idea and win a free C2000 Launchpad.   
    My first project would be to get the LogicBoost logic analyzer to work with the C2000 Launchpad - because the MSP430 Launchpad app UART sucks and the C2000 Launchpad FT2232 UART rocks.
     
    The SMCLK output on P1.4 is used to clock the acquisition memory on the LogicBoost. This was done to allow up to 16 Msps sample rate. Using PWM on the MSP430 would have limited it to 8 Msps, The plan is to jumper one of the ePWM outputs of the C2000 to the P1.4 pin so it can provide a clock up to 20 MHz - the maximum spec for the SPI RAM chips. So using the C2000 will increase the sample rate a little and greatly improve the transfer rate to the host PC.
     
    I am also interested in using ePWM as an audio 'DAC' for music synth applications. Hope to get 14 bits resolution with simple PWM and maybe use the CLA to do delta-sigma modulation for 18+ bits resolution. That would make the C2000 Launchpad and Piccolo control stick great platforms for eXperimentation with digital music synthesis.
  4. Like
    msptest6 reacted to pjkim in [Closed]Tell us your idea and win a free C2000 Launchpad.   
    I am working on a servo motor controller. Stepper motors are used commonly in projects because of low cost and ease of interfacing to microcontrollers. As easy as they are to use, they have significant deficiencies compared to servo motors (DC motors with rotary encoder feedback, not hobby servo) in terms of maximum speed and torque. Servo motors have not found widespread use in the hobby community because of the cost of servo motors and controllers.
     
    I want to make them more accessible. Scooter motors can be had for $20-30 and have over an order of magnitude more torque than stepper motors of comparable price. I want to couple the shaft to an optical encoder from an old mouse. The quadrature signal from the encoder will go into the Launchpad along with step and direction pulses from a computer. The Launchpad will calculate the error signal and calculate a PWM output signal using a PID (proportional integral derivative) algorithm. The PWM signal will drive a L298N motor controller which can be ganged to provide 4A of motor current at up to 45V.
  5. Like
    msptest6 reacted to JohnnyDS in CCSv5 and C2000 launchpad - Debugger crashes   
    Dear Eelcor
     
    I have a win 7 ultimate 64 bits and until now the launchpad and the soft works very fine.
     
    But at first time I made some settings for the ccs to work.
     
    First, I made a new connection for the debugger. The connection is Texas Instruments XDS100v2 USB EMULATOR, for the Board or Device Experimenter Kit Piccolo F28027. And in Connection Properties I put the following:
    Board Data File: Auto Generate
    Emulator Selection; only one XDS100 installed
    In both Boot Mode I put the same thing DISABLE
    And the final setting I put Fixed Default 1 MHz.
     
    Before to do the test you must put S1 and Serial with all the buttons UP.
     
    And then Run the Test Configuration. If you have encounter any problem the CCS will not functioning.
     
    The program is CCS Version: 5.2.1.00018
     
    Sorry about my english.
     
    Best regards for all.
  6. Like
    msptest6 reacted to TI_Trey in What are you going to do with your C2000 Launchpad?   
    Love It!
     
    Actually I was thinking it would be really cool if we did a base board which had the Danger Prototypes case form factor. Then we could really easily put together cases for projects.
  7. Like
    msptest6 reacted to oPossum in Difference Between C2000 Launchpad and Stellaris Launchpad   
    It doesn't have the 16 motion control PWM and QEI (F21x and F23x only), but it does have the 12 general purpose PWM/CCP.
  8. Like
    msptest6 reacted to oPossum in Difference Between C2000 Launchpad and Stellaris Launchpad   
    C2000: Fast control loops - motor control, inverter control, maybe audio processing
     
    Stelaris (ARM): General purpose computing - lightweight OS, network stack, high level languages
     
     
    In some specific applications the C2000 may significantly outperform an ARM by leveraging the power of the CLA.
  9. Like
    msptest6 got a reaction from CorB in Difference Between C2000 Launchpad and Stellaris Launchpad   
    Good question! Lets see. Below is my attempt at this.
     

  10. Like
    msptest6 got a reaction from CorB in Real-Time Control - A C2000 Debugging Gem   
    A test to display a live temperature graph. The chip is pretty warm, so much so that when I place my finger on it, the temp. goes down - meaning my finger is acting as a heat sink. The temp value is the first value of the temperature array. Pretty cool.
     

  11. Like
    msptest6 got a reaction from grim in Real-Time Control - A C2000 Debugging Gem   
    A test to display a live temperature graph. The chip is pretty warm, so much so that when I place my finger on it, the temp. goes down - meaning my finger is acting as a heat sink. The temp value is the first value of the temperature array. Pretty cool.
     

  12. Like
    msptest6 reacted to TI_Trey in Problems in Example_F2802xLaunchPadDemo   
    CorB,
     
    Glad to hear things are working for you. By default I would recommend you keep all the switches in the up position during debugging. S4 really doesn't matter as it is just used to prevent contention on the serial lines should more than two devices be connected to the serial lines. S1controls how the board boots up. Basically if you are debugging you want all the switches up, if you are running standalone you want the switch on the right in the down position. There are other modes as well that can be read about in the BootROM users guide.
     
    Now on to the warnings:

    "../Example_F2802xLaunchPadDemo.c", line 373: warning: argument of type "int (*)(int, char *, unsigned int)" is incompatible with parameter of type "int (*)(int, const char *, unsigned int)" status = add_device("scia", _SSA, SCI_open, SCI_close, SCI_read, SCI_write, SCI_lseek, SCI_unlink, SCI_rename);
    This is a very minor warning. You can see the function wanted a char * and I passed it a const char *. 99.9% of the time this won't cause an issue, but it will depend on the function you are passing the messed up variable to.
     

    "../Example_F2802xLaunchPadDemo.c", line 280: warning: variable "fid" was set but never used volatile FILE *fid;
    This warning just means we saved a value in a variable but never did anything with it. Typically you'll get these when you've added variables for debugging purposes that aren't used else where in your application. These warnings may always be safely ignored.
     

    ../f2802x_common/cmd/F28027.cmd", line 117: warning: memory range not found: FLASHD. on page 0 .text : >> FLASHA | FLASHC | FLASHD. PAGE = 0
    This warning is due to a typo that snuck past me. There is a FlashD in the memory map, but in the linker file somehow a period accidentally got typed instead of a comma. If you change the line to read:

    .text : >> FLASHA | FLASHC | FLASHD, PAGE = 0
    you won't get this warning. I'm aware of this typo and it will be fixed in the next release.
     

    warning: entry-point symbol other than "_c_int00" specified: "code_start"
    All of TI's code gen tools really like your application to start with a symbol called _c_int00. We however supply a piece of code called CodeStartBranch which does some handy things like turn off the watchdog so its easier to debug. In our example applications we manually set the program entry point in the project properties to code_start. If anything other than _c_int00 is used you will get a warning like this. This warning can be safely ignored.
     
    Hope that helps!!!
  13. Like
    msptest6 got a reaction from CorB in Real-Time Control - A C2000 Debugging Gem   
    If you are not familiar with the C2000 series, you are going to love this. C2000 silicon has something known as real-time control. This allows you to watch variables in "real -time" as it changes in your controller in your watch window, through the JTAG. I put real-time in quotes as the update speed depends on your JTAG speed and the amout of data being transferred.
    I know this as I have worked with motor control alot and used the real-time feature to update FOC/current graphs in almost real time. This has been a god-send helping solve many problems.
     
    Anyway, enabling this is simple. Just follow the steps below:
    Compile your program. I'm using Example_2802xLEDBlink.c from ControlSuite in the C2000 Launchpad folder.
     
    Once compiled, press the "Debug" button.
     
    Next place the variable you want to check in the watch window. I used interruptCount++.
     
    Next click the real time button(clock with a pause sign). The button next to it gets selected automatically.This is ok.
     
    Now in the debug window, click the real time continuous refresh button above your watch window.
     
    Place play, or run your program. The variable should automatically update.

    Tips:
    - You can change the refresh rate like below.

     
    - There is something known as rude real time too, but I'm unable to find the setting. I'll update when I do.
    - You can do funky stuff with it like display graphs etc in real time.
  14. Like
    msptest6 reacted to TI_Trey in [Launchpad] Unable to get ADC examples to work   
    Sorry about the troubles with the examples. The driver library is still very new and will grow as it matures and becomes easier to use.
     
    I took a look at the examples and it looks like they are missing a few clock enables.
     
    Try replacing this:

    // Perform basic system initialization WDOG_disable(myWDog); CLK_enableAdcClock(myClk);
    with this:

    // Perform basic system initialization WDOG_disable(myWDog); CLK_enableAdcClock(myClk); CLK_enableTbClockSync(myClk); CLK_enablePwmClock(myClk, PWM_Number_1);
     
    I apologize for how dirty those examples are. The other examples for the LaunchPad aren't that way and I will get these fixed in the next release.
  15. Like
    msptest6 got a reaction from oPossum in Real-Time Control - A C2000 Debugging Gem   
    If you are not familiar with the C2000 series, you are going to love this. C2000 silicon has something known as real-time control. This allows you to watch variables in "real -time" as it changes in your controller in your watch window, through the JTAG. I put real-time in quotes as the update speed depends on your JTAG speed and the amout of data being transferred.
    I know this as I have worked with motor control alot and used the real-time feature to update FOC/current graphs in almost real time. This has been a god-send helping solve many problems.
     
    Anyway, enabling this is simple. Just follow the steps below:
    Compile your program. I'm using Example_2802xLEDBlink.c from ControlSuite in the C2000 Launchpad folder.
     
    Once compiled, press the "Debug" button.
     
    Next place the variable you want to check in the watch window. I used interruptCount++.
     
    Next click the real time button(clock with a pause sign). The button next to it gets selected automatically.This is ok.
     
    Now in the debug window, click the real time continuous refresh button above your watch window.
     
    Place play, or run your program. The variable should automatically update.

    Tips:
    - You can change the refresh rate like below.

     
    - There is something known as rude real time too, but I'm unable to find the setting. I'll update when I do.
    - You can do funky stuff with it like display graphs etc in real time.
  16. Like
    msptest6 reacted to SugarAddict in [Launchpad] Unable to get ADC examples to work   
    http://www.ti.com/tool/sprc832
     
    It's basically the commented code in the ADC example.
  17. Like
    msptest6 reacted to TomKraut in CCSv5 and C2000 launchpad - Debugger crashes   
    Before you reinstall everything, try the MProg utility from FTDI. It should see the XDS100 and display the correct id strings etc. If it doesn't, you have either a hardware or a driver problem. If it does, than CCS seems to be the culprit...
     
    Cheers
    TomKraut
  18. Like
    msptest6 got a reaction from grim in [Launchpad] Unable to get ADC examples to work   
    Is the PWM clock enabled?
     
    After

    CLK_enableAdcClock(myClk);
     
    Add

    CLK_enablePwmClock(myClk, PWM_Number_1);
     
    Does it help?
  19. Like
    msptest6 reacted to NickO1426471349 in Sensored BLDC BoosterPack   
    Chris said it, one driver per board. Simply not the room for two while maintaining the BoosterPack theme. Also as Tom said, thermal dissipation would be difficult.
     
    @Tom
    Don't know anything myself but I'll ask around. I have found the best reference for hardware designs to actually be the DRV830X EVM in control suite under development kits.
  20. Like
    msptest6 got a reaction from STiyer in Jumpers for Piccolo Kit   
    PM me. I'll send you some.
  21. Like
    msptest6 reacted to TI Motor: Chris Clearman in Sensored BLDC BoosterPack   
    This is a single inverter (DRV8302 + NEXFETs) for the BoosterPack. 24V 10A.
    We have a different development board with two inverters (single controlCARD inferface), each 24V 10A that is also in progress. This one will also include an optional dyno bench, using one of the inverters as the dyno and the other under test/control.
  22. Like
    msptest6 reacted to TomKraut in Sensored BLDC BoosterPack   
    I don't think you could cram more than one driver + fets on a BoosterPack. I have a board next to me that is approximately the size of a BoosterPack and there is no way to fit another driver + fets on it, because they don't allow parts directly under them on the bottom side. Besides, cooling them would be a nightmare!
     
    @Nick: You don't know by any chance if there is an update for the DRV8301/2 datasheet planned? The current one is a year old and missing A LOT of information which is available through threads on e2e...
     
    Cheers
    TomKraut
  23. Like
    msptest6 reacted to TomKraut in Anyone know of any xds100v3 emulator deals?   
    All XDS100 are fully capable. If you want, you can build your own from scratch, as TI has made all the schematics public.
     
    There are three different versions of XDS100 (v1 - v3). If you want it for C2000 development with CCS4 or newer, it doesn't matter which one you get (go for the v2).
     
    If you need a stand-alone XDS100 for C2000, chances are you have some skills in soldering etc... because you have build some hardware with at least one TQFP or smaller IC (the C2000... ). So why not modify a $17 LaunchPad instead of buying a $79 emulator?

    Don't get me wrong, if I were in your position, I would buy the Spectrum one as well, because I can later use it with other TI processors... In fact, I have used mine to do some Linux Kernel debugging on a BeagleBoard. I just want to point out that you don't have to do it...
     
    Cheers
    TomKraut
     
    P.S.: to answer all those questions you never had about the XDS100: http://processors.wiki.ti.com/index.php/XDS100
  24. Like
    msptest6 reacted to SugarAddict in [Piccolo] Are MSP430 BoosterPacks compatible with C2000 BoosterPacks   
    Trey: page 12 of the TMS320F28027.pdf has a typo: "Enhanced PWM external synch pulse output" I think a synch pulse would be cool
     
    On a side note... I spent a bit making this spreadsheet so I could see things on one page if anyone else finds it handy.
     
    LPComparison.zip
  25. Like
    msptest6 reacted to SugarAddict in Baseboard   
    2 simple layouts for putting under the C2KLP while still saving the extra headers. Both meant to have rubber feet, female headers upward, and a 90º male header up facing north/south...

     

×
×
  • Create New...