Thanks.
Worked right away!

How do I mark this post as solved?

Thanks for pointing this out.
I am using 5 phase stepper motors. They have a 1000step / rev.

Good catch on the jerk value. I prints better now. But I also noticed I had hiccups after running M122 so I need to reduce my step rate

My duet wifi 2 is stuttering especially on non circular curves/arcs at around 60mm/s or higher.

Here are my drive settings:

M350 X2 Y2 Z8 I0                              ; configure microstepping without interpolation
M350 E16 I1                                   ; configure microstepping with interpolation
M92 X200.00 Y200.00 Z800.00 E393.00           ; set steps per mm
M566 X400.00 Y400.00 Z12.00 E20.00            ; set maximum instantaneous speed changes (mm/min)
M203 X12000.00 Y12000.00 Z180.00 E3600.00     ; set maximum speeds (mm/min)
M201 X1500.00 Y1500.00 Z3000.00 E2000.00      ; set accelerations (mm/s^2)
M906 X800 Y800 Z1000 E900 I30                 ; set motor currents (mA) and motor idle factor in per cent
M84 S30                                       ; Set idle timeout

• My current slicer is S3D. I plan to switch to Cura very soon.
• I do not use automatic mesh bed compensation.
• I do not have pressure advance activated yet.
• I am using panelDue 7i

What are the main causes for this issue?
Does my 3D .STL model have too many vertices?
Are my steps per mm overloading the duet?
Is there a way to reduce final Gcode curve resolution through the slicer?

It feels like I am reaching the steps per second limit on my duet wifi 2.
I really want my printer to cruise through arcs like how it does on straight lines!
Really interested on hearing everyone's input regarding this matter.

Thank you for the reassurance.

My carriage is a little heavy but with alot of friction so I actually need to use a nema 23 motor on the Z axis.

I have already turned down the motor current to the lowest possible. Any lower and it can not move vertically upward anymore.

It is possible to reduce motor current during Z probe ONLY when it is going down and normal power when it is moving up?

I got quite spooked from the nozzle almost crashing a few times already. I just feel very unsafe if I cant visually see the "1000" like before on RRF2. Especially from the fact that it would work the first time and become unresponsive after that.

_

After doing your suggested code, It currently triggers like before with RRF2. Everytime I run homez.g it successfully triggers.

This is the setting:

M558 P9 C"^zprobe.in" H5 F120 T4000            ;set Z probe type to bltouch and the dive height + speeds 

I still am unable to see the "1000"

You are right I am focusing too much on the 0/1000, but what bothers me the most is why RRF2 could read it and now RRF3 cant. I'm afraid it might actually crash in the future if my set up is actually defective and the probe system is now barely working by sheer luck.

Is it now normal to not see the 0/1000 with RRF3 with a BLTouch?

I did some manual testing.

If I manually short the two BLTouch pins ON THE DUET, I will see 1000. When I let go, it will show 0.
Great!

When I use a multimeter on the BLTouch, I get a constant reading of 1.1Ohms regardless of pin position.

I measure 3.3V between the two BLTouch pins ON THE DUET.

***One important thing I did incorrectly was I temporarily reversed the BLTouch plug (the black and white) and plugged it in the wrong polarity when I was not able to get the M401 and M402 commands to work a while ago. Because of this, the BLTouch signal pins would get a negative voltage? Do you think I broke the BLTouch?

Thanks for the suggestions.

I do not know why but my servo command is inversed. But anyways, M401 and M402 are working properly.

Because it did not show the "1000" on DWS or PanelDue, I never actually ran the homez.g test. When I tried it, It was successful! However, when I try homez.g a second time, the printer will continue to dive even when the BLTouch is triggering Blue to Red multiple times. The only way to make it respond once is to cycle the power.

I changed to this:

; Z-Probe
M950 S0 C"!exp.heater7"                       ; 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 C"zprobe.in+zprobe.mod"
G31 P500 X0 Y-35.4 Z2.5                       ; set Z probe trigger value, offset and trigger height

I tried both:

C"zprobe.in" , C"^zprobe.in" , C"^!zprobe.in"

But I still get the same result. Either stuck at 0 or 1000 when at M401 or M402.

When I was using RRF2 I get a solid 0 or 1000 when using the M401/402 commands. Is RRF3 now unable to show probe?

Thanks.
Worked right away!

How do I mark this post as solved?

Hello,
I have duet wifi 2 with expansion breakout board. on RRF 3.1.1
I am using BL touch

I am unable to get the Z probe to read "0" or "1000" correctly. It is stuck at "0"
M280 P0 S10 and M280 P0 S10 is working and my Bl touch will move.
I connect the servo to H7 on the breakout board, and black/white signal wires next to the paneldue port. I reversed the black/white signal wires once to see to troubleshoot another issue a few hours ago. Would this be the cause?

Here is the lines in my config.g regarding probe settings:

; Z-Probe
M950 S0 C"!exp.heater7"                        ; create servo pin 0 for BLTouch
M558 P9 C"zprobe.in+zprobe.mod" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds C"zprobe.in+zprobe.mod"
G31 P500 X0 Y-35.4 Z2.5                       ; set Z probe trigger value, offset and trigger height
M557 X20:180 Y20:180 S20                      ; define mesh grid

I do not understand what this means: C"zprobe.in+zprobe.mod"
I did add a "!" and I was able to get a reading of 1000 but it would not change back to 0. Either stuck at 0 or 1000

Hello,
My paneldue can not connect to my duet wifi 2 anymore. It shows "connecting" on the top right.

I updated my duet wifi 2 to RRF 3.1.1
My panel due worked without failure before this.
My old version was RRF 2.04

I then proceeded to update my panel due firmware successfully and ended up with the same problem; stuck at "connecting" on the top right.

My config file is stock and produced from the reprapconfigurator for V3+ with no extra additions.

Thank you for your advice.

Sorry, I am unfamiliar with what you mean by RRF3. Is that the web service that creates all my config.g, etc.g files? Or are you talking about my version 2.04RC1?

I tried to update to 3.1.1 today
Here is my board information:

Board: Duet WiFi 1.02 or later (duetwifi102)
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 2.04RC1 (2019-07-14b1)
Duet WiFi Server Version: 1.23

Am I the most up to date?

I used a variable DC supply to externally test my pumps. I felt a 14V with 2 pumps wired in series performed very well. My Vin for the Duet board is around 24V.
I only plan to wire my pumps in series, not parallel.

Can I wire 2 pumps in series to my extruder? It seems like it will work because they wont go pass 5A. 2 motors will have a lowest possible of a total of 9ohms. 24V/9ohms = 2.67A which is less than the maximum rated 5A. Did I calculate it correctly? If they are in series, where should I place my flyback diodes, will I need more than 1?

I really like your idea to use an external mosfet. I cant find any information on how to do this for DC air pumps. I am simply not experienced enough to figure this out myself.
In order to make progress, Is it safe for me to just use the second E heater port? What types of issues would it cause if I did not use an external mosfet?

Continuing with using duet extruder heater port, how do I change my E1 into a fan port?
After I correctly map my heater port into a fan port, the last thing I would do is to set my PWM frequency to 25,000Hz?