Hi
The additional libraries for the RepRap Firmware are here:
[github.com]
I will ask Adrian to update the readme.
The main reason the pins handling as it is is because not all SAM3X8E pins are defined on the Arduino (or arduino defines them as a simple digital pin and does not expose the required peripheral function eg PWM). In the future we might combine them all into one replacement variant library. Once we discovered that we wanted to use pins that were not in the Arduino Due variant definition this was the best way to go as a start point.
The arguments that apply to all in one boards vs RAMPS/Sanguinololu boards with chip carriers apply and there are advantages and disadvantages to both. The good thing about basing it on the Due is that the firmware development on projects such as the RAMPS-FD can complement each other with the same base platform.
If you want to use the Ethernet part in a Due platform then there are 3rd party Due variants that expose the ethernet pins.
Cheers
Tony
blog.think3dprint3d.com
The additional libraries for the RepRap Firmware are here:
[github.com]
I will ask Adrian to update the readme.
The main reason the pins handling as it is is because not all SAM3X8E pins are defined on the Arduino (or arduino defines them as a simple digital pin and does not expose the required peripheral function eg PWM). In the future we might combine them all into one replacement variant library. Once we discovered that we wanted to use pins that were not in the Arduino Due variant definition this was the best way to go as a start point.
The arguments that apply to all in one boards vs RAMPS/Sanguinololu boards with chip carriers apply and there are advantages and disadvantages to both. The good thing about basing it on the Due is that the firmware development on projects such as the RAMPS-FD can complement each other with the same base platform.
If you want to use the Ethernet part in a Due platform then there are 3rd party Due variants that expose the ethernet pins.
Cheers
Tony
blog.think3dprint3d.com