모든 주문
규칙
트레이딩 로봇 주문 방법을 보십시오
주문을 실행하거나 포스트하기 전에 규칙을 읽으십시오
MQL5 및 MQL 4의 트레이딩 로봇을 주문하는 방법
로봇을 주문하기 위해샘플 요구 사항을 보십시오
카테고리의 새로운 주문:
30 - 200 USD
30 - 150 USD
30+ USD
100+ USD
100+ USD
작업 종료됨
실행 시간 2 일
고객의 피드백
Smart and helpful developer - I would highly recommend
피고용인의 피드백
verry good
명시
Hi
I need someone to create an EA based on a tradingview indicator (trendicator)
The EA would trade based on the indicator
This is the open source script
//@version=6
indicator('Trendicator', overlay = true)
// Input options for multi-timeframe
EMA1 = input.int(8, 'Quick Moving Average Length')
Sour = input(close, 'Quick Moving Average Source')
EMA2 = input.int(21, 'Slow Moving Average Length')
Colo = input.bool(true, "Use Crossover Colours")
Bool = input.bool(false, "Labels")
timeframe = input.timeframe('', title = 'Chart Timeframe (leave empty for current)')
timeframeSource = input.timeframe('', title = 'Moving Average Timeframe (leave empty for current)')
// Define MA calculations with multi-timeframe support
// Slow MAs (using close and open respectively)
EMABuy = ta.sma(request.security(syminfo.tickerid, timeframe, close), EMA2)
EMASell = ta.sma(request.security(syminfo.tickerid, timeframe, open), EMA2)
// Quick MA (using the chosen source)
EMA = ta.sma(request.security(syminfo.tickerid, timeframeSource, Sour), EMA1)
// Define colors (initialize)
var col1 = color.new(color.green, 0)
var col2 = color.new(color.red, 0)
// --- Corrected Buy and Sell Conditions ---
// Instead of comparing slow vs. quick the “wrong way,” we now say:
// Buy when the quick MA (EMA) is above both slow MAs,
// Sell when the quick MA is below both slow MAs.
Buy1 = EMA > EMABuy
Buy2 = EMA > EMASell
Sell1 = EMA < EMASell
Sell2 = EMA < EMABuy
// Define flags to track crossovers and avoid multiple triggers
var bool buySignal = false
var bool sellSignal = false
// Detect crossovers and set flags
buyCrossover = Buy1 and Buy2 and not buySignal[1]
sellCrossover = Sell1 and Sell2 and not sellSignal[1]
// Update flags to ensure single triggers
buySignal := buyCrossover ? true : sellCrossover ? false : buySignal
sellSignal := sellCrossover ? true : buyCrossover ? false : sellSignal
// Update color based on conditions if using crossover colours
if Buy1 and Buy2 and Colo
col1 := color.new(color.lime, 0)
col2 := color.new(color.lime, 0)
if Sell1 and Sell2 and Colo
col1 := color.new(color.red, 0)
col2 := color.new(color.red, 0)
// Plot the moving averages
p = plot(EMA, 'Quick Moving Average', color = col1, linewidth = 3)
q = plot(EMABuy, 'Slow Moving Average', color = col2, linewidth = 3)
// Fill the area between the two MAs based on trend
fill(p, q, color = Buy1 and Buy2 ? color.new(color.lime, 80) : Sell1 and Sell2 ? color.new(color.red, 80) : na)
// Alert conditions
alertcondition(buyCrossover, title = 'Uptrend', message = 'Buy')
alertcondition(sellCrossover, title = 'Downtrend', message = 'Sell')
// Add labels on crossovers
if buyCrossover and Bool
label.new(x = bar_index, y = low, text = 'Buy', color = color.lime, textcolor = color.white, style = label.style_label_up, size = size.small)
if sellCrossover and Bool
label.new(x = bar_index, y = high, text = 'Sell', color = color.red, textcolor = color.white, style = label.style_label_down, size = size.small)
indicator('Trendicator', overlay = true)
// Input options for multi-timeframe
EMA1 = input.int(8, 'Quick Moving Average Length')
Sour = input(close, 'Quick Moving Average Source')
EMA2 = input.int(21, 'Slow Moving Average Length')
Colo = input.bool(true, "Use Crossover Colours")
Bool = input.bool(false, "Labels")
timeframe = input.timeframe('', title = 'Chart Timeframe (leave empty for current)')
timeframeSource = input.timeframe('', title = 'Moving Average Timeframe (leave empty for current)')
// Define MA calculations with multi-timeframe support
// Slow MAs (using close and open respectively)
EMABuy = ta.sma(request.security(syminfo.tickerid, timeframe, close), EMA2)
EMASell = ta.sma(request.security(syminfo.tickerid, timeframe, open), EMA2)
// Quick MA (using the chosen source)
EMA = ta.sma(request.security(syminfo.tickerid, timeframeSource, Sour), EMA1)
// Define colors (initialize)
var col1 = color.new(color.green, 0)
var col2 = color.new(color.red, 0)
// --- Corrected Buy and Sell Conditions ---
// Instead of comparing slow vs. quick the “wrong way,” we now say:
// Buy when the quick MA (EMA) is above both slow MAs,
// Sell when the quick MA is below both slow MAs.
Buy1 = EMA > EMABuy
Buy2 = EMA > EMASell
Sell1 = EMA < EMASell
Sell2 = EMA < EMABuy
// Define flags to track crossovers and avoid multiple triggers
var bool buySignal = false
var bool sellSignal = false
// Detect crossovers and set flags
buyCrossover = Buy1 and Buy2 and not buySignal[1]
sellCrossover = Sell1 and Sell2 and not sellSignal[1]
// Update flags to ensure single triggers
buySignal := buyCrossover ? true : sellCrossover ? false : buySignal
sellSignal := sellCrossover ? true : buyCrossover ? false : sellSignal
// Update color based on conditions if using crossover colours
if Buy1 and Buy2 and Colo
col1 := color.new(color.lime, 0)
col2 := color.new(color.lime, 0)
if Sell1 and Sell2 and Colo
col1 := color.new(color.red, 0)
col2 := color.new(color.red, 0)
// Plot the moving averages
p = plot(EMA, 'Quick Moving Average', color = col1, linewidth = 3)
q = plot(EMABuy, 'Slow Moving Average', color = col2, linewidth = 3)
// Fill the area between the two MAs based on trend
fill(p, q, color = Buy1 and Buy2 ? color.new(color.lime, 80) : Sell1 and Sell2 ? color.new(color.red, 80) : na)
// Alert conditions
alertcondition(buyCrossover, title = 'Uptrend', message = 'Buy')
alertcondition(sellCrossover, title = 'Downtrend', message = 'Sell')
// Add labels on crossovers
if buyCrossover and Bool
label.new(x = bar_index, y = low, text = 'Buy', color = color.lime, textcolor = color.white, style = label.style_label_up, size = size.small)
if sellCrossover and Bool
label.new(x = bar_index, y = high, text = 'Sell', color = color.red, textcolor = color.white, style = label.style_label_down, size = size.small)
응답함
1
등급
프로젝트
313
28%
중재
33
27%
/
64%
기한 초과
10
3%
무료
2
등급
프로젝트
698
34%
중재
33
70%
/
9%
기한 초과
22
3%
무료
3
등급
프로젝트
0
0%
중재
5
0%
/
80%
기한 초과
0
무료
4
등급
프로젝트
19
42%
중재
3
0%
/
67%
기한 초과
3
16%
무료
5
등급
프로젝트
474
39%
중재
103
41%
/
23%
기한 초과
79
17%
바쁜
게재됨: 2 코드
6
등급
프로젝트
243
74%
중재
7
100%
/
0%
기한 초과
1
0%
무료
게재됨: 1 기고글
7
등급
프로젝트
5
0%
중재
2
50%
/
50%
기한 초과
2
40%
무료
8
등급
프로젝트
0
0%
중재
0
기한 초과
0
무료
9
등급
프로젝트
121
68%
중재
5
80%
/
0%
기한 초과
12
10%
무료
10
등급
프로젝트
54
61%
중재
2
50%
/
50%
기한 초과
0
무료
11
등급
프로젝트
945
47%
중재
309
58%
/
27%
기한 초과
125
13%
무료
12
등급
프로젝트
1
0%
중재
0
기한 초과
0
무료
비슷한 주문
Ninjatrader 8 indicator modification
100+ USD
attached is an nt8 indicator i would like modifications to. this will not be simple. once you review the indicator you will see it prints arrows and dots. the arrows print after the dots stop forming. i am using default settings, on the instrument es, using ninza renko 8:4 i want the arrow to be placed on the first dot. i do not want the arrow to just be backpainted into the past much like a swing indicator or
We are looking for an experienced TradingView / Technical Analysis expert who can suggest and build the best combination of indicators for a profitable and structured trading strategy. This is not about random indicator stacking. We need someone who understands market structure, confirmation logic, risk management, and strategy optimization. The goal is to create a clean, high-probability setup with minimal false
Indicator
100+ USD
Does anyone know what indicator this is on the image because I'm looking for something like this but just a bit more sensitive. Speaking about the diamonds all the rest is irrelevant
Hello . Hello I already have an indicator on TradingView written in Pine Script. I need some modifications and fixes for the existing indicator. The indicator sometimes gives wrong signals and I want to improve it. I will provide the Pine Script source code. The developer should check the code, fix the problems, and adjust the logic if needed
DO NOT RESPOND TO WORK WITH ANY AI. ( I CAN ALSO DO THAT ) NEED REAL DEVELOPING SKILL Hedge Add-On Rules for Existing EA Core Idea SL becomes hypothetical (virtual) for the initial basket and for the hedge basket . When price hits the virtual SL level , EA does not close the losing trades. Instead, EA opens one hedge basket in the opposite direction. Original basket direction Hedge basket direction (opposite) Inputs
DOUBLE STEP MA WITH SUPERTREND
60+ USD
Kindly see details below BUY ALERT 1. Supertrend turns Bullish 2. On this candle , or the last 10, BBStops is Bearish 3. On this candle , or the last 10, price was < or = MA1 4. Instrument is in trend (STEP MA1 and STEP MA 2 are both Bullish) 5. Distance in pips between Lowest price during last time BBstop was Bearish, and the value of Step MA 1 at last bearish candle of Step MA1
EA requirements and necessary correction to be done . The EA monitors the PROFIT of open positions and turns ON or OFF the ALGO TRADING accordingly. By PROFIT I mean the SUM of profit + commission + swap. The EA will have two strategies, the INITIAL and the SECONDARY. Each one of them will be selectable by the user in the EA inputs. Let me explain here how the EA will operate: 1. INITIAL strategy: ·
Hello, I have a breakout EA with reversal logic. I own the full source code for both MT4 and MT5 versions. I need the modifications implemented for both MT4 and MT5 versions. I need several modifications: – Multiple reversals with configurable parameters – Breakeven functionality – Entry only after candle close beyond range + offset – Time-based activation – Alternative offset calculation logic – Automatic close at
Hi I have a simple task (hopefully) I have a custom strategy that I built with the help of Claude Anthropic - everything is finished and I zipped it with power shell but when importing it NT8 gives me the error message that the file was made from an older, incompatible version or not a NinjaScript. My folder structure is correct as far I can see so I don't know what the issues is and it's costing me too much to go
Subject: Development of Ultra-High Precision Confluence Indicator - M1 Binary Options (Non-Repaint) Hello, I am looking for a Senior MQL5 Developer to create a custom "Surgical Precision" indicator for MetaTrader 5, specifically optimized for 1-minute (M1) Binary Options trading. The system must integrate three distinct layers of algorithmic analysis. 1. Core Logic: Triple-Layer Confluence The signal (Call/Put)
프로젝트 정보
예산
30+ USD
기한
에서 1 로 3 일