Best posts made by JayJay

@droftarts said in Poor print quality with RRF3 - especially 3.2.2.:

@deckingman I think the vertical curve is from corners warping up and pulling in. Except for the other issues, I’d usually attribute that to too hot heat bed, too hot extrusion, not enough cooling, over-extrusion, or a combination of those. I doubt it’s a XY positional error.

Ian

It is no wonder the OP is frustrated, people seem hell bent on looking to blame something else instead of facing the reality of the OP's Issue..

The OP is obviously NOT some inexperienced user fitting a Duet board to an Ender-3, so why treat him in that manner, that is condesending and an insult to his obviously considerable intelligence.

The common denominator is the firmware (and possibly the hardware) if previous settings which worked on RRF2/Duet-2 (or an earlier version of RRF3) no longer work on later RRF3/Duet-3 that means that the "newer" firmware (and possibly the hardware) is not the evolution it should be (the terrible initial step pulses on Gen-3 hardware prove that assertion to be correct) And if you are now openly blaming things such as incorrect cooling or incorrect temps and intimating that they now require to be changed to compensate for a firmware update, well that is proof that any firmware "update" has not been an evolution but a retrograde step.

@fcwilt said in Easier to use Software:

@JayJay said in Easier to use Software:

Since the advent of RRF3 and the Duet-3 ecosystem things have IMHOP gone so far south they are being asked for ID McMurdo Station.

I was thinking that since 3.2.2 works fine on the Duet 2 family and the Mini 5 - none of which are using the CAN bus could the problems be related to things unique to the MB6HC/3HC family which rely on the CAN bus or the parts of the firmware the handle the CAN bus.

Frederick

I have (and continue to have) issues if I install RRF3 on my Duet-2 board (but not with RRF2) and have niggly issues on my Duet-3 mini 5+ with RRF3, there is no point in opening new threads on those issues because the fan boys will roll out the stock "post your config.g" etc when its not a config issue. and i just stopped using my 6HC board as its a complete waste of time.

@t3p3tony said in Announcement: Duet 3 Toolboard revision v1.1:

@jmaddrell I know we are shipping them out as fast as we get them!

That doesn't actually answer the question though.

From going down the list the the majority of EU/UK suppliers are not listing the updated version, it appears the only filastruder are "on the ball" enough to be showing updated information, which is a pretty poor service from EU/UK suppliers.

I have even had it from a UK Supplier advertising the v1.0 boards but supplying v0.6 boards, so I am loathe to purchase in-case they just want to offload older stock, and not being able to purchase the newest item unless you contact the supplier and specifically request the v1.1 is tiresome.

@CaLviNx said in Tool board LC1 errors:

so you need to fix either one or the other to match how you have it wired

@CaLviNx

Thank you so very much, an excellent spot, the M569 commands are correct .

I have edited M584 to match and that got rid of the driver0 error and everything is now homing. thank you again.

please accept my apologies in advance as I will no doubt be back with more rookie questions.

@dc42
@Phaedrux
@Veti

Well I finally fixed it....

My homeall.g had G30 S-3 in the script.

I removed that and changed it to single G30 command on its own and now it completes the G32 action with no errors, I dont know why it works fine on my Duet-2 with the S-3 switch in my homeall but the mini 5 doesnt like it