#K40 laserdrw 3 settings driver

Would look a lot weird, but would ensure whatever the first job is, it started correctly at (0,0).

#K40 laserdrw 3 settings driver

In theory, I could make the driver home the device, draw the part where visicut tells me it is, then make the driver home the device again when done. The homing only serves to fixed things between objects. Whisperer returns to the upper left hand corner of the part completed (or tries, it's actually off by 2 mils after a raster). MeerK40t for example just stops exactly where it finished and stays there, or goes to the next part exactly from that location. The issue of homing is that the first engrave operation is assumed to be 0,0 and you might have the head moved, either manually or from something else.

So saving the driver state wasn't an option. Visicut seemed pretty geared towards sending all the data to the device and be done with that device. In the lcode file the command 'IPP' at the end tells it to home the machine. If I left the laser head at (500,1000) and the it sent the next job as a different event it would think it was at 0,0, and would be off by half and inch and an inch respectively. But, this left an issue that between jobs it wouldn't know where the laser head was actually located. The visicut system would work really well for protocols like Moshiboard, and GCode systems without any realtime controls.ĭesignwise, I didn't want to move the laser head when it wasn't needed since I tracked the exact expected position within the driver itself at all times. It's one of the reasons I coded up MeerK40t since I could add such things. Visicut didn't have any jogging or positioning controls or realtime command systems. (Any initial position is considered to be 0,0 and may not be).