0
Under review
Slow cycle time on MD5
It appears the fastest application cycle time on the MD5 currently is 50ms, which is 5x what it was on the MD4. Is this something that is planned to be improved in a future software or firmware release?
I need to be able to send out 10ms messages and it is just not possible from what I can tell on the the MD5 series.
Customer support service by UserEcho
The cycle time on the MD5 has been limited to 50 ms, when performing development tests at shorter cycle times we still see too much fluctuation in application cycle utilization and jitter in the time between period CAN messages.
We have ideas on how this could be improved, but until we have it working I don't want to promise a shorter cycle time.
My recommendation is to allocate fast messages on an MC4x/MC4xFS controller.
We currently use MD4, but I will have the same problem when upgrading to MD5. The transmission control units that equip our machines do not allow transmission rates exceeding 20 ms for some of their messages, which are also protected with CRC calculation. If I reduce the message transmission rate below the cycle time, the CRC will not be calculated correctly.
What is the solution to this problem? We would like to install MD5 on our machines, but we need to find a solution to this problem.
They're trying to push everyone to multi-master. We're moving from MD4/XC43 to MD5/MC43FS to alleviate.
The MC43 can send the fast messages and be a true machine controller while the MD5 becomes only an HMI.
This problem will affect more customers, as it is happening to us with one of the most common transmission brands, which is updating its hardware in its new models and now requires this cycle speed.
It is not the right solution to launch a new series of components with lower specifications than the previous one.
Using a multimaster system in applications that work properly with a single master is a waste of component costs and adds unnecessary steps in programming.