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.
Hi
I have done a PCB with theMCF8316A and all is fine so far.
But when I read out values over the I2C while the motor is spinning. The Motor stop suddenly ( about 1...60 min) or hang with one winding under Power.... and nearly heats up the motor.
the I have no control any more... only power off helps.
I tried to optimize I2C ... with delay ... 100Khz, 400Khz... alle the same.
In the Internet I found that this was aksed 2 Years ago.
e2e.ti.com/.../mcf8316a-driver-stops-working-while-reading-register-with-i2c
Now my questions?
1. Is this already solved?
2. Workarround?
3. If not it would mean I can't use the I2C to control speed during running with a application?
4. is that the same for MCT8316A ( I also have a application with that)
BR
Andreas
Hi Andreas,
This is a known Errata on the MCF8316A (#8 in this E2E FAQ). Unfortunately, the workaround is to not read/write registers constantly during motor operation. If constant speed adjustment is needed, you'd need to use PWM or analog speed input to avoid encountering this errata.
This errata is only present on the MCF8316A, and has been fixed in the MCF8316C with updated firmware (only Q1 available now). MCT8316A or other Trap devices are not affected by this errata.
Regards,
Eric C.
Hi
this is very sad... also my customer is not realy happy. -> At least you sould update the Datasheet since it's 2 years old!!
I fact it meas I can not even change the speed while the motor is turning. Right?
So only PWM/Analog is working stable?
Other question:
Is the error only happen then I talk with MCF8316A device or also when I2C communication with other device when motor is turning?
The FAQ does not specify this and it would kill my project.
BR
Andreas
Hi Andreas,
Yes, unfortunately this means that we recommend using Analog/PWM for speed control to completely eliminate the risk of encountering the issue.
Due to the nature of the bug, the more I2C commands are sent, the more chances there are to triggering the bug, therefore if you are changing the speed constantly during motor operation, there will be a higher chance of encountering this issue.
This issue only occurs when I2C commands are addressed to the MCF8316A while motor is spinning. Other communications on the same I2C bus to other devices should not affect the motor operation.
Regards,
Eric C.