Best posts made by PaulHew

So I made the 8 way cable up, using pins 19 - 26 in a one for one configuration.
Did not work.

Plugged in the original supplied cable, it worked.
Thought it could be my new cable, used patch cables instead, still not working.

Read more, Pin17, patched that in. Now it works!
As per the above post, Duet3's need a 3.3v feed from/to pin 17

So recap, pins required are the following
17, 19, 20, 21, 22, 23, 24, 25 and using two 5x2 DuPont blocks in stead of the 4x2's

I am using using a piece of Cat5e Ethernet cable.

Hope this can help others.

Regards,

Paul.

Sure there is a way, which will require someone more knowledgable than me to assist!

But in the meantime .......

Click the 'Extra'

Regards,

Paul

Before my last upgrades, these configs are for Ender3 Pro which has a Bullseye duct and its BL Touch Mount, I am also running a Maestro board in my printer and using a PanelDue touch screen. All original hardware.

0_1556009924222_config.g
0_1556009972883_bed.g
0_1556009989340_deployprobe.g
0_1556009998929_homeall.g
0_1556010027421_homex.g
0_1556010036914_homey.g
0_1556010048946_homez.g
0_1556010058346_retractprobe.g

Hope these help!
P.

Update....
I took the time last night to remove the Mini 5 from my printer so I can send to Tony. Thanks @T3P3Tony
Whilst at it I checked the fan cabling and found a melt spot on one of the cables. There was also a mark on the brass where i realize now it had shorted, me being inquisitive wiped it to see what it was!

As per the LDO part number and spec sheet which is above in this thread, 800ma is way too much for this little motor, even though they say it is rated for 1amp
The motor was that hot it burnt my fingers when checking the issue, in turn had heated the brass standoffs which then melted the sheath of the fan cable that was resting on the brass. (The whole lot is in a chamber)
Also you can see the heat shrink has been shrunk by the extreme heat. I put them on loose!

All the printers I have built and used the 80% rule, i have never had this.

However lesson learnt, replace chinese cable with silicone or use a protective braid.

For those who think I did not RTFM, I did and always do! Hence how I got into this mess!

I have a room temp sensor and a secondary bed sensor purely for feedback.

In RRF3 I use

M308 S7 P"exp.thermistor7" Y"thermistor" A"RoomTemp" T100000 B3950 R4700

Then I have to go to the 'Extra' page to view.

HTH

Paul.

@steve-lynch Here are all my files for my RailCore, running a Duet3 Mini and 1LC toolboard.
sinned helped me as I was having an issue also.
download.zip.txt
Hope they help you.

I am in the uk and bought a pack each of 5 of the 2 and 3 pins with tails from here
https://www.ebay.co.uk/itm/JST-ZH-1-5-Male-lead-2-Pin-3-Pin-4-Pin-5-Pin-6-Pin-plug-eg-Spektrum-small/331897443004?var=541393872086

HTH

Paul

Here is my config for BLTouch - Duet2 with Duex5

config.g

; Z probe and compensation definition
M558 P9 C"^zprobe.in" H5 R1 F120 T6000 A5 S0.02  ;BLTouch connected to Z probe IN pin
M950 S0 C"duex.pwm1"				             ;BLTouch Servo (S0) on duet pwm1
G31 X2 Y42 Z1.438 P25                            ; Customize your offsets appropriately - do a paper test, and put the probed value in the Z value here
M557 X30:280 Y30:280 S20

Your M950 and M558 are the wrong way round, I made the same mistake!
I am sure the guide is wrong!

HTH

Paul

 10/04/2021, 18:06:12 	Error: VSSA fault, check thermistor wiring
10/04/2021, 18:06:08 	Error: VSSA fault, check thermistor wiring
10/04/2021, 18:06:03 	Error: VSSA fault, check thermistor wiring
10/04/2021, 18:05:59 	Error: VSSA fault, check thermistor wiring
10/04/2021, 18:05:56 	m122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.3beta2+1 (2021-04-09 14:40:21) running on Duet 3 Mini5plus Ethernet (SBC mode)
Board ID: A45XG-F396U-D65J0-40KML-1F03Z-H03XP
Used output buffers: 5 of 40 (36 max)
=== RTOS ===
Static ram: 100072
Dynamic ram: 92364 of which 0 recycled
Never used RAM 48412, free system stack 112 words
Tasks: Linux(resourceWait,119) HEAT(delaying,198) CanReceiv(notifyWait,774) CanSender(notifyWait,363) CanClock(delaying,340) TMC(notifyWait,99) MAIN(running,312) IDLE(ready,20) AIN(notifyWait,259)
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 07:09:53 ago, cause: software
Last software reset at 2021-04-10 00:26, reason: User, none spinning, available RAM 48444, slot 2
Software reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task Linu Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Aux1 errors 0,0,0
MCU revision 3, ADC conversions started 30627993, completed 30627992, timed out 0, errs 5
tnd=0 rnd=0 wrs=0 wrx=5 war=5
Supply voltage: min 0.0, current 35.9, max 35.9, under voltage events: 1, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/1130/1130, gc cycles 0
Driver 0: position 64902, standstill, SG min/max 0/510, read errors 0, write errors 1, ifcnt 62, reads 265, writes 41, timeouts 6924, DMA errors 0, failedOp 0x6a
Driver 1: position -15887, standstill, SG min/max 0/510, read errors 0, write errors 1, ifcnt 62, reads 6828, writes 41, timeouts 361, DMA errors 0, failedOp 0x6f
Driver 2: position 328, standstill, SG min/max 0/242, read errors 0, write errors 1, ifcnt 76, reads 5597, writes 47, timeouts 1586, DMA errors 0, failedOp 0x72
Driver 3: position 0, standstill, SG min/max 0/270, read errors 0, write errors 1, ifcnt 76, reads 6731, writes 47, timeouts 450, DMA errors 0, failedOp 0x41
Driver 4: position 0, standstill, SG min/max 0/274, read errors 0, write errors 1, ifcnt 76, reads 7183, writes 47, timeouts 0, DMA errors 0
Driver 5: position 0, assumed not present
Driver 6: position 0, assumed not present
Date/time: 2021-04-10 18:05:56
Cache data hit count 4294967295
Slowest loop: 1000.25ms; fastest: 0.08ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 0.0MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 14959696ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 1805, completed moves 1805, hiccups 0, stepErrors 0, LaErrors 0, Underruns [6, 0, 8], 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, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP* is doing "M122" 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
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== CAN ===
Messages queued 248388, send timeouts 0, received 309852, lost 0, longest wait 2ms for reply type 6049, peak Tx sync delay 380, free buffers 17 (min 16)
=== SBC interface ===
State: 4, failed transfers: 0
Last transfer: 4ms ago
RX/TX seq numbers: 9831/9831
SPI underruns 0, overruns 0
Number of disconnects: 0, IAP RAM available 0x118a8
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.2.2
Code buffer space: 4096
Configured SPI speed: 8000000 Hz
Full transfers per second: 35.96
Maximum length of RX/TX data transfers: 3628/1248
10/04/2021, 18:05:54 	Error: VSSA fault, check thermistor wiring
10/04/2021, 18:05:50 	Error: VSSA fault, check thermistor wiring

Nothing important.....
Hope this helps @dc42

Thanks Tony.
Issue was, I forgot to put my silicone sock back on to the heater block Doh!

First big print and getting used to the new printer and using Prusa Slicer instead of Cura

The duct and fan for part cooling is tooo good!
Never had these problems on my Ender3 !!! LOL

Thank you and sorry.

P.

@chrishamm
Found this this morning.

'Turn Everything Off' does not do anything.

FIRMWARE_NAME: RepRapFirmware for Duet 2 Maestro FIRMWARE_VERSION: 3.0 ELECTRONICS: Duet Maestro 1.0 FIRMWARE_DATE: 2020-01-03b3

No disrespect @Phaedrux, because he is using S0 and S1with his M208, it is correct....but...

A neater way of setting your maxima and minima is like this

M208 X0:500 Y0:500 Z0:500

It makes it easier to read and diagnose.

Also your M667 I think is incorrect. Your printer is a Cartesian, not Core XY
Remove M667, Use M669 K0, if you are using RRF2.03 or later, this is the new command and K0 defines your printer as a Cartesian.

Also, you say that your 'Hotend' does not display. Are you talking about the cooling fan?

Also as mentioned you need a Z Probe like a BL Touch to do levelling.
If you buy a BL Touch, get an original not a clone, tooo many problems with clones.

As we have both mentioned, read the Ender3 documentation, it will help get the base correct. It is not easy upgrading to a new board and it is a steep learning curve, but a fun one.

HTH. Paul.

@grabercars said in No heaters showing up in the WebUI and other possible issues:

M140 H-1 ; Disable heated bed

Try commenting out this line, save and reboot and see if it gives you a reading in DWC

AH!
Had to pull the SD card as I first created it in the 'System Folder' which did not work using DWC.

Works now, thanks @Phaedrux

What is the filament section for as I do not understand its function.

Paul.

Like most people I use different filaments and have been a bit lazy and not used the filament function to its full potential.
This morning I realised I was over extruding, same brand ABS+ just a different colour.
Calculated my E-Steps, 413 as opposed to 425.
Created a new filament 'Black ABS+', edited the config.g and added m92 E413, saved.
M92 in console, E was 425
In DWC clicked the filament, changed to Black ABS+, M92 in console E was 413, Result!
Changed back to PETG, M92 = E425

Lets do this using M701. FAIL!
My command - m701 s"Black ABS+" did not error BUT my E steps were still 425 as opposed to 413. DWC reported the correct filament.

So the question is, why when I manually change filament in DWC it loads the customised config.g but when I load it from a command line it ignores my custom config.g.
Have I missed something or is it something else?

TIA
Paul.

FYI I think the start code Veti is referring to is in your slicer.
If it is Cura.
Settings - Printers - manage printers
Select your printer and click 'Machine Settings'

On that page at the bottom there is a window with Start G-Code

Remove the lines you have been asked to remove.
M201 X500.00 Y500.00 Z100.00 E5000.00 ;Setup machine max acceleration
M203 X500.00 Y500.00 Z10.00 E50.00 ;Setup machine max feedrate
M204 P500.00 R1000.00 T500.00 ;Setup Print/Retract/Travel acceleration
M205 X8.00 Y8.00 Z0.40 E5.00 ;Setup Jerk

HTH
Paul.

Newer versions of the BL Touch do not need resistors or links cut.
Just wire as per the diagrams and make sure your settings are right in your config.g

What board and revision of firmware are you running?

This document IMO is better.
https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe

HTH.

Paul

@DIY-O-Sphere You are right, Just swapped the lines round in my config.g and it worked.

That came out of the config tool that way round.

Thank you. I thought I was going mad.

Makes sense now when I run my macro, 558 effectively was the last command so when 950 runs from my macro it sorts it out.

Thank you again.

@dc42 and @Veti
Apologies guys, that is why I thought the GCode wiki was wrong, as that how it came out of the config tool.

Paul.

I think I have found another issue. @chrishamm
Yesterday when I had finished printing, I unloaded the filament using DWC.
I did this as I remembered last year when I was new to Duet boards, it would not print as there was no filament loaded, according to DWC. So I was guided how to create and load a filament.
So this afternoon, I sent a new print to my Railcore and it started printing. Not long after I thought, 'Is DWC reporting it has filament?'
No, its asking 'Load Filament'
Screenshot

As you can see it is printing with no filament loaded with the incorrect M92 E steps as it does not load the custom config.g relevant to the filament.

If you need more info, please do not hesitate to ask.

Regards,
Paul

@TheBasedDoge
Z-Probe

My CoreXY config for reference

M558 P9 C"^zprobe.in" H5 R1 F120 T6000 A5 S0.02  ;BLTouch connected to Z probe IN pin
M950 S0 C"duex.pwm1"				             ;BLTouch Servo (S0) on duet pwm1
G31 X2 Y42 Z1.605 P25                            ; Customize your offsets appropriately - do a paper test, and put the probed value in the Z value here
M557 X30:280 Y30:280 S20

I have edited yours, try this.

; Z-Probe
M558 P9 C"^zprobe.in" H5 F120 T6000   A5 S0.02       ; set Z probe type to bltouch and the dive height
M950 S0 C"exp.heater7"                                 ; create servo pin 0 for BLTouchG31 P500 X20 Y5 Z2.5                                   ; set Z probe trigger value, offset and trigger height
M557 X15:300 Y15:300 S20                               ; define mesh grid