Tool board LC1 errors
-
I have a triple Z axes self built corexy printer that I am trying to get up and running.
I have READ AND READ and tried to glean info from various sources but its not the easiest to get up and running as to be honest the documentation is fragmented and plain incomplete.
The on-line config tool doesnt fully do the job either
I have the following
Board: Duet 3 MB6HC (MB6HC)
DSF Version: 3.1.0
Firmware: RepRapFirmware for Duet 3 MB6HC 3.1.1 (2020-05-19b2)
Rpi-3B+
I can communicate with the toolboard using M115 B121
Board TOOL1LC firmware 3.1.0 (2020-05-15b1)The hotend is an "omniadrop" with a 5:1 reduction gear that uses E3D thermistor cartridges.
12v fans as required by the toolboard, a "dumb" 2 wire ormerod X axis endstop switch and a duet3d IR sensor as the probe/z axis endstopAt start up im getting the hot end displaying 730c which is obviously going to "fault" due to M143 H1 being set to a maximum of 310c
I also get x3 other pop-up warnings
Error: G31: Invalid Z probe index Error: M558: Pin 121.io0.in is not free Warning: Board 121 does not have input handle 3000; Config for CoreXY ; ; General preferences ; G90 ; Operate the motion system with absolute positioning moves M83 ; Operate the Extruder with relative positioning moves M669 K1 ; Set the machine to operate in CoreXY mode ; ; Drives (121.XX) denotes the Can-Bus address that the toolboard LC1 is operating on ; M671 X-31:332:150 Y-10:-10:340 S5 ; The Z axes pivot point locations to allow true levelling to be undertaken M584 E121.0 S1 ; Drive mapping for the toolboard LC1 M584 X0.0 Y0.1 Z0.3:0.4:0.5 ; Drive mapping for the mainboard 6HC M569 P121.0 S1 ; Driver 121.0 is connected to the extruder motor output (Driver 0) on the toolboard LC1 & goes forwards M569 P0.1 S1 ; Driver 0.1 is connected to the Z1 axis motor (Front Left) on the mainboard 6HC & goes forwards M569 P0.2 S1 ; Driver 0.2 is connected to the Z2 axis motor (Front Right) on the mainboard 6HC & goes forwards M569 P0.3 S1 ; Driver 0.3 is connected to the Z3 axis motor (Centre Rear) on the mainboard 6HC & goes forwards M569 P0.4 S1 ; Driver 0.4 is connected to the X axis motor on the mainboard 6HC & goes forwards M569 P0.5 S1 ; Driver 0.5 is connected to the Y axis motor on the mainboard 6HC & goes forwards M350 X16 Y16 Z16 E16 I1 ; The stepper motors microstepping & interpolation amount M92 X160.00 Y160.00 Z1600.00 E480.00 ; Steps per mm of each stepper motor M566 X900.00 Y900.00 Z160.00 E160.00 ; The maximum instantaneous speed changes expressed in (mm/min) that the stepper motors are allowed to achieve M203 X6000.00 Y6000.00 Z180.00 E1200.00 ; The maximum speeds expressed in(mm/min) that the stepper motors are allowed to achieve M201 X1000.00 Y1000.00 Z120.00 E120.00 ; The maximum accelerations expressed in(mm/s^2 that the stepper motors are allowed to achieve M906 X800 Y800 Z800 E1000 I30 ; The maximum motor currents expressed in(mA) & idle factor expressed as a % that the stepper motors are allowed to achieve M84 S30 ; The idle timeout ; ; Axis Limits ; M208 X0 Y0 Z0 S1 ; Each axes minimum travel boundaries M208 X320 Y320 Z320 S0 ; Each axes maximum travel boundaries ; ; Endstops ; M574 X1 S1 P"121.io1.in" ; The X endstop is located at the X axes minimum location & is mapped/connected to the io1.in port on the toolboard LC1 M574 Y1 S1 P"io3.in" ; The Y endstop is located at the Y axes minimum location & is mapped/connected to the io3.in port on the mainboard 6HC M574 Z1 S2 ; The Z probe acts as the Z axis endstop & is located at Z axes minimum & mapped/connected to the io0 port on the toolboard LC1 ; ; Z-Probe ; M558 P8 C"121.io0.in" H5 F120 T2000 ; The Z probe is of type 8 & is mapped/connected to the io0 port on the toolboard LC1 G31 P500 X-35 Y0 Z1.00 ; The Z probe's trigger value, offsets & trigger height M557 X15:280 Y15:280 P6 ; The mesh grid's defined points ; ; Bed Heater ; M308 S0 P"temp0" Y"thermistor" T100000 B4138 A"Bed" ; Sensor 0 is a thermistor & mapped/connected to the temp0 port on the mainboard 6HC M950 H0 C"out0" T0 ; The bed heater output is mapped/connected to the out0 port & mapped/connected to sensor 0 on the mainboard 6HC M307 H0 B0 S1.00 ; The bed heater is set to PWM & limited M140 H0 ; The heated bed is mapped/connected to heater 0 port on the mainboard 6HC M143 H0 S120 ; The heated bed it temperature limited to 120C on heater 0 on the mainboard 6HC ; ; Hot End Heater M308 S1 P"121.temp0" Y"thermistor" B4725 C7.06e-8 A"Tool 0" ; Sensor1 is a thermistor & mapped/connected to the temp0 on the toolboard LC1 M950 H1 C"121.out0" T1 ; The hot end heater optput is mapped/connected to the out1 port & mapped/connected to sensor 1 on the toolboard LC1 M307 H1 B0 S1.00 ; The hot end heater is set to PWM & limited M143 H1 S310 ; The hot end temperature is limited to 310C on heater 1 on the toolboard LC1 ; ; Fans ; M950 F0 C"121.out1" ; The hot end cooling fan (fan0)is mapped/connected to out1 on the toolboard LC1 M106 P0 S0 H-1 ; The hot end cooling fan (fan0)is set to value 0 & thermostatic control is turned off M950 F1 C"121.out2" Q5000 ; The part cooling fan(fan1)is mapped/connected to out4 on the toolboard LC1 M106 P1 S1 H1 T45 ; The part cooling fan(fan1)is set to value 1 & thermostatic control turned on ; ; Tools ; M563 P0 D0 H1 F0 ; Tool 0's definition G10 P0 X0 Y0 Z0 ; Tool 0's axes offsets G10 P0 R0 S0 ; Tool 0 is set to active & it's standby temperature is set to 0C ; ; Misc Settings ; T0 ; Define which tool is selected at start up M501 ; Run any config-overide settings ;M122: === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.1.1 running on Duet 3 MB6HC v1.01 or later (SBC mode) Used output buffers: 1 of 40 (10 max) === RTOS === Static ram: 154604 Dynamic ram: 162704 of which 156 recycled Exception stack ram used: 224 Never used ram: 75528 Tasks: NETWORK(ready,1980) HEAT(blocked,1212) CanReceiv(suspended,3424) CanSender(suspended,1488) CanClock(blocked,1436) TMC(blocked,204) MAIN(running,4952) IDLE(ready,76) Owned mutexes: === Platform === Last reset 00:00:45 ago, cause: software Last software reset at 2020-10-11 22:14, reason: User, spinning module LinuxInterface, available RAM 75568 bytes (slot 3) Software reset code 0x0010 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task MAIN Error status: 0 MCU temperature: min 37.5, current 37.8, max 38.0 Supply voltage: min 24.3, current 24.3, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 12.0, current 12.1, max 12.1, under voltage events: 0 Driver 0: standstill, reads 27574, writes 14 timeouts 0, SG min/max 0/0 Driver 1: standstill, reads 27574, writes 14 timeouts 0, SG min/max 0/0 Driver 2: standstill, reads 27578, writes 11 timeouts 0, SG min/max 0/0 Driver 3: standstill, reads 27575, writes 14 timeouts 0, SG min/max 0/0 Driver 4: standstill, reads 27576, writes 14 timeouts 0, SG min/max 0/0 Driver 5: standstill, reads 27576, writes 14 timeouts 0, SG min/max 0/0 Date/time: 2020-10-11 22:14:56 Slowest loop: 3.83ms; fastest: 0.14ms === Storage === Free file entries: 10 SD card 0 not detected, interface speed: 37.5MBytes/sec SD card longest read time 0.0ms, write time 0.0ms, max retries 0 === Move === Hiccups: 0(0), FreeDm: 375, MinFreeDm: 375, MaxWait: 0ms Bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves: 0, completed moves: 0, 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 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1 === GCodes === Segments left: 0 Movement lock held by null HTTP* is ready with "M122" 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 0, running macro Aux2 is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty. === Network === Slowest loop: 1.23ms; fastest: 0.01ms 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: 0 of 8 - Ethernet - State: disabled Error counts: 0 0 0 0 0 Socket states: 0 0 0 0 0 0 0 0 === CAN === Messages sent 157, longest wait 2ms for type 6011 === Linux interface === State: 0, failed transfers: 0 Last transfer: 17ms ago RX/TX seq numbers: 1160/1162 SPI underruns 0, overruns 0 Number of disconnects: 0 Buffer RX/TX: 0/0-0 === Duet Control Server === Duet Control Server v3.1.0 Daemon: Finishing macro daemon.g, started by system > Next stack level Code buffer space: 4096 Configured SPI speed: 8000000 Hz Full transfers per second: 30.53 -
@JayJay said in Tool board LC1 errors:
At start up im getting the hot end displaying 730c which is obviously going to "fault" due to M143 H1 being set to a maximum of 310c
You're missing T100000 in your thermistor config. When using the config tool and selecting the E3D thermistor and toolboard temp0 I get this.
M308 S1 P"1.temp0" Y"thermistor" T100000 B4725 C7.06e-8What do you get when sending M98 P"config.g" ?
Can you post a photo of your wiring?
-
@Phaedrux said in Tool board LC1 errors:
M98 P"config.g"
thank you for the assistance.
I did try it with T1000000 in the M308 command and it made no difference !!!
M98 P"config.g" resulted in the following being reported (nothing else)
M98 P"config.g" Warning: M307: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365CI think its wired correctly, its a V0.6 toolboard and i followed the wiring dairgram for that version.
The thermistor is reading about 80k ohms at my current room temp
-
@JayJay said in Tool board LC1 errors:
Error: G31: Invalid Z probe index Error: M558: Pin 121.io0.in is not free Warning: Board 121 does not have input handle 3000
When do you get these error messages popping up?
-
@Phaedrux said in Tool board LC1 errors:
@JayJay said in Tool board LC1 errors:
Error: G31: Invalid Z probe index Error: M558: Pin 121.io0.in is not free Warning: Board 121 does not have input handle 3000
When do you get these error messages popping up?
At First boot then they dissappear, but i just updated the toolboard firmware and I think they have dissappeared for good now, so it seems like it is just the heater fault to overcome before I can even think about attempting to make it move.
-
@JayJay said in Tool board LC1 errors:
Warning: M307: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C
It's a warning.
-
@Phaedrux said in Tool board LC1 errors:
@JayJay said in Tool board LC1 errors:
Warning: M307: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C
It's a warning.
The guy says his issue is with H1 showing as a fault and the temperature reading is showing to be Incorrect in DWC, surely the fact that H0 is over powered is a secondary issue at this point?
Unless if course its H0 that has the fault and not H1.
So to confirm: which one do you have a problem with the temperature display on
H0= The heated bed?
OR
H1= The hot end -
@CaLviNx surely you see that adding T100000 to his thermistor setting should correct the erroneously high temp reading.
-
@Phaedrux said in Tool board LC1 errors:
@CaLviNx surely you see that adding T100000 to his thermistor setting should correct the erroneously high temp reading.
I'm not disagreeing with you but the guy quite clearly pointed out that, he had tried it with T100000 inserted and that had no effect, so unless the guy is lying the problem lies elsewhere and I fail to see the point in following up about the other heater being over powered instead of concentrating on the guys actual issue.
-
@CaLviNx said in Tool board LC1 errors:
I'm not disagreeing with you but the guy quite clearly pointed out that, he had tried it with T100000 inserted and that had no effect
The default is T100000, so indeed adding T100000 should have no effect.
@JayJay, are you certain that the temperature sensor in your hot end is thermistor, not a PT100, and it is not shorted out or shorting to the hot end metalwork?
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 said in Tool board LC1 errors:
@JayJay, are you certain that the temperature sensor in your hot end is thermistor, not a PT100, and it is not shorted out or shorting to the hot end metalwork?
Thank you for the reply and kind assistance.
Yes the sensor is 100% a thermistor it is shielded in grp sheathing around the hotend etc.
But I think I may have a faulty toolboard, as I moved the very same sensor from "temp0" to "temp1" and changed the config.g to:
M308 S1 P"121.temp1" Y"thermistor" B4725 C7.06e-8
And now the temp is reading correct and the same as the bed temp (when at room temp)
But I now receive the following error message as soon as I try to home X :
Warning: motor phase B may be disconnected reported by driver(s) 0
Warning: motor phase A may be disconnected reported by driver(s) 0Driver0 is where the extruder motor is mapped to and i checked the wires to find the base pairs with a meter and located them in the plug accordingly, the only thing that could be wrong there is that the motor might round the wrong way but why DWC is now reporting Driver0 as being disconnected when i home X is beyond me.
This is my home X, Y & Z files
Home X
; homex.g ; ; called to home the X axis ; G91 ; Switch to relative positioning moves G1 H2 Z5 F6000 ; Drop the Z axis (the bed) by 5mm relative to it's current position G1 H1 X-350 F3000 ; Fast travel the X axis close to it's endstop & stop G1 H2 X5 F6000 ; Move the X axis back by 5mm G1 H1 X-350 F240 ; Slow travel the X axis until it triggers it's endstop G1 H2 Z5 F1000 ; Drop the Z axis (the bed) by 5mm relative to it's current position G90 ; Revert back to absolute positioning movesHome Y
; homey.g ; ; called to home the Y axis ; G91 ; Switch to relative positioning G1 H2 Z5 F6000 ; Drop the Z axis (the bed) by 5mm relative to it's current position G1 H1 Y-350 F3000 ; Fast travel the Y axis close to it's endstop & stop G1 H2 Y5 F3000 ; Move the Y axis away from it's endstop by 5mm G1 H1 Y-350 F240 ; Slow travel the X axis until it triggers it's endstop G1 H2 Z-5 F1000 ; Drop the Z axis (the bed) by 5mm relative to it's current position away from the nozzle G90 ; Revert back to absolute positioningHome Z
; homez.g ; ; called to home the Z axis ; G91 ; Switch to relative positioning moves G1 H2 Z5 F6000 ; Drop the Z axis (the bed) by 5mm relative to it's current position G1 H1 Z-350 F3000 ; Fast travel the Z axis (the bed) up closer to it's endstop & stop G1 H2 Z5 F1500 ; Move the Z axis (the bed) away from the IR probe by 5mm G1 H1 Z-350 F240 ; Slow travel the Z axis (the bed) until it triggers the IR Sensor G91 ; Switch to relative positioning moves G1 Z5 F1000 ; Drop the Z axis (the bed) by 5mm relative to it's current position away from the nozzle G90 ; Revert back to absolute positioning moves -
Your drive mapping M584 is in conflict with what you have in your M569
in M584 you have
M584 X0.0 Y0.1 Z0.3:0.4:0.5But in M569
You have the following
M569 P121.0 S1 ; Driver 121.0 is connected to the extruder motor output (Driver 0) on the toolboard LC1 & goes forwards M569 P0.1 S1 ; Driver 0.1 is connected to the Z1 axis motor (Front Left) on the mainboard 6HC & goes forwards M569 P0.2 S1 ; Driver 0.2 is connected to the Z2 axis motor (Front Right) on the mainboard 6HC & goes forwards M569 P0.3 S1 ; Driver 0.3 is connected to the Z3 axis motor (Centre Rear) on the mainboard 6HC & goes forwards M569 P0.4 S1 ; Driver 0.4 is connected to the X axis motor on the mainboard 6HC & goes forwards M569 P0.5 S1 ; Driver 0.5 is connected to the Y axis motor on the mainboard 6HC & goes forwardsso you need to fix either one or the other to match how you have it wired
-
@CaLviNx said in Tool board LC1 errors:
so you need to fix either one or the other to match how you have it wired
@CaLviNx
Thank you so very much, an excellent spot, the M569 commands are correct .
I have edited M584 to match and that got rid of the driver0 error and everything is now homing. thank you again.
please accept my apologies in advance as I will no doubt be back with more rookie questions.
