@phaedrux Thanx, will do. Currently traveling in Delhi /India, will do so over this coming weekend when I will have free time.

Thank you for support, guys, appreciated.

Cheers,
Beano

@arnold_r_clark said in Weird behaviour homing Y-axis (only):

When you home with a Z probe the X and Y homing code has commands to raise/lower Z to be sure the nozzle is clear of the bed.

im sorry but that statement is not 100% correct which you tried to cover by stating "but varies with the specific end-stop sensor and z probe type" so in effect your initial statement should be preceded with "in my opinion"

That part about moving Z up/down during homing X and Y does not depend on the type of hardware. It's about being sure nothing is touching the bed during the XY moves.

And the statement about "varying" was part of the sentence dealing with speed and it is not an opinion.

And to throw another spanner into the mix what about a z probe that uses an optical end-stop on its trigger ?

The only device I know like that is servo based and you have to deploy/retract some part of it, which takes time. A Z endstop if fixed in place.

Frederick

Without knowing what sort of voltage spike to expect I'd say the safest thing to do is power those servos from a supply that is separate from the one that powers the controller board. You might not need to protect the power supply if you use an old-school, unregulated linear supply with plenty of capacitance.

The servo driver you use with the 1XD board might have some protection built in- I'd check the documentation. I used the cheapest servos available and their integrated drivers seem to be able to withstand the spikes (maybe they just used high voltage rated components), but the spikes definitely get outside the motor, requiring some protection circuit.

The REDump circuit might not be able to handle voltage spikes coming from a 48V motor as is. I'd probably use higher voltage rated Darlington transistor, diode, and capacitor. You might want to check the diode current rating against the motor peak current rating, too.

@andywm 👍

@tinchus True, from what you cite, the usage of M703 looks to be optional. At the bottom of the page, however, the DWC manual states that

the filament mechanism utilizes three GCodes:
M701 to load a filament
M702 to unload a filament
M703 to load a custom filament config.g

Reading this, I expected to see exactly the commands @OwenD kindly grabbed from the console (that is: M907 included in "load" and "change"). That’s why I interpret the sentence you cite as a hint that M703 could also be used stand-alone. I think @engikeneer has addressed this ambiguity by calling for proper action.

@cvmichael to set up a static wifi IP address, you need to include the IP and gateway addresses in the M587 command that you use to program the SSID and password into the wifi module. This is so that every SSID you program in can have a different IP address or use DHCP.

@megamannen said in Filements in RepRapFirmware, fw or doc issue?:

(now I get unsure if it's the web-gui that does a M701 + M703 on filament change or if it's the M701 that does this undocumented behaviour)

DWC issues all the commands necessary to complete the task at once.
My comments in this thread also apply here

@deckingman said in Both hot end heaters go "offline" concurrently during a print:

I'll wait until one of the Duet guys chips in.

We had seen it and were waiting for DC42 to take a look, and I see you've now been in touch.

@phaedrux What input are you interested in? I have from 0 to 11, and under name of each one of them none says "extruder"

@tinchus said in Heated chamber PID and 3.4 stable:

@phaedrux Im not good on this github stuff, How can I upgrade to 3.4.1 RC1? I usually do the update using th sudo apt commands

@tinchus said in Heated chamber PID and 3.4 stable:

The board is a duet3 running in SBC mode, 3.4 version

In your case running a SBC you would need to use these directions to switch to the unstable package feed on the Pi.

https://docs.duet3d.com/User_manual/Machine_configuration/DSF_RPi#switch-to-unstable-packages

@deckingman I've responded privately.

Could the difference be whether or not a tool is selected before the print job is started or not?

The first T0 command comes after the M221 in the gcode file. Perhaps the cases where it's not sticking are the times where the tool is deselected when the job starts.

@highfreq said in Is Ethercat supported?:

@alankilian Are you sure Duet doesn't provide step and direction? I read a bit around and it looks like it is supported trough an external board.

I do not believe that the Duet ecosystem has a way to control the system through a step and direction INPUT (commanded position).

it does have a way to generate step and direction OUTPUT signals to an external motor-control driver board.

I thought you were asking about commanding a Duet board through EtherCat (and others) so I assumed you meant you wanted to also control the Duet board by sending step and direction commands to the board.

I'm sorry for my misunderstanding.

Maybe if you could ask your question in a little more precise way you'll get a different answer.

My assumptions could be completely wrong!

@jschall See the last line of the document post above:

A ringing test print works well and you can change the shaper being used every several layers on the fly by sending a new M593. A good test print STL can be found here,

So basically you can use the above test print to try different shapers and different frequencies. The klipper documentation provides some interesting information on how to estimate the ringing frequency etc. https://www.klipper3d.org/Resonance_Compensation.html

It would be interesting to see how you get on. There seem to have been a number of reports of how input shaping and pressure advance interact. Perhaps you could post samples of how things looked with just pressure advance (or even with both turned off)?

They are clever, by default, the process leaves in thingiverse a link to your Printables account. 😉

I never had a Prusa printer but it seems that they put emphasis on quality and ease of use, be it printers, slicer, web service or filament. I also see it in my professional life, when somebody asks for a printer that 'just works', the overwhelming recommendation is Prusa Mk3.

BTW, I was surprised to see that they encourage also of pre-sliced models, I would expect that even for a Prusa MK3, you would like to have your own profile but I guess they try to cover also real consumers.

"The Author has not uploaded any pre-sliced print files. You can try searching in the User print files section or generate and upload your own."

Do your servos accept a step/dir signal?

https://docs.duet3d.com/en/User_manual/Connecting_hardware/Motors_connecting_external

I'm not exactly sure what you're trying to do.

In short, there is no real way to have multiple endstops for a single axis. Once the axis is homed to one end, the length of the axis is enforced. Endstops are not active during a job either, only during a homing move. So you don't really gain anything anyway. It is possible to configure the endstops to act as an emergency stop in case the axis skips steps and loses position and a crash on the frame would be damaging.

Regardless, it's far easier to configure things in RRF3 than in RRF2, so probably a good time to upgrade as well.

Hi, @oliof ,

That corner is more shiny than the others. It might be a problem there...

However, now, after soldering the capacitors, I see that in the Z corner, the C101 capacitor(I think) is missing.

I need to find the resistor and solder again.

20220501_213634.jpg

Unplugging and replugging the ethernet cable brought it back.

@RomeoFox @timschneider I confirm that this is a bug in RRF 3.4. I will fix it in RRF 3.4.1.

Temporary workaround: for Duet 3 multiply the nonlinear extrusion A coefficient by 750000 and the B coefficient by (750000)^2. For Duet 2 use 937500 in place of 750000.

Thanks @timschneider for identifying the change that introduced the bug.