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
Evaluación
Proyectos
148
59%
Arbitraje
16
38%
/
13%
Caducado
25
17%
Libre
Ha publicado: 1 ejemplo
Solicitudes similares
HFT Directional Grid Scalper
30 - 65 USD
HFT Directional Grid Scalper (Simple, Training Project) Overview We are looking for a developer to create a high-frequency grid scalper with a simple, deterministic logic. This is not a complex bot — the goal is to have a clean implementation for training, testing, and educational purposes. The bot should: Continually open trades in one direction only (BUY or SELL) Use ATR-based grid spacing Maintain a fixed
I want a accurate indicator with buy and sell arrows or circle.. with exit points which trade xauusd and btcusd via weekend ... for small like R100 or 500 .... like which can grow small accounts with ... on for serious developer.. no bullshit ... I need on Friday please
I'd like to automate a relatively simple strategy in Sierra Chart, but I'd like to have it backtested and optimized first. Could we collaborate on this, and what would the cost be? Only bid if you think you can handle this project, and I want expert in sierra chart.. Thanks
EMA Cross Over boom and crash
30+ USD
I need an EMA crossover EA specifically for Boom and Crash. It should automatically buy and sell when crossovers happen. I want adjustable inputs for lot size, timeframe, and maximum loss. I’m keeping it simple because I’ve had bad experiences with EAs before. It should do only the job it is built for, properly and reliably. need someone who have already build EA or Indicator for Boom and Crash befor atleast 10
Need skilled MQL5 programmers for regular work.
30 - 200 USD
//+------------------------------------------------------------------+ //| ProTradingEA MT5 | //| Fully MT5-compliant with MACD, Trailing Stop, Break-Even | //+------------------------------------------------------------------+ #include <Trade\Trade.mqh> CTrade trade; // Optional override input string SymbolOverride = ""; // leave blank to auto-detect struct EASettings { int
MT5 Trade copier
50+ USD
I have access to an MT5 account. I have investor access. I would like to know if someone could help me create a bot that copies only the trades made on XAU/USD in that account but in my MT4 account. In that account, many trades are made across various pairs, and I realize that the conditions of their account are not very favorable for the type of trading they do, as the commissions are very high. I have an account
Scanner EA for mt4 indicator
30 - 50 USD
Good day, I would like to have an expert advisor for my MT4 indicator (Major key alert) that can scan and provide push notification messages for entry opportunities across different time frames when a when a signal is identified
I need an expert advisor at around 30$-50$
30 - 50 USD
"I need an MT5 EA based on price action — liquidity sweep + hammer/shooting star reversal strategy. TREND: Identified by HH/HL for uptrend, LL/LH for downtrend on selected timeframe. No trade in ranging conditions. BUY SETUP: In uptrend, price retraces to swing low zone, wicks below it (liquidity sweep), hammer forms (lower wick min 2x body, closes above swept low). Buy stop entry at hammer high. SL below hammer
I need a professional MQL5 developer to finalize a Gold (XAUUSD) trading bot. The core layering and support-filter logic is already drafted. Key Requirements: Refine a hybrid Martingale/Layering volume calculation (1-10 / 11-20 reset logic). Implement a robust "Safety Mode" based on Daily Low price breaks. Ensure precise 6:00 AM Server Time reset for logic variables. Add professional error handling (Slippage
I want an order manager ea for XAUUSD
30 - 50 USD
I want a gold order management ea that should be like the below... Pending orders When I open one manual order, ea should be able to set 3 pending orders at x amount of pips below (if buy order) or above (if sell order) manual order entry. So like this Pending order 1 true or false Pending order pips away: 20. Pending order lot size:0.3 Pending order 2 true or false Pending order pips away: 40 Pending order lot
Información sobre el proyecto
Presupuesto
30+ USD