Tarea técnica
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.
Han respondido
1
Evaluación
Proyectos
148
59%
Arbitraje
16
38%
/
13%
Caducado
25
17%
Libre
Ha publicado: 1 ejemplo
Solicitudes similares
Expert Advisor (EA) Requirements – MT5 (MQL5) Project Overview Develop an automated Expert Advisor (EA) for MetaTrader 5 based on EMA crossover signals combined with strict risk management and trade management principles. The EA must be optimized for Forex pairs and indices and should operate automatically without manual intervention. Entry Conditions Buy Setup Fast EMA crosses above Slow EMA. Current candle closes
I am in need of a profitable scalping EA for gold. No grid or martingale strategy pls. If you have one fully developed and working, pls reach out. You should be able to provide trial version
Weekend Gap Display Indicator
30+ USD
Simple MT5 indicator showing Friday close to Monday open gap on chart. Features: · Draw horizontal line at Friday close · Label showing gap size in pips · Toggle on/off
Hi. I have the statement of the Ea live results that I want to have. Please check this video from YouTube and the statement to see how the robot is working every day. I want a robot like this or better. The robot has 1-4% drawdown and 300-500% profit per month The robot works with ICMarkets Global 1:500 leverage and FPMarkets. The robot works between 10-30 minutes London session. Also the Robot can start trading from
Modify a (Pruning) Grid EA
30+ USD
MT5 Expert Advisor Development Project Overview I am looking for an experienced MQL5 developer to build a custom MetaTrader 5 Expert Advisor based on a grid-cycle trading framework. This is not a standard grid EA . The system combines: Session-based trade initiation Multi-filter signal generation Dynamic grid management Advanced basket management State-machine-driven trade lifecycle management Dynamic take-profit
I'm building a trading signal platform called Tradexa , focused on US30 and Nasdaq indices. For Phase 1, I need a developer to implement the signal-generation engine based on a detailed strategy document that I will provide. Requirements Multi-timeframe analysis (H4 → H1 → M15) Generate signals on M15 only when all strategy conditions are satisfied Detect liquidity sweeps Market structure shift (BOS/CHOCH) Retest
Hi, ink it would be that much. I have an existing EA that has just stopped working, I installed a new MT4 platform onto a new laptop and now it will not execute any trades, although I have put a price of 30usd I don't think it would be that much. Thanks Roman
Need an MT5 EA coded in MQL5. Strategy uses internally calculated MT5 Heikin Ashi candles, EMA 9 and EMA 21 on M1 USDJPY. Fixed lot size 12.20. One trade at a time. 40-point stop loss. Exit after 3 consecutive opposite Heikin Ashi candles. I have a detailed strategy document and video examples of valid and invalid entries. Videos linked show MT5 IOS but custom EA code will be used for windows MT5
We need an experienced MQL5 developer to build the Equity Guardian Strategy — a risk management overlay EA designed to run alongside two existing Expert Advisors. The Guardian monitors account equity and automatically switches to Recovery Mode when drawdown reaches a set threshold. While in Recovery Mode, the EA must block or ignore trading signals from the other two Expert Advisors. The system uses dynamic hedging
Just a straight forward ea that reacts from candle close and open area using martingale option knowing what the broker charges per pair because will use it in a Z spread account so the ea will know what they charge or I can manually set charges so before ea close in profit it makes sure it covers the charges and added little profit before closing
Información sobre el proyecto
Presupuesto
30+ USD