[TRNSYS-users] TRNSYS early simulation stop

[keilholz, werner]

Michael,

I think the key to the problem is to find out if the problem is on the MATLAB or TRNSYS side. If MATLAB just shuts down, producing a log file (usually called something like hs_err_pidNNN.log where NNN is the process number), you should try to find the vector computed by TRNSYS producing the error and debug it in MATLAB alone. 

If it is not the MATLAB model which is unstable, you should try the opposite (produce a TRNSYS project without MATLAB which causes the same phenomenon). 

I'm afraid this is not much more than psychological support, but I've been through similar pain over the last 2 days (at the end one always finds a solution :-) ).

Werner

-----Message d'origine-----
De : Michael Casier [mailto:michael.casier at student.kuleuven.be] 
Envoyé : mardi 6 octobre 2009 08:11
À : trnsys-users at cae.wisc.edu
Objet : [TRNSYS-users] TRNSYS early simulation stop

Dear TRNSYS users

I have composed a simple configuration with some constant inputs, a MATLAB component, a printer and a plotter.  When I start the simulation, there is no problem.  But I try to do the simulation over a period of one year (8760h).  After 2917h - up to then, the plotter gives a correct output, and I receive also an output (.out)-file from the printer-  the simulation stops.  I receive an error, but without specifications.  When I try to deduce details about ther error, by giving the command 'lasterror" in Matlab, I get no answer. 

My Matlab component type 155 has 7 inputs and 4 outputs.  I have already tried a lot of things to solve the problem, but nothing works. It may be a problem of 'out of memory', but I don't know how to solve that.  

Is there somebody who can help me?  I 've been searching already for 4 days now.

Thanks a lot

Yours sincerely

Michael Casier
Student civil engineer KULeuven
_______________________________________________
TRNSYS-users mailing list
TRNSYS-users at cae.wisc.edu
https://www-old.cae.wisc.edu/mailman/listinfo/trnsys-users