@dc42
So i did another round of tests with a better setup.
Backlash is approx 20-24 microns with empty bed weight 1.2kg. With 2.2kg on the bed the backlash is approx 14 microns. Backlash is pretty much the same (within 10%) when reversing either direction.
200 step motor, 10:1 reduction, 20T pulley at 16i means 800 steps/mm
.024 * 800 = 19.2 microsteps = 1.2 full steps. Could that be applied instantaneously without issue? M425 with S0 could enable this if feasible from a code standpoint.
@engikeneer
Adding a 2.2kg load to the bed (which weighs approx 1.2kg) changed the backlash from about 22 microns to about 14 (there's a variance of a few microns).
I have a machine with 1Z cantilever bed. I'm using a Stepper Online 10:1 precision planetary gearmotor for Z.
I'm measuring a backlash of 0.044mm. (which is about 80% of the datasheet max backlash). 22% of a standard 0.2mm layer height
With a M425 Z0.044 S1
There's too much lag in compensating the backlash to make bed mesh really useful.
Ideally i'd like it taken up as fast as the stepper motor driver can take the steps on the reversal. Can we have an option for that? Like -S0 says do the backlash comp as soon as is possible?
@dc42 if ram is a constraint, then that's an acceptable reason for duet2. But, i'd prefer if some other features were limited (like the LPC port does) to free up ram to support it.
If there isn't 2 axis input shaping in rrf3, I will await the klipper port to duet3. Duet3 mini port has been completed.
Input shaping is THE killer feature. And 2 axis is essential for it to work well.
I should try the same shaper and freq for both axis to see how that impacts print results. Away from printer until monday...
Some before and after pix (ignore the schmoo near the bottom. i have a fan connection that is wonky). 2K to 14K accel at top. 200mm/s
The current RRF documentation for M593 indicates that there's a single frequency selectable for the input shapers. Will this be changed to support independent frequencies and shapers per axis? Machines are far from iso-resonant, so choosing one frequency and shaper for both axis will yield a sub optimal result.
Bedflingers in particular have radically different resonant frequencies.
On my crossed gantry 500x330 printer, one axis is best served by a 46hz ZV and the other by 68hz MZV shaper (according to klipper recommendations).
@arhi said in PanelDue Improvement Tips:
TBH it is easier to make slicer name file with YYMMDDHHmm prefix
Unfortunately PanelDue sorts A-Z so the most recent files are at the bottom, requiring scrolling.
Would be really nice if PanelDue allowed you to set the sort order.
@dc42 said in Duet 3 Mini 5+ : Initial announcement:
We have reduced the stepper driver support from 5+3 to 5+2. T
Deal killer for me. Oh well. I was excited for this board. It was going to be the recommended board for CroXY.
I'm using a hemera on my d300 (with linear rails). it works fine and gets great prints.
https://www.thingiverse.com/thing:4027625
I'm using tricklaser arms which don't pop off like magball arms do. I'd be very hesitant to use magballs and a direct drive extruder.
Check the railcore discord. A used rc with first class components ya was posted about 10 days ago.
My #1 feature request is an option to sort the gcode filenames by date. 99% of the time I want to print the file I just uploaded.
Scrolling thru all the files, while trying to remember what I just uploaded is pretty annoying. I end up with a lot of gcode files that look like aaaaaaSomeobject.gcode with the aaaaaaa to get it to sort at least to the first page. Obviously this isn’t a very good workaround.
@wingtip I'm fighting the same issues with dual X and dual Y motors. Can you post your final config.g and homeall.g (or homex.g)? Might be able to figure out my problem without needing to make a new post.
Thanks.
Ah. Wish i could try the different order. 
@dc42 said in Toolboard Extruder Motor Stutters (most of the time):
ly tried to fetch and install the firmware, and the LED would flash at intervals. If you turned the power off while it was writing to flash memory, perhaps that corrupted the bootloader (it's not clear from the datasheet whether the bootloader protection provides adequate protection if power is removed while another part of the flash memory is being written).
What I would like you to do now is to disconnect the CAN connector from the tool board, and once again power the board up while both buttons are held down (then release them after powering up). If the
The .bin file was the same one I originally flashed to the Toolboard that was uploaded to /sys
Just tried a reboot with CAN disconnected and buttons pressed. No LEDs on between the buttons, and no bootloader/CAN connection.
@dc42 said in Toolboard Extruder Motor Stutters (most of the time):
an has identified the root cause of the original problem: your M906 command that sets the extruder current was earlier in config.g than the M584 command that defined the extruder driver. So the motor current wasn't being set, which would result in less than 100mA current.
In original post: "Increasing current to 1500 with M906 just makes it louder.", so Ian's theory isn't correct. (wasn't totally obvious that I did that with the console)
Ugggh, so this is weird. I updated the firmware thinking it could have been a firmware issue (long shot, I know).
M997 B20
After waiting many miinutes with no response, I power cycled.
'
Now the Duet3 isn't communicating with my Toolboard - tons of CAN response timeouts. No slow red flash, just the solid blue and solid red leds. The heater and fan turned on (I see the warning about that in the docs), so i removed all connections to the board except CAN and power and stepper.
I tried a double button power on to reset.
M115 B121 (or 10 or 20, the address i previously programmed) also error.
M409 K"boards" yields this:
{"key":"boards","flags":"","result":[{"canAddress":0,"firmwareDate":"2020-03-16b1","firmwareFileName":"Duet3Firmware_MB6HC.bin","firmwareName":"RepRapFirmware for Duet 3 MB6HC","firmwareVersion":"3.01-RC4","iapFileNameSBC":"Duet3_SBCiap_MB6HC.bin","iapFileNameSD":"Duet3_SDiap_MB6HC.bin","mcuTemp":{"current":29.4,"max":29.5,"min":18.3},"name":"Duet 3 MB6HC","shortName":"MB6HC","supports12864":false,"v12":{"current":12.2,"max":12.3,"min":12.2},"vIn":{"current":23.9,"max":24.0,"min":23.9}}]}
Seems the bootloader got corrupted.
Is there a bossa solution to reprogram the bootloader on a Toolboard?
1-2: 2.2 ohms
3-4: 2.2 ohms
All other pairs are 2.5 megaohms or more
Board was on Hemera, but i used extra standoffs in addition to the plastic ones and clipped the protruding part leads to shorten them. Happens with the board off the Hemera as well.
Attached pics from the world's finest $15 USB microscope. Solder on the leads looks a little blobby.
I tried two different connector harnesses. No crimping done by me because one side done by ldo the other is the pigtail supplied with the toolboard. The solder connections I made are more than sound. However to test the bad connector theory I made up a 2nd cable. Same problem. I also measured resistance across the a+/a- and b+/b- on the toolboard and they are correct - 2 ohms as expected with no shorts to ground.
Also, ran the hemera with the cover off so the bare pinion gear was free to turn. Still stutters.
I think the driver is bad or bad toolboard connection . The solder on the tmc2209 pins is less than perfect. There might be an unintentional solder bridge between 2 of the pins on the atmel chip. Hard to tell.
Board: Duet 3 MB6HC v0.6 or 1.0 (MB6HC)
DSF Version: 1.2.5.0
Firmware: RepRapFirmware for Duet 3 MB6HC 3.01-RC4 (2020-03-16b1)
Board TOOL1LC firmware 3.01-RC4 (2020-03-16b1)
After doing a 5mm extruder move:
M122 B20
Diagnostics for board 20:
Board TOOL1LC firmware 3.01-RC4 (2020-03-16b1)
Never used RAM 8.2Kb, max stack 604b
HEAT 1132 CanAsync 1460 CanRecv 1392 TMC 212 AIN 532 MAIN 2304
Last reset 00:00:57 ago, cause: software
Driver 0: short-to-ground standstill, SG min/max 0/302, read errors 0, write errors 0, ifcount 44, reads 28602, writes 2, timeouts 0, DMA errors 0, failedOp 0xff
Moves scheduled 4, completed 4, hiccups 0
VIN: 24.0V
MCU temperature: min 33.3C, current 35.8C, max 35.8C
Ticks since heat task active 55, ADC conversions started 57796, completed 57795, timed out 0
Last sensors broadcast 00000002 found 1 59 ticks ago
Free CAN buffers: 36
NVM user row b1d088a9 fffff8bb 20003b9c 20003ba8
TSENS 000ddf GAIN 016461 OFFS 002a69 CAL 1f2f
3/18/2020, 8:29:45 PM