| The Shop > CNC |
| DDCSV1.1 4 Axis controller |
| << < (100/202) > >> |
| awemawson:
Are there enough outputs that you could clock values into an external register set to expand the outputs? (This was pretty well standard practise in the early days when the number of pins on a chip were the limiting factor) |
| librarymark:
it's got 4 axis' worth of IO - seems to me that you could hook up 4 stepper drivers and slave two of them in software, but I don't even have one of these yet, so I don't know squat. |
| Joules:
The X output is quite capable of running two stepper controllers. My old router had 2 X-axis motors each with its own driver module driven from the X-axis signals. |
| librarymark:
--- Quote from: Joules on March 17, 2017, 03:34:52 PM ---The X output is quite capable of running two stepper controllers. My old router had 2 X-axis motors each with its own driver module driven from the X-axis signals. --- End quote --- OK - I will try that - thanks! |
| Benedikt:
--- Quote from: Joules on March 17, 2017, 03:34:52 PM ---The X output is quite capable of running two stepper controllers. My old router had 2 X-axis motors each with its own driver module driven from the X-axis signals. --- End quote --- This is essentially how I am driving my Y axis and I had no issues so far. --- Quote from: librarymark on March 17, 2017, 02:23:23 PM ---it's got 4 axis' worth of IO - seems to me that you could hook up 4 stepper drivers and slave two of them in software, but I don't even have one of these yet, so I don't know squat. --- End quote --- While this sounds nice, bear in mind the FPGA is handling a lot of the actual drive work. That said, it's most likely just writing a number of steps to go for each axis into an FPGA register. Controlling any of the axis ports in an arbitrary way (using them as IO) is not possible. However, there is a serial port on the outside. Does anyone know what it does? What I would want to do is write a driver similar to the motiondev.ko driver that sits in between the application and the actual driver and just records what is sent and might also be able to write data into the stream. I will eventually research this further. This might make reverse-engineering the firmware itself a lot easier, since it opens up some debug capabilities. |
| Navigation |
| Message Index |
| Next page |
| Previous page |