Firmware bundle 3.3.0 released

Touchthebitum

Hello
I'm trying to enable Plugin on the new 3.3.0 firmware.
sudo apt install apparmor worked
echo " lsm=apparmor" >> /boot/cmdline.txt give me an error message : -bash: /boot/cmdline.txt: permission denied

I can still activate plugin in DSW

Help please

tom33

@chrishamm I have the same problem since I upgrade with motor movement and 1XD (like in this post : https://forum.duet3d.com/topic/17780/clearpath-servos-with-1xd-expansion/76?_=1624015273855&fbclid=IwAR2bZCkl7tMWbKrGAJ7wN7WYqi2j4V8Fe9-WJHyBQuSh0yivL_SVDwbOHzs)

I make a gcode with just X movement and sometimes the motor change the direction...

dc42

@tom33 do you have a G4 S5 command early in your config.g file, earlier than the M569 command that refers to that 1XD board?

jay_s_uk

@touchthebitum the correct command is

sudo bash -c 'echo " lsm=apparmor" >> /boot/cmdline.txt'

Touchthebitum

@jay_s_uk thanks

tom33

@dc42 No I, don't have a G4 S5 in my config.g. I need to add this ?

dc42

@tom33 said in Firmware bundle 3.3.0 released:

@dc42 No I, don't have a G4 S5 in my config.g. I need to add this ?

Yes, that's often needed since RRF 3.2 to make sure that the tool boards and expansion boards have time to start up when power is applied, before the main board starts to configure them. Without it, the first command sent to a tool or expansion board (which is typically a M569 command to set the motor direction) may get ignored.

tom33

@dc42 I try this but still the same problem

chrishamm

@tom33 You need to put G4 S5 pretty much at the top of config.g. Is that the case? Also, have you updated the firmware of the 1XD to v3.3 as well?

tom33

@chrishamm I try this without success, the strange things is with the 3.2.2 it's ok, I also try with 3.3RC3+6 but no with the new one...

Some things looks weird with the pulse or DIR generator with 1XD

And the main board and expansion board have the the firmware

dc42

@tom33 you may need to adjust the step timings in the M569 command. Prior to 3.3, on the 1XD the timings you entered were all rounded up to the next multiple of 1.33us. In 3.3 the step pulse generation is faster and the pulse width entered in M569 is rounded up to the next multiple of 83ns. Additionally, the step to direction hold time is timed from the leading edge of the step pulse, so although the hold time from the trailing edge that you specify in M569 will always be honoured, the way that it is rounded up is different.

I will add a note about this to the upgrade notes for 3.3.

tom33

@dc42 I'll try this and keep you inform about the result.

I'm using leadshine CS-D508 Do you recommand any T parameters for this driver ? CS-D508_Manuel.pdf

dc42

@tom33 said in Firmware bundle 3.3.0 released:

@dc42 I'll try this and keep you inform about the result.

I'm using leadshine CS-D508 Do you recommand any T parameters for this driver ? CS-D508_Manuel.pdf

In theory, T2.5:2.5:5:0 should be sufficient to. But also try a little higher e.g. T3:3:6:1.

Tinchus

@chrishamm Whre can I find information about the use of accelerometers now in duet?

droftarts

@tinchus https://duet3d.dozuki.com/Wiki/Accelerometers

Ian

tom33

@dc42 I have just tried this values but same problem... there is no change between 3.3 RC+6 and 3.3.0 ?

dc42

@tom33 said in Firmware bundle 3.3.0 released:

@chrishamm I have the same problem since I upgrade with motor movement and 1XD (like in this post : https://forum.duet3d.com/topic/17780/clearpath-servos-with-1xd-expansion/76?_=1624015273855&fbclid=IwAR2bZCkl7tMWbKrGAJ7wN7WYqi2j4V8Fe9-WJHyBQuSh0yivL_SVDwbOHzs)

I make a gcode with just X movement and sometimes the motor change the direction...

Please start a new thread about this. In that thread post your config.g file and the results of running M122 and M122 B# (where # is the CAN address of the 1XD board) after you have provoked some incorrect movements.

BeosDoc

Apt update and apt upgrade upgraded the Duet 3 6HC main board firmware. It didn't upgrade DWC or the toolboards.

Phaedrux

@beosdoc said in Firmware bundle 3.3.0 released:

Apt update and apt upgrade upgraded the Duet 3 6HC main board firmware. It didn't upgrade DWC or the toolboards.

What version were you on previously?

You can manually initiate the firmware flash by sending M997 B# where # is the can address of the tool board.

For DWC, I'm not sure the best way to update it if it has failed. Can you provide us the results of M122? Are you sure DSF updated at all?

chrishamm

@BeosDoc @phaedrux I doubt the DWC update actually failed. It's much more likely that your browser keeps a cached copy so try pressing Ctrl+Shift+R to force-reload the web interface. Then it should display v3.3.0.

We'll improve the way firmware updates are installed in v3.4 so that firmware updates for expansion board are installed as well.