In laserweb I have set the laser test power to 100 and test fire time to 100 but when I hit the laser test button on the Jog page it does not fire laser.
I am using a smoothie board if it matters.
The laser cutter works when I run the G code, so can I assume it has the fire command?
OK I will try that firmware
Download firmware-cnc.bin, rename to firmware.bin, put on Microsd card, reset board, watch LEDs count up in binary.
I think I understand what is going on. Looking at the config.txt there is a fire pin. The instructions I got when installing the smoothie board on the K40 did not involve hooking up this pin, as far as I am aware. So when I type M03 the test button on the machine fires the laser.
I remove the M3 and M5 from the config under laser fire. I have installed the firmware you sent link to.
Now G28 does not home to the limit switches and laser fire still does not work.
I am also having weird problems, sometimes laswerweb will say connected and idle but commands doe not work. I usually have to power down everything, server smoothie, unplug USB, power up laser wait 10 second plug in smoothie then restart everything.
If I connect smoothie before powering on the laser windows will not recognize the device.
I am wondering if the smoothie board I got is bum board?
The firmware you sent me link to was “firmware-cnc.bin” and in the gcodes it says G28 will go to reference 0,0,0 if in CNC/grbl mode, could the firmware be incorrect?
Here is my configuration for the laser
Laser module configuration
laser_module_enable true # Whether to activate the laser module at all. All configuration is
# ignored if false.
laser_module_pin 2.4! # this pin will be PWMed to control the laser. Only P2.0 - P2.5, P1.18, P1.20, P1.21, P1.23, P1.24, P1.26, P3.25, P3.26
# can be used since laser requires hardware PWM
laser_module_maximum_power 0.8 # this is the maximum duty cycle that will be applied to the laser
laser_module_minimum_power 0.0 # This is a value just below the minimum duty cycle that keeps the laser
# active without actually burning.
#laser_module_default_power 0.8 # This is the default laser power that will be used for cuts if a power has not been specified. The value is a scale between
# the maximum and minimum power levels specified above
laser_module_pwm_period 20 # this sets the pwm frequency as the period in microseconds
switch.laserfire.enable true
switch.laserfire.output_pin 2.6
switch.laserfire.output_type digital
switch.laserfire.input_on_command
switch.laserfire.input_off_command
@Trampas_Stern homing on that firmware requires G28.2
yes I renamed the file…
I uploaded the edge firmware and G28 again homes.
I have noticed in laserweb when I hit test fire on the laser it appears to lock up.
in ponterface if I type @fire 30 it will respond saying it is firing at 30% but the laser does not fire.
I am using a K40 laser and a smoothie upgrade board from Cohesion3D. Ray at Cohesion3D helped me setup the config file and connect the board so I assume it is correct but it might not be.
I am unsure what a “laser module” and a “swithc module” is int this context. I am not sure what pin 2.6 is connected to and why?
OK so I should remove the switch section? from the configuration?
Sorry that is my mistake calling it a smoothieboard
+Peter van der Walt yeah we’re doing the firmware-cnc and a dedicated config file for the laser bundle production batch. In other words, yepp - starting now.
Pin 2.6 controls L. We turn it on using M3 in the start gCode and M5 to turn it off in the end gCode. This way the planner is not broken each line.
Pin 2.4 is level shifted and gets wired instead of the pot wiper for PWM. This way there there should be no ambiguity in laser power levels between individual setups and customers. As a side effect of this the physical test button does not work, because smoothie holds the PWM level at 0 when it is not firing. That said, the fire button in LW makes up for this. Thanks for that 
Other points well noted.
+Peter van der Walt FWIW the fire command is in the laser module and should work regardless of being a CNC build or not. Of course laser users should be using the CNC build for the awesome LCD panel display for lasers 
also for the grbl compatibility mode.
? is also supported in both builds. the main difference is G28 not being home, the error messages you get and the panel display. there probably are no other differences. I suspect the error messages you get are the important aspect of using grbl mode for you. you can also enable grbl_mode true in the config file for a 3d build and it will be almost identical (except for panel).