@dc42 They are 1K resistors, yes. It's a common colour code, but I checked it via the Anmeter anyways.

Ok, I shall see what I can do to replace the PT100. Thank you very much!

Hello once again to readers!

I've run a mesh grid heightmap on a small portion of my "fake bed" (which is a flat block of MDF), and I seem to get a result that is super high from the axis. I don''t entirely know whether this is a G-Code problem, or a BLTouch positioning problem. Is this able to be fixed at all, like offsetting, or would I need to physically adjust something?

Completely forgot to uncomment Tool 0. Tool 0 is back on the Web Server.

@dc42 Hello there!

• The 2-wire connections already have jumpers in place (soldered)
• Unfortunately, I don't think I've been supplied a 100Ω resistor with my sensor. We may have been, but my colleague who has assembled it may have placed it somewhere, and I don't know where it is. All we have supplied are two 1kΩ resistors. I'll try to see what I can do to source/find this 100Ω resistor, then perform the suggestion you have given.
• Putting the second daughter board onto the Duex5 resulted to channels X200-X201 to still work, but X202-X207 to no longer work (all reads 2000ºC). All 10 pins are soldered, from what I can see on the other PT100 on the Duex. On the other hand, swapping the PT100 boards from the Duex5 to the main board, and vice versa, resulted to X200, X204 and X205 to work, somehow.

From my configuration:

• X200 = Heater 4
• X201 = Unknown (Which it should technically be Heater 1)
• X204 = Heater 2
• X205 = Heater 3

On my Duet's LCD Screen, I can see that Heater 1 is also on 2000ºC, meaning that the thermistor is not found on that channel. I have checked the wiring of the PT100, and they are all fine. I believe that there may be a wiring fault on the heater end, but I cannot touch that until my colleague comes back in over a week's time.

At least another thing is that the working heaters are able to function along with the correct extruder motors, which are all assigned on Tool 0 to 3 anyways. I guess Tool 0 will also work once Heater 1's channel also works.

@deckingman Hello there!

I've now done some of your suggestions. Here is what I found:

• Commenting/Removing the T and B parameters made the sensors read at 2000ºC, so I needed to keep it afterwards
• R4700 didn't do anything from what I've seen
• Commenting/Removing M303 also did nothing from what I do, so I kept it commented afterwards
• From before, I had Tool 1 assigned to Heater 1, and so on, up until Tool 4 with Heater 4. Now, from the suggestions you've made, Tools 1-3 are now associated with Heaters 2-4, and are having the correct readings, leaving me with Tool 0 and Heater 1. Tools 1-3 are visible on the Web Server, whereas Tool 0 doesn't exist on there. Adding it manually through the Tools tab, associating Drive 0 with Heater 1, just creates a new tool with 2000ºC, which I think means it's not working - At least we're already 75% of the way there, excluding the bed!

Also thank you for pointing out that Tool 2 mistype. I completely missed that.
Same with the Tool 4 shenanigans.

I do agree with you that I should define the tools from T0 to T3, instead of T1 to T4. I only did the T1 to T4 because I wanted the numbers to match, initially, so I know that they belong to each other, but I've gotten used to it now where 0 = 1, etc.

Now time to check dc42's suggestions.

@deckingman Thank you for giving me suggestions.

I'm currently not working on the 3D Printer until thursday, but I'll try to respond to what I can on your previous message.

I use the PT100s for 4 hot end heaters, yes, but the bed doesn't exist yet, so there's no thermistor installed regarding that.

Anyways, I see! I understand that X200-X203 are for the PT100. I do have a Duex5 board with it, but I was unclear on what the X204-X207 channels were.

I'll hopefully respond back on thursday for updates on your suggestion. Thank you very much!

Hello to whoever reads this!

I've currently managed to setup my Duet to self calibrate itself pre/post-printing, but now, I'm working on aligning the extruders and heaters at the tools list. I've had a browse online but I've only got bits of information that were useful to me.

My setup is a CoreXY Printer, with 4 Z-Axis via 4 leadscrews on all corners, along with 4 separate extruders and 4 heaters/nozzles, for whoever may be reading that has a similar build.

I'm using a double-stacked PT100 Thermal Sensor, and, from what I have obtained online, they use the channels X200 to X207.

My problem is that I cannot get Heater 1 to work (shows 2000ºC). 2, 3 and 4 are currently assigned to X200, X201 and X202, leaving me with 203-207 for Heater 1. I have tried using trial-and-error with X203 to X207, yet the sensor still detects 2000ºC. Heaters 2, 3 and 4 are working, along with their desired temperature values. May I have some help on how I may be able to solve this on the software side? Still unfortunately very new to this.

Here are sections of my config.g for how my tools are configured. The Bed isn't configured as of yet.

M569 P0 S1 ; Drive 0 goes forwards - X Motor
M569 P1 S1 ; Drive 1 goes forwards - Y Motor
M569 P2 S1 ; Drive 2 goes forwards - Z4 Motor
M569 P3 S1 ; Drive 3 goes forwards - E0
M569 P4 S1 ; Drive 4 goes forwards - E1
M569 P5 S1 ; Drive 5 goes forwards - E2
M569 P6 S1 ; Drive 6 goes forwards - E3
M569 P7 S1 ; Drive 7 goes forwards - Z3 Motor
M569 P8 S1 ; Drive 8 goes forwards - Z2 Motor
M569 P9 S1 ; Drive 9 goes forwards - Z1 Motor
M584 X0 Y1 Z2:7:8:9 U9 V8 W7 A2 E3:4:5:6 P10 ; Driver 0 For X, 1 for Y, Z=2:7:8:9 A=2 U=7 V=8 W=9, Extruder 3-6

; Heaters
M305 P0 T100000 B4138 X0 ;R4700 ; Set thermistor + ADC parameters for heater 0
M143 H0 S120 ; Set temperature limit for heater 0 to 120C
M303 H0 S120
M305 P1 T100000 B4138 X203 ;R4700 ; Set thermistor + ADC parameters for heater 1
M143 H1 S280 ; Set temperature limit for heater 1 to 280C
M303 H1 S280
M305 P2 T100000 B4138 X200 ;R4700 ; Set thermistor + ADC parameters for heater 2
M143 H2 S280 ; Set temperature limit for heater 2 to 280C
M303 H2 S280
M305 P3 T100000 B4138 X201 ;R4700 ; Set thermistor + ADC parameters for heater 3
M143 H3 S280 ; Set temperature limit for heater 3 to 280C
M303 H3 S280
M305 P4 T100000 B4138 X202 ;R4700 ; Set thermistor + ADC parameters for heater 4
M143 H4 S280 ; Set temperature limit for heater 4 to 280C
M303 H4 S280

; Tools
;M563 P0 D0 H0 F0 ; Define tool 0 ; Commented because I thought that Tool 0 would be assigned to the Bed, since the bed is Heater 0
;G10 P0 X10 Y10 Z0 ; Set tool 0 axis offsets
;G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C
M563 P1 D1 H1 F0 ; Define tool 1
G10 P1 X-10 Y10 Z0 ; Set tool 1 axis offsets
G10 P1 R0 S0 ; Set initial tool 1 active and standby temperatures to 0C
M563 P2 D2 H2 F0 ; Define tool 2
G10 P2 X10 Y-10 Z0 ; Set tool 2 axis offsets
G10 P21 R0 S0 ; Set initial tool 2 active and standby temperatures to 0C
M563 P3 D3 H3 F0 ; Define tool 3
G10 P3 X-10 Y-10 Z0 ; Set tool 3 axis offsets
G10 P3 R0 S0 ; Set initial tool 3 active and standby temperatures to 0C
M563 P4 D0 H4 F0 ; Define tool 4
G10 P0 X10 Y-10 Z0 ; Set tool 4 axis offsets
G10 P0 R0 S0 ; Set initial tool 4 active and standby temperatures to 0C

Thank you for your reply! I completely forgot to re-name the file inside the sys file for the WiFi Server, previously, so it never managed to install it at all.

I have reset the board once more and performed the M997 S0:1:2 for the complete reinstall.

I'm currently trying to load the web server, but it's taking a long while to load up. Once it's fully loaded up, I'll have a check on its connection reliability, so you're also up-to-date with the information. I hope this does

Is it normal for the Duet Web Server to take ages to load upon first boot? Everytime I do M552 S0 and S1 now, it times out while trying to connect, unless I've done S1 twice.

[EDIT]

Ok, I found out why my web server was taking ages... It was because my phone was updating apps in the background, hindering the local tether bandwidth. I've disabled it now, and the web server loaded instantly - so at least that's sorted.

[EDIT 2]

So far, no disconnections have happened. It's been connected for nearly 10 minutes now, which broke it's old record of an uptime of 30 seconds, so good news as of now. I will create an Edit 3 once I have further analysis.

[EDIT 3]

It's been connected for over 30 minutes now! That's done the charm! Now it's time to sort out the configs for the printer, then I will work out on how to connect it to our office WiFi.

@dc42 Here is what comes up with M122

=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.01(RTOS) running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DDM-9FAM2-LW4S8-6JTDD-3SD6J-93YHX
Used output buffers: 1 of 20 (3 max)
=== RTOS ===
Static ram: 28476
Dynamic ram: 97128 of which 16 recycled
Exception stack ram used: 272
Never used ram: 5180
Tasks: NETWORK(ready,1276) HEAT(blocked,1248) MAIN(running,3484)
Owned mutexes:
=== Platform ===
Last reset 00:02:54 ago, cause: reset button or watchdog
Last software reset at 2018-09-07 15:05, reason: User, spinning module GCodes, available RAM 4940 bytes (slot 2)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00417000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 33.0, current 38.4, max 38.4
Supply voltage: min 0.4, current 0.7, max 0.8, under voltage events: 0, over voltage events: 0
Driver 0: ok, SG min/max not available
Driver 1: ok, SG min/max not available
Driver 2: ok, SG min/max not available
Driver 3: ok, SG min/max not available
Driver 4: ok, SG min/max not available
Driver 5: ok, SG min/max not available
Driver 6: ok, SG min/max not available
Driver 7: ok, SG min/max not available
Driver 8: ok, SG min/max not available
Driver 9: ok, SG min/max not available
Expansion motor(s) stall indication: no
Date/time: 1970-01-01 00:00:00
Slowest loop: 43.89ms; fastest: 0.06ms
=== Move ===
Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 240, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 0, completed moves: 0
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Stack records: 1 allocated, 0 in use
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
serial is ready with "M122" in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 14.22ms; fastest: 0.01ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 0 of 8

• WiFi -
  Network state is running
  WiFi module is connected to access point
  Failed messages: pending 0, notready 0, noresp 0
  WiFi firmware version 1.21
  WiFi MAC address 5c:cf:7f:a4:a5:be
  WiFi Vcc 3.35, reset reason Turned on by main processor
  WiFi flash size 4194304, free heap 17032
  WiFi IP address 192.168.1.134
  WiFi signal strength -67dBm, reconnections 0, sleep mode modem
  Socket states: 0 0 0 0 0 0 0 0
  === Expansion ===
  DueX I2C errors 0

Ok. I shall find out what the full M122 says. Thank you for the reply!

=== Diagnostics ===
Used output buffers: 1 of 32 (3 max)
=== Platform ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 1.21 running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DDM-9FAM2-LW4S8-6JTDD-3SD6J-93YHX
Static ram used: 16152
Dynamic ram used: 101400
Recycled dynamic ram: 1232
Stack ram used: 3576 current, 4420 maximum
Never used ram: 7868
Last reset 00:00:11 ago, cause: power up
Last software reset at 2018-09-03 17:47, reason: User, spinning module GCodes, available RAM 7484 bytes (slot 1)
Software reset code 0x0003 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x00433000, BFAR 0xe000ed38, SP 0xffffffff
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 29.3, current 32.7, max 32.8
Supply voltage: min 0.1, current 0.7, max 0.8, under voltage events: 0, over voltage events: 0
Driver 0: ok, SG min/max not available
Driver 1: ok, SG min/max not available
Driver 2: ok, SG min/max not
<Warning: Maximal number of bytes per line exceeded! Check the end-of-line settings or increase the limit in the advanced terminal settings.>

I just separated the <LF>s manually so you can see it more clearly, but that's all that the lines give me. I notice it saying DuetWiFi 1.02, but I really don't recall even touching that version on the downloads list. Does that mean that I've forgotten a file and it didn't install when I did M997 S0:1:2?