Newbie needs some help...

I recently bought a Lulzbot prusa off of ebay listed as a project. i figured a good way to start was one that was almost ready to go. However i am really struggling with the software and how to install it. I follow the instructions but i must be missing something. ive tried it on vista, and windows 7.
I have a mchine shop, and im very familar with gcode, but this open source software is new to me..

Other questions...
1. How do we tell which ardunio module we have?
2. Is there a step by step (dummy proof) tutorial that shows how to do it?

Thanks in advance for any help, sorry if i posted this in the wrong section, i have been reading your forums and im very excited for this resource.
legion

Do you know what electronics you have? Whether Sanguino, Ramps, Gen6 etc. I use Skeinforge for Windows and Repsnapper and have used Pronterface too all on Windows XP and Windows 7.

When you install skeinforge you need to find the skeinforge.py and double click it to launch skienforge, I right clicked it and sent it to the desktop as a shortcut

---

__________________________________________________________________________
Experimenting in 3D in New Zealand

apparently its a ardunino mega 2560

OK I don't know anything about the mega as I use Sanguino and Gen6 on the 2 machines I have

---

__________________________________________________________________________
Experimenting in 3D in New Zealand

It's probably RAMPS. Go to the RAMPS wiki to help in identifying what version you have.

Hey, you have a RAMPS board.

You DO NOT have to configure anything with Arduino nor flash the firmware, as that is already done and it is calibrated for your printer.

You just need to install printrun to send files to the printer:

printrun is [github.com] and precompiled for windows (without sfact) at [koti.kapsi.fi] & precompiled for OSX (without sfact) at [koti.kapsi.fi]

You can use slic3r to make .gcode files from .stl files (such as found on thingiverse). See:
[www.slic3r.org]

Have fun,

-Jeff moe

Hey jebba, thanks so much for the help, that got it running right away.

I am also very confused with the software side of things. I have my entire reprap assembled, and right now I'm stumped over electronics. I have downloaded pronterface and skeinforge to my computer and successfully created g-codes with them. My main issue is understanding how to load the firmware onto my reprap. I also have no idea which firmware I need or what it does exactly. I am looking for firmware that at least uses acceleration and is compatible with pronterface. I have a RAMPS 1.4 board with a chipKIT Max32 arduino clone. I have been searching for this for a while now, and most of what I find includes a lot of tech language that I honestly don't understand. If someone could at least tell me which firmware to get and point me in the direction of a good tutorial that would be greatly appreciated

Thank you!
Quentin

@Quentin.T

Download the software from here. Once you load the software its pretty straight forward from there.

---

My Reprap blog

jds-reprap.blogspot.com

Quentin...getting firmware loaded had me stumped for a while, and I'm an EE with 27 years experience, so don't feel bad.

I looked up the chipkit max32, and it's a pretty cool board. However, I haven't run across anyone else using it, so you will have some trailblazing to do if you stick with it. The architecture of the chip is different than the Atmel AVR series that people normally use.

I recommend you get an arduino mega 2560 or direct clone of that. Sprinter is a good firmware; you'll need to edit Configuration.h, and possibly the Makefile. Most people compile the code (oddly called 'sketch' in arduino-talk) using the arduino IDE(that's the link Joe provided), though I used avr-gcc, make, and avrdude under Linux instead. Maybe there is a comprehensive tutorial somewhere, but I didn't run across one--just scattered pieces of information. Good luck, and keep asking questions here, the more specific the better.

(edit: removed stuff about isp's and fuses; that should only come into play if you build up a bare board.)

Edited 1 time(s). Last edit at 01/24/2012 09:54PM by RobertB.

I was able to find kliment's sprinter firmware. I compiled it for my board in an environment very similar to the arduino compiler. After compiling, it gave me a whole bunch of errors, but all of them were related to the sd card option that I don't plan on using. Is it possible for me to tell the firmware not to compile that portion of the code since I am not using it? or is there a portion of the sd card code that is important regardless of if you are using the SD card? Below is the error message that comes up

Thanks for the help everyone
Quentin




In file included from /Sd2PinMap.h:23:0,
from /Sd2Card.h:26,
from Sd2Card.cpp:21:
c:\documents and settings\quentin\desktop\mpide-0023-windows-20111221\mpide-0023-windows-20111221\hardware\pic32\compiler\pic32-tools\bin\../lib/gcc/pic32mx/4.5.1/../../../../pic32mx/include/avr/io.h:4:2: error: #error ******** This sketch or library uses AVR-specific code that may not work with the chipKIT platform. See this forum for more information on porting code to chipKIT [www.chipkit.org/forum/viewforum.php?f=7] ********
In file included from /Sd2Card.h:26:0,
from Sd2Card.cpp:21:
/Sd2PinMap.h:285:5: error: 'DDRD' was not declared in this scope
/Sd2PinMap.h:285:12: error: 'PIND' was not declared in this scope
/Sd2PinMap.h:286:5: error: 'DDRD' was not declared in this scope
/Sd2PinMap.h:286:12: error: 'PIND' was not declared in this scope
/Sd2PinMap.h:287:5: error: 'DDRD' was not declared in this scope
/Sd2PinMap.h:287:12: error: 'PIND' was not declared in this scope
/Sd2PinMap.h:288:5: error: 'DDRD' was not declared in this scope
/Sd2PinMap.h:288:12: error: 'PIND' was not declared in this scope
/Sd2PinMap.h:289:5: error: 'DDRD' was not declared in this scope
/Sd2PinMap.h:289:12: error: 'PIND' was not declared in this scope
/Sd2PinMap.h:290:5: error: 'DDRD' was not declared in this scope
/Sd2PinMap.h:290:12: error: 'PIND' was not declared in this scope
/Sd2PinMap.h:291:5: error: 'DDRD' was not declared in this scope
/Sd2PinMap.h:291:12: error: 'PIND' was not declared in this scope
/Sd2PinMap.h:292:5: error: 'DDRD' was not declared in this scope
/Sd2PinMap.h:292:12: error: 'PIND' was not declared in this scope
/Sd2PinMap.h:293:5: error: 'DDRB' was not declared in this scope
/Sd2PinMap.h:293:12: error: 'PINB' was not declared in this scope
/Sd2PinMap.h:294:5: error: 'DDRB' was not declared in this scope
/Sd2PinMap.h:294:12: error: 'PINB' was not declared in this scope
/Sd2PinMap.h:295:5: error: 'DDRB' was not declared in this scope
/Sd2PinMap.h:295:12: error: 'PINB' was not declared in this scope
/Sd2PinMap.h:296:5: error: 'DDRB' was not declared in this scope
/Sd2PinMap.h:296:12: error: 'PINB' was not declared in this scope
/Sd2PinMap.h:297:5: error: 'DDRB' was not declared in this scope
/Sd2PinMap.h:297:12: error: 'PINB' was not declared in this scope
/Sd2PinMap.h:298:5: error: 'DDRB' was not declared in this scope
/Sd2PinMap.h:298:12: error: 'PINB' was not declared in this scope
/Sd2PinMap.h:299:5: error: 'DDRC' was not declared in this scope
/Sd2PinMap.h:299:12: error: 'PINC' was not declared in this scope
/Sd2PinMap.h:300:5: error: 'DDRC' was not declared in this scope
/Sd2PinMap.h:300:12: error: 'PINC' was not declared in this scope
/Sd2PinMap.h:301:5: error: 'DDRC' was not declared in this scope
/Sd2PinMap.h:301:12: error: 'PINC' was not declared in this scope
/Sd2PinMap.h:302:5: error: 'DDRC' was not declared in this scope
/Sd2PinMap.h:302:12: error: 'PINC' was not declared in this scope
/Sd2PinMap.h:303:5: error: 'DDRC' was not declared in this scope
/Sd2PinMap.h:303:12: error: 'PINC' was not declared in this scope
/Sd2PinMap.h:304:5: error: 'DDRC' was not declared in this scope
/Sd2PinMap.h:304:12: error: 'PINC' was not declared in this scope
/Sd2PinMap.h: In function '__uint8_t getPinMode(__uint8_t)':
/Sd2PinMap.h:314:33: error: '__uint8_t getPinMode(__uint8_t)' was declared 'extern' and later 'static'
C:\Documents and Settings\Quentin\Desktop\mpide-0023-windows-20111221\mpide-0023-windows-20111221\hardware\pic32\cores\pic32/wiring.h:130:9: error: previous declaration of '__uint8_t getPinMode(__uint8_t)'
Sd2Card.cpp: In function 'void spiSend(__uint8_t)':
Sd2Card.cpp:27:3: error: 'SPDR' was not declared in this scope
Sd2Card.cpp:28:12: error: 'SPSR' was not declared in this scope
Sd2Card.cpp:28:25: error: 'SPIF' was not declared in this scope
Sd2Card.cpp: In function '__uint8_t spiRec()':
Sd2Card.cpp:33:10: error: 'SPDR' was not declared in this scope
Sd2Card.cpp: In member function '__uint8_t Sd2Card::init(__uint8_t, __uint8_t)':
Sd2Card.cpp:231:3: error: 'SPCR' was not declared in this scope
Sd2Card.cpp:231:16: error: 'SPE' was not declared in this scope
Sd2Card.cpp:231:29: error: 'MSTR' was not declared in this scope
Sd2Card.cpp:231:43: error: 'SPR1' was not declared in this scope
Sd2Card.cpp:231:57: error: 'SPR0' was not declared in this scope
Sd2Card.cpp:233:3: error: 'SPSR' was not declared in this scope
Sd2Card.cpp:233:18: error: 'SPI2X' was not declared in this scope
Sd2Card.cpp: In member function '__uint8_t Sd2Card::readData(__uint32_t, __uint16_t, __uint16_t, __uint8_t*)':
Sd2Card.cpp:358:3: error: 'SPDR' was not declared in this scope
Sd2Card.cpp:362:14: error: 'SPSR' was not declared in this scope
Sd2Card.cpp:362:27: error: 'SPIF' was not declared in this scope
Sd2Card.cpp:368:14: error: 'SPSR' was not declared in this scope
Sd2Card.cpp:368:27: error: 'SPIF' was not declared in this scope
Sd2Card.cpp:373:12: error: 'SPSR' was not declared in this scope
Sd2Card.cpp:373:25: error: 'SPIF' was not declared in this scope
Sd2Card.cpp: In member function 'void Sd2Card::readEnd()':
Sd2Card.cpp:406:5: error: 'SPDR' was not declared in this scope
Sd2Card.cpp:408:16: error: 'SPSR' was not declared in this scope
Sd2Card.cpp:408:29: error: 'SPIF' was not declared in this scope
Sd2Card.cpp:412:14: error: 'SPSR' was not declared in this scope
Sd2Card.cpp:412:27: error: 'SPIF' was not declared in this scope
Sd2Card.cpp: In member function '__uint8_t Sd2Card::setSckRate(__uint8_t)':
Sd2Card.cpp:460:5: error: 'SPSR' was not declared in this scope
Sd2Card.cpp:460:20: error: 'SPI2X' was not declared in this scope
Sd2Card.cpp:462:5: error: 'SPSR' was not declared in this scope
Sd2Card.cpp:462:19: error: 'SPI2X' was not declared in this scope
Sd2Card.cpp:464:3: error: 'SPCR' was not declared in this scope
Sd2Card.cpp:464:18: error: 'SPR1' was not declared in this scope
Sd2Card.cpp:464:32: error: 'SPR0' was not declared in this scope
Sd2Card.cpp: In member function '__uint8_t Sd2Card::writeData(__uint8_t, const __uint8_t*)':
Sd2Card.cpp:559:3: error: 'SPDR' was not declared in this scope
Sd2Card.cpp:563:14: error: 'SPSR' was not declared in this scope
Sd2Card.cpp:563:27: error: 'SPIF' was not declared in this scope
Sd2Card.cpp:565:14: error: 'SPSR' was not declared in this scope
Sd2Card.cpp:565:27: error: 'SPIF' was not declared in this scope
Sd2Card.cpp:570:12: error: 'SPSR' was not declared in this scope
Sd2Card.cpp:570:25: error: 'SPIF' was not declared in this scope

In Configuration.h:

// Comment out (using // at the start of the line) to disable SD support:
#define SDSUPPORT

I have done that already. The error I posted was after I had already commented it out. I think that it still compiles the code for the SD card, and commenting it out just tells it not to use it. Thats the only conclusion I could come to with what I know. or else it is something different entirely

I've been using Repetier-Host + Repetier Firmware+Skeinforge for a while and achieve perfect prints.
Repetier host is very easy to use and its firmware is even more optimised.
You can also combine multiple objects and save it as a separate .STL file.

One of the most difficult objects to print are (IMO) gears and pulleys. I could never get them right with other firmware at reasonable speeds only at very slow speeds.
But since using repetier I get them (ALL) perfect at 80mm/s (main speed) and 30mm/s (perimeter speed). I think it's possible to go even higher but I am very satisfied with current speed and it took me a while to get the bridges perfect for this speed.

Also always print a minimum of 1 extra shells and make sure perimeter is printed after loops for perfect outer shape.

I recommend repetier for people who are new to 3d printing....

Thank you for showing me repetier! It looks very promising. I have downloaded it and tried compiling it, but it still gives a few errors, though far less than sprinter did. If someone could please point me to a place where I can get some help with this that would be great, thanks.


these are the errors in case anyone knows whats going on

In file included from /Configuration.h:32:0,
from Commands.cpp:22:
c:\documents and settings\quentin\desktop\mpide-0023-windows-20111221\mpide-0023-windows-20111221\hardware\pic32\compiler\pic32-tools\bin\../lib/gcc/pic32mx/4.5.1/../../../../pic32mx/include/avr/io.h:4:2: error: #error ******** This sketch or library uses AVR-specific code that may not work with the chipKIT platform. See this forum for more information on porting code to chipKIT [www.chipkit.org/forum/viewforum.php?f=7] ********
In file included from /gcode.h:19:0,
from /Reptier.h:28,
from Commands.cpp:23:
c:\documents and settings\quentin\desktop\mpide-0023-windows-20111221\mpide-0023-windows-20111221\hardware\pic32\compiler\pic32-tools\bin\../lib/gcc/pic32mx/4.5.1/../../../../pic32mx/include/avr/pgmspace.h:4:2: error: #error ******** This sketch or library uses AVR-specific code that may not work with the chipKIT platform. See this forum for more information on porting code to chipKIT [www.chipkit.org/forum/viewforum.php?f=7] ********
In file included from /Reptier.h:29:0,
from Commands.cpp:23:
/fastio.h:2554:2: error: #error pins for this chip not defined in arduino.h! If you write an appropriate pin definition and have this firmware work on your chip, please submit a pull request
In file included from Commands.cpp:24:0:
/Eeprom.h:22:24: fatal error: avr/eeprom.h: No such file or directory
compilation terminated.

Hi Quentin.T,

Never had any errors compiling repetier-firmware,but I have different hardware.

I posted your message in the repetier-section: repetier

The author of repetier will mostlikely be able to help you with this...

Quentin,

Not all libraries used by the firmwares you are trying seems to be compatible with the chipkit. While it may suggest compatibility with Arduino, some libraries might not be working perfectly without proper porting.

I would strongly suggest to get an Arduino Mega so you could get going quickly.