thermistor table for honeywell (budaschnozzle) in firmware?

Hi everyone - thinking about switching to the Repetier firmware from Marlin and I'm trying to define my extruder thermistor.
I'm using a Budaschnozzle which comes w/ a Honeywell 135-104LAG-J01. In Marlin, I can select that particular thermistor because all the thermistor values are defined in "thermistortables.h" How do I use those values in the Repetier firmware? are those thermistor tables stored someplace else?

I looked at the documentation (http://www.repetier.com/documentation/repetier-firmware/rf-installation/) and the section on temp. measurement went over my head pretty quickly, and I don't have the experience to kludge this out....so maybe the least complex solution might work best.

thanks!

You need to use a user defined thermistor table. SImply replace

#define NUM_TEMPS_USERTHERMISTOR0 28
#define USER_THERMISTORTABLE0  {\
  {1*4,864*8},{21*4,300*8},{25*4,290*8},{29*4,280*8},{33*4,270*8},{39*4,260*8},{46*4,250*8},{54*4,240*8},{64*4,230*8},{75*4,220*8},\
  {90*4,210*8},{107*4,200*8},{128*4,190*8},{154*4,180*8},{184*4,170*8},{221*4,160*8},{265*4,150*8},{316*4,140*8},{375*4,130*8},\
  {441*4,120*8},{513*4,110*8},{588*4,100*8},{734*4,80*8},{856*4,60*8},{938*4,40*8},{986*4,20*8},{1008*4,0*8},{1018*4,-20*8}	}

with the table for your thermistor

#define NUM_TEMPS_USERTHERMISTOR0 67
#define USER_THERMISTORTABLE0  {\
   {1*4, 941*8},{19*4, 362*8},{37*4, 299*8},\
   {55*4, 266*8},{73*4, 245*8},{91*4, 229*8},{109*4, 216*8},{127*4, 206*8},{145*4, 197*8},{163*4, 190*8},{181*4, 183*8},{199*4, 177*8},\
   {217*4, 171*8},{235*4, 166*8},{253*4, 162*8},{271*4, 157*8},{289*4, 153*8},{307*4, 149*8},{325*4, 146*8},{343*4, 142*8},{361*4, 139*8},\
   {379*4, 135*8},{397*4, 132*8},{415*4, 129*8},{433*4, 126*8},{451*4, 123*8},{469*4, 121*8},{487*4, 118*8},{505*4, 115*8},{523*4, 112*8},\
   {541*4, 110*8},{559*4, 107*8},{577*4, 105*8},{595*4, 102*8},{613*4, 99*8},{631*4, 97*8},{649*4, 94*8},{667*4, 92*8},{685*4, 89*8},\
   {703*4, 86*8},{721*4, 84*8},{739*4, 81*8},{757*4, 78*8},{775*4, 75*8},{793*4, 72*8},{811*4, 69*8},{829*4, 66*8},{847*4, 62*8},\
   {865*4, 59*8},{883*4, 55*8},{901*4, 51*8},{919*4, 46*8},{937*4, 41*8},\
   {955*4, 35*8},{973*4, 27*8},{991*4, 17*8},{1009*4, 1*8},{1023*4, 0}}

And then set thermistor type to 5.
Watch out the backslashes remain the last character in the rows or you will get compile errors!

---

Repetier-Software - the home of Repetier-Host (Windows, Linux and Mac OS X) and Repetier-Firmware.
Repetier-Server - the solution to control your printer from everywhere.
Visit us on Facebook and Twitter!

thanks repetier!
I also found this: [repraptastic.blogspot.com]

Hello

im using repeptier firmware and i have problem with epcos FFF104 table

cant find the table

can i get the table please

best regards

Googling epcos FFF104 gives only this page as result, so what thermistor are you really using? WIthout knowing the exact model you will not be able to find the matching table.

---

Repetier-Software - the home of Repetier-Host (Windows, Linux and Mac OS X) and Repetier-Firmware.
Repetier-Server - the solution to control your printer from everywhere.
Visit us on Facebook and Twitter!

Hello repetier

im using this one 100K ohm (EPCOS B57560G104F NTC THERMISTOR)

the think is that im using the same type on my bed and im getting a good reading

but not on the hotend - selection number 5 on bed and on hot end

what im doing wrong ?

thank you alot

elidor

5 is a user defined table. You could read the firmware docs on my homepage on how to compute that. But I'm quite sure selecting type 1 should already give good results.

---

Repetier-Software - the home of Repetier-Host (Windows, Linux and Mac OS X) and Repetier-Firmware.
Repetier-Server - the solution to control your printer from everywhere.
Visit us on Facebook and Twitter!

cool thank you

i would like allso to help to translat repetier host to hebrew , where do i begin ?

thank you =)

I hope it is written left to right, because I have no right-left support.
New translations are fairly easy to make and a documentation on this can be found here:

[www.repetier.com]

Simply translate and mail me the translation. I will then include it in the next update.

---

Repetier-Software - the home of Repetier-Host (Windows, Linux and Mac OS X) and Repetier-Firmware.
Repetier-Server - the solution to control your printer from everywhere.
Visit us on Facebook and Twitter!

hI

NO ITS NOT , HOPE TO SEE THIS SUPPORT SOON

THANK YOU FOR TRYING

BEST REGARDS

ELIDOR ZAMIR

HI

im was trying number 1 and again im getting 500 deg

im trying for aweek im lost

elidor

In that case your thermistor has a short. You have to watch carfully at the thermistor itself. The two cables are not isolated and can easyly cause a short. That will no damage, but you measure the resistance of the short now and not the one of the thermistor.

---

Repetier-Software - the home of Repetier-Host (Windows, Linux and Mac OS X) and Repetier-Firmware.
Repetier-Server - the solution to control your printer from everywhere.
Visit us on Facebook and Twitter!

Hello repetier

first i would like to thank you for the great support

i was checking there is no short ,im working on my new design for the delta and i think that the wire is too long and i think that the ressitance is too high because the long running (wire) it atlist 1 meter long

what do you think ?

[www.facebook.com]

thank you

elidor

First I think it is a nice looking delta. You should follow the development tree as I'm currently optimizing the code for deltas.

At room temperature the resistance is 100kOhm, I doubt 1meter cable makes that much difference. But I have currently running a solo board and it shows 500°C because I have no resistor at all. So I might be wrong and you have no connection at all. No connection could of course also mean using the wrong thermistor input, leaving the one shown empty.

---

Repetier-Software - the home of Repetier-Host (Windows, Linux and Mac OS X) and Repetier-Firmware.
Repetier-Server - the solution to control your printer from everywhere.
Visit us on Facebook and Twitter!

I used your advice to setup Repetier FW for the Honeywell 135-104LAG-J01 but I keep getting DEF showing for the hot end temperature on the RepRap-Disccount LCD control panel. If I load Marlin on the same HW, it works and heats up the extruder. Strangely the Host IS reading the temperature reported by the hot end (room temp) in any case. I DON'T have a bed heater hooked up, could Repetier FW be setting the fail for BOTH heaters if only one is bad? Also I noticed that my min temp was set as -10C, but the table you showed for the Honeywell doesn't go negative. Could that be a problem?
BTW I'm running RAMPS 1.4 HW in a standard configuration.

No -10 is no problem. It will just never be reached. So it must be the upper limit that gets reached. One measurement outside allowed range for any heater device triggers the def signal for the while running. You should look into the host log. There you see which device triggered the def initially. It could also be a not connected bed, but I saw no bed compiled into your config. Even if it gives normal values after that. Have you tried pressing reset after first start to see if it still goes to def? Might be a cross talk while powering up. And what did M105 X0 return? (you need to look into the written log since the host filters temperature answers from log)

---

Repetier-Software - the home of Repetier-Host (Windows, Linux and Mac OS X) and Repetier-Firmware.
Repetier-Server - the solution to control your printer from everywhere.
Visit us on Facebook and Twitter!

I'll have to try the M105 X0 later when I'm home. I wish there was a way to reset the error without rebooting the firmware. Or even better, just correct the problem and go. Marlin will dismiss the same error once I hook up the thermistor, repetier seems to need to have everything perfect when it is powered up, even if no print is being started.
BTW another issue I have is that even though my Z max position is set at 300, I can't get the Z to go beyond 116.85mm. It will go negative, though my min position is zero. (from the panel that is).

OK I've analyzed the problem.
I DID have a heated bed defined in my config. IF no thermistor is attached to the bed BOTH the hot end AND the BED show in error. IMHO this is a BUG.
I tried both deleting the heated bed from the config, and attaching a thermistor to the heated bed T1 pins. BOTH fixed the problem.

What I would suggest (and I might try hacking the code to do) is to have the firmware constantly check for error conditions in the thermistor BUT NOT LOCK the error if the extruder is NOT running. ONLY if the error is detected WHILE the extruder is running (or is about to be started) will the extruder be locked out. This will allow one to fix the HW without rebooting.

ALSO the error conditions for the BED and the HOTEND should be separate. After all if you are using PLA you don't necessarily care if the BED won't heat up. Perhaps that should be conditioned to whether you are using ABS or PLA as determined by the temperature setting.

I guess everyone can have a different opinion on this. I personally do not consider it a bug since a system that was defined to have a bed and extruder should have them working. So if one is defect the heating system has to be considered defect and should not run at all for safety. Also there is only one flag that marks dry run. Makeing it depend on pla or abs is too complicated. No slicer tells what it is going to print and we also do not want to wait until a print start. We want to prevent potential prints that will fail as soon as possible.

---

Repetier-Software - the home of Repetier-Host (Windows, Linux and Mac OS X) and Repetier-Firmware.
Repetier-Server - the solution to control your printer from everywhere.
Visit us on Facebook and Twitter!

Well not yet having a chance to look deep enough into the code I don't know how much would have to be changed to do anything in this area. At the very least it would have been nice to have the errors reported for the hot end thermistor and the heated bed one be separate. Marking both as failed when only one was bad made finding the real problem a bit of a issue for someone who didn't know what was going on! Also having a way to reset the error without rebooting would be useful, though this function shouldn't be possible once printing has started! Also if you reset the error and it still existed it would only get set again at once (the next time a temperature reading was made). Other than those two issues I guess I agree with the way things are. Perhaps being able to disable the heated bed without recompiling the software, and if disabled it wouldn't be able to report an error, might be another idea. Once I removed the bed heater from the configuration it no longer was reported in the control panel display, and didn't effect being able to heat the extruder.

Anyway, now that I've got THAT problem out of the way, (and figured out that I needed to change the EEPROM flag number EVERYTIME I made a change to configuration.h) I can get on with more interesting things in getting my printer calibrated and working! Thanks for the help!