CNC 10 v1.51 with Yuasa UDNC-M1 indexer
Moderator: cnckeith
-
- Posts: 26
- Joined: Sun Jan 29, 2023 12:13 am
- Acorn CNC Controller: No
- Allin1DC CNC Controller: No
- Oak CNC controller: No
- CNC Control System Serial Number: 20551
- DC3IOB: No
- CNC12: No
- CNC11: No
- CPU10 or CPU7: Yes
CNC 10 v1.51 with Yuasa UDNC-M1 indexer
So I purchased a Bridgeport Series 1 CNC mill w a Centroid CNC 10 4 axis retrofit. I have been trying to find some info/ manuals for the indexer. The Yuasa controller is a UDNC-M1. The actual indexer has no visible id tags or model numbers. Does anyone have info on these items?
Re: CNC 10 v1.51 with Yuasa UDNC-M1 indexer
That would technically be a 3-axis CNC, with an M-function indexer. Rotary angles are programmed into the Yuasa control.
Most commonly, the Centroid installer will set up an "M12" macro on the Centroid control that triggers the Yuasa indexer to move to its next position.
Most commonly, the Centroid installer will set up an "M12" macro on the Centroid control that triggers the Yuasa indexer to move to its next position.
-
- Posts: 26
- Joined: Sun Jan 29, 2023 12:13 am
- Acorn CNC Controller: No
- Allin1DC CNC Controller: No
- Oak CNC controller: No
- CNC Control System Serial Number: 20551
- DC3IOB: No
- CNC12: No
- CNC11: No
- CPU10 or CPU7: Yes
Re: CNC 10 v1.51 with Yuasa UDNC-M1 indexer
Thanks for the info. So if it just feeding angles thru M codes, would it be possible to do helical milling with it?
Re: CNC 10 v1.51 with Yuasa UDNC-M1 indexer
The typical indexing macro would trigger the indexer to start, then wait until the indexer reports completion before proceeding on to the next line of the CNC program.
You could, of course, write an alternate code or macro that triggers the indexer, but does not wait for completion. Then the next line of your CNC program would begin running while the indexer was running.
However, there would be no coordination. You could not guarantee that both moves would start at the same instant; and if you turned the feedrate override up or down on either controller (Yuasa and/or Centroid), the other controller could not know or compensate. So helical milling would be clumsy, at best.
You could, of course, write an alternate code or macro that triggers the indexer, but does not wait for completion. Then the next line of your CNC program would begin running while the indexer was running.
However, there would be no coordination. You could not guarantee that both moves would start at the same instant; and if you turned the feedrate override up or down on either controller (Yuasa and/or Centroid), the other controller could not know or compensate. So helical milling would be clumsy, at best.