We use cookies to personalize content, interact with our analytics companies, advertising networks and cooperatives, and demographic companies, provide social media features, and to analyze our traffic. Our social media, advertising and analytics partners may combine it with other information that you’ve provided to them or that they’ve collected from your use of their services. Learn more.
I love the Easel environment as it was the easiest cad/cam software to learn. however, it does not control my cnc machine over IP. I have to export the file in gcode then use a webUI to run the job. I currently just completed a full size (48x96") build of the V1Engineering Lowrider 4 CNC machine and it works perfectly. My only drawback is when I design or use Easel, have to export to gcode for my GRBL machine to run the job.
I recently became aware of Cabinetmaker and was all excited but have held off purchasing either because in doing so, I know I will not be able to utilize the full capacity of the purchase… bummer because I would have subscribed to both in a hearbeat if they would control my CNC machine.
When will Easel become compatible (i.e. Control) GRBL machines wirelessly (ESP32)? That would be a huge game changer for an entire community of makers.
It sounds like you want one fluid motion from design to carve (CAD/CAM) but Easel doesn’t work with your controller. While I understand your frustration there might be an advantage to using another sender app. There quite a few to choose from and for me I found that other sender apps have more features (like the ability to run macros). Universal Gcode Sender (UGS) is used quite often as is CNCJS, Candle, Chilipepper, bCNC and GRBLGRU (who is very active in this forum)…. My favorite is CNCJS. The only inconvenience to using another app is the added extra step of downloading your Easel gcode locally once you’ve completed your design (CAD). I would encourage you to look at CNCJS as it might offer you the ability to use the Wi-Fi mode you are seeking.
I appreciate the reply. And using the gcode sender webUI that comes with the FluidNC board has proven to be the best route actually. Once job is designed in Easel or any other CAD program and saved as gcode, it is uploaded to the sdcard on the FluidNC board and then the webUI starts the job. No streaming of job or gcode, no chance of those errors. I was looking for a solution that was actually less efficient and backwards… but came to my senses. LOL