MQL5.comでのフリーランスサービス: 032518 Request

説明

指定

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.

応答済み

評価

(94)

プロジェクト

148

59%

仲裁

38% / 13%

期限切れ

17%

暇

パブリッシュした人: 1 code

類似した注文

Hello, I have two Expert Advisors (EAs) that I'm migrating to my MQL5 VPS. I need a program that I can run on a separate chart or other interface to: - Allow EA #2 (with the magic number) to trade only during the Asian session. Therefore, EA #2 needs to be blocked during all other sessions. - Allow EA #1 to trade without restriction. Thank you

Labouchere System has many series and can transfer the Units to any other Series when needed (this function is very important). Building a dedicated SeriesManager class to handle all eight arrays would be very useful to make the unit transfers "atomic," so the logic is bulletproof and we never have to worry about data errors during the series transitions. The coders who really knows this cancellation sytem can apply

Project Overview I need an MQL5 developer to review and confirm their understanding of this project before providing a quote. Objective: Backtest an Opening Range Breakout (ORB) strategy on NAS100USD and generate detailed trade documentation. Requirements: Instrument NAS100USD only. Backtesting Run the ORB strategy on historical data. Target a minimum of 200 trades if the available data allows. Advise how much

Looking to buy profitable MT4/MT5 Expert Advisors (EAs). Requirements: • Fully automated • 6+ months backtest • 100+ trades • No martingale or grid systems Send: • Backtest report • Max drawdown • Markets traded • Brief strategy summary Only original EAs developed by you. Long-term collaboration available

Hi, We are an experienced team of quants with products top ranked in MQL5 but who needs to gain audience on 10K+ communities to advertise EA to get more traffic on mql5. Thanks

We are looking to purchase Expert Advisors (EAs) for MetaTrader 4 and MetaTrader 5. Requirements: -Minimum 6 months of history (12+ months preferred). -Forex pairs, Gold (XAUUSD), Indices, Commodities, or Crypto CFDs are all acceptable. -Fully automated. -No martingale. -No grid systems. -No lot multiplication or position size scaling based on previous wins or losses. -Not dependent on extremely low spreads/slippage

DESCRIPTION: I require an experienced MQL5 developer to build a fully automated, multi‑engine, multi‑asset trend‑following trading system for MetaTrader 5. The system includes: Multiple TrendEngine instances (one per symbol) A PortfolioController that manages all engines Volatility‑regime detection Dual‑timeframe confirmation ATR‑based breakout logic ATR‑based stop management Micropyramiding Risk‑weighted satellites

Description: I need a semi-automatic Expert Advisor (EA) developed for MetaTrader 5 (Hedging account, optimized for Exness Cent accounts) to manage my manual trades on Gold (XAUUSD) using a positive pyramiding trend-following strategy. Detailed Specifications: 1. Multi-Basket Management (Crucial): The EA does NOT open the initial trade. It waits for me to open a manual trade (Buy or Sell). If I open another manual

Live chart [ expert is not executing trades on xauusd ] , Deleting Existing Parameter not in use , Live Chart Adjustments Only , No Need to Change anything else , expert will be live testing Throughout

//@version=6 indicator("منظومة El_3aksiiya 0 المتكاملة", overlay=true, max_labels_count=500, max_boxes_count=500, max_lines_count=500) // الألوان color_accum = color.new(#0000FF, 85) color_manip = color.new(#FFFF00, 80) color_dist = color.new(#FFC0CB, 80) color_elliot = #FF8C00 color_fib = #FFFF00 color_entry = #00FFFF color_tp = #00FF00 rsiVal = ta.rsi(close, 14) // نموذج AMD var int barCount = 0 if

プロジェクト情報

予算

30+ USD

仕様品質
結果チェックの品質
可用性とコミュニケーションスキル