I LOVE THIS!
I cant believe no one thought of this earlier.
I know for myself, I sometimes get confused because there are so many ways to use a duet and I can't find an example for say a Cartesian vs a delta. The duet team does such a good job with documentation but it is an impossible task for a small team to give so many examples. (now that i own 3 duets im a little better).
I imagine this will be another invaluable resource. Especially for people just starting out.
I seem to be having the same issue. First it only happened in the first few layers like in the pictures. Usually in the same spot but not always. I was generally able to just restart the print and have it work fine. However, I just lost one halfway through. The printer just stops, heater and fans are still running and the web interface thinks that the print is still running. It give me the option to pause but nothing happens. Very weird. I have included an m122 readout below. I will reduce the microstepping as you suggest. Just doing my part to help diagnose.
M122
=== Diagnostics ===
Used output buffers: 3 of 32 (9 max)
=== Platform ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 1.21 running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DDM-9FAM2-LW4S8-6JTDG-3SD6R-13YMX
Static ram used: 16152
Dynamic ram used: 100536
Recycled dynamic ram: 2096
Stack ram used: 1224 current, 6632 maximum
Never used ram: 5656
Last reset 01:30:37 ago, cause: power up
Last software reset at 2018-04-29 01:54, reason: User, spinning module GCodes, available RAM 5656 bytes (slot 3)
Software reset code 0x0003 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x04417000, BFAR 0xe000ed38, SP 0xffffffff
Error status: 0
Free file entries: 9
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 126.7ms
MCU temperature: min 19.7, current 30.5, max 31.0
Supply voltage: min 23.7, current 23.8, max 24.3, under voltage events: 0, over voltage events: 0
Driver 0: standstill, SG min/max 0/393
Driver 1: standstill, SG min/max 0/1023
Driver 2: standstill, SG min/max 0/267
Driver 3: standstill, SG min/max 0/1023
Driver 4: standstill, SG min/max not available
Driver 5: standstill, SG min/max not available
Driver 6: standstill, SG min/max not available
Driver 7: standstill, SG min/max not available
Driver 8: standstill, SG min/max not available
Driver 9: standstill, SG min/max not available
Expansion motor(s) stall indication: no
Date/time: 2018-04-30 14:58:10
Slowest main loop (seconds): 0.980719; fastest: 0.000051
=== Move ===
MaxReps: 508091, StepErrors: 0, LaErrors: 0, FreeDm: 121, MinFreeDm 120, MaxWait: 3635039563ms, Underruns: 277, 0
Scheduled moves: 64659, completed moves: 64629
Bed compensation in use: mesh
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
Heater 0 is on, I-accum = 0.0
Heater 1 is on, I-accum = 0.8
=== GCodes ===
Segments left: 1
Stack records: 2 allocated, 0 in use
Movement lock held by null
http is idle in state(s) 0
telnet is idle in state(s) 0
file is doing "G1 X135.148 Y112.675 E0.0579" in state(s) 0
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Responder states: HTTP(1) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
UPDATE!!
I was in the process of rebuilding my x axis carriage and I ended up rewiring everything. I recently came upon a load of fancy igus flex wiring (which is also shielded) so I decided to use that and replace all the crappy copper coated tin stuff that was there before.
Long story short- the fans are quiet as can be now. Of All the things I thought the new wire would possibly improve that was on the bottom of my list.
SO… if you have noisy blower fans when they are subject to PWM- get some nice wire.
Does anyone have a good source for flexible stranded all copper wire? It always seems way to expensive or like the seller may be trying to push copper coated stuff as all copper.
This is a little thing_
If you have fat fingers , like me, it is easy to misfire on even the 7 inch panel due. The Extrude button on the Extrude menu in the lower left hand corner is right next to the highest settings for extrusions. I only set these when I am retracting. There have been many times where I am trying to retract and I accidentally hit extrude and BOOM… im trying to extrude 100mm at 100mm/s.
If it was reversed the extrude button would be on the side with the slower extrusion speeds and vice versa..
Small issue.
I just got an Prusa MK3 in the mail. I will try their 24v blower fan.
Im a little confused when you say "Change the PWM frequncy". Isnt that what is happening when you go from 20% to 100% fan power?
The fans all run fine at 100% but they do not like anything under S1.0. Sounds like a plane taking off. I print mostly petg so i like to keep my fan at like 20%ish. I just go no fan now because its SOOOOO noisy.
Anyone have recommendations for 24v blower fans that play nice with the duet PWM. Ive tried a handful of <$10 from china and they all sound horrible unless they run at 100%. I'm happy to spend the money for the right one. I just dont want to add any more to my stack of noisy 24v blowers.
thanks!
Im late to the party here . Loving the data points that the filament monitor allows to be recorded.
My question is this…
Does either non-linear extrusion or pressure advance do anything to retraction or do they just solely address this issue via speed and extrusion? Im no expert, but would increasing retraction as speed increases help at all? i could see Deckingman, who has issues with over extrusion during fast prints, wanting the opposite of linear extrusion.... can you supply negative values in the gcode? would linear retraction also be a valuable tool?
Do you think it would be possible to roughly quantify nozzle pressure by say....
doing a bunch of printing moves 1 layer high at a specific speed and then stopping the extruder but continue to move the print head in a line on the bed. My Im guessing you could get an idea of the relative nozzle pressure by the length of the line printed before the nozzle stops oozing.
Im looking forward to getting a filament monitor so that I can come to the data point party.
Id be very interested in this as well. Mremy id be happy to nerd out on this with you. I'd love the ability to set up a secondary microcontroller that can send gcode commands to the duet. I have this idea of using a raspeberry pi or ESP8266 with a secondary touchscreen that I can use to make a custom GUI where I can easily customize a list of my frequently used macros. It cant be that hard. I guess I could do it through the WIFI.
Are there any resources or even better, tutorials, that you have run across that explain in detail how to communicate with the duet from outside sources?
having trouble with Wifi disconnects in RC2. I updated from an earlier beta where everything was fine. Cant seem to stay connected for more than 5 mins now. I just added a duex5 and rewired everything so there is a chance I tweaked something in the process but im pretty sure I had no issues after the rewire until RC2…. Anyone else? Is the last 19 beta living somewhere to roll back to?
anything I can do to help identify a bug in either the version or my own work? Im not super familiar with the debugging process but im pretty good at following directions.
Also the new web interface killed my dark theme. I had to roll that back to 19.3
Which version of DuetWiFiServer are you using?
I was using 1.20beta11… Ill try beta10. I thought the update notes said to use beta11 when it was available
I may have fixed the issue. The name of the printer on my router was different than the name of the printer in the config.g file. For some reason the new firmware made my router unhappy. I have this issue sometimes with raspberry pi's and esp8266 boards that have static IPs. Not sure what changes made this happen or if it was just coincidence. I wonder if others have this issue.
Cheers
having trouble with Wifi disconnects in RC2. I updated from an earlier beta where everything was fine. Cant seem to stay connected for more than 5 mins now. I just added a duex5 and rewired everything so there is a chance I tweaked something in the process but im pretty sure I had no issues after the rewire until RC2…. Anyone else? Is the last 19 beta living somewhere to roll back to?
anything I can do to help identify a bug in either the version or my own work? Im not super familiar with the debugging process but im pretty good at following directions.
Also the new web interface killed my dark theme. I had to roll that back to 19.3
Which version of DuetWiFiServer are you using?
I was using 1.20beta11… Ill try beta10. I thought the update notes said to use beta11 when it was available
having trouble with Wifi disconnects in RC2. I updated from an earlier beta where everything was fine. Cant seem to stay connected for more than 5 mins now. I just added a duex5 and rewired everything so there is a chance I tweaked something in the process but im pretty sure I had no issues after the rewire until RC2…. Anyone else? Is the last 19 beta living somewhere to roll back to?
anything I can do to help identify a bug in either the version or my own work? Im not super familiar with the debugging process but im pretty good at following directions.
Also the new web interface killed my dark theme. I had to roll that back to 19.3
I have a duet wifi and I am currently setting up a duex5 for a diamond hot end. There seems to be a lot of non-essential functionality to exploit via the uncommitted IO pins- especially with the on board voltage converters. I have a stack of raspberry pis, esp8266, and various sensors and chips to the roof and Id love to see some of y'alls usage of these things to get myself inspired and more importantly….. informed.
I am particularly interested in being able to connect the printer to my MQTT server so that I can issue Alexa based voice commands. If I could tell the echo to raise the hot-end 10mm without having to go through all the menus it would be my nerdy dream come true. I have learned through much trial and error the ins and outs of the little micro processor boards but messing around with my $350 of duet hardware seems like a bad idea. Im happy to break a $4 Lolin in the pursuit of higher education but not so much my pride and joy printer.
I cant seem to find any good tutorials or resources for some more advanced ideas.
So here is your chance to brag about your setup to someone who actually cares! (unlike everyone i know who just smiles, nods, and trys not to yawn. Maybe you all have cooler friends than I do).
Thanks for a nudge in the right direction.
I installed the new firmware and I have been good so far…
Cartesian Printer. Running at 256 microsteps. unfortunately i didnt get any good diagnostics when i was having the error. Is there anything I can pull that would be helpful?
I'm running beta 10 on a cartesian, no problems to report.
Seems to be a delta/scara kinematics problem…
I had the issue on my Cartesian printer. I have since restored to the previous firmware and it is fine now. I just pulled off the whole y-axis to do some tweaking so I cant pull up anymore info.
I sliced using S3d.
I had the same issue with the skew.
=== Move ===
MaxReps: 130, StepErrors: 123, FreeDm: 240, MinFreeDm 120, MaxWait: 2228747316ms, Underruns: 0, 0
Scheduled moves: 2721, completed moves: 2721
Bed compensation in use: mesh
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
seems like there are a lot of step errors for 3 layers
me too! Ive been in the aliexpress rabbit hole all day. My mailbox is going to be stuffed in 30-90 days
I like the KK's. I designed and built my rig from scratch so I would have had to do the crimping no matter what. I dont have much experience with the green terminals but in my experience anything with a screw in a place where you may be tweaking is bad. If you are in a perpetual state of rewiring, you will eventually strip the screw.
Im not sure why duponts are the king of the hill. they are the only connectors that you cant "properly" crimp with a cheap $30 crimper because they are a little cockeyed. I lucked out and found an "official" dupont crimper on ebay for $50 which i restored.
My only crimping issue is with those stupid JST PH connectors that are on the stepper motors. I have spent at least a duet ethernets amount of money on tools and connectors trying to crimp my own stepper harnesses. Fail fail fail….
Rant over. My vote will always be for function over convenience The former usually leads to the latter. I would be open minded to consider the benefits of the "phoenix" connectors though.
Have you tried swapping out the motors? or even swapping the x and y for lack of another pair.
Id buy one for sure! I was never thrilled about the idea of the duet filament sensor getting pinched between two gears. However, I trust that the Duet crew and beta testers knew better than me. THe proof is always in the pudding. I would have bought one of those and been just as excited about it once it got the seal of approval. I do like the idea of nothing touching the filament though.