Bad PT100 board?
-
@shadowx said in Bad PT100 board?:
M350 X16 X16 X16 X16 I1
I don't know if this is intentional, but you're setting the microstepping for the X axis 4 times in a row here but not the other axis.
As for your PT100 problems, have you tried reseating the board in it's connector yet?
Can you measure the resistance of R1 and R2 resistors? They should read ~400 ohms.
@shadowx said in Bad PT100 board?:
Just as a sanity check, I unplugged the wires and put in a 100 ohm resistor in the terminals shown with red arrows. I can't read 0 degrees on my PanelDue or web interface. There is no temperature display for the extruder.
What exactly does it display for a temperature?
Finally, can you send M98 P"config.g" just to check for any syntax errors in your config?
-
@shadowx with that board revision, when using a 2-wire connection or testing with the resistor, you need to add a link wire between terminals 1 and 2 and another between 3 and 4 (with the resistor fitted between terminals 2 and 3 as you have indicated), or alternatively put solder bridges across the pads provided.
-
@phaedrux said in Bad PT100 board?:
@shadowx said in Bad PT100 board?:
M350 X16 X16 X16 X16 I1
I don't know if this is intentional, but you're setting the microstepping for the X axis 4 times in a row here but not the other axis.
That is an error on my part. The error has been there since 2018 and earlier that I overlooked. I have fixed the setting as shown in the results on the bottom of this reply.As for your PT100 problems, have you tried reseating the board in it's connector yet?
I reseated the board multiple times. I took the board in and out at least 5 times.Can you measure the resistance of R1 and R2 resistors? They should read ~400 ohms.
They are both about 400.1-400.5 ohms@shadowx said in Bad PT100 board?:
Just as a sanity check, I unplugged the wires and put in a 100 ohm resistor in the terminals shown with red arrows. I can't read 0 degrees on my PanelDue or web interface. There is no temperature display for the extruder.
What exactly does it display for a temperature? The PanelDue screen does not show temperature for the extrude and the web interface shows the bottom image.
Finally, can you send M98 P"config.g" just to check for any syntax errors in your config?
Here are the error messages that came back. This is after fixing the M350 command to:
M350 X16 Y16 Z16 E16 I1M98 P"config.g" Error: in file macro line 31 column 19: M350: array too long, max length = 0 Error: in file macro line 32 column 25: M906: array too long, max length = 0 Error: in file macro line 36 column 24: M566: array too long, max length = 0 Error: in file macro line 37 column 25: M201: array too long, max length = 0 Error: in file macro line 38 column 28: M203: array too long, max length = 0 Error: in file macro line 41 column 18: M92: array too long, max length = 0 Error: Invalid extruder number '0' Error: bad drive number Error: Tool 0 not found Error: Tool 0 not found
At first, after fixing the M350 command, the whining noise was gone and the PanelDue shows "Tool 0 not found". The macro turns on the bed heater bed, but I get the "tool 0 not found" error message. I thought fixing the M350 solved the noise issue at the time.
However, if I shut off the printer and restart it, the noise is back if I run the heater macro right away. After I home the printer, the noise is gone when I start my heater. I guess that noise is related to the motors and homing the printer first before I turn on the heater stopped that noise from happening. Note, when the motors where whining, I did not get a tool error on the panelDue, however, I had to use the stop button or that noise would not stop. After the printer homed, I had no more noise and that tool error message popped right up.
G10 P0 R0 S190 ; Set standby and extruder temp to 200C M140 S65 H0 ; Set heated bed initial value to 65C T0 ; Select Tool 0 to turn on the extruder to active
Thanks for all your help.
-
@dc42 said in Bad PT100 board?:
@shadowx with that board revision, when using a 2-wire connection or testing with the resistor, you need to add a link wire between terminals 1 and 2 and another between 3 and 4 (with the resistor fitted between terminals 2 and 3 as you have indicated), or alternatively put solder bridges across the pads provided.
I use a 4 wire system on my printer. My measurement between the two middle terminal (2 &3) is around 120 ohms. Between connection 1&2, I get around 1.1 ohms and 3&4, I get 1.2 ohms.
On the 100 ohm resistor test, I attached a short jumper cable between 1&2 and 3&4 and still had the same results. The jumper wires measured around 0.7 or 0.8 ohms. Note, these measurements are on the top screws of the terminals on the PWB boards. I wasn't able to probe the bottom solder pads unless I remove the boards.
I just hope it wasn't something stupid I did on the configuration file like left out a semi colon somewhere or added an extra space. I don't believe I changed anything, but its been a least a week since my last print.
I compared it to my last backup in June and I don't see any differences in the extruder heater or tool settings.
-
@shadowx said in Bad PT100 board?:
On the 100 ohm resistor test, I attached a short jumper cable between 1&2 and 3&4 and still had the same results. The jumper wires measured around 0.7 or 0.8 ohms. Note, these measurements are on the top screws of the terminals on the PWB boards. I wasn't able to probe the bottom solder pads unless I remove the boards.
Those measurements sound good. Does the second channel on the PT100 board behave in the same way when you test using the 100 ohm resistor?
-
@dc42 said in Bad PT100 board?:
@shadowx said in Bad PT100 board?:
On the 100 ohm resistor test, I attached a short jumper cable between 1&2 and 3&4 and still had the same results. The jumper wires measured around 0.7 or 0.8 ohms. Note, these measurements are on the top screws of the terminals on the PWB boards. I wasn't able to probe the bottom solder pads unless I remove the boards.
Those measurements sound good. Does the second channel on the PT100 board behave in the same way when you test using the 100 ohm resistor?
Yes. I was only able to test the second channel since the terminals on the RTD1 broke off. I can solder the wires or a connector to the RTD1 solder pads to test.
I have a Kingst LA1010 logic analyzer. Is there certain pins I can connect to on the board to check if I get the proper signals from the RTD board? I recall there was a schematic available somewhere but don't have the links to them anymore. I guess the basic checks is for power first to the board and then any output signals from the SPI interface.
Thanks for you help.
-
There are some issues with your config.g perhaps from the manual transition to RRF3. Here's a clean basic config.g I created in the config tool you can use to start with and modify with your specifics. I tried to copy over as much as I could.
I think part of the problem for those errors is that you lack an M584 command to define the drivers and axis. The whining noise may be due to incorrect defaults being applied for the drivers.
; Configuration file for Duet WiFi (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.3.0 on Fri Aug 06 2021 12:30:20 GMT-0600 (Central Standard Time) ; General preferences M575 P1 S1 B57600 ; enable support for PanelDue G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"My Printer" ; set printer name M665 R105.6 L215 B85 H250 ; Set delta radius, diagonal rod length, printable radius and homed height M666 X0 Y0 Z0 ; put your endstop adjustments here, or let auto calibration find them ; Network M552 S1 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P0 S1 ; physical drive 0 goes forwards M569 P1 S1 ; physical drive 1 goes forwards M569 P2 S1 ; physical drive 2 goes forwards M569 P3 S0 ; physical drive 3 goes backwards M584 X0 Y1 Z2 E3 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X80.00 Y80.00 Z80.00 E2680.00 ; set steps per mm M566 X900.00 Y900.00 Z900.00 E1200.00 ; set maximum instantaneous speed changes (mm/min) M203 X18000.00 Y18000.00 Z18000.00 E3000.00 ; set maximum speeds (mm/min) M201 X2000.00 Y2000.00 Z2000.00 E3000.00 ; set accelerations (mm/s^2) M906 X1000 Y1000 Z1000 E800 I30 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 Z0 S1 ; set minimum Z ; Endstops M574 X2 S1 P"xstop" ; configure active-high endstop for high end on X via pin xstop M574 Y2 S1 P"ystop" ; configure active-high endstop for high end on Y via pin ystop M574 Z2 S1 P"zstop" ; configure active-high endstop for high end on Z via pin zstop ; Z-Probe M558 P1 C"zprobe.in" H5 F480 T6000 ; set Z probe type to unmodulated and the dive height + speeds G31 P500 X0 Y0 Z0.08 ; set Z probe trigger value, offset and trigger height M557 R85 S20 ; define mesh grid ; Heaters M308 S0 P"bedtemp" Y"thermistor" T100000 B3950 ; configure sensor 0 as thermistor on pin bedtemp M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0 M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M143 H0 S120 ; set temperature limit for heater 0 to 120C M308 S1 P"spi.cs2" Y"rtd-max31865" ; configure sensor 1 as thermocouple via CS pin spi.cs2 M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1 M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit M143 H1 S280 ; set temperature limit for heater 1 to 280C ; Fans M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency M106 P1 S0 H-1 ; set fan 1 value. Thermostatic control is turned off M950 F2 C"fan2" Q500 ; create fan 2 on pin fan2 and set its frequency M106 P2 S0 H-1 ; set fan 2 value. Thermostatic control is turned off ; Tools M563 P0 D0 H1 F0 ; 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 ; Custom settings are not defined ; Miscellaneous M501 ; load saved parameters from non-volatile memory T0 ; select first tool
-
@shadowx said in Bad PT100 board?:
@dc42 said in Bad PT100 board?:
@shadowx said in Bad PT100 board?:
On the 100 ohm resistor test, I attached a short jumper cable between 1&2 and 3&4 and still had the same results. The jumper wires measured around 0.7 or 0.8 ohms. Note, these measurements are on the top screws of the terminals on the PWB boards. I wasn't able to probe the bottom solder pads unless I remove the boards.
Those measurements sound good. Does the second channel on the PT100 board behave in the same way when you test using the 100 ohm resistor?
Yes. I was only able to test the second channel since the terminals on the RTD1 broke off. I can solder the wires or a connector to the RTD1 solder pads to test.
I have a Kingst LA1010 logic analyzer. Is there certain pins I can connect to on the board to check if I get the proper signals from the RTD board? I recall there was a schematic available somewhere but don't have the links to them anymore. I guess the basic checks is for power first to the board and then any output signals from the SPI interface.
Thanks for you help.
If you send command M308 S# (where #s the sensor number) with no additional parameters, what is the response? I am assuming you are running RRF 3.
How did the terminals of RTD1 break off? If that was caused by physical damage, perhaps you should just buy another daughter board? They are not expensive, and judging by the version in the photo you attached I suspect you have had that one for several years.
-
@dc42 I think the photo he has in his first post is just the photo used from the wiki page for the PT100 board, not his own board, so not indicative of the version he has.
https://duet3d.dozuki.com/Wiki/Connecting_PT100_temperature_sensors
-
@phaedrux thanks, I didn't consider that.