How to write coding for that?

Hi Please check the attached file.
How can i write coding for changing type value of To NN133 and NN134 (type).
example if To NN133> type = 2, i want to assign NN134> type = 1.
if To NN133>type = 2, i want to assign NN134> type =2.

Please guide me how to do that.
Thanks.

Can you tell us why you want to change that and what you think that it does?
I'm just asking because until now I have never touched it

Originally Posted by Steven Hamoen

Can you tell us why you want to change that and what you think that it does?
I'm just asking because until now I have never touched it

I want to make alternate route (two lane) to dispatch containers to same yard block with truck. NN41 to NN133 is one lane and another is NN42 to NN134 to dispatch. both will dispatch at same block.
Thanks.

Think you are looking for something like:

setnodenum(node(">NN41/connections/connectionsout/To NN133/type",model()),1);

Maybe this is the right direction!?

As far as I can tell the type is used to determine if the edge is passing or non passing. Usually it is not a good idea to mess with the tree that flexsim generates. For instance are you sure that if you change it, it will work without resetting your model?

If you want to change the way objects behave, use the triggers that are supplied in combination with the commands. In this case take a good look at the closenodeedge and opennodeedge commands. Maybe in combination with optimizenetwork.
Or create or change your tasksequences so that they first travel to the correct endnode and then to the end destination.
Or use the callsubtasks tasksequences.

I'm not sure how much access you have to your tasksequence in CT, so you have to try a bit probably.

Originally Posted by Steven Hamoen

As far as I can tell the type is used to determine if the edge is passing or non passing. Usually it is not a good idea to mess with the tree that flexsim generates. For instance are you sure that if you change it, it will work without resetting your model?

If you want to change the way objects behave, use the triggers that are supplied in combination with the commands. In this case take a good look at the closenodeedge and opennodeedge commands. Maybe in combination with optimizenetwork.
Or create or change your tasksequences so that they first travel to the correct endnode and then to the end destination.
Or use the callsubtasks tasksequences.

I'm not sure how much access you have to your tasksequence in CT, so you have to try a bit probably.

Thanks Steven for your guide and reply. As you said, it's not a good idea and i'm already test it. It not working correctly.