Model crashing FlexSim, unrepeatable errors...

Question

question

Marcello Rosadini asked Apr 24, '17 Marcello Rosadini commented Apr 26, '17

Model crashing FlexSim, unrepeatable errors...

Hi,

we are working on a model that is, unfortunately, throwing many errors, the problem is that they are completely unrepeatable... the model sometimes runs, sometimes crashes, sometimes crashes the entire FlexSim instance (and computer) and sometimes just gets blocked. Other times (the few) just runs fine. Also, error duration and frequency changes depending on the version used 17.0 against 17.1

Could you please take a look at it? We are really pressured to deliver this and just can't figure out any other alternative.

Thanks

Software Version:

FlexSim 17.1.0

error messages crashing

· 4

Jeff Nordgren commented · Apr 24, 2017 at 04:03 PM

@marcello.rosadini

I ran your model 10 times without any errors showing up. Now, I did run it in the latest FlexSim version of the software, 17.1.1. Maybe try that version and see what results you get?

0 ·

Marcello Rosadini Jeff Nordgren commented · Apr 24, 2017 at 04:11 PM

@Jeff Nordgren I've just downloaded the model you posted and ran it twice to completion in 17.1.1 (around 55000 secs) an then on the 3rd run at a lower speed FlexSim crashed at about 215 secs

This is what I've experienced, different times of crashing, different errors, and that's what makes it difficult to sort outcaptura2.png

another one at 15677 secs

captura3.png

0 ·

captura2.png (470.1 KiB)

captura3.png (398.1 KiB)

Jacob Gillespie ♦ commented · Apr 24, 2017 at 04:27 PM

@marcello.rosadini I just ran the model you posted in 17.1.1 and it crashed at time 163. So it isn't just you!

0 ·

Marcello Rosadini commented · Apr 24, 2017 at 05:21 PM

Thanks @Jacob Gillespie. Maybe someone from the dev team can take a look? @phil.bobo @anthony.johnson

0 ·

Answer 1 · 2017-04-24T19:49:16Z

Phil BoBo answered Apr 24, '17 Marcello Rosadini commented Apr 26, '17

The crashes in this model are being caused by two bugs in the new FlexScript compiler:

1. The FlexScript compiler is not properly handling the min() command with a dynamic property label access as one of the parameters. You can workaround this bug by changing your min() commands to minof() in the place in bay and place in level code in your racks. You can use find/replace in the tree to make this change quickly.

2. The FlexScript compiler is not properly handling the code in your "Agv" process flow in the "Get remaining section length" activity. If you split that out into custom code without a ternary operator, then it works around the issue:

if (current.section==1)
	return cpdistance(agvinfo(current, AGV_CURRENT_CP), token.section2);
else
	return cpdistance(agvinfo(current, AGV_CURRENT_CP), token.section1);

I have added cases to the dev list to look into fixing these bugs, but for now, you can use the workarounds provided to avoid the crashing.

· 3

Marcello Rosadini commented · Apr 25, 2017 at 07:36 AM

Thank you very much @phil.bobo Model is stable now with your recommendations. I originally meant to post this question as private, but missed the check box. Apparently is not possible to change a posted question to private after posted? Thanks

0 ·

Ben Wilson ♦♦ Marcello Rosadini commented · Apr 25, 2017 at 04:04 PM

@marcello.rosadini,

Correct, a question can't be changed to private (or vice versa) after it has been posted.

You could remove your attachment for better privacy, while still keeping this information regarding the bugs and workarounds public.

EDIT: Looks like Phil already removed the attachment.

0 ·

Marcello Rosadini Ben Wilson ♦♦ commented · Apr 26, 2017 at 04:03 PM

thanks @Ben Wilson!

0 ·

question