STL from verify

[Cuda84]

Friday I created 2 STL files from verify. I am running thru multiple operations and I am creating STL files every so many ops. so that I don't have to run all operations thru verify at one time. Today when I try to creat an STL file I get a 0MB file.

 

Has anyone else seen this? Am I doing something wrong? Should I have just stayed home today?

 

[Matthew Hajicek - Singularity]

It's because of the long weekend. Your computer got lonely and depressed, and now it's being passive-aggressive to get back at you for leaving it alone.

[Smit]

This has happened to me recently too, on a fairly large file.

 

I tried it in X2 and X2MR1 with the same results, a 0 MB file.

 

I hope somebody has an answer...

[Cuda84]

Yeah Matt it's always contrarry on Mondays, but this 3 day weekend realy P!$$ed it off.

 

Smit this file was only 7.3MB quite small for me. I tried about 4 times this morning. 2 of them times it locked up MC, had to kill it. I was just trying to check the pick programs (leftover), but still it should have worked.

 

[Colin Gilchrist]

Cuda, You've got mail.

[Cuda84]

Colin you have mail.

[Smit]

quote:

---

Cuda, You've got mail.

---

quote:

---

Colin you have mail.

---

Did you find a solution you're not sharing?

[Cuda84]

No solution yet, just sharing files so Colin can have a look at my problem. I am at home now so I can't check my mail until tomorrow. I will make sure if I find out what the problem is thru E-mail I will post on the forum also.

 

[Cuda84]

I got this in E-mail from another forum member.

 

-------------------------------------------------

Dave,

 

 

 

I was reading you comments on the problems that you having with verify. I had the some problems with verify on the 15th of May. I was verifying a large fixture and when I got to finish toolpath the software would lock-up, crash or after a long time it would save the .STL file but with nothing in it just a 0 mb. I e-mailed M/C about the problem and after a couple of day going back and forth they logged it in as a bug with the MR1. I was told that the waterfall bug they fixed caused this one. So I had to go back to X2 SP1 because all we cut here are large parts and dies so I can use verify. I hope this can help.

-------------------------------------------------

 

 

Looks like a bug.

 

Thank you

[Colin Gilchrist]

Possibly,

 

I got it to work on your part Dave. I think one of your STL files wasn't positioned correctly. See my email.

[Cuda84]

If I can see it verify the part, and it looks good, shouldn't I be able to make an STL file?

 

[Colin Gilchrist]

Yes you should... Sounds like a bug to me too...

[Cuda84]

Hello all.

 

Colin sugested that I change the STL output format from Binary to ASCII. This seemed to fix the problem, at least on the files that I was working on.

 

I had another problem pop up after makeing this change.

 

Now for some reason I can’t finish a verify at the highest quality settings, I’ve got to drop back one setting. The verify runs to about 84% then jumps to 100%. When it finally displays the model the cut is not finished. So I am running the verify with the quality set down 1 notch. For what I am doing it will be OK, I am not comparing STL to model at the end, I am just checking the toolpaths.

 

[Bruce Gibson]

What type of toolpaths are you verifying around the 84% mark? I have noticed some 2d swept toolpaths can cause this.

[Cuda84]

I was verifing a high speed Scallop.

[sharles]

Dave,

 

you may be having a problem that mc logged as a bug for me. On my really big files the verify memory gets overloaded before it is finished verifying the part. The percentage indicator jumps like you said to 100% but the part is NOT done. Not sure why it would happen on you for a little part, but mc did say it's a bug.

[Don LePore from CNC Software]

Guys, I've been looking into this problem and could use a few of your files. Please send me the file with the toolpaths selected and the Verify settings you are using with it. This includes which engine you are using (Turbo or tool and/or holder simulation), the Speed/Quality setting and a snapshot of your Verify Options settings.

[Don LePore from CNC Software]

Guys, I've been looking into this problem and could use a few of your files. Please send me the file with the toolpaths selected and the Verify settings you are using with it. This includes which engine you are using (Turbo or tool and/or holder simulation), the Speed/Quality setting and a snapshot of your Verify Options settings.

[Cuda84]

Don exactly what problem are you looking into.

The inability to creat the STL file, (0MB file)

Or the jump to 100% without finishing the verify?

[Don LePore from CNC Software]

Sorry, my bad. Right now I'm looking at the problem with the STL file creation.

[Cuda84]

I just recieved this from Don LePore @ CNC software.

 

-------------------------------------------------

Dave, the problem has been found. Unfortunately it is in the API we use for Verify. It has been documented and sent to the vendor. I will ask for a priority fix for it and will let you know when it gets fixed. I’m really hoping for vX2 MR2.

 

 

 

Don

 

-------------------------------------------------

[Don LePore from CNC Software]

Please note that the problem has been identified for the part Dave provided. There is no guarantee that the solution will fix all the problems. If you can identify more parts that exhibit the same problem, please forward them to me so that I can get them to the vendor. The more parts they have to test against, the more robust the solution will be.

[Cuda84]

Don I have a large part I was doing yesterday that did the same thing 0MB file. I will send it along sometime today.

 

[RObert TImby]

Don,

 

Can you please check your e-mail. I sent you an e-mail about the problem that I'm having with the slt files the same as Cuda84

 

Thanks

[Don LePore from CNC Software]

This is a good example of why it's so important to properly report bugs to CNC. Robert's file, while exhibiting the same symptoms as Dave's, was a different problem. It has been fixed in vX2 MR2.