NC files does not work with PythonX

NC files does not work with PythonX

masky007
Participant Participant
2,079 Views
13 Replies
Message 1 of 14

NC files does not work with PythonX

masky007
Participant
Participant

Hello,

My client is having many issues with the NC  files,  created with AS ver 18 ( as this job was detailed in 2018) they use the  PythonX system.

I have attached my NC settings, does anyone have any specific recommended settings for Python X.

 

.

Regards,

 

 

Angelo

 

 

 

 

 

 

 

 

0 Likes
2,080 Views
13 Replies
Replies (13)
Message 2 of 14

Sebastian_Eiche
Mentor
Mentor

maybe we could help if you wrote which problems they have...the NC files are created according to the DSTV Standard and are not adjustable for any problems. 
But we need more information "what is the problem"


Sebastian Eiche
Application Engineer @Mensch und Maschine acadGraph

EESignature

If this information was helpful, please use the Accept as Solution function, this make it easier for other users

0 Likes
Message 3 of 14

masky007
Participant
Participant

Thanks Sebastian for your quick response, much appreciated.

This is the info. I got from the fabricator. Please see attachments there seem to be a number of issues .

Also attached  are the some  of the  pdfs for members . 

Please see the part m8 attached,  I have use steel solutions to view the nc file , only the web seems to be cut off  not the flange.

 

 

0 Likes
Message 4 of 14

Sebastian_Eiche
Mentor
Mentor

I will have a look on Friday, but it seems to be, that it would helpful to have the model.dwg to compare the files and the pdf


Sebastian Eiche
Application Engineer @Mensch und Maschine acadGraph

EESignature

If this information was helpful, please use the Accept as Solution function, this make it easier for other users

0 Likes
Message 5 of 14

Masibanda-CE
Collaborator
Collaborator

Can you send the NC file for m8?

0 Likes
Message 6 of 14

masky007
Participant
Participant

,

 

Please see attachments.

 

 

0 Likes
Message 7 of 14

Masibanda-CE
Collaborator
Collaborator

Like Sebastian, the NC files are usually correct and the problem lies in the machine's interpreting it. Below is a screenshot that should explain things. Your NC file itself does seem a bit "extra" because all that is necessary are the SI paragraph and the middle AK paragraph. Sebastian can probably translate what AK is in Deutsch but in English, it defines the External Countour and yours does just that.

The numbers in the circle define the overall length and Height of the object (front face). The AK paragraph then defines the External Contour of the finished shape. It starts at the bottom left corner, defines each point from there, and then returns where it started. All in X Y coordinates. Pretty simple to define.2019-05-30_16-03-28.jpg

 

0 Likes
Message 8 of 14

masky007
Participant
Participant

Thanks Gary appreciate your response to this, 

I get it , so the output file  should be fined tuned to suit the Python X system 

 

0 Likes
Message 9 of 14

Masibanda-CE
Collaborator
Collaborator

Angelo,

Not sure what you mean but, there's nothing wrong with your NC file. The extra entries I mentioned define your top flange and the back of the web, all correctly, they're just not necessary. You might check your Management Tools and see if "Force beam contours in NC" is checked, and remove it. This MIGHT be causing the fabricator's problem, but it shouldn't, because there is nothing incorrect in your output.

Cheers,

Gary

0 Likes
Message 10 of 14

masky007
Participant
Participant

Thanks Gary and Sebastian for your input for this query 

 any one would need  the NC settings for Python X its all there its tested and  it works.

 

 

 

0 Likes
Message 11 of 14

billingtondetailing
Enthusiast
Enthusiast

Are you saying here in your last post that these are the changes that you made to the NC settings so that they worked? Or were you saying, "Here's the settings I have, help me make them work?"

0 Likes
Message 12 of 14

masky007
Participant
Participant

 I meant , These are settings  in the attachment that worked

0 Likes
Message 13 of 14

jlamacchio6VF6E
Explorer
Explorer

Try saving your file as Nc1

0 Likes
Message 14 of 14

95r380disco1
Advocate
Advocate

As a PythonX operator, Looking at your list of problems, the majority of these issues is based on rounding errors in the NC files with the cuts running down the length of the part. There is usually one number in the y dimension that is off by .01mm.

Doesn't matter what the drafting program is used, it happens with all of them. Our  Python X at work has been a learning curve. There is a lot of things that you can do that they say you can't. We have blown ther minds with some of the stuff we are doing with it.

98% of the file issues is operator error.

PythonX support can help with machine settings to resolve these issues.

I noticed one part looks like a WT. The Python will not cut a Tee from a WT file. There is a work around for that though.

The machine will process flat bar. We do it at least once a week.

The numbering issue is a problem with Advance Steel on the placement. I change the location of the part numbers on a daily basis. Sometimes as many a few hundred a day, depends on how many beams are processed. I have a text file with proven x,y positions saved for different material sizes.