Best posts made by Macgyver

Jay_s_uk hit it right on the head, I was missing the M671.

Here is the config with the 671 configured, It's a long one but it works.

; generated by RepRapFirmware Configuration Tool v3.3.0 on Tue Aug 10 2021 15:48:47 GMT-0400 (Eastern Daylight Time)

; General preferences
M575 P1 S1 B57600 ; enable support for PanelDue
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves

; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet

; Drives
M569 P0 S1 ; physical drive 0 goes forward (Y)
M569 P1 S0 ; physical drive 1 goes backward (Y)
M569 P2 S0 ; physical drive 2 goes backward (X)
M569 P3 S1 ; physical drive 3 goes forward (E0)
M569 P4 S1 ; Physical Drive 4 goes forward (E1)

; Z axis motors are plugged into the Duex contoller numbers 5-8
M569 P5 S1 ; Physical Drive 5 goes forward (Z-LR)
M569 P6 S1 ; Physical Drive 6 goes forward (Z-LF)
M569 P7 S1 ; Physical Drive 7 goes forward (Z-LF)
M569 P8 S1 ; Physical Drive 8 goes forward (Z-LF)

M584 X2 Y0:1 Z5:6:7:8 E3:4 ; set drive mapping

;Z axis leadscrew locations
M671 X-70.0:-70.0:570.0:570.0 Y40.0:520.0:520.0:40.0 S5 ; Z leadscrews are at (-70,40)LR #5, (-70,520)LF #6, (570,520)RF #7 and (570,40)RR #8 , 5mm max correction

M350 X16 Y16 Z16 E16:16 I1 ; configure microstepping with interpolation
M92 X160.00 Y80.00 Z400.00 E695.00:695.00 ; set steps per mm
M566 X900.00 Y900.00 Z60.00 E120.00:120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z500.00 E1200.00:1200.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00:250.00 ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E450:450 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S180 ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X500 Y500 Z500 S0 ; set axis maxima

; Endstops
M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop+zstop" ; configure active-high duel endstops for low end on Y via pins (ystop(L))(zstop(R)
;M574 Y2 S1 P"zstop" ; configure active-high endstop for low end on Y(R) via pin zstop
M574 Z1 S1 ; configure Z-probe endstop for low end on Z

; Z-Probe
M950 S0 C"duex.pwm5" ; create servo pin 0 for BLTouch
M558 P9 C"^zprobe.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
;M558 H30 ;*** Remove this line after delta calibration has been done and new delta parameters have been saved
G31 P500 X5 Y0 Z2.3 ; set Z probe trigger value, offset and trigger height
M557 X15:485 Y15:485 S47 ; define mesh grid

So after much trying to figure out what's going on with this machine, turns out had a weak spot in one of the ground lines in my BLtouch, It would work sometimes and randomly just not trigger. Ran 5 new lines all from the BLtouch through the drag chain to the mainboard (about 17 ft) and now its working 100% predictability.

Just going to post my configuration here in case others want something to ref that is working. All this is done on RRF 3

Config .g file

; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Tue Mar 02 2021 18:05:15 GMT-0500 (Eastern Standard Time)

; Endstops
M574 X1 S1 P"!xstop" ; configure active-high endstop for low end on X via pin !xstop
M574 Y1 S1 P"!ystop" ; configure active-high endstop for low end on Y via pin !ystop

; Z-Probe
M950 S0 C"exp.8" ; Assign GPIO port 0 to Heater3/Pin8 on exp conn, Servo Mode
M558 P9 C"^zprobe.in" H5 F120 T6000 ; set Z probe type to 9 BL Touch and the dive height + speeds
G31 P500 X0 Y0 Z6.3 ; set Z probe trigger value, offset and trigger height
M557 X15:585 Y15:585 S28.5 ; define mesh grid

---

; deployprobe.g
; called to deploy a physical Z probe
M280 P0 S10

---

; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Tue Mar 02 2021 18:05:15 GMT-0500 (Eastern Standard Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 X-605 Y-605 F1800 ; move quickly to X and Y axis endstops and stop there (first pass)
G1 H2 X5 Y5 F6000 ; go back a few mm
G1 H1 X-605 Y-605 F360 ; move slowly to X and Y axis endstops once more (second pass)
G30
G90 ; absolute positioning
G92 Z0 ; set Z position to axis minimum (you may want to adjust this)

---

; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Tue Mar 02 2021 18:05:15 GMT-0500 (Eastern Standard Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G30
G92 Z0 ; set Z position to axis minimum (you may want to adjust this)

HI @jay_s_uk , thanks for the reply

After installing just the Wifi update, Came up with the same scrolling error and then a message connected to the access point, IP address 255.255.255.255,

That was weird because that is a broadcast address. Anyway did the S0 and S1 again and it connected properly. Error is basically still happening.

I updated the DWC as a separate step to help anyone else troubleshoot,

First time I power cycled the printer, Came up perfectly, Connected properly and gave me the proper IP address.
Power cycled it again and back to the same error message.
However, If I just do nothing Eventually it does come online itself. Sometimes takes 2 mins to connect and give me the IP.

So I started thinking maybe there may be some other networks in the configuration that is toying with it. I ran the procedure listed in this Post
https://forum.duet3d.com/topic/9888/how-to-erase-remembered-networks/4

basically the M588 S"*"
I set up my network again from scratch with the M587 and now after 10 power cycles, It seems to be working ok.

If I was to guess what may be going on as you apply firmware versions it may be adding "default" or "beta" networks that it has to scan and see that they are not there before it will move on to the next one. That is strictly my guess but the version of the DWC definitely had the biggest effect.

For me, I just like to try and understand the source of the error but for anyone else troubleshooting this error take @jay_s_uk 's advice and ensure your firmware versions match.

@phaedrux

that's awesome, thank you for the info,

I appreciate the time 2 you both.

Hi Guys

Sorry for going AWOL on this, unfortunately got Covid but finally back in the office and back on this machine.

Going to work through it and update it shortly.

Hi Guys

Sorry, I missed the update, Yes all is working now. thanks again for your help.

Up to the last tests I was doing it was a coding issue, as it turns out somewhere along the line the BLtouch sensor went bad. I wrote a script to probe 10 times and report the divination. the number was never the same, or even close for that point. turned out the touch was bad.

Actually a good point, I missed that,

Not sure where that one came from

you can mark this thread as solved, Hopefully, someone else can find it and make use of the information.

Thanks again for your help guys Truly appreciate it.

Update to this post

I replaced the SD card with a new 16GB card, Formatted and reinstalled all the setup files.

It did give me an error message of mismatched firmware versions although I could not find evidence of anything mismatched. I did reflash the entire package of 3.5.2 and everything now is working as it should.

I can now edit and save changes to the config.g file, As an extra did modify some of the macro files as well as they no longer dissapear.

I would mark this one as resolved.
Just as an additional information I checked the previous SD card in a windows PC, Checked it for errors and no errors were picked up. Still a weird problem but I am chaulking it upto a problem with the origional SD card.