Yes, and no. The thing is Marlins 'parameter names' are open for change. This means a config file from an early marlin might not work on a later version. And lets say, I want to test out Repetier firmware, or maybe the smoothie board firmware. The names are completely different again. But if parameter names could somehow be described on standardized form, then it would be much easier for a userby dkcookie - Developers
Yes, and no. The thing is Marlins 'parameter names' are open for change. This means a config file from an early marlin might not work on a later version. And lets say, I want to test out Repetier firmware, or maybe the smoothie board firmware. The names are completely different again. But if parameter names could somehow be described on standardized form, then it would be much easier for a userby dkcookie - Developers
I would like to propose a new Universal Configuration Language, to use when testing multiple firmwares, on the same machine. The idea is to develop a standard for an abstract language that can be parsed to different firmwares. If we as a community could invent such a language it would make configuration across systems, as well as sharing configurations MUCH easier! I have attached a first draft,by dkcookie - Developers
Hi Amigob, If you got any left, I am very interested.by dkcookie - Developers
Nice Work, if you got more boards left, I am very interested.by dkcookie - Controllers