Mid Year recap!

[jorgerobles]

Hello all @LaserWeb/devteam !

I think is time for a MidYear Recap of Laserweb4 status. I wish We could put what to be done in next efforts and maybe priorities. No pressure :D

Any issue should narrow use cases if possible (to check if are proven necessary or not like postprocessing)

[jorgerobles]

For example:

• Integration with more machines and protocols
• Enhance performance of display #216 <-- GOOD WORK DONE
• Allow users to customize their workspace
• Some killer functionalities ( Vector packing again ;D )
• Postprocessing.
• Enhance Gcode parsing (G2, G3)

[ghost]

Fix missing features not yet ported from LW3 (catch up before we speed onward)

• Missing Probe / per axis homing comms: https://github.com/LaserWeb/LaserWeb4/issues/255
• Trace to Vector (popular user request) (poTrace.js) https://github.com/LaserWeb/LaserWeb4/issues/275
• GCode Parser https://github.com/LaserWeb/LaserWeb4/issues/248 (G2, G3, etc as the old parser already had)

[cprezzi]

Probe and per axis homing is in work. ;)

[ghost]

Yay! Oh how i missed probing (;

Sidenote at some point we need to add Probe Diameter for XY probes (actual probe is at probepos - (probedia /2) since your probe is either an endmill or a ball probe, both of which has a diameter offsetting actual 0. Maybe even extend probe with a second menu 'probe and zero' that

1. Probes (stops at end of probe)
2. Sets Zero (but with half probe dia taken into account)

On Jun 14, 2017 10:07 AM, "Claudio Prezzi" [email protected] wrote:

Probe and per axis homin is in work. ;)

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/LaserWeb/LaserWeb4/issues/343#issuecomment-308354475, or mute the thread https://github.com/notifications/unsubscribe-auth/AHVr21NrNLHIx0MfElifBwBySqaaFx-7ks5sD5S9gaJpZM4N2a0W .

[jeepshop]

Cool feature. Probably shouldn't use recommend using an end mill as they actually aren't round. They have a 'wave' to them when looked at from the side. Below is a common 4 flute end-mill which shows the problem... But even worse are the 0-flute end mills used to cutting plastics, they aren't even flat on the bottom. A piece of drill rod will be much more accurate than an end-mill.

[image: Inline image 1][image: Inline image 2]

On Wed, Jun 14, 2017 at 5:53 AM, Peter van der Walt < [email protected]> wrote:

Yay! Oh how i missed probing (;

Sidenote at some point we need to add Probe Diameter for XY probes (actual probe is at probepos - (probedia /2) since your probe is either an endmill or a ball probe, both of which has a diameter offsetting actual 0. Maybe even extend probe with a second menu 'probe and zero' that

1. Probes (stops at end of probe)
2. Sets Zero (but with half probe dia taken into account)

On Jun 14, 2017 10:07 AM, "Claudio Prezzi" [email protected] wrote:

Probe and per axis homin is in work. ;)

— You are receiving this because you commented. Reply to this email directly, view it on GitHub <https://github.com/LaserWeb/LaserWeb4/issues/343#issuecomment-308354475 , or mute the thread <https://github.com/notifications/unsubscribe-auth/ AHVr21NrNLHIx0MfElifBwBySqaaFx-7ks5sD5S9gaJpZM4N2a0W> .

— You are receiving this because you are on a team that was mentioned. Reply to this email directly, view it on GitHub https://github.com/LaserWeb/LaserWeb4/issues/343#issuecomment-308383127, or mute the thread https://github.com/notifications/unsubscribe-auth/AXxGS1hMNEqOXHFW_Cvjbz6VeOXDv2jRks5sD62agaJpZM4N2a0W .

[tbfleming]

Users which have reversing variable-speed spindles could run the mill in reverse at a low speed.

[cprezzi]

We could add 'probe diameter' in settings, and if the value is 0, use a popup to ask the user for the probe diameter after probe button click. Would that be ok?

[ghost]

Yip would be fine.

In terms of hardware precision etc as above, a) irrelevant to the software side of things. You make your probe run true, we'll send the commands. And b) remember generic approaches. Some people use endmill, others use dedicated probes. Some uses completely different things like probes mounted on the carriages. Irrelevant for our purpose, but it does need an offset from actual 0 to 'probed' trigger (;

On Jun 14, 2017 4:21 PM, "Claudio Prezzi" [email protected] wrote:

We could add 'probe diameter' in settings, and if the value is 0, use a popup to ask the user for the probe diameter after each button click. Would that be ok?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/LaserWeb/LaserWeb4/issues/343#issuecomment-308446360, or mute the thread https://github.com/notifications/unsubscribe-auth/AHVr2zWcMDe0Lb3zuOrqXibxAYAWkLoAks5sD-w0gaJpZM4N2a0W .

[jorgerobles]

@tbfleming @cprezzi Sent you a message by Gplus some days ago. Have you seen it?

[tbfleming]

I don't see it. Try adding a reply tagging us.

[jorgerobles]

Done!

El dom., 22 abr. 2018 13:01, Todd Fleming [email protected] escribió:

I don't see it. Try adding a reply tagging us.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/LaserWeb/LaserWeb4/issues/343#issuecomment-383373218, or mute the thread https://github.com/notifications/unsubscribe-auth/ABoIYAOwy5fc9IB-FlztWDzd2hxgCLWBks5trGL9gaJpZM4N2a0W .