is modification request is centered around creating "as needed" limit orders created until the desired pips goal "y" is obtain. Meaning,
limit order positions are created until the "y" is obtained.
<Start position>
The opening positions are a limit "buy" position and a limit "sell" position opened "x" pips away from the current price.
Example-1, let's say EUR/USD is currently @ 1.1000 and x=10
A limit buy position will be placed @ 1.1010
-AND-
A limit sell position will be placed @ 1.0990
<Closure>
The closure of these positions is determined by "y".
Example-2, let's say EUR/USD is currently @ 1.1000 and x=10 y=10
A buy limit position will be placed @ 1.1010
-AND-
A sell limit position will be placed @ 1.0990
If the buy position is opened @ 1.1010, then the closure will be 10 pips -- as determined as "y".
In this case, it will be 1.1020 and the position will be closed along with the removal of the sell limit order @ 1.0900 even
though it was never opened.
<Process>
When a set of limit orders are placed and both the buy and sell orders are opened prior to reaching "y", this is called a "grid lock". Thus, when a "grid lock" happens,
an additional set of limit orders are placed--an additional set of buy and sell limit orders. The placement of the additional set is "x" away from the 1st set of limit orders.
Example-3, let's say x=10 y=10 using Example-1
A buy limit position was placed @ 1.1010 and was opened and did not reach "y"
-AND-
A sell limit position was placed @ 1.0990 and was opened and did not reach "y"
A 2nd set of limit orders are placed "x" away from the 1st set of limit orders. In this case this would be the following:
A buy limit position placed @ 1.1020 since it is "x" away from the 1st buy limit order @ 1.1010.
-AND-
A sell limit position placed @ 1.0980 since it is "x" away from the 1st sell limit order @ 1.0990.
<Closure>
With the limit orders reaching its 2nd set, the "closure" would be determined by "y". Remember "y" is the net positive difference off all present opened position.
Once "y" is achieved, all positions are closed and removed. Thus, ending this cycle.
Example-4
Continuing fomr Example-3
In the 2nd set of limit orders placed, the buy position was opened @ 1.1010 and reached "y". In this case, "y" will be @ 1.1050
sell-1 opened @ 1.0990 closed @ 1.1050 = -60 pips
sell-2 never opened n/a
buy-1 opened @ 1.1010 closed @ 1.1050 = +40 pips
buy-2 opened @ 1.1020 closed @ 1.1050 = +30 pips
----------------------------------------------------------
Sum = +10 pips
y = 10 pips
Once "y" is achieved, the "cycle" starts again in Example-1.
<Additional set of limit orders>
Since the market is the market, the total number of "grid locks" occuring will always change. Thus, the number of sets of limit orders needed to achieve "closure" can vary.
Thus, whenever a "grid lock" happens, an additional set of limit orders is placed.
If after a new set of limit orders is placed and a "grid lock" doesn't occur, then the next focus would be "Y". "Y" is the total sum of all present opened positions.
<Summary>
This is the process of this request. It is as follows:
1. |START|
2. Define "X" and "Y"
3. Place 1st set of limit orders
4. Did Grid Lock occur? Yes or No
5. If No, proceed to "closure" determined by "Y". Cycle Ends. Start over.
6. If Yes, place 2nd set of limit orders. Placement of orders is determined by "X".
7. Did Grid Lock occur? Yes or No
8. If no, proceed to "closure" determined by "Y". Cycle Ends. Start over.
9. If yes, place 3rd set of limit orders. Placement of orders is determined by "X".
10. Did Grid Lock occur? Yes or No.
11. Repeat this process as needed until there is no "Grid Lock" and "Y" is achieved.
<Significance of Montiero_ea>
In the already provided robot "Montiero_ea" I would like to keep the following variables:
nCycles
Base
Magic
nCycles is number of times you want the robot to complete a closure.
Base is using the balance to determine the number of "lots" for the limit orders.
Magic is the instance number used.
I forsee (as an example) of the following to be the variables|value for this robot request
Variables Value
_1_ __EA Settings__
nCycles Same as Montiero_ea
currencyPair Same as Montiero_ea
Base Same as Montiero_ea
X see example above
Y see example above
Magic Same as Montiero_ea
<END>
If there is any clarification needed on any part of this, please let me know and I will provide greater clarity.
Solicitudes similares
Dear Developers, Please build a hyper-precision, continuous bi-directional Scalping Expert Advisor (EA) for MT5 based on the following extremely detailed requirement specifications: 1. Dynamic Entry Logic (Green and Red Candle Micro-Execution): - Do not use RSI, MACD, or EMA crossover filters for execution. The EA must be active 24/7. - Upon activation, the EA must instantly and simultaneously open both a BUY
I Trade on XAU and I need a proven MT5 profitable EA. Must needs proved of backtesting ROI, drawdown data, and Live proven results. I need solid proof of Live account and needs to check for minimum 7 days for myself. For that you can send me ex5 file at this moment no need to send source code. Once everything is verified then you may send me the source code. Must you will have to supply mq5 file to the end
Title: Scalper V max - EA with Advanced Profit Protection & Loss Defense Project Overview: I require a high-frequency MQL5 (or MQL4) Expert Advisor named "Scalper V max". The bot must execute precision scalping entries on short timeframes (M1 / M5) while strictly enforcing automated profit-locking and loss-defense rules to prevent large drawdowns. 1. Signal & Entry Logic: - Indicator Setup: Combine EMA Crossover
I need an already developed EA with proven ability to grow small accounts for day trading. It can trade any specific instrument like gold, EURUSD or more than one instrument. Any strategy is welcomed, including scalping in lower timeframes A test version is required before concluding the deal or being selected. Only those with ready products apply No fake EAs needed
Hi there. I need someone who can create an trading ea that should place order in points movement if it more then The spread but it must calculate the next price movement points using ai ,atr to be sure with the next points if it greater then the spread , it must read the live spread and compare of the next price can cover up the spread cost message me if you can also test will require only the movement of the next
the final ea must faithfully implement the logic from the provided phython file run cleanly on mt5 and deliver solid backtest result.its shoild be very easy to set up use with clear input parameter proper risk management and no complicated installation steps
PrimeXBT Broker - EA Bot wanted to be built $30 for the job to be completed. I’ve done the code just need this online via an experienced developer. Let’s hope you can make my bot and gain me a better lifestyle
Okay im ready to create my goals new beginning life tough but u learn and restart why not now it never too late chance szszybinvdtvvijbcdyvvxsxhuyfxbj b x d h b x d b xhnnk b v c d taking care of yourself for me is a
ثبت طلبك في مواصفات البوت الثاني كذا: الجودة والأمان أهم من السعر، وما يدخل إلا إذا الفرصة قوية، مع حماية عند الخسائر وانقطاع الاتصال وارتفاع السبريد، وتشغيل مستمر على سيرفر، مع اختبارات إلزامية قبل أي تشغيل حقيقي. بهذه الصيغة يصير يشتغل وأنت مرتاح بالِك، لكنه يوقف تلقائيًا وقت عطلة السوق أو أي خلل. بس أكون واضح معك: ما في بوت يضمن عدم الخسارة، خصوصًا بالمضاربات السريعة، هدفنا نقلل المخاطر ونمنع الخسائر غير المنضبطة
I'm looking for an experienced MQL5 developer to create a Opening Range Breakout EA. The EA should identify the high and low of a configurable trading session and open trades when price breaks out of this range. It should include configurable Stop Loss, Take Profit, fixed lot size, break-even option and trading hours. Full mq5 required