Thor, or should that be Zeus?

[Chaz]

So many options.

http://uk.rs-online.com/web/c/automa...sort-order=asc

Id probably consider the ones like this (http://uk.rs-online.com/web/p/limit-switches/0199046/) or similar.

Panasonic, so not cheap crap. NC, Easy to mount, should work for me but I dont really want to buy 6 if I can avoid it.

[Desertboy]

So many options.

http://uk.rs-online.com/web/c/automa...sort-order=asc

Id probably consider the ones like this (http://uk.rs-online.com/web/p/limit-switches/0199046/) or similar.

Panasonic, so not cheap crap. NC, Easy to mount, should work for me but I dont really want to buy 6 if I can avoid it.

You're paying for the IP rating mostly if you're not running liquid coolant I would be happy with Cherry or Happ microswitches simply because arcades have used them since the 80's pretty much unchanged design and they have proven themselves to be ultra reliable over a long time and arcade machines were abused! They are certainly not suitable if your cutting under running liquid but they are so cheap 6 would cost the same as 1 panasonic and although the panasonic might be better the happ's or cherry's have certainly had a lot lot more real world testing as almost every arcade machine, including gamblers in the 80's, 90's, 00's and even today had/have either happ or cherry switches

[Chaz]

You're paying for the IP rating mostly if you're not running liquid coolant I would be happy with Cherry or Happ microswitches simply because arcades have used them since the 80's pretty much unchanged design and they have proven themselves to be ultra reliable over a long time and arcade machines were abused! They are certainly not suitable if your cutting under running liquid.

True. At the moment I'm not sure if Ill be using coolants. Ive been thinking to get some form of metal / material bellows system in place, id be more comfortable to have them IP Rated, just in case. Suppose in the overall costs of the machine, paying £50 for switches is not really an issue.

[Chaz]

Ok, fundamental question.

Is it normal or acceptable to use the same switch (mechanical or proxy) for both home and limit? I dont understand how the machine would know if it was simply sent home or it actually needs to stop as its a limit. Is there logic that says 'ref all' and it goes home but if its hits the home limit during any other movement (manual or programmed) that the machine will then stop?

[Desertboy]

Ok, fundamental question.

Is it normal or acceptable to use the same switch (mechanical or proxy) for both home and limit? I dont understand how the machine would know if it was simply sent home or it actually needs to stop as its a limit. Is there logic that says 'ref all' and it goes home but if its hits the home limit during any other movement (manual or programmed) that the machine will then stop?

I know how it works on grbl (Arduino cnc solution) when it's doing a home it ignores the limit so doesn't go into shutdown mode. If it's not homing then it treats it as a limit switch and shuts everything down until reset G code is sent.

I'm sure Mach 3 treats it the same way (I think LinuxCNC does)

If I were you though I would fit another set of limit switch further back that trigger an E stop as well as extra protection! I can maybe help you source high quality IP64 rated microswitches I have a friend who services and repairs 4 poster lifting ramps for steam cleaning bays I'll give him a bell see how much he would charge for new ones if they're cheap enough I'll use them lol.

[Clive S]

Ok, fundamental question.

Is it normal or acceptable to use the same switch (mechanical or proxy) for both home and limit? I dont understand how the machine would know if it was simply sent home or it actually needs to stop as its a limit. Is there logic that says 'ref all' and it goes home but if its hits the home limit during any other movement (manual or programmed) that the machine will then stop?

Chaz I think you are getting bogged down with all this. When you home the machine the software knows that you are homing and therefore treats the switches as (homes) when the machine has homed the software then treats the switches as limits.

In your case you will have plenty on inputs so why not keep them separate. (it is also OK to use just one switch for home and one end limit)

[AndrewMawson]

I agree with Clive in his post above (Hi Clive !)

However my personal preference on big powerful machines is to have the home switches inside the boundries set by the limit switches, and have the limit switches trigger powering off of the drives. Also to have the limit switches within the boundries of mechanical stops that limit travel before ball screws over travel.

With a big servo driven machine like my CNC Beaver Partsmaster Mill, or the Traub lathe I rebuilt last year (now sold), the servo drives are a few killowatts, so if they run away damage WILL be done without limits.

However that said, my CNC Plasma Table is set up sharing home and limit switches driven by Mach3 - it's how the chap who originally built it made it, and it wasn't easily altered when I re-built it. But the drives are steppers and only Nema 46's so in the worst case if it runs away not much breaks !

[Chaz]

Chaz I think you are getting bogged down with all this. When you home the machine the software knows that you are homing and therefore treats the switches as (homes) when the machine has homed the software then treats the switches as limits.

In your case you will have plenty on inputs so why not keep them separate. (it is also OK to use just one switch for home and one end limit)

Thanks. The penny dropped, just never knew this before.

[Neale]

Clive has just answered the home/limit question - Mach3 knows what you are doing so treats the switch inputs accordingly. There is a minor gotcha with this. If you use a switch with effectively no offset between on and off positions, you can get problems (to be more accurate, I had problems) with this. Z homed, then X and Y started moving. The Z switch had swapped from homing to limit function, and the slight vibration caused the Z switch to trip and stop the machine ("limit switch event"). Fortunately, the IP/M has the capability to move the axis very slightly away from the home position immediately after homing which fixed the problem.

The limit on number of inputs only applies if you are using a parallel port. That statement on the Mach3 config page is a bit misleading. There are only five input pins on a parallel port as all the others are output only, so the limit is a physical one and nothing to do with Mach3. You will be fine with the IP/A and are free to use all the ports. I doubled up my switches (combined upper and lower) mainly to reduce the number of wires needed and I still have some unused inputs on the IP/M.

Don't worry about voltages. Desertboy was talking about Arduinos and they are definitely 5V only. The IP/A will be very happy with 24V signalling, and in fact this gives much better noise rejection. The CSMIO kit is built to use the industry standard 24V signalling. No pull-up/pull-down resistors needed, but watch the wiring instuctions carefully so that you get it right. Less flexible motion controllers only have one input pin but there are two per channel on the IP/A. There are plenty of examples of how to wire NPN n/c proximity switches in series if you do a Google search - I have had four in series working reliably in testing although in practice I only wire them in pairs on my machine.

[Chaz]

Clive has just answered the home/limit question - Mach3 knows what you are doing so treats the switch inputs accordingly. There is a minor gotcha with this. If you use a switch with effectively no offset between on and off positions, you can get problems (to be more accurate, I had problems) with this. Z homed, then X and Y started moving. The Z switch had swapped from homing to limit function, and the slight vibration caused the Z switch to trip and stop the machine ("limit switch event"). Fortunately, the IP/M has the capability to move the axis very slightly away from the home position immediately after homing which fixed the problem.

The limit on number of inputs only applies if you are using a parallel port. That statement on the Mach3 config page is a bit misleading. There are only five input pins on a parallel port as all the others are output only, so the limit is a physical one and nothing to do with Mach3. You will be fine with the IP/A and are free to use all the ports. I doubled up my switches (combined upper and lower) mainly to reduce the number of wires needed and I still have some unused inputs on the IP/M.

Don't worry about voltages. Desertboy was talking about Arduinos and they are definitely 5V only. The IP/A will be very happy with 24V signalling, and in fact this gives much better noise rejection. The CSMIO kit is built to use the industry standard 24V signalling. No pull-up/pull-down resistors needed, but watch the wiring instuctions carefully so that you get it right. Less flexible motion controllers only have one input pin but there are two per channel on the IP/A. There are plenty of examples of how to wire NPN n/c proximity switches in series if you do a Google search - I have had four in series working reliably in testing although in practice I only wire them in pairs on my machine.

Awesome, thanks.

Suppose now I need to decide if its proxy and mech or only proxy. I could do mech as primary home / limit and proxy as limits via E Stop circuit.