[3.4.0beta6] M32 Response too long error check console

supernovae

Click True Bed Leveling (m32)

Starts and runs to completion - throws error notification "response to long check Console" but there is nothing in console other than showing lead screw adjustments.

bed.g

; bed.g
M561 ; clear any bed transform

if !move.axes[0].homed || !move.axes[1].homed || !move.axes[2].homed
	G28
  
T-1

while true 

	G30 P0 X25.0 Y155.0 Z-9999 ; probe near a leadscrew - left
	G30 P1 X285.0 Y150.0 Z-9999 S2  ; probe near a leadscrew - right

	if move.calibration.initial.deviation <= 0.01
		echo "Leveling successful. Deviation: " ^ move.calibration.initial.deviation ^ "mm"
		break
	if iterations >= 10 
		break
	echo "Repeating leveling because deviation is too high (" ^ move.calibration.initial.deviation ^ "mm)"
 
G28

M98 P"config.g"
HTTP is enabled on port 80
FTP is enabled on port 21
TELNET is disabled

m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.0beta6 (2021-11-06 11:37:41) running on Duet WiFi 1.02 or later
Board ID: 08DGM-917DA-G4MSJ-6JTD6-3SN6L-1TRR9
Used output buffers: 3 of 24 (13 max)
=== RTOS ===
Static ram: 23772
Dynamic ram: 75760 of which 56 recycled
Never used RAM 9564, free system stack 124 words
Tasks: NETWORK(ready,14.0%,245) HEAT(notifyWait,0.0%,310) Move(notifyWait,0.0%,297) MAIN(running,85.5%,440) IDLE(ready,0.5%,30), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:04:22 ago, cause: power up
Last software reset time unknown, reason: User, GCodes spinning, available RAM 15236, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 23.4, current 32.6, max 32.7
Supply voltage: min 24.0, current 24.1, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/484/484, gc cycles 0
Driver 0: pos 54400, standstill, SG min 0
Driver 1: pos 1600, standstill, SG min 0
Driver 2: pos 2967, standstill, SG min 0
Driver 3: pos 0, standstill, SG min n/a
Driver 4: pos 0, standstill, SG min 0
Driver 5: pos 0
Driver 6: pos 0
Driver 7: pos 0
Driver 8: pos 0
Driver 9: pos 0
Driver 10: pos 0
Driver 11: pos 0
Date/time: 2021-11-10 10:36:08
Cache data hit count 4294967295
Slowest loop: 7.56ms; fastest: 0.14ms
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 1.5ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 3, maxWait 27327ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 62, completed 62, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 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: 171.70ms; 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.26
WiFi MAC address 80:7d:3a:3f:f3:25
WiFi Vcc 3.41, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 23328
WiFi IP address 192.168.1.116
WiFi signal strength -70dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 4 0 0 0 0 0 0 0

jay_s_uk

@supernovae that's pretty normal.
The popups can only be so many characters so when they're longer than a set number, they're pushed to the console

supernovae

@jay_s_uk nothing shows up in console

Just looks like it finished but the popup says something and my re-try logic re-tries and eventually gets it (so it seems)

T3P3Tony

@supernovae which version of DWC are you running?

Phaedrux

@supernovae said in [3.4.0beta6] M32 Response too long error check console:

but there is nothing in console other than showing lead screw adjustments.

The "response too long" message is trying to tell you that the lead screw adjustments results are too long to show as a popup and to see them in the console.

supernovae

@t3p3tony said in [3.4.0beta6] M32 Response too long error check console:

@supernovae which version of DWC are you running?

I'm running Duet Web Control 3.4.0-b6

supernovae

@phaedrux said in [3.4.0beta6] M32 Response too long error check console:

@supernovae said in [3.4.0beta6] M32 Response too long error check console:

but there is nothing in console other than showing lead screw adjustments.

The "response too long" message is trying to tell you that the lead screw adjustments results are too long to show as a popup and to see them in the console.

oh hahaha.. it took a bit for my brain to digest that. I was thinking there should be another error in the console not that the leadscrew adjustment warning was too big to show.

I think DWC used to show it in a green box but now it just throws that error popup