Posts made by fieryjekyll

@droftarts Attached is the height map. I've tried both regenerating the height map and deleting it, rebooting the board, and loading the plugin again. The result is an error in both cases.

• heightmap.csv

@jay_s_uk I'm running DWC 3.4.5 on a Duet 2 WiFi with firmware 3.4.5.

A few days ago the height map plugin stopped working for me. I've tried loading DWC from different computers and different browsers and the result is always the same. When the Duet starts up, the height map plugin is not loaded. When I try to manually start it, I get the following error:

ChunkLoadError: Loading chunk HeightMap failed. (error: http://10.19.33.140/js/HeightMap.41c8a697.js)

These are the messages that show up in my JS console:

GET http://10.19.33.140/js/HeightMap.41c8a697.js net::ERR_CONTENT_DECODING_FAILED 200 (OK)

ChunkLoadError: Loading chunk HeightMap failed.
(error: http://10.19.33.140/js/HeightMap.41c8a697.js)
    at Function.requireEnsure [as e] (bootstrap:166:18)
    at DwcPlugin.loadDwcResources (index.js:83:27)
    at loadDwcResources (index.js:33:17)
    at _callee5$ (index.js:192:10)
    at tryCatch (runtime.js:63:40)
    at Generator.invoke [as _invoke] (runtime.js:294:22)
    at Generator.next (runtime.js:119:21)
    at asyncGeneratorStep (asyncToGenerator.js:3:20)
    at _next (asyncToGenerator.js:25:9)
    at asyncToGenerator.js:32:7

Any ideas? Everything else about DWC seems to work fine. Do I need to reinstall DWC?

Hello. I'm confused about homing behavior with RepRapFirmware 3. I'm using the default homedelta.g that was generated by the RRF config tool, and I'm using a Duet 2 WiFi on a Mini Kossel.

My build height is 240mm (actually 241.619mm). When I power up my printer, regardless of the actual state of the printer, RRF sets the x, y, and z coordinates to (0, 0, 240), the home position, and reminds me that the axes have not yet been homed.

When I home the axes (G28), the carriages move up to the top of the printer, but the resulting position is not reset to the home position. This leads RRF to set the printer's position to something completely outside of the build dimensions, e.g. (0.1, 0.2, 443.7). Basically, it is adding the amount of Z travel to the initial, default position.

Below is my homedelta.g, which is unmodified from what I got from the RRF config tool.

; homedelta.g
; called to home all towers on a delta printer
;
; generated by RepRapFirmware Configuration Tool v3.2.1 on Mon Jan 18 2021 01:46:04 GMT-0800 (Pacific Standard Time)
G91                        ; relative positioning
G1 H1 X265 Y265 Z265 F1800 ; move all towers to the high end stopping at the endstops (first pass)
G1 H2 X-5 Y-5 Z-5 F1800    ; go down a few mm
G1 H1 X10 Y10 Z10 F360     ; move all towers up once more (second pass)
G1 Z-5 F6000               ; move down a few mm so that the nozzle can be centred
G90                        ; absolute positioning
G1 X0 Y0 F6000             ; move X+Y to the centre

The behavior is problematic because the firmware thinks the printer head is somewhere that it is not. When I home the printer again, I'll get an error: G0/G1: target position not reachable from current position. If I try to calibrate the printer in this state (G32), the print head will crash into the bed.

If this is the default behavior, then I have to believe this configuration is working for most people. So am I doing something wrong?

To make the printer useful at all, after homing, I manually reset the z coordinate to the build height (which I've determined from calibration). Is this something I'm supposed to add to homedelta.g myself?

Thanks.

Doug