i told it to jog the outside and it tried to run itself off the edge i imagine trying to jog around that
fix:
firmware-package.zip (1.3 MB)
1 Like
Did you see that large shape in krabzcam too?
Maybe you can share a screenshot, and your svg?
Can you post your gcode file here? This looks like a bug in the Maslow code to find the boundary of the object
Bar wrote:
Can you post your gcode file here? This looks like a bug in the Maslow code to
find the boundary of the object
fonts with lots of curves and sharp points can have control points that are a
long way from where you expect the letter to be.
David Lang
Control points shouldn’t show up in the gcode though
This is why I prefer a tight little rectangular block around object to be processed.
1 Like
I came from .88 with great enthusiasm to try 1.15 and encountered the same problem with the giant circle. It almost caused a disaster because my machine went out of bounds. Since it was my first time, I didn’t understand what the circle meant. When I created the trace boundary, I didn’t imagine it was possible for the machine to move so far away. Here’s my G-code if you want to replicate it.
posapiespocket.nc (7.8 KB)
I also used Krabzcam and the circle wasn’t visible there. I created 8 files and only 3 showed the oversized boundary on the Maslow screen.
Ian Abbott wrote:
This is why I prefer a tight little rectangular block around object to be
processed.
rectangular vs up to 100 section polygon isn’t the issue, the issue is what is
there that the softwar thinks it’s drawing around.
David Lang
Javier Betancourt wrote:
I also used Krabzcam and the circle wasn¢t visible there. I created 8 files and only 3 showed the oversized boundary on the Maslow screen.
can you post the file that you are putting into krabzcam as well?
the blue circle in Maslow is maslow trying to draw around your object to show
you where you will be going when you cut.
If there isn’t a bug in the algorithm of it mapping this out, it means that your
g-code is telling it to go out to those areas.
David Lang
Bar wrote:
Control points shouldn¢t show up in the gcode though
another thought I had, if there are g2/g3 circles being drawn that are really
short, an error in precision could make the maslow analysis think these near
zero length circles go out a long way.
David Lang
1 Like
David Lang wrote:
Bar wrote:
Control points shouldn’t show up in the gcode though
another thought I had, if there are g2/g3 circles being drawn that are really
short, an error in precision could make the maslow analysis think these near
zero length circles go out a long way.
The file posted here has lots of g2 and g3 commands.
David Lang
David Lang wrote:
The file posted here has lots of g2 and g3 commands.
There are multiple bugs in how it was handing bounding boxes with g2/g3
commands, it fixed one, I had it check a different test case and it’s fixing
that as well
David Lang
1 Like
give this a try and see if it clears up the problem (it fixes bounding box calculations and fixes the UI so that it decides if it’s an arc or full circle the same way the firmware does)
I am not near a machine to be able to test this (2am my time)
index.html.gz (127.8 KB)
2 Likes
follow_path.nc (106.7 KB) this is the file, it only shows the circle in the maslow it dosent show up on krabzcam from what i can tell
1 Like
I found some other bugs in how the display on the maslow shows G2/G3 commands, they should be fixed in here.
There are a lot of changes queued up for v1.16, so it’s possilble that just loading the index.html.gz with the old firmware won’t work. Just in case, I’m posting both the firmware and the index.html.gz files here
firmware-package.zip (1.3 MB)
@Caleb_Yager your file also uses g2/g3 so is likely to have a similar issue.
the blue shape around your design is supposed to be a rough outline of your design so that you can hit the ‘trace boundary’ button and have the machine walk around the outside of what would be cut (so that you can make sure it’s positioned on the workpiece as you want it to be), but in v1.15 there are bugs that cause it to not properly create that outline when you have g2/g3 arcs in your gcode.
1 Like
thank you i really appreciate it, and so do i just update those files like normal with both, i see the readme but i haven’t changed anything for the index file to go into so do i just upload it like normal too?
Caleb Yager wrote:
thank you i really appreciate it, and so do i just update those files like
normal with both, i see the readme but i haven¢t changed anything for the
index file to go into so do i just upload it like normal too?
the index.html.gz file gets uploaded as a plain file (via the fluidnc tab), the
firmware.bin needs to be uploaded by the firmware upload button to the right of
the files button on that same tab.
you are not erasing or changing your maslow.yaml file.
David Lang
1 Like
@Betalombo that looks like the problem I identified. it’s treating those arcs as if they were full circles and drawing around those. try the new files and see if that solves it for you (be aware that the firmware.bin is very close to what v1.16 will be, so it adds some new features and may have some bugs, so if ANYTHING odd happens, report it so we can check it. We think it’s good, but it hasn’t gone through a lot of testing yet, your reports will help us validate that it’s good to release. 
)
2 Likes