This means the NS1E command that seems to be done in real raster mode is the only reason we'd be forced back to full raster mode. Which means we can change the speed and accel value and other values on the fly. And there appears to be no way to set this axis elsehow. This is to say NSE and other-direction-of-a-raster perform a step along one specific and explicitly given axis. This means that the only real need to call or kick all the way back to real rapid mode is that we will sometimes need to set the major and minor axis. And we could even avoid ever calling vector mode anyway. Here, if we could interpret the commands correctly and perform the relative movements correctly we could implement raster mode in a much more vector-mode friendly way. It's vector mode raster implementation which often clicks at the edges and needs to run much more slowly.
Since the options there included DPI of values like 225 or whatever, which aren't able to be achieved with a set step the current implementation is a hard-raster.
With NSE stepping we can more effectively perform a scanline step effectively.Īlso, since this is a vector mode option, it should also work for things like lightburn ruida emulation which suffered serious problems. G000 might as well just be a flag that means perform unidirectional rastering. I at one time thought G001G002 would do variable stepping on each side, but it doesn't work. We can also do more fine grain control of rastering. This would require pixels also have a 3,3,4 width-wise. Or raster with a variable step such as a 3,3,4 pattern which would give you a DPI of about 300 rather than 250 or 333. We are going to be wasting 4 characters each scanline, however this type of scanline can be set dynamically. With NSE scanline switching we can simply replace the T in that case with NLcSE assuming we're stepping towards the top (L) and our step size for that step is 3 (c). The core of this is understanding that G001 mode turns the switch of right moving raster or left moving raster into what is apparently the same as NSE so if we're going right (B) we can switch, turn off the laser, and reverse with the command T which means turn right. This is mostly for testing unless there's a better reason to add it than it exists. Make guides ("How to setup cameras?", etc)Ĭreated 15 Dec, 2021 Pull Request #708 User Tatarize Provide feedback, criticism is preferable to praise but both are welcome.
There are a lots of ways to help the project.ĭesign ( Good design instincts, smooth out the rough edges) Open source projects live and die with their support. If you need additional support, please research/ask on: If you have a bug, feature request, or other issue raise it here. PPI Power modulation (Yes, power modulation for the M2 Nano) Grid/Guides, Zoom and Pan scene Navigation (use middle mouse button, mouse wheel). The wxMeerK40t is the GUI and is written in wxPython.īuilt in Raster Preprocessing, RasterWizard.ĭual drivers, use either the Whisperer method or LaserDrw method. Please help us make this a comprehensive source of information. The primary source for help and documentation is the
MeerK40t is written in Python and precompiled versions areįor Windows, Mac OSX, Linux and Raspberry Pi.Īlternatively you can run MeerK40t directly from Python.
It's a replacement for LaserDrw, Corel Laser, and K40 Whisperer.įor the M2-Nano, Meerk40t supports two sets of drivers which come with the software supplied with the K40 and which are used by Whisperer and the default USB drivers,Īnd so MeerK40t can usually run alongside these other pieces of software but without requiring them as a pre-requisite. MeerK40t (pronounced MeerKat) is a built-from-the-ground-up MIT licensed open-source laser cutting software.