topic Re: OnBeginOffset in processflow in FlexSim Forum

OnBeginOffset in processflow

aa0976382405 — Wed, 01 Jun 2022 12:36:04 GMT

[ FlexSim 20.0.10 ]

Dear all:

There are three attachment below. Name called "basicturntables" is the reference I want to use. I had using the code of OnBeginOffset to processflow.

Name called "use token" is assign labels to X Location, Y Location,...rotatewhiletraveling in event-triggered source, and let variables be token.xloc ,token.yloc in the code node. But it will have system console.v

Name called "use param" is didn't assign labels to X Location, Y Location,...rotatewhiletraveling in event-triggered source, and let variables be param in the code node. But it still will have system console.

While I am debugging, the results of variables using param will same as the results using OnbeginOffset in the trigger, which is the attachment called basicturntables.

basicturntables.fsm use param.fsm use token.fsm

Re: OnBeginOffset in processflow

jason_lightfoot_adsk — Wed, 01 Jun 2022 13:57:08 GMT

Here is some student level guidance:

Change your process flow to an object based one so that you can refer to 'current' as the basicTE (you can copy the activities across and edit the fields).
Add your BasicTE20 instance as a member of that process flow.
In the OnBeginTravel offset event triggered source activity assign the token label values
Check the "Override return value" on the event triggered source
Use an "AssignLabel" activity to write the kinematicDelay label to your token.
Use code of the label value to return the correct delay - using the code you have in "Rotate to the offset location.....etc". Preserve the default header and remove any duplicated local variables you have in "Rotate to the offset location....." code.
Change the references in that code to read token.xloc, token.yloc instead of param(1), param(2) etc as these are used by the default header (you do this correctly in UpdateKinematics so not sure why you're not doing the same thing in your "Rotate to the offset location..." code.
Add a "Finish" activity instead of a sink and select the "kinematicDelay" label as the value to be returned.

The OnBeginOffset section should look like this:

Re: OnBeginOffset in processflow

aa0976382405 — Wed, 01 Jun 2022 17:28:21 GMT

Should it be like this:

Re: OnBeginOffset in processflow

jason_lightfoot_adsk — Wed, 01 Jun 2022 17:46:08 GMT

You don't need to assign all those labels in the AssignLabels activity - that's there just to record the return value of the kinematic code you have - all those labels listed should be set by the EventTriggered Source. So the AssignLabels activity just set the value of one label called, for example, "kinematicDelay" which you then use on the Finish activity as the return value. The expression to return that is just :

token.kinematicDelay

Again the value field of the label should be kinematic code that returns the time.

Re: OnBeginOffset in processflow

aa0976382405 — Thu, 02 Jun 2022 01:37:46 GMT

Did you mean be like this:

Besides, should I keep the Custom Code?

Re: OnBeginOffset in processflow

jason_lightfoot_adsk — Thu, 02 Jun 2022 02:21:06 GMT

Yes - now your custom code that creates the kinematics goes into the kinematicDelay label's Value field.

Re: OnBeginOffset in processflow

aa0976382405 — Thu, 02 Jun 2022 02:29:43 GMT

But the BasicTE still doesn't work.

Re: OnBeginOffset in processflow

jason_lightfoot_adsk — Thu, 02 Jun 2022 02:32:00 GMT

Did you check the code headers and update the variables so that they're reading token.xloc instead of param(5) (for example). ?

You can step through the kinematic code using the debugger and look at the local variable to check you've assigned them correctly.

Re: OnBeginOffset in processflow

aa0976382405 — Thu, 02 Jun 2022 02:33:53 GMT

Yes. It will be like this, right?

Re: OnBeginOffset in processflow

jason_lightfoot_adsk — Thu, 02 Jun 2022 10:28:06 GMT

Mostly - but I don't see where the token is assign x, y and z - in the event driven source you set up xloc, yloc and zloc - so you you should be using those.

Are you not getting error messages to tell you as much when you run it or step through the code?

Re: OnBeginOffset in processflow

aa0976382405 — Fri, 03 Jun 2022 16:15:03 GMT

Sorry, I update the wrong picture. There isn't any error mesage came out. My process flow will be like this:

Re: OnBeginOffset in processflow

jason_lightfoot_adsk — Fri, 03 Jun 2022 16:37:45 GMT

Right but the code you show needs to be in the Value of the kinematicDelay label - it looks like that's still 0.00

Re: OnBeginOffset in processflow

aa0976382405 — Fri, 03 Jun 2022 16:46:12 GMT

So what value should I change to?

Re: OnBeginOffset in processflow

jason_lightfoot_adsk — Fri, 03 Jun 2022 18:20:30 GMT

Edit the code for the value and paste in your kinematic code you show above. Click the pull down option for the value and choose "Code Editor"

Re: OnBeginOffset in processflow

aa0976382405 — Sat, 04 Jun 2022 18:01:41 GMT

I've tried it. But it still doesn't work. And there is no any error message come out.

Re: OnBeginOffset in processflow

jason_lightfoot_adsk — Sat, 04 Jun 2022 21:35:46 GMT

Can you upload the model?

Re: OnBeginOffset in processflow

aa0976382405 — Sun, 05 Jun 2022 07:30:49 GMT

No problem.0605.fsm

Re: OnBeginOffset in processflow

jason_lightfoot_adsk — Sun, 05 Jun 2022 14:52:19 GMT

You still hadn't checked - "override return value" of the OnBeginOffset event driven source.

I moved the other activities into the Object Process Flow and reattached their events (OnUpdateOffset was not connected for example).

0605_jl.fsm

Re: OnBeginOffset in processflow

aa0976382405 — Sun, 05 Jun 2022 16:45:59 GMT

Sorry, I forget to check it. Thank you so much!
By the way, can you explain the difference between the model I first updated and the new one?

Re: OnBeginOffset in processflow

jason_lightfoot_adsk — Mon, 06 Jun 2022 11:24:44 GMT

I don't know what more to tell you other that I checked the box, changed the label name (spelling only!), and moved the activities from the GeneralProcess Flow to the Object Flow for the BasicTE20/turntable. That last item involved changing the references to the BasicTE20 to "current" so that you can use it with multiple turntables and re-sampling the object events. (I also didn't add all the label assignments for OnUpdateOffset, OnFinishOffset - since you just need the one to tell you if offsetting now.