@jay_s_uk I don't know exactly why, but the problem seems to be solved for now. I have updated the firmware again and replaced all files. I looked through the config.g and config.json again, but could not find any error.
I will write directly as soon as the problem appears again.
Already many thanks for the help so far 
@jay_s_uk I don't know exactly why, but the problem seems to be solved for now. I have updated the firmware again and replaced all files. I looked through the config.g and config.json again, but could not find any error.
I will write directly as soon as the problem appears again.
Already many thanks for the help so far
I have restarted and unplugged the printer several times.
@jay_s_uk
By reset, do you mean, for example, a restart (power off and then on again), or is there a function to reset the printer properly again?
No matter which file I slice from which slicer program with which engine, always the same problem.
The error must be somewhere in the software on the board.
I tested yesterday and turned off the printer in the evening, today nothing has changed in the problem...
GCode_Files_End_Code.txt
No problem, here are the files. Some of the files still look a bit messed up. I'm still setting up and will clean up the files later when everything is working. I am a beginner in the RRF environment.
In the file "GCode_Files_Start_Code.txt" I have summarized the first lines of two tested files. I used two different programs for slicing with the Cura engine.
I do not use actual an start.g file.
config.g homez.g homeall.g homex.g homey.g GCode_Files_Start_Code.txt
Hello all,
I use the MB 6HC in conjunction with a 1LC Toolboard V1.2 and RRF.
RepRapFirmware for Duet 3 MB6HC version 3.4.3 (2022-10-05 09:06:36) running on Duet 3 MB6HC v1.01 (standalone mode)
By the way, this is my first message in this forum... I hope I have placed my message in the right place.
The printer has never been in use before, I rebuilt it and just finished.
The very first short test print looked good, everything worked. But one hour later I have the problem that when I want to print a simple GCode file the x and y axis get "weak" (can move the motors by hand, still they get power). Z axis is strong as ever and runs great. I have not changed anything in the config that could cause this effect.
Mechanically everything is fine.
It is also interesting that when I manually move the printer via the web interface, everything works fine (unrestricted, no matter how long I move). The x and y motors then have full power.
x and y only become weak when I want to print a gcode file. The same gcode file on another printer makes no problems and no matter which slicer I use... always the same result.
In the config file everything is defined, in the manual operation via the web interface everything is great, only not with GCodes...
I checked the config file, the gcode, the mechanical components and coudnt find something...
I am terribly frustrated and can't find the error.
Does anyone have any ideas?
Thanks a lot