Re: [Emc-users] Toolchange M6

2016-04-17 Thread andy pugh
On 18 April 2016 at 00:16, Danny Miller wrote: > Here, it'll pause but AFAIK the dialogue box can't be "OK"ed > with the resume button On my mill you can press the "run" button to "OK" the dialog box. There is a pin belonging to hal_manualtoolchange, you can net that

Re: [Emc-users] Toolchange M6

2016-04-17 Thread Danny Miller
et to a constant. >> >>> -Original Message- >>> From: Danny Miller [mailto:dan...@austin.rr.com] >>> Sent: Saturday, April 16, 2016 7:40 PM >>> To: emc-users@lists.sourceforge.net >>> Subject: Re: [Emc-users] Toolchange M6 >>> >

Re: [Emc-users] Toolchange M6

2016-04-17 Thread hubert
ble with all offsets set to a constant. > >> -Original Message- >> From: Danny Miller [mailto:dan...@austin.rr.com] >> Sent: Saturday, April 16, 2016 7:40 PM >> To: emc-users@lists.sourceforge.net >> Subject: Re: [Emc-users] Toolchange M6 >> >> So I wil

Re: [Emc-users] Toolchange M6

2016-04-17 Thread Gregg Eshelman
com> To: Enhanced Machine Controller (EMC) <emc-users@lists.sourceforge.net> Sent: Saturday, April 16, 2016 2:44 PM Subject: Re: [Emc-users] Toolchange M6 No reason you shouldn't be able to do all the tool changes in a

Re: [Emc-users] Toolchange M6

2016-04-16 Thread Ken Strauss
You could always start each job with a sequence of G10 L1 P3 to clean up the tool table. > -Original Message- > From: andy pugh [mailto:bodge...@gmail.com] > Sent: Saturday, April 16, 2016 8:14 PM > To: Enhanced Machine Controller (EMC) > Subject: Re: [Emc-users] Toolchan

Re: [Emc-users] Toolchange M6

2016-04-16 Thread andy pugh
On 17 April 2016 at 01:06, Ken Strauss wrote: > Just setup a dummy tool > table with all offsets set to a constant. It might start constant, but it will be filled up by random numbers as people touch-off their tools and their work. This doesn't matter unless the

Re: [Emc-users] Toolchange M6

2016-04-16 Thread Ken Strauss
; From: Danny Miller [mailto:dan...@austin.rr.com] > Sent: Saturday, April 16, 2016 7:40 PM > To: emc-users@lists.sourceforge.net > Subject: Re: [Emc-users] Toolchange M6 > > So I will not have a "tool table". That's a nonstarter. I don't > provide bits, people will us

Re: [Emc-users] Toolchange M6

2016-04-16 Thread Danny Miller
So I will not have a "tool table". That's a nonstarter. I don't provide bits, people will use whatever they like (a very large range!) and the CAM stage is their business, not a machine issue. I wouldn't require them to mod out the tooltable file to match their bits, nor would I even allow

Re: [Emc-users] Toolchange M6

2016-04-16 Thread Gene Heskett
On Saturday 16 April 2016 16:30:11 Danny Miller wrote: > What does this do, just skip toolchanges and state it's changed? > But only if it knows, from the previous run, that the requested tool is in the spindle. > Problem being, if you have a file which changes tools, there will be > no

Re: [Emc-users] Toolchange M6

2016-04-16 Thread Danny Miller
I am not in charge of CAM, not in any way. I can't control what people use to generate g-code and people will be doing whatever they feel like doing. Many CAM programs start with M6 T1. There's no reason be requiring a tool table, or stopping for manual toolchange, on the first M6 T1. If

Re: [Emc-users] Toolchange M6

2016-04-16 Thread Gene Heskett
On Saturday 16 April 2016 14:11:07 Danny Miller wrote: > I am setting up a manual toolchange CNC router system. In the past > I've worked extensively with Mach3. > > Someone just brought up g-code from an automated CAM that started with > "M6 T1", and it barfed on loading because "T1 isn't a

Re: [Emc-users] Toolchange M6

2016-04-16 Thread andy pugh
On 16 April 2016 at 22:59, Greg Bentzinger wrote: > Just because you got away with bad habits when using Mach 3 is no excuse not > to learn proper methods. If this machine uses collets and has no way to achieve a reproducible tool height then I think that making every tool

Re: [Emc-users] Toolchange M6

2016-04-16 Thread Greg Bentzinger
Henry Ford saw no reason to ever make a different car than the Model T. The fact that the Model A came about was mostly done behind his back and when ready presented to him as fate accompli. Just because you got away with bad habits when using Mach 3 is no excuse not to learn proper methods.

Re: [Emc-users] Toolchange M6

2016-04-16 Thread John Murphy
zero without complaint but that could be a PathPilot change. > >> -Original Message- >> From: Danny Miller [mailto:dan...@austin.rr.com] >> Sent: Saturday, April 16, 2016 2:11 PM >> To: 'Enhanced Machine Controller (EMC)' >> Subject: [Emc-users] Toolchange M6 >>

Re: [Emc-users] Toolchange M6

2016-04-16 Thread Danny Miller
What does this do, just skip toolchanges and state it's changed? Problem being, if you have a file which changes tools, there will be no opportunity to do so. The machine won't stop, right? The machine will have many users, I should mention that. Quirks on how to set up files, I can

Re: [Emc-users] Toolchange M6

2016-04-16 Thread Tomas Jarmolaitis
> I am setting up a manual toolchange CNC router system. In the past > I've worked extensively with Mach3. > Maybe you just need few lines in hal file: net tool-number <= iocontrol.0.tool-prep-number net tool-change-loopback iocontrol.0.tool-change => iocontrol.0.tool-changed net

Re: [Emc-users] Toolchange M6

2016-04-16 Thread Ken Strauss
allow multiple tools in a single file. Also, all tool table fields can be zero without complaint but that could be a PathPilot change. > -Original Message- > From: Danny Miller [mailto:dan...@austin.rr.com] > Sent: Saturday, April 16, 2016 2:11 PM > To: 'Enhanced Machine Control

Re: [Emc-users] Toolchange M6

2016-04-16 Thread andy pugh
On 16 April 2016 at 19:11, Danny Miller wrote: > I see there's the "hal_manualtoolchange" component which seems like it > would fix this. Is that the logical answer? Can I ditch the tool table? hal_manualtoolchange is intended to convert the operator into a tool-changing

[Emc-users] Toolchange M6

2016-04-16 Thread Danny Miller
I am setting up a manual toolchange CNC router system. In the past I've worked extensively with Mach3. Someone just brought up g-code from an automated CAM that started with "M6 T1", and it barfed on loading because "T1 isn't a defined tool in the tool table". This was the one and only tool