FloWorks: Shared Resource

Question

question

Ville Teivastenaho asked Nov 13, '23 Jason Lightfoot commented Nov 17, '23

FloWorks: Shared Resource

Hi!

I cannot get the Shared Resource object from the FloWorks library to work. There isn't much about it in the manual or in the release notes, so I'm wondering is this object still functioning in the newer versions of FlexSim and FloWorks?

I have never used Shared Resource before, but this time I would need a solution to limit the total flow through multiple loading arms and its description sounds like it could be used for exactly this purpose.

Attached there is a simple model where I tried to test Shared Resource, but it only gives an following error:

"time: 0.000000 exception: Exception Caught in ObjectFunction250__project_library_FlexSimObject_behaviour_eventfunctions_OnTimerEvent object: /Tools/FlowControls/FlowControl1 class: /Tools/FlowControls/FlowControl1

time: 0.000000 exception: Exception caught in TreeNode::receivemessage()

time: 0.000000 exception: Exception caught in Executive::processeventinlist()."

SharedResourceTesting.fsm

Software Version:

FlexSim 23.2.1

FloWorks shared resources

sharedresourcetesting.fsm (36.0 KiB)

· 1

Jason Lightfoot ♦ commented · Nov 17, 2023 at 05:09 PM

Hi @Ville Teivastenaho, was one of Ville Teivastenaho's or Patrick Zweekhorst's answers helpful? If so, please click the "Accept" button at the bottom of the one that best answers your question. Or if you still have questions, add a comment and we'll continue the conversation.

If we haven't heard back from you within 3 business days we'll auto-accept an answer, but you can always comment back to reopen your question.

0 ·

Answer 1 · 2023-11-13T12:40:36Z

Patrick Zweekhorst answered Nov 13, '23

Hi @Ville Teivastenaho ,

This indeed seems to be a bug. We haven't made any changes to the shared resource lately, but it should still work. We are looking into the problem now. I will let you know when we have an update

· 3

Ville Teivastenaho commented · Nov 13, 2023 at 01:14 PM

Thank you @Patrick Zweekhorst. Are there any easy workarounds that you can think off that would create similar functionality or is it just better to wait for the fix?

0 ·

Patrick Zweekhorst Ville Teivastenaho commented · Nov 13, 2023 at 01:20 PM

Hi @Ville Teivastenaho ,

You can try to use the legacy solver for now:

This at least works for your test model and should still work good. The main improvement that has been made is a speed improvement.

Otherwise we need to think about a solution using ProcessFlow to take some more control in the model itself. The easiest thing would be to use the legacy solver.

0 ·

1699881342371.png (36.8 KiB)

Ville Teivastenaho Patrick Zweekhorst commented · Nov 13, 2023 at 01:30 PM

Thank you, I'll try that. So far the run speed hasn't been an issue for this model, so it shouldn't cause any major issues.

0 ·

question