<p>This MKS-GEN-L board is in essence a plain RAMPS board, and as such it uses the same pinout apart from some specific pins. Do note the include of the RAMPS <a href="https://github.com/MarlinFirmware/Marlin/blob/2.0.x/Marlin/src/pins/ramps/pins_MKS_GEN_L_V2.h" rel="nofollow noreferrer">pinout in the MKS-GEN-L at the end of the file</a>. </p>

<p>From your comment you have changed the pins 14 and 15, in doing so, you need to plug the Y-min endstop in the Y-max socket after uploading the modified firmware. With the unmodified firmware (no pin switch), if the Y-endstop works in the Y-max socket, this means that you have a hardware issue. The pin labeled 14 is connected to the Y-max instead of the Y-min. If you did the pinout switch and left the endstop in the Y-min socket, then you can conclude that the 15 pin is not connected to the Y-min socket. Basically you don't have a 15 pin that is exposed. Could be that there is an issue on the board with the traces or the soldering.</p>

CC BY-SA 4.0
2020-06-15T19:28:16.223Z
it worked still messing with the mesh gritpoints right now...
edensan
CC BY-SA 4.0
2020-06-15T11:47:10.463Z
2020-06-15T11:47:10.463Z
0scar
<p>I have a FLSUN i3 220x220x240 with:</p>

<ul>
<li>an 2004 LCD (RepRap Discount Smart Controller)</li>
<li>an MKS-gen-L-v1.0 printer board running Marlin firmware 2.0.5.x</li>
<li>3D touch sensor,</li>
<li>a filament runout sensor.</li>
</ul>

<p>Everything works fine but for the mechanical Y-min switch: it stays triggered.</p>

<p>(<code>M119</code>) YMIN worked under Marlin 1.1.2; everything is connected correctly and is physically working.</p>

<p>I don't know what to do... Does maybe someone have an idea of what I can do?</p>

<p>These are my config files:</p>

<ul>
<li><a href="https://pastebin.com/raw/JP7yUwFQ" rel="nofollow noreferrer">configuration.h</a> </li>
<li><a href="https://pastebin.com/raw/c9K11PA3" rel="nofollow noreferrer">configuration_adv.h</a></li>
<li><a href="https://pastebin.com/raw/QCEED64z" rel="nofollow noreferrer">pins_RAMPS.h</a></li>
</ul>

<p><img src="https://i.sstatic.net/RMMLC.jpg" alt="enter image description here"></p>

CC BY-SA 4.0
2020-06-14T10:16:13.590Z
Please help us  help you! a photo of the printer would help. Does the trigger signal change if you manually trigger it (which would hint that you wired the switch up as Normal Closed not Normal Open. Also, we'd much prefer to have the text of your configurations uploaded on a site where we don't have to download it, for example, pastebin.com - this makes reading the source code much easier.
Trish
CC BY-SA 4.0
2020-06-14T11:08:08.003Z
@Trish if i trigger by hand  no response Y (not defect tested) X ,Z  and FILLAMENT SENSOR repond normal on closed and open (test m119)
edensan
CC BY-SA 4.0
2020-06-14T15:58:37.967Z
I changed pins 14 to 15 and 15 to 14 no difference. Also, if I change Y-min pin to X-min then Y-min trigger and X-min won't trigger! but, when I put the plug in theY-max is working!
edensan
CC BY-SA 4.0
2020-06-15T09:57:09.333Z
sounds like the pinning on the board and the firmware placement for these pins is mixed up. Another possibility might be shoddy soldering that the pins are not properly connected
Trish
<marlin><troubleshooting><endstop>
Y-min stay triggered
edensan
# Y-min stay triggered

(Asked by: username_0 on 2020-06-14)

I have a FLSUN i3 220x220x240 with:

* an 2004 LCD (RepRap Discount Smart Controller)
* an MKS-gen-L-v1.0 printer board running Marlin firmware 2.0.5.x
* 3D touch sensor,
* a filament runout sensor.

Everything works fine but for the mechanical Y-min switch: it stays triggered.

(`M119`) YMIN worked under Marlin 1.1.2; everything is connected correctly and is physically working.

I don't know what to do... Does maybe someone have an idea of what I can do?

These are my config files:

* [configuration.h](https://pastebin.com/raw/JP7yUwFQ)
* [configuration\_adv.h](https://pastebin.com/raw/c9K11PA3)
* [pins\_RAMPS.h](https://pastebin.com/raw/QCEED64z)

![enter image description here](https://i.sstatic.net/RMMLC.jpg)

**Tags:** marlin, troubleshooting, endstop

> **Comments:**
> **username_1**: Please help us  help you! a photo of the printer would help. Does the trigger signal change if you manually trigger it (which would hint that you wired the switch up as Normal Closed not Normal Open. Also, we'd much prefer to have the text of your configurations uploaded on a site where we don't have to download it, for example, pastebin.com - this makes reading the source code much easier.  
> **username_0**: @username_1 if i trigger by hand  no response Y (not defect tested) X ,Z  and FILLAMENT SENSOR repond normal on closed and open (test m119)  
> **username_0**: I changed pins 14 to 15 and 15 to 14 no difference. Also, if I change Y-min pin to X-min then Y-min trigger and X-min won't trigger! but, when I put the plug in theY-max is working!  
> **username_1**: sounds like the pinning on the board and the firmware placement for these pins is mixed up. Another possibility might be shoddy soldering that the pins are not properly connected  

---

## 1 answers

### Answer by username_2 on 2020-06-15. Score: 1

This MKS-GEN-L board is in essence a plain RAMPS board, and as such it uses the same pinout apart from some specific pins. Do note the include of the RAMPS [pinout in the MKS-GEN-L at the end of the file](https://github.com/MarlinFirmware/Marlin/blob/2.0.x/Marlin/src/pins/ramps/pins_MKS_GEN_L_V2.h).

From your comment you have changed the pins 14 and 15, in doing so, you need to plug the Y-min endstop in the Y-max socket after uploading the modified firmware. With the unmodified firmware (no pin switch), if the Y-endstop works in the Y-max socket, this means that you have a hardware issue. The pin labeled 14 is connected to the Y-max instead of the Y-min. If you did the pinout switch and left the endstop in the Y-min socket, then you can conclude that the 15 pin is not connected to the Y-min socket. Basically you don't have a 15 pin that is exposed. Could be that there is an issue on the board with the traces or the soldering.

> **Comments:**
> **username_0**: it worked still messing with the mesh gritpoints right now...  

---

