Gcode by part name V2.2.0.0

[lloydsp]

David,
I fear we're still "not talking the same language".

First, I would really like to know what's causing that.  If it's a bug, it deserves to be fixed.  So I still ask your help in my replicating the problem.

Second, this is not primarily for generating g-code "for only a part".  It is to generate all of the g-code for an entire .cb file, and to separate it out into files by part.

Many folks have  machines (and even I recently acquired one) that can manage g-code either in very small chunks, or for only one tool at a time (my big router doesn't allow tool-changes -- it's an 'extra-cost' option, costing over $2500USD just for the software changes!).

It was designed to address those sorts of problems.

(and yes, I'm going to re-do the control on that monster as soon as time permits!)

Lloyd

[dh42]

Re

I fear we're still "not talking the same language".

Yes sure   .. and I think that I don't understand all ...(tired)

Second, this is not primarily for generating g-code "for only a part".  It is to generate all of the g-code for an entire .cb file, and to separate it out into files by part.

Yes, I understood

Perhaps if you supplied a sample file that misbehaves, along with the PartSavePath.txt file you're using, I could better discern what you're seeing.

Ah ... I've no txt file, maybe it's the pb ? ... what is the goal of this file ?

But it works well if I give a name in each part Oufile property ; in this case, it ask for nothing and it save all the parts with the given names (those in the OutFile properties) in the same location than the .cb file.

++
David

[lloydsp]

David,
There may be two such text files; they both have the same name, but may contain different path strings.

One may reside in the plugins folder.  The other may reside in your .cb files folder.  Each may contain a path like:

"C:\this_project_gcodes\{$cbfile.name}.nc"

If both files exist and contain valid paths, you're given a menu choice of which to use.
You may also put a path in the Machining tab's "Out File" item.  If it exists in addition to one or both of the others, then you'll be given a choice of any of the paths.

If neither file exists NOR the OutFile spec in the Machining Tab, apparently the CBsystem is smart enough to ask!

Lloyd

[lloydsp]

BTW, Eddy!

There's plenty of slack in those two PartSavePath.txt files.  After all, we're only using the first line.

We could have multiple lines... maybe even in an XML-like format to keep it "cb-like", that define other actions the user wishes to accomplish -- like your suggestion of adding the base cb filename to the part name, to differentiate parts from different files.

Such little options wouldn't take much code at all, nor much in the way of structures or variables.

Give some thought to it, if you're so-inclined.  We might "trick this thing out"!

Lloyd

[dh42]

Ok, it's because the txt file was missing in the plugin folder, now it works as you describe

++
David

[Bubba]

Here are the assembly parts and its names I was using and generate the gcode with Lloyd's plugin..

[lloydsp]

All: To be clear, this might be of limited utility -- only some people need such a method.  But the whole thing would still be a VB script if it weren't for EddyCurrent's initial prodding and ongoing help.

His name is in the comments, too!

Lloyd

[EddyCurrent]

Lloyd,

Thanks for the mention 

Michel's requirements aside, why do we need 4 ways to specify where the part files are created ?

1. Blank Machining Outfile
2. specified Machining Outfile
3. master text file
4. local text file

[lloydsp]

Heh!  That was for MY convenience, only, Eddy.

I (personally) wanted that flexibility, because of the way I organize my files.

It certainly was not 'necessary' -- but the code to do it was small, and if someone wishes only one path, they still have that option.

Lloyd

[EddyCurrent]

What about having one text file with multiple lines, each one being a path string that will populate the ListBox ?

[lloydsp]

Hmmmm.... I'll have to think about that. 

I don't know.  As I read it, no obvious objections just 'pop up' in my head, and yet, something in the back of my mind is saying -- "no, you considered that, and discarded it..."

I'll think it all through again.  Sometimes, I wish I'd keep notes on the things I DON'T do, as well as the things I do.

Lloyd

[lloydsp]

Latest touchup, to help system work with the g-code-by-part name plugin.

Lloyd

[lloydsp]

For whomever downloaded that first file I posted a few minutes ago... there was a stale file in the .zip.

I replaced it, and renamed the zip to prevent confusion.

LLoyd

[lloydsp]

Updated to V2.3.0.0 in first post.  Will post source changes when time permits.

LLoyd

[EddyCurrent]

Lloyd,

Just for clarity, can you please list some bullet points of the steps we have to take to get this working. Thanks.