Posts made by xHOBOPHOBIAx

I will keep testing, but I thing it is going like I am expecting now. I can feel the lead screws making small movements while printing so something is happening.

@Phaedrux I'll try those things. Thanks.

@DocTrucker said in I have to be missing something: Mesh bed leveling w/ BL Touch:

@xHOBOPHOBIAx said in I have to be missing something: Mesh bed leveling w/ BL Touch:

... That may be the issue.

I don't think you've said what you thought was the issue yet, and what sort of machine you are using?

Large coreXY printer. I am trying to print a small square at each corner and in the center to test bed level and mesh compensation. I home z with my BL Touch. I run the bed probing through the web interface. The front squares and the square in the middle of the bed have the same first layer where the two at the back of the bed are printing with the nozzle further from the bed.

I tried a large square just in the center of the machine and it's first layer looks uniform. I am thinking the back two squares in my first test were printing over an area of the bed that wasn't probed because of my BL Touch offset and that could be the cause of the issue.

So with that information it looks like the map is being created and loaded.

Does anyone know how the z height is calculated if the print head goes to an area where the probe was not able to hit? That may be the issue.

I am also seeing where it is being saved in the G-Code Console. So I guess my question now is how do I get it to load that map without running the entire probe cycle.

G32
323 points probed, mean error -0.019, deviation 0.035
Height map saved to file heightmap.csv

I am on the most recent firmware also.

@fcwilt said in I have to be missing something: Mesh bed leveling w/ BL Touch:

In your homeZ.g file, before executing G30, you are positioning X,Y to 210,215 - where do those values come from?

This is the center of my bed. I like to home z in the center.

@fcwilt said in I have to be missing something: Mesh bed leveling w/ BL Touch:

I put everything related to my Z probe into a macro file configprobe.g which allows me to make changes, as needed, without having to reboot the firmware.

Would you mind sharing that macro?

I have to be missing something... I don't think that the mesh map ever gets used when I am doing my first bed level tests.

; bed.g
; called to perform automatic bed compensation via G32
;
; generated by RepRapFirmware Configuration Tool v2 on Thu Jan 03 2019 22:56:02 GMT-0600 (Central Standard Time)
M561                ; clear any bed transform
M98 Pdeployprobe.g  ; deploy mechanical Z probe
G29                 ; probe the bed and enable compensation
M98 Pretractprobe.g ; retract mechanical Z probe
G29 S1              ; added because I read about it in Duet forum https://forum.duet3d.com/topic/4374/bed-mesh-compensation/5

In my config.g

; Z-Probe
M574 Z1 S2                                         ; Set endstops controlled by probe
M307 H3 A-1 C-1 D-1                                ; Disable heater on PWM channel for BLTouch
M558 P9 H5 F100 T2000                              ; Set Z probe type to bltouch and the dive height + speeds
G31 P500 X39 Y-47 Z1.20                             ; Set Z probe trigger value, offset and trigger height
M557 X45:405 Y50:370 S20                           ; Define mesh grid for gekotek
;M557 X45:420 Y20:430 S30                           ; Define mesh grid for buildplate
G29 S1                                              ; Load the last bed mesh autocalibration

I put a G29 S1 in both the homez.g and homeall.g. homez.g is below.

; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v2 on Thu Jan 03 2019 22:56:03 GMT-0600 (Central Standard Time)
G29 S2            ; clear bed map
G91               ; relative positioning
G1 Z5 F6000 S2    ; lift Z relative to current position
G90               ; absolute positioning
G1 X210 Y215 F4000; go to first probe point
G30               ; home Z by probing the bed
G29 S1            ; Load the last bed mesh autocalibration

Is there a way that I can take the config.g file that I have modified and convert it to the .json file so I can use the config tool to generate new homeing gcode?

Thanks. My mistake.

Do you have any plans to implement a firmware solution for XY, XZ, and YZ skew? I'm working on a large format printer and am finding Z axis skew to be a pain. It would be great if there was a feature that would straighten up things in the firmware.

I updated to the newest firmwares. The error appears to have gone away. Will check more times over the next couple of days and respond back if the error comes back.

@dc42 said in AJAX error while port fowarding:

Which versions of the firmware and DWC are you using? A change was made at version 2.0 and 1.21.1 so that DWC supplies the password again when it gets that response.

I'm probably still on 1.19. I'll have to check once I get home.

I have my duet wifi set up with static ip and fowarding the port to an external 8081 port. When I try to access it from outside of my network the web interface displays but I can't login to the duet and it gives an AJAX error. Error reason: Not authorized. is there something I need to do on my browser side?

Turns out the home all has an offset of 2.5 set after z home. Removed that and it appears to work fine.

This is some gcode that doesn't work.

G90
M82
M106 S255
G4 P500
M106 S0
M104 S205 T0
M109 S205 T0
G28 ; home all axes
G92 E0
G1 E-1.2000 F3000
G1 Z0.300 F990
; process Process2
; layer 1, Z = 0.300

; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool on Thu Oct 26 2017 22:04:46 GMT-0500 (Central Daylight Time)

; Move quickly to X axis endstop and stop there (first pass)
G1 Z-465 F1800 S1

; Go back a few mm
G91
G1 Z5 F6000
G90

; Move slowly to X axis endstop once more (second pass)
G1 Z-465 F360 S1

; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool on Thu Oct 26 2017 22:04:46 GMT-0500 (Central Daylight Time)

; Relative positioning
G91

; Lift Z
G1 Z5 F6000

; Course home X or Y
G1 X-465 Y-465 F1800 S1
; Course home X
G1 X-465 S1
; Course home Y
G1 Y-465 S1

; Move away from the endstops
G1 X5 Y5 F6000

; Fine home X
G1 X-465 F360 S1
; Fine home Y
G1 Y-465 S1

; Move Z down until the switch triggers
G1 Z-455 F1800 S1

; Absolute positioning
G90

; Tell the firmware where we are
G92 Z2.5

; Uncomment the following line to lift the nozzle after probing
;G1 Z5 F100

I'm homing z with a normal limit switch on a core XY machine. When I try to home z from the web interface, it works perfectly. When I home all axis from a gcode file the limit switch gets pressed, then the bet travels further up past the trigger height. Is there something I need to have in my slicer to tell it its a core XY?

; Configuration file for Duet WiFi (firmware version 1.17 to 1.19)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool on Thu Oct 26 2017 22:04:46 GMT-0500 (Central Daylight Time)

; General preferences
M111 S0 ; Debugging off
G21 ; Work in millimetres
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves
M555 P2 ; Set firmware compatibility to look like Marlin

M667 S1 ; Select CoreXY mode
M208 X0 Y0 Z0 S1 ; Set axis minima
M208 X420 Y430 Z415 S0 ; Set axis maxima

; Endstops
M574 S0 ; Define active low and unused microswitches
M574 X1 Y1 Z1 S1 ; Define active high microswitches
;M558 P0 X0 Y0 Z1 H5 F120 T6000 ; Set Z probe type to switch, the axes for which it is used and the probe + travel speeds
;G31 P600 X0 Y0 Z2.5 ; Set Z probe trigger value, offset and trigger height
M557 X15:445 Y15:445 S20 ; Define mesh grid

; Drives
M569 P0 S0 ; Drive 0 goes forwards
M569 P1 S0 ; Drive 1 goes forwards
M569 P2 S0 ; Drive 2 goes forwards
M569 P3 S0 ; Drive 3 goes forwards
M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
M92 X80 Y80 Z800 E446.23 ; Set steps per mm
M566 X900 Y900 Z12 E120 ; Set maximum instantaneous speed changes (mm/min)
M203 X10000 Y10000 Z1000 E1200 ; Set maximum speeds (mm/min)
M201 X800 Y800 Z250 E2500 ; Set accelerations (mm/s^2)
M906 X1600 Y1600 Z1600 E800 ; Set motor currents (mA)
M84 S0 ; Disable motor idle current reduction

; Heaters
M143 S260 ; Set maximum heater temperature to 260C
M140 H-1 ; Disable heated bed
M305 P1 B4725 C7.060000e-8 ; Set thermistor + ADC parameters for heater 1

; Tools
M563 P0 D0 H1 F1 ; 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

; Network
M550 PBig Boy ; Set machine name
M551 PNo1Knows ; Set password
M552 S1 ; Enable network
; Access point is configured manually via M587 by the user
M586 P0 S1 ; Enable HTTP
M586 P1 S0 ; Disable FTP
M586 P2 S0 ; Disable Telnet

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

; Custom settings are not configured

; Miscellaneous
T0 ; Select first tool

Thank you.

The wiring diagram is confusing me a bit. Is there a jumper to set the PWM fans to run off of 5v? Or do I need to connect + to expansion pin 1 and the - to the PWM ground?