CAM "not a valid ACAD200 file"

[pbft]

I use Ares as my CAD package. Some dxf files work just fine with the UCCNC CAM function, but some generate an error - "not a valid ACAD200 file".
There are no splines or nurbs that I can see in the dxf file.
I did find out that all blocks must be exploded before exporting to dxf, but that's not enough. It appears that there is some drawing feature that taints the drawing so that it won't work any more.
I've attached two dxf files (renamed to .txt to allow upload). They are the exact same part. I created the 'bad' one first, and it had some blocks that were inserted and then deleted. The good one was created by simply copying all of the entities from the bad drawing to a new drawing.
What do I need to do to create usable dxf files? I'm reporting this as a bug because as far as I can tell I have a valid dxf file that UCCNC can't process correctly.

[ger21]

I use AutoCAD, and have never been able to get a .dxf file to load into UCCNC CAM. After an hour of trying, I gave up and never tried again.

[pbft]

I've seen other people post similar experiences. There's an old thread that mentions UCCNC's limitation in that it can't deal with splines or 'nurbs', and Autocad apparently exports many simple features as splines.

That's not the case for me. I don't think Ares is exporting features as splines, and it definitely creates usable exports in some cases.

I'd like to use the UCCNC CAM feature. It has some nice capabilities - pocket and spiral, for instance. When I can get a usable dxf, it's a very handy way to do a quick and simple job. However, I will have to give up if I can't reliably create a usable dxf.

If this gets fixed, I have a few ideas that would make it a replacement for my current CAM solution in most cases:

• File edit/save on the CAD screen (Simple, I think. I can probably do this part myself)
• Configurable G-code 'preface' block - turn on mist / coolant etc.
• Append additional layers to generated G-code (current version only does one layer)
• Tool table

Maybe some (or all) of these exist, but there's no point in looking if I can't use my dxf files.

[bhdavis]

I just found a way to successfully import some .dxf files or parts of files into UCCNC.

I started by creating the drawing on the default .dwt template in AutoCAD LT 2014. That would be the acadlt.dwt file. I drew a square, line and circle and then saved the .dxf. Once saved as a .dxf I resaved the file as a .dwg as Autocad is possessive and won't allow you to open a file in another program if it is already open in Autocad.

If I did the same as above on one of my personally created .dwt template files I got the NOT AN AUTOCAD200 FILE error every time. I had to use the AutoCAD LT default acadlt.dwt template for it to work.

Then I used the CAM package in UCCNC to IMPORT DXF FILE. Worked first time.

However next I tried the same thing with text created in the AutoCAD file. This did not work whether the text was exploded or not. It also did not work when I copy/pasted the text into a new acadlt.dwt template. No error message but the object was simply not there. It seems to me that exploding text in AutoCAD only removes the font attributes but does not really explode the text the same way other objects are exploded.

Then I tried a spline. Again, no matter if original or exploded, or copy/pasted into a new drawing, the spline would not import. No error message but the object was simply not there.

So, it would appear I can get a drawing to import but not text or splines.

Just thought I'd report the results.

BH

[bhdavis]

Well, I've managed to import text into the UCCNC CAM window after all.

As mentioned above I used the default acadlt.dwt template in AutoCAD LT 2014. Then I created the text with the SIMPLEX.SHX font.

Then the file was saved as a .dxf, and then resaved as a .dwg.

Then used the IMPORT DXF FILE button in the UCCNC CAM window and the text came right in.

Only issue is that the SIMPLEX.SHX font appears as a single line font when created in AutoCAD, although in reality it probably is not. It then imports into UCCNC clearly as a perimeter line font. So the toolpath would have to be created down the center of the letter instead of following a single center line.

BH

[ger21]

How are you exploding the text? I don't think you can explode text properly in AutCAD LT. In AutoCAD, you need to use the Explode text Express tools, which I didn't think LT supports.
Can you upload the .dxf that you are importing?

All .shx fonts are single line fonts, so I'm guessing the UCCAM may be swapping it for another default font?

[bhdavis]

Here is the file. While I think you are correct about exploding text in LT the text in this file was not exploded.

Like the above poster I renamed the .dxf file to .txt. Just rename it once downloaded.

BH

[ger21]

As I suspected, your text was not exploded, so when imported into UCCAM, I think the font was substituted.
I exploded your text in AutoCAD, and have attached the .dxf When actually exploded, the text imports correctly.

[bhdavis]

Yup......came in as single line text. I knew there was a problem trying to explode text in Acad LT but did not know that the full blown version of Acad could do it.

Thanks,
BH

[ger21]

You need to use the Express Tools addon for AutoCAD to explode text. It's included with full versions.