Pages:
Actions
  • #1 by Orzola on 22 Apr 2013
  • I think I must be missing something fundamental, because I can't get the most basic cancelling trigger to work.

    All I am trying to do is cancel all bets except those within two ticks of the back or lay price.  So to test that function I manually placed £2 lay bets at 2.94 through to 3.1 and £2 back bets at 3.25 through to 3.55.  Back price and lay price were 3.15~3.25 at the time.  So there were plenty of bets to cancel.

    Then I ran the attached trigger which simply cancels all bets but uses cancel options to keep those priced between r_ticks(back_price,-2) and r_ticks(lay_price,2).

    The bets did not cancel and MF7 stopped responding.  I closed and re-opened MF7.  there was nothing in the Program Log.  The bets were still there, unmatched.  I attach the trigger log.

    I have had similar problems with cancel functions before - hence my testing today.  Previously, either the same thing as today has happened or there has been an "Abnormal program termination" and/or an "Error getting funds at BF" message in the Program Log.

    Any help would be greatly appreciated.
  • #2 by mcbee on 22 Apr 2013
  • hi
    your trigger is set to cancel between r_ticks(back_price,-2) and r_ticks(lay_price,2)

    the KEPT is only for the bet setting kept=keep bets in play , canceled=cancel bets at in play
    you should put
    lay_price<r_ticks(back_price,-2) and lay_price>r_ticks(lay_price,2)

    mcbee
  • #3 by Orzola on 22 Apr 2013
  • Thanks again.
    That explains why nothing cancelled.  The bets would have all have had cancel at in play persistence.
    But does it make sense to you that MF7 would stop responding/crash.  I would have expected just nothing to happen.
  • #4 by Oxa (WellDoneSoft) on 22 Apr 2013
  • What mcbee said, plus there is an error in the trigger expression in the cancel options, the second formula is r_ticks(lay_price,2)1000, the "1000" is probably left from the default value.

    However this does not explain the program termination. Hold on, let me look into it for you, will post again later...
  • #5 by Orzola on 22 Apr 2013
  • Thanks Oxa
    I removed the schoolboy errors and tried a similar cancel back trigger which worked fine on the cancellation but then crashed again after 90 seconds, so I think there is an issue lurking beneath.
  • #6 by Oxa (WellDoneSoft) on 22 Apr 2013
  • Orzola, this is indeed a bug in the Cancel Options. Thanks for helping spot it. I'm preparing a fix, until then you could play with the conditions to work around the cancel options.
    Sorry for the inconvenience.
  • #7 by Oxa (WellDoneSoft) on 08 May 2013
  • Orzola,

    The problem should be gone with the new program's update. Please read here and upgrade.
Pages:
Actions