error message "Clock overflow, running stopped"

When I create 50 flowitems at once, the following message appears. "clock overflow, running stopped"!

I tried to split the flowitems in batches of 25 with 0.01 second delay, but the same message appears. 2 batches of 10 items is no problem, but 2 batches of 11 items is a problem.

Can anybody explain this message and give a solution? I guess the problem is that to much events are fired on the same time. After creating the TaskExecuterFlowItems a message is send to the TEFI.

I would think it determines a zero velocity for the task executer flowitems. How do you create the flowitems?

Martijn

My TEFIs walk 'autonomous', they are dropped in the model, and by recieving a message they'll travel away. In the source I use the InterArrivalTime option and I use the on creation trigger to position my items in the model.

Every thing was ok, as long as my IAT was 0.15 and bigger. But when I try to fill my model very fast with for example 50 items with the arrival schedule (50 at once) or with an IAT of 0.01 the message appears

Martin,

Normally when a task executer flowitem is used its position is set in the "Request Transport From" trigger. Where you are setting it in the "On Creation" trigger, this could be the root of your problem. If you post a sample of your model we could help more?

Good Luck,
Brandon

I used the principle "steal if it is done before". so I copied from, I guess, "Request Transport From" trigger en pasted it in the on creation trigger. On the end of my custom code I set the position. after that only a delayed message is send to the Item self. Everything is okay, until I create the items in a very short time.

after the message trigger is fired of the items a user command is called. this command hold a number of if statements. it seems this is to heavy for the program because a simple model with a source, queue,processor and a sink don't have a problem with an IAT of 0.01

I don't think your model being to heavy for Flexsim is the problem. Something is going wrong and it's hard to analyze without seeing it happen, so as Brandon metioned a sample model would help. Only that's maybe something you don't want.

I got this kind of problem before. If you have a 0 speed TE or TEFlowItem, when it is traveled, Flexsim will do the calculation using the 0 speed. Since the distance is divided by 0, you get an infinite event time, which is the meaning of "clock overflow" in the message.

Here's a very simple model in which a task executer is used. The maximum speed of the TE is set to zero -> Clock overflow.

You can get that error if you have an infinite loop or when there is a division by zero.

Thanks all for your reply. Now I know where I have to search to solve this problem. I'll tell you my solution.

hi all,

during the building of my model I used the command sendmessage in the OnCreation trigger to activate a usercommand to activate my TEFI. Yesterday a changed this to the senddelayedmessage command and changed some other things.

Now I just changed back my sendmessage command and there is no clock overflow any more. maybe the fault is still there, but the model runs as I expect.

thanks all for your help

Martin

Always open your System Console and run your model before you sign-off that all is ok. You might find some exceptions being thrown... Exceptions are usually printed out on a line that starts with ex: By the way, if you turn on the Trace Debugger, it will sometimes print a little extra information about the exceptions shown in the System Console (not sure why this is so)