Error post processing with nc programs

Error post processing with nc programs

jack-pat
Participant Participant
776 Views
10 Replies
Message 1 of 11

Error post processing with nc programs

jack-pat
Participant
Participant

Hi, 

 

Since fusion has updated to automatically use NC programmes, our fanuc post processor is failing. 

If we switch back to the legacy post processor it works fine, can anyone find where the fault is here? We've started using NC programmes so it's a bit of a nuisance having to switch back just for this machine.  

 

attached is a simple f3d file, the error log and the post processor we're using. 

 

Any help much appreciated. 

 

Thanks,

 

Jack

0 Likes
Accepted solutions (1)
777 Views
10 Replies
Replies (10)
Message 2 of 11

engineguy
Mentor
Mentor

@jack-pat 

 

Hmmm, not 100% sure on this but with a small modification it now seems to work OK in both old and new systems, anyway, give it a careful try, usual caveat applies, use at own risk 🙂🙂🙂

Just for interest, here is the small modification done.

for (var i = 0; i < arguments.length; ++i) {

Change to 0 above to the 1 below at Line 1775 in the PP

for (var i = 1; i < arguments.length; ++i) {

 

Message 3 of 11

jack-pat
Participant
Participant

Hi, thanks for that. But now the post is not outputting g28 U0 at the start, end or tool changes ? 

0 Likes
Message 4 of 11

seth.madore
Community Manager
Community Manager
Accepted solution

This is well above my head, so I ran it buy one of the architects behind NC Programs and an overall post guru. Turns out there was some changes to your post that did not play well with the NC Program post dialog. He made the edits, here's your post back. It should work straight away


Seth Madore
Customer Advocacy Manager - Manufacturing


Message 5 of 11

engineguy
Mentor
Mentor

@seth.madore 

 

Yep, that does it 🙂 🙂 🙂

0 Likes
Message 6 of 11

seth.madore
Community Manager
Community Manager

Really?

O1001
N10 G95 G18
N11 G21
N12 G92 S6000
N13 G28 U0.
N14 G0 Z200.

(FACE1)
N15 T0101
N16 G92
N17 M8
N18 G95
N19 G97 S589 M3
N20 G0 X108. Z5.
N21 G92 S5000
N22 G96 S200 M3
N23 G0 Z0.707
N24 X104.
N25 G1 X101.414 F0.25
N26 X100. Z0.
N27 X-1.6
N28 X-0.186 Z0.707
N29 G0 X108.
N30 Z5.
N31 G97 S589 M3
N32 M9
N33 G28 U0.
N34 Z200.

(PROFILE FINISHING1)
N35 T0707
N36 G92
N37 M8
N38 G95
N39 G97 S364 M3
N40 G0 X120. Z5.
N41 G92 S5000
N42 G96 S137 M3
N43 G0 Z-0.038
N44 X103.934
N45 G1 X100.718 F0.0762
N46 X100. Z-0.397
N47 Z-100.397
N48 X104.
N49 G0 X120.
N50 Z5.
N51 G97 S364 M3

N52 M9
N53 G28 U0.
N54 Z200.

Seth Madore
Customer Advocacy Manager - Manufacturing


0 Likes
Message 7 of 11

jack-pat
Participant
Participant

What made you ask really?

0 Likes
Message 8 of 11

seth.madore
Community Manager
Community Manager

I was puzzled by your statement that it wasn't posting G28 U0, as the code I was seeing did have those at the beginning, tool changes and the end. Are you not seeing those same outputs?


Seth Madore
Customer Advocacy Manager - Manufacturing


0 Likes
Message 9 of 11

jack-pat
Participant
Participant
That was with engineguys modified post - we just did a quick comparison in visual studio code with the original post and his and there were no g28's. Looking at the one you sent now 🙂
0 Likes
Message 10 of 11

seth.madore
Community Manager
Community Manager

Oh that's funny, I wasn't getting email notifications of engineguy's replies, so I thought you were talking to me!

🤣


Seth Madore
Customer Advocacy Manager - Manufacturing


Message 11 of 11

jack-pat
Participant
Participant
Looks like that's us sorted anyway, thanks for the help!
0 Likes