@dc42
@droftarts

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.

@Aurimas does the tool also have 4 temperature sensors? What commands in config.g are you using to configure it?

@thooms

It's important to differentiate between G32 - bed leveling (auto or manual) and G29 (mesh compensation - mesh creation - mesh loading)

Both require setting the Z=0 Datum using G30.

G32 (bed leveling) should be followed by G30.

G29 (mesh creation or loading) should be preceded by G30.

On a machine that allows auto bed leveling you will likely use G32 (bed leveling) followed by G30 (setting the Z=0 Datum) then G29 S1 (mesh loading).

In that case the G30 proceeding the G29 satisfies the need to follow G32 by G30.

The reason for G30 after G32 is that the leveling process can change the Z position of Z=0 - doing the G30 resets the Z=0 Datum correctly.

Hope that clarifies rather than confuses.

Frederick

@DoodleCube said in Need help with 5 Bar SCARA configuration:

it seems RRF3 on Duet 2 stopped supporting 5 bar

there are flags in RRF to turn on or off those "exotic" kinematics, so if you're able to compile it yourself, you can turn it on for Duet 2.

Pins.h
'# define SUPPORT_FIVEBARSCARA 0
Set this to 1.

@elmoret
Germany dont remember the retailer it was 2021 or something like that

@droftarts
Solved, firefox had some issues with the site.

@dc42 Thank you, and everyone. I'll put that on the To-Do after this print (took the lazy route and stuck it on an external SD via PanelDue for now).

Will mark as solved.

Ok, it was as simple as using raspi-config to boot to terminal (CLI) instead of desktop (GUI). I'm new to RPi so this was probably obvious to all.

BTW, fun fact, the desktop uses about 600 KB RAM at 1280x900. That leaves me with about 960 KB free which I hope is sufficient.

Bonus side effect was switching to CLI and back seems to have resolved my system instability. So I am happy.

@droftarts Thank you for your help. Unfortunately, I am still receiving the same error even with the older 1.27 Wifi firmware. Here are some pictures of my board.

I assume the board must be somehow damaged? But it seems strange that the firmware upload for Wifi module completes successfully.

Petr

20250212_142609.jpg 20250212_142602.jpg

@rschlachter There's a WiFi troubleshooting page in the wiki that includes more advice: https://docs.duet3d.com/en/User_manual/Troubleshooting/WiFi_troubleshooting

Ian

@jay_s_uk

LMAO!

That's a fun ending to this story!
Thanks!

Solved...typical, just after I wrote this I thought to reinstall Bossa, and also change USB ports, it now works!

@3DOeste I was not sure ,from the other thread, if this is also fixed for you?

@rschlachter said in Resurrecting a printer from 4+ years ago:

Given the new bed size and taller z axis, I know I can't just plug it in and start printing. So should I start completely fresh? Or try to see where I'm at and modify/upgrade?

I'd probably just start again, first by updating the firmware to the latest, as there have been a lot of developments in the last 4 years. Start as if starting again for the first time: https://docs.duet3d.com/en/How_to_guides/Getting_connected/Getting_connected_to_your_Duet
Create a new configuration set of files using the configuration tool:

Is RRF still the way to go? Or is Klipper the new standard? I'm not afraid to switch if it makes sense.

You're on the Duet/RRF forum, so people are likely to have strong opinions about that! Switching to Klipper will require a Raspberry Pi or similar. Duet boards can run Klipper, but we (Duet3D) don't provide support. Performance- and feature-wise there's little to choose between them.

I should be able to grab some of the files and settings from the card, right? I did everything through the web interface previously. No PanelDue.

You can use your old config, assuming you're on RRF 2.x, to inform your new config. But I'd generate a new config set, rather than try and bash the old one into shape.

Anything else I should know before I jump back in?

We're here for you!

Ian

@pr02type said in (After FW update) Failed to initialize WiFi module: SPI Timeout:

=== WiFi ===
Interface state: disabled
Module is disabled
Failed messages: pending 0, notrdy 0, noresp 4
Socket states: 0 0 0 0 0 0 0 0
ok

Hmm, that doesn't tell us much. What happens if you send M552 S0? Then send M122 to check the WiFi state.

Ian

@matteoprati said in Impossible to update Firmware:

Couple of weeks ago, the printer stopped working

What initially went wrong? Generally, updating the firmware is not the first thing to do, as it can cause it's own issues.

Generally, if BOSSA can't detect a board, it's usually because the firmware hasn't been erased. Are you sure you are putting the jumper on the 'erase' pin on the Duet? What does the Duet show as in Windows Device Manager?

When BOSSA is used to flash the SAME70 processor in the MB6HC, the processor uses the USB port in high speed mode (unlike the processors used in other Duets). This means that the length and quality of the USB cable is especially important. USB cables that can be used to send GCode commands and receive replies to/from a Duet MB6HC that is running RepRapFirmware may not be suitable for flashing the firmware using BOSSA. Try a different USB cable.

Also disconnect any attached PanelDue (which can cause interference), and don't turn on the PSU, only power the 6HC from the USB cable (to avoid ground loops). What version is your 6HC? Does it have a USB-C port, or an older mini USB port?

SAM-BA doesn't work with the 6HC. I've only ever got it working with the Duet 2. I nearly bricked a 6HC the last time I tried using it, so please don't use it!

Ian

@thaug29 Are the lines after the 'if' statement correctly indented? If you can post the macro within code tags (</> icon on the message formatting bar) it should show indentation. This macro is also calling a lot of sub-macros, so without posting all of them, it's hard to say where it's causing problems.

Ian

@darylprice sending M997 from DWC should be sufficient to update the 6HC to the same firmware version as DSF. I think DSF will only auto update minor versions (ie 3.5.3 to 3.5.4) but not major versions (ie 3.4 to 3.5), but M997 should fix that. See https://docs.duet3d.com/User_manual/Reference/Gcodes#m997-perform-in-application-firmware-update

Ian

@MichaelKallner the change logs detail what changes have been made between 3.4 and 3.5. That is quite a big jump so there will be a fair few changes however most won't apply to your specific machine config.
https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.x

how do i mark this as solved?