Hi, and welcome to our Community!
Hard to say what the reason could be.
About “no logger info”: when you delete the Temp folder, also the simulation state is deleted. That means, after deletion and restarting the simulation from Automation Studio, the ArSim starts “blank” with an empty default configuration, as the last state and transferred content was deleted. So even if there have been logger entries before, they are also deleted after deleting Temp.
So can you please check the running but offline ArSim instance for messages before deleting Temp?
The’re some possibilities to do so:
If SDM is activated, try to open SDM by “http://localhost/sdm” (maybe it’s still online, we don’t know by now) create a system dump → this archive file then includes all loggers:
… or copy directly the logger file from the Windows filesystem.
The file path "Temp\Simulation< Name of config > \ < Name of CPU > \ RPSHD \SYSROM should contain a file named “arlogsys.br” (see example screenshot) → this is the logger module
Logger files can be loaded offline in Automation Studio (Open → Logger → Load data…) and analysed there.
… if retreiving the logger is not possible, you could open the still running ArSim window → Console → copy the text inside the console and paste it here (see sample screenshot, but please note: having logger files is better then just having text, as the logger files could include some more information):
Coming back to your behavior described:
From my experience, most often I’ve seen such behavior a) because of a memory violation (e.g. caused by string or memory operations into too small destination memory), or b) by some “endless condition” in INIT or EXIT program.
But as I said, it’s hard / impossible to conclude that just because of the behavior described, there’s more investigation needed.
A good test is creating a new small project just with some basic task and setup and try to build & transfer this small test project to ArSim → does that work as expected? If yes it’s still no proof, but a strong hint that the cause it the content of the non-working project itself is the cause.
Best regards!
