Common Issues and Troubleshooting
This page summarizes frequently occurring issues and checks when using the library, including migration scenarios.
Build-time Issues
Compile error due to MPXOpen argument mismatch
- Symptom:
- Argument count error at
MPXOpencall
- Argument count error at
- Check:
- In ADL2L,
MPXOpentakes 3 arguments:Devices, Num, Count
- In ADL2L,
- Action:
- Add
Num(array length) - Ensure old ADL1L two-argument calls are removed
- Add
Link error due to old API names left in code
- Symptom:
- Unresolved symbols such as
MPXSetCANParam
- Unresolved symbols such as
- Check:
- Verify CAN APIs are renamed to
MPXCAN...
- Verify CAN APIs are renamed to
- Action:
MPXSetCANParam->MPXCANSetParamMPXGetLogEx->MPXCANGetLogExMPXSetSlot->MPXCANSetSlot, etc.
Runtime Issues
Logs are not acquired
- Symptom:
- Log count does not increase after monitoring starts
- Check:
MPXGetLog/MPXCANGetLogEx/MPXLINGetLogExis called periodically
- Action:
- Implement a periodic retrieval loop
E_STATUS is returned
- Symptom:
E_STATUSfromMPXMonitorStartetc.
- Check:
MPXCANSetParamorMPXLINSetParamis called beforehand- Call order follows the basic flow
- Action:
- Initialize according to Basic Flow
Multi-device synchronization is unstable
- Symptom:
- Start/stop timing does not align in multi-device setup
- Check:
- Start order: slave -> master
- Stop order: master -> slave
- Action:
- Follow the sequence order strictly
- See Multi-device Control Start Guide
References
- Migration guide (ADL1L): /S810-MX-ADL2L/Migration/adl1l_guide
- Basic flow: /S810-MX-ADL2L/QuickStart/common_first
- Multi-device guide: /S810-MX-ADL2L/QuickStart/multi_device_control
- CAN API list: /S810-MX-ADL2L/CAN/api_list_can
- LIN API list: /S810-MX-ADL2L/LIN/api_list_lin