[KSky]

Version 27.

If I have a long path, ANY post processor apart from ones like Generic Router will crash. I can save the same GCODE file to a shorter folder name and it works. Anybody else see this? Is this a known issue?

If I take out the line with the

"(FILE: ",prog_name,")"

Then the post processor works just fine.

[magicniner]

I don't have 27 but it sounds like you're running up against file path name length issues.
If you create a desktop folder or one in the root of My Documents does the problem still occur?
What happens when you then copy the file using Windows to the folder where you'd like it to reside?

- Nick

[KSky]

All those things work if the path is shorter and windows has no issue with copying the file. I have an especially long customer name and project and that makes for a long path name.

So this fails

/users/MachineShop/desktop/dropbox/customers/OregonIndustralLaser/AR15Jigs/GCode/LowerReceiverDriversSideJig.tap

But

/users/MachineShop/desktop/dropbox/LowerReceiverDriversSideJig.tap

works as well as just copying the file.

I use Dropbox to sync my GCode out to the shop computers.

[MikeC8]

move the dropbox folder to the root c directory? That would shorten your path location quite a bit.You could then place a shortcut on your desktop if you want, to that folder location.

[KSky]

I made a shortcut to that project to in in my "libraries", I think that's the best as the path is short and it's right there. When I am done with this job I can just delete it out of my library.

[SBC Cycle]

I created a file with a path and filename like this and it posted without issue in my standard post processor.

C:\XXX\XXX\29089\buried\burid\buried\buried\buried \buried\buried\buried\buried\buried\buried\buried\ buried\buried\buried\deeper\2908929089290892908929 08929089.bbcd

I think there is something else that my be going on. Are you posting to a network location or anything else out of the ordinary?

[The Engine Guy]

Didn`t we have an issue with long file names a few years ago, think it was the old clunky V22, if memory serves it was Burrman who solved it last time

Hope it`s not something that`s rearing it`s ugly head again

Regards
Rob
:rainfro: :rainfro: :rainfro:

[jrmach]

All those things work if the path is shorter and windows has no issue with copying the file. I have an especially long customer name and project and that makes for a long path name.

So this fails

/users/MachineShop/desktop/dropbox/customers/OregonIndustralLaser/AR15Jigs/GCode/LowerReceiverDriversSideJig.tap

But

/users/MachineShop/desktop/dropbox/LowerReceiverDriversSideJig.tap

works as well as just copying the file.

I use Dropbox to sync my GCode out to the shop computers.

FWIW,you spelled "Industrial" wrong.Not trying to be smart,,just an observation.
Probably nothing there.

[KSky]

I created a file with a path and filename like this and it posted without issue in my standard post processor.

C:\XXX\XXX\29089\buried\burid\buried\buried\buried \buried\buried\buried\buried\buried\buried\buried\ buried\buried\buried\deeper\2908929089290892908929 08929089.bbcd

I think there is something else that my be going on. Are you posting to a network location or anything else out of the ordinary?

Hmm, what post processor are you using? There are a few that don't print the filename in the output that work for me.

[BurrMan]

Mine says this:

"(PROGRAM NAME - ",prog_name,")"

And it only outputs the filename in the code. Not the entire path.

What post are you using that has THAT.....

[KSky]

Mine says this:

"(PROGRAM NAME - ",prog_name,")"

And it only outputs the filename in the code. Not the entire path.

What post are you using that has THAT.....

The "Tormach_PCNC_1100_Rev1.MillPst, but I get the same message using the Fanuc0M.MillPst right out of the box. And your right, it's just the file name.

[jrmach]

The "Tormach_PCNC_1100_Rev1.MillPst, but I get the same message using the Fanuc0M.MillPst right out of the box. And your right, it's just the file name.

Not having the correct machine selected will throw that code.
Make sure your machine is selected under current settings

[BurrMan]

Not having the correct machine selected will throw that code.
Make sure your machine is selected under current settings

Or more specifically the "nc filepath" under the machines settings needs looked at...