Thanks @chrishamm !
The only way to figure if it could be loaded, was to load the height map before homing so to get the warning message!
Have a good day!
ay to verify what height map is being used if one is called before a print?
I am coming with the same question. On duet wifi 2, I upgraded to 3.01-RC9 and Duet Web Control 2.1.4 but loading the height map either with G29 S1 or through the Dashboard tab -> Compensastion & Calibration -> Load saved height map from SD Card the "Disable Mesh compensation" remains disabled.
I see in the diagnostics the following even after I Execute G29 S1 or G29 S2
=== Move === Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms Bed compensation in use: mesh, comp offset 0.000
Is this an issue with my configuration, some bug or anything else? I can see the height map from the height map tab but cannot tell whenever it is active or not even if i turn debugging on/off.
To be exact:
Based on the DuetWifi by Think3dPrint3d and Esher3d, see www.duet3d.com for the original DuetWifi information. This reproduction/modification is not endorsed or supported in any way by Think3dPrint3d or Escher3d".
They did catch up quite fast to be honest
I was hoping to find a UK reseller , but it looks like I may have to go by the slow boat from china route.
Due to never ordering from outside the EU before I`ve looked into the customs / duties / tax etc I would have to pay extra for anything from china.
Which being under £135 I think would cost me just VAT on top ?
Cannot tell for UK though as I live in Greece and I usually buy from banggood. Nothing has gone through customs so no any additional charges. Anything more expensive will go through Netherlands and it will seem like being sent within Europe. There are usually three shipping methods available. The cheapest one and slowest, the airmail priority and a third more expensive and fastest one. Picking any of the first two won't go through customs. Additionally, anything that goes through customs apart from the VAT you will have to pay an additional customs' fee.
I wonder if there is anyone here who can confirm for UK.
I have a 30cmx30cm heated bed at 750W and it takes approx 2:54 minutes to reach 70c
So you had the titan aero assembled, which was working fine until you upgraded the firmware. This is strange indeed.
How fast do you extract? Usually for steps calibration I go as low as 160mm/min (2.6mm/s).
Did you extruder came with bushings or bearings? While extruding do you notice any jam at all, like the extrusion slows down or something?
Since you changed the current to 1.4 and overextruded the only thing that can think of, is that there must be a high friction issue with the extruder. How did you tighten the heatsink? I had a friction issue which i managed to solve by tightening the screws from top right (the freewheel and bearings location but very gently) , right bottom, top left and left bottom. E3D last time i checked suggest the right process should be from top left, bottom left, and move on the right side which didn't work out well for me. Tried it with both bearings and bushings and there was always some tension and minor misalignment when i was following their suggested sequence.
Something else you need to consider is in case if you are using the pancake motor (slim nema motor) is that you are close to its max amp rating and you should be somewhere around 80% of this number (1.4).
No firmware update has affected my titan aero.
I would like to ask you how old is your extruder? I'm asking you this as there was an issue with the titan aero bearings. I had my aero working great until I moved it onto my new coreXY and and the extrusions were inconsistent. It took me a while before i eventually figured out that the bearings were causing this problem due to a friction increase as a result of not only missing steps but also the extruder was getting jammed.
With new bearings I can still use the pancake (slim nema motor that comes with aero) but I still had to increase the current to 1000 (M906 E1000 I50)
I am currently using x16 microstepping and works great
M350 E16 I1 ; Configure microstepping with interpolation
M92 E950 ; Set steps per mm
I had to lower my probing speeds and also introduced a recovery time. Still the probing heights changes range between -0.03 to 0.03 but my prints especially the first layer never caused me any issues.
From M558 P5 X0 Y0 Z1 H5 F500 T2000
I have M558 P9 X0 Y0 Z1 H5 F160 R0.250 T2000 ; P9 probe
In your homeall script, this line:
G1 S1 X5 Y5 F1000 ; go ahead a few mm
probably won't work because X and Y are already homed at that point. But as they are homed, you can omit the S parameter completely from that line.
In your homez script, the only line where it's essential to have the S2 parameter is the first G1 line. After that the Z axis is homed, so G1 commands without the S parameter will work too.
Well spotted! Thanks
I have a CoreXY so sending any movements using S2 for X and Y won't result to a movement on a single axis.
Instead, even without having any axis homed, I still use S1 ie. G1 S1 X10
I only use S2 for the Z as described in the notes.
I don't know if this is the correct way but I won't exceed any limits
My home all script is as shown below:
G91 ; relative positioning G1 S2 Z5 F1000 ; lift Z relative to current position ; << Home XY >> G1 S1 X-305 Y-305 F6000 ; move quickly to X or Y endstop and stop there (first pass) G1 S1 X-305 ; home X axis G1 S1 Y-305 ; home Y axis G1 S1 X5 Y5 F1000 ; go ahead a few mm G1 S1 X-10 F800 ; go back to X endstop slower this time G1 S1 Y-10 F800 ; go back to Y endstop slower this time G90 ; << Home Z >> M98 Phomez.g
and this is my Z homing:
G91 ; relative positioning G1 S2 Z5 F1000 ; Lift nozzle G90 ; absolute positioning m401 ; or M98 Pdeployprobe.g deploy mechanical Z probe G91 ; relative positioning G1 S1 Z-500 F1000 ; Lower bed fast G1 S2 Z5 F1000 ; Lift bed fast G90 M402 ; or M98 Pretractprobe.g to retract mechanical Z probe ;<<< Probe Bed >>> G30 ; Probe at current XY G91 ; relative positioning G1 S2 Z5 F150 ; lift Z 5 mm G90 ; absolute positioning
I got a deviation of 0.007 with my bltouch using a repeatability test macro found here somewhere. I remember getting the same result using marlin.
Using marlin and ramps i had pretty much similar deviation. Now on my new coreXY i get a deviation of around 0.02 - 0.06 unless i go very slow at around 120mm/min
I am very interested in your scripts (config, deployprobe and retrctprobe).
Came here to report.
CoreXY with bltouch and multitouch probing enabled with Probe 5 (P5), prints and everything works fine. Also the web interface feels more responsive.
I believe I have tried my best to resolve this problem without any success.
I have installed Duetwifi (1.21RC1 firmware) on a new CoreXY Build with a new Titan Aero extruder along with a nema 17 1.8 motor. I cannot tune the Extrusion steps as they are always inconsistent especially after I switch duet off and back on again. But the error is weirdly consistent. As an example, I have a 120mm mark on the filament. Extrude 100mm and find the distances of the mark. even if i get it right and see the 20mm mark on the filament and power duet off and back on again the mark is an additional +5mm for the next 3-4 extrusions.
The filament I use is PETG and I extrude at 230C. I tried to extrude both from the interface 100mm at 5mm/s and manually executing G1 E100 F180. At this point i have run out of options. Is there anything else I should check?
[[language]] ; <<< General preferences >>> M111 S0 ; Debugging off G21 ; Work in millimetres G90 ; Send absolute coordinates... M83 ; ...but relative extruder moves M555 P1 ; Set firmware compatibility to look like RepRap Firmware ; Automatic saving after power loss is not enabled ; <<< COREXY Settings >>> M667 S1 ; Select CoreXY mode ;M404 N1.75 ; Filament and Nozzle settings M208 X0 Y0 Z0 S1 ; Set axis minima M208 X300 Y295 Z400 S0 ; Set axis maxima M671 X-2:305:305:-2 Y-2:-2:305:305 P0.5 ; <<< Drives >>> M569 P0 S0 ; Drive 0 goes forwards M569 P1 S0 ; Drive 1 goes forwards M569 P2 S0 ; Drive 2 goes forwards M569 P3 S1 ; Drive 3 goes forwards ; <<< Drives Microstepping >>> M350 X16 Y16 Z128 E64 I1 ; Configure microstepping with interpolation ; <<< Drives Steps >>> M92 X80 Y80 Z6400 E1810 ; Set steps per mm ; <<< Motor Currents >>> M906 X800 Y800 Z800 E940 I30 ; Set motor currents (mA) and motor idle factor in per cent ; <<< Drives Speeds >>> M203 X18000 Y18000 Z900 E1500 ; Set maximum speeds (mm/min) M201 X800 Y800 Z250 E250 ; Set accelerations (mm/s^2) M566 X600 Y600 Z50 E80 ; Set maximum instantaneous speed changes (mm/min) M204 P500 T2000 ; 500mm/s Acceleration for printing moves accelaration 2000mm/s Acceleration for travel moves ; <<< Idle timeout >>> M84 S0 ; Set idle timeout ; <<< Endstops >>> M574 X1 Y1 S1 ; Set active high endstops M574 Z1 S2 ; Set endstops controlled by probe ;M558 P0 H5 F120 T6000 ; Set Z probe type to switch and the dive height + speeds ;G31 P600 X0 Y0 Z2.5 ; Set Z probe trigger value, offset and trigger height ; <<< Heaters >>> M143 H0 S120 ; Set temperature limit for heater 0 to 120C M143 H1 S292 ; Set temperature limit for heater 1 to 292C ; <<< Thermistors >>> M305 P0 T100000 B4138 C0 R4700 S"Bed" ; Set thermistor + ADC parameters for heater 0 M305 P1 X200 S"HotEnd" ; Hot-End PT100 ; <<< PID Heater Parameters >>> M307 H0 A379.6 C961.2 D20 S1.00 B1 ; Heater 0 - BED PID paramaters M307 H1 A765.1 C237.7 D4.2 S1.00 B0 ; Heater 1 - Hot End PID paramaters - Bang Bang ; <<< Fans >>> M106 P0 S0.3 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off M106 P1 S1 I0 F500 H1 T45 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on M106 P2 S1 I0 F500 H-1 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned off ; <<< Tools >>> M563 P1 D0 H1 ; Define tool 1 G10 P1 X0 Y0 Z0 ; Set tool 1 axis offsets G10 P1 R0 S0 ; Set initial tool 1 active and standby temperatures to 0C ; <<< BLTOUCH >>> M307 H3 A-1 C-1 D-1 ; Disable Heater 3 (pin 8) normal function M557 X7:275 Y25:275 S53 ; Define mesh grid with S mm distance between probe points M558 P5 X0 Y0 Z1 H5 F150 T4000 S0.02 R0.300 A5 ; Set Z probe type (use P5 -z axis endstop- probe for Z axis, at F speed and T travel speed between probe points. S tolerances and Probe A times) G31 P25 X6.7 Y23.5 Z1.37 ; Probe offsets from nozzle M376 H11.0 ; taper of height compensation above this mm value
Edit: Grammar check
Edit: Something that I forgot to mention is that the new extruder came with bushings instead of bearings which definitely causes some extra friction. Nevertheless, the motor seems to work smoothly. I wonder if there are any settings that I keep missing though.
Today, I installed (almost) my new DuetWifi, and accessing the Duet Web control for first time whilst being powered on a 24v power supply (350w) and got spammed with this warning:
Warning: Error: Short-to-ground on drivers 0
Warning: Error: Over temperature shutdown on drivers 0
I've double checked and triple checked everything and all my wires are correct. As a matter of fact even without having anything connected to the drivers, (only power wire and heated bed) I still get this error.
I also updated the firmware to 1.20.1
FIRMWARE_NAME: RepRapFirmware for Duet WiFi FIRMWARE_VERSION: 1.20.1 ELECTRONICS: Duet WiFi 1.0 FIRMWARE_DATE: 2018-01-08
Also did run diagnostics (M122) and got the following:
And this the output I am receiving using the M112
=== Diagnostics ===
Used output buffers: 3 of 32 (14 max)
=== Platform ===
RepRapFirmware for Duet WiFi version 1.20.1 running on Duet WiFi 1.0
Board ID: 08DGM-95BNL-MGPSJ-6J1FD-3S46T-KKY3X
Static ram used: 15372
Dynamic ram used: 98780
Recycled dynamic ram: 536
Stack ram used: 1336 current, 4260 maximum
Never used ram: 12124
Last reset 00:06:34 ago, cause: software
Last software reset time unknown, reason: User, spinning module GCodes, available RAM 12124 bytes (slot 3)
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 23.6, current 23.9, max 24.1
Supply voltage: min 24.4, current 24.5, max 24.7, under voltage events: 0, over voltage events: 0
Driver 0: temperature-shutdown! short-to-ground 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: 2018-01-21 14:54:32
Cache data hit count 2316986664
Slowest main loop (seconds): 0.006525; fastest: 0.000108
=== Move ===
MaxReps: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm 240, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 0, completed moves: 0
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
=== 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.19
WiFi MAC address a0:20:a6:2f:bf:f9
WiFi Vcc 3.10, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 39560
WiFi IP address 192.168.1.111
WiFi signal strength -56dBm, reconnections 0, sleep mode unknown
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)
Warning: Error: Short-to-ground on drivers 0
Warning: Error: Over temperature shutdown on drivers 0
Is there anything i might have missed and it is something that can be magically fixed?