Best posts made by oldschoolPiratename

undefined

Hello guys,

I tried it and got a reply.
So that worked.

After being sure that it is only Eth issue, I added a small switch in between, I remember that once I did a similar work-around at a LAN connection at my friend's house during a LAN party (yes, I am that old).

AND I got a reply from printer! DWC smiled at me.

I works like a charm now.
Interface is there, firmware updated and I am happy as I can be.

I would like to thank you both for your help and assistance.

Kind Regards,

P.S. If any of you two passes through Linz, let me know. I owe you a beer or few.

undefined

Hello All,

Long time follower here

Have old Kossel Mini 3 with Duet 0.85 firmware on board.

I wanted to update to
releases - 2.05.1 (not allowed to post links, but it is from Git Firmware Repository
today, but I guess I bricked my Duet 0.85.

Before bricking it, I was running

Firmware Name: RepRapFirmware for Duet
Firmware Electronics: Duet 0.85
Firmware Version: (cant remember version but I remember the date) (2019-11-09b1)
Web Interface Version: 1.21 ( something around here)

Could someone kindly point me to a procedure to update or reflash these old board?

Update I can connect to microcontroller onboard using Sam-ba 2.17.
I tried updating Duet2CombinedFirmware.bin as stated in Duet3d Documentation, but it didnt do the trick.

On board I still have all three LEDs permanently active (Blue, Red Yellow)
I tried copying DWC to SD card /www folder but without success.
In /sys/config file I reviewed ethernet settings. They are set correct. My thinking is programming process is unsuccessful and thus I have no access to the board over ethernet...

Again, any help is greatly appreciated.

Kind Regards,
OldschoolPirate