No. I started writing this under the assumption that it was eventually going to become a WebUI extension but I skipped that part at the beginning. It just meant that I was looking to keep it small in size and not use external libraries. I also sent it down a design path so I could have a standalone viewer and a separate extension version that shared code. I also pointed it at some documentation and the example extensions I wrote without AI. I’m finding it incredibly useful, but it’s not going to just let anyone make whatever they want. Sometimes it gets in a loop where it’s struggling to figure out what is wrong and I either need to give it some direction or just figure it out myself.
fair enough. I guess I will try to find the video, but he made and extension that he can pull up in ncviewer and right there just tell it to cut a line so deep by so long and it does it.
Oh, you’re talking about ncSender not ncViewer. I could certainly make something send gcode commands to do something. My joystick extension already does that. At the same time, I have no intentions of making a sender. I’d be more inclined to generate gcode, upload that to the FluidNC SD card, and run it there. Like I was thinking of generating surfacing gcode and running it that way. I don’t want to have to deal with streaming gcode commands at the right frequency.
Someone said something about falling down a rabbit hole when using AI such that you end up implementing way more than you normally would.
Well, now it lets you define colors for each tool in comments, provides per tool time estimates, and those estimates should be pretty accurate. It’s considering acceleration for each axis and max feedrate for rapid moves. The FluidNC extension is automatically pulling those from the config. When detecting tool changes, it adds 30 seconds per manual tool change (detected as M0 with “tool” comment) or 10 seconds for automatic ones (detected with M6). I also updated the tool parsing to support a format that I can get MillMage to output since it can’t output the tool list at the top like Estlcam.
The FluidNC extension is getting larger. It’s up to almost 24 KB. With 4 MB of Flash, that gives you 192KB of available space. Once you have WebUI3, preferences, and config, you’ve got about 80 KB or so for themes and extensions. Or you can use a custom filesystem to kill OTA support and get 1.92 MB. Or you can use an 8MB ESP32 with a custom filesystem to get even more. Either way, at some point I’ll see if I can trim some space off the FluidNC extension or possibly create a separate reduced size version.
