End Park Position

[[Me...]]

Is there any way to have a separate End Park Position for Mini-Plans?

[[Ri...]]

Maybe with PCM?

[[Me...]]

Please sign in to view this quote.

I'll need some help with that one

[[Ri...]]

One of the gurus will have to help with that one.

[[Me...]]

Please sign in to view this quote.

Guru....that's my favorite noun in this forum 🤣

[[SH...]]

CMM position point will not work??

[[To...]]

Please sign in to view this quote.

After the position point, even with programmable stop, then machine will move to end park position.

It would work if you turned end park position off, but I’m guessing that would be undesirable, too.

[[To...]]

Zeiss: please add objects like moves, programmable stops, end park positions that can be placed in features list.

No, I did not check the feasibility of this request 😁😁😁

[[Ro...]]

This guy found a way to put a condition in the end park position???
Im not quite sure how it works but you only need to read the last comment on page 2, it has the answer in it.

viewtopic.php?f=13&t=1534&hilit=end+par ... n&start=10

[[Is...]]

maybe this:

defineFunctionStart("PositionCMM")
	if getRecordHead("palletlocationnumber") == getRecordHead("lastpalletlocationnumber") then
	positionCMM(getPositionCMM().x,getPositionCMM().y,Pos_Z)
	positionCMM(getPositionCMM().x,Pos_Y,Pos_Z)
	endif
defineFunctionEnd("")


selectCase getRunID()

	case "Miniplan1"
	Pos_Y= -450
	Pos_Z= -10
	executeFunctionNamed("PositionCMM")
	case "Miniplan2"
	Pos_Y= -70
	Pos_Z= -10
	executeFunctionNamed("PositionCMM")
	case "Miniplan3"
	Pos_Y= -50
	Pos_Z= -20	
	executeFunctionNamed("PositionCMM")
endSelect

[[Th...]]

Please sign in to view this quote.

You just gotta right-click the end park commands you want your conditions applied to and add it to each one.

The conditional statement getStartSetting("selection") will return the name of the active characteristic selection in the CNC start options. This includes mini-plan names, so if you were to use a comparison to an expected mini-plan name, you might get what you want. Say you have a mini-plan named "OP1 checks". You could apply the condition getStartSetting("selection")=="OP1 checks" to a clearance move in your end park list. If you picked that mini-plan, this would return true, and you would skip that move command (by default). You could get the opposite result by using <> in place of == or by flipping the condition paths in the window.

I've just tested this and confirmed it will work, but since you can only apply your condition to a single move command at a time, you'd have to come up with a series of end park commands in the same end park position set, each one keyed to function based on the output of its own condition. Like an extremely inefficient if-else function block. It'd be messy.

condition.JPG

[[Ro...]]

Yup, That guy, Thomas.

Jajajajaja

bjkfgdjhkfgdjhkfgd.jpg

[[Th...]]

I should have read Israel's code on the last page first. Certainly, if you have PCM available it'll be a whole lot more elegant. If not, I see that getRunID() does what I attempted with getstartSetting("selection") except it's much quicker to type. That would make my non-PCM solution look more like getRunID()==whatever mini-plan name you want to check against.

[[To...]]

Please sign in to view this quote.

I sort my posts with newest ones on top. I had to look down....LOL