6
« on: January 14, 2020, 01:20:36 PM »
Thanks Mauri for the clarification on that. That was one of the things I figured out last night after I realized I could get the chess pieces to show up correctly in the X axis. I also noted that DRO value that you enter corrects for the z position. What I was attempting to accomplish last night was to be able to swap the rotation to the Y axis, which I thought I could accomplish by changing the zero to a one in the script for the "A rotation" button down script and it would orientate the piece on the screen correctly but the when you enter a value for the dro it moves the z axis but does not regenerate the toolpath like it does when it is set for the X axis.
April of 2018 Dazed+Confused listed the script that was need to correct for the z axis so the radius could be adjusted or corrected to show the toolpath. He wrote "mc.mcToolPathSetAAxisPosition(inst, 0.000, 0.000, getValAsNumber);" for the "dro Radius" which would be the x, y value to be 0 and the z is whatever you input in to the dro. That is what I believe makes the correction so that whatever the work piece Z zero position is, it can be corrected for the toolpath generating. When I wrote that line of the script for the DRO as you stated " mc.mcToolPathSetAAxisPosition(inst, 0.000, 0.000, 0.000);" and tested it I found as you stated the g-code has to have the top of the work piece as zero.
I am going to attempt to work on getting it to swap to the Y axis again tonight and be able to have it correct it with the dro radius value but if you have any ideas I would appreciate it. Using the code Dazed+Confused published back in 2018 works for the X axis as stated but simply changing the axis value in the line “mc.mcToolPathSetARotationAxis(inst, 0)” from 0 to 1 doesn't seem to work as itended.