Posts made by RodF

Thanks again. Happily printing now.

Decided I had nothing to lose and redid the configuration with the RRF configuration tool. This has sorted out all my problems. Thanks for your time David.

Thanks for the input guys. The end stops are 3 wire Makerbot. I am also getting an error on the bed heater.
Error: Temperature reading fault on heater 0: unknown temperature sensor channel
M574 reports Endstop configuration: X:low end unknown type Y: low end unknown type Z: none,

Also getting an error message when connecting on WiFi "Can't open 0:/sys/oem.json to read, error code 4"

I should of said end stops still not stopping X and Y axis and z still getting Insufficient axes homed for bed probing error

The end stops are mechanical except for the IR probe on Z. I have upgraded to 1.2. Now the end stops in Machine properties are hitting but the Z probe has stopped hitting however the red LED on the IR probe is still activating at the right distance from the bed.

Awesome response as usual David. Will do the 1.2 upgrade. In the meantime here is config .g.

; Configuration file for Duet WiFi (firmware version 1.16)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool on Sat Dec 17 2016 11:00:47 GMT+1300 (New Zealand Standard Time)

; 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

M667 S1 ; Select CoreXY mode
M208 X0 Y0 Z0 S1 ; Set axis minima
M208 X300 Y300 Z350 S0 ; Set axis maxima

; Endstops
M574 X1 Y1 Z0 S0 ; Define active low and unused microswitches
M558 P1 X0 Y0 Z1 H5 F120 T6000 ; Set Z probe type to unmodulated, the axes for which it is used and the probe + travel speeds
G31 P500 X0 Y0 z1.76 ; Set Z probe trigger value, offset and trigger height

; Drives
M569 P0 S0 ; Drive 0 goes backwards
M569 P1 S1 ; Drive 1 goes backwards
M569 P2 S1 ; Drive 2 goes forwards
M569 P3 S1 ; Drive 3 goes forwards
M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
M92 X160 Y160 Z3200 E422 ; Set steps per mm
M566 X900 Y900 Z12 E120 ; Set maximum instantaneous speed changes (mm/min)
M203 X6000 Y6000 Z500 E1200 ; Set maximum speeds (mm/min)
M201 X500 Y500 Z250 E250 ; Set accelerations (mm/s^2)
M906 X1700 Y1700 Z1700 E750 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Heaters
M143 S300 ; Set maximum heater temperature to 260C
;M305 P0 T100000 B3950 R4700 ; Set thermistor + ADC parameters for heater 0
M305 P1 X200 ; Set thermistor + ADC parameters for heater 1 and remap it to channel 200

; Tools
M563 P0 D0 H1 ; Define tool 0
G10 P0 X0 Y0 ; Set tool 0 axis offsets
G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C

; Network
M550 PMy printer ; Set machine name
M552 P0.0.0.0 S1 ; Enable network and acquire dynamic address via DHCP
M501

; Fans
M106 P0 S0.3 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 S1 I0 F500 H1 T45 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
M106 P2 S1 I0 F500 H1 T45 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on

; Custom settings are not configured

The end stops are being triggered in Machine properties but not stopping the motors. And I am getting an error message on the IR Z probe "Insufficient axes homed for bed probing". I expect it is my bad, but cannot work it out. I tried changing the ends in M557 but no luck. Here are the home files.

; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool on Sat Dec 17 2016 11:00:47 GMT+1300 (New Zealand Standard Time)

; Relative positioning
G91

; Lift Z
G1 Z5 F6000

; Move towards X and Y axis endstops (first pass)
G1 X-305 Y-305 F1800 S1

; Go back a few mm
G1 X5 Y5 F6000

; Move slowly to axis endstops once more (second pass)
G1 X-305 Y-305 F360 S1

; Absolute positioning
G90

; Go to first bed probe point and home the Z axis
G1 X150 Y135 F6000
G30

; Uncomment the following line to lift the nozzle after probing
;G1 Z5 F100

; homex.g
; called to home the X axis
;
; generated by RepRapFirmware Configuration Tool on Sat Dec 17 2016 11:00:47 GMT+1300 (New Zealand Standard Time)

; Lift Z relative to current position
G91
G1 Z5 F6000
G90

; Move quickly to X axis endstop and stop there (first pass)
G1 X-305 F1800 S1

; Go back a few mm
G91
G1 X5 F6000
G90

; Move slowly to X axis endstop once more (second pass)
G1 X-305 F360 S1

; Lower Z again
G91
G1 Z-5 F6000
G90

; homey.g
; called to home the Y axis
;
; generated by RepRapFirmware Configuration Tool on Sat Dec 17 2016 11:00:47 GMT+1300 (New Zealand Standard Time)

; Lift Z relative to current position
G91
G1 Z5 F6000
G90

; Move quickly to Y axis endstop and stop there (first pass)
G1 Y-305 F1800 S1

; Go back a few mm
G91
G1 Y5 F6000
G90

; Move slowly to X axis endstop once more (second pass)
G1 Y-305 F360 S1

; Lower Z again
G91
G1 Z-5 F6000
G90

; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool on Sat Dec 17 2016 11:00:47 GMT+1300 (New Zealand Standard Time)

; Lift Z relatively to current position
G91
G1 Z5 F6000

; Back to absolute positioning
G90

; Go to first bed probe point and home the Z axis
G1 X20 Y30 F6000
G30

; Uncomment the following lines to lift Z after probing
G91
G1 Z5 F100
G90

I'm running a similar motor on Z axis in my Core XY. It is working fine at 1.8 amps. I did get an external stepper driver in case I needed to go over the 2 amp Duet limit. I'm pretty sure that a Nema 17 would have had enough power for my Z though.

Great thanks dc42 that's done the trick.

Thanks for that dc42. I used M500 and here is my config-override file.

; This is a system-generated file - do not edit
; Heater model parameters
M307 H0 A350.2 C637.4 D6.0 S1.00 B0
M307 H1 A340.0 C140.0 D5.5 S1.00 B0
M307 H2 A340.0 C140.0 D5.5 S1.00 B0
M307 H3 A340.0 C140.0 D5.5 S1.00 B0
M307 H4 A340.0 C140.0 D5.5 S1.00 B0
M307 H5 A340.0 C140.0 D5.5 S1.00 B0
M307 H6 A340.0 C140.0 D5.5 S1.00 B0
M307 H7 A340.0 C140.0 D5.5 S1.00 B0
; Z probe parameters
G31 T1 P500 X0.0 Y0.0 Z2.25
G31 T3 P500 X0.0 Y0.0 Z0.70
G31 T4 P500 X0.0 Y0.0 Z0.00

If I do a M307 H0 I still get the bang-bang values.

M307 H0
Heater 0 model: gain 90.0, time constant 700.0, dead time 10.0, max PWM 1.00, mode: bang-bang

I assume config-override overrides config.g. Is there any way of telling?

I thought I would change the bed heating from bang-bang to PID. It took me a while working through the documentation and the G code wiki to sort out what M code to send. After a couple of false starts I got a result. Actually I got 2 results so I am wondering which one to send with M304.
M307 H0
Heater 0 model: gain 361.6, time constant 647.2, dead time 9.3, max PWM 1.00, mode: PID
Setpoint change: P34.3, I0.053, D223.6
Load change: P34.3, I1.119, D223.6

Warning: Heater 0 appears to be over-powered and a fire risk! If left on at full power, its temperature is predicted to reach 381C.
Auto tune heater 0 with PWM=0.25 completed in 1797 sec, maximum temperature reached 103.5C
Use M307 H0 to see the result

M303 H0 P0.25 S120
Auto tuning heater 0 - do not leave printer unattended

Mine is running fine now and I have a fully functioning machine. I did look at best practice wiring and nearly bought a roll of 4 wire twisted pair shielded cable. I must say the DuetWifi is a huge step up from the Rumba board in my other printer.

Not sure what happened there. Visually checked everything, checked continuity, checked resistance, checked for shorts, no problems.
Removed heater and extruder, PT100 works. Reconnected them and PT100 still works. I had installed firmware 1.17RC3 and DWC 1.14. Oh well moving on.
As usual awesome support dc42.

Well I rewired pretty much the same as Dc42's and after fixing the end stop wiring error (thanks Dc42) got the firmware sorted out. However the PT100 sensor now reads 2000c all the time. So bypassed the wiring bundle and the problem goes away. The only other power going through the loom was E motor so powered down and disconnected it and the problem goes away again. So I will need to do some research on this and get some decent twisted shielded wire and rewire again.

Many thanks Dc42 that was the problem. Firmware is sorted out now. Awesome support thanks.

During the commissioning of my printer I was having trouble with induction spikes in the PT100 temp sensor. Resolved that and rewired. However I have now lost all contact with the printer. It doesn't show up in device manager and cannot connect through Repetier or SAM-BA. The 5v led and usb led light on the board and the blue power led if I power it up with mains also fans work. I did push the erase and reset buttons.
I had errors when I had tried to install firmware ie "failed to rename file" or something to that effect and 'failed to save changes" in config.G. SD card seems to be OK.

To test I bypassed the wiring and the problem went away. I might try disassembling my wiring harness and twisting them or I will get some multi-strand twisted pair cable. Thanks a lot for the answer dc42. BTW Impressed with the lack of over shoot on the extruder temperature. Deckingman I did mine the same as you, but it is quite a long run. Pics can be seen here http://forums.reprap.org/read.php?397,676997,page=7

@dc42:

My guess is that the spike occurs when the hot end heater changes from being fully on to PWM. Do you have the PT100 and hot end heater wires as different conductors in a single multicore cable? If so then you need to separate them. Twisted pair is ideal but not essential.

Thanks for the reply. The cables are in a single untwisted bundle. I was hoping to get away with it, but no maybe not. I will get some twisted pair multi core cable and rewire.

Equipment is Duetwifi, volcano hot end with 24v heater, PT 100 sensor and daughter board.
When I start heating temperatures are reported up until 10 degrees before target then the temperature reports as a 2000Cspike and I get this. Error: Temperature reading fault on heater 1: hardware error
This occurs at all temperature settings although if I set the target at 100C I get 3x 2000C spikes before the error appears.