I'm working with Pavel on handling Tx and M6 by executing O-word subroutines to do the actual pin wiggling, moves and so forth. It's not yet usable, but not that far off either. I imagine this will be an option and traditional handling through iocontrol will stay in place unless configure otherwise, at least for the time being.
I envisage current M6 handling be renamed to an unused M6x code, so the o-word M6 could still refer to it if needed. This poses the question how M6x toolchanger faults would be handled in g-code. As it stands now in my iocontrol-v2-candidate branch, all toolchanger faults cause an abort of the current program, including the calling M6-oword sub. This makes it impossible to handle tool changer faults in gcode. I'm thinking about an alternative way of handling this, similar to the G38.x probe command. G38 has variants to either abort on probe failure (no contact), or alternatively just setting a parameter flag (5070) which signals success or failure, and the G38 command does not abort. The way this would work: - negative toolchanger fault codes would continue to abort at the M6x as if hitting Escape in Axis. - positive fault codes would just 'complete' the M6x and set a #5xxx parameter to signal success/failure and another #5yyy parameter to access the fault code. 'complete' means the program continues to run, it does NOT mean the toolchange completed. It would be the programmers responsibility to check the #5xxx flag wrt success or failure of the tool change and go from there. entertaining opinions, -Michael ------------------------------------------------------------------------------ Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
