@chrishamm I reinstalled everything again for the production board (not the testboard). Now the network seems to be working again properly, don't ask me why. However I stil have the same error as before when using the command for the motor with name "g" / 'g . It gives the errors at startup: Warning: G500.0: Command is not supported and Warning: G6000.0: Command is not supported, etc. So basically every time the motor mapping 'g is used it looks like it it not processing the commands.

@T3P3Tony Now using the command M584 on version 3.5.0 rc3+ I get the following output.
M584
Driver assignments: X12.1 Y12.2 Z12.3 a0.1 b0.0 c0.2 d0.3 e0.5 f0.4 (r)(c)A11.0 (r)(c)B11.1 (r)(c)C11.2 (r)(c)D11.3 U11.4 V11.5 W12.0, 21 axes visible.

I should get 22 axes visible. So I suppose this means the 'g axes is not configured?
@T3P3Tony You mentioned 30 axes in v3.5.0. At the moment I use ABCDUVWXYZabcdefghijkl for the mapping. Which letters are still available?

@chrishamm I managed to replicate the same error on a single test board I still have. It looks like I can install the version 3.5.0 rc3 but not the rc3+ versions @T3P3Tony provided earlier. So I get to the point where the version 3.5.0 rc3 is fully installed, however afterwards during the startup of the DSF/DWC in the webpage there comes a moment where the connection is lost.

Step 1. Start with a fresh Duet3 image 3.4.6 on the SBC
Step 2. Upgrade using the the commands on https://docs.duet3d.com/User_manual/Machine_configuration/DSF_Other for the unstable installation (version 3.5.0).
Step 3. The installation is completed and version 3.5.0 rc3 is installed.
Step 4. Initially I get a connection to the board however after +-1 minute the connection fails and cannot be restored. It gives the error message: "Connection lost, attempting to reconnect". Whenever the connection is lost, it is never restored.

@chrishamm I manage to resolve the network connection issue, by totally emptying my config.g and return only the bare minimum commands.

@T3P3Tony I am performing the updates, however after updating I cannot connect anymore via the webpage to the mainboard. The mainboard has an SBC connected, so no SD cart. I still can login to the SBC via ssh. The other 6HC who are used as extension boards seem to work fine. Some 1XD extension boards I also could not update.

I am not sure if I caused the network connection problem myself because after updating there was an error that my machine name was invalid due to the use of _ in the name. So that is the only thing I have changed.

For the why question. I am using multiple 6HC boards (connected to mainboard via CANbus) and need to map all motors to a separate axis, because they are all different motors. I did see the useage of lowercase in the description in the configuration manual(https://docs.duet3d.com/User_manual/Connecting_hardware/Motors_configuring). So therefore I already followed that example and used lowercase letters for the mapping.

@T3P3Tony The reply from command M584:
Driver assignments: X12.1 Y12.2 Z12.3 a0.1 b0.0 c0.2 d0.3 e0.5 f0.4 (r)(c)A11.0 (r)(c)B11.1 (r)(c)C11.2 (r)(c)D11.3 U11.4 V11.5, 15 axes visible

@T3P3Tony Thank you for mentioning the case senitivity, but I already took this into account and did use lowercase in all of my config file.

@oliof No, that does not make a difference.

Hello everyone,

I hope this is the right place to ask a question about the firmware and a warning I get when setting the config.g file.

I am setting up a configuration on on the mainbord 6HC using Duet3 MB6HC DSF version 3.4.6 and reprapfirmware 3.4.6.
In the config file I am setting all of my axis and mapping according to the manual(https://docs.duet3d.com/User_manual/Connecting_hardware/Motors_configuring). However could it be possible that there is a bug in the code, whenever I use the small letter g as a motor axis mapping in config.g using command M584 g5 and accordingly set the steps per mm and micro-stepping using commands M92 g16 and M350 g80.00 for example I get the following warning in the console. Warning: G80.0: Command is not supported and Warning: G16: Command is not supported. I do not understand why I get a warning as I am only setting the config file and not using any real g code here. Could this be a bug or is this already solved? I would like to know if it is a problem to use this small letter g in my motor mapping.

Thanks for the information. I found them. The explanation that it was at the backside of the board helped a lot.

Hello everyone,

I want to daisy chain multiple mainboards via CANbus. I read the description about connecting multiple Duet3 Mainboards 6HC as extension boards. In the user manual is written that this is possible, however you need to remove the cuttable trace or desolder the termination resistor on the boards v.1.02 and above (https://docs.duet3d.com/User_manual/Machine_configuration/CAN_connection). From the description in the user manual I could not find exactly where this trace should be. Could somebody help me, preferably with a picture or something what resistor I should remove/cut on the mainboard?

@deckingman @Rushmere3D Thanks for the explanations. It is clear to me now how to use it.