@Jered It should be written straight to the terminal, not sure why it didn't output anything for you.

@Jords27 to build RRF 3.5 you now need branch 'main' of project WiFiSocketServer RTOS in your workspace, instead of project DuetWiFiSocketServer.

Update to the newest Firmware of Duet2 and PanelDue works flawless today, additional I flashed V2.10d onto the Wifi Module, because I also have problems before.

The config.g need a couple of tweaking.
But so far it is looking good.

Thanks a lot,
Regards Kubunter

I have performed other tests and the result is still the same. Until a few firmware versions ago, I think before 3.2 but I don't remember well, when input shaping was an external plugin, the error "The selected motion profile contains overflows" never appeared. Then with an update it started to appear.

I rewired and not much has changed (i.e... now at least it works, albeit with data overflow).

Question: does the presence of this error, in any way affect the proper functioning of input shaping?

Thanks

@chrishamm Both power supplies have their neutrals connected and the machine is earthed.
I put a Multimeter on the 24v supply for the Mini5plus. When I turned the heats on the voltage dropped to 23.7v but the machine didn't fault, as soon as i removed the meter it faulted.
I will get a new PSU tomorrow and see if it makes a difference.
It could be a coincidence the printer was running fine on the old firmware before updating to 3.5.0

This is how the 6HC and The SBC are connected
449317926_1663863644462850_1799249480196842481_n.jpg

@DavidSummerlin Try to run M997 from the G-code input and check if that fixes it

@Phaedrux said in Can't connect Duet 3 6HC v1.0 after updating to RRF 3.5.2:

Can you try chrome?

I could, but I don't want to risk another brick + reflash, sorry... 😅

If I'll remember I'll do it in the next update.

@Proschi78

Tried the above and the movement behaviour became consistently erratic. Not sure as to why. Reverted back to the below and seems to be have "settled" to a somewhat normal behaviour. Potentially might reset the mbh6c and expansion board back to square one. Potentially the firmware updates may have left some things stuck which shouldnt be the case but never know as all the boards were still on 3.2 beta firmware when started up this time round.

M561 G91 ; relative positioning G1 H2 Z5 F6000 ; lift Z relative to current position G1 H1 X-450 F5000 ; move quickly to X Y and U axis endstops and stop there (first pass) G1 H1 U0 F5000 G1 H1 Y-450 F5000 G1 H2 X5 F6000 ; go back a few mm G1 H2 U-5 F6000 G1 H2 Y5 F6000 G1 H1 X-450 F360 ; move slowly to X Y and U axis endstops once more (second pass) G1 H1 U0 F360 G1 H1 Y-450 F360 G1 F6000 X243 Y200 G30 G90 ; absolute positioning G29 S1 ; this loads the contents of /sys/heightmap.csv

@Phaedrux i got it, thank you for all the help

@kellyaltom If you're on firmware 3.4.6 and can access DWC, you can just re-upload the 3.4.6 zip. It will create the firmware folder and put the files in the correct place. You can then delete all the firmware binaries out of the system folder.

Alternatively, you can use the M997 P parameter and tell RRF where the binary file you want to install is, eg:

M997 S1 P"0:/sys/DuetWiFiServer.bin"

Ian

@chrishamm Chris you are a fricken legend!

@droftarts sure, here is the result

/23/2024, 9:34:32 AM Error: in file testmacro.g line 8: in file macro line 0: unknown variable 'x6'
5/23/2024, 9:34:32 AM Error: in file testmacro.g line 7: in file macro line 0: Expression nesting too deep
5/23/2024, 9:34:32 AM Error: in file testmacro.g line 6: in file macro line 0: Expression nesting too deep
5/23/2024, 9:34:31 AM Error: in file testmacro.g line 5: in file macro line 0: Expression nesting too deep
5/23/2024, 9:34:31 AM Error: in file testmacro.g line 4: in file macro line 0: Expression nesting too deep
5/23/2024, 9:34:31 AM Error: in file testmacro.g line 3: in file macro line 0: Expression nesting too deep

@Adamrobot Please post your config.g again. You have M501 in config.g, so please post your config-override.g too. It may be incorrect setting are being used, ie not the ones that the tuning suggests. Send M301 H1 to see the parameters that are in use.

When tuning, can you do a screen grab of the temperatures? Usually you get the "Warning: heater behaviour was not consistent during tuning" message when the hot end is holding on to the heat, so each heating cycle gets shorter and shorter. It may be that your hot end cooling fan isn't sufficient to cool the cold side of the hot end down.

Ian

@droftarts I was able to flash the firmware using Bossa on a windows partition of my macbook. Everything now works as it should. Thank you all of your help.

Sam

@droftarts thank you

@bartekp Not reliably. You can try SAM-BA, which is documented in the second tab after Bossa, here https://docs.duet3d.com/User_manual/RepRapFirmware/Updating_firmware#all-other-duet-boards

Does the Duet show up in the USB devices? If not, more likely that you're using a USB cable that is for power only, ie no data lines. Try a different USB cable, and/or different USB port.

Bossa also won't recognise the Duet if the firmware has not been erased. Or it's possible that the USB connector has failed. Do any LEDs light up on the board? If so, go through the list here: https://docs.duet3d.com/User_manual/Troubleshooting/Duet_wont_respond

Ian

@jhalewood It works just fine but note that the RPi imager also adjusts cmdline.txt AFAIK. I guess you need to do the same as well.

@jay_s_uk said in DuetPi Bookworm builds featuring v3.5.1 stable now available:

@achrn or use M997... Note the lack of S2

Yes, I had cause to roll back to 3.4.2, so then came back back to 3.5.1 and M997 (no S2) (followed by M997 B121 for the toolboard and M999) worked fine. Thanks.