ok guys, I tested different settings and I am happy with my temperature settings at 65 for the first layer with a speed of 20mm/s. Yes it takes longer but its worth it. Happy printing everybody and thanks for the support.
And btw I used a photo lighting softbox from amazon as my "chamber" and a personal heater to get it up to temp. Works great for what I paid.
@alankilian Yes Prusa Slic3er does offer that. Like I said I am printing some different tests with first player speed and first layer bed temp to find the point where it goes from failing to working and hopefully keep those settings for all future prints.
@alankilian Did run a test with 10mm/s instead of 30mm/s. It definitely helped. Have to find the sweet spot cause the print time on larger object will be significantly higher.
@Phaedrux I used a glue stick before, didn't like cleaning up after 
I think the ambient temperature here is maybe causing another issue. its 18C roughly. At night even less. Ordered a chamber to help that. Will try lowering the speed and do a test print.
It looks like we have a winner! Thank you so much Joerg55 and Phaedrux, I would never have thought about the glass bed changing with temperature, now it makes sense.
I got one small issue left, My filament starts to "roll" and sometimes stick to the nozzle and cause this:
is that a temperature issue?
@JoergS5 It's a glass bed. I think they are unlikely to bend?
Yes I heat it to regular PLA temp of 65C for first layer.
I just took all the gantry apart and assembled it with 90 degree on one site the other I could only manage 80.5.
Here before and after mechanical changes:
before:
after:
I have noticed everything is "low" now.
As far as for the hotend, the bowden tube to me looks very free on the first layer printing. Can you describe this more in detail?
talking about the stiff screws, do you mean the adjuster knobs? Cause they are pretty stiffened up. Maybe loosen them all the way and just go back a bit to set in place?
@Phaedrux if it would bin in line on the Y and closer to the nozzle? SO offset would be x+- 10 and y also +-10?
This is what I am using so no modification possible I believe.
I need to be educated. If the probe does the mesh level, it is at the same position the nozzle will be later when printing. Why does the offset effect it so much?
in this case I would need a mount for a micro swiss direct drive extruder with the probe in line with the Y axis. Hope google can help me there.
@Phaedrux said in Mesh Compensation working only half of the built plate:
Based on those numbers it does seem like you have a different trigger height from the left side to the right side.
3.495 vs 3.360
Try and get your printer squared up as much as possible. In a cartesian bed slider the bed (Y) and gantry (X) must be totally aligned. Mesh compensation can correct for a lot, but it assumes that the probe to nozzle offset is consistent regardless of XY position. There are certain mechanical situations such as skew of the X and Y axis that it can't really compensate for if the probe has an offset from the nozzle.
working on the tomorrow and keep you posted. It makes sense that its from hardware side since it has been consistent in any firmware.
Here are some results, hope I did it right:
x50 y50 3.495 mm
x100 y50 3.406 mm
x150 y50 3.312 mm
x200 y50 3.331 mm
x250 y50 3.362 mm
x300 y50 3.360 mm
x50 y100 3.511 mm
x50 y150 3.483 mm
x50 y200 3.483 mm
x50 y250 3.499 mm
x50 y300 3.546 mm
will that not show the same like the heightmap?
No even with the older version 2.05? I believe it was the same exact problem.
G32 in bed.g is disabled again only using G29
I was hoping it would extrapolate the data, but was not sure.
Will do the tests with G30 S-1 and report as soon as I am done.
I did run the Calibration of the Z offset, if I remember correctly, 3x 3.78 3.82 and 3.83
first test print just confirmed that nothing has changed. left side too close right not close enough
Warning: Skipping grid point (305.0, 85.0) because Z probe cannot reach it
yes it does that. But does that really explain all my problems? Left side to close, right side too far?
I checked the DWC and I see more then 4 points as you can see in the 2nd code box.
I changed the x-axis max to 345 and now it can reach more (X 280mm) testing a print soon to see if that changes anything.
Here is the result of the mesh:
0.106, 0.099, -0.021, 0.019, 0.029, 0.019, 0.017, 0.044, 0.082, 0.112, 0.106, 0.129, 0.156, 0.151, 0.341, 0, 0, 0
0.142, 0.125, 0.091, 0.041, 0.035, 0.030, 0.029, 0.019, 0.054, 0.085, 0.076, 0.069, 0.082, 0.064, 0.283, 0, 0, 0
0.101, 0.085, 0.051, 0.010, 0.020, 0.017, 0.017, 0.014, 0.059, 0.095, 0.084, 0.111, 0.131, 0.140, 0.305, 0, 0, 0
0.107, 0.072, 0.053, 0.014, -0.003, -0.006, 0.007, -0.008, 0.039, 0.061, 0.057, 0.077, 0.070, 0.069, 0.273, 0, 0, 0
0.114, 0.091, 0.057, 0.017, -0.010, -0.001, 0.005, -0.003, 0.036, 0.047, 0.051, 0.079, 0.090, 0.094, 0.247, 0, 0, 0
0.121, 0.087, 0.066, 0.019, -0.004, 0.006, 0.015, 0.002, 0.050, 0.056, 0.059, 0.064, 0.067, 0.062, 0.244, 0, 0, 0
0.090, 0.057, 0.050, 0.001, -0.025, 0.002, 0.000, -0.018, 0.039, 0.057, 0.064, 0.064, 0.100, 0.102, 0.255, 0, 0, 0
0.107, 0.065, 0.056, 0.005, -0.025, 0.011, 0.000, -0.008, 0.043, 0.047, 0.050, 0.039, 0.049, 0.050, 0.220, 0, 0, 0
0.146, 0.105, 0.090, 0.021, -0.014, 0.016, -0.010, -0.008, 0.019, 0.041, 0.045, 0.023, 0.055, 0.045, 0.194, 0, 0, 0
0.115, 0.076, 0.074, 0.015, -0.013, 0.013, 0.002, 0.006, 0.031, 0.055, 0.061, 0.034, 0.045, 0.031, 0.215, 0, 0, 0
0.114, 0.079, 0.070, 0.004, -0.025, -0.008, -0.008, 0.001, 0.013, 0.046, 0.059, 0.040, 0.081, 0.066, 0.231, 0, 0, 0
0.134, 0.097, 0.071, 0.013, -0.020, -0.010, -0.010, -0.003, 0.004, 0.030, 0.046, 0.021, 0.046, 0.025, 0.219, 0, 0, 0
0.095, 0.061, 0.044, -0.016, -0.044, -0.046, -0.036, -0.016, -0.004, 0.034, 0.045, 0.024, 0.081, 0.070, 0.235, 0, 0, 0
0.116, 0.077, 0.051, 0.009, -0.014, -0.028, -0.021, -0.005, 0.002, 0.054, 0.054, 0.031, 0.060, 0.047, 0.250, 0, 0, 0
rerunning it to compare
After playing around with the M557 and looking at the heightmap, I am curious if the problem could be the probe only goes to X 255mm as most far but the print is beyond it?
; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.1.4 on Sun Nov 15 2020 13:08:08 GMT-0800 (Pacific Standard Time)
; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"TevoTornado 2" ; 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 S0 ; physical drive 1 goes backwards
M569 P2 S0 ; physical drive 2 goes backwards
M569 P3 S0 ; physical drive 3 goes backwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z800.00 E127.00 ; set steps per mm
M566 X900.00 Y900.00 Z12.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X180000.00 Y180000.00 Z6000.00 E1200.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E950 I5 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout
; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X310 Y310 Z400 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-45.25 Y-8.28 Z3.53 ; set Z probe trigger value, offset and trigger height
M557 X5:265 Y5:265 S52 ; define mesh grid
; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as PT1000 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" T100000 B4138 ; sensor 1 ; configure sensor 1 as PT1000 on pin e0temp
M950 H1 C"e0heat" T1 ; create heater and map sensor 1 ; 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 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on
M950 F2 C"fan2" Q500 ; create fan 2 on pin fan2 and set its frequency
M106 P2 S0.5 H-1 ; set fan 2 value. Thermostatic control is turned off
; Tools
M563 P0 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
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss
M501
after updating to v3 today I got a message that the G32 will be no longer supported so take it out I guess?
RepRapFirmware height map file v2 generated at 2020-11-15 14:34, min error -0.197, max error 0.076, mean -0.085, deviation 0.066
xmin,xmax,ymin,ymax,radius,xspacing,yspacing,xnum,ynum
5.00,265.00,5.00,265.00,-1.00,52.00,52.00,6,6
0.076, 0.001, -0.086, -0.054, -0.030, 0
-0.010, -0.120, -0.145, -0.089, -0.041, 0
0.004, -0.101, -0.170, -0.125, -0.071, 0
-0.020, -0.132, -0.160, -0.108, -0.081, 0
-0.016, -0.160, -0.197, -0.131, -0.054, 0
0.025, -0.132, -0.178, -0.142, -0.094, 0
this could be set back to M561 G29 delete the rest since it will be no longer supported?
bed.g
; called to perform automatic bed compensation via G32
;
; generated by RepRapFirmware Configuration Tool v3.1.4 on Sat Sep 05 2020 23:38:17 GMT-0700 (Pacific Daylight Time)
M561 ; clear any bed transform
G29 S2 ; probe the bed and enable compensation //S2
; Probe 2-point
M401 ; Deploy probe - deployprobe.g
G30 P0 X5 Y5 Z-9999 ; Middle Left
G30 P1 X5 Y285 Z-9999 ; Middle Right
G30 P2 X285 Y285 Z-9999 ; Middle Right
G30 P3 X285 Y5 Z-9999 S4 ; Middle Right
M402 ; Retract Probe - retractprobe.g
Upgraded my Tevo Tornado with a Duet 2 Wifi board. I never was able to get the mesh bed leveling working 100%. Today I updated to the newer firmware 3. Hoping that could help. After making all changes it seems to be working just the same way. On the right side of the bed everything is loose and the left side smashed into the bed. I have a BLtouch. As soon as I get to the printer I will post config.g bed.g and the heightmap. If there is anything else I can get config wise let me know.