I am working on a model in Dymola and use the Dymola S-block in Simulink to compile the model and then run the model in Simulink. After a few compilations, the interface stops working with the error in the Matlab workspace as
Error using ddereq
The first argument 'channel' is not valid.
Error in newDymolaGuiJava
Error in newDymolaGuiJava
Error in newDymolaGui Error while evaluating UIControl Callback.
I have to restart Matlab every time I encounter this to make it work. And it happens very frequently. I'm not sure what the problem is.
Related
I'm currently changing Simulink Ext Mode to xcp. Now i'm running into the Issue DWARF Parser internal error: Parser::describeSymbol xcpDummyDoubleVariable is not a global variable. According to this post, the issue should have been fixed but it still doesn't work.
https://de.mathworks.com/matlabcentral/answers/703597-dwarf-parser-internal-error-parser-describesymbol-xcpdummydoublevariable-is-not-a-global-variable
I also tried the first approach (the second one is already active in version 22b) but the Error still occurs.
Have u got any suggestions why the error still occurs?
When Compiling Simulink Model based on NI Veristand
, I get a Model error - Error: NI Veristand Error: Invaild character in ‘model path’, exiting code generation. The name cannot start or end with / character.Then I check the model in model of the path, but don’t find relative character.
Finally I need to do something to solve this problem.
Name of simulink model hides part. And Compiling Simulink Model is correct after deleting hidden part.
This error may appear if some of the Simulink blocks are unnamed. Please make sure all blocks are named and try compiling again.
Using mosek in cvxpy, I'm getting the error that the solver failed. Is there a way to recover the error code from Mosek? Cvxpy doesn't seem to provide it.
Cvxpy ignores it. However, you can hack it by changing the line in mosek_coinf.py that does task.optimize and retrieving the response code according to https://docs.mosek.com/8.1/pythonapi/optimizer-task.html#mosek.task.optimize
Moreover, if you enable logging (verbose=True) then you should see from the solver log what happened.
I have a model designed with Matlab/Simulink R2017a and it is running well with no errors or warning messages in Diagnostic Viewer or MATLAB Command Window when I run it diretly from the Simulink.
However, when I start a build process on ConfigurationDesk from dSPACE to use this model in an embedded application the build process is aborted and the following message is shown:
Could not generate model code for model 'Model'. See MATLAB Command Window for details.
In MATLAB Command Window the following message is shown:
Struct contents reference from a non-struct array object.
================================================================================
Aborted Model-Code Generation for Model "Model".
================================================================================
As you can observe In MATLAB Command Window, there is no enough details about the error and due that I'm not being able to fix it.
There is any way to get more details about the error in order to track down it?
Thank you so much in advanced!
I cannot run state flow diagram from Matlab. I am using Matlab 2013b. Whenever I try to run it it gives a warning:
Warning: The model 'xyz' does not have continuous states, hence
Simulink is using the solver'FixedStepDiscrete' instead of solver
'ode4'. You can disable this diagnostic by explicitly specifying a
discrete solver in the solver tab of the Configuration Parameters
dialog, or by setting the 'Automatic solver parameter selection'
diagnostic to 'none' in the Diagnostics tab of the Configuration
Parameters dialog
However I have modified the above mentioned two requirement from configuration setup. But it is still showing problem. Do I need to set up some additional software to fix this problem?
This is just a warning, not an error message, your model will run just fine as is. If you want to get rid of the message, change the solver in the model to FixedStepDiscrete instead of ode4 and it will go away, but it won't change anything in the actual running of the model.