question

Tyler B2 avatar image
0 Likes"
Tyler B2 asked Jason Lightfoot edited

Crash Issues

I apologize if this is not where the question should be placed.

This is a general question about the software, I tried to research a bit and couldn't find anything on some of the issues I have been having with the program.

I will attach a picture showing a few errors being thrown and a lack of racks, lifts, etc. All vanishing once I had saved the program. Is this a processing power issue or an internal one? I'm fairly new to the program still, is the process flow too rough to run well?

Beyond this I've had other odd reoccurring issues with the decide not changing once I had changed it (reverting to old values) along with a few other odds and ends doing the same. And some objects behaving incorrectly, though I believe some of these issues are due to the process flow influencing this not necessarily a bug.

To Summarize:

1) What is the processor requirements or possible hardware issues that would cause crashes?

2) Could you inform or direct me to a general process flow 'skeleton' that helps keep the work flow and code smooth

3) Any general information about current bugs or issues known/fixes that i could be pointed to would be very helpful.

Thank you for your assistance!

[Image and Program attached]

20C25M01R34.fsm

FlexSim 20.2.0
process flowflexsim 20.2.0crashbugs
flex-sim-crash.jpg (588.6 KiB)
20c25m01r34.fsm (376.7 KiB)
5 |100000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

1 Answer

Jason Lightfoot avatar image
0 Likes"
Jason Lightfoot answered Jason Lightfoot edited

If there are exceptions being output to the system console (as you show) then these really need to be addressed as priority as it's an indication that something(s) wrong with the model and could cause all sorts of unwanted behaviour.

The first exception relates to the Rack4b expecting to finish processing a box (case1: minimum staytime of 40s) that seems to have been removed before the 388.086s Process Finish event. Two boxes are moved into the rack at 282.17s and 348.09s but are removed at 361.32s

If you're having trouble coordinating the process flow with the FixedResource (3D) objects then I would encourage the use of pushing and pulling to global lists between the two.

I expect there are many styles for process flows but no design patterns/templates - you could try taking the best parts of the standard one for AGVs, and others your might find. You could also try to make the use of subflows (within the same process flow object or seperate ones) and have a high level flow that calls them. You can also split the connectors for a cleaner appearance.




twoboxesentrytimes.png (8.7 KiB)
5 |100000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.