Posts made by supernovae

@dc42 well, here's the odd thing. I read that link and thought I understood it. I was running 3.5rc1 on Github and it would always just move 1 axis and sit there.

Today, I saw you linked a newer RC1+ build. I installed that, went back to read the input shapping page and put in two movements and I got both movements.

So perhaps, i was hitting a bug in 3.5. Now things make a lot more sense - i thought i was missing a step or needed to click the play button that the second movement had next to it.

Now it complete more than 1 axis and it says motion profile #2 is complete.

Now its time for me to see the data and see what to do next may have more questions but at least this latest build unblocked me.

@dc42 awesome, I may give those a try thx for all your great work on this!

Is there any guide to figuring out input shaping? I can't really wrap my head around it.

I've got the Duet3d accelerometer connected and lit up and when I make a movement I can move an axis but i'm not sure what to do beyond that and when i think i'm moving multiple axis it just moves on the first and stops so i'm not sure what i'm doing.

3.5 rc1 seems long in tail - are there blockers for a stable release or has it gone back to drawing board?

@supernovae

Found the issue, I have some commands to set speed on layers and it shows up as X1500 which the regex catches... maybe i'll try and see if i can limit/exclude it lol

@pcr said in Only probe where printed. Solution here!:

@supernovae

easier solution

• (Cura slicer plugin) To make the macro to work in Cura slicer, you need to install the post process plugin by frankbags - In cura menu Help -> Show configuration folder. - Copy the python script from the above link in to plugins folder. - Restart Cura - In cura menu Extensions -> Post processing -> Modify G-Code and select Mesh Print Size (PLUGIN)

the

M557 X%MINX%:%MAXX% Y%MINY%:%MAXY% S8

Not sure if you can help, but running the python plugin and enabling the M557 in start gcode I always get a huge max X

For example:

looking at the gcode output:

M557 X131.900:1500.000 Y131.900:168.100 S35.000 ; Leveling mesh defined by LevelingMeshOptimizer

Not sure where 1500 comes from.. any idea where to look for in fixing/address that? Or anyone getting this in latest cura?

@phaedrux You were right, it finished - took 5110 seconds

Running 3.4b6 and ran m303 h0 s60 to PID tune hot bed after replacing a failed thermistor and it's been running almost 40 minutes

Temperature just seems to be going up and down slowly

Phase 4 has been 25 minutes itself.

@pcr So awesome! Thanks!!

FYI, if its not loading for you, rename the file to match exactly the class name - it is CaSE SenSiTive "LevelingMeshOptimizer.pl"

Found a post processing script for cura here: https://forum.duet3d.com/topic/14994/f-r-auto-define-m557-mesh-bounds-from-gcode/5?_=1637506151764

It would be nice if we could have the firmware parse this as defining it in every tool i use is a pain

Poked around in a sliced gcode from cura - it passes MIX/MAX as comments in beginning of gcode.

;FLAVOR:RepRap
;TIME:1813
;Filament used: 2.3164m
;Layer height: 0.28
;MINX:124.335
;MINY:124.335
;MINZ:0.24
;MAXX:175.665
;MAXY:175.664
;MAXZ:21.45
;Generated with Cura_SteamEngine 4.12.1

Looking to see if those are values that can be used in start... if not, may be able to write a small plugin that set variables

Doesn't look like cura has anything that is set as a user variable for print position max that I can find

Since Prusa announced their new technique of probing the bed only in print (wih their soon to be released XL) area to guarantee a good first layer, I saw the folks at Klipper have already posted up a macro.

https://gist.github.com/ChipCE/95fdbd3c2f3a064397f9610f915f7d02

Is this possible to pull off with Duet?

The gist shows how to do start gcode and the gcode for calculating the print area to mesh out.

Maybe i'll take a spin in porting it over next week. Just figured I'd ask if anyone has already done this

@dc42 said in PC Won't recognize paneldue:

@supernovae the PanelDue only presents the USB port when the firmware on it has been erased.

ahh, makes sense now! ty!!

@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

@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

Realized my paneldue is running really old 1.x firmware and when i connect it to my Win11 PC via USB it's not detected as a device, but it does power on and let me click around.

Any tips to get it to show up? Nothing seems to show up in device manager either.

@pcr I can't figure out PM or DM's here, but dropped you a chat thx!

@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)

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