Greg,
FYI, the concept of the Comet is that 1/2 of the board is populated on each table. This is in an effort to reduce the total transfer time hit per board. The on machine optimizer should be able to handle the split of the program. If you need to balance the program across the two tables, then multiply the feeders in the optimizer.
BTW, I assume that the reason you want to do this is to 'balance' the placement cycle time between front and rear, but in fact one table (can't remember which) will be slower because of the pick to vision to table distance will be longer on one table.
Greg
reply »