Heaters disappear in RRF Config Tool
I'm using the "RRF config Tool" for the initial setup of required files.
My system consists of a Duet 3 and 3 expansion boards.
In total I have 5 heaters. Every set of Heater, temperature element and extruder are connected to the same expansion board. The heater paragraph at section I/O mapping shows the bedheater and the 5 hotend heaters. (see picture Heaters.jpg)
The heaters section is showing the hotbed and the 5 defined hotend heaters (see picture heater section).
Every set of extruder, hotend heater and thermo element will be part of a tool element, i.e. a total of 5 tools.
So far so good, however when looking at the Tools section, suddenly, I only have E0, E1, E3 and E4, suddenly E2 disappeared. Is this a bug in the tool? Am I doing something incorrectly?
Of course, I know that I can adjust the files manually, no problem there, However when I misunderstood something than the manual adjustment will not work.
Thanks. I've been able to reproduce it in the tool. However, it looks like it's only a display issue in the tool as the gcode produced includes all the correct tools and heaters.
; Tools M563 P0 D0 H1 F0 ; define tool 0 G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C M563 P1 D1 H2 F0 ; define tool 1 G10 P1 X0 Y0 Z0 ; set tool 1 axis offsets G10 P1 R0 S0 ; set initial tool 1 active and standby temperatures to 0C M563 P2 D2 H3 F1 ; define tool 2 G10 P2 X0 Y0 Z0 ; set tool 2 axis offsets G10 P2 R0 S0 ; set initial tool 2 active and standby temperatures to 0C M563 P3 D3 H4 F1 ; define tool 3 G10 P3 X0 Y0 Z0 ; set tool 3 axis offsets G10 P3 R0 S0 ; set initial tool 3 active and standby temperatures to 0C M563 P4 D4 H5 F0:2 ; define tool 4 G10 P4 X0 Y0 Z0 ; set tool 4 axis offsets G10 P4 R0 S0 ; set initial tool 4 active and standby temperatures to 0C
H1, H2, H3, H4, H5 all accounted for.
Could have come to this myself pfff. Sometimes you get into a loop to start, trying to solve it.
Thanks Phaedrux for the very quick reply!
So finally it is a bug in the webapp. Who do I report this to?
Consider it reported.