My version got 17pips yesterday during the last upswing, now flat. The version of Nonethless suffered an SL in the last trade, also now flat. Wait for the next upswing.
which version of yours Phoentzs? Some you already shared or some version u can share?
A version that I didn’t share, but that is based on the description from this post onwards. Plus a trailing SL.
Breakout M5 / H4 Nasdaq
Did u made a short version of this code phoentzs? Something u would share?
Yes, I have a short version running in demo. But I’m on the move at the moment. You are welcome to contribute your ideas.
“You are welcome to contribute your ideas.”
Well put, I’ll start trying out a short version and post it here if I have any success. Thanks again for sharing the initial idea.
No coder but Ill make it a try 🙂
Feel free make this version better:
//Break-H4 Nasdaq M5
//================================================
DEFPARAM CUMULATEORDERS = false
defparam preloadbars = 5000
//Risk Management
PositionSize=1
timeframe(4hour, updateonclose)
barCount = barIndex
D1 = low
D2 = (Close < Open) //green
D3 = (Close > Open) //red
D4 = (low < low[1])//lowerhigh
D5 = (low > low[1])//higherhigh
//MACDLiniex = MACDline[12,26,9](close) > 0
MA5xx = Average[3,1](typicalprice) //close
MA10xx = Average[10,1](typicalprice) //close
MA15xx = Average[15,1](typicalprice) //15,1 close
myshortx = MA15xx < MA15xx[1]
timeframe(default)
once tradeOn = 1
if intradayBarIndex = 0 then
tradeOn = 1
endif
tradeBar = barCount
if not onMarket and tradeBar<>tradeBar[1] then
tradeOn = 1
endif
//Volaititätfilter
AvgRange = average[20,0](range)
TradeOFF = range > (AvgRange * 3) //no trading if the current range > twice its average //3
// trading window
ONCE BuyTime = 080000
ONCE SellTime = 215500
// position management
IF Time >= BuyTime AND Time <= SellTime THEN
If close crosses under D1 and myshortx and D3 and tradeOn Then //and not c5
sellshort PositionSize CONTRACTS AT MARKET
SET STOP %LOSS 0.9 //100
SET TARGET %PROFIT 1 //125
tradeOn = 0
ENDIF
If close crosses under D1 and myshortx and D2 and tradeOn Then
sellshort positionsize CONTRACTS AT MARKET
SET STOP %LOSS 0.8 //100
SET TARGET %PROFIT 1 //125
tradeOn = 0
ENDIF
endif
////////FOR STOPLOSS MANNGEMENT
startBreakeven = 35
PointsToKeep = 52
once breakeven = 1//1 on - 0 off
//reset the breakevenLevel when no trade are on market
if breakeven>0 then
IF NOT ONMARKET THEN
breakevenLevel=0
ENDIF
// --- BUY SIDE ---
//test if the price have moved favourably of "startBreakeven" points already
IF LONGONMARKET AND close-tradeprice(1)>=startBreakeven THEN
//calculate the breakevenLevel
breakevenLevel = tradeprice(1)+PointsToKeep
ENDIF
//place the new stop orders on market at breakevenLevel
IF breakevenLevel>0 THEN
SELL AT breakevenLevel STOP
ENDIF
// --- end of BUY SIDE ---
IF SHORTONMARKET AND tradeprice(1)-close>startBreakeven THEN
//calculate the breakevenLevel
breakevenLevel = tradeprice(1)-PointsToKeep
ENDIF
//place the new stop orders on market at breakevenLevel
IF breakevenLevel>0 THEN
EXITSHORT AT breakevenLevel STOP
ENDIF
endif
if time = 220000 and dayofweek=5 and (PositionPerf * PositionPrice / PipSize) >= 5 then //
EXITSHORT AT Market
endif
Short on Nasdaq is difficult. I have a reasonably reasonable version on Dax Short. But still see if she really works. In the chart, it looks easy if you are manually. It is automatically difficult.
Är u running this in m3?
TEST-Break-H4-Nasdaq-M5.itf
Long works well in M5, M3 better and M1 even better. But only with trailing stop.
witch cind of trailing stop?
once trailingstopPC = 1 // Percentage TS, includes break even function
once enableBreakEven = 1 //Break even, can be used in conjunction with ATR TS
once trailingstopATR = 1 //ATR TS
once trailingstopRTS = 1 //RobertoGozzi trailing stop
You can only use a trailing stop. It is possible that exist in my trial versions several breakbacks or trailing stops. What you do not use do you have to comment.
Here is my 1st attempt NASDAQ Short with this strategy. I created in the M5, but maybe even better in M3 or even M1. I have to say, I am positively surprised how well it seems to work. Maybe another work.
@nonethleess: Do you have time to try your knowledge here again?
Maybe one more question for the great masters … Nicolas? Robertogozzi? If you manage entries from large time units with a trailing stop … which TF is best used for this? M1… 5? Is more data history better or faster reaction to a trailing stop?
I did some backtests and think M3 i best so far
