CONV_INFO_ESTIMATE_CONVEY_TIME not depending on distAfterSource ?

Question

question

David Besson asked Oct 10, '16 David Besson commented Oct 12, '16

CONV_INFO_ESTIMATE_CONVEY_TIME not depending on distAfterSource ?

Hello,

When I use the command "conveyorinfo" with "CONV_INFO_ESTIMATE_CONVEY_TIME", it seems that the parameter "distAfterSource" has not any influence. It should not be the case, right? Or I do not understand this parameter...

For example:

treenode DP1 = node("DP1", model());
treenode DP2= node("DP2", model());
double distAfterSource = 4.5;
return conveyorinfo(DP1, CONV_INFO_ESTIMATE_CONVEY_TIME, distAfterSource, DP2);

20161010-q-conveyorinfo-estimate-convey-time.fsm

Thanks for your help!

David

Software Version:

FlexSim 16.2.0

conveyor

capture.png (16.7 KiB)

20161010-q-conveyorinfo-estimate-convey-time.fsm (16.1 KiB)

5 |100000

Attachments: Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Answer 1 · 2016-10-11T17:32:53Z

Phil BoBo answered Oct 11, '16 David Besson commented Oct 12, '16

This is a bug. The function is not properly taking those offset parameters (distAfterSource and distAfterDest) into account in its calculations.

I'll add a note to the development list.

· 1

5 |100000

Attachments: Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

David Besson commented · Oct 12, 2016 at 05:35 AM

Ok, thanks!

0 ·

Answer 2 · 2016-10-10T16:57:03Z

Jeff Nordgren answered Oct 10, '16 Phil BoBo converted comment to answer Oct 11, '16

@David Besson

David,

First off, the first parameter in the conveyorinfo() command should be a reference to the conveyor, not a DP as in your model.

Attached is your model with the reference changed to the conveyor. Is this what you were looking for?

q-conveyorinfo-estimate-convey-time-jn1.fsm

q-conveyorinfo-estimate-convey-time-jn1.fsm (15.4 KiB)

· 1

5 |100000

Attachments: Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

David Besson commented · Oct 11, 2016 at 05:52 AM

@Jeff Nordgren

Thanks for your answer.

According to the documentation, the first parameter could be also an object that represents some point on a conveyor:

CONV_INFO_ESTIMATE_CONVEY_TIME(num distAfterSource, obj dest, num distAfterDest, num itemLength, num flags)( Estimates the time it will take to convey from one point in the conveyor system to another, including transfer times and assuming no blockage. This may be used in optimizing merge control logic for better slug release timing. In this query, the conveyor and dest parameters may be either a reference to a conveyor object, or an object that represents some point on a conveyor, such as a photo eye, decision point, entry transfer or exit transfer. distAfterSource and distAfterDest are offset distances from the associated point. itemLength should be the assumed item length. The flags parameter can either be 0, or CONV_ESTIMATE_STANDARD_SPEEDS. If 0 (default), the estimation algorithm will assume slug-build conveyors will convey at their slug release speed. If CONV_ESTIMATE_STANDARD_SPEEDS is defined, the estimation algorithm will use normal conveying speeds.

Anyway, even with the first parameter referencing a conveyor, the parameter "distAfterSource" has not any influence also...

0 ·

question