The MINTEMP setting sets the measurement below which it thinks your sensor is broken. You could set MINTEMP below the last entry in your thermistortables.h to make it never trigger. Many of the thermistor tables in Marlin don't go past zero. If your lab is -10°C, then you should make sure the thermistor tables you are using go below the expected environment, and set MINTEMP appropriately.by DaveX - Firmware - mainstream and related support
The heatbed is heater "-1", so calling for 8 calibration cycles around 80C on the heatbed would be: M303 E-1 S80 C8 If you have multiple extruders, you can set the different E?? for the calibration, but the underlying PID shares the resulting kP, Ki, and kD values for all the extruders. In other words, you can use M303 E-1 to find bed_Kp bed_Ki, and bed_Kd to set them with M304, verby DaveX - Reprappers
Editing the D calculation a bit: QuoteDaveX Are these the units for the Teacup PID parameters? P: counts/(C/4)*PID_SCALE I: counts/((C/4)*(s*4)) *PID_SCALE = counts/(C*s)*PID_SCALE D: counts/((C/4)/(TH_COUNT*s/4)) * PID_SCALE = counts/(C/(s*TH_COUNT))*PID_SCALE or counts/(C/8s)*PID_SCALE I Limit: C/4*s*4 = C*s The default parameters are set around while the PID_SCALE is 1024L and TH_COby DaveX - Firmware - experimental, borrowed, and future
That link was from drilling down of of the current into Marlin/Configuration.h (on the Marlin_v1 branch?) You should be able to get it from the zip download link on the right hand size of the page, which links to Personally, I use 'git clone git@github.com:ErikZalm/Marlin.git' work from the command line.by DaveX - Firmware - mainstream and related support
Try looking at TEMP_SENSOR_1_AS_REDUNDANT aroundby DaveX - Firmware - mainstream and related support
The 57560 is good up to 300 C per the datasheet at You could plug in a few values off of pages 5 & 6 of that into the program and get more values for the lookup table if you want. Below is the output from the patch using -- The resolution up around 260C starts getting big. You might want to use a smaller pullup. $ ./createTemperatureLookupMarlin.py --rp=4700 --t1=25:100000 --t2=150by DaveX - General
Quotes1000rr Found the problem!! For some reason I have to put the com port as 0 in the config file even though I'm using com port 3 for communication. Don't know why this solved the problem but I've been able to make changes and upload them without any problems since making that fix. Cheers, Sebastian "Why" is because your Azteeg uses the ATmega2560's serial 0 on pins 0,1 for communication toby DaveX - Firmware - mainstream and related support
QuoteTimTeunAndLotte Thanks for the quick answer, how does one do these things exactly? -T, T and L Exactly how you do it depends on the stepper driver. The link at has a picture with someone measuring the reference voltage Vref off the wiper of the adjustment potentiometer. The official guide for Pololu shown in the picture is at under the "Current limiting" section. If you haven't tuned/by DaveX - General
If your stepper drivers are overheating, they can cause a stutter. You may want to reduce the current/vref. Check them per something likeby DaveX - General
by DaveX - Firmware - mainstream and related support
The code is different now: Try updating your source.by DaveX - Firmware - mainstream and related support
fixed this to Please try a newer version.by DaveX - Firmware - mainstream and related support
If the other tables in your thermistortables.h use an "*OVERSAMPLENR" constant, you will need that for your table as well. Marlin reads the thermistor ADC 16 times and adds them up before interpolating between the left-hand values.by DaveX - Firmware - mainstream and related support
ULTRA_LCD currently needs some sort of encoder to make the menu system work and you are falling into the default case. Try defining NEWPANEL (and ULTIPANEL) in Configuration.h per the #ifdef around I recently posted a patch at that tests if no encoder is defined and lets it compile without those two defines, which provides basic output-only LCD support, .by DaveX - Firmware - mainstream and related support
Are these the units for the Teacup PID parameters? P: counts/(C/4)*PID_SCALE I: counts/((C/4)*(s*4)) *PID_SCALE = counts/(C*s)*PID_SCALE D: counts/((C/4)/(s*4*TH_COUNT)) * PID_SCALE = counts/((C/16s)*TH_COUNT))*PID_SCALE or counts/(C/2s)*PID_SCALE I Limit: C/4*s*4 = C*s The default parameters are set around while the PID_SCALE is 1024L and TH_COUNT is 8 in config.h The s*4 factor is duby DaveX - Firmware - experimental, borrowed, and future
MbaseCNC Wrote: ------------------------------------------------------- > I did manage to make the Teensy port from DaveX > working before Teacup changed ownership to > Traumflug, after that the port was gone from > Github. > I'm glad it is back > I managed to get it compiling and uploading > through the Arduino IDE but had to remove all > instances regarding the heatersby DaveX - Firmware - mainstream and related support
I've got my Teensy 3.0 port in the teensy3 branch in Traumflug's github for Teacup:by DaveX - Firmware - mainstream and related support
The trick is that R1 is set to zero to flag it being non-existent. From your jpgs, Beta is 4390, R2 is the series 4700 ohm R25 in your schematic, so: createTemperatureLookup.py --r2=4700 --beta=4390 --r1=0by DaveX - Firmware - mainstream and related support
Traumflug Wrote: ------------------------------------------------------- > Is it possible to use teacap at all? > > Huh? Of course Teacup works. It should even work > with 250'000 baud, if you set that in config.h. > > > Regarding USB speed: at least V-USB is known to > almost exhaust the CPU at 12 MHz, so you have > still not much room at 16 or 20 MHz. Not sure howby DaveX - Firmware - experimental, borrowed, and future
nophead Wrote: ------------------------------------------------------- > With pronterface or pronsole, I can connect at > "9600" to my Teensy2.0 and communicate with > visually undetectable latency. > > Visually undetectable means less that about 100ms, > which is huge latency at 250KB. Yep, my visual timing measurement is poor. Measured latency between successive no-op gcoby DaveX - Firmware - experimental, borrowed, and future
karabas Wrote: ------------------------------------------------------- > What about comport connection speed bottleneck? > For currect firmwares it's not higher 250000baud. > Thar's too slow for "high density" gcode and some > of us are forced to print from sdcards for better > prints. I think that bottleneck is in the electronics rather than the firmware. Doesn't hardware with bby DaveX - Firmware - experimental, borrowed, and future
Sounds cool. Following Github's procedure, revising the your repository's 'origin' to point at the new URL would be: git remote set-url origin # 'origin' git fetch origin To add a local branch tracking the accel_clock branch: git branch accel_clock origin/accel_clockby DaveX - Firmware - experimental, borrowed, and future
Is the Teacup now under instead of github ?by DaveX - Firmware - experimental, borrowed, and future
I like that test. On Mar 28, 2013, at 12:48 PM, Traumflug wrote: QuoteBTW., I think most other RepRap firmwares set an divider of 8 for the step interrupt, so timing is not entirely as accurate as with Teacup, but the 32 bit extension can be avoided. They then get maximum delays of (1 / F_CPU) * 65535 * 8 = 0.026 s = 26 ms. Translates to a minimum feedrate of 38 steps/second or 288 mm/min on aby DaveX - Firmware - experimental, borrowed, and future
I'm sorry, I was unclear. I meant about modifying the entire codebase to handle different architectures. ARM vs AVR will mess with the analog, arduino, clock, crc, dda_queue, delay, gcode_process, heater, memory_barrier, mendel, serial.h, sersend.h, timer, usb_serial, and watchdog.c files. I've got it compiling and uploading to a Teensy 3.0 with , but I don't have the communication working,by DaveX - Firmware - experimental, borrowed, and future
Thanks. This delay stuff depends on AVR-specific util/delay_basic assembly code, which doesn't seem to be reimplemented on PRJC's port of an arduino-like build environment for its ARM chip. How would you see alternate architecture code developing? One could put #ifdef __AVR__ branches around specific lines in existing files Or maybe try to build alternate delay_ARM.c or cortex_m4/delay.cby DaveX - Firmware - experimental, borrowed, and future
I was fiddling with Teacup for a Teensy 3.0 (ARM cortex-m4, mk20dx128) and noticed that for Teacup, delay(n) means a delay of n microseconds rather than milliseconds: Since that's opposite of the usage in the Arduino world, might it be nice to make it delay_us() or delay_us_wdt() to highlight the differences? Looking into where delay() is used in Teacup, it seems like the calls in sd.c might bby DaveX - Firmware - experimental, borrowed, and future
You use a compiler to make a .elf file and turn it into a .hex file with avr-objcopy. The details are in the Makefile.by DaveX - Firmware - mainstream and related support
If reprap-jerk is the maximum change in speed in mm/sec that than be changed in the interval between two segments, its correspondence to the "jerk" in a kinematic position/velocity/acceleration/jerk sense is sort of like acceleration. The DEFAULT_XYJERK of 20mm/s might be understood as 20mm/s limit on delta-V across the end/beginning of a segment, so its units might be something like 20mm/s/stby DaveX - Firmware - mainstream and related support
If you need a flat, you can make one with a file. I put some masking tape over the bearing to protect mine from the filings while I did it.by DaveX - General