Should the selections under Settings / User interface and List items remain after a printer on/off restart. Mine is reverting back to default.
Posts made by str8up
-
RE: FINAL (I hope) RRF 1.20 release candidate 4 and DWS 1.20RC1
-
RE: Recomendation Extruder/Nozzle
Nimble in use here. Great addition. Very easy to load. I did have to drop my feed rate though.
-
RE: New beta firmware release 1.20beta10
Same here as well. Back to wifiserver 1.20beta9.
-
RE: New experimental firmware 1.20 alpha 2
OK i give up. Where are the gcode files going on the micro SD card?
-
RE: Duet WiFI 1.19.2 from 1.18 upgrade - DWC won't connect
A little off topic. Can someone tell me where the gcode files are being saved on SD card 0? It goes through the download process. I have to change directories to something off root before it shows up. Another thing I am seeing is my setting - Temp additions ATX on / off are not there after a restart. I am using 1.19 +3.
-
RE: New firmware 1.18RC1
Here is the heightmap.csv data.
RepRapFirmware height map file v1 generated at 2017-02-30 10:19, mean error -0.01, deviation 0.12
xmin,xmax,ymin,ymax,radius,spacing,xnum,ynum
-100.00,100.10,-100.00,100.10,105.00,20.00,11,11
0, 0, 0, 0, -0.107, -0.261, -0.329, 0, 0, 0, 0
0, 0, 0.041, -0.028, -0.038, -0.016, -0.050, -0.051, -0.177, 0, 0
0, -0.032, -0.144, -0.122, -0.152, -0.150, -0.120, -0.119, -0.113, -0.012, 0
0, -0.034, -0.019, 0.040, 0.043, 0.100, 0.131, 0.080, 0.059, 0.122, 0
0, -0.098, -0.132, -0.081, -0.059, -0.030, 0.039, -0.010, 0.059, 0.109, 0.153
0, -0.078, -0.041, 0.017, 0.089, 0.109, 0.170, 0.161, 0.193, 0.159, 0.202
0, -0.140, -0.159, -0.080, -0.032, 0.050, 0.067, 0.137, 0.160, 0.151, 0.121
0, -0.071, -0.059, -0.039, -0.068, -0.018, 0.012, 0.077, 0.191, 0.270, 0
0, 0, -0.122, -0.237, -0.149, -0.061, 0.020, 0.060, 0.117, 0.102, 0
0, 0, 0, -0.128, -0.093, -0.043, -0.021, 0.048, 0.090, 0, 0
0, 0, 0, 0, 0, -0.052, -0.069, 0, 0, 0, 0 -
RE: New firmware 1.18RC1
David,
Thanks and respect for all your hard work on this.
Installed 1.18RC1 yesterday. After running Auto Cal then Mesh leveling I checked to see if the mesh compensation was active with M122. Are the Bed probe heights correct? This is a delta printerAM
M122
=== Diagnostics ===
Used output buffers: 1 of 32 (11 max)
=== Platform ===
Static ram used: 20304
Dynamic ram used: 72928
Recycled dynamic ram: 976
Stack ram used: 968 current, 11264 maximum
Never used ram: 25600
Last reset 15:05:08 ago, cause: software
Last software reset code 0x0003, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x00400000, BFAR 0xe000ed38, SP 0xffffffff
Spinning module during software reset: GCodes, available RAM 33056 bytes (slot 1)
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 2.8ms
MCU temperature: min 26.3, current 31.2, max 39.5
Supply voltage: min 0.3, current 23.3, max 25.2, under voltage events: 1, over voltage events: 0
Driver 0: stalled standstill
Driver 1: stalled standstill
Driver 2: stalled standstill
Driver 3: standstill
Driver 4: standstill
Date/time: 2017-03-29 11:54:37
Slowest main loop (seconds): 0.087280; fastest: 0.000000
=== Move ===
MaxReps: 5, StepErrors: 0, MaxWait: 49669874ms, Underruns: 0, 0
Scheduled moves: 21597, completed moves: 21597
Bed compensation in use: mesh
Bed probe heights: 0.000 0.000 0.000 0.000 -0.116
Probe change coordinates:
=== Heat ===
Bed heater = 0, chamber heater = -1
Heater 0 is on, I-accum = 0.0
Heater 1 is on, I-accum = 0.4
=== GCodes ===
Segments left: 0
Stack records: 3 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
Code queue is empty.
=== Network ===
WiFiServer is running
SPI underruns 0, overruns 0
=== Webserver ===
HTTP sessions: 1 of 8 -
RE: Mesh Bed Leveling
Thanks DC42,
Is there another way to tell if the compensation is working because it doesn,t seem to be having any effect on my printer. -
RE: Mesh Bed Leveling
Greetings all.
I am new to the DuetWiFi and the BLtouch probe. Although I get a mesh map and I have G29 S1 in the config.g file I see no Z changes as I try to print. I use M122 to see it the mesh is being called and it appears to be so. I am using a Delta style (Delta Trix on Instructables web site) printer. It will print ok with out the Auto Delta Configuration or the bed mesh but I believe it could do better with both. I am trying to pickup as much information from this forum.