as part of my code safari through EMC, I've arrived at the point where the 
tooltable mechanism looks like it needs redesign.

As part of that effort, I roughly plan:

- move the tooltable mechanism to the interpreter, and remove the limitations 
which come from NML message size limits
- to replace the current table by an abstract data type (class) which has an 
sqlite3 database underneath, and a normalized data model without data 
dependencies ("magic pocket 0" for the random TC, for instance)
- to model the prepare, change and other operations by configurable SQL scripts 
which encapsulate the semantics of the changer-specific operations and thus 
better support different change strategies
- cut down on/remove changer-specific code (like "if (random_toolchange)" etc)
- iocontrol will, for the rest of its lifespan, be only an output mechanism for 
the current tool and its data but not involved in storage or manipulation of 
tool data per se any more


At this point I'm trying to figure the data model. I do not plan to change the 
support at the G-code level, but probably extend it by "insert tool into 
changer at pocket", and "remove tool from changer" type operations

I had a question from a local integrator about "poor support for multiple 
spindle machines" in EMC and I'm still trying to figure what that means, and 
wether the tool handling mechanism needs to take care of that.

Does it make any sense to:
- support more than one spindle?
- support more than one tool changer (maybe bound to a spindle)?

Any other suggestions which might make sense addressing at this point?

-Michael
------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network 
management toolset available today.  Delivers lowest initial 
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers

Reply via email to