I was having this issue over the weekend but with VCarve, not Easel, so this probably isn’t your issue but you can check. I’m still not even sure why this was an issue. Long story short, check your post processor.
When I initially set up VCarve with the Onefinity post processor, the output was a .ngc file. I went out to start some files on Friday night and when I went to save the Gcode file, the software made me pick the post processor again (it was blank, when it is normally already populated). Without thinking about it, I selected one of the two options availabe (Onefinity Inches or Onefinity mm), saved my files, and transferred them to the controller.
Every single file that I uploaded that day was just cutting air no matter what I did. The files that were already in the controller worked fine. After about an hour of frustration (checked machine, toolpaths, zero, re-homed, basically did everything I could think of), I noticed that the post processor in VCarve had changed from outputting a .ngc file to outputting a .gcode file. The post processor for outputting a .ngc file was no longer available. After resetting the computer and the software, the .ngc post processor was back. I saved and transferred my files and they ran without any issues.
The issue that night was that VCarve had somehow switched to a .gcode post processor instead of .ngc and the file was running everything except the Z-axis. After I switched back to the .ngc post processor, everything worked fine. I found it odd because I’ve run .gcode files from another software (JointCam) just fine. The only thing I can think of is that the .gcode file from VCarve was tossing something in there that the Onefinity controller didn’t like. I was in a hurry to get cutting so once my files were running, I just got to it and didn’t stop to compare the code from both files.
Different software for you but it might still be worth looking into.