仕事が完了した
実行時間4 日
開発者からのフィードバック
Great client to work with. Clear requirements and very good communication throughout the project. Payment was fast and everything went smoothly. I would be happy to work together again in the future.
依頼者からのフィードバック
There is no best developer, only the right developer for you.
指定
| List: | |
| Close EA (No Stop EA) | 2,3,4 |
| SendNotification | 1 |
| Guard monitor EA | 7,8,12,13,14 |
| Failed market Delay | 5 |
| ToDeveloper | 9,10,11 |
| interval | 15 |
| Modification 7: | ||||||||
| Added 1 feature to the Expert Advisor (EA): | ||||||||
| Maximum number of consecutive losing orders = 500 | ||||||||
| Uncounted loss orders (losses >= N pips) = 300 | ||||||||
| symbol | magic number | |||||||
| XAUJPYm | 834 | |||||||
| Explanation: This EA has a maximum of 500 consecutive losing orders. If this limit is exceeded, a notification will be sent: "EA_834(XAUJPYm)_Exceeded Maximum Number of Consecutive Losing Orders_Safety Control Activated." After stopping, close the EA. | ||||||||
| This function allows the EA to check its historical trading records. | ||||||||
| This function does not calculate the total number of consecutive losing orders for the entire account, but rather the consecutive losing orders for the EA itself. | ||||||||
| Condition 1: Losing orders closed within the same number of seconds will only be counted once. | ||||||||
| For example 1, if 6 orders close at a loss within the same number of seconds, it will only be counted once. | ||||||||
| For example 2, if 13 orders with different comments close at a loss within the same number of seconds, it will only be counted once. | ||||||||
| For example3, if 5 orders with different comments close at the same time ("2026.02.26 03:15:39") and are considered losing orders, they will only be counted once. | ||||||||
| Then, if 6 orders close at the same time ("2026.02.26 03:15:42") and are considered losing orders, they will only be counted once, for a total of 2 counts. | ||||||||
| Then, if 5 orders at different times are consecutively losing orders, they will only be counted 5 times, for a total of 7 counts. | ||||||||
| Then, if 6 orders are consecutively losing orders, but 2 of them exceed 300 pips in loss, they will only be counted 4 times, for a total of 11 counts. | ||||||||
| The counting will reset only when a profitable order is closed. | ||||||||
| Remark: The function belongs to "Guard monitor EA" function. | ||||||||
| ----------------------------------------------------------------------------------------------------------- | ||||||||
| Modification 8: | ||||||||
| Add 3 conditional statements about "The EA continuously monitors the status of the current step and the previous step". | ||||||||
| Previous_Price_Points_Steps_Deviation = 100 | ||||||||
| Case1: | ||||||||
| Direction_Steps = s s b | ||||||||
| Price_Points_Steps = 0 -200 4000 | ||||||||
| If the distance between the current step "b" and the previous step "s" is <= 3900 because of (4000-100), send a notification "EA_834_EURUSD_Status anomaly of current step and previous step (Price_Points_Steps)_step2_4000", then close the EA order and the EA. | ||||||||
| The notification format is: = EA_"magic number"_"symbol"_Status anomaly of current step and previous step (Price_Points_Steps)_"current stepN"_"Price_Points_Steps value" | ||||||||
| Case2: | ||||||||
| Direction_Steps = b s | ||||||||
| Price_Points_Steps = 0 -4000 | ||||||||
| If the distance between the current step "s" and the previous step "b" is >= -3900 because of (-4000+100), send the notification "EA_834_EURUSD_Current Step and Previous Step Status Anomaly (Price_Points_Steps)_step1_-4000", then close the EA order and the EA. | ||||||||
| Case3: | ||||||||
| the current step buy order(include b,b#) = 3001.22 | ||||||||
| the previous step sell order(include s,s#) = 3001.23 | ||||||||
| If the price of the current step buy order(include b,b#) is below the price of the previous step sell order(include s,s#), send the notification "EA_834_ETHUSD_Current Step and Previous Step Status Anomaly (Direction_Steps)_step4", then close the EA order and the EA. | ||||||||
| The notification format is: EA_"magic number"_"symbol"_Current Step and Previous Step Status Anomaly (Direction_Steps)_"current stepN" | ||||||||
| Remark: The function belongs to "Guard monitor EA" function. | ||||||||
| ----------------------------------------------------------------------------------------------------------- | ||||||||
| Modification 12: | ||||||||
| Next_Price_Points_Steps_Deviation = 1000 | ||||||||
| If the EA detects that an order has met the conditions for opening an order, and this condition has been exceeded by 1000 pips for 10 minutes, it will begin sending a notification, after which the EA will attempt to replenish the order. | ||||||||
| If, for unknown reasons, the order still does not exist, and this condition has been exceeded by 1000 pips for 30 minutes, a second notification will be sent, after which the EA will attempt to replenish the order. | ||||||||
| If, for unknown reasons, the order still does not exist, and this condition has been exceeded by 1000 pips for 120 minutes, a third notification will be sent, after which the EA will attempt to replenish the order. | ||||||||
| If, for unknown reasons, the order still does not exist, and this condition has been exceeded by 1000 pips for 4320 minutes, a fourth notification will be sent, after which all orders will be closed, and the EA will be shut down. | ||||||||
| Case1: | ||||||||
| string Direction_Steps= | b b b s | |||||||
| string Driection_Lots= | 0.01 0.02 0.03 0.18 | |||||||
| string Price_Points_Steps= | 0 -600 -1200 -1200 | |||||||
| For example: | ||||||||
| 3600.12 <--- step0 | ||||||||
| 3594.12 <--- step1 | ||||||||
| 3582.12 <--- step2 "current step" | ||||||||
| 3570.12 <--- step3 "next step" | ||||||||
| A price less than 3570.12 is the condition for starting an order in step3. | ||||||||
| The first notification will be sent if the price is below 3560.12 (because 3570.12 - 1000 pips) and remains so for more than 10 minutes. The notification will then be: "EA_834_ETHUSD_STEP3_Price has met the condition to open an order at 3570.12, but the order has not been opened after 10 minutes." EA will then attempt to add the order. | ||||||||
| If, for unknown reasons, the order still does not exist, and the price exceeds the opening condition by 1000 pips and remains so for 30 minutes, the notification will be: "EA_834_ETHUSD_STEP3_Price has met the condition to open an order at 3570.12, but the order has not been opened after 30 minutes." The EA will then attempt to add the order. | ||||||||
| If the order still doesn't exist for unknown reasons, exceeding the order activation requirements of 1000 pips and lasting for 120 minutes. The EA will then send a notification: "EA_834_ETHUSD_STEP3_Price has met the order activation requirement of 3570.12, but no order has been activated after 120 minutes." The EA will then attempt to add the order. | ||||||||
| If the order still doesn't exist for unknown reasons, exceeding the order activation requirements of 1000 pips and lasting for 4320 minutes, a fourth notification will be sent: "EA_834_ETHUSD_STEP3_The next step cannot be activated even after exceeding the order activation requirements of 1000 pips and 4320 minutes. Safety Control Activated. EA stopped." The EA will then stop, close all orders, and then shut down. | ||||||||
| Remark: The function belongs to "Guard monitor EA" function. | ||||||||
| ----------------------------------------------------------------------------------------------------------- | ||||||||
| Modification 13: | ||||||||
| Holding current orders (not historical orders), If an order has 3 or more duplicates with the same symbol, magic number, and comment, | ||||||||
| for example, if there are 5 duplicates, | ||||||||
| the EA (Expert Advisor) will delete 4 of the duplicate orders, keeping only 1, and send a notification: "EA has found 5 duplicates with the same symbol, magic number, and comment; this has been corrected." If, after correction, there are still 3 or more duplicates with the same symbol, magic number, and comment, the EA will close all orders and send a notification: "EA has found the same product, magic number, and comment for the second time, therefore the EA is forcibly closed." The EA will then be close all order and then shut down. | ||||||||
| Remark: The function belongs to "Guard monitor EA" function. | ||||||||
| ----------------------------------------------------------------------------------------------------------- | ||||||||
| Modification 14: | ||||||||
| An Expert Advisor (EA) can open a maximum of 100 orders within every <=200 seconds and <=500 pips. | ||||||||
| If this limit is exceeded, the EA will be stopped, the orders closed, and the EA closed, and a notification sent. | ||||||||
| Stopping the Expert Advisor (EA) before closing the order prevents the EA from continuously closing orders while simultaneously opening new ones. | ||||||||
| The notification format is: "Indications of continuously opening orders - More than 100 orders opened within 200 seconds and 500 pips, EA closed (EA_magic number_symbol_comment)". | ||||||||
| EA Function Name | Parameters | |||||||
| Maximum Number Of Orders Allowed | 100 | |||||||
| Monitor Each Time Range (in seconds) | 200 | |||||||
| Monitor Each Price Range (in pips) | 500 | |||||||
応答済み
1
評価
プロジェクト
71
37%
仲裁
4
25%
/
75%
期限切れ
1
1%
暇
パブリッシュした人: 1 code
2
評価
プロジェクト
28
7%
仲裁
9
33%
/
33%
期限切れ
1
4%
仕事中
3
評価
プロジェクト
35
23%
仲裁
4
0%
/
50%
期限切れ
2
6%
仕事中
4
評価
プロジェクト
11
27%
仲裁
1
0%
/
0%
期限切れ
5
45%
暇
5
評価
プロジェクト
8
38%
仲裁
1
100%
/
0%
期限切れ
2
25%
暇
6
評価
プロジェクト
571
35%
仲裁
83
31%
/
45%
期限切れ
206
36%
暇
7
評価
プロジェクト
1
0%
仲裁
0
期限切れ
0
暇
8
評価
プロジェクト
257
53%
仲裁
16
50%
/
38%
期限切れ
83
32%
暇
9
評価
プロジェクト
53
57%
仲裁
2
100%
/
0%
期限切れ
1
2%
暇
パブリッシュした人: 5 codes
10
評価
プロジェクト
22
41%
仲裁
8
0%
/
50%
期限切れ
3
14%
暇
11
評価
プロジェクト
12
0%
仲裁
3
33%
/
33%
期限切れ
0
暇
12
評価
プロジェクト
269
29%
仲裁
2
50%
/
0%
期限切れ
3
1%
仕事中
パブリッシュした人: 2 codes
13
評価
プロジェクト
25
36%
仲裁
3
33%
/
67%
期限切れ
3
12%
仕事中
14
評価
プロジェクト
39
23%
仲裁
14
0%
/
93%
期限切れ
4
10%
暇
15
評価
プロジェクト
13
62%
仲裁
1
0%
/
100%
期限切れ
2
15%
仕事中
16
評価
プロジェクト
0
0%
仲裁
0
期限切れ
0
暇
類似した注文
Development of custom SMC Trading EA for MT5
80 - 100 USD
Hi, I want to develop a custom SMC (Smart Money Concepts) EA for MT5. My budget is $100. Here are the strategy requirements: 1. Auto identification of BOS, CHoCH, Order Blocks (OB), and FVG. 2. Auto entry when price returns to OB/FVG. 3. Auto SL above/below OB and TP based on Risk-to-Reward ratio (1:2, 1:3). 4. Risk Management (Risk % per trade or fixed lot size), Trailing Stop, Break-Even, and Max Spread filter. 5
I need an experienced MQL5 developer to build a prototype MT5 Expert Advisor called RiskLock. The software should enforce user-defined trading risk rules before trades are executed. It should support risk percentage or fixed monetary risk, calculate position size using account equity, entry price, stop loss, tick value and contract specifications, block or reduce oversized trades, and include daily loss limits
I need EA Lil-MeProBot for MT5. Phone user, deliver .mq5 + .ex5. Symbols: XAUUSD EURUSD GBPUSD USDJPY BTCUSD, M15, Magic 777001 Strategy 6X Confluence score 4/6: 1. EMA 50/200 trend 2. Break of Structure 3. RSI 14 4. Strong body FVG/Order Block 5. Session 8am-9pm GMT+2 6. ATR filter Money Management LASTING: Lot 0.01 fixed, NO martingale, NO grid, Max 1 per symbol Max 2 total, SL ATR*2 TP ATR*3, Daily loss R40 stop
MQL5 Quantitative Research & EA Optimization Project
280 - 2000 USD
Project Overview I have an existing MT5 Expert Advisor (EA) written in MQL5. The source code ( .mq5 ) will be provided. The underlying strategy is a trend-following system that performs well during trending market conditions, but requires professional quantitative research to improve its ability to identify and avoid highly sideways/range-bound market conditions. The objective of this project is not to build a new EA
I am looking for an experienced MQL5 Expert Advisor (EA) developer to analyze an existing trading setup and develop a similar automated trading robot. Project Overview I have access to a demo trading account where trades are being executed automatically. The trading results look very promising, but I do not know exactly what strategy, logic, indicators, or trade-management rules are being used. I will provide access
Most of the expert is already coded . Create a panel to show the Ratio for the Range . Trigger is based on ratio . Show Distribution / project starts after we clear Distribution
Modification of existing ea
30+ USD
Modification of existing ea …. Add ema filter, add risk percentage per trade, and modify the pips per day filter. I already have the ea code I just need these things added and modifified
Expert Advisors
300+ USD
double CRiskManager::CalculateLotSize(double slPoints) { double balance = AccountInfoDouble(ACCOUNT_BALANCE); double riskMoney = balance * (m_riskPercent / 100.0); double tickValue = SymbolInfoDouble(_Symbol, SYMBOL_TRADE_TICK_VALUE); double tickSize = SymbolInfoDouble(_Symbol, SYMBOL_TRADE_TICK_SIZE); double pointValue = tickValue / tickSize; double lot = riskMoney / (slPoints * pointValue);
Trading Bot for MT5
30+ USD
i share my strategy i need a bot trending bot fo mt5 . i attached the photo with this it help to make bot. it basicly 1 hours time frame base. i try but failed to make it
Title: Simple background trading bot for my Oanda account (v20 REST API) Overview Hi, I need a simple, lightweight event based standalone trading bot that connects directly to my Oanda account using broker’s standard REST API (V20 account) via VPS The bot just needs to look at group of 5 currency pairs (manually selectable and adjustable) in different 4 baskets, do some basic percentage math every period, and place
プロジェクト情報
予算
30+ USD