X axis resetting

I too have experienced a similar problem to a now closed discussion. When cutting multiple (repeated) objects, the gender code resets the x-axis prior to starting the second cut. From reading an earlier discussion it seems that reducing the feed was the culprit and a potential solution was resetting the SLB. I started from there.

Equipment ALTMIL 4X4 about 1 year old.

About me: I have 2 years experience with the first year of learning the ropes on a Fox Alien X-PRO.

Problem : I routinely run my machine at about 80% feed of specified tool rates. Mostly because I am not in a hurry and a bit of caution. Have not had a problem of this nature before. (Note starting experiencing “issues” after upgrading to gsender 1.6.2) I have cut projects that had duplicate pieces using earlier versions of G-sender without issue.

After determining that the errors were not mine and ruining several board feet of red oak I followed the following trouble shooting process.

  1. Because of earlier discussion I powered down the SLB, not because I was convinced but it offered a starting point.
  2. At 100 % feed rate ran the same gsender code that I had experienced problems with earlier but only withe the desire to see if the x-axis had been changed. results - run at 100% no resset. changed to 90% feed rate - x-axis rest .384 inches. zeroed x- axis again and repeated 80% run - fail with x-axis resetting .8 inches (indicating to me that the error in code was accumulating) Ran again at 100% but x-axis reset 1,1 inches. (So problem not necessarily related to speed reduction) I was going to power down SLB at this point but chose not to because I was not convinced that this is the problem.
  3. I homed machine, reset my zeroes and the chose to close gsender. I reran the tests above and closed gsender every time prior to making the cuts and the x-axis did not reset.
  4. I have so far been able to use this work around and completed two projects without error.

I do not think resetting gsender every time is a good solution but it allowed me to finish some work. I intend to rerun test with an earlier version of gsender as well as watch the gsender code in edit mode to see if I can see when the new x-axis value is introduced.

I will follow up as time permits. I hope this helps someone and please comment with thoughts and ideas.

I am a newbie

Bill

@Hilton Welcome to the group, Bill. I’ve moved your post to the gSender category since you say that the problem started with the upgrade to 1.6.2. The gSender group at Sienci will see it here.