Currently my lack in confidence at maintaining an accurate home is bringing me very close to abandoning Mach. This is because e-stop and Limit events are very common, and after which Mach requires re-homing.
1) Continuous absolute feedback. (Many (most all?) modern professional systems do this)
Homing mechanism: n/a
Mach doesn't currently support any of these options. I'm not putting Mach in catagory #3 because because #3 systems have been around for at least 10+ years (pretty sure 30+ years). AHHA systems, for example, don't loose home with e-stop or limit events. Now that I think about it, from my experience, Mach is the ONLY system I've seen with the capability to control professional systems that DOES require homing after an e-stop or limit event.
Currently my lack in confidence at maintaining an accurate home is bringing me very close to abandoning Mach. This is because e-stop and Limit events are very common, and after which Mach requires re-homing.
Requirement: The only time a CAM system (without absolute positioning) should require homing is at power up, after a motor drive failure, or when the operator decides it's necessary (after a crash).
Also, for servo systems, an uncontrolled e-stop is downright unsafe. I made a custom 1800IPM gantry system for a client this year using a National Instruments motion card, servomotors and Gecko G340 drivers. Controlled motion on e-stop and soft limit events were a requirement. Suddenly stopping the pulse stream resulted in a drive error/shut-down allowing the carriage to freewheel and do (more) damage. (I wrote my own g-code CAM software in LabView for this project - - a far cry from Mach in features but not bad, I think).
Ok so your typical home-build machine doesn’t do 1800IPM. But the speeds are getting to the point where controlled stops are going to be an important requirement (especially w/ the G100).
However, the Trak system at one of my clients never requires homing, and both a friend’s AHHA system as well as his modern Akira-Seki VMC don't require homing after e-stop or limit events.
Naturally, Improved confidence in my homing repeatability will help for safety as I'd rather not second guess the ramifications of hitting the e-stop.
And, yes. I do occasionally jog in the wrong direction and hit the limits as my tool change position is at machine 0,0,0
Also, for servo systems, an uncontrolled e-stop is downright unsafe. I made a custom 1800IPM gantry system for a client this year using a National Instruments motion card, servomotors and Gecko G340 drivers. Controlled motion on e-stop and soft limit events were a requirement. Suddenly stopping the pulse stream resulted in a drive error/shut-down allowing the carriage to freewheel and do (more) damage. (I wrote my own g-code CAM software in LabView for this project - - a far cry from Mach in features but not bad, I think).
Why can’t the index pulse of an encoder be fed in as a Mach home switch?
Right, the roigersmachine error detection board is a great idea for a stepper system with encoder or glass scale feedback.
Why can’t the index pulse of an encoder be fed in as a Mach home switch?
Does anyone know if Mach's encoder DROs are consistent across e-stops and limit events?
Does anyone know if Mach's encoder DROs are consistent across e-stops and limit events?
QuoteAlso, for servo systems, an uncontrolled e-stop is downright unsafe. I made a custom 1800IPM gantry system for a client this year using a National Instruments motion card, servomotors and Gecko G340 drivers. Controlled motion on e-stop and soft limit events were a requirement. Suddenly stopping the pulse stream resulted in a drive error/shut-down allowing the carriage to freewheel and do (more) damage. (I wrote my own g-code CAM software in LabView for this project - - a far cry from Mach in features but not bad, I think).
Ok so your typical home-build machine doesn’t do 1800IPM. But the speeds are getting to the point where controlled stops are going to be an important requirement (especially w/ the G100).
I think most controll the motion on e-stops and limits by using enable pins to fault or disable the drives.
...
Brett
...Take a look at the G100 and Galil motion control boards if you have needs that go beyond what a few parallel ports will do.
To be accurate the the controller needs to see the edge of the index pulse, (edge triggerd). There is no guarantee that all parallel port inputs will latch at the same time so trying to edge trigger on a fast signal, w.r.t another input would be at best, tough.
From what I am reading that you wrote, I dont think the homing accurcy is your complaint. I think what you want is after a crash/E-stop condition, you want to be able to restart the program from where the problem occured without losing your position. You could re-home, BUT, for what you want, you would need to have "Absolute" Encouders.
I'm not certain if the encoder dros are consistent across an e-stop. I wouldn't think so. Maybe someone else will reply with this info.
Does anyone know if the encoder DRO's are consistent across error/reset events?
QuoteDoes anyone know if the encoder DRO's are consistent across error/reset events?
Ted,
I will find out the definitive answer ASAP and let you know.
Brett
Is it possible to enter numbers in Mach 3 using the keyboard's number keys?
Peabody distinguishes between a safe stop and an e-stop. A safe stop allows a machine to return to a known position from which it can commence working without an elaborate reset process. An e-stop removes power to the machine immediately, stopping it but possibly scrambling programs. After an e-stop, a machine needs time to gather its wits.
With robots, an operator can push a safe stop button and a locked perimeter guarding will remain that way until the robot has come to a controlled stop. Only then will the guard unlock.
I think my oldest son said it best" POP, If you build your machine and program your code to the same level of accuracy and dependability that you WANT the software to maintain then you will rarely have trouble(;-) "I get E-stop occasionally from the safety swing open perspex guard on my Super X3. I don't lose position. It only happens when I am changing a tool when not moving. No problems resuming, nothing lost. But we cannot assume microstepping is not screwed if power to stepper system goes off. If the E-stop just stops the drives without killing their brains, then there should be no problem, else reference it again. My limit (read reference) switches are optics, and resolve position edge to within the same narrow (1 step (not microstep) on the stepper I think) and repeatbility is excelent. Tight window on refence switch edge is important. Mach3 seems to get it right.
The Estop and limits are there for a last measure to HELP prevent damage to the operator and machine not save your project from disaster
ANY time you estop or limit stop a machine, and it does not matter WHO made it, you should reference it back to home to verify that it is still accurate.
If you are running into situations that require constant estops then you need to whack the programer in the head(;-). If you are constantly hitting the limits then you need to whack the operator in the head(;-)
There IS a SOFTLIMITS you can set up that will HELP prevent the limit crashes. Heck it will even show you the softlimit boundary on the screen when you load the code. If your part goes outside the limits the operator should see it. Can't ask too much more from Mach(;-)
HUM i'll have to test the estop and limits to see if MACH really looses position. I know I have estopped and resumed without loss of position. I don't recall having tested the limits situation.
(;-) TP
i used to program in CThen it's like you used to fly jet fighters and now you're about to learn how to flap your arms (but with one of them tied behind your back) - you'll be fine.
About jet fighters, unfortunately(?) it's not the language that make the program ! and a precise idea of what you want to do + a good knowledge of what can be done may compensate a n heavy syntax also our computers are very fast now so i think we can handle it.I stand corrected - sorry for my attempt at encouragement by way of a little joke...
I also meet guy who where programming in c VERY inefficiently !
And since some manage to do it so i can do it too(hopefully)