GCodes for the next-generation Duet

wilriker

@dc42 My personal favorite in this list is number 3. I would in this case also allow to optionally address the drivers of the main board with a 0. prefix to be able to have a consistent scheme if one wishes to do so.

Second choice would be number 2 for me.

I don't like number 1 because on a say 6th expansion board one would have to seriously calculate the number of the driver taking into account that these are indexed zero-based. That might confuse non-CS people too much and is bound to cause trouble.

JoergS5

@dc42 The more drivers, fans and heater you support the more problems with counting ("what is my P8?") will arise. So an optional labeling would be nice, maybe implemented as preprocessor. Then the user can name it as one's will and it can be displayed in the panel. It is easer to recognise "Heater Back Top" than H7.

dc42

@joergs5 said in GCodes for the next-generation Duet:

@dc42 The more drivers, fans and heater you support the more problems with counting ("what is my P8?") will arise. So an optional labeling would be nice, maybe implemented as preprocessor. Then the user can name it as one's will and it can be displayed in the panel. It is easer to recognise "Heater Back Top" than H7.

So in the command you used to assign the name "Heater Back Top" to a heater, how would you specify which heater that is?

projectR3D

I think option two would be my first choice with the third coming next. Also if there will be the possibility to daisy chain more than one expansion would the drivers on the first expansion be 101, 102, 103.... while the next expansion in the line be 201, 202, 203...?

gtj0

@projectr3d said in GCodes for the next-generation Duet:

I think option two would be my first choice with the third coming next. Also if there will be the possibility to daisy chain more than one expansion would the drivers on the first expansion be 101, 102, 103.... while the next expansion in the line be 201, 202, 203...?

FWIW, I think option 3 will result in even more "this is too fricking hard to configure" posts.

gtj0

Oh yeah @dc42, on the new boards you'd better make sure the silkscreen labels match the physical designator scheme. Labelling things with their logical uses on the Duet2 and Duex5 was very confusing for me when I started out.

Labelling them with their physical capabilities would be the best option.
drive
2 pin pwm out (2PO)
3 pin in (3IN)
low power mosfet (LPM)
high power mosfet (HPM)
etc.

JoergS5

@dc42 said in GCodes for the next-generation Duet:

@joergs5 said in GCodes for the next-generation Duet:

@dc42 The more drivers, fans and heater you support the more problems with counting ("what is my P8?") will arise. So an optional labeling would be nice, maybe implemented as preprocessor. Then the user can name it as one's will and it can be displayed in the panel. It is easer to recognise "Heater Back Top" than H7.

So in the command you used to assign the name "Heater Back Top" to a heater, how would you specify which heater that is?

I would take option 1 in this case to be back compatible. The function is recognisable by the label, you have to assign it only one time at the beginning.

fma

Option #3 is the most intuitive.

To second @gtj0, the naming on the boards should be totally neutral. I mean, don't use X, Y, Z, just numbers, so routing between drives, hotends, endstops is not confusing. I would also put all drivers together, all endstops inputs together, all fans input together... Aslo, if all I/O could have the same behavior, it would be great (on the current board, Duet endstops and Duex ones can't do the same things, like monitoring filament sensor...).

Anyway, I'm sure the next hardware will be awesome!

dc42

@projectr3d said in GCodes for the next-generation Duet:

I think option two would be my first choice with the third coming next. Also if there will be the possibility to daisy chain more than one expansion would the drivers on the first expansion be 101, 102, 103.... while the next expansion in the line be 201, 202, 203...?

To achieve that numbering, you would need to set the ID switch on the first expansion board to 1, and the ID switch on the second board to 2.

dc42

@gtj0 said in GCodes for the next-generation Duet:

Oh yeah @dc42, on the new boards you'd better make sure the silkscreen labels match the physical designator scheme. Labelling things with their logical uses on the Duet2 and Duex5 was very confusing for me when I started out.

Labelling them with their physical capabilities would be the best option.
drive
2 pin pwm out (2PO)
3 pin in (3IN)
low power mosfet (LPM)
high power mosfet (HPM)
etc.

We're planning to label the connectors Motor0, Motor1, Out0, Out1 etc. Some of the Out ports will have a higher power capability than others, but all will be configurable as motors, fans or general purpose output.

dc42

@gtj0 said in GCodes for the next-generation Duet:

@projectr3d said in GCodes for the next-generation Duet:

I think option two would be my first choice with the third coming next. Also if there will be the possibility to daisy chain more than one expansion would the drivers on the first expansion be 101, 102, 103.... while the next expansion in the line be 201, 202, 203...?

FWIW, I think option 3 will result in even more "this is too fricking hard to configure" posts.

Why do you think option 3 is harder than option 2? They are logically the same, but for option 2 you need to do the (100 * board_id + device_id) calculation yourself.

Just to be clear: if you don't have any expansion boards then you will just need to specify the device number on the main board as now; although if we adopt option 3 then I would allow "0.1" as an alternative to "1" and so on.

keyz182

I think option 3 is by far the cleanest. If labelling is added too, it becomes even more clear, e.g. if you set the label of expansion board 1 to "MyAwesomeExpansion" and one of it's drives to "ZAxis", you get super easy to visually parse
M569 S1 PMyAwesomeExapnsion.ZAxis

Qdeathstar

I think option 3 is best. If only because that is an existing standard.

gtj0

@dc42 said in GCodes for the next-generation Duet:

@gtj0 said in GCodes for the next-generation Duet:

@projectr3d said in GCodes for the next-generation Duet:

I think option two would be my first choice with the third coming next. Also if there will be the possibility to daisy chain more than one expansion would the drivers on the first expansion be 101, 102, 103.... while the next expansion in the line be 201, 202, 203...?

FWIW, I think option 3 will result in even more "this is too fricking hard to configure" posts.

Why do you think option 3 is harder than option 2? They are logically the same, but for option 2 you need to do the (100 * board_id + device_id) calculation yourself.

Just to be clear: if you don't have any expansion boards then you will just need to specify the device number on the main board as now; although if we adopt option 3 then I would allow "0.1" as an alternative to "1" and so on.

Sorry, I meant option 2 would result in more "this is too...". I'm totally on board with option 3.

fma

@keyz182 said in GCodes for the next-generation Duet:

I think option 3 is by far the cleanest. If labelling is added too, it becomes even more clear, e.g. if you set the label of expansion board 1 to "MyAwesomeExpansion" and one of it's drives to "ZAxis", you get super easy to visually parse
M569 S1 PMyAwesomeExapnsion.ZAxis

Some sort of device tree overlay could be used to make the labeling...

gtj0

@dc42 said in GCodes for the next-generation Duet:

@gtj0 said in GCodes for the next-generation Duet:

Oh yeah @dc42, on the new boards you'd better make sure the silkscreen labels match the physical designator scheme. Labelling things with their logical uses on the Duet2 and Duex5 was very confusing for me when I started out.

Labelling them with their physical capabilities would be the best option.
drive
2 pin pwm out (2PO)
3 pin in (3IN)
low power mosfet (LPM)
high power mosfet (HPM)
etc.

We're planning to label the connectors Motor0, Motor1, Out0, Out1 etc. Some of the Out ports will have a higher power capability than others, but all will be configurable as motors, fans or general purpose output.

YAY!

keyz182

@fma Could be an interesting idea, especially it the DTO is stored on the expansion (seeing as they're getting more intelligent, with CanBus). Plug'n'Play

Danal

Another vote for option 3.

And another vote for neutral naming on the silkscreen, and exactly matching the silkscreen number to the gcode number.

And... EVERYTHING should use a CONSISTENT index origin. The first thingie should always be the zero-eth thingie. Always. In a all silkscreen, configuration addressing, documentation, DWC text, etc, etc.

pawPrinter

I like #3, but could a 4th idea be an additional parameter? eg. P for board, Q for it's driver. Maybe that complicates it more...

fcwilt

Hi,

#3 for sure.

Frederick