Hi Vishwesh,
Visual Studio official documentation provides guidance on this topic. There is quite a bit of other guidance regarding this error across stack overflow and other programming sites as it often relates to the build process, loading the wrong dll, caching of symbols, etc.
A few other thoughts related to PLECS integration:
- If PLECS has crashed, use your task manager to ensure no
plecs.exeinstances are lingering. Windows will not unload a DLL while the process lives and VS will silently keep stale symbols. You want to ensure you’re connecting to the correctplecs.exeinstance. - Best practice would be to attach the debugger before running the model in PLECS.
- If the same DLL is loaded multiple times in one simulation or even multiple different simulations one needs to be cautious.
Regards,
Bryan