Why does the CANdb Mode Signal get stored with an incorrect value in the Embedded Target for Motorola MPC555 1.1 (R13SP1)?

Question

MathWorks Support Team am 27 Jun. 2009

0
Verknüpfen

Direkter Link zu dieser Frage

https://de.mathworks.com/matlabcentral/answers/91795-why-does-the-candb-mode-signal-get-stored-with-an-incorrect-value-in-the-embedded-target-for-motorol

Akzeptierte Antwort: MathWorks Support Team

I am packing information into a CAN message using the CANdb blocks from the Embedded Target for Motorola MPC555 1.1 (R13SP1), and using mode signals. The mode signal input is not of data type 'double', and is getting packed with incorrect value into the CAN message.

Melden Sie sich an, um diese Frage zu beantworten.

Answer 1

MathWorks Support Team am 27 Jun. 2009

0
Verknüpfen

Direkter Link zu dieser Antwort

https://de.mathworks.com/matlabcentral/answers/91795-why-does-the-candb-mode-signal-get-stored-with-an-incorrect-value-in-the-embedded-target-for-motorol#answer_101146

This bug has been fixed in Release 14 Service Pack 2 (R14SP2). For previous releases, please read below for any possible workarounds:

This limitation has been addressed in R14 and other datatypes for the Mode signal are supported.

In Embedded Target for Motorola MPC555 1.1 (R13SP1), incorrect packing / unpacking of the CANdb Mode signal may occur if the datatype specified for the Mode signal input / output is not 'double'. Currently, to work around this issue, try changing the datatypes in your model (possibly using a data type conversion block) to make sure that the Mode signal is always specified as 'double'.