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

Entry Rules: > * Open BUY when a Bullish Fair Value Gap (FVG) forms. Open SELL when a Bearish Fair Value Gap (FVG) forms. Risk Management: Every trade must have a Stop Loss and Take Profit. I want to be able to change these numbers in the settings. Mobile Features: The bot must send a "Push Notification" to my phone app for every trade. Assets: Must work on WTI Oil and Bitcoin

I want to create an EA that will help me stack trades. I'll set the price line and anytime the market goes at that price line it should execute the trade be it but or sell also the bot will have a timed finish and a timed start. That means I can set a time(during sessions, I'll specify more) when I want a trade to be executed instantly and also a time I want a trade to automatically close itself

I am looking for a reliable and well-developed Expert Advisor (EA) that demonstrates low drawdown and consistent profitability on a real trading account . If you have already built such an EA, I would be interested in evaluating it. I would require: Verified backtest results Forward testing performance (demo or real account preferred) Ideally, a live track record (Myfxbook / FXBlue or similar) I am serious about

🏆 HIRING: Quantitative Gold (XAU/USD) Trading Strategy Developer ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 📌 PROJECT OVERVIEW ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ I am building a professional trading signal platform (xtraderlab.com) and need an experienced quant trader or algo developer to design, code, and backtest a high-performance intraday Gold (XAU/USD) trading strategy. The strategy will be integrated into an existing

Technical Specifications: "Dawn Range Breakout" Expert Advisor (Final Version) 1. Overview The purpose of this EA is to capture the breakout of a specific hourly range on Gold (XAUUSD) or any other pair, with a focus on high-precision entry, strict risk management (1 trade per day), and partial profit taking. 2. Core Trading Logic Timeframe: M15. Reference Hour: The EA must identify the High and Low of the H1 candle

I need an Expert Advisor based on SK indicator for gold trading. Entry: - Open trade immediately when SK signal appears Stop Loss: - Fixed stop loss = $200 per trade Take Profit: - TP1: close 50% of the position - TP2: final target Lot Size: - Fixed lot = 0.02 Pair: - XAUUSD only Timeframe: - M15 Rules: - Only one trade per signal - No duplicate trades - Move stop loss to breakeven after TP1 Requirements: - The EA

i am looking for an experienced MQL5 developer to build a high-frequency trading Expert Advisor (EA) for XAUUSD (Gold) on M1 and M5 timeframes. The EA must include advanced execution logic, dynamic pending orders, risk management, and news/session filters. Clean, efficient, and well-documented code is required. Strategy type: Scalping (fast trades, quick profit). Very fast execution logic (optimized for speed). Goal

I would like to develop a bot that allows me to manually input trades based on the Masaniello money management system, which I will configure at the outset. Within this setup, I will be able to define all the key parameters of the Masaniello strategy, including the total number of events, expected winning events, stake ratio (i.e. the TP/SL ratio), and the initial capital. Once the Masaniello parameters are set, the

ZigZag based on oscillators is needed The idea of the indicator Create a ZigZag indicator, which is constructed based on extreme values determined using oscillators. It can use any classical normalized oscillator, which has overbought and oversold zones. The algorithm should first be executed with the WPR indicator, then similarly add the possibility to draw a zigzag using the following indicators: CCI Chaikin RSI

Essential Components for Indicator Specification Objective & Overview: Briefly describe what the indicator calculates (e.g., trend, momentum, volatility) and its main purpose. Input Parameters (Variables): List all user-definable inputs (e.g., Moving Average periods, ATR multiplier) to avoid hardcoding values. Detailed Logic/Calculation Rules: Explain the formula or logic to calculate indicator values. Define

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