Version 3.4-b7 released

chrishamm · 17 Dec 2021, 12:03

I'm happy to announce the release of v3.4-beta7 on behalf of the Duet3D team. Notable changes in this version are:

Support for non-Newtonian cooling
New bottom navigation bar for mobile devices and smaller menu items in DWC in desktop mode
Support for easy webcam setup using a new DSF plugin (see here and here)
Improved DWC plugin documentation and new npm script to simplify plugin builds

Please read the full upgrade notes first for

Duets in standalone mode can be updated by uploading the release files on the System Files page. Users of SBC mode must be on the unstable package feed before the software can be updated using sudo apt update && sudo apt upgrade method.

OwenD · 17 Dec 2021, 12:29

@chrishamm
Is heater_fault.g called at all times, or only during printing?

The handling of heater faults has changed. When a heater fault occurs, an event is created. To handle the event, RRF runs macro file heater_fault.g without pausing the print first

chrishamm · 17 Dec 2021, 12:31

@owend ~~I think it's always called when a fault occurs.~~ If that file does not exist, RRF pauses the print instead and shows a message. See https://duet3d.dozuki.com/Wiki/Events for further information.

jay_s_uk · 17 Dec 2021, 12:36

@chrishamm i got this error when updating my SBC

 Error:
  An assembly specified in the application dependencies manifest (PluginManager.deps.json) was not found:
    package: 'runtimepack.Microsoft.NETCore.App.Runtime.linux-arm', version: '6.0.0'
    path: 'System.Net.Quic.dll'

Anything to worry about?

chrishamm · 17 Dec 2021, 12:52

@jay_s_uk I just downgraded to 3.4-b6, upgraded to 3.4-b7 again, and I did not see that message. Are you using the 32-bit or the 64-bit build?

jay_s_uk · 17 Dec 2021, 12:57

@chrishamm i have no idea. probably 32 bit from the age of the image.

dc42 · 17 Dec 2021, 13:02

@owend said in Version 3.4-b7 released:

Is heater_fault.g called at all times, or only during printing?

Only during printing from SD card or an attached Pi.

CNCModeller · 17 Dec 2021, 18:05

Hi All,
Just trying out the updated firmware. The v0.2 alpha closed loop plugin doesn't allow me to select current step and step phase parameters for graphing. The check boxes are greyed out as if I hadn't selected to record the data.

I noted;

"When collecting data from EXP1HCL closed loop driver boards, some fields in the .csv file have been renamed to match changes to the plugin."

Note: I did use the 0.3 1HCL driver to update my pre-production board.

Is there a new version of the plugin available? The latest is 0.2 alpha in the git repo from August.

Many thanks
Barry M

oliof · 17 Dec 2021, 20:08

Before I consider 3.4b7 and following, I would like clarification on the heater fault changes:

Note that the event system is still under development, Currently, RRF does not attempt to turn off power to the whole machine if the user does not respond to the heater fault. We plan to reinstate this or a similar function in release 3.4.0RC1.

What would I need to put into heater-fault.g to recreate the exact behavior that was built-in in 3.3-3.4b6? Any special considerations I need to take on an IDEX printer?

OwenD · 17 Dec 2021, 20:27

With regard to driver_error....

Do all parameters equally apply to Duet 2 (apart from CAN address)?
The notes say if the macro isn't found the print is paused without running pause.g. Presumably because pause.g would normally have movements which may not be possible. What state are the heaters left in?

Just weighing up the pros and cons of having a driver_error.g macro in place.

MintyTrebor · 18 Dec 2021, 08:40

@chrishamm Small UI bug with the left navigation menu @ 1024x768 (iPad), & 1024x1366 (iPad Pro) resolutions.

When running below 1024x768 resolution the left menu contains the connect and emergency stop buttons, and the new bottom menu is shown for the remaining menu items.
When running @ 1024x768 or 1024x1366 the left menu is empty and the the connect buttons & emergency stop buttons move to their original top bar position. The new bottom menu is still displayed with the full menu items.

Update : Also at these resolutions the status panel is shown by default and available as a menu item so you end up with 2 status sections. I think the framework resolution display breakpoints have been mixed up.

I don't think the empty/blank left menu is by design.

I found this whilst updating BtnCmd to work with new mobile menu designs in 3.4b7, which leads me to another question...

I chose to define anything below 1024x768 as the resolution to trigger specific mobile features in BtnCmd, as user feedback was that when running on larger Tablet/Pads the desktop version was preferred, and this seemed to be inline with DWC. It would appear that the new bottom menu is triggered at higher resolutions, which is conflicting with BtnCmd. I would prefer to keep BtnCmd inline with DWC, so can you confirm if triggering the bottom menu for <= 1024x1366 is correct, and I will adjust BtnCmd to be inline with that choice.

Many Thanks

dc42 · 18 Dec 2021, 11:25

@owend said in Version 3.4-b7 released:

With regard to driver_error....

Do all parameters equally apply to Duet 2 (apart from CAN address)?

Yes. The B parameter is provided but for compatibility but it will always be zero on Duet 2.

The notes say if the macro isn't found the print is paused without running pause.g. Presumably because pause.g would normally have movements which may not be possible. What state are the heaters left in?

Heaters are left running.

Fred-Y · 19 Dec 2021, 18:43

Just wanted to let you know that the issue I reported on the b6 for the Delta here https://forum.duet3d.com/topic/26033/3-4-0-b6-delta-print-leaning-moving-on-y-and-z/12 appears to have been resolved in the b7

I will try to make a few prints on my 2 deltas during the next days

Marcossf · 20 Dec 2021, 16:56

@chrishamm @dc42

Any news about correct the CAN delays limitation?

We can't use the mesh bed leveling in our printer because this issue. It get's increase each trigger point for the probe as it's going on while mesh creation or static G30 S-1 probe. Is not an accuracy or precission probe problem at all.

We drive all our axis (XYZUV) with 1XD boards connected by CANbus, and prinheads with 1LC (E0,E1,E2) and driven by absolute encoder closed loop motors (Oriental Motor AZD-K drivers and motors) using STEP and DIR signals from 1XD to OM Drivers.
So we think all the problems regarding probing (located in Z axis) are caused by this timing problem, while all the normal printing work is fine.

Thank you very much.

dc42 · 20 Dec 2021, 18:59

@marcossf I'm sorry, this isn't resolved yet. It is a high priority item though.

Marcossf · 21 Dec 2021, 10:16

@dc42 Thanks David.

I hope you will be able to sort it out very soon. Let me know if you want us to test something on our hardware, if you need it.

Best,
Marcos

EducatingSavvas · 22 Dec 2021, 11:29

@chrishamm Hi and thanks for the update. I've just updated to the new web controls from 3.3 but have lost any information about machine and work positions at the top of the dashboard. I am using CNC Mode. I can see it returns in Printer Mode. Is it also possible to have the option to see this information for advanced users, and to also remove the Go To Zero button under the movement buttons. If someone is using the wasteboard as Z0 and material has been fixed, moving to zero will crash the bit.

	Error:
	An assembly specified in the application dependencies manifest (PluginManager.deps.json) was not found:
	package: 'runtimepack.Microsoft.NETCore.App.Runtime.linux-arm', version: '6.0.0'
	path: 'System.Net.Quic.dll'