can outobject command be cascaded?

Question

question

Edwin Purwanto asked Jul 19 2016 at 6:58 AM Brandon Peterson commented Jul 21 2016 at 12:21 PM

can outobject command be cascaded?

Hello,

In this case, we just need to distribute the flowitem moving in conveyor into an empty buffer placed alongside it. Actually we can make it work using just a command of content(node("queue110",model())) for instance, but to set it like that while we have quite lots of buffer (queue110 being a particular buffer), it become tedious.

So I thought of using pointer outobject, as follow (this script is at on arrival on each decision point):

int contentleft = content(outobject(outobject(current, 1), 1));
int contentright = content(outobject(outobject(current, 2), 1));
 
if (contentleft < 1) { // check left buffer space
	// send to left buffer space
	conveyorsenditem(item, outobject(outobject(current, 1), 1));
} else if (contentright < 1) { // check right buffer space
	// send to right bufferspace
	conveyorsenditem(item, outobject(outobject(current, 2), 1));
} else // continue
	return 0;

But this command result in an error as below.

time: 302.369221 exception: Exception caught in flexscript execution of MODEL:/DP100>variables/localType/onArrival line 8 instruction 19. Discontinuing execution.

So I was under impression that the cause of this error is most likely because I cascade the outobject. is this possible to be done? or some syntax error?

Thank you very much for your kind help

Best Regards,

Edwin

conv-dist.png

Software Version:

FlexSim 16.1.0

conveyor decision point outobject

conv-dist.png (324.9 KiB)

· 4

Edwin Purwanto commented · Jul 20 2016 at 1:17 AM

Hello all, thank you very much for your answer.

So, to conclude from all of your advice that the main problem is from the conveyorsenditem command.

However, when I tried only this command

int contentright = content(outobject(outobject(current, 2), 1));

I still get the same error, so i have no idea on how to dynamically check the content of the buffer for now, instead of one by one doing content(node("queue110",model())).

Thanks and best regards,

Edwin

0 ·

Brandon Peterson ♦ Edwin Purwanto commented · Jul 20 2016 at 12:30 PM

Edwin,

If you post your model I can look at it and tell you what is going wrong with your function call. From your picture it looks like you should not be having any problems.

If you make an output connection (holding "A") from the conveyor to the second queue then you should get a different exit transfer that you can place on the opposite side of the conveyor. You may need to move the second queue to a temporary location that is further down the conveyor from the 1st queue when you make the connection and then move it back to its proper location.

Brandon

5 ·

Edwin Purwanto Brandon Peterson ♦ commented · Jul 21 2016 at 9:02 AM

Hello Mr Peterson,

Thanks a lot for your help, actually I alter it with all queue goes to 1 exittransfer.

But I am anyway still curious on how this thing happen, so I also attach the model here.

Here, DP8 should direct at least 1 flowitem each buffer. It is not done.

test9.fsm

0 ·

test9.fsm (71.1 KiB)

Edwin Purwanto Edwin Purwanto commented · Jul 20 2016 at 1:29 AM

Another question is regarding the characteristic of exitransfer. Whenever I tried to make connection on the other side, it is compacted in one exitransfer.

Actually, if there is two exitransfer, it makes the work rather easier, but It seems i cannot do it, what is the problem here?

0 ·

______

Cookie preferences

Your privacy is important to us and so is an optimal experience. To help us customize information and build applications, we collect data about your use of this site.

May we collect and use your data?

Learn more about the Third Party Services we use and our Privacy Statement.

Strictly necessary – required for our site to work and to provide services to you

These cookies allow us to record your preferences or login information, respond to your requests or fulfill items in your shopping cart.

YES

Improve your experience – allows us to show you what is relevant to you

These cookies enable us to provide enhanced functionality and personalization. They may be set by us or by third party providers whose services we use to deliver information and experiences tailored to you. If you do not allow these cookies, some or all of these services may not be available for you.

YES

NO

Customize your advertising – permits us to offer targeted advertising to you

These cookies collect data about you based on your activities and interests in order to show you relevant ads and to track effectiveness. By collecting this data, the ads you see will be more tailored to your interests. If you do not allow these cookies, you will experience less targeted advertising.

YES

NO

Are you sure you want a less customized experience?

We can access your data only if you select "yes" for the categories on the previous screen. This lets us tailor our marketing so that it's more relevant for you. You can change your settings at any time by visiting our privacy statement

Your experience. Your choice.

We care about your privacy. The data we collect helps us understand how you use our products, what information you might be interested in, and what we can improve to make your engagement with Autodesk more rewarding.

May we collect and use your data to tailor your experience?

Explore the benefits of a customized experience by managing your privacy settings for this site or visit our Privacy Statement to learn more about your options.

Answer 1 · 2016-07-19T12:11:56Z

Brandon Peterson answered Jul 19 2016 at 12:11 PM Brandon Peterson commented Jul 21 2016 at 12:21 PM

Edwin,

Your problem is not being caused by cascading the outobject command. You can cascade the outobject, inobject, and centerobject commands as much as you want. The problem is that the object you are returning is not to a point within the conveyor system. In the image you shared in your post it appears that the reference you are returning is to one of the queues connected to the conveyor.

The description for the conveyorsenditem command states that the destination must be a "decision point, a photo eye, or an exit transfer." The destination must also be reachable from the current location within the conveyor system, or in other words, it must be downstream from the current location.

As the queues cannot be part of the conveyor system you would need to specify an alternate location. I would recommend that you specify the exit transfer in the conveyorsenditem command and then use the "Send To Port" trigger on the exit transfer to send the item to the appropriate queue.

I hope this helps,

Brandon

· 1

Brandon Peterson ♦ commented · Jul 21 2016 at 12:21 PM

Edwin,

Here is your model with some corrections so that it will work. Here are the changes that I made and why:

Changed the Arrival code of DP8
- Both Queues were still using the same exit transfer and as a result your content code was not looking in the correct place for one of the queues.
- Set a label on the item that tells the exit transfer which port to send the item to.
Moved DP8 closer to the queues, set the Item Edge value to leading, and changed the Send To Port field.
- With DP8 so far away from the queues it was sending multiple items to the same queue because the queue was still empty when the following items would reach DP8
- Set the Item Edge to leading so that I could place DP8 as close the the queue exit transfer as possible
- I changed the send to port field to send to the port specified by a label that I set in the Arrival code of DP8
Removed the output port connections on the queues that connected back to the conveyor.
- I did this so that the test results would be more clear
  - Queues do not delay items from exiting and as a result the items were staying in the queues for zero time
Created a copy of DP8 to send items to the 3rd and 4th queues on the line

I hope the changes in the model answer your questions and clear things up for you,

Brandon

4 ·

decision-point-logic-and-cascaded-portobject-comma.fsm (71.9 KiB)

Answer 2 · 2016-07-19T09:51:11Z

Joerg Vogel answered Jul 19 2016 at 9:51 AM

the cascading of outobject commands is not a problem. It is a problem to place the cascading referrence in the conveyorsenditem command. The destination has to be the next object and not the following of the next object.

question