invisible walls

[gibl5s]

ok I have been running 2d profile files all day and I came upon my last file and started having trouble. I outposted my files together, so after it would run one file it would head home and then start the next file. Only in this case when it finished running one file it started heading home and it acted like it hit an invisible wall!!!. It didn't grind like it really hit something, but it totally lost its position and the software totally went off. SO I re-ran the file again and it did the same thing at the same spot as it messed up previously.
Now I'd like to ask if anyone has ever experienced this before? And is there a way to find at what line did my file quit.
thanks in advance.

[adrianm]

The only time I've had that is when I've created a toolpath that included a stray vector that was way off the workspace. I was scratching my head for ages until I ran through the preview and saw a rapid move way off into the distance.

If you look in the location where you ran the file from there should be a log file (unless you turned that option off in SB3) that will show you how far it got.

[gibl5s]

thanks Adrian, that atleast points me in the direction where I need to start. I had no idea what was going on.
Thanks again

[shilala]

I've not had a lot of luck combining toolpaths into one output file.
I tend to keep them pieced out and start the next file, even if it's the same bit.
It helps if I want to run a portion of a job to do a "clean up", too.
I always preview the cuts in Aspire, too.
It helped me clean up a couple goofs this morning. :)