Topics created by michaelr123

@dc42

Is there any way to look up or request DWC to record the actual print time?

@michaelr123 Remember that running config.g does not reset things back to the default state before you run it. So anything that you do not explicitly set in the config.g will just keep whatever setting it may have had before you ran the config.g. Some commands may also not execute correctly (for instance if you had already assigned a pin in the old config.g, it may not be free if you try to use it for some other purpose in the new config.g). Personally I always reset things when making changes to config.g, just to be sure.

@Phaedrux

I'm an idiot, I was using temp_1 instead of temp_0 in my config. disregard, works great now.

@DuetUser

I've done this before for a dual drive Z axis on machines in the past without issue. You could give it a shot and report back how it went? The goals of an AWD system for a Voron is to shorten the belt paths, and to get as much power into the motion system as possible.

@dc42

Excellent, thank you!

Currently stuck looking at the Z-probe scanner and trying to decide if I want to throw that in the cart as well 😄

@michaelr123 said in CoreXY performance (max print speed) comparison:

............................. I know rapido uhf's claim they can hit 75mm3/s, not sure how possible that really is, ..............................

A lot depends on the filament. Something like PLA with a low viscosity will give a much higher volumetric flow rate than PET-G for example. When I was experimenting with 6 input, single nozzle multi-material hot ends, I tried some high flow rate prints using all 6 extruders in mixing mode, just out of curiosity. With a 1.5mm nozzle, 1.65mm layer width, 1mm layer height, I got and average flow rate for the entire print of 73mm^3/sec https://www.youtube.com/watch?v=gc8AciHjf4I but the best I could get with PET-G was around 44mm^3/sec using the same hot end, nozzle, layer width and layer height combination.

@Phaedrux said in Config Settings for AWD voron 2.4 - coreXY:

HA! so I have.

Look at HevORT, too. 😃

@droftarts

Awesome, thank you very much!

@michaelr123 in my opinion you're simply using too long arms. Long arms multiply the errors. If you're using 10 cm arms, you'll get much better solution. You can use cantileved mode to place the hotend a bit away from the last hinge. Placing the XY actuator with bigger distance will also help (but this conflicts with the short arms). I have/had similar problems with 6 axis robot, so this is from my experience (better would be parallel arms vertically or parallelogram structure. Stability could be gained by overconstraining with tensegrity methods also).

But if your project requirement is a big print area and you have time pressure, using CoreXY (or Cartesian in Gantry style) will probably be a better option.

I made a little tool to help you plan the arm lengths:
https://github.com/bondus/5barscara/tree/master/JS

Fetch the git and open the html in a browser. It's a very crude little tool where you can experiment with arm lengths and work modes, it renders the possible work area and you can mouse in the work area to see the arms.

well so far so good! I ran around 5 hours worth of prints yesterday and everything ran great!

I have no idea why grounding the floating X-axis fixes the problem but it seems to be looking pretty good.

I made a macro to speed things up. This is script I wrote:

M204 P10000 T10000 ; set acceleration
M593 P"EI3" S.025 F38 ; input shaping test 3/7/2022 change this as needed
G1 X-100 G4 S2 M956 P0 S1000 A0 G4 P10 G1 X100 F20000 ;movement code along X axis, collect data from accelerometer

One thing to remember as you're playing with accelerations, I think you need to update the M201 code in your config file to allow for an acceleration this high.

@phaedrux

I ran through wiring and discovered one had worn through the shielding near the connection point through the case. I patched this up and replaced the fuse, good as new!

Please send an email to warranty@duet3d.com and CC your reseller. Include a link to this forum thread and the details of your original purchase. You'll receive a reply with a form to fill out.

@boynextdoor

Hey there!

I appreciate the kind words! I don't run a blog or anything, but I've thought about documenting more of it as now I finally feel like its worthy of it! 😄

shoot me any questions you have on the build!

@michaelr123 said in Connecting to DWC v3.3.0 via wifi:

Would going to a raspberry Pi 4 help at all?

Should be ok on a pi3, but the pi4 definitely has a lot more breathing room. It might be a useful way to see if it's a hardware problem with
the Pi itself, which does occasionally happen.

@michaelr123 It appears I was able to fix the issue by updating the board through BOSSA, now I just need to get the config all setup again...

@michaelr123 said in DWC not accesible from one of my computers?:

Possibly was a cache thing?

Sounds plausible to me. Glad it's working out now.

https://duet3d.dozuki.com/Wiki/What_to_do_if_your_Duet_won't_respond

https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware#Section_Fallback_procedure_Num_3

See if these will get you connected.