Pages:
Actions
  • #1 by binsey on 18 Jan 2014
  • Hi , is there anyway to make my stop loss a bit less" twitchy ". I want it to only kick in if a selections price has risen above ( bm_backp*1.2 ) for more than 2 seconds before it fires rather than the instant that price has been reached in the market.
    Any help would be most gratefully received.
  • #2 by MarkV on 19 Jan 2014
  • Hi
    In the attached file:
    remember when the condition is met the first time
    delay 2 seconds
    check the condition a second time in the stoploss

    In the trigger file I have used Write to Action Log. You need to make this your stoploss trigger using the conditions as shown. You should also define your selection.
    There is a constant you can set for the delay.

    Please test it in test mode.  


  • #3 by binsey on 19 Jan 2014
  • Brilliant, many thanks. :)
  • #4 by binsey on 20 Jan 2014
  • Hi, I've incorporated this into my trigger but the stop loss doesn't seem to fire no matter how much I tweak the timing- could you take a look at it for me .. Many thanks
  • #5 by mcbee on 20 Jan 2014
  • hi
    the trigger   This will be your stoploss trigger - use the conditions as shown
    has a condition that is NOT complete

    Trigger Unknown number of runs is greater that 0

    where is says   Unknown   you need to add the triggers name

    it should be

    and trigger Check stoploss 1st time number of runs is greater that 0


    mcbee
  • #6 by MarkV on 20 Jan 2014
  • Hi
    Please try the attached amended trigger file in test mode.
    I have added some additional relevant conditions now I can see the context of the stoploss usage.

    Just a note on testing observation. Where the price moves very quickly towards the end of a race, the delay and the second check works against you. By the time the second check is completed and the stoploss fires, the lay prices are sometimes around 500 or higher. I would say this trigger will work better in longer length races.
Pages:
Actions