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

I have EA available for boom 900 able to make 30$ daily from 100$ . I need investors to partner together and create a substantial capital for greater gains and equitable pooling and distribution

I need a local trade copier solution to transmit trades from MT4 and MT5 to NinjaTrader 8 instantly for arbitrage purposes, with ultra-low latency and no cloud services involved. Scope of work - Develop MT4/MT5 EA or script for detecting and sending trades locally. - Create NT8 NinjaScript for listening to and executing trades. - Support market orders and lot size conversion. - Implement symbol mapping for trades. -

hello great developer I want to develop a trading bot which connects with my Binance account. A bot that can work with tradingview.com where I use trading indicator which is called " TonyUX Ema scalper ". This indicator generates Buy and Sell signal. So i want a bot which can execute trade on binance when it gets a Buy/sell signal on tradingview.com ( see attached picture) Most likely you already have a similar bot

I need an MT5 Expert Advisor based on SMC (Smart Money Concepts) and SCOB pattern. Entry logic (M1 first, must work all TF): 1. Detect OB or FVG. 2. When price touches OB/FVG, wait for SCOB candle confirmation. 3. Enter at close of SCOB. Stop Loss: - SL at the high/low of SCOB candle. Take Profit (Box TP rule): - Use distance between point 1 and point 2 as a box. - TP = 2 × box size. - Same method as drawing box and

I would like someone Who can design an EA for me. I will give him the Required Details and Trading Plan How it should Work. its going to be a Simple EA System Around Moving Averages Crossover. I will Provide Him the Moving Averages Settings and How It should execute trades and Exit them

Hello. I already have a fully working TradingView indicator written in Pine Script. I am NOT asking for a new strategy or indicator to be designed. I need an experienced NinjaTrader (NinjaScript / C#) developer to replicate the same logic and behavior of my existing TradingView indicator so it works on NinjaTrader. Important points: The TradingView indicator does NOT repaint (uses confirmed bars only). This is logic

No jokers copy pasters allowed. If you're proficient in MQL5, have a proven track record with EAs apply. Commissioning the development of a high-performance Expert Advisor (EA) engineered for the MetaTrader 5 (MT5) environment. The objective is to deploy an institutional-grade automated trading system capable of systematic market analysis, precision execution, and strict risk governance within the global forex

I’m looking to acquire an existing, profitable Expert Advisor (EA) with full source code to add to our client investment portfolio. To be clear, this is not a request to develop or design a new strategy. If you already have an EA that is proven, consistent, and production-ready, I’m open to reviewing it immediately. Please apply only if you meet all the requirements below. Submissions without a proper introduction or

Hello, I would like you to develop a trading robot (EA) with the following specifications: The robot should be able to target large moves, ideally 60–100 pips or more per trade. It should use high-precision “sniper” entries, focusing on high-probability setups rather than frequent trades. Once the initial trade reaches breakeven, the robot should be able to add additional positions (scale in) while maintaining strict

Hello, I would like to commission the development of a trading robot (EA) designed specifically to pass a prop firm challenge within one week, with a maximum allowable drawdown of 2%. Key requirements: Strict risk management with drawdown hard-limits Controlled lot sizing and position management Strategy focused on high-probability, low-risk entries Full compliance with prop firm rules (daily drawdown, max drawdown

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