Topics created by kb58

@achrn and @kb58, filamentPresent was removed from the object model in RRF 3.2 as documented in the change list. Use the "status" field instead.

@kb58 you can connect it to the main board if instead of configuring it via M591 you configure it as a GpIn pin and set up a M581 trigger on it.

It means that the heating and cooling rates didn't settle down to consistent values after several cycles. One possible reason is noise in the temperature sensor readings, which would be apparent in temperature graph. However, your graph appears to be stable, at least in the time scale it can display.

@fcwilt Okay, thanks. This relates to my earlier comments about not knowing "who wins" as far as applying settings. Prusa sets temperature and other filament-related variables, yet, so can the printer/Duet code, so it was confusing about who's driving the bus, so to speak. Your configuration makes it clear that the Duet code applies all pertinent settings.

@kb58 said in Can the XY travel speed between G30 test points be changed?:

Ah, okay, I see what you did. While I'm sure that it works, it sort of "cheats" in that it requires what sw engineers call "magic numbers." That is, if you ever redefine your probe points, you have to remember to also change a second set of number, potentially located somewhere else.

Why not set variables for the test points, then reference them in the G30 commands? Meets the goal of not having to hard code those numbers in twice.

@kb58 said in How do I enable the hot end heater:

@fcwilt I may add in several print statements to see what the tool state is, but obviously that's not a fix, but would still be curious where or how it's not happening.

I wish the DWC had a means to search all files which would make finding errant code bits easier.

Yes I can download everything into my standalone editor which will do such a search but I tend to avoid doing it.

Frederick

@cosmowave Found it.... wow, the consequences of having placed a block of code a ways down the screen and meaning to come back to it. Forgetting about it, all I'd see when checking the file was the first code block.

How about you guys just go have a nice day and I'll pretend that I didn't trouble you! Thanks for the quick reply, guys.

https://github.com/Duet3D/RRF-machine-config-files/tree/master/DBotCoreXY/x0r-wifi-RRF3/macros

You might find some good examples in there as well.

@Phaedrux, thanks for the pointers to the wiki. I've read it before but the step describing setting the tool to the new operating temp after tpre#.g is executed disappeared from my memory.
My pseduo code for the three files are:

tfree:
;!0. Remember the tool location.
;!1. Lower the bed a bit.
;!2. Retract the filament a bit.
;!3. Call the nozzle wiping macro (if we make one).
;!4. Set the nozzle temperature to a standby value.
;!5. Move the tool in front of the tool dock.
;!6. move the tool into the dock.
;!7. Call the macro that turns the tool latch to the unlatched position.
;!8. Move the tool carrier back from the tool dock.
;!9. Perform some task that confirms the tool was really left on the dock and is not still attached to the carrier, or fell out of the dock. No idea how to do this yet.
;!10. Return to the remembered location.

tpre:
;!0. Heat the nozzle to it's target temperature.

tpost:
;!1. Lower the bed a bit so we don;t hit anything.
;!2. Switch to the master coordinate system so we can find the tool dock.
;!3. Move to a position just in front of the tool dock.
;!4. Move the tool carrier into the docked tool position (advance Y).
;!5. Call the macro to lock the tool to the carriage.
;!6. Move backout of the dock. Hopefully we have something that verifies the tool is porperly docked.
;!7. Switch to this tools coordinate system (means engage it's offsets in X, Y, and Z).
;!3. Execute the wiping macro (if we make one).
;!4. Move back to the remembered location

@kb58

Always glad to help when I can.

Frederick

@kb58 said in Is there a cure for embarrassing oozing?:

@fcwilt As you've mentioned, there are so many variables associated with 3D printing, often interrelated, it makes for a long process of sorting them all!

Indeed.

The same can be said of slicers. I normally using Simply3D (S3D) but I have Cura and Prusa which I keep up to date.

I try them every once in a while but their default settings don't work well for me and it's another long process to get to know them as well as I know S3D.

PLA works well for most of what I do.

I have some other kinds of filament I wish to try but I tend to postpone starting down that rabbit hole again.

Try dropping your extruder temp in 5 degree steps. You also up your retraction in 1mm steps.

I prime and clean the nozzle at the start of a print and it gets busy printing the skirt long before any significant oozing occurs.

Frederick

@kb58 said in Heaters turn off while bed moving to print start position:

I had no idea about the M703 command. I see that if no filament config file is present, it will do nothing and not flag an error. This still leaves the question of where the heaters are getting switched off, since the actual sliced file being sent to the printer doesn't appear to be turning them off.

I've got a house full of guests but if I get I chance I will work to determine what is happening.

Frederick

@kb58 If you haven't seen or used this guide on basic calibration yet it's a good starting point. A level bed and proper flow rate is the foundation of a good print.

https://duet3d.dozuki.com/Guide/Ender+3+Pro+and+Duet+Maestro+Guide+Part+4:+Calibration/40

@kb58 Yikes!

@paulhew said in Pin name for extruder driver on Toolboard 1.1:

M584 X0.0 Y0.1 Z0.2:0.3:0.4 E20.0

That was it! Thank you very much; I think I've been staring at this too long today

@diy-o-sphere this is scheduled for fixing in release 3.4.

Oh, snap! Yes, you reminded me that new firmware needs to be in /Firmware. Fixed, and thank you, sir!

@kb58 said in PSA for DWC losing connectivity, it's not always the Duet3:

Thank you for the replies. The Duet3 has a hard-coded Ethernet address. Once it connects, it's solid until I unplug it. "Most of the time" it reconnects without issue, but 2-3 times the laptop just goes brain dead about the physical connection. I'll have to find out what a crossover cables is... I'm guessing it's got swapped wires. If that's the problem, how is the current cable still working most of the time?

Your laptop probably has an Ethernet port that attempts to auto detect whether the connections need to be crossed or not. The connections need to be crossed when you connect the laptop directly to the Ethernet port of a device such as another PC or a Duet, but not when you connect it to a router or Ethernet switch. My guess is that the detection that a crossover is needed isn't always working.

Search Amazon or eBay for "Ethernet crossover adapter" or "Ethernet crossover cable".

@kb58 said in Theory: bed magnets bias inductive probes:

Just to add a conclusion. Swapped in a BLTouch, and all bed related issues vanished. It was indeed the bed magnets messing with the inductive sensor. FWIW, I have a spring steel sheet on top of the build bed, and thought it would shield the bed sensor for any variations in the perceived surface, but guess not!

There are magnetic systems that use a flexible magnetic material which does not seem to interfere with inductive sensors but the ones I have seen have a temp limit.

Frederick

@kb58 said in Learn me M563:

@jay_s_uk My confusion is that the above command seems to associate the extruder to the parts cooling fan, or am I misunderstanding?

It does associate the tool (extruder) with the parts cooling fan. Typically the fan is mounted to the tool in some fashion so when the tool is printing the fan can be used to cool the part being printed.

The hotend fan is mounted to the hotend and is associated with the hotend temp sensor. So when the hotend temp sensor reaches the temp set in the fan config the fan turns on.

Frederick