I've been working with T2Laser for a few weeks now really getting down to the nitty gritty finite level detail and have noticed a disparity in overall image size when using the Trace feature of a bitmap and generating the G-Code from that versus T2Laser taking an image, primarily been working with .png import, and letting the software convert the image to G-Code. Normally this wouldn't be an issue if you're only working with one material piece at a time, however to speed up efficiency of my work load I'm preloading 36 pieces on top of each other, each piece measuring 38.1mm wide by 6.35mm high. Overall image size loaded into T2L is to come out at 228.6mmx38.1mm. In reality in order for the drop in height to accomodate Trace G-Code creation I have to set the image size to 229.32mmx38.1mm. The disparity in the G-Code measurement is enough to drag the image for each piece from the pieces center point. I've spent some time to work around this, by increasing overall size of the batch, tonight after identifying this was an issue with the offset from centerpoint on each piece growing as the laser moved downward on the work area. I'm also experiencing a loss of about 4mm from the sides. Although currently this is not an issue, I can forsee it becoming an issue down the road when we start doing batches larger than 36 in a single column.
Do you have any suggestions on correcting this loss in size? Is this something in regards to the GRBL version being used? T2L is telling me to use 0.9i for the EleksMaker A3 Pro 2.5W; I'll be installing an Endurance 10Watt tomorrow. Is this correct for the 2.5Watt? Will it need to change for the 10Watt, I'm thinking yes as the power output values will be different; am I wrong here?