BtnCmd-DWC Plugin - Customise DWC - v01.03.05 20-09-24

[Stephen6309]

@mintytrebor 6HC with a Pi4 and 1LC.
FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.3beta3 ELECTRONICS: Duet 3 MB6HC v1.01 or later FIRMWARE_DATE: 2021-04-22 16:28:03

Duet TOOL1LC firmware version 3.3beta3 (2021-04-21 20:42:51)

DWC is 3.3.0-b3

Installed via System's upload system files.

[Stephen6309]

Update: I had uninstalled and deleted those new files in Jobs. I've now reinstalled, and nothing show up in Jobs. Dang computers...

[MintyTrebor]

@stephen6309 Sounds like a glitch on the install. Glad you got it resolved!

[Stephen6309]

@mintytrebor Can't select a panel from the drop down that appears underneath the add panel dialog, the drop down just disappears. The help hint for enable MQTT is under the BtnCmd Setting dialog, so you can't read it.

Chrome Version 90.0.4430.85 (Official Build) (64-bit)

Microsoft Edge does the same thing.

Windows 10 20H2 64-bit.

[MintyTrebor]

@stephen6309 Thanks for the feedback. Is it similar to this issue https://forum.duet3d.com/topic/22403/weird-dwc-z-index-dialogue-issue ?

[Stephen6309]

@mintytrebor Select add panel, click on down arrow, drop down appears, can't use mouse to select, but the up/down keys work.

Reuploaded DuetWebControl-SD.zip, no change.

[MintyTrebor]

@stephen6309 Does it look like this or different?

[Stephen6309]

@mintytrebor No, that dropdown is underneath the Edit Panel. Can't see DWC Webcam and Alt Webcam.

[MintyTrebor]

@stephen6309 Thanks for info. If you/when you have an opportunity I would appreciate it if you could check if the issue is the same on the edit button settings window.

This does sound like the same issue as I linked to previously, its unfortunate the resolution didn't work for you. We were never able to track down what the cause was....

[Stephen6309]

@mintytrebor No dropdown appears with Edit Button Type. Up/Down keys work.

[MintyTrebor]

@stephen6309 Thanks! I think that confirms it is the same issue.. I wish the fixed had worked for you.

I will re-instate the work around I had in place, I only took it out in this version. To get around the problem (because we could never track it down), I implemented a "use radio buttons" option which changed all the drops downs to radio buttons, for the users who experienced this problem. I cannot re-create the problem and there is nothing in the code that is causing the issue, it seems to be a weird framework bug, which does not impact everybody. I'll let you know when I have published the changes, at least then you can use the plugin without issues.

Thanks for the feedback, and answering my questions its appreciated.

[tristanryerparke]

Hey @MintyTrebor, thanks for the new version. I just made myself a little endstops monitor.
How ever I cant get the object model panel to display the value of a global variable. The panel just lists: ### as the value. Have tried with strings, ints, floats and booleans. All other OM values seem to work.
Are you or anyone else experiencing this issue?
Duet3-6HC + Pi4, DSF, DWC and RRF all running 3.3beta3
Thanks,
T

[MintyTrebor]

@stephen6309 I have just pushed 0.8.17 Alpha to github.
If you open global settings and disable the "Selections in Settings" option, all of the drop downs will switch to radio buttons.

You may still experience a few hover/tooltip issues.

The overall issue appears to be a plugin system or framework bug, which occurs at the local level and does not affect every user. Unfortunately I am unable to correct this issue within my plugin as there no options available to me to change this behaviour as it is part of the core bootstrap/vue system used by DWC. The fact you had an issue installing the plugin the first time, is a new data point I did not have before.

If any others are having this issue please can you let me know, or post an issue on github. I would really like to get the bottom of the issue - I want to know if its my stupid mistake, or something else.

[MintyTrebor]

@tristanryerparke The three ### is a placeholder I put in the code to tell you/me when the system is unable to match the Model Path you entered in the current machine model resident in DWC. Which means 1 of three things..

1. The active machine model in DWC does not always contain all of the object model at the same time, some values may only be available during print etc.

2. I'm using the wrong machine object model resident in DWC or DWC does not load global variables in its default object model and I have to supplement the default model with global variables in my plugin code.

3. You have entered the wrong path - but given this is exclusive to a particular class of object I doubt this very much.

Could you give me an example path you are using please, then I track it down.

Edit - Also any chance of a screen shot? I would like to see how your using it!

[Stephen6309]

@mintytrebor v0.8.17 works with Selections in Settings off.

[MintyTrebor]

@tristanryerparke I ran some tests by creating my own global variables using the

global <new-variable-name> = <expression>

command.

In the OMB plugin it looks like this:

I set up a new Model Panel in BtnCmd like this:

Which worked OK.

Is this what you did/expected, or am I missing something?

[OwenD]

@mintytrebor
It works for me, although didn't at first because I accidentally copied a trailing space when I copied it from the OM browser.
The only problem is that the DWC global variable values aren't updated at the moment.
The dev's are aware, so it will likely be fixed in the next beta.

[MintyTrebor]

@owend Great! Thanks for letting me know.

[tristanryerparke]

@mintytrebor I'm going through the same process:
First sending:

global testBTN = 40

Checking in OM browser (refreshed a few times to be sure):

Then setting up the panel:

I checked for trailing spaces and made sure they were not there.
Still getting "###":

Also I tried sending this command:

set global.testBTN = 45

To see if it would update the value in the panel, but still have "###".
Are you guys in standalone mode/duet2? I'm running an SBC.
Cheers,
T

[MintyTrebor]

@tristanryerparke I'm using a stand alone config on a duet2. That may account for the variance??

In principle DWC is the same for both versions - however there maybe some differences in the way the machine model is retrieved in the backend.

In the plugin I am not retrieving the model, I am using the one that is already resident in DWC, so I will have to do some digging to see what I can find out. Its unlikely to be a speedy process though.

Update: I've just spotted this post https://forum.duet3d.com/post/227873, which seems related to this issue. Looks like its an SBC issue.....