I have an Atomstack A10 Pro V2 which I have connected by TCP/IP to lightburn via Wifi. I have tried it with two different Pc’s and have come to an issue on both… The first one keeps loosing connection and generally is an issue, so I moved to the second one to see if it was PC related or not. Once I was connected the second PC, themachine will only cut one layer. I was trying a 100mm sq box with engraved lines spanning the X & Y to give me references to measrue to get an average for adjusting both axis. I select both layers which are both showing output. tell it to start, it begins states that the stream is complete in a few seconds shows the laser busy (which is executing the top layer in the layers window), once its completed it stops and homes as it is set to do at the end of every cut. DTR setting doesnt seem to have an effect I dont believe, which I will verify once the current job is complete on my other laser. I dont know of a Cut only one layer setting, other than trunign off the specific layer’s output in the layers window. I am at a loss. I wouldn’t think that the connection would have an effect on it, and again I am not aware of any setting. This machine is beng a bit of an issue as I am trying to set it up for bataching out a job. My Falcon has been cranking out parts all week on this PC. I am at a loss, does anyone have any ideas?
DTR signal does not have an effect when using WiFi.
Did you check with the Preview (Alt + P)? This will always show you what exactly gets sent to the laser.
If you loose connection to the laser while running a job, you should see some error message in the Console window.
Aaron, Thakns for that information re: DTR. Iwasnt sure and I thought I had read something about that in the TCP/IP setup. At this point with some further testing and efforts, I have determined that the Wifi connection is a problem on my network for some reason through WiFi. I was able to export the Gcode and cut it that way through the use of the Atomstack app, however the same only cuts one llayer applied. If I do sub layers it does that, but there is no getting it to cut multiple layers from Lightburn via WiFi. I am getting a notification through the Atomstack app that the firmware needs an update, I havent been able to get it to install at this point, but I will continue my efforts.
Get rid of wifi. It’s the worst method of connection available. Wi-Fi is unstable and prone to interference. Use a usb cable whenever possible. And it IS possible in 99.9% 
Yeah I am thinking of purchasing another Raspberry Pi and use Virtual here for it like i am doing fo rthe Creality.
Yeah, your connection method is unsupported for a reason - a hacky implementation using a pi to emulate a USB port over WiFi is bound to have issues.
Ok… well its not the Unsupported Connection Method that is the issue. Its a different machine entirely. The machine that is running from Virtual Here is running great, with no issues and has been cranking out parts for over a week with no connection issue what so ever. I have been using that product for months with no issues.
The machine that is connected via TCP/IP settings in Lightburn’s connection is the one i am having issue with. I am not stating that they are or are not the reason. After I the original post I went back and tried a few different configurations and double checked my settings from one machine to the other. I tried dumping the file to Gcode with multiple Layers selected with output on, and saved it to a card which I then ran from the machine direct and again it went to through one layer and stopped. When I tried again this time with Sub layers it that worked for the images on that layer and then it stopped.
I initially thought perhaps that the process for the over TCP/IP might be a dump of the entire Gcode at once rather than a continual stream as it appears on the serial connection side. When I start the stream on the TCP/IP Machine it will say that the stream is completed in a few second instead of the 90 plus minutes it should take, and the machine comes on, continues to work until the layer is completed then it stops.
Again things didn’t seem to equate to each other. the only reason i even mentioned the connection methods was to see if there was a difference in the way the program communicated with the controllers over the different connection methods.
SOLUTION… RTFM… It was Buffered Transfer mode that was causing my issue. Changed it to synchronous and sent a test and both layers ran in real time stream.
To see why, add a WIFI Analyzer app to your phone or tablet. You will see signals on various channels drop to zero ampitude.