Posts made by CTRDevelopments

@phaedrux 20% was much improved. I am now going to try 18% as still some very slight marks. The prints take a few days each so feedback is not the fastest, but it is a good test. Thanks for help

@blacksheep99 25%

@blacksheep99 OK, so perimeters have now eradicated it completely. I am however getting a bleed through of the infill into the outer walls. I am printing 3 outer walls (0.8mm nozzle) and only 5% infill (the wavy prusa slicer one). I didnt have this before but not sure if it is linked to the changes or not as I have swapped to fiberlogy filament as I ran out of the 3DFilaprint PETG large spools

So, retraction at 0.3 got probably 90% of the way there. Will try the perimeters next

@blacksheep99 so, I am using 1.4 mm retraction, I can try lowering that (35mm/s speed also)

@Phaedrux yes, I have that selected, again I will try that

I have just started a 2 days print so will tweak after that

many thanks both

Cheers

I am getting strange gaps in the outer perimeters of parts. It looks to me like pressure advance but I have disabled pressure advance and it is still doing it. Everything else seems OK, steps per mm etc etc

I am using a hemera extruder but was also getting this with a different Aqua extruder.

Sliced with Prusa slicer

It seems to be at the start of the extrusion

TIA

@jay_s_uk said in Duet 3 Tools:

@CTRDevelopments said in Duet 3 Tools:

Essentially can a 'tool' consist of a toolboard AND other inputs elsewhere?

dc42 said in Duet 3 Tools:

be connected to different boards.

yes

ahh, yes, didnt spot that. Would help if I read things properly! Cheers

@Phaedrux said in Duet 3 Tools:

@CTRDevelopments said in Duet 3 Tools:

Is this possible using toolboards on the Duet 3 as one motor would be on the tool board and now wouldnt

I'm not sure what you mean with this. Using a toolboard for the spool motor would be possible yes, but seems overkill for just a motor. Or I am missing what you're saying.

sorry, what i mean is if I have the actual tool (direct drive extruder motor, heater, Pt100, filament monitor) all connected to a toolboard physically on the tool itself, can I programmatically sync a second bowden extruder to this. This bowden extruder will NOT be connected to the same toolboard, rather just connected to the main board.

Essentially can a 'tool' consist of a toolboard AND other inputs elsewhere?

Of course if I could connect 14 motors to a Duet 2 then I would be laughing

DC, thats what I have got now, which works fine. Is this possible using toolboards on the Duet 3 as one motor would be on the tool board and now wouldnt

I have a question re Duet 3 and tools. I am looking at converting from Duet 2 to Duet 3 on my larger printer so that I can implement a toolchanger on it for multiple tools. The need to change to Duet 3 is that I will run out of motor inputs on Duet 2. [1 for x, 2 for y, 3 for z and then each tool needs 2 and I want more than 2 tools if I do this]. However each tool has a direct drive motor on the toolhead and a bowden style motor close to the spools. These are physically 1.5 ish metres apart. The idea of the toolboard makes sense for wiring but to then have to have 4 wires going back from each toolboard (direct drive motor) to the bowden motor defeats the point. Is it possible to map the motors to a single 'tool' even though one would be on a toolboard and another on something else (direct into the main board)?

Hopefully this makes sense

Cheers

Matt

aha, it seems the macros were causing the issue, all fixed

OK, I have fixed the temperatures not showing. It seems a couple of typos on my behalf

Sorry for the spam! It just looked clearer to me

Many thanks

1/29/2021, 6:59:04 AM M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Error: Unknown sensor type name "max31865"
Warning: Sensor number 1 has not been defined
Error: Sensor number out of range
Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 530C
Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 530C
Error: Heater 2 not found
Error: Heater 3 not found
Error: Heater 4 not found
Error: Heater 5 not found
Error: Heater 6 not found
Error: Heater 7 not found

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2 running on Duet WiFi 1.0 or 1.01 + DueX5
Board ID: 08DAM-999TL-MQ4S4-6JKDJ-3SD6K-1QGBZ
Used output buffers: 3 of 24 (12 max)
=== RTOS ===
Static ram: 23460
Dynamic ram: 73716 of which 0 recycled
Never used RAM 14904, free system stack 191 words
Tasks: NETWORK(ready,175) HEAT(blocked,323) DUEX(blocked,35) MAIN(running,548) IDLE(ready,19)
Owned mutexes:
=== Platform ===
Last reset 00:01:27 ago, cause: software
Last software reset at 2021-01-29 06:57, reason: User, GCodes spinning, available RAM 14904, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 17.7, current 18.2, max 19.0
Supply voltage: min 24.3, current 24.4, max 24.6, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: position 0, standstill, SG min/max not available
Driver 1: position 0, standstill, SG min/max not available
Driver 2: position 0, standstill, SG min/max not available
Driver 3: position 0, standstill, SG min/max not available
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0, standstill, SG min/max not available
Driver 6: position 0, standstill, SG min/max not available
Driver 7: position 0, standstill, SG min/max not available
Driver 8: position 0, standstill, SG min/max not available
Driver 9: position 0, standstill, SG min/max not available
Driver 10: position 0
Driver 11: position 0
Date/time: 2021-01-29 06:58:33
Cache data hit count 107583709
Slowest loop: 11.37ms; fastest: 0.20ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 3.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 288.93ms; fastest: 0.00ms
Responder states: HTTP(2) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8

• WiFi -
  Network state is active
  WiFi module is connected to access point
  Failed messages: pending 0, notready 0, noresp 0
  WiFi firmware version 1.25
  WiFi MAC address 5c:cf:7f:2c:27:7e
  WiFi Vcc 3.37, reset reason Turned on by main processor
  WiFi flash size 4194304, free heap 24640
  WiFi IP address 192.168.86.66
  WiFi signal strength -55dBm, mode 802.11n, reconnections 0, sleep mode modem
  Clock register 00002002
  Socket states: 0 0 0 0 0 0 0 0
  === DueX ===
  Read count 1, 0.68 reads/min

; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool on Mon Jan 01 2018 19:47:24 GMT+0000 (GMT Standard Time)
G90 ; relative positioning
G1 Z5 F6000 ; lift Z relative to current position
G90 ; absolute positioning
G1 X40 Y40 F6000 ; go to first probe point
G30 ; home Z by probing the bed

; Uncomment the following lines to lift Z after probing
G91 ; relative positioning
G1 Z5 F100 ; lift Z relative to current position
G90 ; absolute positioning

; homey.g
; called to home the Y axis

G91 ; use relative positioning

G1 H2 X0.5 Y-0.5 F10000 ; energise

M400 ; make sure everything has stopped before we make changes

M913 X75 Y75 ; drop motor currents to 75%
M915 H200 X Y S7 R0 F0 ; set X and Y to sensitivity 7, do nothing when stall, unfiltered

G1 H2 Z3 F5000 ; lift Z 3mm
G1 H1 Y1 F2000 ; move away from end
G1 H1 Y-500 F3000 ; move to the front 400mm, stopping at the endstop
G1 H1 Y2 F2000 ; move away from end
G1 H2 Z-3 F1200 ; lower Z
G90 ; back to absolute positioning

M400 ; make sure everything has stopped before we reset the motor currents
G4 P100 ; wait 400ms
M913 X100 Y100 ; motor currents back to 100%

M574 X1 S0 ; Define active low and unused microswitches
M915 H200 X Y S3 R3 F0 ; set X and Y to sensitivity 3, Rehome when stall, unfiltered

I didn't use the tool directly, as I could work out how to get 2 motors on the extruder and 3 on the z etc. But I made a basic setup and copied the changes.

; homex.g
; called to home the X axis

G91 ; use relative positioning
G1 H2 X0.5 Y-0.5 F10000 ; energise
M400 ; make sure everything has stopped before we make changes
G4 P100 ; wait 400ms

;M913 X25 Y25 ; drop motor currents to 50%
M915 H200 X Y S10 R0 F0 ; set X and Y to sensitivity 10, do nothing when stall, unfiltered

G1 H2 Z3 F5000 ; lift Z 3mm
G1 H1 X1 F3000 ; move right 1mm, stopping at the endstop
G4 P100 ; wait 100ms
G1 H1 X-500 F3000 ; move left 400mm, stopping at the endstop
G1 H1 X2 F2000 ; move away from end
G1 H2 Z-3 F1200 ; lower Z
G90 ; back to absolute positioning

M400 ; make sure everything has stopped before we reset the motor currents
G4 P100 ; wait 400ms
;M913 X100 Y100 ; motor currents back to 100%
M574 X1 S0 ; Define active low and unused microswitches

Hi, I have just upgraded from RRF2 to 3.2 (via 3.0). I have modified my config.g, but am getting some strange errors which must be my mistakes/misunderstandings.

Firstly I am getting an error when I home the x and y axis (not tried z yet), where it tells me 'endstop type 0 is not longer supported, use type 1 and invert'. However I dont think I am using type 0? I am using sensorless homing, which worked fine previously

I also get am getting wierd errors on the temps for both the bed and the nozzle where they have clearly defaulted to 2000 degrees.

Lastly, when I startup the printer the paneldue gives 'bad command 00' and then displays 'heater 2 not found' 'heater 3 not found' and so on.

yes there are 2 motors on y, 2 extruder motors, and 3 z motors

Any help would be most appreciated

Many thanks
code below

; General Preferences
M111 S0 ; Debugging off
G21 ; Work in millimetres
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves
M555 P2 ; Set firmware compatibility to look like Marlin
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; Configure automatic saving on power loss
M564 H0 ; Allow movements before homing
M575 P1 S1 B57600 ; enable support for PanelDue

; Network
M550 P"CTR 3DPrintR" ; Set machine name
M552 S1 ; Enable network
;*** Access point is configured manually via M587
M586 P0 S1 ; Enable HTTP
M586 P1 S0 ; Disable FTP
M586 P2 S0 ; Disable Telnet

; Drives
M569 P0 S1 ; Drive 0 goes forwards, X Axis
M569 P3 S1 ; Drive 3 goes forwards, E0
M569 P4 S1 ; Drive 4 goes backwards, E1
M569 P5 S1 ; Drive 5 goes forwards, Y Axis
M569 P6 S1 ; Drive 6 goes forwards, Y Axis
M569 P7 S1 ; Drive 7 goes forwards, Z Axis
M569 P8 S1 ; Drive 8 goes forwards, Z Axis
M569 P9 S1 ; Drive 9 goes forwards, Z Axis
M584 X0 Y5:6 Z7:8:9 E3:4 ; New drive mapping
M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
M92 X320 Y320 Z1600 E880:745 ; Set steps per mm
M566 X500 Y500 Z12 E120 ; Set maximum instantaneous speed changes (mm/min)
M203 X30000 Y30000 Z150 E5000 ; Set maximum speeds (mm/min)
M201 X750 Y750 Z250 E3000 ; Set accelerations (mm/s^2)
M906 X1000 Y1500 Z1500 E1500:500 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

;Axis Limits
M208 X0 Y0 Z0 S1 ; Set axis minima
M208 X490 Y495 Z400 S0 ; Set axis maxima

; Endstops
M574 X1 S3 ; Set Stall endstops X
M574 Y1 S4 ; Set Stall endstops Y
M574 Z1 S2 ; Set endstops controlled by probe
M915 H200 X Y S3 R3 F0 ; Configure Stall Endstops, set X and Y to sensitivity 3, Rehome when stall, unfiltered

;Z-Probe
M558 P1 C"zprobe.in" H5 F120 T6000 ; Set Z probe type to unmodulated and the dive height + speeds
G31 P500 X-55 Y60 Z3.32 ; Set Z probe trigger value, offset and trigger height, Positive Value of Z moves the head closer to the bed
M557 X20:410 Y80:430 S50 ; Define mesh grid

;Mechanical Setup
M671 X-85:620:620 Y300:60:500 S5 ; Ballscrews at centre left, front right and rear right

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B3950 C0 R4700 ; Set thermistor + ADC parameters for heater 0
M950 H0 C"bedheat" T0 ; Create bed heater output on bedhaeat and map it to sensor 0
M307 H0 B0 S1.00 ; Disable Bang Bang mode for the bed heater and set PWM limit
M140 H0 ; Map heatbed to heater 0
M143 H0 S120 ; Set temperature limit for heater 0 to 120C

M308 S0 P"spi.cs1" Y"max31865" F50 ; Set thermistor + ADC parameters for heater 1 and remap it to channel 200
M950 H1 C"e0heat" T1 ; Create nozzle 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
M143 H1 S280 ; Set temperature limit for heater 1 to 280C

; Fans
M950 F0 C"fan0" Q500 ; Create fan0 on pin 0 and set its frequency
M106 P0 S0 H-1 ; Set fan0 value. Thermostatic control is off
M950 F1 C"fan1" Q500 ; Create fan1 on pin 0 and set its frequency
M106 P1 T20:40 H100:101:102 I1 F25000 ; Set fan0 value. Thermostatic control is on at 45 degrees. Case Cooling Fan

; Tools
M563 P0 D0:1 H1 ; Define tool 0
G10 P0 X0 Y0 Z0 ; Set tool 0 axis offsets, Positive Value of Z moves the head closer to the bed
G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C
M307 H1 A505.7 C412.1 D3.9 S1.00 V24.2 B0
M567 P0 E1:1

; Magnetic Filament Sensor
;M591 D0 P4 C3 S1 R0:300 L25.0 E20 ;Duet3D rotating magnet sensor for extruder drive 0, connected to E0 endstop input, enabled, sensitivity 25.0mm.rev, 70% to 300% tolerance, 30mm detection length

M501

I thought that might be the case, I was hopefully there was a setting to invert the logic. Thanks for confirming though