@phaedrux
Sorry, too many irons in the fire...
Not sure about grounding on the EVA, so probably not. I'll have to look into that.
I've been running without issue on the second thermistor.
I'll try a quick look at the sense resistor the next time I have some spare cycles.
Thanks for the info!
@mr_phelps
I've switched to the second thermistor input and that is working. So I'm back to printing! 
@mr_phelps
Oops, forgot to say that the sensor is currently reading the correct ambient temperature. Same as the bed thermistor.
@phaedrux
Purchased June 4, 2022 from Matterhackers in the US.
I have the Rapido thermistor directly connected to the Duet 3 6HC on Temp1. Though now I'm getting "Heater 1 fault: failed to read sensor: unknown sensor." which is old, since I was running a direct connection before I put the toolboard in. 
I may just have syntax wrong somewhere.
; config.g
; executed by the firmware on start-up
; RepRapFirmware 3.4.0 configuration for V-Core 3 500x500 with
; - Duet 3 Mainboard 6HC
; - Duet 3 Toolboard 1LC (on default CAN ID #121)
; - Duet Paneldue 7i (not yet)
; - Duet Filament Monitor (not yet)
; - Super PINDA
; - Keenovo silicone heater pad 480x480 (1500W) 110V
; - Keenovo C-Lin SSR 40A440VAC solid state relay
; - Phateus Rapoido Hotend
; - 104NT-4-Ro25H42G/ Element's maximum heat resistance : 290c
; - BondTech LGX extruder (e-steps value : 400 using 32 microsteps, stepper 1.8 current rating: 1A/Phase, recomended 0.45A - 0.6A max 0.7A) (need to check this)
; - Steppers X,Y and Z: LDO 1.8 48mm LDO-42STH47-2504AC (current rating: 2.5A/Phase)
; General preferences
G4 S3 ; wait for tool board to start
M575 P1 S1 B57600 ; enable support for PanelDue
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"V-Core 3" ; set printer name
M669 K1 ; CoreXY
G29 S1 ; Set Units to Millimeters
; Network
M552 P192.168.1.100 S1 ; enable network and assign adx
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet
; Drives
M569 P0.0 S0 D3 ; physical drive 0.0 goes forwards
M569 P0.1 S0 D3 ; physical drive 0.1 goes forwards
M569 P0.2 S0 D3 ; physical drive 0.2 goes forwards
M569 P0.3 S1 D3 ; physical drive 0.3 goes forwards
M569 P0.4 S1 D3 ; physical drive 0.4 goes forwards
M569 P0.5 S1 D3 ; physical drive 0.5 goes forwards
M584 X0.4 Y0.3 Z0.0:0.1:0.2 E121.0 ; set drive mapping
M350 X16 Y16 Z16 E32 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z800.00 ; set steps per mm
;M906 X1600 Y1600 Z1600 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout
M566 X4000.00 Y4000.00 Z6.00 E2000.00 P1 ; set maximum instantaneous speed changes (mm/min)
M203 X8000.00 Y8000.00 Z300.00 E3600.00 ; set maximum speeds (mm/min)
;M203 X10800.00 Y10800.00 Z1000.00 E3600.00 ; Increase it up when you have it all working set maximum speeds (mm/min)
M201 X3000.00 Y3000.00 Z200.00 E2400.00 ; set accelerations (mm/s^2)
;M201 X3000.00 Y3000.00 Z100.00 E3600.00 ; Increase it when you have it all working set accelerations (mm/s^2)
;Driver Current -Affected by speed. if you go over 6000 Accel you will need more current.
M906 X1600 Y1600 Z1600 E600 I50 ; Z is very heavy on 500 I needed 1000+ set motor currents (mA) and motor idle factor in percent
M84 S30 ; Set idle timeout
; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X510 Y500 Z500 S0 ; set axis maxima
; Endstops
M574 X1 S1 P"121.io1.in" ; configure active high endstops
M574 Y2 S1 P"io1.in" ; configure active high endstops
M671 X-4.5:250:504.5 Y-4.52:505:-4.52 S5 ; define positions of Z leadscrews or bed levelling screws
M557 X25:475 Y25:475 P7 ; define 7x7 mesh grid
; Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B3950 A"Bed" ; configure sensor 0 as thermistor on pin temp0
M950 H0 C"out1" T0 ; create bed heater output on out5 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 S110 ; set temperature limit for heater 0 to 110C
;; Run Bed PID Tune!! Bellow is an example for a 300x300 bed
M307 H0 B0 R0.162 C521.5 D1.74 S1.00 V23.8
;; M307 H1 A303.1 C356.7 D1.4 S1.00 V24.0 B0
; Fans
M950 F0 C"121.out2" Q500 ; create fan 1 on pin out3 and set its frequency
M106 P0 C"Hotend Fan" S0 H1 T45 L255 ; set fan 1 name and value. Thermostatic control turned on for Hotend
M950 F1 C"121.out1" Q500 ; create fan 0 on pin out4 and set its frequency
;M950 F0 C"out4+out4.tach" Q500
;M106 P0 C"Layer Fan" S0 H-1 L255 ; set fan 0 name and value. Thermostatic control is turned off
M106 P1 C"Layer Fan" S0 H-1
; Tools
M563 P0 D0 H1 F1 ; define tool 0
G10 P0 X0 Y0 Z0.0 ; set tool 0 axis offsets
G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C
M950 H1 C"121.out0" T1 ; create nozzle heater output on out2 and map it to sensor 1
M307 H1 R4.098 K0.573:0.233 D4.53 E1.35 S1.00 B0 V23.4 ;output from PID tune - for Rapido
;M307 H1 R4.590 K0.563:0.541 D1.37 E1.35 S1.00 B0 V23.5 ;output from PID tune - old for Revo
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S300 ; set the maximum temperature in C for heater
; EVA 3 / LGX / Rapido
M92 E830 ; set extruder steps per mm, 0.9 angle/step (LDO Pancake)
M906 E800 ; set extruder motor current (mA) and idle factor in per cent
;M308 S1 P"121.temp0" Y"thermistor" T100000 B4725 C7.060000e-8 A"Hotend"
M308 S1 P"temp1" Y"thermistor" T100000 B4725 C7.060000e-8 A"Hotend"
;; Run Heater PID Tune!!
;; M307 H2 A751.5 C196.6 D4.7 S1.00 V23.9 B0
; Z-Probe
;; Inductive Probe
M557 X10:480 Y10:480 S30 ;Set mesh grid
M558 P8 C"121.io2.in" H5 F400 T5000 A5 ; set Z probe type to unmodulated and the dive height + speeds
G31 P500 X-30 Y-15 Z0.52 ; set Z probe trigger value, offset and trigger height, more Z means closer to the bed
;Accelerometer
M955 P121.0 I10 ; specify orientation of accelerometer on Toolboard 1LC with CAN address 121
M593 P"mzv" F37
T0
; Pressure Advance
M572 D0 S0.05
@phaedrux
Sorry, should have given more info. Was a late night and a little bit frustrated.
The Ver 1.2 toolboard had probably close to 200 hours of print time. The printer was working with mostly just chasing some movement issues around small, rapid movements.
I saw an error of 2000c on the hotend thermistor a couple of times that I was able to fix with a power cycle. But then the toolboard faulted out and was stuck at 423c whether a thermistor was connected or not.
I have since wired the hotend thermistor directly to the 6HC and it reads correctly. So definitely a problem with the toolboard. Is this a warrenty thing or do I have to buy a replacement board?
Thanks,
Mike
I should point out that two different hotends report the same behavior and I can measure the resistance of the thermistor all the way to the toolboard.
I am running Duet 3 MB6HC with Toolboard Ver. 1.2, both at 3.4.1
I saw a few 2000c errors before that cleared with a power cycle.
Running a Ratrig VCore 3 500
Here is the M122 messages.
9/20/2022, 7:03:30 PM M122 B121.0
Diagnostics for board 121:
Duet TOOL1LC rev 1.1 or later firmware version 3.4.1 (2022-06-01 21:16:39)
Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
All averaging filters OK
Never used RAM 2592, free system stack 88 words
Tasks: Move(notifyWait,0.0%,153) HEAT(notifyWait,0.2%,61) CanAsync(notifyWait,0.0%,65) CanRecv(notifyWait,0.0%,76) CanClock(notifyWait,0.0%,65) ACCEL(notifyWait,0.0%,61) TMC(notifyWait,3.0%,57) MAIN(running,91.9%,351) IDLE(ready,0.0%,26) AIN(delaying,4.9%,142), total 100.0%
Last reset 00:21:40 ago, cause: power up
Last software reset data not available
Driver 0: pos 0, 830.0 steps/mm,standstill, SG min 0, read errors 0, write errors 0, ifcnt 14, reads 60527, writes 14, timeouts 0, DMA errors 0, CC errors 0, steps req 0 done 0
Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
Peak sync jitter 1/6, peak Rx sync delay 213, resyncs 0/0, no step interrupt scheduled
VIN voltage: min 23.7, current 23.7, max 23.7
MCU temperature: min 37.4C, current 40.1C, max 40.1C
Last sensors broadcast 0x00000002 found 1 16 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 26019, send timeouts 0, received 11720, lost 0, free buffers 37, min 37, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
Accelerometer: LIS3DH, status: 00
I2C bus errors 0, naks 3, other errors 0
9/20/2022, 7:02:55 PM M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.1 (2022-06-01 21:09:01) running on Duet 3 MB6HC v1.01 or later (standalone mode)
Board ID: 08DJM-956BA-NA3TJ-6J1FD-3S06T-KU8UT
Used output buffers: 1 of 40 (13 max)
=== RTOS ===
Static ram: 151000
Dynamic ram: 95884 of which 520 recycled
Never used RAM 103268, free system stack 200 words
Tasks: NETWORK(ready,27.5%,209) ETHERNET(notifyWait,0.1%,173) HEAT(notifyWait,0.0%,321) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,772) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,339) TMC(notifyWait,7.7%,92) MAIN(running,64.7%,925) IDLE(ready,0.0%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:21:05 ago, cause: power up
Last software reset at 2022-09-18 09:47, reason: User, GCodes spinning, available RAM 99788, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 142
MCU temperature: min 25.7, current 38.5, max 38.8
Supply voltage: min 23.8, current 23.9, max 23.9, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.2, max 12.3, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 1 queued, 1 completed
Driver 0: standstill, SG min 0, mspos 8, reads 13859, writes 15 timeouts 0
Driver 1: standstill, SG min 0, mspos 8, reads 13859, writes 15 timeouts 0
Driver 2: standstill, SG min 0, mspos 8, reads 13859, writes 15 timeouts 0
Driver 3: standstill, SG min 0, mspos 8, reads 13859, writes 15 timeouts 0
Driver 4: standstill, SG min 0, mspos 8, reads 13859, writes 15 timeouts 0
Driver 5: standstill, SG min 0, mspos 8, reads 13862, writes 12 timeouts 0
Date/time: 2022-09-20 19:02:54
Slowest loop: 11.08ms; fastest: 0.05ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 3.3ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== 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
LCD is idle in state(s) 0
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== CAN ===
Messages queued 11398, received 25292, lost 0, boc 0
Longest wait 3ms for reply type 6053, peak Tx sync delay 268, free buffers 50 (min 49), ts 6329/6328/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 22.49ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
HTTP sessions: 1 of 8
@jay_s_uk Thanks! Looks like that worked. When the controller on my Prusa 2.5 finally died I swapped over to the Duet Mini 5+. Probably got the z connectors reversed by accident.
If I manually level the bed I get a good first layer.
When I run G32 it seems to make the adjustment in the wrong direction.
Here is the z parts of config.g:
M584 X1 Y2 Z0:4 E3 ; set drive mapping
M671 X-37:287 Y0:0 S10 ; define dual driven z-axis
Here is bed.g:
; bed.g
; called to perform automatic bed compensation via G32
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Mon Mar 15 2021 19:09:36 GMT+0100 (Mitteleuropäische Normalzeit)
M561 ; Clear any existing bed transform.
G28 ; home
M558 F100 A5 S0.003
G30 P0 X15 Y125 Z-99999 ; probe near a leadscrew, half way along Y axis
G30 P1 X205 Y125 Z-99999 S2 ; probe near a leadscrew and calibrate 2 motors
M558 F200 A1
G1 X10 Y210 Z10 F10000
Any suggestions on what I am doing wrong?
Thanks,
Mike
@phaedrux Running two printers of my Surface (other printer is a Prusa Mk 2.5S that I changed to Duet 5 Mini board.)
So I shut everything down. Power cycled the Surface. Open DWC and grabbed the file you linked (thanks for that) and ran the upgrade. This time it worked. Not sure if for some reason the web browser was the thing not letting the upgrade finish.
But now, with latest firmware, the plugin sees the accelerometer and it actually ran the routine.
So I think we are good to go. Thanks for all the help!
@mr_phelps Tried to upgrade to 3.4.1 but it still shows as 3.4.0 and still getting the Accelerometer not found issue.
Was trying to use the Machine specific tab and went through several tries. Downloaded both versions of the upgrade that I could find (Master and SD) but same results each time. Had to set it aside as the next print needs to start. ~24 hour print and these have to be done before the end of the week. (Though that only gets one set out when I need two. Second set will have to ship to France next week.)
@chrishamm The current part will finish in a few hours. Once that is done I can try your request. DWC is 3.4.0.
I'm still not great at upgrading, so that might take a little bit once I get back from work.
@dc42 I will try that once the current print finishes. When you say clicking on the tool in DWC, do you mean "Tool 0" in the Tools and Extra window?
@mr_phelps Poked at it a little between prints. I can get data from the M956 command. So the machine can talk to the accelerometer. But there is no option to select a tool when I try to use the plugin. As soon as I select "Record Motion Profile" it dumps me out with the not found error.
@mr_phelps Just to be clear, how do select a tool? I can't mess with the menu at the moment. I don't want to risk the 16 hour print.
@dc42 Ah, I will try that as soon as the current print finishes. Should be in 4 hours or so. In a time crunch to get work parts out.
Thanks for your time!
@dc42 When I use the Input Shaper plugin to try to generate a motion profile it returns with the "Accelerometer not found" pop-up.
I had a LIS3DH installed before an that worked fine.
If I query with M955 the machine returns with 121:0 with orientation 10.
If I query with M122 B121 it comes back yes with status 00
I am running a Duet 3 6HC with a Tool board V1.2 using the Duet web interface to run the printer.
Printer is a VCore 500.
What am I doing wrong?