-
-
Notifications
You must be signed in to change notification settings - Fork 19.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Export M503 setting to file - serial redirect #26904
base: bugfix-2.1.x
Are you sure you want to change the base?
Conversation
Why are people so adverse to using a control program?.. Dont have to fight with a sdcard or any such silliness... |
You should use serial - or computer, or phone/tablet with USB OTG adapter. |
People are too lazy. Otherwise: when you have a possibility to Export settings to a file and Import it you use it. So i have written something similar and People like and use it. |
This is simply a user experience upgrade. It does seem useful to me. Why do anything to make things simpler? Well, cause it makes life easier for some people. My only qualm is that this would require 2 SDCards, since the one used to flash has to contain only the firmware file. |
I’m not aware of any board that requires this. You can store / print G-code from the same SD that’s used for flashing firmware. |
@vovodroid: It would be extremely helpful if you completed this PR to add a proper configuration option as well as ensure all CI tests pass. |
On Ender-3 the firmware.bin file must be the only file on the SDCard to properly flash the firmware. While you could use one card, it would involve backing up on a computer and kinda defeat the whole purpose of this. But that is just 1 machine, and maybe not even all of those machines, since mine seems to have some weird quirks with flashing. Still a useful feature to add this IMHO. |
Can I run all these tests in my local environment? |
Yes, with make tests-all-local Note
(h/t to @The-EG for walking me through these errors!) Or run a single test like: make tests-single-local TEST_TARGET=FYSETC_F6 |
I tried to run
|
a253733
to
80cc6fb
Compare
I see you have a MingW64 environment setup, whether you intended to use it for this or not. The makefile is intended to be used in a linux/unix environment, so you'll need to arrange for the standard utilities to be there. In this case it's complaining about not finding Note that you need that *nix environment and PlatformIO both available, and PIO generally doesn't play nicely with MingW/MSYS. I've gotten these running on Windows before with some finagling but setting up WSL would probably be a better solution for this (and you can even use VSCode with it still too). |
I will second this. Actually cloning the git repo into a WSL session and opening it remotely from VSCode works very well. As long as you are using WSL2 and using a native-Linux path for the git repo it will also build much faster than doing it on Windows through MinGW. Just be sure you are not using WSL2 inside a Windows folder...that is horrendously slow. (WSL1 was exactly the opposite, but I imagine nobody is using WSL1 anymore?) |
I didn't succeed in getting platformio working in WSL, so eventually I run all (including Visual Studio Code) inside VMware Ubuntu guest. But when I run
while on Guthub after |
3a04b53
to
1e88ac8
Compare
I updated PR to pass all tests. But when new feature is disabled by default no actual build is performed. Also when Sanity.h detects conflicting option for some config test also fails. So just for tests I enabled setting export and and add check to Configuration_adv.h to prevent test fail. For actual build two latest commit should be discarded. |
finally #15052 |
c792921
to
37fb26b
Compare
* 🔨 Update ESP32 env for MKS Tinybee * 🔨 Updated LPC common env * 🔨 Other env improvements Co-Authored-By: Michael <[email protected]>
bbcac94
to
5198037
Compare
37d77d6
to
aa44542
Compare
Description
This PR adds menu item for redirection of M503 serial output to M503.gc file in the SD card root.
Requirements
SD media and LCD screed. Build and tested with TFT35 display.
Benefits
It allows to save and next load current memory settings. It could serve as backup, and especially useful when flash new Marlin build with changed settings structure, demanding initialization of EEPROM. After such initialization M503.gc file could be "printed" and previous settings is being loaded into the memory.
Serial redirect could also be used in future for saving logs to file.
Example of export file:
Related Issues