Having recently built my first repstrap based on a Prusa Mendel i2, I am now keen to explore an alternative arrangement for X and Y axes that will hopefully offer some advantages over the original. This experiment will involve radically different equations for the X and Y movement. One approach I am considering is to retain my entire existing reprap and just mount the alternative bed on top of it's bed. I will loose some Z capacity but it will be fine to test the concept. Doing it this way, I would only need to buy two more steppers and simply swap the connections on the RAMPS for X and Y to do the testing (possibly using 4 way switches). It would avoid the need to duplicate the rest of the hardware and I could readily revert to the original configuration as needed. My question is - what is the best approach for coding?: customising the firmware or post processing the G-code? My new X-Y scheme will be computationally intensive so it may be a stretch to process it on Arduino in firmware. I haven't even looked at what would be involved in changing the firmware so forgive me if this sounds daft. Post processing the G-Code would allow me to revert to the PM i2 without having to also revert the firmware. I am leaning towards post processing G code so that the firmware can remain unchanged. Any thoughts and guidance would be appreciated. Neil https://reprap.org/forum/read.php?147,298795,298795#msg-298795 Sat, 10 Oct 2026 19:48:40 -0400 Phorum 5.2.23 https://reprap.org/forum/read.php?147,298795,317999#msg-317999 https://reprap.org/forum/read.php?147,298795,317999#msg-317999 APrinter firmware runs on quite a few ARM based boards (Arduino Due, 4pi, Teensy 3), and it supports custom transforms.]]> ambrop7 Firmware - experimental, borrowed, and future Sat, 01 Mar 2014 08:39:30 -0500 https://reprap.org/forum/read.php?147,298795,315852#msg-315852 https://reprap.org/forum/read.php?147,298795,315852#msg-315852 You could as well find all the #define DELTA and swap out the functions.]]> sam0737 Firmware - experimental, borrowed, and future Tue, 25 Feb 2014 08:42:16 -0500 https://reprap.org/forum/read.php?147,298795,299023#msg-299023 https://reprap.org/forum/read.php?147,298795,299023#msg-299023
Anything run on the arduino is done in real time as you are printing. G code post processing is done ahead of time. If you have a choice of which way to go, I'd lot for the latter.]]> jbernardis Firmware - experimental, borrowed, and future Wed, 22 Jan 2014 01:35:56 -0500 https://reprap.org/forum/read.php?147,298795,298795#msg-298795 https://reprap.org/forum/read.php?147,298795,298795#msg-298795
One approach I am considering is to retain my entire existing reprap and just mount the alternative bed on top of it's bed. I will loose some Z capacity but it will be fine to test the concept. Doing it this way, I would only need to buy two more steppers and simply swap the connections on the RAMPS for X and Y to do the testing (possibly using 4 way switches). It would avoid the need to duplicate the rest of the hardware and I could readily revert to the original configuration as needed.

My question is - what is the best approach for coding?: customising the firmware or post processing the G-code? My new X-Y scheme will be computationally intensive so it may be a stretch to process it on Arduino in firmware. I haven't even looked at what would be involved in changing the firmware so forgive me if this sounds daft. Post processing the G-Code would allow me to revert to the PM i2 without having to also revert the firmware. I am leaning towards post processing G code so that the firmware can remain unchanged. Any thoughts and guidance would be appreciated.

Neil]]> n.glasson Firmware - experimental, borrowed, and future Tue, 21 Jan 2014 15:22:03 -0500