Slow Results Sheet

[Royville]

Hi,

I am trying out the Betdaq version and finding it ok, except that the Results sheet takes forever to update. The next race starts before the last race results get updated. Is this a problem or am I missing some setting or something?

Please help

Thanks
Royville

[osknows]

Hi Roy,

I think that's by design as it's the same on BA for Betfair. The result sheet normally only refreshes when the market forwards or if it's forced using -6 in cell Q2. I'm sure Gary will correct me if I'm wrong.

[Royville]

Hi Osknows

Yes, I am sending -6 to cell Q2 on sheet 1 every 5 seconds, so I thought it would update quite quickly after the finish of the race.

I wonder if there any other methods one could use to check the outcome of a race straight after the finish?

Any ideas?

Regards
Royville

[GaryRussell]

Hi Osknows

Yes, I am sending -6 to cell Q2 on sheet 1 every 5 seconds, so I thought it would update quite quickly after the finish of the race.

I wonder if there any other methods one could use to check the outcome of a race straight after the finish?

Any ideas?

Regards
Royville

I don't recommend using -6 every 5 seconds. It's not designed handle that and you risk getting your requests throttled by Betdaq's server. Maybe this is happening because it should be updated before the next race. I wouldn't expect this method to be very reliable in the Betfair version either. It's only intended to be used occasionally, ie. every 5 minutes or so.

[GaryRussell]

Just had an idea. I could optimise it to only requests details from the API for the first bet. If this is unsettled it follows the rest will be so it doesn't need to request those. It will possibly be ok to call every 5 seconds then. Leave it with me.

[Royville]

Hi Garry,

Thanks for that, I never realised I could actually be making it worse by sending -6 every 5 sec's. I'll stop immediatly and await your recomendation.

Many thanks
Royville

[BERTRAND]

Hi Osknows

Yes, I am sending -6 to cell Q2 on sheet 1 every 5 seconds, so I thought it would update quite quickly after the finish of the race.

I wonder if there any other methods one could use to check the outcome of a race straight after the finish?

Any ideas?

Regards
Royville

I don't know how critical the previous result is to your strategy, but you can be better than 99% certain that the "last matched price" after suspension will reveal the winner. You can use this knowledge to update a virtual bank and trigger from this virtual bank.
I have my sheet to auto lay bet and If my selection has a "last price matched" of more than $5 (takes care of most photo finnishes)then my virtual bank gets updated with a win automatically. I am trying to figure out a way for a correction to be made after settlement if my system was wrong (very rare).
Bert

[GaryRussell]

I have optimised the retrieval of settlement information. If a bet has already been checked from the same market and it is unsettled then it will assume the remaining bets for the same market are unsettled instead of making additional API calls. Please try it out and let me know if it helps.

Uninstall and install version 1.0.7.4 from the link below.
http://www.gruss-software.co.uk/BA_Betd ... etdaq2.msi

[Royville]

Hi Gary,

Thank you for such a quick response. I will install and try out the new version today and report back later.

Kind regards
Royville.

[Royville]

Hi Gary,

My strategy only produced one bet yesterday, but it did seem to update the result a lot quicker than it had been doing. So it does look like it may be an improvement.

Ill keep an eye on it and report back after a few days.

Many thanks
Royville

[Royville]

Hi

I think there is a definate improvement in the updating of results Gary, but I am still (occasionaly) getting the situation where the next race starts before the last result is known.

It would be really useful to find a solution for this.

Is there any other way around the problem?

Regards
Royville

[GaryRussell]

If it's not known it's because they haven't settled the market. There aren't any instant result services available to us so I'm afraid we cannot solve that issue.