MTP Development Note 17 | It is not abnormal that EA does not enter. The filter is a safety device.
Hello, this is Tsumo.
This article isMTP Development Notes, No. 17.
Last time, we organized the points to watch during the first week of getting MTP started.
The first week is not a period to look at profits.
It is a period to see whether MTP is functioning as designed.
That is what we discussed.
Look at the update time of the Dashboard.
Look at the account health ratio.
Look at the available margin.
Look at open positions and their lots.
See why the Slave did not enter.
Look at the logs in the Expert tab.
By looking at these, you can finally see the outline of the operation.
This time, we will discuss something particularly important among them.
MTP: What to do when Slave does not enter.
The copied EA has entered.
MTP Master also recognizes it.
But the MTP Slave does not enter.
At this time, many people become anxious.
“Did I misconfigure it?”
“Is the EA broken?”
“Is there no communication?”
“Should I loosen the conditions further?”
I understand the feeling of urgency.
But, I will state this first.
Whether the EA enters or not is not necessarily abnormal.
Rather, the important thing in MTP is the “decision not to enter.”
MTP does not simply copy everything from the source EA as-is.
In dangerous situations, it stops.
Wait until conditions are right.
When the account state is poor, do not enter new follow-ups.
Avoid going against the momentum.
Do not enter around important indicators.
For this reason, there is a filter.
Filters are not obstacles.
They are safety devices to protect your account.
If you are interested in adopting MTP, please also take a look here.
What we will organize this time
This time, we will organize the reasons why MTP does not enter.
We will mainly cover the following contents.
There are two types of states where EA does not enter
Distinguish normal waiting from misconfigurations and errors
Reasons to wait at the subsequent entry stage
Reasons to wait for favorable entry
Reasons to stop with RSI filter
Reasons to stop with indicator stop filter
Reasons to stop with account health ratio filter
Reasons to stop with minimum entry interval
Where to look when it stops
Things to consider before turning off the filter
The purpose of this article is not to finely tune the filters.
First,to understand why MTP stops.
If you know the reasons for stopping, you will not panic during operation.
You will also reduce the number of times you tinker with settings.
This is important.
“Not entering” is not the same in every case
When MTP Slave does not enter, there are things to separate and consider first.
That is,
Are you waiting properly?
Are you not able to operate due to misconfiguration or errors?
These two are it.
Even though you are waiting normally, you might weaken the filter.
Even though it isn’t operating due to a misconfiguration, you might assume it’s the filter and leave it as is.
Both are dangerous.
From the perspective of “not entering,” it may look the same.
But the causes are completely different.
The first thing to look at in MTP operation is here.
Separate the reasons for not entering.
Even this alone allows much calmer verification.
Cases where you are waiting normally
First, cases where you are waiting normally.
This is a state where MTP is doing its job as designed.
For example, in cases like the following.
Have not yet reached the subsequent entry start level
Waiting for favorable entry conditions
RSI filter stops contrarian entries
Indicator stop filter is active around important indicators
Account health ratio has fallen, stopping new follow-ups
Hit the minimum entry interval
But here, due to lot caps or margin conditions, you pass
This is not MTP slacking off.
We are making judgments.
The judgment is that you are not entering.
In automated trading, the scariest thing is that everything enters.
Enter when you should enter.
Do not enter when it is better not to.
These two together make operation possible.
Cases where misconfiguration or errors prevent operation
On the other hand, there are cases where misconfigurations or errors truly prevent operation.
For example, cases like the following.
EA tag differs between Master and Slave sides
MT4’s automated trading is OFF
Auto-trading permission OFF when placing EA
DLL usage permission OFF
MTP: Slave not entered on the live account
Cannot log in to MT4 for the live account
Currency pair does not match
Lot settings are invalid
Insufficient margin
Order errors appear in the Expert tab
File access errors occur
This is not normal waiting.
Correction is required.
Therefore, when MTP: Slave does not enter, do not immediately blame the filter.
Conversely, do not immediately conclude the EA is faulty.
First, separate normal waiting from misconfigurations.
Skipping this often leads to getting lost.
Moreover, getting lost in EA operation drags your account balance into the forest.
Not recommended.
Waiting at the subsequent entry start level
One of the common reasons MTP does not enter is the subsequent entry start level.
For example,
Subsequent entry start level = 3If set to 3, the Slave will not follow the source EA's first and second levels.
It becomes a candidate to follow from the third level onward.
In other words, even if the source EA enters at level 1, it is normal for the Slave not to enter.
This is not a failure.
It is waiting as configured.
If you do not understand this, you will be anxious at the first check.
“The source EA entered, but the Slave did not.”
That is why it seems so.
But if the subsequent entry start level is 3, that is as planned.
Deliberately skip shallow first entries.
Follow from the subsequent levels.
Reduce risk a little.
This is the idea behind the subsequent entry start level.
The subsequent entry start level is designed to reduce entries
The subsequent entry start level is not just a number.
It is a philosophy of operation itself.
Whether to follow from the first level or
from the second level,
or from the third level.
This greatly changes how MTP Slave enters.
If you follow from the first level, you increase entry opportunities.
Yet you simply receive the source EA's initial entry as is.
If you follow from the third level, entry opportunities decrease.
But there is a possibility to follow after the market has moved against you to a certain extent.
There is no right or wrong here.
Character of the source EA.
Currency pair.
Capital amount.
Lot design.
Operating policy.
It depends on these.
However, in the initial deployment, first see whether you are waiting as configured.
Do not lower the subsequent entry start level just because it does not enter.
That would be like removing the door instead of checking why the doorway key is locked.
Yes, you can make it in.
But the protection will disappear.
Waiting for favorable entries
Next, favorable entries.
MTP Slave does not necessarily enter at the same price just because the source EA entered.
If favorable entries are valid, wait for a position advantageous to the Slave.
For example, in BUY scenarios.
The source EA enters with BUY.
Then the price falls.
Moves toward a favorable direction for the Slave.
Updates the extreme value even further.
From there, it becomes a candidate to enter on a rebound.
This is the kind of movement we look for.
In other words, MTP does not jump in.
It waits.
Entering here is not a fault.
It is waiting for a favorable price.
MTP waits not to increase entry次数 but to choose the right place to enter.
Favorable entries have meaning because they require waiting
Favorable entries are a mechanism to delay entries.
Therefore, naturally, the number of entries can decrease.
The source EA has entered.
But the MTP: Slave did not enter.
Cases like this can occur.
But that is the behavior of favorable entries.
There is meaning in not taking all entries.
If the market does not move in a favorable direction, you do not enter.
If the launch distance has not been reached, you do not enter.
If you do not rebound from the extreme, you do not enter.
This waiting makes MTP more than a simple copy.
While absorbing the source EA's movements, you also look at conditions on the Slave side.
If you do not understand this and immediately weaken favorable entries, the value of MTP diminishes.
“Because it doesn’t enter quickly, weaken it.”
That is easy to do.
But adjustments that seem simple can cost more later.
Stop with RSI filter
RSI filter is to avoid contrarian moves during rapid rises or falls.
This is often misunderstood.
It stops entries that go against momentum.
For example, when RSI exceeds 70.
That indicates overbought, i.e., a potential rapid rise.
Entering with SELL at this time would oppose the strong upward move.
Therefore, SELL follow-ups are restricted.
Conversely, when RSI drops below 30.
That indicates oversold, i.e., potential rapid drop.
Entering with BUY at this time would oppose the strong downward move.
Therefore, BUY follow-ups are restricted.
To summarize:
RSI >= 70
→ Overbought
→ Rapid rise
→ Restrict SELL followRSI <= 30
→ Oversold
→ Rapid fall
→ Restrict BUY followStopping at RSI filter means MTP is avoiding directions against momentum.
This is a safety device. (note)