Release 3.2beta2 and mesh
-
good morning guys
last night I installed Release 3.2beta2 and a strange thing happens
when I go to mesh the plate, the graphical representation of the calibration does not come out on the screen and makes me see the one memorized previously, therefore totally useless, it had happened to me also with Release 3.2beta1, I thought that things had changed but nothing.
-
6/10/2020, 11:40:50 M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2-beta2 running on Duet WiFi 1.02 or later
Board ID: 08DGM-917NK-F23T0-6JTD0-3S06T-TYAJF
Used output buffers: 3 of 24 (12 max)
=== RTOS ===
Static ram: 24028
Dynamic ram: 100252 of which 44 recycled
Exception stack ram used: 560
Never used ram: 6188
Tasks: NETWORK(ready,143) HEAT(blocked,294) MAIN(running,451) IDLE(ready,19)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:49:49 ago, cause: power up
Last software reset details not available
Error status: 0x00
MCU temperature: min 18.6, current 31.1, max 31.3
Supply voltage: min 23.2, current 23.5, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: position 47672, standstill, SG min/max 0/122
Driver 1: position 1616, standstill, SG min/max 0/150
Driver 2: position 2768, standstill, SG min/max 0/3
Driver 3: position 0, standstill, SG min/max not available
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 2020-10-06 11:40:49
Cache data hit count 4294967295
Slowest loop: 17.35ms; fastest: 0.18ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 4.3ms, write time 2.1ms, max retries 0
=== Move ===
Hiccups: 0(0), FreeDm: 169, MinFreeDm: 167, MaxWait: 2397106ms
Bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 85, completed moves: 85, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 0 is on, I-accum = 0.8
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
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
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 15.92ms; fastest: 0.00ms
Responder states: HTTP(2) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8- WiFi -
Network state is active
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.23
WiFi MAC address 84:0d:8e:b3:b4:8a
WiFi Vcc 3.39, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 24200
WiFi IP address 192.168.178.22
WiFi signal strength -64dBm, reconnections 0, sleep mode modem
Clock register ffffffff
Socket states: 4 0 0 0 0 0 0 0
=== Filament sensors ===
Extruder 0 sensor: ok
- WiFi -
-
ok I just discovered that the page doesn't refresh, I have to do it manually with F5, as a browser I use chrome
-
Yeah same here, we still have a bug I believe.
-
I can confirm this and I've got a fix ready. It will be part of the next beta.
-
good boy
-
problem solved with Release 3.2beta3.2
-
thanks you guys
