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

Hi, I can get the EA source code for you, If you have any EA that you like using. let me know and i will code exactly the same EA with the same logic and inputs and it runs exactly like the one you using. lets chat

Help optimize ea. Write new conditions help current conditions when market go against it. Help write new conditions for ea improve my current conditions. Check current ea. Ea use only ohlc mtf. Uses pending limit, stop order

Hi Im working with a Crypto trading company and we want to branch out with our indicator, i'm researching the bot automation and need some hands on board. i i want to hear your opinion about the indicator that i would like you to build. in the PDF i explain the whole indicator and how it need to look like. happy to hear form you

The ea must repeat all orders until closed manually by a 'close all button' needed on panel EA must start at specific time / day and enter 'at market' - should be easy to code :) INPUTS REQUIRED: Pair ___ - Lot Size____ - Type ____ ( buy / sell) - Distance between trades in points______ - TP for each trade in points_____ - Maximum spread in Pips _____ - Time and day to

I want someone to hold a session for me and explain in details on how to implement them in. I would really appreciate your guidance on how to properly set up GoCharting and get access to CME futures data

//+------------------------------------------------------------------+ //| SMC_ICT_Advanced_EA.mq5 | //| Smart Money Concepts Trading | //| Combines Order Blocks, FVG, BOS, CHoCH | //+------------------------------------------------------------------+ #property copyright "SMC/ICT Trading System" #property version "2.00" #property strict #include <Trade/Trade.mqh>

Logic: Healthy → no action Weak → reduce exposure Danger → strong protection Requirements: Equity tracking Basic trade management Simple dashboard Only apply if you understand risk-based EA logic

Title: MT5 Martingale EA (Based on Stop Loss of Previous Trade) Description: Hello, I need a simple and efficient MT5 Expert Advisor based on a martingale logic. Main Logic: The EA should work with trades placed manually or by another EA (including limit orders). When a trade hits Stop Loss, the EA must automatically open a new trade in the same direction. The lot size of the new trade should be multiplied

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

I want the EA to be fully automated and capable of taking trades across multiple timeframes. It should be optimized for a starting account balance of $100 with proper risk management suitable for a small account, and it will be used with the broker ApexMarket.io. ⸻ Platform • Platform: MetaTrader 5 (MT5) • Type: Fully automated Expert Advisor • Operation: Hands-free (no manual trade management required) ⸻ 📈 Markets

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