You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
-
1interesting, is the membrane covered hole there just from machining the part?– SwiftyCommented Jan 22, 2021 at 21:15
-
The hole is normal and should be found on all models of this type. Obviously it should not leak a lot. I can only assume the hole is strategic so that if one was to overfill, the extra would just flow out the extra hole. Don't take my word for granted though, still have some research to do!– love2phishCommented Jan 22, 2021 at 21:24
-
Found this: patents.google.com/patent/US20180056967A1/en I have looked through it and kind-of/sort-of gives you an idea what could go wrong.– love2phishCommented Jan 22, 2021 at 21:37
-
1seems to be the patent for SRAM's version of Shimano's J-kit where the lever and hose can be shipped pre-bled but disconnected. The mention of a 'port' I read was to to with a port valve at the interface of hose and lever where it is closed until the two are mated when it opens automagically. but I didn't read it all and don't have the answer, I'm intrigued to know– SwiftyCommented Jan 23, 2021 at 13:41
-
1I have found out that the cap actually could be removed and diaphragm reset on older models of Shimano MTB brakes, but it does not seem to be the case with the newest models. I gave the link to this info in the comment to MaplePanda's answer. By the way, my brake works just fine despite the leak. The leak is just a squirt that happens when I overfill the brake during bleeding, and does not occur later, during use. However I can imagine that it could be a more serious problem for some people, if the membrane was damaged or if it moved more than mine.– MickCommented Jan 23, 2021 at 15:37
|
Show 2 more comments
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
-
create code fences with backticks ` or tildes ~
```
like so
``` -
add language identifier to highlight code
```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- quote by placing > at start of line
- to make links (use https whenever possible)
<https://example.com>
[example](https://example.com)
<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. mountain-bike), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you