PDA

View Full Version : Texturing file unexpected stop



kenakabrowncom
05-09-2014, 09:54 AM
Here is one for you gurus!

I have had my "buddy" for several years now... everything on this bot runs along just great.

For the first time yesterday I tried creating and running a texture operation. This is only a test to get familiar with the function. I created a file and started it using a 1/8" ball nose bit. After running for a while the machine suddenly stopped for no apparent reason. No errors at the PC... the elapsed time clock kept running too. The spindle just stopped and the spindle went up directly at the point it stopped as if the job was done. I totally shut down the bot and rebooted the PC. I re-ran the file and the SAME thing happened at the same spot in the file. I looked at the file to see if there was something weird and saw nothing.

I recreated the file, made some tweaks to the texturing and started over. Again, it stopped. This time at line 365. I started it over and same thing... stopped at 365.

I'm stumped.

I have attached file for this job... any help would be VERY much appreciated.

steve_g
05-09-2014, 12:30 PM
Ken...
It appears to run normally in the SB preview mode... but then I don’t know what it’s supposed to look like!
Does it look right to you in the SB preview Mode?
SG

srwtlc
05-09-2014, 12:37 PM
Ken, what version of SB3 are you running. Some of the earlier versions of 3.8.XX had issues that exhibited this. There are some concurrent J3's at that line and I would often see this with v-carve files too. Are you running any modified ramp settings. Also, try running the file with a speed setting something like 3.3,1.3 and see what happens. You could also change all J3's into M3's and try it.

Check your version first.

srwtlc
05-09-2014, 03:45 PM
Ran your file too and it finished fine on mine. This is the exact kind of file that would cause the issue in earlier 3.8 versions, lots of J3's one after another. I'm not so sure that it's totally fixed in the current version though as I've encounter various issues, similar and not similar. If you're running 3.8 and haven't updated to 3.8.14, give it a try.