topic Re: Custom Task Sequence using PF in FlexSim Forum

Custom Task Sequence using PF

SimFlex_support — Fri, 13 Apr 2018 14:12:32 GMT

[ FlexSim 18.1.0 ]

eflexsim-projectsgpproject-fileslgpark2018180411-s.fsm

I will try to make a model of custom task sequence like below;

The processors have not any buffer before or after themselves.

After the processor finish the job, a AGV should move new item from QueueFrom to the processor.

And the AGV should load the finished item from the processor and then unload the new moved item to the processor.

And the AGV move the finished item to the QueueTo and the AGV come back to QueueFrom to finish the task sequence.

The repeated Task-Sequence starts according to the processors finish the jobs.

3D model is good but using PF is good also.

Help me!

Re: Custom Task Sequence using PF

Matthew_Gillespie — Fri, 13 Apr 2018 17:48:10 GMT

This model works pretty well without Process Flow, I just A connected the processors and checked the Use Transport box for each.

eflexsim-projectsgpproject-fileslgpark2018180411-s.fsm

Re: Custom Task Sequence using PF

jeff_nordgren — Fri, 13 Apr 2018 18:51:56 GMT

@david.seo,

Attached is your model with the changes that I made to your PF to do what you are describing. Take a look at the model and see if something like this would work for you.

Thanks.

david-eflexsim-fileslgpark2018180411-s-jn1.fsm

Re: Custom Task Sequence using PF

SimFlex_support — Fri, 13 Apr 2018 21:18:46 GMT

Dear @Jeff Nordgren. That's my looking for solution.

Yes. Thank you very much.

The process flow mudule is not easy for me to make the model.

Re: Custom Task Sequence using PF

SimFlex_support — Fri, 13 Apr 2018 21:36:16 GMT

@Jeff Nordgren

I found the model is good in flexsim 2018.0.4 but it happens error like below when running flexsim 2018 update 1.

What's the matter? I guess Flexsim 2018 update 1 has a bug.

Please check it.

Thanks.

Re: Custom Task Sequence using PF

jeff_nordgren — Fri, 13 Apr 2018 23:11:04 GMT

@david.seo,

I'm not sure why version 2018.1 broke it. It seems like the P_Item label that is being assigned in the Source (PF) works in 2018.0.4 but not in 2018.1. I'm wondering if @Logan Gold, @Sam Stubbs, @Jacob Gillespie, @Ben Wilson or @phil.bobo might have some insight into what changed in 2018.1?

Anyway, I added an Assign Labels block to the PF to create a new/different reference for P_Item which will make it work again. I'm just not sure why that has to be done.

Thanks.

david-eflexsim-fileslgpark2018180411-s-v20181-jn1.fsm

Re: Custom Task Sequence using PF

philboboADSK — Mon, 16 Apr 2018 15:20:33 GMT

What version of FlexSim did you build this with, Jeff? Some version of the 2018 Update 1 Beta?

The Event-triggered Source's Label Assignment table is busted in this model. I don't know how it got into that state.

I tried to replicate this issue by building a similarly configured Event-triggered Source in 18.0 and updating it to 18.1, but that worked fine. Also building a new Event-triggered Source with the same configuration in 18.1 worked fine.

How did this activity get into this state?

Re: Custom Task Sequence using PF

SimFlex_support — Mon, 16 Apr 2018 21:08:21 GMT

@phil.bobo and @Jeff Nordgren

I made it using 2018.0.4 in first and uploaded it. And Jeff finished it.

But I don't know which version Jeff used. He will answer about it.

Re: Custom Task Sequence using PF

jeff_nordgren — Tue, 17 Apr 2018 21:16:19 GMT

@phil.bobo,

I used 2018.0.4 as well. I never send models back in a beta version. I just took David's model and loaded it into 2018.0.4. At least it doesn't appear to be a problem then if you can do it in both versions.

@david.seo

I would just try building it in 2018.1 and see if it works.

Thanks.

Re: Custom Task Sequence using PF

philboboADSK — Tue, 17 Apr 2018 21:18:12 GMT

OK. That's the problem. You opened an 18.1 model in 18.0.4 and saved it. You shouldn't edit models from newer versions in older versions of the software.

The model was an 18.1 model, but you added an 18.0 activity to it, so the activity isn't going through the update process when you open it in 18.1.

I'll add a case to the dev list to try to prevent users from editing newer versions of models in older versions of the software.