config.g vs config.json?
-
I just started with a Duet2 Wifi board.
So i have a lot to learn.But i change some settings in the config.g file. Other settings i changed with the RRF Config Tool. But now a lot of settings are changed, which i didn't change in the RRF Config Tool...??
So what is the difference between the 2 config files, and which do i have to edit??
Thanks in advance!!
-
@SoDamnInsane The file config.g on the SD card contains the Gcodes your Duet2 will execute at start-up. The RFF Config Tool is just a means to generate a basic config.g by entering technical data of your printer and some components. From this, it produces some kind of template-config.
In many cases, you will have to modify and adjust the Gcodes after that. This should better be done by editing the config.g file directly. Finally, you will need some basic understanding of these Gcodes, anyway.
-
@infiniteloop said in config.g vs config.json?:
@SoDamnInsane The file config.g on the SD card contains the Gcodes your Duet2 will execute at start-up. The RFF Config Tool is just a means to generate a basic config.g by entering technical data of your printer and some components. From this, it produces some kind of template-config.
In many cases, you will have to modify and adjust the Gcodes after that. This should better be done by editing the config.g file directly. Finally, you will need some basic understanding of these Gcodes, anyway.
Thanks!
So if i understand correctly, the settings in the config.g overrules the config.json settings??
I came from Marlin firmware before, so i know something about G-codes. But it's still a difference, lol.
And because i used parts of my old Anet A6, and added other hardware and upgrades, it's difficult to find my way in the Duet2 firmware.. -
@SoDamnInsane said in config.g vs config.json?:
I came from Marlin firmware before, so i know something about G-codes. But it's still a difference, lol.
So true. With Marlin, you deal with the firmware itself; on a Duet, the firmware is fixed (kind of), you configure and control the printer with the means of Gcodes. Think of the Duet firmware as a Gcode interpreter. For the world of 3d printers, it’s like the step from assembler to the first BASIC on early PCs.
The json file is an intermediate format for the RRF config tool, it has nothing to do with the Duet. This means: the RRF config tool is a one-way ticket, it helps to generate a basic config.g to start with, but it is by no means a human interface to edit and maintain an existing config.g file.
So, you have to learn Gcode. This here is a good language reference, I use it regularly. However, take it with a grain of salt: some of the Gcodes need a specific context, which is not always obvious. That’s where this forum becomes invaluable - well, you’ve found it already. Welcome.
-
@infiniteloop said in config.g vs config.json?:
@SoDamnInsane said in config.g vs config.json?:
I came from Marlin firmware before, so i know something about G-codes. But it's still a difference, lol.
So true. With Marlin, you deal with the firmware itself; on a Duet, the firmware is fixed (kind of), you configure and control the printer with the means of Gcodes. Think of the Duet firmware as a Gcode interpreter. For the world of 3d printers, it’s like the step from assembler to the first BASIC on early PCs.
The json file is an intermediate format for the RRF config tool, it has nothing to do with the Duet. This means: the RRF config tool is a one-way ticket, it helps to generate a basic config.g to start with, but it is by no means a human interface to edit and maintain an existing config.g file.
So, you have to learn Gcode. This here is a good language reference, I use it regularly. However, take it with a grain of salt: some of the Gcodes need a specific context, which is not always obvious. That’s where this forum becomes invaluable - well, you’ve found it already. Welcome.
Thanks, haha
That's where i went wrong. I thought that i could use both simultaneously....
Now my complete config is a mess.. I have the Duet2 board for about 1 month but just printed 2 test cubes with it, lol...
But thanks for the good explanation. I understand know what to do, i think, LOL.
I think i've to start all over again. But that is part of studying...
-
@SoDamnInsane said in config.g vs config.json?:
I think i've to start all over again. But that is part of studying…
Yeah, advanced studies in Gcode. But that’s exactly how to get a deep understanding of the matter. When you get a feeling of how the commands work and interoperate, you will have no problems to refine your prints. By the way: if you’ve already finished two objects, you have come a long way - I had a hard time figuring out how to just move a single axis, not to mention bed probing and levelling…
-
@infiniteloop said in config.g vs config.json?:
@SoDamnInsane said in config.g vs config.json?:
I think i've to start all over again. But that is part of studying…
Yeah, advanced studies in Gcode. But that’s exactly how to get a deep understanding of the matter. When you get a feeling of how the commands work and interoperate, you will have no problems to refine your prints. By the way: if you’ve already finished two objects, you have come a long way - I had a hard time figuring out how to just move a single axis, not to mention bed probing and leveling…
Hahahaha.... I had help from a few guys from the Facebook group. Unfortunately, i don't have a probe installed.. I bought a precision Piezo sensor. But i can't install it on my X carrier, i think... So i have to print a completely new one. And therefore i need the printer, lol.
-
@SoDamnInsane … and I had to print new part-cooling ducts without having part cooling available to print them - that was a major design challenge
