This is the Cerberus Gigante Deltabot. 5' x 34" print envelope. I didn't use the expansion board, but I am using Duet2 wifi with external drivers which theoretically 'could' have been connected that way? In any case, it's a cool deltabot project. Currently in operation at Arizona State University in the Grant Street Studios 3D media lab location. I'm the 6'3" shiny headed dude in the photo, for size reference.

First day, delivery!

Or just a big tornado print that was ready when I came back the next morning?

@phaedrux -- Problem resolved on my end.

Thank you very much for getting me over that hurdle. I'm very appreciative of your time and expertise with something that really had me stumped.

Last evening I switched out the motor and endstop wiring (physically moving the tower mapping to X=Z, Z=Y and Y=X) and ran the same print. The error stayed with the original tower even though it is now mapped to believe it's the 'X' tower. I then interfaced with the motor using the Teknic MSP software and using the 'scope function it appears that the motor is actually losing positioning early in the move and never recovers. Because it was getting late and it was not at my shop I didn't delve into the exact number of steps it's losing. It's just strange that it loses that positioning in one direction only.

In any case, I don't think this is a Duet hardware or firmware issue and I'll be contacting Teknic for an RMA.

Regards to all and thanks to you guys for developing such a configurable controller. Overall I'm extremely happy with its performance on my most recent printers, and I've begun retrofitting some older ones too.

It struck me last night as I was falling asleep that I wasn't seeing the super basic and easy way to accomplish what I want.

The best overall solution would of course be to set up a dynamic macro to repeat any currently selected print via a physical button. And that would require knowing the current print file name and path which would require upgrading to RRF3.1. That way the button would be maintenance free.

In my case I'm printing a known file over and over and I don't have time to upgrade right now. So I'll simply hard-code the macro with the filename I want to reprint. If that file ever changes due to versioning, etc. I'll just edit the macro.

M32 "0:/gcodes/Cerb400_1-1.0mmNozz/PETG/30xMB_V4.0-Plated.gcode"

When I finalize the physical button housing attached to the printer it will include several other momentary push buttons for preheat, motors off, home and board reset. Maybe I'll include a little clip to hold a post-it with the macro-filename listed on it.

@phaedrux -- Problem resolved on my end.

Thank you very much for getting me over that hurdle. I'm very appreciative of your time and expertise with something that really had me stumped.

RRF Config Tool Settings:

What am I doing wrong here?

I/O Mapping screenshot:

Heaters screenshot:

Web Interface screenshot: Notice that the bed heat is working but the hotend is disabled:
This is what I get when using the code generated above by the RRF Config Tool.

I finally decided to take the plunge and upgrade my deltabot printer from v2 to v3 firmware. This was very scary in concept, and not so hard in reality. Except that the bed and hotend heaters didn't remap properly. Honestly the V3 codes are much harder for me to understand and 5 hours into this I still can't edit my way out of the problem. Aside from feeling like a loser, the heater remapping is my problem that I need help with.

I'm using a 24v SuperVolcano hotend and a 110v SSR controlled bed heater. Because of this I have the heater and bed outputs remapped/swapped. The bed heater mosfet being better suited to the current draw from the 80W SuperVolcano heater, and the Duet hotend mosfet controlling the bed SSR.

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.02 or later

My functional 'Heaters' code from my V2 config.sys is;

; Heaters
M140 H1                                     ; remap heated bed to heater 1
M307 H1 B0 S1.0                             ; disable bang-bang mode for the bed heater and set PWM limit
M305 P0 T100000 B4388 R4700                 ; set thermistor + ADC parameters for heater 0
M143 H0 S290                                ; set temperature limit for heater 0 to 280C
M305 P1 T100000 B3950 R4700                 ; set thermistor + ADC parameters for heater 1
M143 H1 S120                                ; set temperature limit for heater 1 to 120C

I used the RRF config tool and uploaded my v2 JSON template, specifying V3 config.sys output. But this is not working.

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0                                   ; create nozzle heater output on bedheat and map it to sensor 0
M307 H0 B0 S1.00                                        ; disable bang-bang mode for heater  and set PWM limit
M143 H0 S290                                            ; set temperature limit for heater 0 to 290C
M308 S1 P"e0temp" Y"thermistor" T100000 B4092           ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1                                    ; create bed heater output on e0heat and map it to sensor 1
M307 H1 B0 S1.00                                        ; disable bang-bang mode for the bed heater and set PWM limit
M140 H1                                                 ; map heated bed to heater 1
M143 H1 S120                                            ; set temperature limit for heater 1 to 120C

It struck me last night as I was falling asleep that I wasn't seeing the super basic and easy way to accomplish what I want.

The best overall solution would of course be to set up a dynamic macro to repeat any currently selected print via a physical button. And that would require knowing the current print file name and path which would require upgrading to RRF3.1. That way the button would be maintenance free.

In my case I'm printing a known file over and over and I don't have time to upgrade right now. So I'll simply hard-code the macro with the filename I want to reprint. If that file ever changes due to versioning, etc. I'll just edit the macro.

M32 "0:/gcodes/Cerb400_1-1.0mmNozz/PETG/30xMB_V4.0-Plated.gcode"

When I finalize the physical button housing attached to the printer it will include several other momentary push buttons for preheat, motors off, home and board reset. Maybe I'll include a little clip to hold a post-it with the macro-filename listed on it.

Unfortunately, M24 and M23 commands both expect a filename to be included with the command. So that's a no-go.

The 'Start Again' button in the DWC uses M32 command but it too is asking for the filename, and in the DWC the command+filename is written out directly to the html page when it's generated.

It appears that any macro created to restart a completed job using the M23, 24 or 32 commands would need to have the filename of the currently selected file written to it each time a print was selected. Or maybe the filename would need to be held in memory.

Unless there is some other option.

@bot Why thank you Bot (not actually a bot)!

I'll give it a try as soon as the current print is finished

Hi guys,

I've been printing the same plate of mask buckles in production mode over and over with no issues. It would be great if I had a physical push button on the printer to start the last print over again after clearing the bed instead of having to wake the pc from sleep, wait for it to reconnect to the wifi and then click the restart print button in the DWC.

I understand how to set up physical buttons to run macros, but what is the Mcode to restart a print that completed successfully? (I did look for this but maybe I'm going blind? ...)

Thanks!

Steve Graber

Board: Duet WiFi 1.02 or later
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 2.02(RTOS) (2018-12-24b1)
Duet WiFi Server Version: 1.23

@dc42 Well.... No worries. I'm just happy to get it working and to move on to my next issue, which is to figure out exactly how many steps/mm this big stepper puppy needs and what the actual mix ratio is supposed to be. The Cerambot documentation is thin, to put it kindly.

Thanks again for a really fantastic piece of configurable hardware.

Steve Graber

Ok, I resolved the issue by moving the E0 stepper to E1 connector and making the change for that stepper output 3 to 4 in the config.g file.

M569 P4 S1 ; physical drive 4 goes forwards
M569 P5 S1 T2.5:2.5:5:2 ; physical drive 5 goes forwards
M584 X0 Y1 Z2 E4:5 ; set drive mapping

It appears that you can skip a stepper driver P3 after defining the xyz motion steppers, but the extruder mixing stepper drivers have to sequential? E4:E5

Is it allowed to skip the second board driver E1 in the mapping?

Danal, because of the way the 'Tool' is set up as mixing, it is treated like any extruder extrusion command the firmware does the mixing based on the M567 ratio.

But, this is my first attempt at a mixing extruder, so I've almost certainly fat-fingered something?