@dc42 It worked after updating ICE's firmware. Found out that atmel-ice firmware version was same. And again tried to flash bootloader it got failed with same error. Then again updated the atmel-ice firmware it worked. There is problem with ICE. Thanks

Hey @argo!
Yeah, I remember I tried the table from Prusa's firmware with some stepped logic functions, and did testing to derive my own table, but in the end I found that with temperatures held (verified with a flir), during day to day testing, over a 7 day period, the probe trigger was not very repeatable/accurate as it drifted. Granted, the possibility exists it could have been my specific probe that was at fault but it seemed to me that it just wasn't the best sensor for the job. Once I installed a BLT, I consistently got accurate, and repeatable, findings on a continuing basis - with the added benefit that I could change bed surfaces and not have to do any adjusting.
But, if the pinda is your cup of tea, and I do see benefits of it - I'm not saying they are all horrible, I think it would be best to simplify things and upgrade to a v3.

(as I am not allowed to edit my post 3600sec+ after writing)

EDIT:
After a while it worked.
Didnt tested it for a couple of hours but then it worked.

I will check if it just "needs its time" or if the network settings are now correct.
As I am away for a week it will take a while when I can tell more.

Thanks so far dc42 👍

@sinnedwrong said in Upgrading Firmware from 2.02RC3 to 3.2:

I didn't find in the change log for version 3.2 that BANG-BANG wouldn't work only that there was a new heating algorithm.

Bang-bang can still be used. However, if you don't run heater tuning, then RRF knows nothing about your heater; so its heating rate may be lower than RRF expects, leading to a heater fault being raised.

@visionary said in Duet 3 Paneldue not working:

Diagnostic LED is on too although its very dim.

On a Duet 3, that normally means that the board isn't running any firmware.

@docfail, are you sure that 1.02 isn't the hardware revision detected by the firmware? As in this response to M115:

FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.3beta2+1 ELECTRONICS: Duet WiFi 1.02 or later

The WiFi firmware version is shown in the M122 response (if the WiFi module has been enabled), and in the Machine-Specific tab of Duet Web Control.

@phaedrux said in hotend fan on only when hotend stop heating:

Yes but which fuse blew? Does your board have 2 fuses? One for vin and one for the fans?

If the fan fuse blew and the fans are still running then it wasn't actually the fan fuse? Or the clone is really really bad.

Either way, a photo would be helpful to see.

yes the board has two fans like on your picture. it is the 1a fan fuse. at the moment the board is not installed. here are some pictures! the blew fuse is not installed on the picture20210411_122546.jpg 20210411_122604.jpg 20210412_200545.jpg

@phaedrux Thx a lot.
I will think about that how much i really want those new fancy Features.

Sounds good. Thanks for the info.

If all else fails and you want to manually install a particular version you can use BOSSA and USB to flash a particular firmware version to the Duet. And if you're using a SBC as well, then you can start fresh with a new image of DuetPi and simply update using the stable branch.

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

If you still have access to DWC you can just upload the full zip file for the release you want and that should take care of it.

If you still have access to DWC. Upload these 3 zip files, one at a time in the system tab. Don't extract them. Reboot after each. Use M115 to verify the firmware has been applied.
https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/Duet2Firmware-2.05.1.zip
https://github.com/Duet3D/RepRapFirmware/releases/download/3.0/Duet2and3Firmware-3.0.zip
https://github.com/Duet3D/RepRapFirmware/releases/download/3.2.2/Duet2and3Firmware-3.2.2.zip
That will get your firmware and DWC up to date.

@phaedrux said in Solved: Homing issue with X & Y after upgrading to RRF3:

@willmackey said in Solved: Homing issue with X & Y after upgrading to RRF3:

Old topic but was relevant to me as a new user how tries to find answers with the outdated wiki.

Which part is out dated?

Just noticed some stuff not matching the reality anymore which as a fresh Duet user caused some head scratching and wasted time going through configs. Didn't keep track of them unfortunately but around this endstop topic atleat:

Switch status page (I think it was called endstops) in the Machine-specific menu. Wiki still guides there but it no longer exists (some object model browser update is related to this but OMB isn't there either?). Whole endstop wiki page only describes two settings (NO / NC) and I guess there only used to be only 2 settings based on YT videos but now there's 4 settings for the endstops and I have no idea how 'active low pull-up' differs from 'active low'. Inputs seem to be pulled-up even without the pull-up selection.

But in general it is really nice to see so comprehensive documentation! 👍

@generisi said in Firmware install from scratch:

@Phaedrux , how do I untangle a mix of RRF 3.2.2 and 3.3 ? My goal is 3.3 but the printer is behaving strangely and the web interface and the Paneldue are not working fully correctly?

Depends what you're running. It would be best if you started a new thread with your details.

@dc42 désoler avec la traduction c’est un peu compliqué juste pour vérifier que j’ai bien compris je coupe dans le ruban duex5 et je met une résistance de 27k entre le vssa et la résistance 22k de la thermistance de ma duex5 thats ok like that

Setting bed centre to be X0 Y0 has various advantages; but for IDEX printers it also makes it easier to configure a tool for mirror printing.

@paulhew The command christhamm suggested copies (actually, makes a symbolic link) of the /sys/Duet3_SBCiap32_Mini5plus.bin IAP file in the /firmware folder. RRF 3.3 uses the firmware folder for updates, so that's where the files need to be.

Instead of running this command, if you upload another copy of Duet3_SBCiap32_Mini5plus.bin in DWC, it should put it in the /firmware folder, then you can flash firmware. Because DWC 3.2.2 doesn't show the firmware folder, you can check the file is there by sending: M20 P"/firmware"

If you are on the 'unstable' feed, and you run 'sudo apt-get update & apt-get' from a terminal on the SBC, it will reinstall the beta firmware. To change back to the stable feed, see https://github.com/Duet3D/DuetSoftwareFramework#2-apt-package-feed

Basically, all you should need to do is edit the /etc/apt/sources.list.d/duet3d.list file. Open a terminal on the SBC, either via SSH or locally on the Pi itself and run:
sudo nano /etc/apt/sources.list.d/duet3d.list
Edit the only line, changing 'unstable' to 'stable':

deb https://pkg.duet3d.com/ stable armv7

Exit, save, then run sudo apt-get update & apt-get to get everything back on the stable branch. You may still need to update the firmware on the boards, though.

Ian

@hughbee please contact filafarm for a warranty exchange.

@engikeneer ok thanks yea i get that error when i turn on the printer and am not doing anything i thought that would come on when u actually power up he bed.

and thanks about the zprobe info i made a new config file with the reprap tool and saw the change

Figured it out, I thought my double quotations "" set in keyboard settings were in straight down format but they weren't, didn't even know it was a thing. If it helps anyone else here it is lol.
Connect to the network straight away.

I believe the files should already be present if you've already uploaded the 3.0 zip file once before. But I could be wrong. If so, upload it too.

Well that's great news!