Do you have know Gcode to set up hardware

irondesk40

had some time to do some looking in the forum and it appears you have to make a lot of modifications in Gcode etc. in order to get things to work properly, or am i wrong. Thanks

Stephen6309

@irondesk40 Easy way to setup the config.g file: https://configurator.reprapfirmware.org/Start

irondesk40

thanks. bacground is PLC and automation machines and new to 3d printer control boards. Very interested in learning and having some fun.

Phaedrux

It's definitely helpful to be familiar with gcode, or at least be able to look it up when needed.

This is a useful page to have open in another tab during setup,

https://duet3d.dozuki.com/Wiki/GCode

And also the main documentation site,

https://duet3d.dozuki.com/

irondesk40

looking at getting list of everything and reading on controlling external drivers and the link takes me to this information.
Maybe i have overlooked the information but on the guide to control external drivers i did not see a link to go to a section that explains how to modify the config.g file. Could you give guidance?

Using External Drivers for X/Y/Z Axis
To use external drivers to drive X, Y and/or Z axes instead of the internal ones, you need to remap the X/Y/Z axis to the external driver. The drive numbers are:

Number Name
0 X Axis
1 Y Axis
2 Z Axis
3 E0 Axis
4 E1 Axis
5 E2 Axis (Expansion Header)
6 E3 Axis (Expansion Header)
7 E4 Axis (Expansion Header)
8 E5 Axis (Expansion Header)
9 E6 Axis (Expansion Header)
10 10 (LCD_CONN Header)
11 11 (LCD_CONN Header)
To remap the X, Y or Z motors to external drivers in RepRapFirmware 1,14 or later, use the M584 command.

Danal

Depends on what you mean by "familiar with Gcode". I'd take that to mean knowing what the move commands are, etc.

Duet DOES use "G-Code" as a configuration language. However, prior knowledge isn't going to help all that much, as it uses specific M commands, with specific parameters, mostly unique to the Duet.

So... use the configuration tool to get a "starter" and adjust from there.

The VERY NICE thing about this setup is that the commands work in real time, the moment they are issued. Sure, there is a set of them in the file "config.g" that automatically run at boot... but there's nothing unique about them... feel free to issue commands via the console or web interface and see the changes. Update the command in config.g when you get what you want.

A few of the commands have order dependencies. This is mostly common sense. For example, a heater must be defined before parameters for that heater can be set, or it can be grouped into a tool, or similar.

Anyway, configuring everything with "M" commands may seem strange at first. As it turns out, it is VERY powerful and relatively easy to use.

irondesk40

Thanks. Been doing some reading today here at work in our lab. Pretty slow today and now have a little better understanding of how the G code works, only a little. But to be honest was looking at this product or a smoothie board and from the support on this site and from some emails, Duet wins by a mile. We are hoping this works out and if so could evolve into a lot of test machines, but being a R&D department, you have to first test and prove a concept and cost savings.

Danal

Compared to the smoothie community, two things are easy to observe:

the primary developer of duet is VERY active, VERY responsive, and very humble.
The community, right here on this board, is the same...