trying to get my pro running after a 3+ year hiatus
got my design in sheet cam, but when I click run post processor, nothing happens, even though I have the check boxes next to my operations.
any idea what dumb obvious thing I’m forgetting?
I re downloaded and installed postprocessor 1.6
Thanks,
E-
The simplest way to get advice on Sheetcam setup is to post the .job file. Then we can review setings, etc.
I tried to upload it and it was not allowed, so I posted it on my google drive
I corrected all the error on screen, even ones about lead in on small holes.
Ignore the word laser in the name, that was the file name when I first traced it.
Thanks,
E-
From what I can see you don’t have a layer selected.
Once I selected the layer it worked just fine. Are getting an error prior to running the post processor?
the operations show the layer for each
if its not there, where do I need to select the layer? I appreciate thehelp.
I click the post processor button and nothing happens, no errors i see, no popups.
Thanks
I don’t know, it works for me. It looks like you have a layer selected and even if you didn’t the post processor seems to still work. It may mot produce a usable gcode but it still ran!
Maybe reload Sheetcam?
Maybe some of the more experienced guys have a better answer.
just to be sure i’m right, when i click run post processor, it’s supposed to popup a file dialog, so i can tellit what file to save i to… correct?
I checked for updates have the latest sheetcamtng, and tried changing the job file for a simpler one and changing to a different post processor and back.
Thanks,
E-
@sircaladin , I looked at the job file and as @Just-For-Fun mentions, there was no layer selected in the Operation; but then you posted that you seem to have corrected that mistake and still no post processor is running. At this point, it will be easiest to diagnose if you send sales@sheetcam.com a customer support.zip file. Instructions are here-
@sircaladin Did you get your post processor figured out?
I followed the reset proceedure from sheetcam support, and it was still failing. On a whim I ran it as admin and now I’m getting post processor output, but when I run it in fire control, it throws the old no speed setting error…
Completely lost on how to fix that as its the post processor that’s supposed to be what inserts that I’ve tried the stock version of the post processor , and what ever I edified to make it work 3 years ago and forgot… neither work.
when i edit the tap file in notepad++ this is all it has in it
(v1.6-sc)
G90 G94
G17
G20 (Units: Inches)
H0
M5 M30
(PS0)
That’s the whole tap file
I admit the dxf is just 2 circles one inside and out outside (basically abig washer)
but still that seems short.
I load an older tap file, that i used before and then let firecontorl convert, and it’s got the exact same lines in it.
Bummer, I don’t have enough experience to help much.
It sounds like you might not have the operation checked. I just duplicated you gcode by unchecking the operation.
The other thing that produces that same gcode is running the Post Processor before you run a plasma cut operation.
I believe having to run as admin is a strong clue that your Windows userid has inadequate authorization to data folders that sheetcam is trying to use during post processor runtime.
I cannot reproduce your latest minimal gcode problem using the job file and pp from the latest support.zip that you sent me. That minimal gcode that you’re getting is coming from OnInit() and OnFinish() only. My results seem complete and good gcode, certainly including the toolpaths of the two shapes in the job.
I have always installed sheetcam with a Windows admin class userid, but I have run sheetcam with non-admin ids as I recall.
Before giving further instructions, I’ll escalate this to have @LesNewell take a look.
That is just the commands that the post processor puts into every file. There are no motion or torch firing commands in there.
This typically happens when you fail to create a jet cutting operation before post processing.
I know you have shown that you did that, so I have no explanation why this is happening. We’ll have to see what Les has to say about it.
I just received an email from OP that Les did fix the problem by sending him a replacement license file after seeing that the license file included in his support.zip package was corrupted.
There were multiple and progressive symptoms in this case, several corrections were applied in that progression. Also note that the final symptom has a couple of causes as pointed out by a couple of users, perhaps the least of which is a corrupted license file, but it can happen obviously. Many thanks to all that lent a hand.
Thanks again for all the help!
