Heater 1 and Fan1 Stopped Working
It worked thanks Dave!! The M305 had me stumped until I realised the P is substituted for H!
M307 H3 A340 C140 D5.5 I0 V0 S1.0
M301 H3 P10 I0.10 D100 T0.50 S1.0 ; PID settings for extruder 0
M563 P0 D0 H3 X0 F0 ; Define tool 0 to use extruder drive 0 and heater 3
M305 P3 X200; Put your own H and/or L values here to set the first nozzle thermistor ADC correction
Unfortunately its one of your first V1 board so no warranty… but I will use as is for now with remapped fan and heater
If you are in the US you can ask Dieter (forum user W3DRK) to give you a price for repairing it.
Was investigating a new issue where the bed temperature doesn't rise with the heat of the bed and noticed the MCU temp is running way too high... can this be causing the issue? Th machine is just idling, no printing and the temp was touching 115 degrees? From M122...
MCU temperature: min 99.1, current 99.2, max 115.8
Supply voltage looks ok…?
=== Diagnostics ===
Used output buffers: 3 of 32 (8 max)
=== Platform ===
RepRapFirmware for Duet WiFi version 1.20 running on Duet WiFi 1.0 + DueX5
Board ID: 08DAM-999TL-MQ4S4-6J1FG-3SD6S-TPGRY
Static ram used: 15448
Dynamic ram used: 99416
Recycled dynamic ram: 3920
Stack ram used: 1392 current, 4504 maximum
Never used ram: 7784
Last reset 00:05:29 ago, cause: software
Last software reset at 2018-01-06 14:37, reason: User, spinning module GCodes, available RAM 7784 bytes (slot 1)
Software reset code 0x0003 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0441f000, BFAR 0xe000ed38, SP 0xffffffff
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 99.1, current 99.2, max 115.8
Supply voltage: min 24.8, current 25.0, max 25.3, under voltage events: 0, over voltage events: 0
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Driver 5: standstill, SG min/max not available
Driver 6: standstill, SG min/max not available
Driver 7: standstill, SG min/max not available
Driver 8: standstill, SG min/max not available
Driver 9: standstill, SG min/max not available
Expansion motor(s) stall indication: no
Date/time: 1970-01-01 00:00:00
Cache data hit count 1314881303
Slowest main loop (seconds): 0.014140; fastest: 0.000045
=== Move ===
MaxReps: 0, StepErrors: 0, FreeDm: 240, MinFreeDm 240, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 0, completed moves: 0
Bed compensation in use: mesh
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
Heater 0 is on, I-accum = 0.0
Heater 3 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Stack records: 1 allocated, 0 in use
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
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
Network state is running
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.20
WiFi MAC address 60:01:94:09:ba:08
WiFi Vcc 3.36, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 17288
WiFi IP address 192.168.1.5
WiFi signal strength -56dBm, reconnections 0, sleep mode modem
HTTP sessions: 1 of 8
Socket states: 2 0 0 0 0 0 0 0
Responder states: HTTP(1) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
2:42:53 PMMessage Log cleared!
Is the MCU really running that hot? If so, something is wrong. If not, perhaps you have a bad M912 command in config.g.
The voltage reading looks a little high, but if the 3.3V rail voltage is low that will cause an artificially high reading, because the 3.3V rail is the voltage reference when the MCU measures VIN.
Just checked wit IR thermometer… around 32 degrees on the sticker on top of the chip....? I have no M912 in config.g....
Also if I unplug the bed thermistor... temp still shws 28 degrees.... I am plagues by wierdness
How do I measure 3.3V rail?
3.225V on Duex 5 GPIO pins…
3.222 across pin 1 and 2 on Con_LCD connector on Duet Wifi
MCU at 41.1C now using external thermometer
Send M912 with no parameters, to check that no CPU temperature calibration is being applied. AFAIR, before calibration the MCU temperature on the ATSAM4E on the generation 2 Duets should be within 14C of the correct value.
The voltage reading on the 3.3V rail looks too low, it should be with 2% of 3.3V. Assuming your multimeter is accurate, I suspect either too much load on the 3.3V rail (in which case the 3.3V regulator IC U2 will be getting hot), or the 5V rail is at less than 4V.
MCU temperature calibration adjustment is 0.0°C
Across jumpers for int_5v and V_Fan.. 4.88V
Voltage at board input from PS is 24.29V
U2 Regulator measures 38C with the Temperature guns Laser centred on it.
Still cant understand why when I have no thermistor plugged into the H0 Heatbed pins … it reports 25.4C on the display??? Where could it possibly be getting this from.... I would expect a heater fault error and a 20000 display....
T:26.2 /0.0 27.0 /0.0 26.2 /0.0 27.0 /0.0 B:25.0 /0.0
This doesn't work either…
M307 H4 A90 C700 D10 I0 V0 S1.0 ; remapped to heat bed From Duex5 E4 temp sensor
M305 P0 X4 T100000 B4388 R4700 H30 L0 ; Put your own H and/or L values here to set the bed thermistor ADC correction
Unfortunately it sounds as though the ADC in the microcontroller may be blown.
Ouch!! Oh well, I shall have to get another board, at least I learnt a bit more along the way do you have stock?
Order placed… and for the new IR probe.
Thanks for all the help David,
If you are in the USA, forum user W3DRK may be able to replace the MPU for you.
Just checked my original order and it was in September… so I guess it is still under warranty! I am in South Africa, so what do I need to do to claim? I have ordered another in the meantime.... but it would be good to have a spare...
Order ID: #414
Date Added: 15/09/2016 Payment Method: PayPal
Product Name Model Quantity Price Total
- PreOrderBatch: Batch5
- Addon Hardware: PT100 daughterboard
- Addon Hardware: PanelDue with 4.3&qu.. DuetWifi 1
If it was delivered in September 2016 not 2017 then it is out of warranty.
Do you know anyone local to you who can replace the processor? If your soldering skills are good enough you could try it yourself. Use ChipQuik or similar low melting point solder and a cheap vacuum pick up tool to remove the old one. There are videos on YouTube.
Btw the more recent Duet versions have improved protection for the ADC.
Oh gosh you are right sorry late night !! I have dome some SMD repairs before so I will take a look when I remove it. Dot think I have done so many legs before though (older Atmel stuff mostly)
The tricky part is removing the old chip without lifting the PCB traces. You need either a good desoldering hot air gun with an appropriately sized nozzle and a vacuum pickup tool, or ChipQuik or similar low melting point solder (and preferably the vacuum pickup tool too). If you succeed without damaging the PCB, soldering the new chip in place is relatively easy if you have a no-clean flux pen, also some solder wick to help remove the inevitable solder bridges.
Thanks Dave I will give it a whirl after I have my new one fitted