|
|
Home
Search
Register
Login
Recent Posts
»Forums Index
»Archive (2017 and earlier)
»Data and Content Support
» errors when trying to get @RA#C and @TU#C historic 1min bars
|
|
| Author | Topic: errors when trying to get @RA#C and @TU#C historic 1min bars (3 messages, Page 1 of 1) |
 Skaarj -Interested User- Posts: 11 Joined: Jul 10, 2014 |
Posted: Feb 15, 2019 08:50 AM
Msg. 1 of 3
When I try to request historic data for @RA#C and @TU#C it returns only part of bars and then raise "Connection Timeout Error".
I send: HIT,@TU#C,60,20190101 000000,20190214 235959,,,,1,H_0000000000,100,s HIT,@RA#C,60,2070101 000000,20190214 235959,,,,1,H_0000000000,100,s For @TU#C I've got a break at: H_0000000000,2019-01-11 16:58:00,106.0234375,106.0234375,106.0234375,106.0234375,333164,22, H_0000000000,E,Connection Timeout Error., H_0000000000,!ENDMSG!, H_0000000000,2019-01-11 17:00:00,106.0312500,106.0156250,106.0312500,106.0234375,333993,829, For @RA#C: H_0000000000,2008-06-13 10:26:00,123349.9344,123349.9344,123349.9344,123349.9344,31,1, H_0000000000,E,Connection Timeout Error., H_0000000000,!ENDMSG!, H_0000000000,2008-06-13 10:27:00,123349.9344,123349.9344,123349.9344,123349.9344,35,4, |
|
DTN_Steve_S -DTN Guru- Posts: 2091 Joined: Nov 21, 2005 
|
Posted: Feb 18, 2019 08:44 AM
Msg. 2 of 3
Sorry for the delay responding here.
I'm not finding an API account for you based on your info in your forum account. If you would like to PM me your account info I can provide better info (or email dev support). With that said, my best guess without being able to check anything else would be to make sure you are running the latest beta version posted on the website (if you haven't already). There are changes in that version that help support @TU contracts. |
|
Skaarj -Interested User- Posts: 11 Joined: Jul 10, 2014 |
Posted: Feb 19, 2019 04:35 AM
Msg. 3 of 3
Thanks, upgarding from 6.0.0.5 to 6.0.1.1beta helps.
|
|
|