Customizaton? #1897
Replies: 5 comments 2 replies
-
There is nothing wrong with such approach. Maybe it will attract new developers to bCNC project. Can you please provide detailed description of what features you want to get in bCNC? |
Beta Was this translation helpful? Give feedback.
-
Harvie, |
Beta Was this translation helpful? Give feedback.
-
Hi Tomas,
Thanks for getting back to me!The problem with butting up two pieces would
be at the joint between them, which may be different thicknesses. Between
the row of probe points on one board to the next row on the other board,
the data would be interpreted as a slope and throw off any engraving close
to the edge. Since I'm engraving really fine detailed stuff, even a
variation of 0.1mm makes a noticable difference.
Ideally I would set as many as 4 different probe zones, which would each
have their own height map which could be applied to a single gcode file in
bCNC.
Are you the brain child behind bCNC? This software is so good!
If you don't have the bandwidth for your feature, perhaps there is one
small one you could take, which is assigning macro buttons to keys on the
keyboard. Or if this is already possible, I don't know how to do it.
Let me know if you can squeeze the height probe project into your schedule.
Cheers,
Tyler
…On Fri, Aug 16, 2024, 04:44 Tomas Mudrunka ***@***.***> wrote:
I am rather busy, but i am thinking about some of the features you've
said. Can't you just autoprobe whole workspace? that way you wouldn't need
to have separate autoprobe maps for each part of the workspace.
—
Reply to this email directly, view it on GitHub
<#1897 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGUKYUWQOLOUA6UC3A3W52DZRW3W3AVCNFSM6AAAAABMAN5WPGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMZVGYZTGNI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Sorry, I should never send an email before my first cup of coffee. I'll
write another one later that spells things out a little more clearly.
Cheers,
Tyler
…On Fri, Aug 16, 2024, 08:30 Wire Monkey ***@***.***> wrote:
Hi Tomas,
Thanks for getting back to me!The problem with butting up two pieces would
be at the joint between them, which may be different thicknesses. Between
the row of probe points on one board to the next row on the other board,
the data would be interpreted as a slope and throw off any engraving close
to the edge. Since I'm engraving really fine detailed stuff, even a
variation of 0.1mm makes a noticable difference.
Ideally I would set as many as 4 different probe zones, which would each
have their own height map which could be applied to a single gcode file in
bCNC.
Are you the brain child behind bCNC? This software is so good!
If you don't have the bandwidth for your feature, perhaps there is one
small one you could take, which is assigning macro buttons to keys on the
keyboard. Or if this is already possible, I don't know how to do it.
Let me know if you can squeeze the height probe project into your
schedule.
Cheers,
Tyler
On Fri, Aug 16, 2024, 04:44 Tomas Mudrunka ***@***.***>
wrote:
> I am rather busy, but i am thinking about some of the features you've
> said. Can't you just autoprobe whole workspace? that way you wouldn't need
> to have separate autoprobe maps for each part of the workspace.
>
> —
> Reply to this email directly, view it on GitHub
> <#1897 (reply in thread)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AGUKYUWQOLOUA6UC3A3W52DZRW3W3AVCNFSM6AAAAABMAN5WPGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMZVGYZTGNI>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
Beta Was this translation helpful? Give feedback.
-
Hi Tomas,
Not sure if my reply went through. I think I should have hit "reply all".
Message below:
Hi Tomas,
Thanks for getting back to me! The problem with butting up two pieces would
be at the joint between them, which may be different thicknesses. Between
the row of probe points on one board and the other board, the data would be
interpolatwd as a slope and throw off any engraving close to the edge.
Since I'm engraving really fine detailed stuff, even a variation of 0.1mm
makes a noticable difference.
Ideally I would set as many as 4 different auto level "zones," which would
each have their own height map which could be applied to a single gcode
file in bCNC based on XY coordinates.
Are you the brain child behind bCNC? This software is so good!
If you don't have the bandwidth for this autolevel multi zone feature,
perhaps there is one small feature you would be able to add, which is
assigning macro buttons to keys on the keyboard. Or if this is already
possible, I don't know how to do it.
Let me know if you can squeeze the autolevel multizone project into your
schedule and we can talk details and payment
Cheers,
Tyler
…On Fri, Aug 16, 2024, 04:44 Tomas Mudrunka ***@***.***> wrote:
I am rather busy, but i am thinking about some of the features you've
said. Can't you just autoprobe whole workspace? that way you wouldn't need
to have separate autoprobe maps for each part of the workspace.
—
Reply to this email directly, view it on GitHub
<#1897 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGUKYUWQOLOUA6UC3A3W52DZRW3W3AVCNFSM6AAAAABMAN5WPGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMZVGYZTGNI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Hey folks,
I've been using bCNC almost daily for almost 5 years now and love the software. I've had little issue and what I find sets it apart from other senders is the: super easy Z autoprobing, ability to quickly edit gcode by clicking in toolpath, macros, etc.
There are some specific functions that I would like to add based on my manufacturing use case and I wonder if anyone on here is actively working on bCNC and would like to earn some money customizing the software for my needs.
I don't know the etiquette on github regarding requests for paid work, so I hope I'm not breaking any rules. If there is an official way to do this, I'm all ears.
Cheers!
Tyler
Beta Was this translation helpful? Give feedback.
All reactions