Force Verify?

[DanaEd]

Hi guys,

Is there any way to force a user to run verify before a program is posted?

[JOHNAKA]

Sure,

 

all you have to say is verify or you're fired

 

lol

[jagg2499]

Now that is pretty darn funny right there !!!

[Rob @ Target Machine]

That is effin' funny but....

 

It is conceivable that your reseller can do something like this in your post.

 

For instance, you could force the user to save the stl from verify with the same name as the nci file into the nci folder.

 

code:

---

pcheck_for_stl

s_stl : "" # Path/Name of the stl from verify

 

s_stl = spathnci$ + snamenci$ + ".stl"

 

result = fexist(s_stl)

 

if result = 1,

[

#do nothing - stl exists

]

else,

exitpost$ #bail out - stl does not exist

---

Not working code here, but a just an example that shows that it wouldn't be impossible to do.

[DavidB]

Running verify is no guaranty you have good code anyway, as verify only runs the NCI file.

 

Rob that would be good for the first time but what if changes are made. The STL would be there from the first posting so the checking would allow posting.

 

Good idea though.

 

Cheers Dave

[Rob @ Target Machine]

Yup, you're right.

There would be many ways around it, and if you haven't figured out how to beat it, it would be a bad idea if you're having trouble with verify crashing.

 

You'd be screwed.

[kunfuzed]

quote:

---

all you have to say is verify or you're fired

---

I would add to that "If you have a crash, and we go back, look, and see it in Verify, then your fired!

[DanaEd]

Thanks guys...

[MotorCityMinion]

1/2 the guys where I work can't even set up the stock right to see Verify, the other 1/3 don't know what they are looking at when its running.

Backplot with the vapor trail seems to be the fav here. Grrrr.

[Rob @ Target Machine]

I use both.

 

Backplot with quick verify turned on to check against the wire or solid to check for missed corner radii.

 

Then verify with change tool color to see the blend areas, and of course, to verify and compare against the solid.

 

Why someone wouldn't use the tools in front of them is beyond me.

[Programinator]

Verify saved me so many times and most times it only takes seconds. The problem many people have is that they dont set it up right with stock setup and using wcs instead of tons of levels. When you can select all toolpaths and verify and see a complete part instead of only one operation at a time thats soooo nice. its amazing how many people still use wireframe 2d geometry that they draw themselves and they dont bother with the wcs or stock setup. all their tools are not defined right for backplot and verify. They just post and crash and then try to figure it out. So insane

[Cannon]

quote:

---

Verify saved me so many times and most times it only takes seconds. The problem many people have is that they dont set it up right with stock setup and using wcs instead of tons of levels. When you can select all toolpaths and verify and see a complete part instead of only one operation at a time thats soooo nice. its amazing how many people still use wireframe 2d geometry that they draw themselves and they dont bother with the wcs or stock setup. all their tools are not defined right for backplot and verify. They just post and crash and then try to figure it out. So insane

---

Insane is that we still cant turbo verify when using WCS.

[Programinator]

quote:

---

Insane is that we still cant turbo verify when using WCS.

---

I KNOW RIGHT

[Mark H]

quote:

---

Insane is that we still cant turbo verify when using WCS.

---

+1

[88Matt]

Verify and backplot are fine for 2&3 axis work. I use them all day long. If you are running 4/5 axis work you should be using Machine Sim, vericut, or comp software. As stated above, verify and backplot run off the NCI and not the NC. Also, they don't check for anything but the tool and toolholder. You need to check the spindle as well.

Also, if you are running live tooling on a lathe I would us it as well. Running machine sim saved us from jamming a drill through the back of the lathe which would not have shown up with either verify or backplot.

[Programinator]

quote:

---

Verify and backplot are fine for 2&3 axis work. I use them all day long. If you are running 4/5 axis work you should be using Machine Sim, vericut, or comp software. As stated above, verify and backplot run off the NCI and not the NC. Also, they don't check for anything but the tool and toolholder. You need to check the spindle as well.

Also, if you are running live tooling on a lathe I would us it as well. Running machine sim saved us from jamming a drill through the back of the lathe which would not have shown up with either verify or backplot.

---

+1

[Chipmakr]

quote:

---

Insane is that we still cant turbo verify when using WCS.

---

+1000

[Matthew Hajicek - Singularity]

quote:

---

If you are running 4/5 axis work you should be using Machine Sim, vericut, or comp software.

---

True dat. Sad when management says "there's no time for that and no money for software, we need to get the machine running now!" Then when there's a small gouge they say "How could this happen?! this is a $1500 part!"

[Steve Hattori]

Matt, that could be a $35,000 spindle and $10k of labor to straighten all 5 axes out again...

 

And +10000 on turbo verify. It takes so long to run on most of my parts, I leave run overnite, and then it crashes so I have to separate it into little pieces and start over 10 times. Bah!