This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

MSP430FR4133: MSP430FR4133 and MSP430F5132

Part Number: MSP430FR4133
Other Parts Discussed in Thread: MSP430F5132, TIDA-01353

Hello,

We are using MSP430F5132 to drive a BLDC motor and MSP430FR4133 to control the motor speed through IR communication. Our plan is to consolidate the two mentioned micro-controllers to a single micro solution.

Can we use MSP430FR4133 to drive the BLDC motor and run IR remote control? Your URGENT response will be greatly appreciated.

Thanks 

  • Hi Ron

    What's the function in MSP430F5132? Just turn on and off ?Or add the direction of rotation?

    Best regards
    Gary
  • Hi Ron,

    which resources do you use on MSP430F5132?
  • Hi Gary,

    Actually we are using this design from TI ( http://www.ti.com/tool/TIDA-01353

  • Hi Tomasz,

    Actually we are using this design from TI ( www.ti.com/.../TIDA-01353 ) where MSP430F5132 is used to control the BLDC motor speed.



    Thanks,

    Ron
  • Hi Ron,

    it will take me a while analyze which resources, I mean timers, PWM, clecks, etc., are used by www.ti.com/.../TIDA-01353 .
    Your link does not tell me which resources you use.
    I do understand that your project is commercial, however, if you do not help me I cannot help you.
  • Hi Ron

    Tomasz is right. To evaluate the solution you should analysis which resources you need, like how many of PWM, timers, ADC or memory you need.To see MSP430FR4133 can cover this. If so, you can just use one chip to control the motor.

    Gary
  • The TIDA-01353 Report (TIDUCE0A) says that its F5132 software (a) runs at 25MHz (b) uses TimerD for motor PWM (c) uses the TEC for overcurrent feedback.

    The FR4133 (a) is limited to 16MHz (b) doesn't have TimerD (c) doesn't have a TEC.

    Timer D provides very high (256MHz) resolution PWM/Capture, and the TEC provides feedback directly into the PWM generator. It was clearly designed with motor control in mind, and I suspect is a prime motivation behind this Reference Design. As far as I know the only MSP430s (ever) with the TimerD/TEC are in the F51xx series.

    The Report says that it uses the InstaSPIN technique, but as near as I can tell InstaSPIN libraries are only available for the C2000, so it's presumably locally coded. (I haven't been able to locate the source code.)

    All things are possible, I suppose, but this sounds like a significant porting/re-implementation task, and it may not work as well as the original.
  • Hi Ron,

    sorry for being silent.
    Time_D and TEC usage in your project is still an assumption because you could make some changes to the original project example.

    Assuming that you have not changed the original architecture,
    the TEC feature that connects different Timer_D module instances to each other and routes the external signals to the Timer modules,
    could be the key to your design.

    Assuming the above you are limited to Time_D and TEC:
    MSP430FR57xx, MSP430FR58xx, MSP430FR59xx, and MSP430FR6xx families does not support Timer_D, nor TEC.

    In your situation, I would consider a usage of C2000 family.
    I would do everything to avoid InstaSPIN on MSP430.

**Attention** This is a public forum