Warning: Error using Simulink.SLXPart (line 74)
Mostrar comentarios más antiguos
Hello,
recently, i keep getting this warning whenever i run or save my simulink model:
Warning: Error using Simulink.SLXPart (line 74)
Part name must start with a slash
Error in slxPackager/partDefResources>i_partinfo
Error in slxPackager/partDefResources>i_save
Error in Simulink.SLXPartHandler/pExecute (line 105)
feval(cb,packager);
Error in Simulink.SLXPartHandler/doSave (line 66)
pExecute(obj(i),packager,cb,'Save',logger);
Error in Simulink.SLXPartHandlerRegistrar/executeSaveCallbacks (line 94)
doSave(obj.getHandlers,packager);
Error in slxPackager/executeSaveCallbacks
Error in slxPackager/save
Error in slprivate (line 11)
[varargout{1:nargout}] = feval(function_name, varargin{1:end});
Error in SimulinkStudio.callbacks.saveCB (line 14)
SLM3I.saveBlockDiagram( cbinfo.model.Handle );
Error in SLStudio.ToolBars
Please give me some tipps on how to solve this issue, thanks :)
Brian
2 comentarios
Sobhi Zeidan
el 4 de Dic. de 2019
Hello,
DId you ever get this issue resolved?
Regards,
Sobhi
Tet Kong Brian Chia
el 8 de Dic. de 2019
Respuesta aceptada
Himani Raina
el 29 de En. de 2020
0 votos
This typically happens when there are unresolved image annotations in the model. When copying an image from the clipboard as an annotation into the model, Windows may not preserve the right path name. So when copying from the clipboard the Windows path may point to a temp folder or a URL if it is from your browser. The result is an annotation with a missing image and hence you get this warning when you try to save the model. The problem should be resolved by using the insert image dialog box for your annotations.
4 comentarios
Tet Kong Brian Chia
el 17 de Feb. de 2020
Firas
el 17 de Jul. de 2020
Andrew De Bruin
el 13 de En. de 2021
Editada: Andrew De Bruin
el 13 de En. de 2021
Is there a method to easily identify these unresolved image annotations? The warning does not provide a link/path to the offending image.
Firas
el 6 de Mzo. de 2024
Thank you very much. After 4 years I went through my model block by block and I found two image annotations that I deleted and resolved this issue.
Más respuestas (1)
Jochen Lenz
el 12 de Jul. de 2024
I also just had this problem - and it is really annoying. Here is a proposal about how to find such broken annotations, where "bdroot" is the actual Simulink model:
clc
hAnno = find_system( bdroot, ...
'FindAll', 'on', ...
'Type', 'annotation' ...
);
for n = 1 : length(hAnno)
disp('-----------------------------------------');
disp( [' > ' get_param(hAnno(n), 'Parent') ':'] );
disp( get_param(hAnno(n), 'Name') );
end
In the resulting list on the commandscreen, you might see XML-like content, beginning with
<!DOCTYPE HTML PUBLIC ...>
When you see content like this, then it's ok:
<img src="[$unpackedFolder]/simulink/resources/mwimg_ ... -8fae7932e4e5.tif"/>
When you however see something like this, then it might be the cause of your problem:
<img src="D:\users\ ... /mwimg_ ... -2160b69c8c0c.png" />
The, use the Parent of the annotation to navigate to the Simulink SubSystem.
Categorías
Más información sobre Programmatic Model Editing en Centro de ayuda y File Exchange.
Productos
el 17 de Sept. de 2019
el 12 de Jul. de 2024
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!
Translated by 
