TPD Feedback and Issues
Unfortunately we will not be able to provide GPS data from Sedgefield today. One of our Course Operators has suffered some sort of medical emergency and is on his way to hospital. I am told nothing too serious but obviously puts him out of action for a little while.
- jamesedwards
- Posts: 3583
- Joined: Wed Nov 21, 2018 6:16 pm
Working fine this morning. Even if Betfair aren't.TPD-Zone wrote: ↑Wed Dec 04, 2024 2:28 pmAn update re Jebel Ali - this is a long, protracted story but the short version is as follows. A senior member of the Jebel Ali course management team would not let the requisite tracking equipment (radio masts, repeaters etc.) be installed at the locations which would provide optimum transmission of the GPS data. We believe that the "dispute" has now been resolved and all should be fine for the next meeting.

Happy to report that the issue has been resolved. Somehow the Betfair marketids were being corrupted in our system tables. Apologies for the inconvenience.
- jamesedwards
- Posts: 3583
- Joined: Wed Nov 21, 2018 6:16 pm
It's been exactly a year since my last significant TPD related loss due to transponder error. (touch woodTPD-Zone wrote: ↑Wed Jun 26, 2024 3:49 pmTo add more detail; we receive error codes from the source data supplier (Gmax in most instances). The TPD Developers have amended the API such that a warning field can contain one of three warning values and Bet Angel transacts that information as appropriate. I have reached out to our Developers and asked them to provide the precise details of how the Gmax error codes translate to that which the Bet Angel platform is picking up from the API. Will post in here when I have the answer and feed into the documentation.

The introduction of the transponder swap alert has made a significant different to overall profitability. Thanks to all who were part of it.