032518 Request

MQL5 Asesores Expertos

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
Desarrollador 1
Evaluación
(94)
Proyectos
148
59%
Arbitraje
16
38% / 13%
Caducado
25
17%
Libre
Ha publicado: 1 ejemplo
Solicitudes similares
Hello everyone, I’m looking for someone who can help me develop an Expert Advisor (EA) for Boom and Crash markets. I need a developer who has proven experience and has already developed at least 10–15 EAs for Boom and Crash. This will help save both your time and my time when filtering developers. The EA will include: EMA crossover strategy Different time filters Additional custom conditions and logic I’m also
I want to find a Developer to perform this work and settle payments in this Application. I undertake not to communicate with Applicants anywhere else except this Application, including third-party messengers, personal correspondence or emails. I understand that violators will be banned from publishing Orders in the Freelance service. I have read the Rules of using the Freelance service and accept them. I agree with
Overview: I would like to create a robot in MT5 (what I use) that when the price or candle touches a moving average it auto- matically gets me into a trade. Details or features I need: 1 a way to tell it how much to trade 0.10 or ten cents per pip or more or do I set this in MT5? 2 a way to limit the number of trades per candle or set it to two or three trades (if the price crosses over the moving average ten times I
Candle bot 30+ USD
A dual-direction breakout stacking EA using previous candle highs/lows as triggers with rolling pending orders and fixed micro take profits. It is suitable for: automation EA development trend capture with repeated entries recovery-style trade management
Szukam doświadczonego programisty do stworzenia dedykowanego doradcy eksperckiego (EA) do tradingu. Programista powinien posiadać solidną wiedzę z zakresu MT5, logiki strategii, wskaźników, zarządzania ryzykiem i backtestingu. Doświadczenie w tworzeniu niezawodnych i profesjonalnych robotów handlowych będzie dodatkowym atutem. Proszę o kontakt, jeśli zrealizowałeś już podobne projekty. wszystkie szczeguły podam w
I am looking to buy a ready-made automated trading robot / EA that works on the Tradovate platform and is proven to pass prop firm challenges for Apex Trader Funding, Tradeify, and Lucid Trading.Key Requirements (must be ready-made or very close to plug-and-play):Fully functional on Tradovate (native or via stable bridge/copier/webhook/API integration – MT5 EA + Tradovate bridge is acceptable if it works reliably)
Alex 1000+ USD
Нужен бот для скальпинга именно на Python. Работа напрямую через API биржи (без привязки к TradingView и MetaTrader). Бот будет запускаться локально на ноутбуке / VPS. Критически важна скорость (использование асинхронности, WebSockets
Looking for an experienced programmer to create a fully automated trading system. The EA must be able to detect SPECIFIC H&Shoulder patterns, identify entry point and open a position. Parameters: Candle Count : EX: 50 - meaning the max amount of candle history to look for a pattern. (user adjustable) RISK: EG "2" Meaning the position that must be opened must be 2% of the Balance of the account (user adjustable). The
I’m looking for an experienced MetaTrader 4 (MT4) developer to analyze, repair, and live-test an existing .EX4 Expert Advisor. Project Details Existing file: GannMadeEasy_pro.ex4 Platform: MetaTrader 4 Issue: EA is not loading properly on charts in newer MT4 builds Goal: Make the EA fully functional and compatible with current MT4 versions Requirements The developer must: Analyze the existing EX4 file Identify
i need the EA same working on trading view chart with same specifications of enter in a trade and sl/tp open 2 trades and 1 trade set tp1 & second trade set to tp 3 but sl should move to breakeven when tp1 hit and go to tp2 sl on tp1

Información sobre el proyecto

Presupuesto
30+ USD