If you can tell me exactly what part of signals is unclear I could maybe point you at some instructions/examples, but here are few links (which you may or may not have seen)
viewtopic.php?f=37&t=11941
viewtopic.php?f=43&t=11943
It also starts on this page of the user guide
https://www.betangel.com/user-guide/usi ... 3D&mw=MzIw
All the conditions (unmatched bets etc) are working fine and as they should be, until a bet/s is showing in the market and that info is returned by BF they will not be able to see if a bet has been matched or is still unmatched.
Did you try adding the Fill or Kill bet time condition I advised in my first reply?
https://www.betangel.com/user-guide/fil ... 3D&mw=MzIw
That sets locally so won't allow another bet within the time you set, so you could set the condition to
Greater than 2 secs, that will be plenty of time for the bet info to be retrieved so your matched/unmatched conditions can then take over
BA too fast for its own good...
- Kafkaesque
- Posts: 886
- Joined: Fri Oct 06, 2017 10:20 am
As I mentioned in a reply, the fill or kill bet time was a great shout in most cases. However, a rather big part in my strategy requires dripping into the market in many cases. Thus it's really a no go for me.Dallas wrote: ↑Tue Mar 27, 2018 11:56 pmIf you can tell me exactly what part of signals is unclear I could maybe point you at some instructions/examples, but here are few links (which you may or may not have seen)
viewtopic.php?f=37&t=11941
viewtopic.php?f=43&t=11943
It also starts on this page of the user guide
https://www.betangel.com/user-guide/usi ... 3D&mw=MzIw
All the conditions (unmatched bets etc) are working fine and as they should be, until a bet/s is showing in the market and that info is returned by BF they will not be able to see if a bet has been matched or is still unmatched.
Did you try adding the Fill or Kill bet time condition I advised in my first reply?
https://www.betangel.com/user-guide/fil ... 3D&mw=MzIw
That sets locally so won't allow another bet within the time you set, so you could set the condition to
Greater than 2 secs, that will be plenty of time for the bet info to be retrieved so your matched/unmatched conditions can then take over
I'll have a go at signals and see if I can set something up which solves it.
And don't you worry.....although I can't say what gets me, just yet, but I'll give a shout when I get to the part of signals which get me stuck First part was to stop just jumping into trying to have a go, and actually read, as I for the first few frustrating attempts was assuming that the signal needed setting within the existing rules.
Out of sheer curiousity, do you have an official role with BA, or are you a super helpful automation whiz kid? Been meaning to ask forever, and don't think I've ever seen it mentioned on here.
- Kafkaesque
- Posts: 886
- Joined: Fri Oct 06, 2017 10:20 am
Okay, that was a bit easier to set up than I expected. Actually quite a bit easier!!!Dallas wrote: ↑Tue Mar 27, 2018 11:56 pmIf you can tell me exactly what part of signals is unclear I could maybe point you at some instructions/examples, but here are few links (which you may or may not have seen)
viewtopic.php?f=37&t=11941
viewtopic.php?f=43&t=11943
It also starts on this page of the user guide
https://www.betangel.com/user-guide/usi ... 3D&mw=MzIw
All the conditions (unmatched bets etc) are working fine and as they should be, until a bet/s is showing in the market and that info is returned by BF they will not be able to see if a bet has been matched or is still unmatched.
Did you try adding the Fill or Kill bet time condition I advised in my first reply?
https://www.betangel.com/user-guide/fil ... 3D&mw=MzIw
That sets locally so won't allow another bet within the time you set, so you could set the condition to
Greater than 2 secs, that will be plenty of time for the bet info to be retrieved so your matched/unmatched conditions can then take over
And at first glance it looks to work an absolute charm. Thanks Dallas (and Shaun, despite me not taking the advice at first )