trabajo MQL5: 032518 Request

Descripción

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.

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

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.

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.

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.

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.

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.

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

Evaluación

(94)

Proyectos

148

59%

Arbitraje

38% / 13%

Caducado

17%

Libre

Ha publicado: 1 ejemplo

Solicitudes similares

Hello, I need a professional MT5 Expert Advisor (EA) developed for a custom indicator-based strategy. Strategy Logic: Determine the trend direction: Uptrend = Buy opportunities only. Downtrend = Sell opportunities only. Entry Conditions: The indicator has 4 lines: 2 Green lines, 1 Red line, and 1 Blue line. Open a Buy trade when both Green lines move inside/between the Red and Blue lines during an uptrend. Open a

A trading robot that operates with a balance of $20 to $50, with a loss of $5 and a profit of $10, and a maximum of three trades per day

I am looking for an MT5 Expert Advisor specifically designed to help meet common prop-firm evaluation requirements while prioritizing consistency, low drawdown, and strong risk management. The EA should use a robust trend-following and market structure-based strategy with multi-timeframe confirmation, momentum filtering, and optional news filtering to avoid low-quality trades. It must include configurable risk

The bot uses: RSI MA(2/7) crossover for entry signals Price Bollinger Bands as trend filter RSI Bands(34) as confirmation London/NY session filter (M5 only) ATR-based SL/TP Gap bridge between sessions Here's your EA. Here's what it replicates from the Pine Script bot: Strategy logic RSI MA(2) crosses MA(7) for entry signals Price Bollinger Bands(20) as trend filter RSI Bands(34) as confirmation filter ATR-based SL/TP

An Executive Assistant provides comprehensive administrative and operational support to senior leaders, ensuring efficient management of schedules, communications, meetings, and projects. They act as a key point of contact, coordinate business activities, maintain confidentiality, and help executives focus on strategic priorities while supporting organizational effectiveness

I need a simple bot for opening range. Simple Entry / Exit rules, to be able to customize the timeframe, time zone (entry candle) and other normal settings like size, etc

Hello, I am searching profitable, 0/1 rules strategy. Only serious offers please, I am expecting longer co-operation, I am open for your propositions, ideas. Have a nice day! I hope I will find here honest person

Need an Expert Advisor designed specifically for XAUUSD (Gold) , based on liquidity sweep + breakout confirmation logic. Market Focus Instrument: XAUUSD only Optimized for high volatility and intraday expansion behavior typical for Gold. Strategy Concept The EA is based on liquidity sweep of previous day levels followed by market structure shift and continuation in the confirmed direction. Daily Levels Previous Day

Can we do this 2 Indicatos at once NOTES 1. Step MA are on HTF, So values to be used are for Time frame that have closed 2. Pairs that are to be displayed for 2 STEP MA TREND DISPLAY are to be arranged in alphabetical order 3. Pairs in Bullish Weak trend are to be displayed in Green 4. Pairs in Bearish Weak Trend are to be displayed in Red 5. Position for displayed to be adjustable

Evening. I need a programme who will be patient with my EA specifications as it consists of +/- 30 sections ..but before we can start I want us to agree on these terms ...are as follows...the programmer should follow these order .[.Market regiom > trend bias > Lequidity > Smc > Momentum > Session > Risk > Entry > Exit ] and also should help me with these prototype request phase 1=Logicframework . phase 2=Entry engine

Información sobre el proyecto

Presupuesto

30+ USD

Calidad de la tarea técnica
Calidad de la verificación de resultados
Disponibilidad y habilidades de comunicación