so.. no easy solution I guess?? I ordered a 0,5mm , we'll see..by [email protected] - General Mendel Topics
Nope, it's the next thing to try I guess. Pity, I like the resolution of the 0,35mm.. I hope to see other ideas before I pull out one of my tungsten PCB micro-drillsby [email protected] - General Mendel Topics
Hi all, I've built a Prusa with Megatronics, it has a 0.35mm printhead, uses 1,75mm filament trough a classic hinged extruder, only tried PLA for now. I have had some perfect prints, especially small prints come out great. So I now my calibration must be ok.. I guess. Bigger prints, though, are a pain, because after let's say an hour into a print, the heat separator is sure to clog up. The filby [email protected] - General Mendel Topics
exactly the same problem here.. while I have had very good prints for a while with the same hotend.. If I raise the extrusion temp, the clogging in the pfte tube gets worse. Lower temp makes it mess some layers up. ??by [email protected] - General Mendel Topics
datasheet, found it.. http://reprapworld.com/mt/datasheet%20megatronicsv2.pdfby [email protected] - Reprappers
brupje Wrote: ------------------------------------------------------- > I have released an preliminary datasheet: > > megatronicsv2.pdf file no longer available? wish I had saved it after allby [email protected] - Reprappers
Thanks! It worked!by [email protected] - RAMPS Electronics
Solved! it was overcurrent on the steppers. they heat up and shut down, resulting in skipping steps. I turned the pots down a little on the Pololu drivers, and it came out very nice! Now I can concentrate on calibration!by [email protected] - Printing
Hi, My newly built Prusa with Megatronics and Pololu is giving me a hard time. The first seconds of most prints go well, but then my X and Y axes begin to skip quite fast. Same in pronterface. I think I read somewhere this might be due to overcurrent? The steppers would protect themselves against overheating thus skipping G-code commands? where do I look if I want to try if reducing the curreby [email protected] - RAMPS Electronics
Hey, I just finished building my first 3D printer, and tried some small prints in order to get the settings right / calibrate. (It's a Prusa with Megatronics2 and Marlin, I use Slicer & Pronterface) It has been quite a journey I must say, but enjoyed it every step of the way :-) I took a small object from thingyverse, I think it was this one In the picture you can find the results firstby [email protected] - Printing
SOLVED: I took a close look at the schematics of the board and compared Marlin to it. what it is now in Marlin: /* #define SHIFT_CLK 38 #define SHIFT_LD 42 #define SHIFT_OUT 40 #define SHIFT_EN 17 #define LCD_PINS_RS 16 #define LCD_PINS_ENABLE 17 #define LCD_PINS_D4 23 #define LCD_PINS_D5 25 #define LCD_PINS_D6 27 #define LCD_PINS_D7 29 */ what it should be: #define SHIFT_CLKby [email protected] - Firmware - mainstream and related support
SUCCES! Took another LCD, because It turned out it WAS a bad one. Damn you, Murphy! tried again with your firmware, still compilation error. tried again with my setting, it works! I am sooooo proud of me ) thanks all for your help!by [email protected] - For Sale
sorry I can't agree.. I just downloaded this file again, same problem again. by the way, I'm looking at the PDF schematics of the board and it suggests the pinouts are different than in Marlin: what it is now: /* #define SHIFT_CLK 38 #define SHIFT_LD 42 #define SHIFT_OUT 40 #define SHIFT_EN 17 #define LCD_PINS_RS 16 #define LCD_PINS_ENABLE 17 #define LCD_PINSby [email protected] - For Sale
yeah stupid me big thanks, we're getting there.. as I suspected, the declarations were commented out // still something not right with the pin numbers I guess, but that's not a firmware problem :-)by [email protected] - Firmware - mainstream and related support
I found where these errors come from. As I thought the pins weren't defined (they were, but they were commented out //) they can be found in pins. h // #define SHIFT_CLK 38 // #define SHIFT_LD 42 // #define SHIFT_OUT 40 // #define SHIFT_EN 17 these were commented out, is you take the // away, the errors dissappear and you can compile. but I suspect the pinout numbers are still wrongby [email protected] - For Sale
yep same thing here glad it's not meby [email protected] - For Sale
yes, I took the standard file you provided, with the only modification: -define Ultra_lcd but then it goes back to that "SHIFT_CLK" was not declared in this scope I'm not very familiar with programming, but I think this has to do with buttons. I have just a 16x2 lcd without buttons.. OR this could be the defining of the pinouts for the LCD, but the pins numbers to the MEGA aren't declared?by [email protected] - For Sale
does someone know where the pinouts for the LCD are declared in Marlin? thxby [email protected] - Firmware - mainstream and related support
it does display something if I do that, but only a line of black blocks (first line). I'd think there's something wrong with the pins, but I checked over and over again... Maybe something in Marlin, does someone know where these pins adresses are defined?by [email protected] - For Sale
something is getting clearer to me. I think the ULTRA_LCD is not the same as a generic 16x2 lcd without buttons. I bet the variables above have something to do with those buttons, haven't they? those are my settings now, but the problem remains //LCD and SD support #define ULTRA_LCD //general lcd support, also 16x2 //#define SDSUPPORT // Enable SD Card Support in Hardware Console ... //#ifby [email protected] - Firmware - mainstream and related support
ok, got that, then I got some errors while compiling; 'SHIFT_CLK' was not declared in this scope. and other similar. I read about similar error codes, and tried to fill in what I found by googling when I put this at the beginning of the scope: #define SHIFT_CLK 38 #define SHIFT_LD 42 #define SHIFT_OUT 40 #define SHIFT_EN 17 int8_t encoderDiff; it will compile, but I think the varby [email protected] - Firmware - mainstream and related support
I'm just finishing my Prusa with a relatively new megatronics 2 board and Marlin firmware. It's my first 3D printer, so I'm fighting against a high learning curve. But I think I almost got it, It moves allright (not calibrated yet), but I'm missing some pieces to finish it, so I'm awaiting delivery. In the meanwhile, I was trying to hook up a 16x2 LCD display I had lying around in my arduiby [email protected] - Firmware - mainstream and related support
It seems like I'm an early adopter :-) I'm just finishing my Prusa with this board and Marlin firmware. It's my first 3D printer, so I'm fighting against a high learning curve. But I think I almost got it, It moves allright (not calibrated yet), but I'm missing some pieces to finish it, so I'm awaiting delivery. In the meanwhile, I was trying to hook up a 16x2 LCD display I had lying around inby [email protected] - For Sale
I've seen that setting. Haven't tried it yet, because my extruder shouldnt go there at all. I think I've solved it partially by AGAIN switching the steppers directions, and also changing the endstop-logic. now the extruder goes in the correct direction to start. I also tinkered with the bed_centre, and it seems like it is better now. But still! I tried printing a small object, still without acby [email protected] - Firmware - mainstream and related support
I meant burning out my stepper drivers (pololu MD09B actually) But, I found out by closely looking at the specsheet. it mentions the pinout (but it's not on the silkscreen.) I took a gamble, connected it, and thankyoujezus no blue smoke I'm currently tying to figure out what the correct settings are in slicer and pronterface, but I'll get there :-) thanks!by [email protected] - General
Hey, I'm building a Prusa with Megatronics 2 with Marlin firmware. I use Slicer and Pronterface. I have set a lot of variables in Slicer and in the Firmware, but I must be overlooking something? I think I'm almost there, but I have an issue. In pronterface, when I home the extruder, the end-stops do what they have to do, everything seems to go well. (I had to inverse the direction of all theby [email protected] - Firmware - mainstream and related support
Hi Guys, short story: Read a lot about 3D printing, have some degree of experience with electronics, Arduino and physics, and thought I'd take a shot at it. I compared and compared again, and bought a DIY kit from reprapworld.com. Along with a Megatronics V2.0 all-in-one board. I spent about 3 days at building the raw frame, following the very good instructional videos on the wiki. This workeby [email protected] - Controllers
-- sorry - wrong subject! -- Hi Guys, short story: Read a lot about 3D printing, have some degree of experience with electronics, Arduino and physics, and thought I'd take a shot at it. I compared and compared again, and bought a DIY kit from reprapworld.com. Along with a Megatronics V2.0 all-in-one board. I spent about 3 days at building the raw frame, following the very good instructionalby [email protected] - General