Mini 5 no heaters
-
@Veti said in Mini 5 no heaters:
he wrote he connected it to out1 but wrote out0 in the code
we will need a picture of the tool-board to check that.
@JayJay please post a picture of your tool-board wiring
-
Thank you all for the input.
@Veti thanks for the advice on moving the heater wires, i used out2 because i have an SSR and thought it would be ok to use, i moved the wires to out0 and changed the config, and now the bed heater works.
I also updated the toolboard firmware to Duet TOOL1LC firmware version 3.2-RC2 (2020-12-24)
And now since doing that the temp reading has dissappeared and shows n/a where as before it did show the correct temp, and i can now click on the hot end button and activate it but as there is no temp reading i get a fault, so i just need to work on that now.
@CaLviNx
my originalpost about the toolboard being on out1 is a typo it is wired into out0 same as the config.
-
can you post the M122 of both the mini and the toolboard. maybe there is a can communication problem.
-
@Veti said in Mini 5 no heaters:
can you post the M122 of both the mini and the toolboard. maybe there is a can communication problem.
i also tried moving the thermistor to temp0 and that shows as n/a also
M122 === Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.2-beta3.2+1 running on Duet 3 Mini5plus WiFi (standalone mode) Used output buffers: 3 of 40 (11 max) === RTOS === Static ram: 97472 Dynamic ram: 132764 of which 368 recycled Never used RAM 30516, free system stack 176 words Tasks: NETWORK(ready,168) HEAT(blocked,195) CanReceiv(blocked,875) CanSender(blocked,371) CanClock(blocked,370) TMC(blocked,56) MAIN(running,448) IDLE(ready,20) AIN(blocked,258) Owned mutexes: === Platform === Last reset 00:03:29 ago, cause: software Last software reset at 2020-12-29 14:51, reason: User, GCodes spinning, available RAM 30516, slot 2 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN Error status: 0x00 Supply voltage: min 0.0, current 23.6, max 23.6, under voltage events: 0, over voltage events: 0, power good: yes Driver 0: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 39, reads 29883, writes 9, timeouts 0, DMA errors 0 Driver 1: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 39, reads 29883, writes 9, timeouts 0, DMA errors 0 Driver 2: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 39, reads 29883, writes 9, timeouts 0, DMA errors 0 Driver 3: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 39, reads 29883, writes 9, timeouts 0, DMA errors 0 Driver 4: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 39, reads 29883, writes 9, timeouts 0, DMA errors 0 Driver 5: position 0, assumed not present Driver 6: position 0, assumed not present Date/time: 2020-12-29 14:55:14 Slowest loop: 10.22ms; fastest: 0.12ms === Storage === Free file entries: 10 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 3.3ms, write time 4.7ms, max retries 0 === Move === Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, 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, 0], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed moves 0, StepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters = 0 -1, chamberHeaters = -1 -1 Heater 0 is on, I-accum = 0.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. === Network === Slowest loop: 26.88ms; fastest: 0.00ms Responder states: HTTP(0) 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.25beta0 WiFi MAC address f4:cf:a2:6f:bd:af WiFi Vcc 3.38, reset reason Power up WiFi flash size 2097152, free heap 26680 WiFi IP address 192.168.0.115 WiFi signal strength -48dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0 === CAN === Messages sent 0, send timeouts 0, longest wait 2ms for type 6049, free CAN buffers 15 M122 B121 Diagnostics for board 121: Duet TOOL1LC firmware version 3.2-RC2 (2020-12-24) Bootloader ID: not available Never used RAM 4176, free system stack 96 words HEAT 90 CanAsync 89 CanRecv 83 TMC 54 MAIN 324 AIN 64 Last reset 00:05:42 ago, cause: software Last software reset data not available Driver 0: position 0, 80.0 steps/mm, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 51, reads 39933, writes 10, timeouts 0, DMA errors 0 Moves scheduled 0, completed 0, in progress 0, hiccups 0 No step interrupt scheduled VIN: 24.0V MCU temperature: min 32.2C, current 32.6C, max 32.6C Ticks since heat task active 61, ADC conversions started 342054, completed 342053, timed out 0 Last sensors broadcast 0x00000000 found 0 64 ticks ago, loop time 0 CAN messages queued 2765, send timeouts 0, received 3098, lost 0, free buffers 36
-
@JayJay said in Mini 5 no heaters:
RepRapFirmware for Duet 3 Mini 5+ version 3.2-beta3.2+1
you did not do the update to 3.2-RC2
after the update power the entire system down and up again
-
@Veti said in Mini 5 no heaters:
@JayJay said in Mini 5 no heaters:
RepRapFirmware for Duet 3 Mini 5+ version 3.2-beta3.2+1
you did not do the update to 3.2-RC2
after the update power the entire system down and up again
hmmm i dont know why it is saying that as i definately downloaded the rc2 candidate from github
i uploaded it to the board and it asked me if i wantted to update which i did.
i think the correct file is : Duet3Firmware_Mini5plus.uf2
and : Duet3_SDiap32_Mini5plus.bin -
@JayJay said in Mini 5 no heaters:
and : Duet3_SDiap32_Mini5plus.bin
rename the old Duet3_SDiap_Mini5plus.bin to old
and copy another version of Duet3_SDiap32_Mini5plus.bin and remove the 32 and try the firmware update again. -
that cured all thank you.
but i want to know why the bed didnt work on out2 ? as with an SSR it should have been fine
-
maybe a bad crimp job?
-
nah my job is an auto electrician the crimps were fine i checked continuity with a meter too.
-
@JayJay said in Mini 5 no heaters:
that cured all thank you.
but i want to know why the bed didnt work on out2 ? as with an SSR it should have been fine
Yes it should have worked, provided that the fuse for the heaters/motors/fans is intact (the bed heater uses a separate fuse).
- Did the red LED next to OUT2 light when you tried to turn on the bed heater?
- Did you try running M98 P"config.g" to check for errors in the config,g file?
-
@dc42 said in Mini 5 no heaters:
@JayJay said in Mini 5 no heaters:
that cured all thank you.
but i want to know why the bed didnt work on out2 ? as with an SSR it should have been fine
Yes it should have worked, provided that the fuse for the heaters/motors/fans is intact (the bed heater uses a separate fuse).
- Did the red LED next to OUT2 light when you tried to turn on the bed heater?
- Did you try running M98 P"config.g" to check for errors in the config,g file?
The fuses are all intact.
I cant remember if the LED turned on or not, since i moved it to out0 and it worked i left it alone.
M98 reports
M98 P"config.g" HTTP is enabled on port 80 FTP is disabled TELNET is disabled
but i am now encountering an issue with getting the probe to be recognised during G32