Macros on PanelDue's Control Screen
-
@droftarts yes, I am running v1.24. Sorry I failed to mention that..
-
@Kolbi I’ve rebooted several times.. are you running a Duet 3 connected to an Raspberry Pi with macros on the RPi’s SD card?
-
@oozeBot No, I am not - I'm running Duet2WiFi, but the panel is its own serial attached appendage and I believe it would function the same.
Do the macros show up on the macro's screen? -
@Kolbi thanks for clarifying. It should act the same, but there were issues with it that 1.24 addressed when accessing the RPi’s SD card, but I think this wasn’t caught.. yes, the macros do show up on the macro tab.
-
@oozeBot Ok, understand all. From a curiosity standpoint, have you performed a power-down then power-on and seen if that yields a change?
-
@Kolbi yes - nothing shows after a reboot. The Macros tab lists them all, but nothing on the Control tab. @droftarts - would you please ask @dc42 and/or @chrishamm to review this? Thanks
-
@oozeBot rgr all. Just was curious if scenario changed with software reboot vice shutdown via power and the full power on - it happens to a lot of systems that we deal with. Best of luck
-
@oozeBot said in Macros on PanelDue's Control Screen:
From what I've read, the top 4 macros should be visible in the circled area in the pic
Where did you read that? I wasn't aware macros would show up there now, just in the top right corner. Maybe I missed that.
-
@Phaedrux well, maybe that is my misunderstanding of where they'd show up as I just assumed it was in that empty row.. where are they supposed to show up? Is it the empty area in the top right corner? If so, my mistake.. but they still aren't showing up at all. If this is just my misunderstanding, is there any guidance you can give me?
-
They would show here on the control tab.
-
@Phaedrux thanks for the photo. What I am experiencing on a Duet 3/RPi is that no macros are showing up on the Control tab of the PanelDue. My suspicion is this is a defect that has gone unreported until now. It was just recently that the defect was corrected that allowed Macros on the RPi's SD card to even show up on the PanelDue (I'm the one that reported it). This feels like a similar scenario. Would you please ask @dc42 and/or @chrishamm to review this?
-
@oozeBot
I don't run a pi, so can't be sure if it's the same, but on the D2, macros will only show on that screen if they are placed in the root of the macros folder.
Anything in a sub folder can only be accessed from the macros page. -
@OwenD said in Macros on PanelDue's Control Screen:
@oozeBot
I don't run a pi, so can't be sure if it's the same, but on the D2, macros will only show on that screen if they are placed in the root of the macros folder.
Anything in a sub folder can only be accessed from the macros page.Good call out - the test scripts are in the root Macros folder. Thanks
-
How are they named?
Can you test in standalone mode to isolate the problem to the rpi side?
-
@Phaedrux there is currently just a single macro in the root macros folder named 01_test.g. It shows up as test.g on the Macros tab, but does not show up at all on the Control tab.
While I understand what you are asking, I do not have any experience running the Duet 3 in stand-alone mode. I suspect it would work as I’ve found several other things that seemed to only break when running from the RPi’s SD card- specifically, no macros displayed on the macros tab before 3.1.1..
-
@Phaedrux - is there a better way to report defects than forum posts? Github? Thanks
-
I've brought it to attention, but it is the weekend after all.
-
@Phaedrux thank you. Sorry- I didn’t mean it like that.. I’m new to Duet and am literally asking the best method for reporting defects.
-
You've found the right place.
-
@oozeBot How many tools have you configured? There is a bug in the current release that for 4 tools or more it won't show macros on the Control tab even though it could still show them for 4 tools (but no longer for 5 tools).
This is fixed in the new PanelDueFirmware 3.2-RC1 that I am about to release now.
Also there was an issue fixed in DuetSoftwareFramework 3.2-beta1 that might have caused this problem.
