Posts made by illy

@jay_s_uk thank you for the information!

@jay_s_uk Thank you for your response, but I could not see any information about the Wifi module after sending a M409 command.

{"key":"","flags":"","result":{"boards":[{}],"directories":{},"fans":[{},{},{},{}],"heat":{},"inputs":[{},{},{},{},{},{},{},null,null,{},null,{}],"job":{},"limits":{},"move":{},"network":{},"scanner":{},"sensors":{},"seqs":{},"spindles":[{},{},{},{}],"state":{},"tools":[{},{}],"volumes":[{},{}]}}<LF>ok<LF>

Hi everyone,

This is the response I get after sending a M408 S0 R1 command in 3.1.1:

{"status":"I","heaters":[23.9,24.1,24.2],"active":[0.0,0.0,0.0],"standby":[0.0,0.0,0.0],"hstat":[0,0,0],"pos":[294.000,27.000,5.194],"machine":[294.000,27.000,5.494],"sfactor":100.0,"efactor":[100.0,100.0],"babystep":0.300,"tool":-1,"probe":"0","fanPercent":[0.0,100,100,0,0,-1,-1,-1,-1,-1,-1,-1,-1],"fanRPM":[-1,-1,-1,-1],"homed":[1,1,1],"msgBox.mode":-1}<LF><LF>ok<LF>

In RRF 3.0 there is still an information about our Wifi module ("resp":....), but now it's completely gone. This has an impact on my display software. I can not see the IP address anymore on the display.

I've also tried with a M408 S0 command without R1, but I got the identic response as before (with R1).

Maybe someone can help me. Thankyou!

It's because your g1 x y move to position the probe also contains a z move. Z hasn't been homed yet so it's complaining. At the start of the file you're already lifting the z axis with an S2 move so you don't need to move it again afterwards.

@Phaedrux It's working now. Thank you! But my main problem is not solved yet. The mesh bed compensation does not compensate the uneven bed during printing as you can see in the pictures above. Maybe you also could help me.

@Phaedrux I've just tried it. I commented out all the M564 commands and did not change another commands in the homing files. I homed X and Y first and then G28 Z. It reported the same error as before.

@Phaedrux said in Improving mesh bed compensation with M558 HX:

@sykb said in Improving mesh bed compensation with M558 HX:

M350 X256 Y256 Z256 E16:16 I1 ; Set 16x microstepping with interpolation

It's not recommended to use x256 microstepping. It has a high load on the CPU for step generation and there's very little reason to use it. Use x16 with interpolation to x256 enabled. Lower cpu load and you still get the benefit of quiet smooth motor movement.

I'll try it later, thank you for the support!

@peter247 I always ran G29 S0 at full working temperature. 220c extruder temperature and 60c bed temperature. That's correct, right?
@Phaedrux I tried to home Z with G28 Z command and it reported an error. This is my full config.g:

; Communication and general
M575 P1 B57600 S0 ; Baud rate
M111 S0 ; Debug off
M550 PDISCOVERY ; Machine name

; Networking
M552 S0
M586 P0 S1 ; Enable HTTP
M586 P1 S0 ; Disable FTP
M551 Preprap ; Machine password
M586 P2 S0 ; Disable Telnet

; Ethernet networking: Adjust the IP address and gateway in the following 2 lines to suit your network
M552 P0.0.0.0 ; (0 = DHCP)
M554 P192.168.169.255 ; Gateway
M553 P255.255.255.0 ; Netmask

; Basic Settings
M555 P0 ; Set output to look like RepRap_Firmware
G21 ; Work in millimetres
G90 ; Send absolute coordinates
M83 ; but relative extruder moves

M208 X-39 Y-10 Z0.0 S1 ; Set axis minima
M208 X300 Y220 Z320 S0 ; Set axis maxima

M143 H1 S295 ; Max. Extruder temp
M143 H0 S125 ; Max. Heatbed temp

; Endstops
M574 X1 Y1 S1 ; Set endstops at low side, active high endstop input
M574 Z0 S2 ; Z endstop at low end, Z probe is used

M558 P5 X0 Y0 Z1 I0 H5 A3 F120 T6000 ; Set Z probe type

G31 P600 X32.7 Y35 Z0.5 ; Set Z probe trigger NEW
M557 X67:270 Y75:265 S101.5:90 ; Define mesh grid NEW

; Axis and motor configuration
M667 S0 ; Set Cartesian Mode

; Achsen Motor Richtung
M569 P0 S0 ; Drive 0 goes backwards
M569 P1 S1 ; Drive 1 goes forwards
M569 P2 S1 ; Drive 2 goes forwards

; Extruder Motor Richtung
M569 P3 S1 ; Drive 3 goes forwards
M569 P4 S1 ; Drive 4 goes forwards

M350 X256 Y256 Z256 E16:16 I1 ; Set 16x microstepping with interpolation
M92 X1600 Y1600 Z8533 U1600 ; Set axis steps/mm
M92 E2700:2700
;M92 E1800:1800
M906 X1100 Y1100 Z900 E500 I30 ;E855 I30 ; Set motor currents (mA) and motor idle factor to 30%
M201 X2000 Y2000 Z500 E120 ; Accelerations (mm/s^2)
M203 X30000 Y30000 Z1200 E1200;E3000 ; Maximum speeds (mm/min)
M566 X900 Y900 Z12 E40:40 ; Maximum instant speed changes mm/minute

; Thermistors
M307 H0 A86.5 C432.2 D6.4 I0 B0 S1.0 V12.0

;M140 H-1 ;tells the firmware, there is no bed termistor

; Put your own H and/or L values here to set the bed thermistor ADC correction
M305 P0 T100000 B3950 R4700 H30 L0

; Put your own H and/or L values here to set first nozzle thermistor ADC correction
M305 S"Extruder0" P1 T100000 B4725 R4700 H30 L0 C7.06e-8

; Put your own H and/or L values here to set 2nd nozzle thermistor ADC correction
M305 S"Extruder1" P2 T100000 B4725 R4700 H30 L0 C7.06e-8

; Fans
M106 P0 S1.0 I0 H1 T45 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned on; davor 500
M106 P1 S1.0 I0 H2 T45 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on

M106 P2 S1.0 I0 F500 H-1 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P3 S1.0 I0 F500 H-1 ; Set fan 3 value, PWM signal inversion and frequency. Thermostatic control is turned off

M106 P4 S1.0 I0 F500 H-1 ; Set fan 4 value, PWM signal inversion and frequency. Thermostatic control is turned off

M106 P2 S0
M106 P3 S0

; Tool definitions
M563 P0 D0 H1 F2 S"Extruder0" ; Define tool 0
G10 P0 R0 S0 ; Set tool 0

M563 P1 D1 H2 F3 S"Extruder1" ; Define tool 1
G10 P1 R0 S0 ; Set tool 1

; Definiert den X Offset
G10 P0 X-32.7 L1 ; tool 0 offset
G10 P1 X32.7 L1 ; tool 1 offset

; Prepare magnet control pins
;M307 H4 A-1 C-1 D-1 ; Heater 4 off for freeing the pin
;M307 H5 A-1 C-1 D-1 ; Heater 4 off for freeing the pin
;M42 P4 S0 ; switch on the magnet
;M42 P5 S0

M208 S1 Z-0.2 ; set minimum Z

; Filament Sensor 0
M591 D0 P2 S1 C3

; Filament Sensor 1
M591 D1 P2 S1 C4

; SERVOS SETUP
M307 H6 A-1 C-1 D-1
M307 H7 A-1 C-1 D-1
M42 P6 S0
M42 P7 S0

M570 H1 P3000 T50
M570 H2 P3000 T50

M98 P/macros/OVERRIDE_CFG_MACRO ;Run override macro of webinterface

M98 P/macros/OVERRIDE_EXTRUDER_MACRO_0 ;Run override macro of webinterface for tools

M98 P/macros/OVERRIDE_EXTRUDER_MACRO_1 ;Run override macro of webinterface for tools

M572 D0:1 S0.2 ;Pressure advance

G28

M98 P/macros/T_freeAll ;Free all Tools

M98 P/macros/OVERRIDE_NETWORK_MODE ;Run override macro for network

@peter247 yes a real physical print with filament. This is the test print of the first layer. Thank you for your support so far, I really appreciate it

You can see the print quality difference in some position in the pictures below. I did not see any mesh bed compensation applied there that compensated the uneven bed. (please tell me, if I'm wrong)

As you can see in the first picture (right side), there is a huge quality difference between above and below.

Right side:

left side:

@peter247 the problem is the mesh bed compensation. It seems to not be working correctly or maybe not working at all. I've tried varying the H parameter in the M558 command but I always got the same test print result. No improvement. "A large dive height could tolerate a very uneven bed or poor calibration". But it doesn't work for me.

@peter247 250x210x325 mm. Yes, the probe can go outwards without hitting anything.

@Veti I've tried S30 (49 points) in RRF 2.05.1 and this is the result:

And then I did a test print but got the same result as before.

@Phaedrux I've changed the code to S30 in the M557 command and to H10 A6 S0.01 in the M558 command, but there is still no improvement. I've also tried removing the M564 commands in the homing files, as you suggested, but after that I could not home Z at all and got an error report saying: Error: G0/G1: insufficient axes homed.

And this the height map with the changed parameter:

Thank you everyone for your response and sorry for my slow response. I'll try all your suggests.

@peter247 yes, the off set is correct. I can show you a picture.

@Veti yes, I have not changed it. I just wanted to show you how it looks with 9 points. I'll update the firmware first to 2.05.1 and try with S10 or S15, as you suggested.

@Phaedrux I've tried adding M558 A parameter in 2.02 and didn't get a better result. I'll try it again but in 2.05.1.

I'm using an inductive sensor as probe. You can also see it on the picture above.

@deonholt yes, you also have to define the X and Y min and max values, as @fcwilt said.

@Veti

@peter247 I'm using probe to home Z

Hi everyone!

I think my mesh bed compensation is not working correctly (maybe not working at all). I've tried to vary the H parameter in the M558 command but it didn't get better, always got the same result. It's a cartesian printer with RRF 2.02.

I've tried it with H30 and then G29 S0. I've also sent a M122 command. "Bed compensation in use: mesh".

This is the code in config.g:

M558 P5 X0 Y0 Z1 I0 H5 A3 F120 T6000 S0.01 ; Set Z probe type
G31 P600 X32.7 Y35 Z0.5 ; Set Z probe trigger
M557 X67:270 Y75:265 S101.5:90 ; Define mesh grid

homeall.g:
G91 ; relative positioning
G1 Z5 F6000 S2 ; lift Z relative to current position
G1 S1 X-382 Y-457 F1800 ; move quickly to X and Y axis endstops and stop there (first pass)
G1 X5 Y5 F6000 ; go back a few mm
G1 S1 X-382 Y-457 F360 ; move slowly to X and Y axis endstops once more (second pass)
G90 ; absolute positioning
M564 S0 H0
G1 X33.5 Y27 Z15 F6000 ; go to first bed probe point and home Z
M564 S0 H1
G30 ; home Z by probing the bed

homez.g:
G91 ; relative positioning
G1 Z5 F6000 S2 ; lift Z relative to current position
G90 ; absolute positioning
M564 S0 H0
G1 X33.5 Y27 Z15 F6000 ; go to first probe point
M564 S0 H1
G30 ; home Z by probing the bed

I would like to know if there is another way to improve the mesh bed compensation or if I've done something wrong with the H parameter. Look forward to your help, thank you!

@dc42 it also happens to the tprex.g files, but it moves downwards after the last G1 Z-2 command instead of upwards. Is it because of the Z offset that being applied and cancelled after a tool change?

@dc42 I think yes. The Z offset is 0.89 mm. This is the code in the macro file:

G10 P0 X-32.85 Y-2 Z0.89 L1

I've also tried with a M400 command but it did not help me.

Hi everyone!

I have just upgraded my firmware from RRF 3.0 to 3.1.1 and found out that there is a strange movement in the tfreex files. It moves upwards after the last G1 Z-2 command in the tfreex.files.

tpre0.g

M400

G91
G1 Z2
G90

G1 X-30 F12000
G1 X-39.5 F1000
G4 P300
M280 P0 S155
G4 P300
G1 X-30 F12000

;G91 ; commented out, the user Z coordinate is restored immediately
;G1 Z-2
;G90

and this is the tfree0.g

G91
G1 Z2
G90

G53 G1 X-30 F12000
G53 G1 X-39.5 F1000
G4 P300
M280 P0 S60
G4 P300
G53 G1 X-30 F12000

G91
G1 Z-2
G90

I look forward to your help. Thanks!

@dc42 problem solved, thanks a lot!