Thanks, I did manage to do it manually but that means being there at the right time. Seems like an obvious thing to add to the slicer programs.

It may sound strange but after almost 2 years I have never tried to print 2 colours. I am using a delta with a duet and Simplify3d for slicer, I want to pause the print at 2mm and change the filament. I would have thought the slicer would have this option but I cannot find it if it does and looking on S3D forums it seems they are putting code in the additional code section like:

[[language]]
{REPLACE "; layer" "M117 Layer"}
{REPLACE " Z = " " Z="}
{REPLACE "\nM117 Layer 4, Z=" "\nG1 X10 Y5\nM0\nM117 Layer 4, Z="}

Which seems a complicated way to just pause the printer as when I pause the print manually the head automatically moves up and out of the way.

Thanks, I will have to have another go at it I guess, They were both well out of position so I guess the best thing to do is get them as close to perpendicular to the board as possible and both as close to 45% as possible and get it probing level if not at the right height then adjust the outer LED to get the height withing tolerance. Hopefully I can get it working or I will have to buy another which isn't a problem except you are out of stock currently.

Ok got it all working, thanks for the help. Now I have another problem, seems I must have knocked or otherwise moved both of the LED's on my IR Probe while I was upgrading and it is way out now. I tried moving them back to a position that looked more or less even and level which improved it somewhat and I managed to get it triggering at the centre position at a decent height (1.18mm) but something is still wrong, it triggers fine in the centre but as it is going round on the calibration it is triggering very high in some places and hitting the bed in others. Is there something I can do to get the led's repositioned properly?

Ah I see, thanks again.

Thanks DC42, on that page what voltage do I need to select, there is the option of 3.3v and 5v?

@dc42:

To use a PT100 with a Duet 085 you need a third-party PT100 interface board based on the MAX31865 chip. They are available on eBay. See https://duet3d.com/wiki/Connecting_PT100_temperature_sensors#Duet_0.6_or_0.8.5. You don't need the amplifier.

Regarding which version of the Flex3drive, I suggest you send ask Jason, aka Mutley3D on the forums at reprap.org.

In the link for connecting the PT100 is says "Purchase a third-party MAX31865-based PT100 interface board. The Duet uses 3.3V signalling, so get a board without 5V level shifters. The reference resistor on the board must be 400 ohms."

I have been unable to find a PT100 interface board without the level shifters, the only ones I can find have the level Shifters and a 430ohm reference resistor, it is possible to make these work? This one for instance i

This is still happening almost every print.

[[language]]
14:02:05
M122
=== Diagnostics ===
Used output buffers: 2 of 32 (9 max)
=== Platform ===
Static ram used: 45820
Dynamic ram used: 39916
Recycled dynamic ram: 280
Stack ram used: 1088 current, 4804 maximum
Never used ram: 7484
Last reset 00:08:59 ago, cause: software
Last software reset code 0x7004, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0042f00f, BFAR 0xe000ed38, SP 0xffffffff
Spinning module during software reset: Move, available RAM 5228 bytes (slot 3)
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 21.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 40.1, current 41.9, max 47.7
Date/time: 2017-06-02 14:02:05
Slowest main loop (seconds): 0.006195; fastest: 0.000061
=== Move ===
MaxReps: 0, StepErrors: 0, 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 heater = 0, chamber heater = -1
Heater 0 is on, I-accum = 0.0
Heater 1 is on, I-accum = 0.3
=== 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 idle 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
Code queue is empty.
=== Network ===
Free connections: 15 of 16
Free transactions: 23 of 24
Locked: 1, state: 4, listening: 0x20071b54, 0x0, 0x0
=== Webserver ===
HTTP sessions: 1 of 8
FTP connections: 0, state 0
Telnet connections: 0, state 0

Well the print finished but when I went to upload a new file to print the Duet reset again.

M122
=== Diagnostics ===
Used output buffers: 2 of 32 (30 max)
=== Platform ===
Static ram used: 45820
Dynamic ram used: 39916
Recycled dynamic ram: 280
Stack ram used: 1088 current, 4408 maximum
Never used ram: 7880
Last reset 00:00:17 ago, cause: software
Last software reset code 0x7003, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0042f00f, BFAR 0xe000ed38, SP 0xffffffff
Spinning module during software reset: GCodes, available RAM 4956 bytes (slot 0)
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 21.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 42.8, current 45.3, max 47.7
Date/time: 2017-05-26 21:34:11
Slowest main loop (seconds): 0.018618; fastest: 0.000104
=== Move ===
MaxReps: 0, StepErrors: 0, 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 heater = 0, chamber heater = -1
Heater 1 is on, I-accum = 0.0
=== 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 idle 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
Code queue is empty.
=== Network ===
Free connections: 15 of 16
Free transactions: 23 of 24
Locked: 1, state: 4, listening: 0x20071b54, 0x0, 0x0
=== Webserver ===
HTTP sessions: 1 of 8
FTP connections: 0, state 0
Telnet connections: 0, state 0

Well I have erased and reinstalled using Bossac and so far so good, Hope I don't jinx the print but it is halfway through a 2 hour print and is still going which is more than it has done for a while.