I don’t think the probe signal is even used by Atomstack. It’s not going into the ESP32 and it is terminated by a capacitor and a diode on the pcb as far as i can see. Needs some more investigation.
Thanks for the heads up on FLUIDNC. I had not heard about it, and that seems like the way to go.
This kind of mod for the laser head is to much effort for the additional value i can get. Will keep it as it is. Regarding the probe signal it is connected in a similar way as the MKS DLC. This probe pin is not directly connected to the ESP but via a resistor. I traced this and as far as i remember they have not added all the components even the pad are there. As far as i remember the resistor is the one beside the TTL connector between the two spots missing the components. The probe connector is the one directly beside the I2C connector. The next one is the Z limit connector with the probe label at the bottom. So the labels are not 100% correct at the LaserBox ESP32. Loks to be there some slightly different variants out there at leas with different labeling.
/a bit OFFTOPIC (but as we talk about improvments…)
In the Meantime, I have found a new software to virtualise USBs over LAN and access them from within LightBurn, tested today with the Atomstack, it works flawlessly.
I have virtualised three USB : this give me two remote cameras (one for lightburn software and one for overall control with a more larger view) and obviously one to control the laser via its serial USB remotly.
That just require a Raspberrypi3 and the Virtualhere software (and a very good network…USB eats a lot of bandwith).
Lightburn is then fully Wireless, and I can access the laser & its cameras from any where within my house by Wifi, pretty cool, this solution works a lot better than the previous one I have tested.
(I also would like to see how to add its cameras to “Home Assitant”.)
/a bit OFFTOPIC
I have flashed my motherboard with the firmware you suggested, running fine, I can see SCL go high on M7 command and down on M9 (M8 does not seems to do anything).
I got a warning message :
Your Grbl may not support Variable Power mode (M4)
If your laser does not turn off between cuts,
switch to the GRBL-M3 device
But I have verified by looking at the signal on the TTL pin of the lazer, and variable power mode is working well, I can see the PWM changing on corner.
About the laser connector I see two 24V power line (4 wires) and the fifth is th TTL, I suppose one power line is for the fan and the other for the lazer, it should not be difficult to make the fan just on when TTL is alive and let it on few seconds/minutes when it stop.
By the way, thanks @mj666 !
I think the X30 laser is using two GND and two 24V connections to deliver the required power for the laser. You may be able to check fro continuity between the pins of the connector. I don’t think the fan has a separate power connection.
You probably right, cable are not very thick, I will check.
On another subject I think that I will use an ESP32 or something like this to controle the fan based on the laser TTL signal, at first I wanted to do that only with analogic components, but as I have a bunch of ESP & like’s… the idea is to turn on the fan as soon as a TTL high level is detected, and stop it approximatly 30 seconds after the last detected TTL high level, so basically the laser TTL high signal will just start/restart a 30 seconds timer and once the timer end the fan will go off.
I just want to be able to let the laser on power without having the laser fan make its unberable fan noise, for now I just power it on & off each time I want to do something with it, the FAN is not really endurable for long time specially when the laser is not working…
Have you chosen the right branch from the GITHUB page? I had the same issue when i checked out the branch master and built the wrong source 
I have made some progress on mine the last few days.
The probe connection is probably supposed to be connected to a height probe inside the module, but not finished. The laser module is working fine without the signal.
My machine is rewired now and I have installed some optical home switches.
Im in progress of making a ESP8266 I2C port expander, so i can get all the outputs i need. I have decided I need 2 extra pins for enclosure fan and air assist and output 1 pin for PWM signal to the fan in the laser module and 1 ADC input for getting the temperature . I’m about 90% done with the software implementations for that, and it just needs some code cleanup. There are still some work to do around the timer delay for the enclosure fan(M8) and some logic for the tempsensor/fan in the laser module.
I have made 2 boards. One is an optocoupler mosfet driver for the air assist and the second is a opto coupled triac circuit for controlling the 230V enclosure fan.
I’m also building a custom ESP3D UI for the webui, but not a lot of progress there yet.
Nop 
, I just changed Lightburn configuration for my device to use M7 rather than M8, and despite the warning the variable power mode works well so I will probably stay with this firmware, or is there other surprises I am not aware ?
This is on my todo… I want to remake ALL cable, and displace buttons & plug, lot of work but this is what we like, no ?
Some more information would be appreciated
Todo for the chamber, I think I will use the same idea than for the laser fan with maybe a longer timer
I am fine without WebUI and without screen, using USB over IP, it is really unecessary 
EDIT: an another idea I have is to try to make a UART proxy between my computer/or the raspberry and the laser, so I would cathc on the fly any command/g-code, I think this should not be too hard using ESP reading from one serial and writing to the second, could be fun.
Not that I’m aware of. If its working why fix it 
Yeah, I like to tinker with everything. I guess you are like that as well. Am I right?
I can push the changes back to Michaels repository if he doesnt mind when I’m done and I will post some more info on it here when its complete. I dont have any time to work on it until next week, so I guess by the end of next week or so I will be done with it.
Yeah, I just found out I can stream gcode from Lightburn to the controller via WIFI/Telnet, so I might cut the cord as well if it is working correctly.
I remember this warning during my experiments. Have not seen this anymore after i switched off return to home after finishing the job in Lightburn. I also had issues to add more passes with this setting enabled since i always had an offset. Im using MKS-DLC32/V2.0.8_H35_20220105_N.bin at main · makerbase-mks/MKS-DLC32 (github.com) flashed with the MKSLaserTool since quite a while. I have not seen any issues with this firmware so far.
Ok, so I will stick with this one
I just want to be sure I understand the content of this thread correctly… the MKS-DLC32 firmware is OK for the LaserBox ESP32 v1.0 board if I want to use air assist? In this case it is for a 12V A5 Pro
Yes but you will have to wire the air assist using optocoupler on the I2C connector :
Be sure to use the proper firmware for the 1.x DLC32 board mentioned above. The latest released binary is not working for a 1.x board.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.