PT-100 temperature constantly at 2000 degrees after failure
-
Maybe it's because you've set P1 to use both channels (X200 and X201). If you've only got one PT100 and it's used on the hot end, all you need is M305 P1 X200. If you are using 2 PT100s, one for the bed and one for the hot end, then you have something like M305 P0 X200 and M305 P1 X201. You don't need the thermistor and ADC parameters for a PT 100 but those lines probably just get ignored.
-
Can you post your full Config.g file wonder if there is a line after the M305 that may be overriding it?
Doug
Ian I think the op has tried all those lines one at a time to try and get to the bottom of the issue not all at the same time
-
The strange thing is that it used to work before until it failed in the beginning of a print. Since then i only fiddled around with the M305 P1 command.
[[language]] ; Configuration file for Duet WiFi (firmware version 1.17) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool on Wed Apr 19 2017 22:18:05 GMT+0200 (W. Europe Daylight Time) ; General preferences M111 S0 ; Debugging off G21 ; Work in millimetres G90 ; Send absolute coordinates... M83 ; ...but relative extruder moves M555 P2 ; Set firmware compatibility to look like Marlin M208 X0 Y0 Z0 S1 ; Set axis minima M208 X205 Y205 Z205 S0 ; Set axis maxima ; Endstops M574 X1 Y1 Z1 S1 ; Define active high microswitches M558 P0 X0 Y0 Z0 H5 F120 T6000 ; Set Z probe type to switch, the axes for which it is used and the probe + travel speeds G31 P600 X0 Y0 Z0 ; Set Z probe trigger value, offset and trigger height M557 X15:190 Y15:190 S20 ; Define mesh grid ; Drives M569 P0 S1 ; Drive 0 goes forwards M569 P1 S1 ; Drive 1 goes forwards M569 P2 S1 ; Drive 2 goes forwards M569 P3 S1 ; Drive 3 goes forwards M350 X16 Y16 Z8 E16 I0 ; Configure microstepping without interpolation M92 X157.4804 Y157.4804 Z533.3333 E832 ; Set steps per mm M566 X1200 Y1200 Z480 E120 ; Set maximum instantaneous speed changes (mm/min) M203 X8100 Y8100 Z1200 E1200 ; Set maximum speeds (mm/min) M201 X500 Y20 Z250 E250 ; Set accelerations (mm/s^2) M906 X1100 Y1100 Z1100 E1100 I30 ; Set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Heaters M143 S310 ; Set maximum heater temperature to 310C M301 H0 S1.00 P10 I0.1 D200 T0.4 W180 B30 ; Use PID on bed heater (may require further tuning) M305 P0 T10000 B3988 C0 R4700 L0 H0 ; Set thermistor + ADC parameters for heater 0 M305 P1 X200 ; Tools M563 P0 D0 H1 ; Define tool 0 G10 P0 X0 Y0 Z0 ; Set tool 0 axis offsets G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C ; Network M550 PUltimaker ; Set machine name M552 P0.0.0.0 S1 ; Enable network and acquire dynamic address via DHCP ; Fans M106 P0 S1 I0 F500 H1 T45 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned on M106 P1 S1 I0 F500 H-1 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned off M106 P2 S1 I0 F500 H-1 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned off ; Custom settings are not configured -
Something to try. Go to the GCode console in DWC and send M305 P1 X0 followed by M305 P1 X200. If it can't communicate with the chip on the daughter board, it should return an error message within a few seconds. Repeat for channel 201. If you get no errors, you can test whether the error reporting is working by trying a channel you don't have such as 202 or 203.
-
Taking a step back and reading through this thread, it seems that it was all working fine then suddenly failed. Since then, you've tried a different sensor, a new daughter board and a new duet board. So how about the actual wires that link the sensor to the daughter board? That's the only thing I can think of that you haven't explicitly said has been replaced.
-
Yes the error reporting is working and i get no error when calling M305 P1 X0 and M305 P1 X200 or X201 right after that. I've tried that before.
Can I somehow debug the firmware? Maybe there i can find out what the issue is.
-
I really don't think it's a firmware issue, because other people (including me) are using PT100 sensors without this problem. Some users see temperature spikes to 2000C, caused by interference. That's why I would really like to know how your board behaves with just the 2 links and a 100 to 180 ohm resistor connected to the terminals.
-
Ok I'm going to get a resistor next week , but I don't expect to see any difference. As i said before, i can already make sure that the resistance between 2 and 3 is of around 180 ohm and the resistance between 1 and 4 is 180 ohm as well.
How can i check if the daughter-board is actually doing anything?
As the UI shows 2000° even when no daughter-board is connected at all, I think the issue must be somewhere there. I just don't get it why it i the exactly the same with the new hardware. -
The UI will show 2000C whenever a temperature reading can't be obtained after several attempts for any reason. The difference is that when you send the M305 P1 X200 command, you get an error message if no daughter board is connected. You are not getting that error message, which means that the firmware is communicating with the daughter board.
Perhaps we should include a 100 ohm resistor with the daughter boards, to help diagnose this sort of problem.
-
Well, all this because of almost nothing! Things like that always result in the smallest possible issue.
First of all I got a E3D cartridge thermistor instead of a PT100 and the second i ordered was the V6 fixing kit with contains the cartridge thermistor as well. The biggest problem is that they look exactly the the same.
The test with a 150 ohm resistor worked and gave me a result of around 130° instead of 2000°. So I ordered a real PT100 sensor and right now I'm printing all fine with the thermistor in place (logically without the daughter-board in use).Thanks for all that support.
-
I'm glad you solved it.
-
Thought this might be the thread to ask.
I got a daughterboard from T3P3 this morning (ordered yesterday so impressed).
I solder-bridged the pads on RTD1 carefully. I have attached my e3d pt100 (which reads 111ohms at room temp - 30 deg C!) to pins 2 and 3 on the screw terminal.
I added M305 P2 X200 to config.g
and M563 P99 H2 to tool definitions (planning to use this as chamber temp monitor until I get a heater block which can accept the sensor).
But no dice… 2000 deg C showing.
I've checked the daughterboard is properly located over the SPI pins with the bulk of the board facing in.
I've been into console and sent M305 P2 X0 - okay
then M305 P99 X200
"Error: failed to initialise RTD: bad response from sensor"Any ideas?
-
Try a lower number for the P parameter not sute but pretty certain the Firmware won't know about sensors numbered that high.
Sure David will be along soon to confirm or deny my assumption?
Doug
-
I'll try that sure maybe it should have been p2 or it could be something else on this board that's not quite right, but spi must work or a whole load of things would be dead which are working fine.
-
Simon,
I'm using pt100s via the daughter board for my hot end and bed. The first channel on the daughter board is X200 and the second is X201 and P is the heater number.
So what you need is M305 Pnnn X200 (or X201) where Pnnn is the heater number (not the tool number). In my case I have M305 P0 X200 for the bed, and M305 P1 X201 for the hot end.
HTH
Ian
-
Thanks guys. Okay so I tried M305 P2 X200 (and 201,202,203) but still Error: Failed to inialise RTD, bad response from sensor.
I will rule out the pt100 board being at fault by sticking it onto my other machine and seeing if I can initialise it.
-
Okay so it works fine and reads fine on my other machine, it must be this slightly iffy duetwifi board. I won't waste any more of your time. Thank you gentlemen. Enjoy your evenings.
CalvinX looks like its back to the fridge thermometer for me
-
I’m having the same issue- installed new pt100 and board and it sits at 2000.
I get 104 ohms for resistance of the PT100
2.02 volts between 1-4 on daughter board
Config file line: M305 P1 X200
Sent M305 P1 X0 followed by M305 P1 X200- no errors. No errors for channel X201 and I did get error for 202.
I’m using wire from a cat5 cable, so each pair has a slight twist to them.
They are running within a single lose bundle from the hotend to center of top of printer and down a tower leg alone. -
Okay so it works fine and reads fine on my other machine, it must be this slightly iffy duetwifi board. I won't waste any more of your time. Thank you gentlemen. Enjoy your evenings.
Do you have anything else connected to the SPI bus on that Duet, for example a PanelDue connected via a ribbon cable to CONN_SD ?
-
In my case the issue was with poor quality crimping on the original e3d pt100 sensor and not an iffy duetwifi board please consider that a retraction.
I now stock pt100s without connectors with 95cm leads for less chance of a bad connection. See my signature below.
