Turnkey

[ajfoul]

I haven't worked with the plugin for a long time, so this may be way off. But, it wasn't working for me (and apparently others) with Smoothie because the M3 was missing.

[ghost]

Smoothie doesnt use M3:

G1 = cut, G0 = seek:

http://smoothieware.org/laser

Here is how Smoothie laser control works : G0 and G1 are exactly the same command, they take positional parameters ( X10 Y5 Z3 for example ) and move the tool to that position.

The only difference is that when using G0 the laser stays off, and when using G1 the laser is on, only during movement.

To test, try moving your laser with G0 and try moving it with G1 :

G0 X10 F300
G1 X20 F300

You can set the power for the laser by using the S parameter. Values goes from 0 ( 0% ) to 1 ( 100% ).

For example :

G1 X10 F300 S0.2

[ajfoul]

Yes, I understand how the laser module works. But, it was intended for single pin PSUs. With a two pin PSU you either have to have the fire pin always on or you can config a switch to fire/extinguish on M3/M5. I prefer that latter method.

BTW I manage the Opensource Laser group. Come on over!

[ghost]

Ahh ok! Makes sense! Will add that logic to my github.com/openhardwarecoza/LaserWeb - wasnt a scenario i thought of (:

[ajfoul]

Oh, I knew I recognized the name... You posted a comment on my K40 buildlog. Cool stuff, haven't tried it yet as I don't Chrome, but I bet there are folks on the Google group who would like to give it a go...

As to this pull request, I am wondering if I've addressed a real issue as it hasn't been merged or rejected. I'm on a Mac and lately every system update breaks Inkscape which makes it hard for me to test.

Also, I mostly do vector cutting and Autodesk F360 (with the Smoothie post processor I helped them implement; Yay me! ;-) has really smoothed out my workflow.

[funinthefalls]

LaserWeb is really starting to mature. Peter does some nice work, and is always quick to address issues or feature enhancement requests.