How to prevent EC0E on Quantum CPU by optimizing the XXMIT
Question:
Customer met with Quantum CPU crash of code EC0E when manipulating the XXMIT function in Unity Pro. What is the resolution on that?
Answer:
The crash is due to weakness in communication buffer management which is fixed by Unity Pro 11.
Prior to the unity upgrading, there is a way to optimize the process on XXMIT to prevent the crash.
Please take the following two adjustment at application level to prevent the next occurence.
1. The MSGIN is size of response buffer from slave and it should be of sufficient length.
Size of MSGIN (Msg_IN in this application) should correspond to number of words asked in the parameter (Modbus_Master_Output_Massage [2]).
2. Use one XXMIT to handle multi messages with multi parameters is suggested using following procedure.
step1: in case of error or done the Start bit(EN and ENO are not used in XXMIIT and it is mentioned in document also. ) should be set to 0
step2: change the "Modbus_Master_Output_Massage" during XXMIT disabled
step3: enable the XXMIT again to take into account the new parameters.
Customer met with Quantum CPU crash of code EC0E when manipulating the XXMIT function in Unity Pro. What is the resolution on that?
Answer:
The crash is due to weakness in communication buffer management which is fixed by Unity Pro 11.
Prior to the unity upgrading, there is a way to optimize the process on XXMIT to prevent the crash.
Please take the following two adjustment at application level to prevent the next occurence.
1. The MSGIN is size of response buffer from slave and it should be of sufficient length.
Size of MSGIN (Msg_IN in this application) should correspond to number of words asked in the parameter (Modbus_Master_Output_Massage [2]).
2. Use one XXMIT to handle multi messages with multi parameters is suggested using following procedure.
step1: in case of error or done the Start bit(EN and ENO are not used in XXMIIT and it is mentioned in document also. ) should be set to 0
step2: change the "Modbus_Master_Output_Massage" during XXMIT disabled
step3: enable the XXMIT again to take into account the new parameters.