Don't understand

I am having a horrible time with the DUET. I have had no issues this weekend with setting up the probe. The probe never hit the bed. Today, while I am still trying to get my first print, now when I do home all or home Z, it moves the bed, I see the probe value change from 0 to my target of 940. It slows down and then continues to move until it hits the bed and I have to shut the printer off to kill the movement. Here is my conifg file.

***********************************************************************************************************************
CoreXY sample config file for dc42 Duet firmware

M111 S0 ; Debug off
M550 Pprinter ; Machine name (can be anything you like)
M551 Preprap ; Machine password (used for FTP connections)
M540 P0xBE: MAC Address
;*** Adjust the IP address and gateway in the following 2 lines to suit your network
M552 P192.168.25.75 ; IP address (0 = use DHCP)
M554 P192.168.25.1 ; Gateway
M553 P255.255.255.0 ; Netmask
M555 P2 ; Set output to look like Marlin
M575 P1 B57600 S1 ; Comms parameters for PanelDue

G21 ; Work in millimetres
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves

; Machine configuration
M569 P0 S1 ; Drive 0 goes forwards (change to S0 to reverse it)
M569 P1 S0 ; Drive 1 goes forwards
M569 P2 S1 ; Drive 2 goes forwards
M569 P3 S1 ; Drive 3 goes forwards
M569 P4 S1 ; Drive 4 goes forwards
; If you use an endstop switch for Z homing, change Z0 to Z1 in the following line, and see also M558 command later in this file
M574 X1 Y1 Z0 S1 ; set endstop configuration (X and Y and endstops only, at low end, active high)
M667 S1 ; set CoreXY mode
M350 X16 Y16 Z16 E16 I1 ; set 16x microstepping with interpolation
M92 X63.69 Y63.69 Z800 E706.7 ; Set axis steps/mm
M906 X600 Y600 Z1200 E600 ; Set motor currents (mA)
M201 X800 Y800 Z400 E1000 ; Accelerations (mm/s^2)
M203 X15000 Y15000 Z200 E3600 ; Maximum speeds (mm/min)
M566 X600 Y600 Z30 E20 ; Maximum jerk speeds mm/minute
M208 X350 Y330 Z200 ; set axis maxima (adjust to suit your machine)
M208 X0 Y0 Z-0.5 S1 ; set axis minima (adjust to make X=0 and Y=0 the edges of the bed)

; Z probe
M558 P1 X0 Y0 Z1 ; Analog Z probe, also used for homing the Z axis
G31 Z1 P942 ; Set the probe height and threshold (put your own values here)
; The following M557 commands are not needed if you are using a bed.g file to perform bed compensation
;*** Adjust the XY coordinates in the following M557 commands to suit your build and the position of the Z probe
M557 P0 X60 Y0 ; Four...
M557 P1 X60 Y300 ; ...probe points...
M557 P2 X300 Y300 ; ...for bed...
M557 P3 X300 Y0 ; ...levelling
;M557 P4 X175 Y165 ; 5th probe point for levelling

; Tool definition
M563 P0 D0 H1 ; Define tool 0
G10 P0 S0 R0 ; Set tool 0 operating and standby temperatures
M92 E706.7 ; Set extruder steps per mm (single nozzle)
;*** If you have a dual-nozzle build, remove or comment out the previous line, and un-comment the following 3 lines
;M563 P1 D1 H2 ; Define tool 1
;G10 P1 S0 R0 ; Set tool 1 operating and standby temperatures
;M92 E420:420 ; Set extruder steps/mm (dual nozzle)

; Thermistors and heaters
;*** If you have a Duet board with 4.7K thermistor series resistors, change R1000 to R4700 to the following M305 commands
; You can also use S and B parameters to define the parameters of the thermistors you are using
M305 P0 B3950 R4700 H0 L0 ; Put your own H and/or L values here to set the bed thermistor ADC correction
M305 P1 R4700 H0 L0 ; Put your own H and/or L values here to set the first nozzle thermistor ADC correction
M305 P2 R4700 H0 L0 ; Put your own H and/or L values here to set the second nozzle thermistor ADC correction

;*** If you are using axis compensation, put the figures in the following command
M556 S78 X0 Y0 Z0 ; Axis compensation here
;
T0 ; select first hot end
*************************************************************************************************************

Any help would be appreciated. I have a make gear M2 that is marlin based so I know that and printers. Just don't know what is going on with this.

Found issue number one. I had the P value at 942. I changed it to 940 and it worked. Now I am having an issue with bed.g If I add the file and command a G32 or use the bed level button on web or panel due is does nothing. Here is my code for that.

M561
G28  ; clear any existing bed transform
G30 P0 X10 Y10 Z-99999  ; define 4 points in a clockwise direction around the bed, starting near (0,0)
G30 P1 X10 Y300 Z-99999
G30 P2 X330 Y300 Z-99999
G30 P3 X330 Y10 Z-99999
G30 P4 X175 Y165 Z-99999 S0  ; finally probe bed centre, and calculate compensation
G1 X0 Y0 F5000  ; move the head to the corner (optional)


I have commented out the M557 in the config.g file above

Which type of probe are you using? If it is my IR probe then you must set the trigger threshold to 500 in the G31 command as described in the fitting instructions at [miscsolutions.wordpress.com]. You should only get a value greater than 550 out of it if the phototransistor is saturated, which can occur if you use an unsuitable target e.g. bright aluminium - see the fitting instructions for advice on bed surface.

Check the Console page of the web interface for error messages when you run G32. It sounds like it isn't finding the bed.g file. Did you put it in the correct place, which is the /sys folder of the SD card? The M557 commands will only be used if bed.g is not found.

Edited 1 time(s). Last edit at 09/07/2016 05:04AM by dc42.

---

Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].

David,
I am using a PNP probe. It seems like the probe value has to be the correct number. I was able to run a test part. It looks good, but the bed.g file did not work. I added the file from the web interface so the file should have been seen. I also verified that it was on the card in the right space when I pulled it out of the DUET. If I enter G32, I see nothing on the console. I have removed the bed.g file and the machine was able to run.