'Relocate' MOP - move tool between MOPs avoiding clamps

[jk]

Quick and dirty plugin to guide tool between mops avoiding clamps.

Basically it is a take on a http://www.cambam.co.uk/forum/index.php?topic=4645.0 plugin by EddyCurrent.
This time as a new kind of MOP.

Usage:
Insert Relocate MOP between the MOPs in question.
Specify primitive ids with nodes to follow while relocating. Pointlists, open polylines and lines are supported.
Specify clearance.
If G1 feed instead of G0 is required, put feed value into the 'Move feedrate' field (0 default to rapid)

In generated g-code tool should rise to the clearance, visit nodes in sequence and come
to the initial cut point of the next mop.

As a bonus, initial cut points of the all MOPs are highlighted with the little orange circles.

Simulation is strongly recommended to make sure all is ok.

Quirks:
Nesting may give strange results
If Relocate is a first mop in g-code, first rapid may be wrong
If there is a custom mop footers/headers used (with movements), result may be wrong
First segment of relocation path is not displayed until the g-code generated (until the start point is known)
Spindle control/toolchange may be emitted, since MOP inherits MOPs common properties

Source code at https://github.com/jkmnt/relocator

---
v1.1.1
* fix for a wrong default feed property (broke load/save on CB 9.8)

v1.1.0
* mop is true 'geometry mop' now, should be more robust
* G1 feed instead of G0 rapid may be specified now

v1.0.0
* initial release

[lloydsp]

JK,
THANKS!  I can put that plugin to work in the morning!

LLoyd

[dh42]

Hello,

Thanks ! another interesting plugin ... but too late to test now (bed time)

++
David

[lloydsp]

David, it's as sweet as honey!  I've needed this for a while!

Lloyd

[dh42]

http://www.cambam.co.uk/forum/index.php?topic=6237.0

 

[EddyCurrent]

Quick and dirty plugin to guide tool between mops avoiding clamps.

Basically it is a take on a http://www.cambam.co.uk/forum/index.php?topic=4645.0 plugin by EddyCurrent.
This time as a new kind of MOP.

Yes, I've found my script very handy on a lot of jobs but for some reason people found the required .txt file too difficult to manage.

Tested the version for CamBam_1 with Linux and it works okay.

[lloydsp]

JK,
If I might:  This isn't a criticism, but a 'wish'.  If you could equip the MOp to use either G0 or G1-and-a-feed rate, it would be beneficial in some situations (and especially if one wanted to test a circuitous path with one hand hovering over the kill button!<grin>).

LLoyd

[jk]

Yes, I've found my script very handy on a lot of jobs but for some reason people found the required .txt file too difficult to manage.

Tested the version for CamBam_1 with Linux and it works okay.

I've used it too on some jobs, pretty useful - especially there the clamp it too high and my machine can't clear it at all.

http://www.cambam.co.uk/forum/index.php?topic=6237.0

 

No unexpected new plugins are planned up to date )

If I might:  This isn't a criticism, but a 'wish'.  If you could equip the MOp to use either G0 or G1-and-a-feed rate, it would be beneficial in some situations (and especially if one wanted to test a circuitous path with one hand hovering over the kill button!<grin>).

It may be possible and useful. Say, I'll add a single feedrate field, defaulting to 0. Zero means use G0 rapid, non-zero - use G1 with the specified feedrate.

[dh42]

Hello

A little feedback.

- the first toolpath from the end point of MOP1 to the first point of the pointlist/polyline is missing for me (both vertical and horizontal (see picture)  tried with the 3 graphic mode (XP pro)  it's ok in the Gcode.

- the "select drawing objects" context menu of the relocate mop is not working (but it works with the |...| button)

- the undo is not working correctly when I changes the ID used for the mop if the change is done with the |...| button, but works if I directly write the ID in the field.

++
David

[Garyhlucas]

JK,
Nice to see this MOP.  I recall suggesting this after about my first week of using CamBam about 4 years ago after crashing a tool.  Wow time flies, it is hard to believe it has been that long. I've been at this job 3-1/2 years and built my CNC before I came here.

[jk]

First post updated with v1.1.0

* mop is true 'geometry mop' now, should be more robust
so primitives manipulation (copy, paste format, undo etc) will work.
A true 'geometry mop' should specify spindle control and tool.
Leaving them default shouldn't break anything, since next mop will change them again if required.
It may be even useful in some cases.


* G1 feed instead of G0 rapid may be specified now

- the first toolpath from the end point of MOP1 to the first point of the pointlist/polyline is missing for me (both vertical and horizontal (see picture)  tried with the 3 graphic mode (XP pro)  it's ok in the Gcode.

It's a one of the quirks :-) I don't know the start point until the g-code generation. After the g-file is generated,
first segment should be visible.

JK,
Nice to see this MOP.  I recall suggesting this after about my first week of using CamBam about 4 years ago after crashing a tool.

In perfect world clearance plane always means 'safe z', so this plugin would be never needed )

[Garyhlucas]

JK,
Nice to see this MOP.  I recall suggesting this after about my first week of using CamBam about 4 years ago after crashing a tool.

In perfect world clearance plane always means 'safe z', so this plugin would be never needed )

No even in a perfect world it is needed safe Z is specified per MOP. I don't one operation that is at lower elevation going up to a safe Z and wasting time. I do however want it to go to a higher safe Z clear everything before going to an operation on a higher plane. Your MOP provides that.

[dh42]

Hello,

It's a one of the quirks :-) I don't know the start point until the g-code generation. After the g-file is generated,
first segment should be visible.

Right ! ... it works after Gcode is done .. sorry, I misread your explanations  

Good job

++
David

[dh42]

re

Works on 1.0, but on the 0.98, the plugin return a loading error (and I'm sure I install the right version )

on 1.0, the first vertical line is missing even after the Gcode is done (it worked on previous version)

on 0.98 the plugin is usable but fail to save/load any files even if they do not contain a relocate mop

++
David

[jk]

Works on 1.0, but on the 0.98, the plugin return a loading error (and I'm sure I install the right version )

on 1.0, the first vertical line is missing even after the Gcode is done (it worked on previous version)

on 0.98 the plugin is usable but fail to save/load any files even if they do not contain a relocate mop

Thank you for test. Loading error is fixed, but I can't reproduce the vertical line error.
May you supply a test file ?