User Variable Bug?

Print3d

I've been playing around with object model variables and came across a strange bug. I noticed my DWC was running v3.2.2 while everything else was running V3.3-b2.

Board: Duet 3 MB6HC (MB6HC)
DSF Version: 3.3-b2
Firmware: RepRapFirmware for Duet 3 MB6HC 3.3beta2 (2021-03-10)

Under this configuration, "user variables" shows up in the object model tab of DWC... I'm not sure why DWC didn't update when I updated DSF so I manually uploaded the "DeutWebControl-SD-3.3-b2.zip" to bring everything up to the same rev. As expected, DWC rebooted and I confirmed DWC was now running 3.3b2 however now "user variables" in the object model tab have disappeared.

To test this again, I downgraded DWC back to 3.2.2 and saw "user variables" re-appear. Upon upgrading DWC to 3.3b2 once more, "user variables" has again disappeared from the object model tab.

To make matters more interesting, I tried creating a new variable in daemon.g by adding " var testing1 = 1;". Once saved, DWC console then pits out "Error: Failed to read code from macro daemon.g: Keyword Var is not supported in line 8"... I'm assuming its not recognizing the user variable because the "user variable" directory was somehow deleted during the upgrade?

Has anyone else come across this bug or am I doing something wrong with my variable declaration syntax or DWC update procedure?

I've uploaded a screenshot of DWS 3.3b2 to show "user variables" is missing. Object model screenshot.JPG

gloomyandy

If you are running in SBC mode I don't think that variables are supported by DSF in beta2. See known issues: https://github.com/Duet3D/DuetSoftwareFramework/blob/v3.3-dev/WHATS_NEW.md

Print3d

@gloomyandy That makes sense, I'm running SBC mode. Do you know if a hybrid solution has been tested by inserting an SD card with configuration files into the Duet3 board so all sys files are loaded stored locally, while still communicating with SBC?

I haven't tried this at all but it would seem this hybrid solution would be the best of both worlds -- if it worked and one could manage to disable the Duet auto updates from SBC.

jay_s_uk

@print3d that's not supported. It's one or the other