No unknown devices in any category and nothing under the USB category or at least these values don't change when its plugged in.

image url)

Here is what I tried, but according to to the wiki for RRF3 both endstops can be called on on the same line like this "M574 Y2 S1 P"ystop+zstop". Then it matches with the drives you call out for the Y axis " Y1:9".

CONFIG
; Endstops
M574 X2 S1 P"xstop" ;X axis active high endstop switch
M574 U1 S1 P"e0stop" ;U axis active high endstop switch
M574 Y2 S1 P"Ystop" ;Y axis active high endstop switch
M574 V2 S1 P"zstop" ;V axis active high endstop switch

HOMEY
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
M584 Y1 V9 ; Split Y axis motors
G1 H1 Y500 V500 F1800 ; move quickly to Y axis endstop and stop there (first pass)
G1 Y-5 V-5 F6000 ; go back a few mm
G1 H1 Y25 V25 F360 ; move slowly to Y axis endstop once more (second pass)
G1 H2 Z-5 F6000 ; lower Z again
G90 ; absolute positioning
M584 Y1:9 ; Combine Y-Axis

@aidar From what I read this does not need to be done in RRF3 but I tired anyways to see what happends. Axis's finally separated but the "V" drive does not stop with the "zstop". They both motors stop with the "ystop".

Yep, that is for RRF2. With 3 you are supposed to be able to home them without spiting them up. Its why I switched to 3 when it just came out but I have gotten it to work yet.

I still have not found a solution to home my y-axis powered by two different steppers to two different endstops.

FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.1.1 ELECTRONICS: Duet WiFi 1.02 or later + DueX5 FIRMWARE_DATE: 2020-05-19b2

Currently this is what I have in my config. The y-axis stops if either the Ystop or the Zstop is triggered, the endstops are not paired to each stepper. Does someone see the issue.

M584 X0 U2 Y1:9 Z5:6:7 E3:4 ; set drive mapping

M574 X2 S1 P"xstop"
M574 U1 S1 P"e0stop"
M574 Y2 S1 P"ystop+zstop"

On a side note, I had this exact configuration when RRF3 just came out and the switches acted totally different then they do now with the latest firmware....

Thanks! Updated RRF and DWC to the latest RC and the height map is now displaying properly.

To update DWC to 2.1.5 do I not just upload the .zip like I do for RRF? After I do this the status on the general tab does not change from 2.0.4.

Yeah, but do you not know the answer to my original questions?

3.01
2.0.4

Thanks but I am ware of that page. Below is how I am calling up the height map after a G30.

G29 S1 P"buildtak.csv"

Can you verify if the height map should change, like I asked previously? Also you would think the name of the height map would be displayed so you know which one was active.

Is there a way to verify what height map is being used if one is called before a print?

I have two csv files, one for each one of my flex plates. When I call a previous mesh the current map is the web interface does not change. Should it change or does it always display the last map probed?