Multiple issues after RRF 3.2.0 to 3.3.0 update

fcwilt

@phil333 said in Multiple issues after RRF 3.2.0 to 3.3.0 update:

I have been using 3.3 for many months on multiple printers generating hundreds of prints and have not found any significant problems

That's great, but it doesn't help me. I also don't know what you are trying to tell me with this information.

Sorry - I wasn't clear.

I would suspect the problem is related to your hardware and/or configuration, rather than the firmware itself. It there was a fundamental flaw in the firmware I think I would have encountered it by now.

Frederick

T3P3Tony

@phil333 said in Multiple issues after RRF 3.2.0 to 3.3.0 update:

As there is no fix yet, should I downgrade to RRF 3.2 anyway to help you tracking this issue?

yes that would confirm the issue which would be helpful.

Phil333

@T3P3Tony _
I uploaded Duet2and3Firmware-3.2.zip and let it install.

DWC is now on 3.2.0 but RRF is still on 3.3:

I will now try to just upload the Duet2CombinedFirmware.bin and see how it goes.

EDIT:
Seems like I cant downgrade this way.
Uploaded and installed the Duet2CombinedFirmware.bin from release 3.2 but I am still on 3.3:

What am I doing wrong?

EDIT 2:
I also tried a downgrade to 3.0
While DWC downgraded sucessfully:

RRF remained on 3.3

T3P3Tony

@phil333 please do the following:

reupload the 3.2 Duet2and3Firmware.zip so DWC is on 3.2 and the binary firmware files are 3.2
send M997 to force a firmware update.

Phil333

@T3P3Tony

I did so and used the Duet2and3Firmware-3.2.zip (no renaming involved).

After decompressing, it asks me if I want to update:

This time I clicked on "NO" and did the M997 on the console.

Then it started updating, but I am still on RRF 3.3

Any ideas?

T3P3Tony

@phil333 probably caused by the change in directory try:

M997 P"0:/sys/Duet2CombinedFirmware.bin"

If that does not work try

M997 P"0:/firmware/Duet2CombinedFirmware.bin"

Phil333

@t3p3tony

M997 P"0:/sys/Duet2CombinedFirmware.bin"
is giving me a beacon:

but it seems to do something:

Yeap!
It did it!

Now the important part:
The BLtouch is working normally with the 2 pin out/in cycle, no delay, everything as before!

This includes:

BLtouch inititialization as normal
The"Calibration and Compensation" -> "Define Area for Mesh Compensation (M557)" on the Dashboard is working correctly.

(Testing the rest right now)

For you @T3P3Tony :
Should I now go to RRF 3.3 again and see if this issue is reproducible?

T3P3Tony

@phil333 I am checking with @dc42 to see if the potential fix has been added yet. In the mean time if you have the time then please do upgrade back to 3.3 and then to 3.4b5 and test at each point.

I have these instructions here from another post which I am posting in there entirety. I am not yet sure if 3.4b5+1 has the potential fix in it though.

First upgrade to 3.3:

download the Duet2and3Firmware-3.3.zip file from https://github.com/Duet3D/RepRapFirmware/releases/tag/3.3
and use "system" -> "upload system files to upload it. it will prompt you to install the updates say yes.
Assuming that all goes as expected DWC should reload and you should see 3.3 versions reported for DWC and RRF in the General and Machine Specific tabs in DWC.
To get around a issues with future upgrades (we switched from /sys/ to /firmware for firmware binaries between 3.2 and 3.3) the best thing is to re- upload the Duet2and3Firmware-3.3.zip again at this point. you don't need to re-install the updates. this just ensures stuff is in the right place for future upgrades.

Second upgrade to 3.4b5

get the Duet2CombinedFirmware.bin and DuetWebControl-SD.zip files from here: https://github.com/Duet3D/RepRapFirmware/releases/tag/3.4.0beta5
Upload the firmware binary first and say yes to install the update. then upload the SWC zip.
check that the firmware and DWC are now reported as being 3.4b5

Finally upgrade to the 3.5b5+1

Get the Duet2CombinedFirmware.bin from the dropbox link (https://www.dropbox.com/sh/xeu30go894p9xbs/AAB5U66SH4wbjKIcX0snUbKxa?dl=0). There is no updated DWC.
uploaded it as in the previous step, say yes to the update
the Machine specific tab/M115 should report 3.4.0beta5+1 (2021-10-29)

Phil333

Hey @T3P3Tony

I took the time, because its important for you to know - and I am happy to help you and give something back

For 3.3
I did update to RRF 3.3 using the Duet2and3Firmware-3.3.zip then reuploaded it (not installing again).
Installation was successfull.
I turned the printer off completely (to ensure all files properly and freshly loaded).
The issue with the BLtouch appeared again.

For 3.4.0 beta 5
I uploaded the Duet2CombinedFirmware.bin and istalled it.
Thereafter I uploaded the DuetWebControl-SD.zip.
Update was successfull:
Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.4.0beta5
FIRMWARE_DATE: 2021-10-12 13:55:00
Duet Web Control 3.4.0-b5

BLtouch issue still exists.

For the 3.5b5+1
I did so and update was successfull:
Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.4.0beta5+1
FIRMWARE_DATE: 2021-10-28 21:18:14

The issue is still existent.

Is there anything more I can do/check for you right now?
If so, please give me further instructions

If not, I will roll back to 3.2.x to have a usable system.
This issue caused already a crash where my printhead got deformed and unleveled my 4 axis print bed, which I will now calibrate and level again (to print something later on).
This happened after starting a print right after booting,when the BLtouch was not yet ready and I was not aware of this problem

T3P3Tony

@phil333 thanks for you help testing this. Best to roll back to 3.2 for now. I will post here when i have an update.

dc42

@phil333, YouTube tells me that your video is private, so I am unable to view it.

dc42

@phil333 in future, please start a separate thread for each separate issue. Threads that contain multiple issues take too long to search for information relevant to one particular issue.

Regarding the issue of the BLTouch not initialising, I am unable to reproduce this. I have tested BLTouch versions 1.0 and 3.1 with RRF 3.3 at both 12V and 24V VIN, and BLTouch version 3.1 with RRF 3.4.0beta5+1 at 12V and 24V. In all cases the BLTouch initialises correctly. The BLTouch was connected to the exp.heater3 output as shown at https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe#Section_Duet_2_WiFi_Ethernet_without_expansion_board.

Assuming this remains a problem for you, please start a new thread and include or attach your config.g file to your post.

Phil333

@dc42

Try again, I corrected it

Here for a faster access:
https://youtu.be/IHGDNubi_jQ

Its a problem that you cant reproduce it.
I am using a Duet 2 Wifi v1.04c powered by 24V (Meanwell) and a quiet recent BLtouch (so v3.0 or 3.1)
All genuine and the issue is on my side 100% reproducible.

Wiring is definetly not the issue here. (tested with the clone directly connected to the Duet - shortest wire possible).
2 different BTtouch clones tested with the same issue.

I am pretty sure its a firmware issue.
Tested the BLtouch on exp.heater3 (connected currently) but also checked (exp.heater4 and exp.heater5.)

As the problems disappears on 3.2.0 and comes back again on 3.3+ I think we can say its not a hardware issue.

I already opened a thread only for this issue:
https://forum.duet3d.com/topic/25573/bltouch-problem-after-upgrade-to-rrf-3-3/5

But as more issues came up, I thought to open one not in the "third party add-on" section but rather to the "firmware" section".

All other problems then the BLtouch are solved.