Reprap32 -- 32Bit Reprap control based on AVR32
Description
It is a functional replacement for the Gen4 Aruduino mega and it's motherboard. The code has been ported to AVR32 GCC from Makerbot G3 branch (the V2 code),
Status: As of OCT 8th, 2011
The atmel CDC driver for USB is now running on the hardware with terminal emulators. The next step is to port it into tha main REPRAP32 application. I will probably try a USB branch on the main git repository. I have not yet published a branch and need to learn how to do it correctly.
I have some bare stepstick PCBs in hand now. So I can build a full stepstick based prusia with USB reprap32 for my daughter at college.
I checked the loading of the 64us stepper timer interrupt to see how much cpu time the steppers are using. I found 22% nominal and 36% worst case. This leaves 53 DMips of cpu still available.
I was able to drive the Gen3 stepper drivers on my Prusa with no issues. Just a cable slide from 10 pin to 6 pin IDC. I did not even change any settings in ReplicatorG!!! it just works.
Most of my issues were related to pin assignments and not having end stops
Properly terminated. They are now disconnected in the software build.
check out sites.google.com/site/reprap32
Instructions
github link github.com/daveland/reprap32
I still need to make a part list (BOM) and some other documentation.
Contributors to this project are Welcome!!! If you have something to add let me know. I work way too slowly so help is always appreciated.
You must be logged in to post a comment.
Davelandia - I just happened to stumble upon this - I've actually got the AT32UC3C1512C that I'm implementing for a 32 bit controller. This puppy has on board CAN, Ethernet, USB 2.0 as well as a FPU. My purpose is to expand the featureset available on board but also to implement new GCode maneuvers such as Arc that are computationally intensive and require a significant amount of precision. This will allow for true curves as opposed to tangental linear movements of the print head. What's more is that I also want to get this beast connected online by ethernet.
How far along are you with porting over some firmware?
Hi.. I was looking at the UC3C series, But could not find any stock in Febuary when I began the design. But I was hoping to port to it once the chips came out.
I have ported the Makerbot V2 firmware. Replicator-g connects and I am debugging the toolhead uart. I hope to have my re-rap running on it in a couple of weeks. I only get time on weekends and hurricanes/snowstorms so it is going slowly.
:-D
What is the benefits of going 32bit?
Speed mainly. as you move to shorter line segments, acceleration, and constant velocity around corners, you require more calculation power. 32bit cpus are now capable of doing 32 /64 bit math in single instructions. This allows more moves per second.
Native USB control is embedded as well. plus I think that I can emulate two toolheads with PID loops and speed control. All this fits on one 3"X4" card that you can assemble yourself..
Of course I have to get all this working... ;)
Nice to see the movement to 32 bits. If this also means that silly serial bottleneck is eliminated then it is all for the better.
Your choice of atx power supply is a bit conservative, IMHO. Maybe 12V is sufficient for slow machines, but ultimately you will want your machine to be faster. With the same stepper motors, that means you need a higher voltage.
How many steppers can it run maximum? I need something that will run 7 at a minimum.
I have pins for 5 steppers x,y,z and two stepper extruders. What would you want to use the others for? hexapod style robot?
I see XYZAB, so I think it can do 5. Why would you need 7 of them?
Anyway, if this uC has CANBUS on board (and canbus is broken out), you could use that to control extra steppers, but you'd need to modify the software for it and find a suitable can-stepper driver.
License
More from davelandia
Reprap32 Now Prints!!! I made the first pair of test cubes this evening. I found that I could use the Gen3 stepper drivers with just a cable offset. No changes to ReplicatorG were required. It printed really well. Now on to unfinished things, EEPROM , config Settings, and Stress testing.
:-D