Axis Wrote: ------------------------------------------------------- > If I tell it to extrude 100mm and the mark is 30mm > from the extruder, wouldn't that mean it fed 70mm? > Shouldn't it be 100/70? Depends on where you started. If you marked it at 100 from the extruder, told the extruder to move 100 then measured it at 30 from the extruder, then d_Ordered/d_Extruded is 100/70 and youby DaveX - Printing
2035.6 microsteps/mm? Wouldn't that mean your acme threads are 2035.6*25.4/200/16=16.1577 threads per inch? I'd have guessed that 1/4-16 threads would need 2015.748 microsteps/mm, (or maybe 2016.0 steps/mm for 1/4-16.002 threads) What layer height are your using? 2035.6 microsteps/mm * 0.1mm = 203.56 microsteps/layer 2035.5809493712193 microsteps/mm * 0.1mm = 203.55809 microsteps/layerby DaveX - General
If its processing power, you can reduce the processing power required by using less microstepping or reducing the feed rates or max feed rates. A 100mm X0.4x0.6mm strand would need ~5.7mm of filament, so if all your axes are about 181486 steps/m, then a diagonal 100mm deposition would need about 26700 steps. With a max of 15kSteps/s (per ) -- you might run into max feed rate issues around 50by DaveX - Firmware - experimental, borrowed, and future
If the board is reporting changes in temperatures, then the controller pin and A/D converter is working and you will not need to switch pins. Is the new 100K thermistor exactly the same as the old one? If not an exact replacement, you could need a different thermistor table/configuration to get accurate temperatures. You could test the thermistor by checking its resistance against the expectby DaveX - Reprappers
Sublime did it with about 10 discrete components:by DaveX - General
Looks like delivery is in December for folks ordering now. Seems like an inventive sort could wire a bowden to a hotend and a stripped-down firmware (two pots to control temp and feedrate, one push button to do M101/M103, or G01 E0.5 repeatedly) and have one almost overnight.by DaveX - General
Zedsquared Wrote: ------------------------------------------------------- > The idea of extruding "up" for in fill will run > into a lot of problems as regards stopping the > extruder colliding with the work though... Layer > by layer it isn't a problem as the head is always > moving through empty space yet to be printed in, > add the third dimension and all of a sudden the >by DaveX - General
In general you want the cold end of the hotend to be cold so you can have a short transition zone where the plastic melts in order to have good control over the extrusion. For the tricolor, you might want to cool the unused hotends down quickly when you switch.by DaveX - General
From Cyberwizard's Lookahead code per and I've made a patch that seems to print on my atmega32u. I cut out the leading-axis-tracking, since it didn't seem to be actually using it & was giving me a warning, cuts out some of the emergency-stop code, and compiles and works for !defined LOOKAHEAD path. It doesn't patch all the config.*.h files--only the config.teensy.h file is tested with aby DaveX - Firmware - experimental, borrowed, and future
Traumflug Wrote: ------------------------------------------------------- > What hardware are folks using with the > arduino_usb1287.h / MCU_TARGET = at90usb1287 > configuration of Teacup? > > Can't tell that, maybe it was some custom made > electronics. Nevetheless I applied your patch, > except the Makefile change (which is a personal > preference, only). Thanks a lot!by DaveX - Firmware - experimental, borrowed, and future
I had a bunch of warnings during a recent compile. I needed to upgrade my avr-gcc to get past this one: $ make rm -f build/depend mkdir -p build avr-gcc -DF_CPU=16000000L -mmcu=at90usb1287 -g -Wall -Wstrict-prototypes -std=gnu99 -funsigned-char -funsigned-bitfields -fpack-struct -fshort-enums -Winline -fno-move-loop-invariants -fno-tree-scev-cprop -Os -ffunction-sections -finline-functions-cby DaveX - Firmware - experimental, borrowed, and future
Parallel: I suppose you'd want dual heaters for a capability of about 40W. Wiring them in serial would get you only about 10W. You should be able to measure about 2*12V/6.8ohm=3.4A through the pair while heating up from cold. Check your temperatures with something other than the thermistor readings themselves.by DaveX - General
I added a 3.7 ohm + 3300uF lowpass filter (fc=1/(2*pi*3.7*3300e-6)=13.0348Hz) on my ATX's +5VSB supply line and cleaned my VCC of a lot of noise. If someone needs to use the EWMA or oversampling/decimation to get stable readings, I think they ought to at least check their power supply ripple. I'm happy to give up the 0.5 volt for the reduced noise. Mine was 25-100 mVpp with 120Hz and 50kHz+ coby DaveX - Firmware - experimental, borrowed, and future
From there is: for Autodependencies, but it also has some cruft and things specific to my setup. has the 15Hz to 60Hz change, but the whitespace doesn't match. and do the table-code for createThermistorTable.py Maybe it would be possible to do the thermistor-table-creating in CPP, but I sort of like the separate program for tuning the thermistor circuit. I've been generating some --nuby DaveX - Firmware - experimental, borrowed, and future
Darn. I misread/mispatched the flags. The above patch makes Timer4 slow PWM be 15 Hz. It you want it to match the others' frequencies, then swap CS41 for CS42: $ git diff -w upstream Gen7 heater.c diff --git a/heater.c b/heater.c index df03488..7c5b162 100644 --- a/heater.c +++ b/heater.c @@ -138,9 +138,9 @@ void heater_init() { TCCR4A = MASK(PWM4A) | MASK(PWM4 ; // enby DaveX - Firmware - experimental, borrowed, and future
Here's another one for heater.c to slow down the amega32U4 10bit timer and let DEBUG report on other PWMs: v21837:Teacup_Firmware drf$ git diff heater.c diff --git a/heater.c b/heater.c index 51ed374..62998e0 100644 --- a/heater.c +++ b/heater.c @@ -132,7 +132,10 @@ void heater_init() { TCCR4A = MASK(PWM4A) | MASK(PWM4 ; // enable A and B TCCR4Cby DaveX - Firmware - experimental, borrowed, and future
Attached is a patch to createTemperatureLookup.py to update some of the links, add some comments, and add a couple options. I got confused about the proper choice of resistors/resistor for my electronics, and I very much like having the script calculate the resolution and self-heating power for me. The comments in the generated pointed to old code that doesn't work with r1=0 non-existent scheby DaveX - Firmware - experimental, borrowed, and future
Traumflug Wrote: ------------------------------------------------------- > Dave, I've taken the (a bit bold) step to replace > lufa serial with usb serial. usb_serial.{c|h} is > now in Teacup's repository, this gets rid of the > external dependency. If there are actually lufa > serial users and it breaks something for them, I > think we can work that out. > > I've also reby DaveX - Firmware - experimental, borrowed, and future
Teensy and lufa_serial are refusing to work for me, but maybe I'm doing something wrong. I seem to remember that I did have the LUFA usb code working on the Teensy back in February, but I think I might have had to redefine things deep in the LUFA tree, somewhere around LUFA/trunk/LUFA/Drivers/Board/TEENSY/LEDs.h or something. I do remember that I kept having problems and hacked together serialby DaveX - Firmware - experimental, borrowed, and future
Might there be a problem with casting/truncation or something in the EWMA code in temp.c? On the EWMA_ALPHA = 0.1, I had a problem with some reported temperature values for a AIO clamped to Vref for my unheated bed. Readings would stay at 0 for minutes, then jump and sticking at about 6397.50 C. I saw something similar on my extruder after I went through a printing cycle, after which the g-cby DaveX - Firmware - experimental, borrowed, and future
Triffid_Hunter Wrote: ------------------------------------------------------- ... > no need to avoid 16 bit timers for PWM, just set > them to 8 bit mode and write to the high word. > Should already be some code for the mega to do > that Cool. I'm testing the PWMs I tried to define for the ATmega32U4 in and correcting the _PWM registers. I really did not understand the differencesby DaveX - Firmware - experimental, borrowed, and future
I do not see where heater_pwm is set to 30, but I do see: for (i = 0; i < NUM_HEATERS; i++) { if (heaters.heater_pwm) { *heaters.heater_pwm = 0; ... around line 98 of The heater pins are already set low and output enabled around so i don't think you'd need to do more. I seem to remember that I used the PID code to BANG_BANG a non-PWM pin, but I thought I had to #define BANG_BANGby DaveX - Firmware - experimental, borrowed, and future
Looks good, but there might be one issue: I had a problem with the earlier bang-bang code, and thought that the "#define BANG_BANG_OFF 45" should be less than the heater.c/heater_set threshhold of 8. Since OFF and ON both are larger than 8, wouldn't the defaults make the heater always on?by DaveX - Firmware - experimental, borrowed, and future
I've tested on my branch/fork/code for a while. Do you want a patch as is available at that link or a patch like the attached file?by DaveX - Firmware - experimental, borrowed, and future
QuoteHow's shipping from McMaster-Carr for long rods? Since they don't calculate shipping until after an order is in progress, I didn't want to take the chance of a high oversize charge. Quotederevaun I can't remember what McMaster charged for the shipping. The heavy duty shipping tubes were very expensive looking. is a good discussion of bar types.by DaveX - General
For my Wallace, I went with cheap, but high tolerance annealed oil-hardening drill rod from McMaster Carr: 9 ft of 6mm for about $15. Precision ground hardened shafts looked like about $61/meter for stainless or $30 for steel, and I figured I could upgrade later if need be. Plain or galvanized rods form the hardware store seemed not that much less expensive than the drill rod option. Nopheadby DaveX - General
Traumflug Wrote: ------------------------------------------------------- > ... > > Thanks a lot, slightly edited patch committed. > There's no need for the alternative code, as the > optimiser reduces the formula to the trivial case > for TEMP_EMWA = 1.0. Also added the index to > support multiple sensors. Glad you like it. I like EWMAs in work life, and was happy to findby DaveX - Firmware - experimental, borrowed, and future
phord: Without using any patches, you could try increasing TEMP_HYSTERESIS and shortening TEMP_RESIDENCY_TIME to something quick. If all the readings are within TEMP_HYSTERESIS of the setpoint for TEMP_RESIDENCY_TIME, the hang should clear itself. I guess that's explicitly in the config file: Quoteconfig.h temperature is "achieved" for purposes of M109 and friends when actual temperature isby DaveX - Firmware - experimental, borrowed, and future
I'm not the user from IRC, but my thermistor circuit is pretty noisy (deltaT for successive readings up to 10C) . I'd been avoiding M116, and the patch worked for me with a TEMP_HYSTERESIS = 10 and TEMP_RESIDENCY_TIME = 20. I didn't realize how bad my thermistor circuit was until now. Using the unfiltered +5 from an ATX power supply rail with a 4.7uf capacitor across the thermistor is not suffby DaveX - Firmware - experimental, borrowed, and future
Traumflug Wrote: ------------------------------------------------------- > (the one you gave doesn't show in which file, > which line this snippet should be applied) > > Scratch that. As I noticed later, you actually did > provide a proper patch. Thanks a lot, I applied > most of them to the Gen7 branch, the de-facto > development branch. > > > The only open questby DaveX - Firmware - experimental, borrowed, and future