Command M503 does not work on builds compiled from GitHub Actions

[natey416]

Did you test the latest release build?

Yes, and the problem still exists.

Bug Description

Attempting to get EEPROM Editor working through Octoprint.
When using the firmware compiled from GitHub actions (Aquila_GD32_UBL-ProUI-EX-12-12.bin), the M503 command sends response Recv: echo:Unknown command: "M503"

When compiling through platformio, copying the configurations found in configurations/Voxelab Aquila/UBL/, I was able to get the M503 command working.

Here's my marlin configs: Marlin.zip
Didn't change anything besides the input shaping settings.

Hoping this is just something with the actions bot.

Printer Model

Voxelab Aquila

Model Type

Aquila OG

Your Mainboard

Aquila GD32

Other Mainboard Type

No response

Add-ons that could be involved

CR-Touch, Rasp-pi

ProUI-EX | Extra Features?

Yes

Bed Leveling

UBL - Unified Bed Leveling

Did you include your own configuration files?

• A ZIP file containing your Configuration.h and Configuration_adv.h.

Additional information & file uploads

No response

[classicrocker883]

some things had to be disabled in order for all the options to fit.
there is one called MARLIN_SMALL_BUILD in Configuration_adv.h in which disables M503, but it wouldnt be enabled for Aquila_GD32_UBL-ProUI-EX. maybe if it had MPC & INPUT_SHAPING

[classicrocker883]

I made a test release here. let me know if it still does not work.

do you recall a time [month] that this did start working ?

[classicrocker883]

#168

does this issue sound familiar? maybe related?

[natey416]

I did see #168 when looking up my issue, this could be related, which I why I ended up trying my own config. My configurations are attached in the original post, Everything else is based on 2024-December release.

Using Aquila_GD32_UBL-ProUI-EX-01-26.bin, still results in Recv: echo:Unknown command: "M503"

I can do more testing after work today, but that's all I had time for this morning.

[classicrocker883]

instead of ubuntu-latest, ill go the way Marlin went which was to keep 22.04 since they were having issues with the latest (24.04)

Im going to post a January release and hopefully everything else should be fixed

[classicrocker883]

I changed the workflow so hopefully this fixes the issue
Posted the new release here

[natey416]

Just downloaded Aquila_GD32_UBL-ProUI-EX-01-30.bin.
M503 gives the same Unknown command: "M503"
Compiling it works just fine with default UBL aquila config.

If I'm the only one with this issue, it might just be my hardware. There doesn't seem to be a lot of complaints about this.

[classicrocker883]

how do you get this error? what steps do you take

[natey416]

I'm switching from the older Alex/Jyers Firmware. I use the firmware selector to select the Aquila G32 mainboard, ProUI, Cr/Bl Touch, and UBL. I take this firmware and place it in the SDROOT/firmware/ folder on the printer's SD card. I unplug octoprint from the printer, insert the SD, start up the printer. Firmware automatically updates successfully and the splash screen runs just fine.

Before I touch any settings, I connect octoprint back up, establish connection, then go to the terminal and run the command M503. The error will show then. Running it through pronterface shows the same error.

This process is the same whether I download from firmware selector or manually pick out the firmware in the release section. Compiling it with the defaults the actions bot should be using works just fine.

[classicrocker883]

have you tried any of the older firmware files, like 2024-April release I would suggest.

[natey416]

I can try those ones out this afternoon when I get off work. I'll let you know which month stops working.

[classicrocker883]

actually a quick look at the other issue I see this:

I tried the newer builds (Nov 2024 rev1, Nov 2024, Oct 2024 rev1) and the only one that connects is the October 2024 (2.1.3f-10) one.

but have you tried October?
which you can find here

[natey416]

Apologies for the wait. Got wrapped up in a bunch of stuff yesterday.
Just tried out 2.1.3f-10 October 2024. M503 and EEPROM Editor work as expected!
Attempting 2.1.3f-10-1 through latest results in the same Unknown commmand: "M503"
Everything prior (including 2.1.3f-7 through 2.1.3f-9) seem to work as expected.