Dashboard error while using process flow logic

Question

question

G C asked May 19, '16 Brandon Peterson edited Jun 22, '16

Dashboard error while using process flow logic

I'm using process flow to dictate all logic within my 3d model. I want to get utilization statistics back from my operators, but they do not change states while using logic from process flow. To fix this, I added a custom code before my delay bubble with these lines:

treenode operator = getlabel(token, "Operator Resource");
treenode ts = createemptytasksequence(operator, NULL, NULL);
inserttask(ts, TASKTYPE_UTILIZE, item, NULL, 0);
dispatchtasksequence(ts);

I added the same code after the delay bubble, except it is releasing my operators. This seems to work, and I can see my operators changing states. However, when I now try to get statistics from the 3d model, I get this error:

exception: Exception caught in flexscript execution of VIEW:/active/StateAnalysisProperties579109024/tabcontrol/Colors/Scroll/Panel>eventfunctions/getRGBColor line 18 instruction 120 (evaluating command parameter 1 as number). Discontinuing execution.

exception: Exception caught in flexscript execution of VIEW:/active/StateAnalysisProperties579109024/tabcontrol/Colors/Scroll/Panel>eventfunctions/getRGBColor line 18 instruction 120 (evaluating command parameter 2 as number). Discontinuing execution.

exception: Exception caught in TreeNode::callMemberFunction() flexscript execution VIEW:/active/StateAnalysisProperties579109024/tabcontrol/Colors/Scroll/Panel>eventfunctions/getRGBColor c: VIEW:/active/StateAnalysisProperties579109024/tabcontrol/Colors/Scroll/Panel theclass: VIEW:/active/StateAnalysisProperties579109024/tabcontrol/Colors/Scroll/Panel

How do I fix this?

Software Version:

FlexSim 16.0.1

process flow operator statistics utilization state chart

· 2

Jeff Nordgren commented · May 19, 2016 at 07:02 PM

C G,

Without an actual model (or sample of the problem) to look at, it becomes very difficult to answer anything specific about how the model is working or should work.

Is it possible to send the model or a sample that we can look at?

Thanks,

0 ·

G C Jeff Nordgren commented · May 19, 2016 at 07:18 PM

help-model.fsm

Here is a stripped down version of my model. Notice that the state on the operators are changing. Try adding a state bar and select the 3 operators as objects to use in the state bar. This is when the error will appear in the console.

0 ·

help-model.fsm (656.6 KiB)

Answer 1 · 2016-05-24T00:14:10Z

Jeff Nordgren answered May 24, '16 G C commented May 25, '16

G C,

I'm not really sure what is up with your model. I can't seem to track it down. But I did create my own, like yours, with some differences in the ProcessFlow blocks. The model seems to work for me. Take a look at it and see if you have any questions or comments about what I have done.

Thanks.

my-help-model-fs1.fsm (56.0 KiB)

· 1

G C commented · May 25, 2016 at 08:17 PM

It ended up being a problem with the operators. Maybe they were corrupted or had bad settings? Adding new operators from scratch fixed my issue.

Thanks,

-GC

0 ·

Answer 2 · 2016-05-25T20:55:28Z

Jordan Johnson answered May 25, '16

As far as I can tell, this problem was caused by a bug with the state profile mechanism, which was updated in version 16.0. At some point, the operator's state was set to 101, which added 50 states to the operator's state profile. In version 7.7, those state had names like "state 51" and "state 52", etc. In version 16.0, due to a bug, new state names are all set to "NULL".

The chart assumed that all state names would be unique, but since 50 states are all named "NULL", that isn't true anymore. This bug will be fixed in future releases. Thanks for bringing it to our attention!

Answer 3 · 2016-05-19T23:33:41Z

Jeff Nordgren answered May 19, '16 Paul Toone edited May 20, '16

operator-dashboard-sample-fs1.fsm

G C,

While I'm looking at your model, attached is a simple model that I've created to show that using Process Flow, the Operator stats seem to show up just fine.

Take a look at the model and see what you think. In the mean time, I will look at your model.

Thanks.

operator-dashboard-sample-fs1.fsm (25.5 KiB)

question