unusual/unnerving noises + error codes
-
The bottom right corner of that same display box under the heading Z-Probe
-
@Phaedrux so im not sure what just happened but it seems to be working now however when homing the x axis it shakes for a couple seconds and then is fine. the y axis homes but stays to far away so i had to manually flick the bl touch probe. But it worked. Is this just playing around with the axis limits?
-
Well you should still verify the basics.
I suggest you take a look through these guides.
https://duet3d.dozuki.com/Guide/Ender+3+Pro+and+Duet+Maestro+Guide+Part+3:+Commissioning/39
https://duet3d.dozuki.com/Guide/Ender+3+Pro+and+Duet+Maestro+Guide+Part+4:+Calibration/40
-
Thank you for this!!! i now have everything homing correctly and no weird noises or shaking which is great.
Apologies for this, i am trying to find pages that help and i really appeciate all the help you have given me to far. But...
I have been following this
https://duet3d.dozuki.com/Guide/Ender+3+Pro+and+Duet+Maestro+Guide+Part+3:+Commissioning/39
Ive got to step 8 and as soon as i get to roughly 30 degree it stops and shows this message
Error: Heater 0 fault: temperature rising much more slowly than the expected 1.7°C/sec
i did some googling and found this
it says i need to do this 'Therefore, you must perform a PID auto tuning to give the firmware a model for bed heater performance. Failure to do so will result in an error message that the heater temperature is not rising fast enough'
But i dont know what a PID is or how to run it. Are you able to help with this?
-
Pid tuning is part of the calibration guide.
-
So i have no idea what happened but i have tried to connect this morning and it doent seem to be connecting to the wifi. I noticed that when i turn it on. the Blue LED (wifi LED) go straight to a solid blue rather than flickering a bit while connecting. . I have plugged it in with the USB and went into terminal and i dont seem to be able to get it into idle. I can turn it off using M552 S-1 but when checking the status of the wifi using M552 it says 'WiFi module is being started' and when putting M587 it returns 'Error: M587: Failed to retrieve network list'
Any ideas on how i can connect again?
-
@PR1OR ive advanced. By using M997 S1 however it keeps reverting back again. Is there a code i need to put in to stop it 'forgetting'?
-
And you have m552 S1 in your config.g?
If you send m122 at the end of the report it should show some wifi info. Post that here..
-
@Phaedrux said in unusual/unnerving noises + error codes:
m122 at the end of the report it should show some wifi info. Post that
m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet WiFi 1.02 or later
Board ID: 08DJM-9178L-L2MSD-6JKF6-3SD6R-1TDUN
Used output buffers: 3 of 24 (11 max)
=== RTOS ===
Static ram: 27980
Dynamic ram: 93936 of which 24 recycled
Exception stack ram used: 264
Never used ram: 8868
Tasks: NETWORK(ready,384) HEAT(blocked,1224) MAIN(running,1816) IDLE(ready,80)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:03:30 ago, cause: software
Last software reset at 2020-09-18 19:00, reason: User, spinning module GCodes, available RAM 8636 bytes (slot 3)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN
Error status: 0
MCU temperature: min 37.8, current 38.3, max 38.8
Supply voltage: min 23.7, current 23.8, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
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
Date/time: 2020-09-18 19:04:28
Cache data hit count 369890305
Slowest loop: 5.90ms; fastest: 0.12ms
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 1.0ms, write time 0.0ms, 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 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
Heater 1 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 119.41ms; 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.23
WiFi MAC address cc:50:e3:32:51:9f
WiFi Vcc 3.41, reset reason Unknown
WiFi flash size 4194304, free heap 20544
WiFi IP address 192.168.1.145
WiFi signal strength -50dBm, reconnections 0, sleep mode modem
Socket states: 0 4 0 0 0 0 0 0
- WiFi -
-
So it seems to be working ok now which is good. but when going for a test print i reserve this
Error: Fan number 2 not found
Error: Invalid tool number
Warning: Tool 0 was not driven because its heater temperatures were not high enough or it has a heater faultthe Fan i think can probably wait til a little later but the tool i feel is an issue
-
I think you should try a different slicer. Something is not right in your simplify3d setup.
Are you using the config.g from the set I provided? Can you post what you have now? Copy and paste from the config.g edit window or upload the file here.
All of your hardware works when you control it from the web interface, but when you try to print a file sliced in simplify 3d it doesn't work. I think your printer profile in S3D is setup for a different printer. I don't use S3D so I'm not much help there.
-
@Phaedrux said in unusual/unnerving noises + error codes:
simplify 3d
yeah using the your one.
; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.1.4 on Wed Sep 16 2020 13:09:04 GMT-0600 (Central Standard Time); General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Duet2Wifi" ; set printer name; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet; Drives
M569 P0 S0 ; physical drive 0 goes backwards
M569 P1 S1 ; physical drive 1 goes backwards
M569 P2 S0 ; physical drive 2 goes forwards
M569 P3 S0 ; physical drive 3 goes forwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ;a configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E93.00 ; set steps per mm
M566 X900.00 Y900.00 Z12.00 E1200.00 ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2)
M906 X600 Y600 Z600 E600 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; Axis Limits
M208 X-5.5 Y-10 Z0 S1 ; set axis minima
M208 X220 Y220 Z250 S0 ; set axis maxima; Endstops
M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop
M574 Z1 S2 ; configure Z-probe endstop for low end on Z; Z-Probe
M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch
M558 P9 C"^zprobe.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X-31 Y0 Z0.6 ; set Z probe trigger value, offset and trigger height
M557 X9.5:220 Y5:195 S20 ; define mesh grid; Heaters
M308 S0 P"bedtemp" Y"thermistor" T98801 B4185 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0 ; create bed heater output on bedheat 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 S120 ; set temperature limit for heater 0 to 120C
M308 S1 P"e0temp" Y"thermistor" T98801 B4185 ; configure sensor 1 as thermistor on pin e0temp
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; Fans
M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P0 C"Heatsink" S0 H-1 ; set fan 0 name and value. Thermostatic control is turned off
M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
M106 P1 C"PartCooling" S1 H1 T45 ; set fan 1 name and value. Thermostatic control is turned on
M950 F1 C"fan2" Q500 ; create fan 2 on pin fan2 and set its frequency
M106 P1 C"ExtruderCooling" S1 H1 T45 ; set fan 2 name and value. Thermostatic control is turned on; Tools
M563 P0 S"Extruder 01" D0 H1 F0 ; define tool 0
G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C; Custom settings are not defined
; Miscellaneous
M575 P1 S1 B57600 ; enable support for PanelDue
M501 ; load saved parameters from non-volatile memory
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss
T0 ; select first toolSo i didnt use a slicer there was a gcode on the interface for the benchy so i thought id try that. Im just downloading cura now so will try again and see what happens
-
@PR1OR said in unusual/unnerving noises + error codes:
; Fans
M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P0 C"Heatsink" S0 H-1 ; set fan 0 name and value. Thermostatic control is turned off
M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
M106 P1 C"PartCooling" S1 H1 T45 ; set fan 1 name and value. Thermostatic control is turned on
M950 F1 C"fan2" Q500 ; create fan 2 on pin fan2 and set its frequency
M106 P1 C"ExtruderCooling" S1 H1 T45 ; set fan 2 name and value. Thermostatic control is turned on
; Tools
M563 P0 S"Extruder 01" D0 H1 F0 ; define tool 0This defined the fans and tool.
The tool uses fan 0 for part cooling, extruder 0 for the motor, and heater 1 for the hotend.
The hotend heatsink fan is fan1.
Fan 2 is being used as maybe a duet board cooling, but maybe you don't have anything connected to fan2?
You won't be able to print old gcode, you'll need to slice a new file.
You'll have to setup Cura with a new printer profile. Make sure to tell it you are using reprap gcode flavor.
-
@Phaedrux perfect i think i have this right.
I think i only have two things left wooohooo
-
I have two fan bars on the DWC but they only seem to move together and not individually. How would i make them independant?
-
When doing the true bed leveling i keep getting this response. But i can see where to amend either G32 or G29
Warning: Skipping grid point (190.0, 60.0) because Z probe cannot reach it
Warning: Skipping grid point (210.0, 60.0) because Z probe cannot reach it
Warning: Skipping grid point (210.0, 80.0) because Z probe cannot reach it
Warning: Skipping grid point (190.0, 80.0) because Z probe cannot reach it
19/09/2020, 11:36:03 G29
Warning: Skipping grid point (190.0, 20.0) because Z probe cannot reach it
Warning: Skipping grid point (210.0, 20.0) because Z probe cannot reach it
Warning: Skipping grid point (210.0, 40.0) because Z probe cannot reach it
Warning: Skipping grid point (190.0, 40.0) because Z probe cannot reach it
-
-
@PR1OR said in unusual/unnerving noises + error codes:
I have two fan bars on the DWC but they only seem to move together and not individually. How would i make them independant?
Those two sliders are for the same thing. The tool fan slider is for the fan of the currently selected tool, which is fan0, and the fan0 slider is for fan0. If you had two tools with different fans, the tool slider would always control the fan of the currently selected tool and you'd have 2 sliders for each fan as well. There is a little button link near the fan sliders "change visibility" that will let you hide one of you like since you only have 1 tool.
To get rid of those errors we need to change the M557 grid spacing to take your probe offset into account because it can't reach some of the areas you're asking it to.
Try
M557 X5:185 Y5:205 P6 -
@Phaedrux Ahh ok fine thats ok then ill just hide one of them
in regard to the M557 X5:185 Y5:205 P6 i have updated this.
and am now getting this
G32Warning: Skipping grid point (5.0, 5.0) because Z probe cannot reach it
Warning: Skipping grid point (41.0, 5.0) because Z probe cannot reach it
Warning: Skipping grid point (77.0, 5.0) because Z probe cannot reach it
Warning: Skipping grid point (113.0, 5.0) because Z probe cannot reach it
Warning: Skipping grid point (149.0, 5.0) because Z probe cannot reach it
Warning: Skipping grid point (185.0, 5.0) because Z probe cannot reach it -
also are you able to break down that code so i can start understanding the structure and meaning? I think it will help for the future (rofl)
I would on SAP and code regularly so i think if i started understanding what everything means i maybe able to start fault finding alittle better
-
Well to define a good M557 you'd take your M208 axis limits and your G31 X Y offsets and choose points such that the probe is able to reach them.
A good way to do this is to draw a diagram of your bed showing the size and probe offsets and then you can see where the probe is able to reach.
It's skipping the Y5 area now, but I thought it should be able to reach it because the probe is inline with the nozzle (y0 offset) and the Y axis goes from -10 to 220.
-
@Phaedrux said in unusual/unnerving noises + error codes:
220
Thank you for this!! i now am not getting that message. I have sorted the parameters and i think i have as bigger printing area as i can get.
However i am now getting this
Warning: the height map has a substantial Z offset. Suggest use Z-probe to establish Z=0 datum, then re-probe the mesh.
36 points probed, min error -1.793, max error -0.002, mean -0.966, deviation 0.483I have tried to recalibrate the BL touch using this
https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe
As i read that, that maybe the issue, but it keeps coming up now
Any ideas? also as a side point (pardon my ignorance) should the BL touch auto adjust the Z axis depending on the height or do i still have to manually have to adjust using the height map?
-
@PR1OR said in unusual/unnerving noises + error codes:
Warning: the height map has a substantial Z offset. Suggest use Z-probe to establish Z=0 datum, then re-probe the mesh.
this mean you are loading the mesh before you have homed the printer.
check your start code
if you have G28 and G29 make sure that G28 comes first.
