Posts made by jnofsinger

@dc42

I have a very sturdy ender3 frame with corner blocks and all wheels removed for rails. I also have removed the glass bed to reduce weight. Tests run with

M203 X12000 Y12000 Z500 E1200 ; Set maximum speeds (mm/min)
M201 X3000 Y3000 Z250 E250 ; Set accelerations (mm/s^2)
M566 X300 Y300 Z20 E600 ;jerk

After running multiple tests with ei3 and zvddd is that canceling the high frequency in the graph produces the best overall result. ( I have not done Y yet only X)

Here is no shaping and speeds from 30, 45, 60, 75, 90, 105, 120, 135, and 150mms for both X and Y

here is the best I can get so far using ZVDDD 78.9

here is the backside view of ZVDDD 78.9

very impressive overall happy with ZVDDD and the higher frequency cancel. I will try again with the mount on Y to see if I can tune Y itself. Although not part of the latest beta firmware in my case I could use a separate Y frequency cancel.

I might try to play around with sampling as you suggested in the other thread to smooth at lower speeds. I normally print around 75/90mms but many smaller prints can't get up to speed so I do need a better cancel at lower also.

Jim

@dc42 said in what to tune out with input shaping:

G1 X-50 G4 S2 G1 X50 F20000 M400 M956 P0 S1000 A0

I have 3.4.0beta6 installed right now. That command definitely showed a different kind of graph.

using ei3 and tuning out the 78.2 peak produces this result

here is zvddd tuned

I assume that is what is desired for input shaping... no large spikes? I don't think ei3 is the best shaper to use, i'll try with others also.

Thanks
Jim

Hello everyone,

I have hooked up an accelerator board to the duet and it is pretty awesome. Just wanted to verify while running (running latest beta firmware)

G1 X-50 G4 S2 M956 P0 S1000 A0 G4 P10 G1 X50 F20000

with no input shaping I get this result

I assume that we should ignore the start and end of sample (100mhz)? So the object is to have a pretty straight line between those 2 points?

When setting input shaping to ei3 f20 I get this line

and setting it to ei3 f40 I get this line

should I keep trying different input shapers and f numbers? is it better to have a flatter line on the low end? 20mhz or in the middle/end like 40mhz produces for me? or should I try to tune out the 100mhz line instead? (not sure if any input shaper can do that though?)

I know at the end of the day whatever looks best is what I should try in a print, just trying to understand the tricks/process of tuning itself.

Thanks,
Jim

@dc42

I am trying them now and see that ei2 did a much better job at getting rid of the X and Y overall. I noticed there is 1 place where the ripples are still around which I am testing with zvd/d next.

I assume there is a min speed which input shaping needs to happen? the low end of my tests are all the same at 30mm/s which isn't good.

Is there any tuning with speeds left after input shaping in general? I guess pressure advanced isn't something to use either or does that still help retraction?

Thanks for your time and effort in making reprap/duets very relevant and fun

In the quest to have the perfectly tuned printer I started playing with input shaping on my duet wifi. here is what I did to test and what machine I have

ender3 skeleton with .9 degree steppers, lighter bed, direct drive hero me5, dual axis, rails on x, rails on y, 16 tooth pulley (yeah I like to play with upgrades).

set
M203 X12000 Y12000 Z500 E1200 ; Set maximum speeds (mm/min)
M201 X3000 Y3000 Z250 E250 ; Set accelerations (mm/s^2)
M566 X300 Y300 Z20 E600 ;jerk

and used the ringing_tower.stl from Klipper at .2 layer height in vase mode using a .35 nozzle.

all tests performed for 20 layers starting at 30, 45, 60, 75, 90, 105, 125, 140, 165mm/s (I usually print at 60)

the singular picture is with no input shaping... ghosting even at 30

here is a picture of no input shaping, input shaping DAA at 24 and input shaping DAA at 42 (which I calculated using math)

to my eyes any input shaping was better than nothing, but the calculated DAA 42 at 90mm/s print speed came out the best and it is really noticeable. still a tiny bit of ghosting left.

I still have ringing at Y which I don't think can be fixed? I think the math would come out a bit different as the ripples appear longer.
they are not as bad though as X was.

What else could I try to improve quality? would the new beta code be different with ZVA?
is there a reason to tune Jerk values would it even help get rid of the last ripples?

It is amazing the print quality you can achieve with a Duet... I have had this board for 5 years now and it has just been amazing.

Thanks,
Jim

@the-big

I would verify the exp.heater3 pin is in use for the BLTouch. I am using heater7 otherwise it is the same. does it work differently when you "homeall" vs "homez"?

the heater rising too slowly is an known message and you can fix it by PID tuning (the better explanation is on the duet website)

My fan line is pretty similar to yours other than using S1.0 instead of S1 (doubt that would make a difference). Do the fans still work though?

Hello,

I have been researching some options for Dual Z with a Duet Wifi. I don't really expect it to do too much for my printer, but I do love tinkering with the mechanical options

I think there are 3 options for the Duet Wifi?

• use the secondary port (located under Z slot)

• use E1

• use a splitter cable

To use the full advantage of Z compensation you would need to use E1 as an independent Z2?
https://duet3d.dozuki.com/Wiki/Bed_levelling_using_multiple_independent_Z_motors

Has anyone used E1 with multiple probe points before? how well does it work for you?

Also I would assume the splitter cable although is convenient is overall the worst option of the bunch since we have onboard options with the Duet.

Would also rather not have to crash home similar to what I hear the Prusa printers and at least my Ender5+ has to do to keep everything in sync from time to time. That is why the multi z probing has peaked my interest.

Thanks
Jim

So this is now fixed! The mosfets were damaged. The ones I had are black so they are very difficult to see the damage till I took the board out of the printer.

I ordered the newer ones from Digikey before the storm, so they Monday.

I can say this is the first time I replaced such a small part on the board, but with enough patience and practice on a scrap board it is completely do-able without expensive gear. I just have a regular $50.00 iron and a very small tip.. I then just dragged it over the ends and the solder stuck!

it was just pretty strange the under-voltage issue with the broken mosfets... not sure how long they were blown as the heater fan I have is 5v and it was pulling 4.4v for awhile.

Thanks again for your help!

Jim

@Phaedrux

I will investigate and report the results.

@Phaedrux

That would certainly explain why the errors would never clear unless the printer was powered off. Thanks for the explanation.

@Phaedrux

files posted. Thanks for looking Phaedrux

Jim

entire config.g

; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.1.4 on Thu Aug 27 2020 15:36:37 GMT-0400 (Eastern Daylight Time)

; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Ender3" ; set printer name Ender3!

; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S1 ; disable FTP
M586 P2 S0 ; disable Telnet

; Drives
M569 P0 S0 ; physical drive 0 goes backwards
M569 P1 S0 ; physical drive 1 goes backwards
M569 P2 S1 ; physical drive 2 goes forwards
M569 P3 S1 ; physical drive 3 goes backwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X200.00 Y100.00 Z400.00 E869.11 ; set steps per mm

M566 X800 Y800 Z24 E3000 ; set maximum instantaneous speed changes (mm/min)
M203 X9000 Y9000 Z180 E6000 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z100 E5000.00 ; set accelerations (mm/s^2)

M906 X800 Y800 Z800 E1000 I50 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Axis Limits
M208 X-3.0:232.5 Y4.5:212.0 Z0:250 ; set axis minima and maxima

; Endstops
M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop
M574 Z1 S2 ; configure Z-probe endstop for low end on Z

; Z-Probe
M950 S0 C"exp.heater7" ; create servo pin 0 for BLTouch
M558 P9 C"^zprobe.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds use P9 for BLTouch
G31 P500 X-57 Y-10 Z3.150 ; set Z probe trigger value, offset and trigger height
M557 X25:172.6 Y25:203.9 S20 ; define mesh grid

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
M307 H0 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M308 S1 P"e0temp" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M308 S3 P"spi.cs1" Y"thermocouple-max31856" ; configure sensor 2 as thermocouple via CS pin spi.cs1
;M950 H3 C"e1heat" T3 ; create chamber heater output on e1heat and map it to sensor 2
;M307 H3 B1 S1.00 ; enable bang-bang mode for the chamber heater and set PWM limit
;M141 H3 ; map chamber to heater 3

M307 H1 R3.710 C142.5 D1.45 S1.00 V24.6 ; PID tune e0heat new style v6
M307 H0 R0.294 C414.8 D0.66 S1.00 V24.4 ; PID tune bedheat winter

; Fans
; Fans
M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0.0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1.0 H1 T45 ; set fan 1 value. Thermostatic control is turned on
M950 F2 C"fan2" Q25000 ; create lights and set its frequency
M106 P2 S0.0 H-1 ; set lights0 value. Thermostatic control is turned off

; Tools
M563 P0 D0 H1 F0 ; define tool 0
G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C
T0 ; select first tool

; Pressure Advance
M572 D0 S0.060 ; pressure advance for a direct drive setup (aka retration)

; BLTouch startup
G4 S2 ; Pause a couple seconds
M280 P64 S160 ; Clear any alarms
G4 S2 ; Pause a couple seconds
M402 ; retract pin just in case

; Custom settings are not defined

; Miscellaneous

@Phaedrux said in Odd PWM fan voltage:

M98 P"config.g

2/12/2021, 11:18:49 AM Error: in file macro line 85: M280: parameter 'P' too high
2/12/2021, 11:18:48 AM M98 P"config.g"
HTTP is enabled on port 80
FTP is enabled on port 21
TELNET is disabled

M122

2/12/2021, 11:17:31 AM M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2 running on Duet WiFi 1.0 or 1.01
Board ID: 08DAM-999TL-MQ4S8-6J9D4-3SJ6N-K4B3W
Used output buffers: 3 of 24 (24 max)
=== RTOS ===
Static ram: 23460
Dynamic ram: 73540 of which 156 recycled
Never used RAM 14924, free system stack 99 words
Tasks: NETWORK(ready,163) HEAT(blocked,309) MAIN(running,452) IDLE(ready,19)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 22:30:09 ago, cause: power up
Last software reset at 2021-02-11 12:33, reason: User, GCodes spinning, available RAM 14924, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x04
Aux0 errors 0,0,0
MCU temperature: min 25.1, current 33.0, max 40.3
Supply voltage: min 23.9, current 24.3, max 24.7, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: position -600, standstill, SG min/max 0/344
Driver 1: position 450, standstill, SG min/max 66/310
Driver 2: position 11982, standstill, SG min/max not available
Driver 3: position 0, standstill, SG min/max 0/1023
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: 2021-02-12 11:17:27
Cache data hit count 4294967295
Slowest loop: 217.12ms; fastest: 0.16ms
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 52.5ms, write time 11.0ms, max retries 1
=== Move ===
DMs created 83, maxWait 2521067ms, bed compensation in use: mesh, comp offset 0.113
=== MainDDARing ===
Scheduled moves 7237, completed moves 7237, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 8, 5], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 0 is on, I-accum = 0.0
Heater 1 is on, I-accum = 0.5
=== 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: 200.38ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 2 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.25
  WiFi MAC address 5c:cf:7f:2b:ee:bf
  WiFi Vcc 3.48, reset reason Turned on by main processor
  WiFi flash size 4194304, free heap 24576
  WiFi IP address 172.16.37.118
  WiFi signal strength -55dBm, mode 802.11n, reconnections 0, sleep mode modem
  Clock register 00002002
  Socket states: 0 0 0 0 0 0 0 0

I have this in my RR3.x configuration (see below) duet wifi 1.01 board

Fan0 works as it is turned off at 0 and on when the slider increases all the way 100.

Fan1 the hotend fan just stays on.. I don't mind as it is a 5v noctura so it is silent at least.

Fan2 when the Duet is turned on it is 24v, when fan2 slider is moved to 100 it drops to 20v??

From what I can tell are the PWM1/2 gone? I haven't done anything recently just tuned on the printer this morning. If that is the case I assume I can use a relay/extra pwm pin/power supply combo to make it work?

I don't know what else to look for in determining what could be wrong, suggestions? Would inverting the PWM fan pin work?

M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0.0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q25000 ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1.0 H1 T45 ; set fan 1 value. Thermostatic control is turned on
M950 F2 C"fan2" Q25000 ; create lights and set its frequency
M106 P2 S0.0 H-1

@stuartofmt

So far so good! I have a 72 frame capture and will print another test. The logs are clean and did not show any disconnects. Will continue to test it tonight and let you know.

Great program for the duet. I do have a question, do you plan on offering a flag to flip images with the ffmpeg processing? My camera is flipped as it comes from the top of my Ender3.

Thanks,
Jim

@stuartofmt

I have a Duet Wifi 1.01 board. it has been with me for a very long time and is impossible to kill ;).

I can just have the program open and it will throw those errors even when not printing. If I switch it to take picture every x seconds it will work fine. Your idea of some type of communication issue between the pi and duet is correct. I also have the webcam from the duet pointing to the same URL for a quick print and it stays connected.

I will try it again with the .1 version and see if it improves. Also I will remove the webcam url from the duet itself to see if something differs.

Thanks
Jim

Hello,

Trying out 3.2.0 and running into the following issue (below). The print starts fine and captures a handful of images till the connection reset issue. Both the duet and the pi are running on the same wifi subnet, and the duet is the latest firmware version.

running with the following options (have more logs if needed)

/usr/bin/python3 /home/pi/Desktop/images/DuetLapse3.py -port 8181 -verbose -duet 172.16.37.118 -detect layer -camera1 stream -weburl1 http://127.0.0.1:8080/?action=stream

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/usr/lib/python3.7/threading.py", line 917, in _bootstrap_inner
self.run()
File "/usr/lib/python3.7/threading.py", line 865, in run
self._target(*self._args, **self._kwargs)
File "/home/pi/Desktop/images/DuetLapse3.py", line 1068, in captureLoop
oneInterval('Camera1', camera1, weburl1, camparam1)
File "/home/pi/Desktop/images/DuetLapse3.py", line 612, in oneInterval
zn = getDuetLayer(apiModel)
File "/home/pi/Desktop/images/DuetLapse3.py", line 733, in getDuetLayer
r = requests.get(URL, timeout=5)
File "/usr/lib/python3/dist-packages/requests/api.py", line 75, in get
return request('get', url, params=params, **kwargs)
File "/usr/lib/python3/dist-packages/requests/api.py", line 60, in request
return session.request(method=method, url=url, **kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 533, in request
resp = self.send(prep, **send_kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 646, in send
r = adapter.send(request, **kwargs)
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 498, in send
raise ConnectionError(err, request=request)
requests.exceptions.ConnectionError: ('Connection abort

@gtj0

Awesome it works! handful of undefined things, but i think that is to be expected.

Thanks for the quick turnaround... I tried for 2 days to get it working

Yes the latest beta2 standalone and zip uploaded via duet web control