Gianluca wrote:

but i ask for a check because somethimes in my algos there is some problems with it

Do you have problems with all 4 x TS Codes or just one specific TS Code?

@Gianluca make sure the trailing stop is above the breakeven. Makes a difference too.

Using above codes, then you have to use “not on market” as entry condition.

However, if you have long position and get a short signal you want to reverse immediately right, but that maybe get’s skipped now since it’s waiting for the active trade to first hit a target (stoploss, trailing-stop, breakeven etc) because of “not on market” condition.

If you use those codes, and do not use “not on market” as entry criteria, you may get unexpected results.

That’s an issue and influences WF and optimisation results. I think it creates fake WF results! (but perhaps looking nicer)

Hi Paul, I wonder wether you can help here – I’ve coded the below as far as I can get but seem to be just missing one minor detail! I’m Still working on a way to combine a trailing stop with a trailing step that becomes a fixed stop – i.e Trade is a buy open with a 10pt stop, if it moves 2 up, your stop is now 8, if it moves another 2, it’s now 6 but when it gets to 10, so break even on a 1-1, it becomes fixed. Currently I only get a trailing to stop at breakeven, so still risking the full 10.

I notice that with this although I’m getting the result of the trailing stop at breakeven which is great, the trailing stop still seems to be live with a step as the deal closes sometimes later at 25 or 35 or 45 etc…great problem to have but not what I want as I lose on bigger moves.

Adding a trailing stop after the first one becomes fixed would be the next part, so if it moves another 30 pts you bank another 10 for example. I’m thinking this is a simple code tweak..? Code below, perhaps you can help me..?

// Definition of code parameters
DEFPARAM CumulateOrders = False // Cumulating positions deactivated

// Prevents the system from creating new orders to enter the market or increase position size before the specified time
noEntryBeforeTime = 143000
timeEnterBefore = time >= noEntryBeforeTime

// Conditions to enter long positions
indicator1 = SuperTrend[4,90]
c1 = (close CROSSES OVER indicator1)

IF c1 AND timeEnterBefore THEN
BUY 10 PERPOINT AT MARKET

ENDIF

// Conditions to exit long positions
indicator2 = SuperTrend[4,90]
c2 = (close CROSSES UNDER indicator2)

IF c2 THEN
SELL AT MARKET
ENDIF

// Conditions to enter short positions
indicator3 = SuperTrend[4,90]
c3 = (close CROSSES UNDER indicator3)

IF c3 AND timeEnterBefore THEN
SELLSHORT 10 PERPOINT AT MARKET

ENDIF

// Conditions to exit short positions
indicator4 = SuperTrend[4,90]
c4 = (close CROSSES OVER indicator4)

IF c4 THEN
EXITSHORT AT MARKET
ENDIF

//reset the breakevenLevel when no trade are on market
IF NOT ONMARKET THEN
breakevenLevel=0
ENDIF

// Stops and targets
SET STOP pTRAILING 20

//place the new stop orders on market at breakevenLevel
IF breakevenLevel>0 THEN
SELL AT breakevenLevel STOP
ENDIF

do you use all 4 codes in the same strategy? or only 1 code in 1strategie?

nonetheless wrote:

Should I have ‘not onmarket’ in the entry conditions? I’ve tried it with and without but back test results are identical.

Hi, I don’t prefer that. When optimising for good signals, all signals should have value, regardless if there’s a position in opposite direction or not.

You could try this, made it a bit as my other trailing stops. Tested with not onmarket  and without in entry conditions and have different results.

// %trailing stop function
once trailingstoptype     = 1   // trailing stop - 0 off, 1 on

once trailingpercent      = 0.3 //trailing will start @trailingstart points profit
once steppercent          = 0.1 //% step to move the stoploss

once sensitivityts        = 1   // [0]close;[1]high/low
//
if trailingstoptype then

if onmarket then
trailingstart =tradeprice(1)*(trailingpercent/100) 
trailingstep = tradeprice(1)*(steppercent/100)
endif
 
//reset the stoploss value
if not onmarket or ((longonmarket and shortonmarket[1]) or (longonmarket[1] and shortonmarket)) then
newsl=0
endif
//
if sensitivityts then
sensitivitytslong=high
sensitivitytsshort=low
else
sensitivitytslong=close
sensitivitytsshort=close
endif

//manage long positions
if longonmarket then
//first move (breakeven)
if newsl=0 and sensitivitytslong-tradeprice(1)>=trailingstart then
newsl = tradeprice(1)+trailingstep
endif
//next moves
if newsl>0 and close-newsl>trailingstep then
newsl = newsl+trailingstep
endif
endif
 
//manage short positions
if shortonmarket then
//first move (breakeven)
if newsl=0 and tradeprice(1)-sensitivitytsshort>=trailingstart then
newsl = tradeprice(1)-trailingstep
endif
//next moves
if newsl>0 and newsl-close>trailingstep then
newsl = newsl-trailingstep
endif
endif
 
if longonmarket then
if newsl>0 then
sell at newsl stop
endif
if newsl>0 then
if low crosses under newsl then
sell at market //when stop is rejected
endif
endif
endif
//
if shortonmarket then
if newsl>0 then
exitshort at newsl stop
endif
if newsl>0 then
if high crosses over newsl then
exitshort at market //when stop is rejected
endif
endif
endif
endif

edit…