작업 종료됨
실행 시간 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 코드
2
등급
프로젝트
27
7%
중재
9
33%
/
33%
기한 초과
1
4%
작업중
3
등급
프로젝트
35
23%
중재
4
0%
/
50%
기한 초과
2
6%
작업중
4
등급
프로젝트
10
20%
중재
1
0%
/
0%
기한 초과
4
40%
작업중
5
등급
프로젝트
8
38%
중재
1
100%
/
0%
기한 초과
2
25%
무료
6
등급
프로젝트
565
35%
중재
81
31%
/
44%
기한 초과
204
36%
무료
7
등급
프로젝트
1
0%
중재
0
기한 초과
0
무료
8
등급
프로젝트
257
53%
중재
16
50%
/
38%
기한 초과
83
32%
무료
9
등급
프로젝트
51
59%
중재
2
100%
/
0%
기한 초과
1
2%
무료
게재됨: 5 코드
10
등급
프로젝트
22
41%
중재
8
0%
/
50%
기한 초과
3
14%
무료
11
등급
프로젝트
12
0%
중재
3
33%
/
33%
기한 초과
1
8%
무료
12
등급
프로젝트
267
30%
중재
0
기한 초과
3
1%
작업중
게재됨: 2 코드
13
등급
프로젝트
20
20%
중재
3
33%
/
67%
기한 초과
3
15%
무료
14
등급
프로젝트
39
23%
중재
14
0%
/
93%
기한 초과
4
10%
무료
15
등급
프로젝트
10
50%
중재
1
0%
/
100%
기한 초과
2
20%
무료
16
등급
프로젝트
0
0%
중재
0
기한 초과
0
무료
비슷한 주문
Hello looking for someone to convert an indicator from tradingview to Thinkorswim I have attached the codes from trading view Also, I like make it trigger (alert) a one-time alert when the trend changes, and can also create a custom watchlist column that flags symbols currently in a new trend so you can scan multiple stocks easily. And like the watchlist to show only fresh trend changes or the current trend direction
Version document : 1.0 Plateforme : TradingView Langage : Pine Script v6 Type : Indicateur d'analyse et d'aide à la décision (non-exécutant) 1. Présentation du projet Nom du produit ONYX SR V2 — Intelligent Support & Resistance Scalping System Objectif Créer un indicateur TradingView capable d'identifier automatiquement des opportunités de scalping basées sur : supports et résistances dynamiques ; action du prix ;
I have a EA/indicator that I want built. I should say 1st off dont know how to code myself so I will be using AI to verify that the source code is complete and matches the documents spec or if better so if you can not truly do the job do not waste either of out time. This is a idea I came.up wit and used AI to produce a framework for it.... and of course AI isn't 100% accurate so I need a knowledgeable quantitative
TumiiFX
30 - 20000 USD
1. Use two EMAs: 20 and 50. If EMA 20 is above EMA 50 → uptrend (look for buys) If EMA 20 is below EMA 50 → downtrend (look for sells) 2. Wait for a pullback into the area between the two EMAs. - For buys: price must touch or move between EMA 20 and EMA 50 during the last few candles. - For stils: same idea, but in a downtrend. 3. Entry signal: Buy: a bullish engulfing candle in an uptrend after the pullback
I Need HFT bot working on MT4
30 - 100 USD
I am looking for an experienced MQL4 developer to build a professional High-Frequency Trading (HFT) / Low-Latency Expert Advisor for MetaTrader 4 (MT4) . The EA will be deployed on an IC Markets Live account and should be optimized for the fastest possible execution using a low-latency VPS located in LD4 or NY4 . The primary instruments will be US30 and XAUUSD (Gold) . The goal is to create an EA capable of
A robot
50+ USD
HIGH-FREQUENCY M5/M15 CONCURRENT ENTRY SNIPER import time class HighFrequencySniper: def __init__(self): self.target_profit = 25.00 # Targeted Delta Move self.max_execution_time = 3600 # 1 Hour Sandbox (Seconds) self.lot_allocation = "CALIBRATED_TO_RISK" def execute_hft_scan(self, current_price, m5_rsi, m15_order_block): print(f"[SCANNING] Current Kernel Metric: ${current_price:.2f
I need a trading bot, please i need this project urgently and when messaing me kindly send me samples of past works and dont forget i need the project to be done as soon as possible
A lightweight MT5 chart overlay displaying total floating P&L, average entry price, combined lot size, and current symbol exposure as a percentage of account balance, all updating in real time with color-coded profit/loss indicators, delivered with clean object-oriented source code and no DLL dependencies
ENTRY EXIT TIMING (ET BANDS)
30 - 50 USD
QUIERO CONSEGUIR EL CODIGO FUENTE DE ESTE INDICADOR QUE ME GUSTA MUCHO TAMBIEN TIENE EL NOMBRE DE ET BANDS O ENTRY EXIT TIMING . no se los componentes pero estas son las imagenes. que mejor lo describen
I am looking to convert my existing TradingView Pine Script (v5) strategy into an MQL5 Expert Advisor (EA) for MetaTrader 5. Strategy Details: Asset: Gold (XAUUSD) Timeframe: 15-minute Strategy Logic: The strategy is based on a breakout concept. Anchor Candle: The base calculation starts from the Specified Candle Entry Window: The EA should only look for entries As Per Indicator Risk Management: The strategy
프로젝트 정보
예산
30+ USD