RRF3 and PT100/Thermocouple daughterboards



  • Updating to RRF3 and I'm struggling with temperature sensors.

    I found information on the daughterboard port names "spi.cs0" etc., but I've been unable to get my temperature sensors to go live.

    Bed temp is a PT100 into a daughterboard direct on the Duet2 WiFi. Extruders are type K thermocouples into a stacked daughterboard.

    Would appreciate some spoon-feeding regarding the configuration.

    Here's my V2 config.g heater-related lines
    ; Heaters
    M307 H0 B1 ; bang-bang mode for the bed heater
    M305 P0 X200 ; configure PT100 for heater 0
    M143 H0 S120 ; set temperature limit for heater 0 to 120C
    M305 P1 X152 ; configure thermocouple for heater 1
    M143 H1 S310 ; set temperature limit for heater 1 to 310C
    M305 P2 X153 ; configure thermocouple for heater 2
    M143 H2 S310 ; set temperature limit for heater 2 to 310C

    Here is the current state of my V3 config heaters section - comments have not been updated from what came out of the config tool.
    M308 S0 P"spi.cs0" A"BED" Y"rtd-max31865" ; configure sensor 0 as thermistor on pin bedtemp
    M950 H0 C"spi.cs0" T0 ; create bed heater output on bedheat and map it to sensor 0
    M307 H0 B1 S1.00 ; enable 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.cs3" A"E0" Y"thermocouple-max31856" K"k" ; configure sensor 1 as thermistor on pin e0temp
    M950 H1 C"spi.cs3" 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 S310 ; set temperature limit for heater 1 to 310C
    M308 S2 Y"drivers" A"DRIVERS" ; configure sensor 2 as temperature warning and overheat flags on the TMC2660 on Duet
    M308 S3 Y"mcu-temp" A"MCU" ; configure sensor 3 as thermistor on pin e1temp for left stepper

    E0 shows up under the Extra tab reporting the correct temp, but it's not associated with the tool.

    BED doesn't show up at all.

    MCU reports under the Extra tap and on the MCU temperature in status. Drivers shows 0.0.

    I appreciate your help.


  • Moderator

    Can you send M98 P"config.g" and M122 and report the results? Just to confirm the firmware version installed and check for any syntax errors.

    Here's an example of a working PT100 config.

    M308 S1 P"spi.cs1" Y"rtd-max31865"                 ; configure sensor 1 as thermocouple via CS pin spi.cs1
    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 S300                                       ; set temperature limit for heater 1 to 300c
    


  • M98 P"config.g"
    

    HTTP is enabled on port 80
    FTP is disabled
    TELNET is disabled
    Error: Unknown pin name 'spi.cs0'
    Error: Unknown pin name 'spi.cs0'
    Error: Heater 0 not found
    Error: Heater 0 does not exist
    Error: Pin 'spi.cs3' is not free
    Error: Heater 1 not found
    Error: Heater 1 does not exist
    Warning: the height map was loaded when the current Z=0 datum was not determined probing. This may result in a height offset.
    Error: Heater 0 not found
    Error: Heater 1 not found
    Error: Heater 2 not found
    Error: Heater 4 not found
    Error: Heater 5 not found
    Error: Heater 6 not found
    Error: Heater 7 not found

    M122
    === Diagnostics ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet WiFi 1.02 or later
    Board ID: 08DJM-9178L-L4MSN-6JKD0-3SJ6S-K93AQ
    Used output buffers: 3 of 24 (18 max)
    === RTOS ===
    Static ram: 27980
    Dynamic ram: 93764 of which 236 recycled
    Exception stack ram used: 496
    Never used ram: 8596
    Tasks: NETWORK(ready,388) HEAT(blocked,1272) MAIN(running,1880) IDLE(ready,80)
    Owned mutexes: WiFi(NETWORK)
    === Platform ===
    Last reset 00:38:07 ago, cause: software
    Last software reset at 2020-12-11 22:59, reason: User, spinning module GCodes, available RAM 9004 bytes (slot 1)
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN
    Error status: 0
    MCU temperature: min 32.2, current 33.1, max 33.7
    Supply voltage: min 24.0, current 24.2, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
    Driver 0: standstill, SG min/max 0/274
    Driver 1: standstill, SG min/max 0/241
    Driver 2: standstill, SG min/max 0/1023
    Driver 3: standstill, SG min/max not available
    Driver 4: standstill, SG min/max not available
    Date/time: 2020-12-11 23:37:39
    Cache data hit count 3699721385
    Slowest loop: 10.07ms; fastest: 0.14ms
    I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
    === Storage ===
    Free file entries: 10
    SD card 0 detected, interface speed: 20.0MBytes/sec
    SD card longest read time 3.8ms, write time 2.8ms, max retries 0
    === Move ===
    Hiccups: 0(0), FreeDm: 169, MinFreeDm: 167, MaxWait: 525838ms
    Bed compensation in use: mesh, comp offset 0.000
    === MainDDARing ===
    Scheduled moves: 20, completed moves: 20, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
    === AuxDDARing ===
    Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
    === Heat ===
    Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
    === GCodes ===
    Segments left: 0
    Movement lock held by null
    HTTP is idle in state(s) 0
    Telnet is idle in state(s) 0
    File is idle in state(s) 0
    USB is idle in state(s) 0
    Aux is idle in state(s) 0
    Trigger is idle in state(s) 0
    Queue is idle in state(s) 0
    Daemon is idle in state(s) 0
    Autopause is idle in state(s) 0
    Code queue is empty.
    === Network ===
    Slowest loop: 202.38ms; fastest: 0.00ms
    Responder states: HTTP(2) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
    HTTP sessions: 1 of 8

    • WiFi -
      Network state is active
      WiFi module is connected to access point
      Failed messages: pending 0, notready 0, noresp 0
      WiFi firmware version 1.23
      WiFi MAC address 84:0d:8e:b3:59:bd
      WiFi Vcc 3.41, reset reason Unknown
      WiFi flash size 4194304, free heap 24584
      WiFi IP address 192.168.1.130
      WiFi signal strength -62dBm, reconnections 0, sleep mode modem
      Socket states: 4 0 0 0 0 0 0 0
      === Filament sensors ===
      Extruder 0 sensor: ok


  • @zemlin said in RRF3 and PT100/Thermocouple daughterboards:

    Error: Unknown pin name 'spi.cs0'
    Error: Unknown pin name 'spi.cs0'

    there no spi.cs0 it starts at 1

    Warning: the height map was loaded when the current Z=0 datum was not determined probing. This may result in a height offset.

    remove the loading of the heightmap from the config.g and move it to the start g code after the G28

    M950 H1 C"spi.cs3" T1 ; create nozzle heater output on e0heat and map it to sensor 1

    that is not a heater channel. do you mean e0heat



  • Thank you both. It appears I got it sorted with your help.

    Current state of my heater/sensor setup:

    ; Heaters
    M308 S0 P"spi.cs1" Y"rtd-max31865"                 ; configure sensor 0 as RTD on pin spi.cs1
    M950 H0 C"bedheat" T0                              ; create bed heater output on bedheat and map it to sensor 0
    M307 H0 B1 S1.00                                   ; enable bang-bang mode for heater
    M143 H0 S120                                       ; set temperature limit for heater 1 to 120c
    M140 H0                                            ; map heated bed to heater 0
    M143 H0 S120                                       ; set temperature limit for heater 0 to 120C
    M308 S1 P"spi.cs3" A"Tool 0" Y"thermocouple-max31856" K"k"   ; configure sensor 1 as thermocouple on pin spi.cs3
    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 S310                                       ; set temperature limit for heater 1 to 310C
    M308 S2 P"spi.cs4" A"Tool 1" Y"thermocouple-max31856" K"k"   ; configure sensor 2 as thermistor on pin spi.cs4
    M950 H2 C"e1heat" T2                               ; create nozzle heater output on e1heat and map it to sensor 2
    M307 H2 B0 S1.00                                   ; disable bang-bang mode for heater  and set PWM limit
    M143 H2 S310                                       ; set temperature limit for heater 2 to 310C
    M308 S4 Y"mcu-temp" A"MCU"                         ; configure sensor 4 as MCU temp
    

  • Moderator

    @zemlin said in RRF3 and PT100/Thermocouple daughterboards:

    Error: Unknown pin name 'spi.cs0'
    Error: Unknown pin name 'spi.cs0'
    Error: Heater 0 not found
    Error: Heater 0 does not exist
    Error: Pin 'spi.cs3' is not free
    Error: Heater 1 not found
    Error: Heater 1 does not exist
    Warning: the height map was loaded when the current Z=0 datum was not determined probing. This may result in a height offset.
    Error: Heater 0 not found
    Error: Heater 1 not found
    Error: Heater 2 not found
    Error: Heater 4 not found
    Error: Heater 5 not found
    Error: Heater 6 not found
    Error: Heater 7 not found

    Were you able to eliminate all those?



  • @Phaedrux

    M98 P"config.g"
    HTTP is enabled on port 80
    FTP is disabled
    TELNET is disabled
    Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 687C
    

    I haven't tuned heater 1.


  • Moderator

    The warning is normal. Just letting you know what it thinks a runaway power temp might reach.


Log in to reply