Posts made by ractorIII

@owend - thanks! this is very helpful. I'm going to test today this all today, including parking the head.

@phaedrux @OwenD

So, I did set in config.g:

M84 S0

Am I misunderstanding what M84 does? I thought setting the seconds(S) to zero would hold infinitely.

But the motors still lost power at the end of the print and dropped... Alternatively, is there a way to run a script or macro at the end of every print that will park the print head in a designated place? I could just type up the gcode and add it to the footer but that is not optimal for my purposes.

I need the Z axis stepper of my machine to stay engaged at the end of a print; otherwise the print head drops. I would like the idle timeout of my other axis to be 30 seconds. Can I separate these? In Config.g, would the syntax be:

M84 X Y S30 Z S0

Are tool mix ratios limited to a single decimal place?

e.g. M567 P2 E0.1:0.2:0.1:0.6

or can it be:

M567 P2 E0.15:0.25:0.15:0.45

or even:

M567 P2 E0.155:0.255:0.155:0.435

providing that the the values total to 1

@fcwilt

The N0 etc is line numbers - I find it helpful for troubleshooting.

I’ll have to report back with specifics, but - my m203 X and Y values are 6000, for Z and E they are lower.

@oliof and @fcwilt

I did read that on the Duet supported Gcode page, but I should still be able to use both G1 and G0 in my gcode if for no other reason that human readability, and with the following, I would assume that I can expect the first command to travel at twice the speed of the second and third.

N0 G0 F1000 X89.491664 Y138.276349 Z3.000
N1 G1 F500 X89.491664 Y138.276349 Z0
N2 G1 F500 X94.440476 Y138.573733 Z0 E0.310

But for some reason, all travel is about the same speed...

m203 max is defined at 6000 so I should be able to use any feedrate under that.

I'm used to working with a different flavor of gcode and I'm a little confused about controlling the speed for Duet Wifi.

background: I am generating gcode for a custom machine using Rhino to model and Grasshopper to create code. I'm switching from a tinyg control board by synthetos to the DuetWifi. I'm used to using G1 and G0 separately with different speed assignments so that the tool will move fast when not extruding (G0 for traveling between extrusion, G1 for travel associated with extrusion). In response to the following gcode, my G0 movements are not any faster than my G1 movements. What am I missing?

;PRINTING_2018_SORTING_1.0.4

;Friday, June 5th 2020 (13:51:03)

G90 ;ABSOLUTE DISTANCE MODE
M82 ; EXTRUDER ABSOLUTE DISTANCE MODE
G0 F1000 ;feedrate
G1 F500 ;feedrate

G92 A0 ;VERIFY AND SET A POSITION TO 0

M567 P0 E1:0:0:0:0
N0 G0 F1000 X89.491664 Y138.276349 Z3.000
N1 G1 F500 X89.491664 Y138.276349 Z0
N2 G1 F500 X94.440476 Y138.573733 Z0 E0.310
N3 G1 F500 X99.333629 Y139.371951 Z0 E0.620
N4 G1 F500 X104.124716 Y140.647376 Z0 E0.930
N5 G1 F500 X108.7726 Y142.373478 Z0 E1.239
N6 G1 F500 X113.239765 Y144.524609 Z0 E1.549
N7 G1 F500 X117.489313 Y147.078892 Z0 E1.859

Thanks, It helped me find a typo in M208 as declared in config.g

Issue closed.

I have a cartesian setup and I want my 0,0,0 home to be in the center for X and Y. For instance, my X settings range from -243 to 243 but when I home it is still setting the X min as 0 rather than -243.

I've tried adding "G92 x -243" to the end of homex.g and attempted entering it into the console. It does not seem to acknowledge negative values.

I guess that does work - I was looking feedback on the screen - like maybe 'ok' if it ran the command.

Having trouble: I can open the console on the 7" PanelDue display and type commands with the on screen keyboard, but I do not understand how to send the command (there is not obvious enter key).

Sorry - this was meant to be a message toward @dc42 :

@ractorIII said in Bench Testing Mixing Extruder with Pronterface:

@deckingman - thanks for your help. Eliminating the E6 driver mapping resolved the issue. All steppers are tested to be operating as expected.

I would like to use that final stepper on the Duex5 as an extruder eventually but will not need it anytime soon.

@deckingman - thanks for your help. Eliminating the E6 driver mapping resolved the issue. All steppers are tested to be operating as expected.

I would like to use that final stepper on the Duex5 as an extruder eventually but will not need it anytime soon.

thanks @dc42 - I need 5 extruder steppers at the moment - if that is the case I'll remap my motors so my dual Y steppers are not doubled up on one driver. Maybe that will fix my issue - I'll look into your other suggestions later today.

I would be interested in having more extruder steppers available in the future - or even the ability of mapping all of the drivers as extruders - the goal would be precise stationary liquid slurry mixing machine.

@Phaedrux - yeah - I wasn't sure if the drive should match the extruder number or the drive number, so I tried both M563 P0 D0:1:2:3:4 and M563 P0 D3:4:5:6:7 am getting the same 'tool creation: bad drive number. I read the sections on drive mapping and tool defining and everything seems to be in order. Unless I missed something. Dumbfounded at the moment.

@Phaedrux

; Configuration file for Duet WiFi (firmware version 2.03)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v2.1.8 on Sat Feb 01 2020 21:20:25 GMT-0500 (Eastern Standard Time)

; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"My Printer" ; set printer name

; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet

; Drives
M569 P0 S0 ; physical drive 0 goes backwards
M569 P2 S0 ; physical drive 2 goes backwards
M569 P1 S1 ; physical drive 1 goes forwards
M569 P3 S1 ; physical drive 3 goes forwards
M569 P4 S1 ; physical drive 4 goes forwards
M569 P5 S1 ; physical drive 5 goes forwards
M569 P6 S1 ; physical drive 6 goes forwards
M569 P7 S1 ; physical drive 7 goes forwards
M569 P8 S1 ; physical drive 8 goes forwards
M569 P9 S1 ; physical drive 9 goes forwards
M584 X0 Y2 Z1 E3:4:5:6:7:8:9 ; set drive mapping
M350 X16 Y16 Z16 E16:16:16:16:16:16:16 I1 ; configure microstepping with interpolation
M92 X87.58 Y87.58 Z1511.57 E3200.00:3200.00:3200.00:3200.00:3200.00:3200.00:3200.00 ; set steps per mm
M566 X900.00 Y900.00 Z12.00 E120.00:120.00:120.00:120.00:120.00:120.00:120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 E1200.00:1200.00:1200.00:1200.00:1200.00:1200.00:1200.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00:250.00:250.00:250.00:250.00:250.00:250.00 ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E800:800:800:800:800:800:800 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Axis Limits
M208 X-315 Y-650 Z-50 S1 ; set axis minima
M208 X315 Y650 Z300 S0 ; set axis maxima

; Endstops
M574 X0 Y0 Z0 S0 ; set active low and disabled endstops

; Z-Probe
M558 P0 H5 F120 T6000 ; disable Z probe but set dive height, probe speed and travel speed
M557 X-300:215 Y-635:195 S20 ; define mesh grid

; Heaters
M140 H-1 ; disable heated bed

; Fans
M106 P0 C"FAN3" S1 I0 F500 H-1 ; set fan 0 name, value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 C"FAN4" S1 I0 F500 H-1 ; set fan 1 name, value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P2 C"FAN5" S1 I0 F500 H-1 ; set fan 2 name, value, PWM signal inversion and frequency. Thermostatic control is turned off

; Tools
M563 P0 S"V" D0:1:2:3:4 F-1 ; 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
M568 P0 S1 ; enable mixing for tool 0
M567 P0 E0.2:0.2:0.2:0.2:0.2 ; set mixing ratios for tool 0

; Custom settings are not defined

; Miscellaneous
T0 ; select first tool

@Phaedrux -scratch that - installed and seems to be in sync now.

still trouble defining tool head - same bounce back from DWC on issuing M563 P0 D0:1:2:3:4

'tool creation:bad drive number

@Phaedrux - not able to upload file with DWC - followed instructions here:

https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware#Section_Updating_WiFi_firmware_or_DuetWebControl_files

to unzip DuetWebControl-SD.zip onto SD card after deleting old file contents

issue remains - AJAX error when uploading files via DWC

@Phaedrux - you may be right - this is what is listed on DWC. Should the Web Interface Version be HTML: 3.0? I'm starting to get very confused...

Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Version: 3.0 (2020-01-03b3)
Web Interface Version: HTML: 1.11

@Phaedrux Nothing happens when I attempt to send gcode through the Duet Web Interface - though the log state that I am connected, the log does not indicate that any code was sent. Another issue that I am having with DWC is that if I attempt to upload the zipped reprap config file I get an AJAX error and it disconnects. If I remember right - I was having this issue before and had to disconnect my power supply from the board and run it strictly of usb to get the upload to work - very inconvenient. I guess I'll open my housing and pull the micro SD out to update reprap config files.

To the issue at hand, which is getting a tool designated for bench testing my extruder setup. The following is how print run responds when issued:

SENDING:M563 P0 D0:1:2:3:4
Error: Tool creation: bad drive number
[ERROR] Error: Tool creation: bad drive number

I'm using a duet wifi with x5 expansion - I have a total of 7 extruder steppers and for this tool I am trying to use the 2 that are on the Duet Wifi and the first 3 that are on the x5 expansion.