Tag Archives: matlab
Section folding not present
Using R2024B, i got the option to use the live editor and some things changed without asking.
Most importantly, the + buttons to fold a section have dissappeared, while in preferences/editor/code folding the option sections is ON.
Another change is that the titles of the scripts are in an additional column.
FInally, beneath the folder section, there is a new window with the ‘script’ , i.e. a shortcut to jump to a section.
How can I get the section folding again?
Cheers, PaulUsing R2024B, i got the option to use the live editor and some things changed without asking.
Most importantly, the + buttons to fold a section have dissappeared, while in preferences/editor/code folding the option sections is ON.
Another change is that the titles of the scripts are in an additional column.
FInally, beneath the folder section, there is a new window with the ‘script’ , i.e. a shortcut to jump to a section.
How can I get the section folding again?
Cheers, Paul Using R2024B, i got the option to use the live editor and some things changed without asking.
Most importantly, the + buttons to fold a section have dissappeared, while in preferences/editor/code folding the option sections is ON.
Another change is that the titles of the scripts are in an additional column.
FInally, beneath the folder section, there is a new window with the ‘script’ , i.e. a shortcut to jump to a section.
How can I get the section folding again?
Cheers, Paul section folding MATLAB Answers — New Questions
Why is there not a button for FIK and License file?
It’s impossible to find these 2 pieces of info. Please create a button pointing to them next to the license number.It’s impossible to find these 2 pieces of info. Please create a button pointing to them next to the license number. It’s impossible to find these 2 pieces of info. Please create a button pointing to them next to the license number. fik MATLAB Answers — New Questions
Modeling load-depend friction in bearings in Simscape
Hi everyone,
i’m trying to model a five-point double-toggle lever with bearings with load-dependent friction, based on the normal-force (Coulomb, which is constant at any velocity).
I’ve tried modeling the bearing with the Multibody Interface and Rotational Friction, but i can only add a constant friction torque. When i calculate the torque using the measured normal force of the bearing, I get an algebraic loop. Is it possible to apply a load dependent Torque (Tr = Fr*d/2 = Fn*µ*d/2) and a friction force (Fr = µ*Fn) without creating algebraic loops?
Note on the image below: The force Rij is calculated as R = µ*N and acts opposite to the velocity. If R is transformed to the center, this results in atorque (T = r*R), acting opposite to the velocity.
Best greetings!Hi everyone,
i’m trying to model a five-point double-toggle lever with bearings with load-dependent friction, based on the normal-force (Coulomb, which is constant at any velocity).
I’ve tried modeling the bearing with the Multibody Interface and Rotational Friction, but i can only add a constant friction torque. When i calculate the torque using the measured normal force of the bearing, I get an algebraic loop. Is it possible to apply a load dependent Torque (Tr = Fr*d/2 = Fn*µ*d/2) and a friction force (Fr = µ*Fn) without creating algebraic loops?
Note on the image below: The force Rij is calculated as R = µ*N and acts opposite to the velocity. If R is transformed to the center, this results in atorque (T = r*R), acting opposite to the velocity.
Best greetings! Hi everyone,
i’m trying to model a five-point double-toggle lever with bearings with load-dependent friction, based on the normal-force (Coulomb, which is constant at any velocity).
I’ve tried modeling the bearing with the Multibody Interface and Rotational Friction, but i can only add a constant friction torque. When i calculate the torque using the measured normal force of the bearing, I get an algebraic loop. Is it possible to apply a load dependent Torque (Tr = Fr*d/2 = Fn*µ*d/2) and a friction force (Fr = µ*Fn) without creating algebraic loops?
Note on the image below: The force Rij is calculated as R = µ*N and acts opposite to the velocity. If R is transformed to the center, this results in atorque (T = r*R), acting opposite to the velocity.
Best greetings! simulink, friction, bearing, simscape, loop MATLAB Answers — New Questions
Custom storage class for Argument Simulink parameters identifiable by TLC script
Hi,
My objective is to define a custom storage class specifically intended for "Argument" Simulink parameters. The primary requirement is to programmatically identify which model parameters are using this custom storage class from within a TLC script executed during code generation.
I initially attempted to create the custom storage class using an Embedded Coder Dictionary. However, at code generation time, I have been unable to definitively determine which model parameters are using my custom storage class. The only observable indicator appears to be the field ModelParameters.Parameter[i].IsSpecifiedAsNewStorageClass, which is set to 1. I would appreciate confirmation on whether this is the intended mechanism or if additional fields should be accessible.
I subsequently explored the Custom Storage Class Designer, which showed promise. Upon inspection, the custom storage class appeared clearly within the TLC script context under the CustomStorageClasses record. However, as far as I know, it is not possible to define a custom storage class for "Argument" Simulink parameters this way.
Are there any aspects of either methodology that I may have overlooked or configured incorrectly?
Is there an alternative approach or recommended candidate method that would better satisfy my requirements?
Best regardsHi,
My objective is to define a custom storage class specifically intended for "Argument" Simulink parameters. The primary requirement is to programmatically identify which model parameters are using this custom storage class from within a TLC script executed during code generation.
I initially attempted to create the custom storage class using an Embedded Coder Dictionary. However, at code generation time, I have been unable to definitively determine which model parameters are using my custom storage class. The only observable indicator appears to be the field ModelParameters.Parameter[i].IsSpecifiedAsNewStorageClass, which is set to 1. I would appreciate confirmation on whether this is the intended mechanism or if additional fields should be accessible.
I subsequently explored the Custom Storage Class Designer, which showed promise. Upon inspection, the custom storage class appeared clearly within the TLC script context under the CustomStorageClasses record. However, as far as I know, it is not possible to define a custom storage class for "Argument" Simulink parameters this way.
Are there any aspects of either methodology that I may have overlooked or configured incorrectly?
Is there an alternative approach or recommended candidate method that would better satisfy my requirements?
Best regards Hi,
My objective is to define a custom storage class specifically intended for "Argument" Simulink parameters. The primary requirement is to programmatically identify which model parameters are using this custom storage class from within a TLC script executed during code generation.
I initially attempted to create the custom storage class using an Embedded Coder Dictionary. However, at code generation time, I have been unable to definitively determine which model parameters are using my custom storage class. The only observable indicator appears to be the field ModelParameters.Parameter[i].IsSpecifiedAsNewStorageClass, which is set to 1. I would appreciate confirmation on whether this is the intended mechanism or if additional fields should be accessible.
I subsequently explored the Custom Storage Class Designer, which showed promise. Upon inspection, the custom storage class appeared clearly within the TLC script context under the CustomStorageClasses record. However, as far as I know, it is not possible to define a custom storage class for "Argument" Simulink parameters this way.
Are there any aspects of either methodology that I may have overlooked or configured incorrectly?
Is there an alternative approach or recommended candidate method that would better satisfy my requirements?
Best regards code generation, simulink parameters, storage class MATLAB Answers — New Questions
DLL fails to load – matlabruntimeforpython_abi3
Hi all,
I’ve been struggling with this one for a few days now. I’m looking for proof of concept program that I can package a matlab function and then import it to my python executable. So far everything runs great in a terminal, but after using PyInstaller to generate the executable the I cannot get it to run. I’ve installed the MATLAB 2025b runtime and did install the package that was generated using the Python Package Compiler in MATLAB.
I get the following output in my command window when I attempt to launch matlab_test.exe:
My MATLAB function:
function a = matlab2python(b)
a = sqrt(b);
end
My python code:
import os
import sys
import time
import matlabsdk as sdk_python_test
import matlab
if __name__ == "__main__":
pkg = sdk_python_test.initialize()
result = pkg.matlab2python(9.0)
print(result)
pkg.terminate()Hi all,
I’ve been struggling with this one for a few days now. I’m looking for proof of concept program that I can package a matlab function and then import it to my python executable. So far everything runs great in a terminal, but after using PyInstaller to generate the executable the I cannot get it to run. I’ve installed the MATLAB 2025b runtime and did install the package that was generated using the Python Package Compiler in MATLAB.
I get the following output in my command window when I attempt to launch matlab_test.exe:
My MATLAB function:
function a = matlab2python(b)
a = sqrt(b);
end
My python code:
import os
import sys
import time
import matlabsdk as sdk_python_test
import matlab
if __name__ == "__main__":
pkg = sdk_python_test.initialize()
result = pkg.matlab2python(9.0)
print(result)
pkg.terminate() Hi all,
I’ve been struggling with this one for a few days now. I’m looking for proof of concept program that I can package a matlab function and then import it to my python executable. So far everything runs great in a terminal, but after using PyInstaller to generate the executable the I cannot get it to run. I’ve installed the MATLAB 2025b runtime and did install the package that was generated using the Python Package Compiler in MATLAB.
I get the following output in my command window when I attempt to launch matlab_test.exe:
My MATLAB function:
function a = matlab2python(b)
a = sqrt(b);
end
My python code:
import os
import sys
import time
import matlabsdk as sdk_python_test
import matlab
if __name__ == "__main__":
pkg = sdk_python_test.initialize()
result = pkg.matlab2python(9.0)
print(result)
pkg.terminate() pyinstaller, python312 MATLAB Answers — New Questions
Flexibility in Satellite Toolbox
Is there any way to both add and visualize customized gimbals and/or sensors to the satellite toolbox?
My particular scenario is looking at putting a camera on a platform but limiting the gimbal angles and field-of-view non-symmetrically.
The FOV is different in along and cross track directions (not conical). While other toolboxes have "rectangular" FOVs, I don’t see the capability in the satellite toolbox. Functions could be added to filter, but they won’t visualize properly.
My gimbals are pitch and roll rather than azimuth and elevation. I can compute the corresponding angles, but wondering if there’s a way to change how gimbals are controlled.
My gimbals don’t have complete freedom to move throughout the entire hemisphere. Again, results can be filtered but the visualization doesn’t correspond.
Is there currently (or possibly in the future) a path to customizing gimbals or sensors (with visualization) in this toolbox? Maybe an API?Is there any way to both add and visualize customized gimbals and/or sensors to the satellite toolbox?
My particular scenario is looking at putting a camera on a platform but limiting the gimbal angles and field-of-view non-symmetrically.
The FOV is different in along and cross track directions (not conical). While other toolboxes have "rectangular" FOVs, I don’t see the capability in the satellite toolbox. Functions could be added to filter, but they won’t visualize properly.
My gimbals are pitch and roll rather than azimuth and elevation. I can compute the corresponding angles, but wondering if there’s a way to change how gimbals are controlled.
My gimbals don’t have complete freedom to move throughout the entire hemisphere. Again, results can be filtered but the visualization doesn’t correspond.
Is there currently (or possibly in the future) a path to customizing gimbals or sensors (with visualization) in this toolbox? Maybe an API? Is there any way to both add and visualize customized gimbals and/or sensors to the satellite toolbox?
My particular scenario is looking at putting a camera on a platform but limiting the gimbal angles and field-of-view non-symmetrically.
The FOV is different in along and cross track directions (not conical). While other toolboxes have "rectangular" FOVs, I don’t see the capability in the satellite toolbox. Functions could be added to filter, but they won’t visualize properly.
My gimbals are pitch and roll rather than azimuth and elevation. I can compute the corresponding angles, but wondering if there’s a way to change how gimbals are controlled.
My gimbals don’t have complete freedom to move throughout the entire hemisphere. Again, results can be filtered but the visualization doesn’t correspond.
Is there currently (or possibly in the future) a path to customizing gimbals or sensors (with visualization) in this toolbox? Maybe an API? satellitetoolbox, gimbal, concialsensor MATLAB Answers — New Questions
Simulink simulation becomes very slow after adding FOC to a 6-phase PMSM drive with CHB inverter
I am simulating an asymmetrical six-phase PMSM drive in Simulink (R2025b).
The original model consisted of:
– 5-level cascaded H-bridge inverter
– phase-shifted PWM (PSPWM)
– asymmetrical 6-phase PMSM (30° phase shift)
In this configuration the simulation runs normally. After introducing field-oriented control (FOC) the simulation becomes very slow.
The FOC implementation includes:
– VSD transformation (abc-def → αβxy)
– Park transformation
– PI current controllers (id, iq, ix, iy)
– speed PI controller
– inverse transformations
– discrete current filters ( for i_αβ)
Main parameters:
– PWM carrier frequency: fcr = 5 kHz
– duty cycle update rate: 100 kHz
– solver: ode14x
– Simulink version: R2025b
The electrical model of the inverter and machine has not changed, only the control structure was added.
My question is: Is it normal that adding FOC significantly slows down the simulation in Simulink, and what are recommended practices to keep such motor drive simulations efficient (solver choice, controller sampling rates, or implementation of transformations)?I am simulating an asymmetrical six-phase PMSM drive in Simulink (R2025b).
The original model consisted of:
– 5-level cascaded H-bridge inverter
– phase-shifted PWM (PSPWM)
– asymmetrical 6-phase PMSM (30° phase shift)
In this configuration the simulation runs normally. After introducing field-oriented control (FOC) the simulation becomes very slow.
The FOC implementation includes:
– VSD transformation (abc-def → αβxy)
– Park transformation
– PI current controllers (id, iq, ix, iy)
– speed PI controller
– inverse transformations
– discrete current filters ( for i_αβ)
Main parameters:
– PWM carrier frequency: fcr = 5 kHz
– duty cycle update rate: 100 kHz
– solver: ode14x
– Simulink version: R2025b
The electrical model of the inverter and machine has not changed, only the control structure was added.
My question is: Is it normal that adding FOC significantly slows down the simulation in Simulink, and what are recommended practices to keep such motor drive simulations efficient (solver choice, controller sampling rates, or implementation of transformations)? I am simulating an asymmetrical six-phase PMSM drive in Simulink (R2025b).
The original model consisted of:
– 5-level cascaded H-bridge inverter
– phase-shifted PWM (PSPWM)
– asymmetrical 6-phase PMSM (30° phase shift)
In this configuration the simulation runs normally. After introducing field-oriented control (FOC) the simulation becomes very slow.
The FOC implementation includes:
– VSD transformation (abc-def → αβxy)
– Park transformation
– PI current controllers (id, iq, ix, iy)
– speed PI controller
– inverse transformations
– discrete current filters ( for i_αβ)
Main parameters:
– PWM carrier frequency: fcr = 5 kHz
– duty cycle update rate: 100 kHz
– solver: ode14x
– Simulink version: R2025b
The electrical model of the inverter and machine has not changed, only the control structure was added.
My question is: Is it normal that adding FOC significantly slows down the simulation in Simulink, and what are recommended practices to keep such motor drive simulations efficient (solver choice, controller sampling rates, or implementation of transformations)? simulink, motor-control, pmsm, foc, power_electronics_control MATLAB Answers — New Questions
How to place code generated from subsystem into RAM on Ti C2000?
I am trying to plase parts of the code generated from one of the subsystems into RAM to speed up execution. The help provided in Control Data and Function Placement in Memory by Inserting Pragmas is not sufficient.
Is there a better explanation on how to add #pragma CODE_SECTION(myCriticalTask, "ramfuncs") to the generated function?
Do I need to edit linker command file?
Do I need to add code to copy function from flash to RAM on power up?
Thanks.I am trying to plase parts of the code generated from one of the subsystems into RAM to speed up execution. The help provided in Control Data and Function Placement in Memory by Inserting Pragmas is not sufficient.
Is there a better explanation on how to add #pragma CODE_SECTION(myCriticalTask, "ramfuncs") to the generated function?
Do I need to edit linker command file?
Do I need to add code to copy function from flash to RAM on power up?
Thanks. I am trying to plase parts of the code generated from one of the subsystems into RAM to speed up execution. The help provided in Control Data and Function Placement in Memory by Inserting Pragmas is not sufficient.
Is there a better explanation on how to add #pragma CODE_SECTION(myCriticalTask, "ramfuncs") to the generated function?
Do I need to edit linker command file?
Do I need to add code to copy function from flash to RAM on power up?
Thanks. c2000, matlab, simulink, embedded coder MATLAB Answers — New Questions
Clarification on Sampling Rate vs. Control Bandwidth in Average Current Mode Control for Buck Converter
I am implementing Average Current Mode Control for a Buck converter. According to control theory, the voltage loop (outer loop) is typically designed to be 5–10 times slower than the current loop (inner loop) to ensure stability and proper decoupling.
However, in my current simulation setup, the ADC for both voltage and current is triggered at the same time. Does this imply that the execution frequency (sampling rate) of both control loops must be identical?
How can I implement a slower voltage loop while maintaining the same ADC sampling frequency for both signals in Simulink/Embedded C? Any insights on whether this ‘simultaneous sampling’ contradicts the principle of having a slower outer loop would be greatly appreciatedI am implementing Average Current Mode Control for a Buck converter. According to control theory, the voltage loop (outer loop) is typically designed to be 5–10 times slower than the current loop (inner loop) to ensure stability and proper decoupling.
However, in my current simulation setup, the ADC for both voltage and current is triggered at the same time. Does this imply that the execution frequency (sampling rate) of both control loops must be identical?
How can I implement a slower voltage loop while maintaining the same ADC sampling frequency for both signals in Simulink/Embedded C? Any insights on whether this ‘simultaneous sampling’ contradicts the principle of having a slower outer loop would be greatly appreciated I am implementing Average Current Mode Control for a Buck converter. According to control theory, the voltage loop (outer loop) is typically designed to be 5–10 times slower than the current loop (inner loop) to ensure stability and proper decoupling.
However, in my current simulation setup, the ADC for both voltage and current is triggered at the same time. Does this imply that the execution frequency (sampling rate) of both control loops must be identical?
How can I implement a slower voltage loop while maintaining the same ADC sampling frequency for both signals in Simulink/Embedded C? Any insights on whether this ‘simultaneous sampling’ contradicts the principle of having a slower outer loop would be greatly appreciated average current mode, cascaded control MATLAB Answers — New Questions
Amplitude Modulation using simulink
I am currently doing amplitude modulation using three very high frequency sine waves which I getting perfectly after adding all the three due to already set parameters in the simulation parameter box.
The carrier frequency is also very high, up to 3000 Hz, but the scope is displaying is correctly. But after the message signal and carrier are passing through the product, I am not getting amplitude modulated signal. Instead, I am getting a completely zero straight line. My sample time in the Product is 0.0001.
I am pretty sure it has to do something with the product parameters or simulation parameters but I so not sure exactly what it is?I am currently doing amplitude modulation using three very high frequency sine waves which I getting perfectly after adding all the three due to already set parameters in the simulation parameter box.
The carrier frequency is also very high, up to 3000 Hz, but the scope is displaying is correctly. But after the message signal and carrier are passing through the product, I am not getting amplitude modulated signal. Instead, I am getting a completely zero straight line. My sample time in the Product is 0.0001.
I am pretty sure it has to do something with the product parameters or simulation parameters but I so not sure exactly what it is? I am currently doing amplitude modulation using three very high frequency sine waves which I getting perfectly after adding all the three due to already set parameters in the simulation parameter box.
The carrier frequency is also very high, up to 3000 Hz, but the scope is displaying is correctly. But after the message signal and carrier are passing through the product, I am not getting amplitude modulated signal. Instead, I am getting a completely zero straight line. My sample time in the Product is 0.0001.
I am pretty sure it has to do something with the product parameters or simulation parameters but I so not sure exactly what it is? amplitude, sine MATLAB Answers — New Questions
Matlab 2023B keeps crashing every time I edit a script
Here is the log
————————————————
MATLAB Log File
————————————————
——————————————————————————–
Access violation detected at 2026-03-13 21:50:24 -0700
——————————————————————————–
Configuration:
Crash Decoding : Disabled – No sandbox or build area path
Crash Mode : continue (default)
Default Encoding : UTF-8
Deployed : false
Graphics Driver : Uninitialized hardware
Graphics card 1 : Microsoft ( 0x0 ) Microsoft Remote Display Adapter Version 10.0.26100.7705 (2006-6-21)
Graphics card 2 : NVIDIA ( 0x10de ) NVIDIA RTX A4000 Version 27.21.14.6296 (2021-7-2)
Interpreter 0 : Executing request: 54434D657373616765536572766963654C6966656379636C65506C7567696E2E637070
Java Version : Java 1.8.0_202-b08 with Oracle Corporation Java HotSpot(TM) 64-Bit Server VM mixed mode
MATLAB Architecture : win64
MATLAB Entitlement ID : 13541140
MATLAB Root : C:Program FilesMATLABR2023b
MATLAB Version : 23.2.0.2485118 (R2023b) Update 6
OpenGL : hardware
Operating System : Microsoft Windows 11 Pro
Process ID : 14832
Processor ID : x86 Family 25 Model 33 Stepping 0, AuthenticAMD
Session Key : fff3bd3b-69ba-4abf-b330-25c329984861
Window System : Version 10.0 (Build 26200)
Fault Count: 1
Abnormal termination:
Access violation
Current Thread: ‘MCR 0 interpreter thread’ id 17220
Register State (from fault):
RAX = 0000000000000000 RBX = 000001dcd0ddc190
RCX = 000001dcd0ddc190 RDX = 0000000000000000
RSP = 000000b42f8f5080 RBP = 0000000000000000
RSI = 0000000000000000 RDI = 000001dcd4a096c0
R8 = 000001dccdcc0080 R9 = 000000000000001b
R10 = 000001dcdfda0000 R11 = 000000b42f8f5108
R12 = 0000000000000000 R13 = 000000b42f8f5e40
R14 = 00007ffcc272e468 R15 = 00007ffcc272d180
RIP = 00007ffcc15cf5ca EFL = 00010246
CS = 0033 FS = 0053 GS = 002b
Stack Trace (from fault):
[ 0] 0x00007ffcc15cf5ca C:WINDOWSsystem32DriverStoreFileRepositorynv_dispi.inf_amd64_ec858e090be52f0envcuda64.dll+03995082 cuProfilerStop+01762586
[ 1] 0x00007ffcc15c0300 C:WINDOWSsystem32DriverStoreFileRepositorynv_dispi.inf_amd64_ec858e090be52f0envcuda64.dll+03932928 cuProfilerStop+01700432
[ 2] 0x00007ffcc13b9127 C:WINDOWSsystem32DriverStoreFileRepositorynv_dispi.inf_amd64_ec858e090be52f0envcuda64.dll+01806631
[ 3] 0x00007ffcc13bc1c5 C:WINDOWSsystem32DriverStoreFileRepositorynv_dispi.inf_amd64_ec858e090be52f0envcuda64.dll+01819077
[ 4] 0x00007ffcc136b277 C:WINDOWSsystem32DriverStoreFileRepositorynv_dispi.inf_amd64_ec858e090be52f0envcuda64.dll+01487479
[ 5] 0x00007ffcc136c436 C:WINDOWSsystem32DriverStoreFileRepositorynv_dispi.inf_amd64_ec858e090be52f0envcuda64.dll+01492022
[ 6] 0x00007ffcc136c670 C:WINDOWSsystem32DriverStoreFileRepositorynv_dispi.inf_amd64_ec858e090be52f0envcuda64.dll+01492592
[ 7] 0x00007ffcc13cb844 C:WINDOWSsystem32DriverStoreFileRepositorynv_dispi.inf_amd64_ec858e090be52f0envcuda64.dll+01882180 cuInit+00000500
[ 8] 0x00007ffcc86a8949 C:WINDOWSSYSTEM32nvcuda.dll+02066761 cuInit+00000169
[ 9] 0x00007ffcc88a7518 C:Program FilesMATLABR2023bbinwin64gpudeviceinfo.dll+00095512 MLTerminate_gpudeviceinfo+00042808
[ 10] 0x00007ffcc889e858 C:Program FilesMATLABR2023bbinwin64gpudeviceinfo.dll+00059480 MLTerminate_gpudeviceinfo+00006776
[ 11] 0x00007ffcc88a5622 C:Program FilesMATLABR2023bbinwin64gpudeviceinfo.dll+00087586 MLTerminate_gpudeviceinfo+00034882
[ 12] 0x00007ffcc88aa7d3 C:Program FilesMATLABR2023bbinwin64gpudeviceinfo.dll+00108499 gpudeviceinfo::setDeviceStatusCallback+00000899
[ 13] 0x00007ffcc889c6ee C:Program FilesMATLABR2023bbinwin64gpudeviceinfo.dll+00050926 gpudeviceinfo::validateGPU+00000014
[ 14] 0x00007ffcc89097be C:Program FilesMATLABR2023bbinwin64gpushim.dll+00235454 gpushim::gpuArrayLXE::setHandle+00010046
[ 15] 0x00007ffcc8909047 C:Program FilesMATLABR2023bbinwin64gpushim.dll+00233543 gpushim::gpuArrayLXE::setHandle+00008135
[ 16] 0x00007ffcc890b417 C:Program FilesMATLABR2023bbinwin64gpushim.dll+00242711 gpushim::gpuArrayLXE::setHandle+00017303
[ 17] 0x00007ffcc88fc590 C:Program FilesMATLABR2023bbinwin64gpushim.dll+00181648 gpushim::MLTerminate_gpushim+00011728
[ 18] 0x00007ffcc88f9763 C:Program FilesMATLABR2023bbinwin64gpushim.dll+00169827 gpushim::MLInitialize_gpushim+00000019
[ 19] 0x00007ffcc8e1bf6f C:Program FilesMATLABR2023bbinwin64builtinsparallelgpuapishimmwgpushim_builtinimpl.dll+04636527 gpushim::gpuArrayLXE::~gpuArrayLXE+00657487
[ 20] 0x00007ffd23f82967 C:Program FilesMATLABR2023bbinwin64m_dispatcher.dll+00403815 mdLoadLmBuiltinAllowedProtected::operator=+00020119
[ 21] 0x00007ffd23f5ea73 C:Program FilesMATLABR2023bbinwin64m_dispatcher.dll+00256627 Mlm_MATLAB_fn_impl::try_load+00000035
[ 22] 0x00007ffd23f5e13c C:Program FilesMATLABR2023bbinwin64m_dispatcher.dll+00254268 Mlm_MATLAB_fn_impl::load+00000044
[ 23] 0x00007ffd23f732da C:Program FilesMATLABR2023bbinwin64m_dispatcher.dll+00340698 mdLoadModuleForPackageOrClass+00000522
[ 24] 0x00007ffce6b1bb44 C:Program FilesMATLABR2023bbinwin64mcos_impl.dll+00965444 mwboost::serialization::singleton_module::unlock+00443268
[ 25] 0x00007ffd31c70eca C:Program FilesMATLABR2023bbinwin64contextdata.dll+00134858 MCOSContextData::ClassInfo::getSuperclassesOfClass+00000058
[ 26] 0x00007ffd31c6264e C:Program FilesMATLABR2023bbinwin64contextdata.dll+00075342 MCOSContextData::ClassInfo::ClassInfo+00000366
[ 27] 0x00007ffcd133d898 C:Program FilesMATLABR2023bbinwin64pa_bridges.dll+00120984 PathItemImpl::isA+00000504
[ 28] 0x00007ffd226ef391 C:Program FilesMATLABR2023bbinwin64pa_function_registry.dll+00652177 MathWorks::functionRegistry::Argument::isArgumentAttribute+00292433
[ 29] 0x00007ffd22780d82 C:Program FilesMATLABR2023bbinwin64pa_function_registry.dll+01248642 MathWorks::functionRegistry::fileParts+00003362
[ 30] 0x00007ffd2278fb1c C:Program FilesMATLABR2023bbinwin64pa_function_registry.dll+01309468 MathWorks::functionRegistry::Function::lookupFunctionsWithoutPathInfo+00000124
[ 31] 0x00007ffd2278766a C:Program FilesMATLABR2023bbinwin64pa_function_registry.dll+01275498 MathWorks::functionRegistry::Function::SignatureMismatchException::getFunction+00009898
[ 32] 0x00007ffd22785d64 C:Program FilesMATLABR2023bbinwin64pa_function_registry.dll+01269092 MathWorks::functionRegistry::Function::SignatureMismatchException::getFunction+00003492
[ 33] 0x00007ffd227850b4 C:Program FilesMATLABR2023bbinwin64pa_function_registry.dll+01265844 MathWorks::functionRegistry::Function::SignatureMismatchException::getFunction+00000244
[ 34] 0x00007ffd22788925 C:Program FilesMATLABR2023bbinwin64pa_function_registry.dll+01280293 MathWorks::functionRegistry::MetadataContainers::getJsonSignatureStems+00000405
[ 35] 0x00007ffd22789976 C:Program FilesMATLABR2023bbinwin64pa_function_registry.dll+01284470 MathWorks::functionRegistry::getMatchingFunctionsForStaticAnalysis+00000230
[ 36] 0x00007ffcd15eaa62 C:Program FilesMATLABR2023bbinwin64tabcompletion.dll+00895586 mwboost::serialization::singleton_module::unlock+00827586
[ 37] 0x00007ffcd15e8070 C:Program FilesMATLABR2023bbinwin64tabcompletion.dll+00884848 mwboost::serialization::singleton_module::unlock+00816848
[ 38] 0x00007ffcd15e7d44 C:Program FilesMATLABR2023bbinwin64tabcompletion.dll+00884036 mwboost::serialization::singleton_module::unlock+00816036
[ 39] 0x00007ffcd158f5ff C:Program FilesMATLABR2023bbinwin64tabcompletion.dll+00521727 mwboost::serialization::singleton_module::unlock+00453727
[ 40] 0x00007ffcd15407ef C:Program FilesMATLABR2023bbinwin64tabcompletion.dll+00198639 mwboost::serialization::singleton_module::unlock+00130639
[ 41] 0x00007ffcd15411af C:Program FilesMATLABR2023bbinwin64tabcompletion.dll+00201135 mwboost::serialization::singleton_module::unlock+00133135
[ 42] 0x00007ffcd1540b7e C:Program FilesMATLABR2023bbinwin64tabcompletion.dll+00199550 mwboost::serialization::singleton_module::unlock+00131550
[ 43] 0x00007ffcd1598a10 C:Program FilesMATLABR2023bbinwin64tabcompletion.dll+00559632 mwboost::serialization::singleton_module::unlock+00491632
[ 44] 0x00007ffcd15986d9 C:Program FilesMATLABR2023bbinwin64tabcompletion.dll+00558809 mwboost::serialization::singleton_module::unlock+00490809
[ 45] 0x00007ffcd16a26ea C:Program FilesMATLABR2023bbinwin64tabcompletion.dll+01648362 TabContext::FindCompletion+00006186
[ 46] 0x00007ffcd16a621a C:Program FilesMATLABR2023bbinwin64tabcompletion.dll+01663514 TabContext::GetInfo+00001050
[ 47] 0x00007ffcd16a473a C:Program FilesMATLABR2023bbinwin64tabcompletion.dll+01656634 TabContext::GetInfo+00002074
[ 48] 0x00007ffcd16a5d2f C:Program FilesMATLABR2023bbinwin64tabcompletion.dll+01662255 TabContext::GetInfo+00000143
[ 49] 0x00007ffcca07e2b2 C:Program FilesMATLABR2023bbinwin64connector_pluginstabcompletion_message_servicemwtabcompletion_message_service.dll+00254642 mwboost::archive::codecvt_null<wchar_t>::~codecvt_null<wchar_t>+00031026
[ 50] 0x00007ffcca08fcc7 C:Program FilesMATLABR2023bbinwin64connector_pluginstabcompletion_message_servicemwtabcompletion_message_service.dll+00326855 mwboost::serialization::singleton_module::get_lock+00002935
[ 51] 0x00007ffcca058856 C:Program FilesMATLABR2023bbinwin64connector_pluginstabcompletion_message_servicemwtabcompletion_message_service.dll+00100438
[ 52] 0x00007ffcca084c20 C:Program FilesMATLABR2023bbinwin64connector_pluginstabcompletion_message_servicemwtabcompletion_message_service.dll+00281632 mwboost::archive::codecvt_null<wchar_t>::`default constructor closure’+00020528
[ 53] 0x00007ffd243c8c3a C:Program FilesMATLABR2023bbinwin64iqm.dll+00822330 iqm::PackagedTaskPlugin::execute+00000074
[ 54] 0x00007ffd241d58e0 C:Program FilesMATLABR2023bbinwin64mcr.dll+00415968 installMOCmdWinSink+00074384
[ 55] 0x00007ffd2439cbb7 C:Program FilesMATLABR2023bbinwin64iqm.dll+00641975 iqm::Iqm::setupIqmFcnPtrs+00100471
[ 56] 0x00007ffd2436cc61 C:Program FilesMATLABR2023bbinwin64iqm.dll+00445537 iqm::Iqm::create+00007745
[ 57] 0x00007ffd23963f5e C:Program FilesMATLABR2023bbinwin64libmwbridge.dll+00081758 ioReadLine+00000430
[ 58] 0x00007ffd23963d75 C:Program FilesMATLABR2023bbinwin64libmwbridge.dll+00081269 ioReadLine+00000165
[ 59] 0x00007ffd23995fb0 C:Program FilesMATLABR2023bbinwin64libmwbridge.dll+00286640 mnGetCommandLineBuffer+00000288
[ 60] 0x00007ffd239964b2 C:Program FilesMATLABR2023bbinwin64libmwbridge.dll+00287922 mnParser+00000578
[ 61] 0x00007ffd241db398 C:Program FilesMATLABR2023bbinwin64mcr.dll+00439192 mcr_initialize_main+00013816
[ 62] 0x00007ffd24188604 C:Program FilesMATLABR2023bbinwin64mcr.dll+00099844 mcrFunctionSignature::set_signature+00078996
[ 63] 0x00007ffd241a61a0 C:Program FilesMATLABR2023bbinwin64mcr.dll+00221600 mwboost::archive::codecvt_null<wchar_t>::`default constructor closure’+00017728
[ 64] 0x00007ffd243c8c3a C:Program FilesMATLABR2023bbinwin64iqm.dll+00822330 iqm::PackagedTaskPlugin::execute+00000074
[ 65] 0x00007ffd241d58e0 C:Program FilesMATLABR2023bbinwin64mcr.dll+00415968 installMOCmdWinSink+00074384
[ 66] 0x00007ffd2439cbb7 C:Program FilesMATLABR2023bbinwin64iqm.dll+00641975 iqm::Iqm::setupIqmFcnPtrs+00100471
[ 67] 0x00007ffd2436de81 C:Program FilesMATLABR2023bbinwin64iqm.dll+00450177 iqm::Iqm::create+00012385
[ 68] 0x00007ffd2436d5c9 C:Program FilesMATLABR2023bbinwin64iqm.dll+00447945 iqm::Iqm::create+00010153
[ 69] 0x00007ffd241c1c1c C:Program FilesMATLABR2023bbinwin64mcr.dll+00334876 mcrInstantiationError::operator=+00009948
[ 70] 0x00007ffd241c2645 C:Program FilesMATLABR2023bbinwin64mcr.dll+00337477 mcrInstantiationError::operator=+00012549
[ 71] 0x00007ffd241bffd0 C:Program FilesMATLABR2023bbinwin64mcr.dll+00327632 mcrInstantiationError::operator=+00002704
[ 72] 0x00007ffd5bcb92ea C:Program FilesMATLABR2023bbinwin64mwboost_thread-vc142-mt-x64-1_78.dll+00037610 mwboost::detail::win32::handle_manager::swap+00001642
[ 73] 0x00007ffd7a8437b0 C:WINDOWSSystem32ucrtbase.dll+00014256 wcsrchr+00000336
[ 74] 0x00007ffd7bd2e8d7 C:WINDOWSSystem32KERNEL32.DLL+00190679 BaseThreadInitThunk+00000023
[ 75] 0x00007ffd7dfec40c C:WINDOWSSYSTEM32ntdll.dll+00574476 RtlUserThreadStart+00000044Here is the log
————————————————
MATLAB Log File
————————————————
——————————————————————————–
Access violation detected at 2026-03-13 21:50:24 -0700
——————————————————————————–
Configuration:
Crash Decoding : Disabled – No sandbox or build area path
Crash Mode : continue (default)
Default Encoding : UTF-8
Deployed : false
Graphics Driver : Uninitialized hardware
Graphics card 1 : Microsoft ( 0x0 ) Microsoft Remote Display Adapter Version 10.0.26100.7705 (2006-6-21)
Graphics card 2 : NVIDIA ( 0x10de ) NVIDIA RTX A4000 Version 27.21.14.6296 (2021-7-2)
Interpreter 0 : Executing request: 54434D657373616765536572766963654C6966656379636C65506C7567696E2E637070
Java Version : Java 1.8.0_202-b08 with Oracle Corporation Java HotSpot(TM) 64-Bit Server VM mixed mode
MATLAB Architecture : win64
MATLAB Entitlement ID : 13541140
MATLAB Root : C:Program FilesMATLABR2023b
MATLAB Version : 23.2.0.2485118 (R2023b) Update 6
OpenGL : hardware
Operating System : Microsoft Windows 11 Pro
Process ID : 14832
Processor ID : x86 Family 25 Model 33 Stepping 0, AuthenticAMD
Session Key : fff3bd3b-69ba-4abf-b330-25c329984861
Window System : Version 10.0 (Build 26200)
Fault Count: 1
Abnormal termination:
Access violation
Current Thread: ‘MCR 0 interpreter thread’ id 17220
Register State (from fault):
RAX = 0000000000000000 RBX = 000001dcd0ddc190
RCX = 000001dcd0ddc190 RDX = 0000000000000000
RSP = 000000b42f8f5080 RBP = 0000000000000000
RSI = 0000000000000000 RDI = 000001dcd4a096c0
R8 = 000001dccdcc0080 R9 = 000000000000001b
R10 = 000001dcdfda0000 R11 = 000000b42f8f5108
R12 = 0000000000000000 R13 = 000000b42f8f5e40
R14 = 00007ffcc272e468 R15 = 00007ffcc272d180
RIP = 00007ffcc15cf5ca EFL = 00010246
CS = 0033 FS = 0053 GS = 002b
Stack Trace (from fault):
[ 0] 0x00007ffcc15cf5ca C:WINDOWSsystem32DriverStoreFileRepositorynv_dispi.inf_amd64_ec858e090be52f0envcuda64.dll+03995082 cuProfilerStop+01762586
[ 1] 0x00007ffcc15c0300 C:WINDOWSsystem32DriverStoreFileRepositorynv_dispi.inf_amd64_ec858e090be52f0envcuda64.dll+03932928 cuProfilerStop+01700432
[ 2] 0x00007ffcc13b9127 C:WINDOWSsystem32DriverStoreFileRepositorynv_dispi.inf_amd64_ec858e090be52f0envcuda64.dll+01806631
[ 3] 0x00007ffcc13bc1c5 C:WINDOWSsystem32DriverStoreFileRepositorynv_dispi.inf_amd64_ec858e090be52f0envcuda64.dll+01819077
[ 4] 0x00007ffcc136b277 C:WINDOWSsystem32DriverStoreFileRepositorynv_dispi.inf_amd64_ec858e090be52f0envcuda64.dll+01487479
[ 5] 0x00007ffcc136c436 C:WINDOWSsystem32DriverStoreFileRepositorynv_dispi.inf_amd64_ec858e090be52f0envcuda64.dll+01492022
[ 6] 0x00007ffcc136c670 C:WINDOWSsystem32DriverStoreFileRepositorynv_dispi.inf_amd64_ec858e090be52f0envcuda64.dll+01492592
[ 7] 0x00007ffcc13cb844 C:WINDOWSsystem32DriverStoreFileRepositorynv_dispi.inf_amd64_ec858e090be52f0envcuda64.dll+01882180 cuInit+00000500
[ 8] 0x00007ffcc86a8949 C:WINDOWSSYSTEM32nvcuda.dll+02066761 cuInit+00000169
[ 9] 0x00007ffcc88a7518 C:Program FilesMATLABR2023bbinwin64gpudeviceinfo.dll+00095512 MLTerminate_gpudeviceinfo+00042808
[ 10] 0x00007ffcc889e858 C:Program FilesMATLABR2023bbinwin64gpudeviceinfo.dll+00059480 MLTerminate_gpudeviceinfo+00006776
[ 11] 0x00007ffcc88a5622 C:Program FilesMATLABR2023bbinwin64gpudeviceinfo.dll+00087586 MLTerminate_gpudeviceinfo+00034882
[ 12] 0x00007ffcc88aa7d3 C:Program FilesMATLABR2023bbinwin64gpudeviceinfo.dll+00108499 gpudeviceinfo::setDeviceStatusCallback+00000899
[ 13] 0x00007ffcc889c6ee C:Program FilesMATLABR2023bbinwin64gpudeviceinfo.dll+00050926 gpudeviceinfo::validateGPU+00000014
[ 14] 0x00007ffcc89097be C:Program FilesMATLABR2023bbinwin64gpushim.dll+00235454 gpushim::gpuArrayLXE::setHandle+00010046
[ 15] 0x00007ffcc8909047 C:Program FilesMATLABR2023bbinwin64gpushim.dll+00233543 gpushim::gpuArrayLXE::setHandle+00008135
[ 16] 0x00007ffcc890b417 C:Program FilesMATLABR2023bbinwin64gpushim.dll+00242711 gpushim::gpuArrayLXE::setHandle+00017303
[ 17] 0x00007ffcc88fc590 C:Program FilesMATLABR2023bbinwin64gpushim.dll+00181648 gpushim::MLTerminate_gpushim+00011728
[ 18] 0x00007ffcc88f9763 C:Program FilesMATLABR2023bbinwin64gpushim.dll+00169827 gpushim::MLInitialize_gpushim+00000019
[ 19] 0x00007ffcc8e1bf6f C:Program FilesMATLABR2023bbinwin64builtinsparallelgpuapishimmwgpushim_builtinimpl.dll+04636527 gpushim::gpuArrayLXE::~gpuArrayLXE+00657487
[ 20] 0x00007ffd23f82967 C:Program FilesMATLABR2023bbinwin64m_dispatcher.dll+00403815 mdLoadLmBuiltinAllowedProtected::operator=+00020119
[ 21] 0x00007ffd23f5ea73 C:Program FilesMATLABR2023bbinwin64m_dispatcher.dll+00256627 Mlm_MATLAB_fn_impl::try_load+00000035
[ 22] 0x00007ffd23f5e13c C:Program FilesMATLABR2023bbinwin64m_dispatcher.dll+00254268 Mlm_MATLAB_fn_impl::load+00000044
[ 23] 0x00007ffd23f732da C:Program FilesMATLABR2023bbinwin64m_dispatcher.dll+00340698 mdLoadModuleForPackageOrClass+00000522
[ 24] 0x00007ffce6b1bb44 C:Program FilesMATLABR2023bbinwin64mcos_impl.dll+00965444 mwboost::serialization::singleton_module::unlock+00443268
[ 25] 0x00007ffd31c70eca C:Program FilesMATLABR2023bbinwin64contextdata.dll+00134858 MCOSContextData::ClassInfo::getSuperclassesOfClass+00000058
[ 26] 0x00007ffd31c6264e C:Program FilesMATLABR2023bbinwin64contextdata.dll+00075342 MCOSContextData::ClassInfo::ClassInfo+00000366
[ 27] 0x00007ffcd133d898 C:Program FilesMATLABR2023bbinwin64pa_bridges.dll+00120984 PathItemImpl::isA+00000504
[ 28] 0x00007ffd226ef391 C:Program FilesMATLABR2023bbinwin64pa_function_registry.dll+00652177 MathWorks::functionRegistry::Argument::isArgumentAttribute+00292433
[ 29] 0x00007ffd22780d82 C:Program FilesMATLABR2023bbinwin64pa_function_registry.dll+01248642 MathWorks::functionRegistry::fileParts+00003362
[ 30] 0x00007ffd2278fb1c C:Program FilesMATLABR2023bbinwin64pa_function_registry.dll+01309468 MathWorks::functionRegistry::Function::lookupFunctionsWithoutPathInfo+00000124
[ 31] 0x00007ffd2278766a C:Program FilesMATLABR2023bbinwin64pa_function_registry.dll+01275498 MathWorks::functionRegistry::Function::SignatureMismatchException::getFunction+00009898
[ 32] 0x00007ffd22785d64 C:Program FilesMATLABR2023bbinwin64pa_function_registry.dll+01269092 MathWorks::functionRegistry::Function::SignatureMismatchException::getFunction+00003492
[ 33] 0x00007ffd227850b4 C:Program FilesMATLABR2023bbinwin64pa_function_registry.dll+01265844 MathWorks::functionRegistry::Function::SignatureMismatchException::getFunction+00000244
[ 34] 0x00007ffd22788925 C:Program FilesMATLABR2023bbinwin64pa_function_registry.dll+01280293 MathWorks::functionRegistry::MetadataContainers::getJsonSignatureStems+00000405
[ 35] 0x00007ffd22789976 C:Program FilesMATLABR2023bbinwin64pa_function_registry.dll+01284470 MathWorks::functionRegistry::getMatchingFunctionsForStaticAnalysis+00000230
[ 36] 0x00007ffcd15eaa62 C:Program FilesMATLABR2023bbinwin64tabcompletion.dll+00895586 mwboost::serialization::singleton_module::unlock+00827586
[ 37] 0x00007ffcd15e8070 C:Program FilesMATLABR2023bbinwin64tabcompletion.dll+00884848 mwboost::serialization::singleton_module::unlock+00816848
[ 38] 0x00007ffcd15e7d44 C:Program FilesMATLABR2023bbinwin64tabcompletion.dll+00884036 mwboost::serialization::singleton_module::unlock+00816036
[ 39] 0x00007ffcd158f5ff C:Program FilesMATLABR2023bbinwin64tabcompletion.dll+00521727 mwboost::serialization::singleton_module::unlock+00453727
[ 40] 0x00007ffcd15407ef C:Program FilesMATLABR2023bbinwin64tabcompletion.dll+00198639 mwboost::serialization::singleton_module::unlock+00130639
[ 41] 0x00007ffcd15411af C:Program FilesMATLABR2023bbinwin64tabcompletion.dll+00201135 mwboost::serialization::singleton_module::unlock+00133135
[ 42] 0x00007ffcd1540b7e C:Program FilesMATLABR2023bbinwin64tabcompletion.dll+00199550 mwboost::serialization::singleton_module::unlock+00131550
[ 43] 0x00007ffcd1598a10 C:Program FilesMATLABR2023bbinwin64tabcompletion.dll+00559632 mwboost::serialization::singleton_module::unlock+00491632
[ 44] 0x00007ffcd15986d9 C:Program FilesMATLABR2023bbinwin64tabcompletion.dll+00558809 mwboost::serialization::singleton_module::unlock+00490809
[ 45] 0x00007ffcd16a26ea C:Program FilesMATLABR2023bbinwin64tabcompletion.dll+01648362 TabContext::FindCompletion+00006186
[ 46] 0x00007ffcd16a621a C:Program FilesMATLABR2023bbinwin64tabcompletion.dll+01663514 TabContext::GetInfo+00001050
[ 47] 0x00007ffcd16a473a C:Program FilesMATLABR2023bbinwin64tabcompletion.dll+01656634 TabContext::GetInfo+00002074
[ 48] 0x00007ffcd16a5d2f C:Program FilesMATLABR2023bbinwin64tabcompletion.dll+01662255 TabContext::GetInfo+00000143
[ 49] 0x00007ffcca07e2b2 C:Program FilesMATLABR2023bbinwin64connector_pluginstabcompletion_message_servicemwtabcompletion_message_service.dll+00254642 mwboost::archive::codecvt_null<wchar_t>::~codecvt_null<wchar_t>+00031026
[ 50] 0x00007ffcca08fcc7 C:Program FilesMATLABR2023bbinwin64connector_pluginstabcompletion_message_servicemwtabcompletion_message_service.dll+00326855 mwboost::serialization::singleton_module::get_lock+00002935
[ 51] 0x00007ffcca058856 C:Program FilesMATLABR2023bbinwin64connector_pluginstabcompletion_message_servicemwtabcompletion_message_service.dll+00100438
[ 52] 0x00007ffcca084c20 C:Program FilesMATLABR2023bbinwin64connector_pluginstabcompletion_message_servicemwtabcompletion_message_service.dll+00281632 mwboost::archive::codecvt_null<wchar_t>::`default constructor closure’+00020528
[ 53] 0x00007ffd243c8c3a C:Program FilesMATLABR2023bbinwin64iqm.dll+00822330 iqm::PackagedTaskPlugin::execute+00000074
[ 54] 0x00007ffd241d58e0 C:Program FilesMATLABR2023bbinwin64mcr.dll+00415968 installMOCmdWinSink+00074384
[ 55] 0x00007ffd2439cbb7 C:Program FilesMATLABR2023bbinwin64iqm.dll+00641975 iqm::Iqm::setupIqmFcnPtrs+00100471
[ 56] 0x00007ffd2436cc61 C:Program FilesMATLABR2023bbinwin64iqm.dll+00445537 iqm::Iqm::create+00007745
[ 57] 0x00007ffd23963f5e C:Program FilesMATLABR2023bbinwin64libmwbridge.dll+00081758 ioReadLine+00000430
[ 58] 0x00007ffd23963d75 C:Program FilesMATLABR2023bbinwin64libmwbridge.dll+00081269 ioReadLine+00000165
[ 59] 0x00007ffd23995fb0 C:Program FilesMATLABR2023bbinwin64libmwbridge.dll+00286640 mnGetCommandLineBuffer+00000288
[ 60] 0x00007ffd239964b2 C:Program FilesMATLABR2023bbinwin64libmwbridge.dll+00287922 mnParser+00000578
[ 61] 0x00007ffd241db398 C:Program FilesMATLABR2023bbinwin64mcr.dll+00439192 mcr_initialize_main+00013816
[ 62] 0x00007ffd24188604 C:Program FilesMATLABR2023bbinwin64mcr.dll+00099844 mcrFunctionSignature::set_signature+00078996
[ 63] 0x00007ffd241a61a0 C:Program FilesMATLABR2023bbinwin64mcr.dll+00221600 mwboost::archive::codecvt_null<wchar_t>::`default constructor closure’+00017728
[ 64] 0x00007ffd243c8c3a C:Program FilesMATLABR2023bbinwin64iqm.dll+00822330 iqm::PackagedTaskPlugin::execute+00000074
[ 65] 0x00007ffd241d58e0 C:Program FilesMATLABR2023bbinwin64mcr.dll+00415968 installMOCmdWinSink+00074384
[ 66] 0x00007ffd2439cbb7 C:Program FilesMATLABR2023bbinwin64iqm.dll+00641975 iqm::Iqm::setupIqmFcnPtrs+00100471
[ 67] 0x00007ffd2436de81 C:Program FilesMATLABR2023bbinwin64iqm.dll+00450177 iqm::Iqm::create+00012385
[ 68] 0x00007ffd2436d5c9 C:Program FilesMATLABR2023bbinwin64iqm.dll+00447945 iqm::Iqm::create+00010153
[ 69] 0x00007ffd241c1c1c C:Program FilesMATLABR2023bbinwin64mcr.dll+00334876 mcrInstantiationError::operator=+00009948
[ 70] 0x00007ffd241c2645 C:Program FilesMATLABR2023bbinwin64mcr.dll+00337477 mcrInstantiationError::operator=+00012549
[ 71] 0x00007ffd241bffd0 C:Program FilesMATLABR2023bbinwin64mcr.dll+00327632 mcrInstantiationError::operator=+00002704
[ 72] 0x00007ffd5bcb92ea C:Program FilesMATLABR2023bbinwin64mwboost_thread-vc142-mt-x64-1_78.dll+00037610 mwboost::detail::win32::handle_manager::swap+00001642
[ 73] 0x00007ffd7a8437b0 C:WINDOWSSystem32ucrtbase.dll+00014256 wcsrchr+00000336
[ 74] 0x00007ffd7bd2e8d7 C:WINDOWSSystem32KERNEL32.DLL+00190679 BaseThreadInitThunk+00000023
[ 75] 0x00007ffd7dfec40c C:WINDOWSSYSTEM32ntdll.dll+00574476 RtlUserThreadStart+00000044 Here is the log
————————————————
MATLAB Log File
————————————————
——————————————————————————–
Access violation detected at 2026-03-13 21:50:24 -0700
——————————————————————————–
Configuration:
Crash Decoding : Disabled – No sandbox or build area path
Crash Mode : continue (default)
Default Encoding : UTF-8
Deployed : false
Graphics Driver : Uninitialized hardware
Graphics card 1 : Microsoft ( 0x0 ) Microsoft Remote Display Adapter Version 10.0.26100.7705 (2006-6-21)
Graphics card 2 : NVIDIA ( 0x10de ) NVIDIA RTX A4000 Version 27.21.14.6296 (2021-7-2)
Interpreter 0 : Executing request: 54434D657373616765536572766963654C6966656379636C65506C7567696E2E637070
Java Version : Java 1.8.0_202-b08 with Oracle Corporation Java HotSpot(TM) 64-Bit Server VM mixed mode
MATLAB Architecture : win64
MATLAB Entitlement ID : 13541140
MATLAB Root : C:Program FilesMATLABR2023b
MATLAB Version : 23.2.0.2485118 (R2023b) Update 6
OpenGL : hardware
Operating System : Microsoft Windows 11 Pro
Process ID : 14832
Processor ID : x86 Family 25 Model 33 Stepping 0, AuthenticAMD
Session Key : fff3bd3b-69ba-4abf-b330-25c329984861
Window System : Version 10.0 (Build 26200)
Fault Count: 1
Abnormal termination:
Access violation
Current Thread: ‘MCR 0 interpreter thread’ id 17220
Register State (from fault):
RAX = 0000000000000000 RBX = 000001dcd0ddc190
RCX = 000001dcd0ddc190 RDX = 0000000000000000
RSP = 000000b42f8f5080 RBP = 0000000000000000
RSI = 0000000000000000 RDI = 000001dcd4a096c0
R8 = 000001dccdcc0080 R9 = 000000000000001b
R10 = 000001dcdfda0000 R11 = 000000b42f8f5108
R12 = 0000000000000000 R13 = 000000b42f8f5e40
R14 = 00007ffcc272e468 R15 = 00007ffcc272d180
RIP = 00007ffcc15cf5ca EFL = 00010246
CS = 0033 FS = 0053 GS = 002b
Stack Trace (from fault):
[ 0] 0x00007ffcc15cf5ca C:WINDOWSsystem32DriverStoreFileRepositorynv_dispi.inf_amd64_ec858e090be52f0envcuda64.dll+03995082 cuProfilerStop+01762586
[ 1] 0x00007ffcc15c0300 C:WINDOWSsystem32DriverStoreFileRepositorynv_dispi.inf_amd64_ec858e090be52f0envcuda64.dll+03932928 cuProfilerStop+01700432
[ 2] 0x00007ffcc13b9127 C:WINDOWSsystem32DriverStoreFileRepositorynv_dispi.inf_amd64_ec858e090be52f0envcuda64.dll+01806631
[ 3] 0x00007ffcc13bc1c5 C:WINDOWSsystem32DriverStoreFileRepositorynv_dispi.inf_amd64_ec858e090be52f0envcuda64.dll+01819077
[ 4] 0x00007ffcc136b277 C:WINDOWSsystem32DriverStoreFileRepositorynv_dispi.inf_amd64_ec858e090be52f0envcuda64.dll+01487479
[ 5] 0x00007ffcc136c436 C:WINDOWSsystem32DriverStoreFileRepositorynv_dispi.inf_amd64_ec858e090be52f0envcuda64.dll+01492022
[ 6] 0x00007ffcc136c670 C:WINDOWSsystem32DriverStoreFileRepositorynv_dispi.inf_amd64_ec858e090be52f0envcuda64.dll+01492592
[ 7] 0x00007ffcc13cb844 C:WINDOWSsystem32DriverStoreFileRepositorynv_dispi.inf_amd64_ec858e090be52f0envcuda64.dll+01882180 cuInit+00000500
[ 8] 0x00007ffcc86a8949 C:WINDOWSSYSTEM32nvcuda.dll+02066761 cuInit+00000169
[ 9] 0x00007ffcc88a7518 C:Program FilesMATLABR2023bbinwin64gpudeviceinfo.dll+00095512 MLTerminate_gpudeviceinfo+00042808
[ 10] 0x00007ffcc889e858 C:Program FilesMATLABR2023bbinwin64gpudeviceinfo.dll+00059480 MLTerminate_gpudeviceinfo+00006776
[ 11] 0x00007ffcc88a5622 C:Program FilesMATLABR2023bbinwin64gpudeviceinfo.dll+00087586 MLTerminate_gpudeviceinfo+00034882
[ 12] 0x00007ffcc88aa7d3 C:Program FilesMATLABR2023bbinwin64gpudeviceinfo.dll+00108499 gpudeviceinfo::setDeviceStatusCallback+00000899
[ 13] 0x00007ffcc889c6ee C:Program FilesMATLABR2023bbinwin64gpudeviceinfo.dll+00050926 gpudeviceinfo::validateGPU+00000014
[ 14] 0x00007ffcc89097be C:Program FilesMATLABR2023bbinwin64gpushim.dll+00235454 gpushim::gpuArrayLXE::setHandle+00010046
[ 15] 0x00007ffcc8909047 C:Program FilesMATLABR2023bbinwin64gpushim.dll+00233543 gpushim::gpuArrayLXE::setHandle+00008135
[ 16] 0x00007ffcc890b417 C:Program FilesMATLABR2023bbinwin64gpushim.dll+00242711 gpushim::gpuArrayLXE::setHandle+00017303
[ 17] 0x00007ffcc88fc590 C:Program FilesMATLABR2023bbinwin64gpushim.dll+00181648 gpushim::MLTerminate_gpushim+00011728
[ 18] 0x00007ffcc88f9763 C:Program FilesMATLABR2023bbinwin64gpushim.dll+00169827 gpushim::MLInitialize_gpushim+00000019
[ 19] 0x00007ffcc8e1bf6f C:Program FilesMATLABR2023bbinwin64builtinsparallelgpuapishimmwgpushim_builtinimpl.dll+04636527 gpushim::gpuArrayLXE::~gpuArrayLXE+00657487
[ 20] 0x00007ffd23f82967 C:Program FilesMATLABR2023bbinwin64m_dispatcher.dll+00403815 mdLoadLmBuiltinAllowedProtected::operator=+00020119
[ 21] 0x00007ffd23f5ea73 C:Program FilesMATLABR2023bbinwin64m_dispatcher.dll+00256627 Mlm_MATLAB_fn_impl::try_load+00000035
[ 22] 0x00007ffd23f5e13c C:Program FilesMATLABR2023bbinwin64m_dispatcher.dll+00254268 Mlm_MATLAB_fn_impl::load+00000044
[ 23] 0x00007ffd23f732da C:Program FilesMATLABR2023bbinwin64m_dispatcher.dll+00340698 mdLoadModuleForPackageOrClass+00000522
[ 24] 0x00007ffce6b1bb44 C:Program FilesMATLABR2023bbinwin64mcos_impl.dll+00965444 mwboost::serialization::singleton_module::unlock+00443268
[ 25] 0x00007ffd31c70eca C:Program FilesMATLABR2023bbinwin64contextdata.dll+00134858 MCOSContextData::ClassInfo::getSuperclassesOfClass+00000058
[ 26] 0x00007ffd31c6264e C:Program FilesMATLABR2023bbinwin64contextdata.dll+00075342 MCOSContextData::ClassInfo::ClassInfo+00000366
[ 27] 0x00007ffcd133d898 C:Program FilesMATLABR2023bbinwin64pa_bridges.dll+00120984 PathItemImpl::isA+00000504
[ 28] 0x00007ffd226ef391 C:Program FilesMATLABR2023bbinwin64pa_function_registry.dll+00652177 MathWorks::functionRegistry::Argument::isArgumentAttribute+00292433
[ 29] 0x00007ffd22780d82 C:Program FilesMATLABR2023bbinwin64pa_function_registry.dll+01248642 MathWorks::functionRegistry::fileParts+00003362
[ 30] 0x00007ffd2278fb1c C:Program FilesMATLABR2023bbinwin64pa_function_registry.dll+01309468 MathWorks::functionRegistry::Function::lookupFunctionsWithoutPathInfo+00000124
[ 31] 0x00007ffd2278766a C:Program FilesMATLABR2023bbinwin64pa_function_registry.dll+01275498 MathWorks::functionRegistry::Function::SignatureMismatchException::getFunction+00009898
[ 32] 0x00007ffd22785d64 C:Program FilesMATLABR2023bbinwin64pa_function_registry.dll+01269092 MathWorks::functionRegistry::Function::SignatureMismatchException::getFunction+00003492
[ 33] 0x00007ffd227850b4 C:Program FilesMATLABR2023bbinwin64pa_function_registry.dll+01265844 MathWorks::functionRegistry::Function::SignatureMismatchException::getFunction+00000244
[ 34] 0x00007ffd22788925 C:Program FilesMATLABR2023bbinwin64pa_function_registry.dll+01280293 MathWorks::functionRegistry::MetadataContainers::getJsonSignatureStems+00000405
[ 35] 0x00007ffd22789976 C:Program FilesMATLABR2023bbinwin64pa_function_registry.dll+01284470 MathWorks::functionRegistry::getMatchingFunctionsForStaticAnalysis+00000230
[ 36] 0x00007ffcd15eaa62 C:Program FilesMATLABR2023bbinwin64tabcompletion.dll+00895586 mwboost::serialization::singleton_module::unlock+00827586
[ 37] 0x00007ffcd15e8070 C:Program FilesMATLABR2023bbinwin64tabcompletion.dll+00884848 mwboost::serialization::singleton_module::unlock+00816848
[ 38] 0x00007ffcd15e7d44 C:Program FilesMATLABR2023bbinwin64tabcompletion.dll+00884036 mwboost::serialization::singleton_module::unlock+00816036
[ 39] 0x00007ffcd158f5ff C:Program FilesMATLABR2023bbinwin64tabcompletion.dll+00521727 mwboost::serialization::singleton_module::unlock+00453727
[ 40] 0x00007ffcd15407ef C:Program FilesMATLABR2023bbinwin64tabcompletion.dll+00198639 mwboost::serialization::singleton_module::unlock+00130639
[ 41] 0x00007ffcd15411af C:Program FilesMATLABR2023bbinwin64tabcompletion.dll+00201135 mwboost::serialization::singleton_module::unlock+00133135
[ 42] 0x00007ffcd1540b7e C:Program FilesMATLABR2023bbinwin64tabcompletion.dll+00199550 mwboost::serialization::singleton_module::unlock+00131550
[ 43] 0x00007ffcd1598a10 C:Program FilesMATLABR2023bbinwin64tabcompletion.dll+00559632 mwboost::serialization::singleton_module::unlock+00491632
[ 44] 0x00007ffcd15986d9 C:Program FilesMATLABR2023bbinwin64tabcompletion.dll+00558809 mwboost::serialization::singleton_module::unlock+00490809
[ 45] 0x00007ffcd16a26ea C:Program FilesMATLABR2023bbinwin64tabcompletion.dll+01648362 TabContext::FindCompletion+00006186
[ 46] 0x00007ffcd16a621a C:Program FilesMATLABR2023bbinwin64tabcompletion.dll+01663514 TabContext::GetInfo+00001050
[ 47] 0x00007ffcd16a473a C:Program FilesMATLABR2023bbinwin64tabcompletion.dll+01656634 TabContext::GetInfo+00002074
[ 48] 0x00007ffcd16a5d2f C:Program FilesMATLABR2023bbinwin64tabcompletion.dll+01662255 TabContext::GetInfo+00000143
[ 49] 0x00007ffcca07e2b2 C:Program FilesMATLABR2023bbinwin64connector_pluginstabcompletion_message_servicemwtabcompletion_message_service.dll+00254642 mwboost::archive::codecvt_null<wchar_t>::~codecvt_null<wchar_t>+00031026
[ 50] 0x00007ffcca08fcc7 C:Program FilesMATLABR2023bbinwin64connector_pluginstabcompletion_message_servicemwtabcompletion_message_service.dll+00326855 mwboost::serialization::singleton_module::get_lock+00002935
[ 51] 0x00007ffcca058856 C:Program FilesMATLABR2023bbinwin64connector_pluginstabcompletion_message_servicemwtabcompletion_message_service.dll+00100438
[ 52] 0x00007ffcca084c20 C:Program FilesMATLABR2023bbinwin64connector_pluginstabcompletion_message_servicemwtabcompletion_message_service.dll+00281632 mwboost::archive::codecvt_null<wchar_t>::`default constructor closure’+00020528
[ 53] 0x00007ffd243c8c3a C:Program FilesMATLABR2023bbinwin64iqm.dll+00822330 iqm::PackagedTaskPlugin::execute+00000074
[ 54] 0x00007ffd241d58e0 C:Program FilesMATLABR2023bbinwin64mcr.dll+00415968 installMOCmdWinSink+00074384
[ 55] 0x00007ffd2439cbb7 C:Program FilesMATLABR2023bbinwin64iqm.dll+00641975 iqm::Iqm::setupIqmFcnPtrs+00100471
[ 56] 0x00007ffd2436cc61 C:Program FilesMATLABR2023bbinwin64iqm.dll+00445537 iqm::Iqm::create+00007745
[ 57] 0x00007ffd23963f5e C:Program FilesMATLABR2023bbinwin64libmwbridge.dll+00081758 ioReadLine+00000430
[ 58] 0x00007ffd23963d75 C:Program FilesMATLABR2023bbinwin64libmwbridge.dll+00081269 ioReadLine+00000165
[ 59] 0x00007ffd23995fb0 C:Program FilesMATLABR2023bbinwin64libmwbridge.dll+00286640 mnGetCommandLineBuffer+00000288
[ 60] 0x00007ffd239964b2 C:Program FilesMATLABR2023bbinwin64libmwbridge.dll+00287922 mnParser+00000578
[ 61] 0x00007ffd241db398 C:Program FilesMATLABR2023bbinwin64mcr.dll+00439192 mcr_initialize_main+00013816
[ 62] 0x00007ffd24188604 C:Program FilesMATLABR2023bbinwin64mcr.dll+00099844 mcrFunctionSignature::set_signature+00078996
[ 63] 0x00007ffd241a61a0 C:Program FilesMATLABR2023bbinwin64mcr.dll+00221600 mwboost::archive::codecvt_null<wchar_t>::`default constructor closure’+00017728
[ 64] 0x00007ffd243c8c3a C:Program FilesMATLABR2023bbinwin64iqm.dll+00822330 iqm::PackagedTaskPlugin::execute+00000074
[ 65] 0x00007ffd241d58e0 C:Program FilesMATLABR2023bbinwin64mcr.dll+00415968 installMOCmdWinSink+00074384
[ 66] 0x00007ffd2439cbb7 C:Program FilesMATLABR2023bbinwin64iqm.dll+00641975 iqm::Iqm::setupIqmFcnPtrs+00100471
[ 67] 0x00007ffd2436de81 C:Program FilesMATLABR2023bbinwin64iqm.dll+00450177 iqm::Iqm::create+00012385
[ 68] 0x00007ffd2436d5c9 C:Program FilesMATLABR2023bbinwin64iqm.dll+00447945 iqm::Iqm::create+00010153
[ 69] 0x00007ffd241c1c1c C:Program FilesMATLABR2023bbinwin64mcr.dll+00334876 mcrInstantiationError::operator=+00009948
[ 70] 0x00007ffd241c2645 C:Program FilesMATLABR2023bbinwin64mcr.dll+00337477 mcrInstantiationError::operator=+00012549
[ 71] 0x00007ffd241bffd0 C:Program FilesMATLABR2023bbinwin64mcr.dll+00327632 mcrInstantiationError::operator=+00002704
[ 72] 0x00007ffd5bcb92ea C:Program FilesMATLABR2023bbinwin64mwboost_thread-vc142-mt-x64-1_78.dll+00037610 mwboost::detail::win32::handle_manager::swap+00001642
[ 73] 0x00007ffd7a8437b0 C:WINDOWSSystem32ucrtbase.dll+00014256 wcsrchr+00000336
[ 74] 0x00007ffd7bd2e8d7 C:WINDOWSSystem32KERNEL32.DLL+00190679 BaseThreadInitThunk+00000023
[ 75] 0x00007ffd7dfec40c C:WINDOWSSYSTEM32ntdll.dll+00574476 RtlUserThreadStart+00000044 matlab, crash, unexpected shutdown, abnormal termination, access violation MATLAB Answers — New Questions
Simulink and Arduino simulation issues
Hi,I want to use Simulink to receive temperature data from the Arduino NANO 33 BLE Sense, with the HTS221 as the temperature sensor. So far, I have completed the configuration as shown in the figure. However, no data is received during runtime.The version I’m using is MATLAB2024b. Are there any solutions to this issue?Hi,I want to use Simulink to receive temperature data from the Arduino NANO 33 BLE Sense, with the HTS221 as the temperature sensor. So far, I have completed the configuration as shown in the figure. However, no data is received during runtime.The version I’m using is MATLAB2024b. Are there any solutions to this issue? Hi,I want to use Simulink to receive temperature data from the Arduino NANO 33 BLE Sense, with the HTS221 as the temperature sensor. So far, I have completed the configuration as shown in the figure. However, no data is received during runtime.The version I’m using is MATLAB2024b. Are there any solutions to this issue? simulink and arduino simulation issues MATLAB Answers — New Questions
how to use trained LSTM model for predicting new data?
Hi everyone,
I’ve just developed a LSTM model for predicting flood. Its inputs are the rain and evaporation data and the output would be the amount of runoff. Now I have a question in this regard?
1- How to save and used the trianed model for the future predictions? For example, I want to enter today’s data of rain and evaporation and see the prediction of runoff for tomorrow.Hi everyone,
I’ve just developed a LSTM model for predicting flood. Its inputs are the rain and evaporation data and the output would be the amount of runoff. Now I have a question in this regard?
1- How to save and used the trianed model for the future predictions? For example, I want to enter today’s data of rain and evaporation and see the prediction of runoff for tomorrow. Hi everyone,
I’ve just developed a LSTM model for predicting flood. Its inputs are the rain and evaporation data and the output would be the amount of runoff. Now I have a question in this regard?
1- How to save and used the trianed model for the future predictions? For example, I want to enter today’s data of rain and evaporation and see the prediction of runoff for tomorrow. lstm, data prediction, neural networks, time series, regression MATLAB Answers — New Questions
How to fix “Are you up to date on software maintenance?”
Hi, I am a user with a perpetual Home license for MATLAB and Simulink. I currently want to purchase a toolbox (Simscape), but I’m getting this “Software Maintenance” error. How can I purchase and download the toolbox I want? Also, in my License Center, it shows that the end-of-service dates for MATLAB and Simulink are February 28, 2026, and July 31, 2026, respectively.Hi, I am a user with a perpetual Home license for MATLAB and Simulink. I currently want to purchase a toolbox (Simscape), but I’m getting this “Software Maintenance” error. How can I purchase and download the toolbox I want? Also, in my License Center, it shows that the end-of-service dates for MATLAB and Simulink are February 28, 2026, and July 31, 2026, respectively. Hi, I am a user with a perpetual Home license for MATLAB and Simulink. I currently want to purchase a toolbox (Simscape), but I’m getting this “Software Maintenance” error. How can I purchase and download the toolbox I want? Also, in my License Center, it shows that the end-of-service dates for MATLAB and Simulink are February 28, 2026, and July 31, 2026, respectively. maintenance, add-on-explorer MATLAB Answers — New Questions
how to add noise with vairience 0.002 in the code with mean 0
a = -1;
b = 1;
g = a + (b-a).*rand(1,250);
x = zeros(1,250);
k = zeros(1,250);
v = 0.01*randn(1,250);
for n = 1:250
k(n) = g(n) + 0.5*g(n)*g(n)*g(n);
end
for t = 6:250
x(t) = 0.8*(x(t-1) – 0.3*x(t-2) – 0.105*x(t-3) + 0.059*x(t-4)) …
+ 0.6*(x(t-2) – 0.3*x(t-3) – 0.105*x(t-4) + 0.059*x(t-5)) …
+ 0.4*(k(t-1) – 0.3*k(t-2) – 0.105*k(t-3) + 0.059*k(t-4)) …
– 0.2*(k(t-2) – 0.3*k(t-3) – 0.105*k(t-4) + 0.059*k(t-5)) …
+ v(t);
end
now i have to generate noise signal with variance 0.002 and mean 0,how to write codea = -1;
b = 1;
g = a + (b-a).*rand(1,250);
x = zeros(1,250);
k = zeros(1,250);
v = 0.01*randn(1,250);
for n = 1:250
k(n) = g(n) + 0.5*g(n)*g(n)*g(n);
end
for t = 6:250
x(t) = 0.8*(x(t-1) – 0.3*x(t-2) – 0.105*x(t-3) + 0.059*x(t-4)) …
+ 0.6*(x(t-2) – 0.3*x(t-3) – 0.105*x(t-4) + 0.059*x(t-5)) …
+ 0.4*(k(t-1) – 0.3*k(t-2) – 0.105*k(t-3) + 0.059*k(t-4)) …
– 0.2*(k(t-2) – 0.3*k(t-3) – 0.105*k(t-4) + 0.059*k(t-5)) …
+ v(t);
end
now i have to generate noise signal with variance 0.002 and mean 0,how to write code a = -1;
b = 1;
g = a + (b-a).*rand(1,250);
x = zeros(1,250);
k = zeros(1,250);
v = 0.01*randn(1,250);
for n = 1:250
k(n) = g(n) + 0.5*g(n)*g(n)*g(n);
end
for t = 6:250
x(t) = 0.8*(x(t-1) – 0.3*x(t-2) – 0.105*x(t-3) + 0.059*x(t-4)) …
+ 0.6*(x(t-2) – 0.3*x(t-3) – 0.105*x(t-4) + 0.059*x(t-5)) …
+ 0.4*(k(t-1) – 0.3*k(t-2) – 0.105*k(t-3) + 0.059*k(t-4)) …
– 0.2*(k(t-2) – 0.3*k(t-3) – 0.105*k(t-4) + 0.059*k(t-5)) …
+ v(t);
end
now i have to generate noise signal with variance 0.002 and mean 0,how to write code noise MATLAB Answers — New Questions
Power system simulink model converted from 2025a to 2017b have low frequency oscillations
Hi,
I am working on a Simulink model of a generator excitation system in 2025a that includes an IEEE AC11C-type exciter and a UEL2C (Under-Excitation Limiter) block. The complete model runs correctly and produces stable field voltage (Efd) when tested in MATLAB/Simulink R2025a, but the same exact model and parameters, when converted and run in MATLAB/Simulink R2017b, produces a persistent low‑frequency oscillation (~2–3Hz) in the exciter output (Efd), reactive power (Qt), real power (Pt), and various internal UEL2C signals.
The oscillation appears only when the UEL2C output is connected to the AC11C exciter.
If I bypass UEL2C and feed AC11C with a constant input, the oscillation disappears completely in 2017b.
Opening the same 2017b model file in 2025a makes the oscillation disappear again ─ system becomes stable.Hi,
I am working on a Simulink model of a generator excitation system in 2025a that includes an IEEE AC11C-type exciter and a UEL2C (Under-Excitation Limiter) block. The complete model runs correctly and produces stable field voltage (Efd) when tested in MATLAB/Simulink R2025a, but the same exact model and parameters, when converted and run in MATLAB/Simulink R2017b, produces a persistent low‑frequency oscillation (~2–3Hz) in the exciter output (Efd), reactive power (Qt), real power (Pt), and various internal UEL2C signals.
The oscillation appears only when the UEL2C output is connected to the AC11C exciter.
If I bypass UEL2C and feed AC11C with a constant input, the oscillation disappears completely in 2017b.
Opening the same 2017b model file in 2025a makes the oscillation disappear again ─ system becomes stable. Hi,
I am working on a Simulink model of a generator excitation system in 2025a that includes an IEEE AC11C-type exciter and a UEL2C (Under-Excitation Limiter) block. The complete model runs correctly and produces stable field voltage (Efd) when tested in MATLAB/Simulink R2025a, but the same exact model and parameters, when converted and run in MATLAB/Simulink R2017b, produces a persistent low‑frequency oscillation (~2–3Hz) in the exciter output (Efd), reactive power (Qt), real power (Pt), and various internal UEL2C signals.
The oscillation appears only when the UEL2C output is connected to the AC11C exciter.
If I bypass UEL2C and feed AC11C with a constant input, the oscillation disappears completely in 2017b.
Opening the same 2017b model file in 2025a makes the oscillation disappear again ─ system becomes stable. simulink model conversion 2017b, simulink model conversion, 2025a, 2017b MATLAB Answers — New Questions
How to create a .cvf file to exclude external m-files from coverage report?
Hi, I’m trying to exclude external m-files coverage from coverage report in Simulink Test. I tried creating coverage filter file refering to https://in.mathworks.com/help/slcoverage/ref/slcoverage.blockselector-class.html
I’m trying to exclude mutiple functions from coverage. Below is my edited script for it.
files = dir(‘*.m’);
for i = 1:length(files)
selector = slcoverage.BlockSelector(slcoverage.BlockSelectorType.BlockInstance, files(i).name);
filt = slcoverage.Filter;
rule = slcoverage.FilterRule(selector, ”, slcoverage.FilterMode.Exclude);
filt.addRule(rule);
end
setFilterName(filt,’MFileExclusion’);
save(filt,’MFileExclusion’)
I tried adding this cvf file to Simulink Test, but its not working. I’m using R2024a.
Is there an issue with the script? Is there any alternate solution here?
Thanks in advance.Hi, I’m trying to exclude external m-files coverage from coverage report in Simulink Test. I tried creating coverage filter file refering to https://in.mathworks.com/help/slcoverage/ref/slcoverage.blockselector-class.html
I’m trying to exclude mutiple functions from coverage. Below is my edited script for it.
files = dir(‘*.m’);
for i = 1:length(files)
selector = slcoverage.BlockSelector(slcoverage.BlockSelectorType.BlockInstance, files(i).name);
filt = slcoverage.Filter;
rule = slcoverage.FilterRule(selector, ”, slcoverage.FilterMode.Exclude);
filt.addRule(rule);
end
setFilterName(filt,’MFileExclusion’);
save(filt,’MFileExclusion’)
I tried adding this cvf file to Simulink Test, but its not working. I’m using R2024a.
Is there an issue with the script? Is there any alternate solution here?
Thanks in advance. Hi, I’m trying to exclude external m-files coverage from coverage report in Simulink Test. I tried creating coverage filter file refering to https://in.mathworks.com/help/slcoverage/ref/slcoverage.blockselector-class.html
I’m trying to exclude mutiple functions from coverage. Below is my edited script for it.
files = dir(‘*.m’);
for i = 1:length(files)
selector = slcoverage.BlockSelector(slcoverage.BlockSelectorType.BlockInstance, files(i).name);
filt = slcoverage.Filter;
rule = slcoverage.FilterRule(selector, ”, slcoverage.FilterMode.Exclude);
filt.addRule(rule);
end
setFilterName(filt,’MFileExclusion’);
save(filt,’MFileExclusion’)
I tried adding this cvf file to Simulink Test, but its not working. I’m using R2024a.
Is there an issue with the script? Is there any alternate solution here?
Thanks in advance. coverage, m file, matlab function MATLAB Answers — New Questions
Only File Exchange Access Denied When I Want to Access the File Exchange
When I want to access the File Exchange part of Mathworks Community, the following error message is displayed in my Edge browser:
Access Denied
You don’t have permission to access "http://ww2.mathworks.cn/matlabcentral/fileexchange/?" on this server.
Reference #18.2609e773.1773383091.143abaaa
https://errors.edgesuite.net/18.2609e773.1773383091.143abaaa
How to resolve this issue?When I want to access the File Exchange part of Mathworks Community, the following error message is displayed in my Edge browser:
Access Denied
You don’t have permission to access "http://ww2.mathworks.cn/matlabcentral/fileexchange/?" on this server.
Reference #18.2609e773.1773383091.143abaaa
https://errors.edgesuite.net/18.2609e773.1773383091.143abaaa
How to resolve this issue? When I want to access the File Exchange part of Mathworks Community, the following error message is displayed in my Edge browser:
Access Denied
You don’t have permission to access "http://ww2.mathworks.cn/matlabcentral/fileexchange/?" on this server.
Reference #18.2609e773.1773383091.143abaaa
https://errors.edgesuite.net/18.2609e773.1773383091.143abaaa
How to resolve this issue? access denied, file exchange MATLAB Answers — New Questions
loadlibrary unable to find
Hello,
I’m trying to use Dynamixel with MATLAB R2025b. It was working a few days, but then we tried setting up matlab on another user’s account (we all have individual licenses). At first it had pathdef.m issues, but we resolved it on that account. But then we got this issue when trying to test dynamixel
Error using loadlibrary
Failed to preprocess the input file.
Output from preprocessor is:In file included from C:UsersPublicDocumentsDynamixelSDK-4.0.3rosdynamixel_sdkincludedynamixel_sdkgroup_bulk_read.h:27,
from C:UsersPublicDocumentsDynamixelSDK-4.0.3rosdynamixel_sdkincludedynamixel_sdkdynamixel_sdk.h:26:
C:UsersPublicDocumentsDynamixelSDK-4.0.3rosdynamixel_sdkincludedynamixel_sdkpacket_handler.h:35:10: fatal error: vector: No such file or directory
#include <vector>
^~~~~~~~
compilation terminated.
Error in initialize_library (line 17)
[notfound, warnings] = loadlibrary(lib_name, ‘dynamixel_sdk.h’, ‘addheader’, ‘port_handler.h’, ‘addheader’, ‘packet_handler.h’, ‘addheader’, ‘group_sync_read.h’, ‘addheader’, ‘group_sync_write.h’);
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Error in run (line 112)
evalin(‘caller’, strcat(scriptStem, ‘;’));
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Error in main_7joint_sync_pegboard_v6_darsh (line 54)
run(‘initialize_library.m’)
We confirmed that MATLAB has the C/C++ compiler from MingW (from the Add-on Installer), and that mex -setup was using MingW for both C and C++. We’re not sure what could be causing this issue then.
When we switched back to my account (which had no issues a week ago), we were first hit with the pathdef.m issue again, and after resolving it (restoredefaultpath + savepath + adding dynamixel subfolders to path), we got the same error of being unable to find vector header file.
My hunch is that trying to setup other user accounts caused something to be dropped from the path, but I have no way of verifying this, or any ideas on how to fix the current issue on my account.Hello,
I’m trying to use Dynamixel with MATLAB R2025b. It was working a few days, but then we tried setting up matlab on another user’s account (we all have individual licenses). At first it had pathdef.m issues, but we resolved it on that account. But then we got this issue when trying to test dynamixel
Error using loadlibrary
Failed to preprocess the input file.
Output from preprocessor is:In file included from C:UsersPublicDocumentsDynamixelSDK-4.0.3rosdynamixel_sdkincludedynamixel_sdkgroup_bulk_read.h:27,
from C:UsersPublicDocumentsDynamixelSDK-4.0.3rosdynamixel_sdkincludedynamixel_sdkdynamixel_sdk.h:26:
C:UsersPublicDocumentsDynamixelSDK-4.0.3rosdynamixel_sdkincludedynamixel_sdkpacket_handler.h:35:10: fatal error: vector: No such file or directory
#include <vector>
^~~~~~~~
compilation terminated.
Error in initialize_library (line 17)
[notfound, warnings] = loadlibrary(lib_name, ‘dynamixel_sdk.h’, ‘addheader’, ‘port_handler.h’, ‘addheader’, ‘packet_handler.h’, ‘addheader’, ‘group_sync_read.h’, ‘addheader’, ‘group_sync_write.h’);
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Error in run (line 112)
evalin(‘caller’, strcat(scriptStem, ‘;’));
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Error in main_7joint_sync_pegboard_v6_darsh (line 54)
run(‘initialize_library.m’)
We confirmed that MATLAB has the C/C++ compiler from MingW (from the Add-on Installer), and that mex -setup was using MingW for both C and C++. We’re not sure what could be causing this issue then.
When we switched back to my account (which had no issues a week ago), we were first hit with the pathdef.m issue again, and after resolving it (restoredefaultpath + savepath + adding dynamixel subfolders to path), we got the same error of being unable to find vector header file.
My hunch is that trying to setup other user accounts caused something to be dropped from the path, but I have no way of verifying this, or any ideas on how to fix the current issue on my account. Hello,
I’m trying to use Dynamixel with MATLAB R2025b. It was working a few days, but then we tried setting up matlab on another user’s account (we all have individual licenses). At first it had pathdef.m issues, but we resolved it on that account. But then we got this issue when trying to test dynamixel
Error using loadlibrary
Failed to preprocess the input file.
Output from preprocessor is:In file included from C:UsersPublicDocumentsDynamixelSDK-4.0.3rosdynamixel_sdkincludedynamixel_sdkgroup_bulk_read.h:27,
from C:UsersPublicDocumentsDynamixelSDK-4.0.3rosdynamixel_sdkincludedynamixel_sdkdynamixel_sdk.h:26:
C:UsersPublicDocumentsDynamixelSDK-4.0.3rosdynamixel_sdkincludedynamixel_sdkpacket_handler.h:35:10: fatal error: vector: No such file or directory
#include <vector>
^~~~~~~~
compilation terminated.
Error in initialize_library (line 17)
[notfound, warnings] = loadlibrary(lib_name, ‘dynamixel_sdk.h’, ‘addheader’, ‘port_handler.h’, ‘addheader’, ‘packet_handler.h’, ‘addheader’, ‘group_sync_read.h’, ‘addheader’, ‘group_sync_write.h’);
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Error in run (line 112)
evalin(‘caller’, strcat(scriptStem, ‘;’));
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Error in main_7joint_sync_pegboard_v6_darsh (line 54)
run(‘initialize_library.m’)
We confirmed that MATLAB has the C/C++ compiler from MingW (from the Add-on Installer), and that mex -setup was using MingW for both C and C++. We’re not sure what could be causing this issue then.
When we switched back to my account (which had no issues a week ago), we were first hit with the pathdef.m issue again, and after resolving it (restoredefaultpath + savepath + adding dynamixel subfolders to path), we got the same error of being unable to find vector header file.
My hunch is that trying to setup other user accounts caused something to be dropped from the path, but I have no way of verifying this, or any ideas on how to fix the current issue on my account. mex, c++ MATLAB Answers — New Questions
<img src="https://app-pack.telkomuniversity.ac.id/wp-content/plugins/feedzy-rss-feeds/img/feedzy.svg" title="loadlibrary unable to find ” />
GPS Acquisition and Tracking on AMD RFSoC – Wrong PRNs from ADC Input (Loopback Works Fine)
Hi everyone,
I am working on the **GPS Acquisition and Tracking Using AMD RFSoC Device**
GPS Acquisition and Tracking Using AMD RFSoC Device – MATLAB & Simulink
reference design from MATLAB & Simulink, and I have run into a puzzling issue with the ADC path. I would really appreciate any insights from those who have worked with this design or with RFSoC ADC/DAC configurations in general.
**What Works**
In **loopback mode** (ADC input connected directly to DAC output), the system works perfectly — I can see correct PRN codes being acquired through the internal signal generator path.
**The Problem**
When I **disconnect the DAC** and feed real GPS data into the ADC (from a BladeRF via antenna or wire), I get **incorrect PRN codes**. The strange part is:
> **Even when the ADC is fully disconnected, I see those exact same wrong PRNs in the ILA (Integrated Logic Analyzer).**
This strongly suggests the issue is **not** with the incoming RF signal itself, but rather something internal — possibly a signal path that is not being properly muxed or gated when switching away from loopback, or a residual/default signal being driven onto the AXI-Stream bus when the ADC input is inactive.Hi everyone,
I am working on the **GPS Acquisition and Tracking Using AMD RFSoC Device**
GPS Acquisition and Tracking Using AMD RFSoC Device – MATLAB & Simulink
reference design from MATLAB & Simulink, and I have run into a puzzling issue with the ADC path. I would really appreciate any insights from those who have worked with this design or with RFSoC ADC/DAC configurations in general.
**What Works**
In **loopback mode** (ADC input connected directly to DAC output), the system works perfectly — I can see correct PRN codes being acquired through the internal signal generator path.
**The Problem**
When I **disconnect the DAC** and feed real GPS data into the ADC (from a BladeRF via antenna or wire), I get **incorrect PRN codes**. The strange part is:
> **Even when the ADC is fully disconnected, I see those exact same wrong PRNs in the ILA (Integrated Logic Analyzer).**
This strongly suggests the issue is **not** with the incoming RF signal itself, but rather something internal — possibly a signal path that is not being properly muxed or gated when switching away from loopback, or a residual/default signal being driven onto the AXI-Stream bus when the ADC input is inactive. Hi everyone,
I am working on the **GPS Acquisition and Tracking Using AMD RFSoC Device**
GPS Acquisition and Tracking Using AMD RFSoC Device – MATLAB & Simulink
reference design from MATLAB & Simulink, and I have run into a puzzling issue with the ADC path. I would really appreciate any insights from those who have worked with this design or with RFSoC ADC/DAC configurations in general.
**What Works**
In **loopback mode** (ADC input connected directly to DAC output), the system works perfectly — I can see correct PRN codes being acquired through the internal signal generator path.
**The Problem**
When I **disconnect the DAC** and feed real GPS data into the ADC (from a BladeRF via antenna or wire), I get **incorrect PRN codes**. The strange part is:
> **Even when the ADC is fully disconnected, I see those exact same wrong PRNs in the ILA (Integrated Logic Analyzer).**
This strongly suggests the issue is **not** with the incoming RF signal itself, but rather something internal — possibly a signal path that is not being properly muxed or gated when switching away from loopback, or a residual/default signal being driven onto the AXI-Stream bus when the ADC input is inactive. gps, rfsoc, hdl coder, soc, matlab, simulink, hdl, c/a code MATLAB Answers — New Questions
