Hello all,
Brand new to the forum, and in dire need of help. I manufacture baseball bats, and we recently took on a project to manufacture a piece of a bat barrel to send to another company for them to finish. I run a Locatelli Multimatik 1600 V.1 and use Goelan 4.6 software on it. It operates on an Osai computer unit.
I am having an issue when trying to do these barrels with my sanding belt. We typically run stock that is 33-36" long and the machine runs flawlessly. This particular project calls for stock to be 16-19" and it is having a fit. When it completes its final cut, the sanding belt moves into position but spins in place and does not progress down the barrel of the bat into the handle. The computer unit throws the error: Positive Overtravel Limit Z. Myself, nor our old bat designer have never seen this code, and the founder of our company who bought the machine said he never saw that code in the 13 years of us owning the machine.
Can anybody help out with some tips or tricks, or maybe some feedback of what I should look at in the design of the project itself to avoid this error code?
Thanks,
BT
Brand new to the forum, and in dire need of help. I manufacture baseball bats, and we recently took on a project to manufacture a piece of a bat barrel to send to another company for them to finish. I run a Locatelli Multimatik 1600 V.1 and use Goelan 4.6 software on it. It operates on an Osai computer unit.
I am having an issue when trying to do these barrels with my sanding belt. We typically run stock that is 33-36" long and the machine runs flawlessly. This particular project calls for stock to be 16-19" and it is having a fit. When it completes its final cut, the sanding belt moves into position but spins in place and does not progress down the barrel of the bat into the handle. The computer unit throws the error: Positive Overtravel Limit Z. Myself, nor our old bat designer have never seen this code, and the founder of our company who bought the machine said he never saw that code in the 13 years of us owning the machine.
Can anybody help out with some tips or tricks, or maybe some feedback of what I should look at in the design of the project itself to avoid this error code?
Thanks,
BT