Safety Height Issue

[mkrabset]

Safety Height Issue

[mkrabset]

Hi, thanks for your input!

1. If I understand correctly, you would want z=0 to be at safety height, instead of at the z-level where the tool touches the workpiece.
   I'm afraid I have to disagree. For me it makes more sense to zero the machine where the tool touches the material (using a touch sensor or the paper-method or whatever). A sudden change in this behaviour would probably also cause accidents for existing users.
   So for now I will leave this as-is.
   Maybe I will reconsider later if I get the same issue raised by other users. As of now I haven't.

2. Sizing in SVG is a bit involved. Please provide a sample file and info about what sizes you expect, and I will have a look.

3. If you want a local copy, you can just open it and save it locally as 'complete webpage'.
   It has no server-side backend, so your local copy should contain everything you need.

best regards
Marius

[CycloRetro]

Hi Marius the z height after doing a cut should always return to the z height set by the operator which is usually just above the material. Currently your KrabCam doesn't include code to do this, it currently moves to the next shape to cut without raising the z axis. As you can imagine this causes the cutting bit to smash into the material and break the cutting bit. In regards to the size issue see attached my original svg file and the gcode created in KrabCam Kind regards Chris Howard P: 0407 841 088 E: ***@***.*** ***@***.***> W: www.cycloretro.com F: www.facebook.com/chrishowardcycloretro

…

On Sun, Aug 22, 2021 at 6:09 PM Marius Krabset ***@***.***> wrote: Hi, thanks for your input! 1. If I understand correctly, you would want z=0 to be at safety height, instead of at the z-level where the tool touches the workpiece. I'm afraid I have to disagree. For me it makes more sense to zero the machine where the tool touches the material (using a touch sensor or the paper-method or whatever). A sudden change in this behaviour would probably also cause accidents for existing users. So for now I will leave this as-is. Maybe I will reconsider later if I get the same issue raised by other users. As of now I haven't. 2. Sizing in SVG is a bit involved. Please provide a sample file and info about what sizes you expect, and I will have a look. 3. If you want a local copy, you can just open it and save it locally as 'complete webpage'. It has no server-side backend, so your local copy should contain everything you need. best regards Marius — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#16 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AVJRB2O6SD6HR7JBCSWONLTT6CWFJANCNFSM5CSRW3WA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email> .

[mkrabset]

Hi,
Did you attach any files, or did you maybe forget? I cannot find any...

I would need both an SVG, a screenshot of your operation settings and the generated gcode.

I find this strange though. There are quite a few Krabzcam users (myself included), and I haven't heard about this problem from anybody else. Neither have I experienced it myself.

-Marius

[CycloRetro]

Try this file. This is a typical logo file I usually engrave, involves lines and pocket fills about 0.4mm deep into alloy. See attached files. When I import this into Mach3 there are extra large circles that are not on the artwork and not on the KrabCam svg imported file. Why is KrabCam creating extra circles? Kind regards Chris Howard P: 0407 841 088 E: ***@***.*** ***@***.***> W: www.cycloretro.com F: www.facebook.com/chrishowardcycloretro

…

On Thu, Aug 26, 2021 at 12:42 AM Marius Krabset ***@***.***> wrote: Hi, Did you attach any files, or did you maybe forget? I cannot find any... I would need both an SVG, a screenshot of your operation settings and the generated gcode. I find this strange though. There are quite a few Krabzcam users (myself included), and I haven't heard about this problem from anybody else. Neither have I experienced it myself. -Marius — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#16 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AVJRB2OOMK6LIRJXHF2MIBTT6T6ORANCNFSM5CSRW3WA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email> .

[mkrabset]

Sorry, I still don't see any attached files.

These extra circles are usually due to rounding problems on G2/G3 parameters.
It might help to enable checkbox "Disable arc interpolation".

-Marius

[CycloRetro]

I can't explain why you cannot see the attached files, everyone else gets my attachments Kind regards Chris Howard P: 0407 841 088 E: ***@***.*** ***@***.***> W: www.cycloretro.com F: www.facebook.com/chrishowardcycloretro

…

On Thu, Aug 26, 2021 at 3:50 PM Marius Krabset ***@***.***> wrote: Sorry, I still don't see any attached files. These extra circles are usually due to rounding problems on G2/G3 parameters. It might help to enable checkbox "Disable arc interpolation". -Marius — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#16 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AVJRB2ITAJADBTR4UW3C5ILT6XI3VANCNFSM5CSRW3WA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email> .

[mkrabset]

https://docs.github.com/en/github/writing-on-github/working-with-advanced-formatting/attaching-files

[CycloRetro]

What’s your direct email and send the files to you directly. I can’t send svg nor nc files through GitHub Chris

On Thu, 26 Aug 2021 at 6:48 pm, Marius Krabset ***@***.***> wrote: https://docs.github.com/en/github/writing-on-github/working-with-advanced-formatting/attaching-files — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#16 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AVJRB2LACRQ2TSKRKQ5HQ73T6X5WRANCNFSM5CSRW3WA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email> .

-- Chris Howard CycloRetro E: ***@***.*** P: 0407 841 088 W: www.cycloretro.com

[mkrabset]

You need to create a zip-file. As it says in the doc, github only supports the following file-types for attachments:

PNG (.png)
GIF (.gif)
JPEG (.jpg)
Log files (.log)
Microsoft Word (.docx), Powerpoint (.pptx), and Excel (.xlsx) documents
Text files (.txt)
PDFs (.pdf)
ZIP (.zip, .gz)
Video (.mp4, .mov)

[CycloRetro]

Ok Try this attachment Kind regards Chris Howard P: 0407 841 088 E: ***@***.*** ***@***.***> W: www.cycloretro.com F: www.facebook.com/chrishowardcycloretro

…

On Thu, Aug 26, 2021 at 11:24 PM Marius Krabset ***@***.***> wrote: You need to create a zip-file. As it says in the doc, github only supports the following file-types for attachments: PNG (.png) GIF (.gif) JPEG (.jpg) Log files (.log) Microsoft Word (.docx), Powerpoint (.pptx), and Excel (.xlsx) documents Text files (.txt) PDFs (.pdf) ZIP (.zip, .gz) Video (.mp4, .mov) — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#16 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AVJRB2PUNNH2KG4CAVPHDBLT6Y6CPANCNFSM5CSRW3WA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email> .

[mkrabset]

Still no attachment.

[CycloRetro]

Do you have another email address Chris

On Fri, 27 Aug 2021 at 12:40 am, Marius Krabset ***@***.***> wrote: Still no attachment. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#16 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AVJRB2PHBAMQKZUP5SAM2XLT6ZG6HANCNFSM5CSRW3WA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email> .

-- Chris Howard CycloRetro E: ***@***.*** P: 0407 841 088 W: www.cycloretro.com

[mkrabset]

Hi, it's not a good idea to write personal email-addresses here, since this conversation is publicly visible at github.

I suspect the problem is that you reply via email.
Try sending attachement using the github web-interface instead.
That should work fine as long as you follow the instructions at the link I sent you.

You will then also be able to preview your reply before you send it.

-Marius