Thermistor 104nt-4-r025h42g
-
Hello,
I am new wiht RepRap and using FW 2.02 with a E3D Toolchanger and had to change a thermistor.
The old gcode looks like this is the config file:
M305 S"T2" P3 T100000 B4138 C0 X202
Now I changed it to
M305 S"T2" P3 T100000 B4725 C7.060000e-8 X202
but 2000°C are measured.
What did I mess up?Thanks!
Mike -
@MIke-1 Maybe you are new to RepRap, but your firmware is from the Stone Age: more than 4 years old. So don’t expect too much enthusiasm to support you with that old bone.
With a tool changer, you really will benefit from the latest RRF versions - this forum will guide you through the upgrade procedures if you need help.
What did I mess up?
To your thermistor: did the old
M305Gcode work? The X parameter looks strange, didn’t ever use that in my old config files.2000°C are measured.
However, a readout of 2000°C means most likely a short in your wiring. So please check that.
-
@infiniteloop said in Thermistor 104nt-4-r025h42g:
@MIke-1 Maybe you are new to RepRap, but your firmware is from the Stone Age: more than 4 years old. So don’t expect too much enthusiasm to support you with that old bone.
I saw a lot of changes in the gcode form Version 2 to Version 3. That scares me. The system was in a very bad condition when I bought it. Homing and all the coordinates for the toolchanges are messed up. I do have 2 Hemera and 2 bowden printheads. Homing is either done with the printhead (Hemera) or the toolchanger (bowden) hitting the frame... 2 tools work....OMG
With a tool changer, you really will benefit from the latest RRF versions - this forum will guide you through the upgrade procedures if you need help.
I am scared of naming the ports and updating many files. Is it only the config file?
To your thermistor: did the old M305 Gcode work? The X parameter looks strange, didn’t ever use that in my old config files.
It looks like no changes in the config file or comand line work....
2000°C are measured.
However, a readout of 2000°C means most likely a short in your wiring. So please check that.
The resistiance is 150kOhms and I used the old thermistor that still workes. I switched because the old one is too weak or the PID failed as well...so it should be software.
Just let me know your oppinion. Thanx!!!
-
@MIke-1 said in Thermistor 104nt-4-r025h42g:
I saw a lot of changes in the gcode form Version 2 to Version 3. That scares me.
With a reason. When I updated my printer from 2.05 to 3.3, it was a long run and took me to re-write most of my config and the macros. The good thing is: @Phaedrux has a helpful text module with all the necessary steps listed
The resistiance is 150kOhms
Did you measure that at the board or the thermistor itself?
A resistance of 150k is not very plausible: having looked up the 104nt-4-r025h42g, its nominal values is 100k (at room temperature). Or do you live in an especially frosty environment?
The reading "2000°C" is the maximum value to display, it corresponds to a very low resistance of the thermistor - that's why I can imagine a short as plausible reason.
so it should be software.
I can think of a quirk with the tool definition in your config, so please post your config.g (use the </> tag from the editor). BUT: as you run a very outdated version of RRF, I might be unable to give good advice
-
You can find an example config for a RRF3 tool changer here: https://github.com/Duet3D/RRF-machine-config-files/tree/master/E3D_Tool_Changer/dc42-duet3-centreZero-2Titan-2Hemera
If you still have access to DWC. Upload these zip files, one at a time in the system tab. Don't extract them first. Reboot after each. Use M115 in the gcode console to verify the firmware has been applied.
https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/Duet2Firmware-2.05.1.zip
https://github.com/Duet3D/RepRapFirmware/releases/download/3.0/Duet2and3Firmware-3.0.zip
https://github.com/Duet3D/RepRapFirmware/releases/download/3.3/Duet2and3Firmware-3.3.zip
https://github.com/Duet3D/RepRapFirmware/releases/download/3.4.5/Duet2and3Firmware-3.4.5.zipThat will get your firmware and DWC up to date.
You can see the change logs here:
https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.xFor your config, might be a good idea to run through the configurator tool and generate a fresh set for RRF3.
https://configtool.reprapfirmware.org/StartBackup your existing config files in the sys folder in case you want to switch back to RRF2. It’s easy to switch back and forth, just upload the zip file for the version you want and then upload your config files.
These documents will come in handy during the conversion.
https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview
https://docs.duet3d.com/en/User_manual/RepRapFirmware/Migration_RRF2_to_RRF3
https://docs.duet3d.com/en/User_manual/Reference/Gcodes -
@Phaedrux said in Thermistor 104nt-4-r025h42g:
your existing config files in the sys folder in case you want to switch back to RR
I think I got the message.
-So I will copy the sd card.
-Run all firmeware updates.
-Use the configurator
-Make a lot bugfixingWill most likely need your support!
It will take a few month...
Is it going to work?
-
Now it is flashed to 3.3. Everything including WiFi is gone. Will have to fix this next.
-
@MIke-1 said in Thermistor 104nt-4-r025h42g:
Now it is flashed to 3.3. Everything including WiFi is gone. Will have to fix this next.
It's possible the firmware for the wifi module didn't flash properly. You can usually resolve this by connecting via USB and using YAT to send M997 S1, or if you have a PanelDue just send M997 S1 from the console. That will trigger a reflash of the wifi module.
-
@Phaedrux said in Thermistor 104nt-4-r025h42g:
irmware for the wifi module didn't flash properly. You can usually resolve this by connecting via USB and using
M587: Failed to add SSID to remembered list: another SPI transfer is pending ist the original Error
M997: File 0:/firmware/DuetWiFiServer.bin not found is the Error.
What went wrong. Such a dictionary is not existing on the sd card.Just copied the files...now on the best way to 3.45
-
@MIke-1 said in Thermistor 104nt-4-r025h42g:
What went wrong. Such a dictionary is not existing on the sd card.
The 3.3 update adds a firmware directory. Either the directory creation failed or the firmware update looked there before it was created. Once you're passed 3.3 it's not an issue anymore.
-
Made it to 3.45 now
I finshed the configurator and now want to use this as a basis to build it all up.
The config is quite strange. I have issues with M950 and I think I mess up channels.
Here is a section for the Z-Probe:
; Z-Probe Configurator
;M558 P5 C"^zprobe.in" H5 F120 T18000 ; set Z probe type to switch and the dive height + speeds
;G31 P500 X0 Y0 Z2.5#########################################################
;New code: Duet website
;M558 P9 C"zprobe.in" H5 F120 T3000 ; BLTouch connected to Z probe IN pin, free up MOD pin
;M950 S0 C"zprobe.mod" ; servo/gpio 0 is Z probe MOD pin
;...
;M280 P0 S10 ; send control signal to BLTouch through servo/gpio 0old code
M558 P7 X0 Y0 Z2 H3 F360 I0 T20000 ; Set Z probe type to switch, the axes for which it is used and the dive height + speeds
G31 P200 X0 Y0 Z0 ; Set Z probe trigger value, offset and trigger height ; set Z probe trigger value, offset and trigger height
M557 X15:385 Y15:385 S40 ; define mesh grid####Toolchanger example:
M558 P8 C"io3.in" H3 F1000:300 I0 T30000 ; Set Z probe type to switch, the axes for which it is used and the dive height + speeds
G31 P200 X0 Y0 Z0 ; Set Z probe trigger value, offset and trigger height
M557 X-140:140 Y-80:80 S40 ; Define mesh gridHow do I detect which is the right channel?
-
This post is deleted! -
M950 uses pin names. You can learn about them here: https://docs.duet3d.com/User_manual/RepRapFirmware/Migration_RRF2_to_RRF3#pin-names
-
old code
M558 P7 X0 Y0 Z2 H3 F360 I0 T20000 ; Set Z probe type to switch, the axes for which it is used and the dive height + speeds
G31 P200 X0 Y0 Z0 ; Set Z probe trigger value, offset and trigger height ; set Z probe trigger value, offset and trigger height
M557 X15:385 Y15:385 S40 ; define mesh gridnew code
M558 P7 C"zstop" H3 F360 I0 T20000
G31 P200 X0 Y0 Z0 ; set Z probe type to switch and the dive height + speeds
M557 X15:385 Y15:385 S40Does this make sense? The cable is linked to the z-endstop on the board.
Is P7 the motor because ist should be P2 as it is linked to the barod's z-axis ?
-
No P is the probe type.
https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m558-set-z-probe-type
-
@Phaedrux
Made some progress. I uplaoded files without any magic smoke.
But the last 3 termistiors do show -273°CAny idea what it could be?
-
@MIke-1 said in Thermistor 104nt-4-r025h42g:
But the last 3 termistiors do show -273°C
Can you show a screenshot of what you mean?
Can you send M98 P"config.g" in the gcode console and copy paste the results here?
-
@Phaedrux said in Thermistor 104nt-4-r025h42g:
M98 P"config.g"
M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Error: Unknown pin name 'fan3'
Error: Fan number 3 not found
Error: Unknown pin name 'fan4'
Error: Fan number 4 not found
Error: Unknown pin name 'fan5'
Error: Fan number 5 not found
Error: Unknown pin name 'fan6'
Error: Fan number 6 not found
Error: Unknown pin name 'fan7'
Error: Fan number 7 not found
Error: Unknown pin name 'fan8'
Error: Fan number 8 not found
Warning: Macro file config-override.g not found
Have to got to work now
-
If you get a temperature of -273°C, this indicates an open circuit, i.e. nothing is connected to the defined pins:
Check that the temperature sensor is connected to the correct pins
Check the wiring for breaks
Measure the resistance of the wires that connect to the Duet, and that it corresponds with what the firmware expects
Check that the configuration is set correctly for the temperature sensor. -
@MIke-1 said in Thermistor 104nt-4-r025h42g:
Error: Fan number 3 not found
Error: Unknown pin name 'fan4'
Error: Fan number 4 not found
Error: Unknown pin name 'fan5'
Error: Fan number 5 not found
Error: Unknown pin name 'fan6'
Error: Fan number 6 not found
Error: Unknown pin name 'fan7'
Error: Fan number 7 not found
Error: Unknown pin name 'fan8'
Error: Fan number 8 not foundFor the fan names you'll need to use the actual fan pin names of where they are connected. Such as duex.fan# etc
