Support Board
Date/Time: Thu, 28 Nov 2024 10:46:38 +0000
how to assign a new live funded trade account?
View Count: 462
| [2023-05-02 16:32:20] |
| User85195 - Posts: 60 |
|
I've a live funded account with AMP and I've already assigned it as my live trading account so that I can access real time trading data from the exchanges. however I'm having problem with AMP and I'm now unable to log into my AMP live trading account. as a result, I've been receiving delayed date feed for the last few days. I have another live funded trading account with IB, and I've logged into it from sierrachart, but my data feed is still delayed. what is the reason for this delay? do I need to assign IB as my live trading account? if so, please give me a link to do so. I've searched but couldn't find it anywhere in my account page. |
| [2023-05-02 17:30:34] |
| John - SC Support - Posts: 36350 |
|
Everything on your account looks good, so you should be getting real-time data for the CME Group. Make sure that you have the correct symbols since you switched to IB. Open your chartbooks and select "Edit >> Translate Symbols to Current Service". If you are still having an issue after this, then we would need to see your Message Log by following these instructions: Follow the instructions here to clear the Message Log: Message Log: Clearing the Message Log Open a chart for the symbol you have an issue with. Tell us that symbol of the chart. Tell us about *one* symbol only. Disconnect from the data feed with "File >> Disconnect". Connect to the data feed with "File >> Connect to Data Feed". After the connection and after about 10 seconds, provide a copy of the Message Log following these instructions: Support Board Posting Information: How to Post Your Message Log (Required In Some Cases) We will then determine what the problem is. For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2023-05-03 13:44:12] |
| User85195 - Posts: 60 |
|
the symbol is: MNQM3.cme I have both SC and Rtraderpro open, the data feed in SC is a few minutes late for some reason. but the timestamp is the same in both platforms. Software version: 2497 64-bit | 2023-05-03 22:39:56.074 Primary Thread ID: 14296 | 2023-05-03 22:39:56.074 Usage end date: 2023-09-05 | 2023-05-03 22:39:56.074 Enabled for: Sierra Chart Historical Data Service. | 2023-05-03 22:39:56.074 Enabled for: Denali Real-Time Exchange Data Feed. | 2023-05-03 22:39:56.074 Enabled for: Delayed Denali Exchange Data Feed. | 2023-05-03 22:39:56.074 Enabled for exchange2: CME (Trading Account Required) | 2023-05-03 22:39:56.074 Enabled for exchange2: CBOT (Trading Account Required) | 2023-05-03 22:39:56.074 Enabled for exchange2: COMEX (Trading Account Required) | 2023-05-03 22:39:56.074 Enabled for exchange2: NYMEX (Trading Account Required) | 2023-05-03 22:39:56.074 Enabled for exchange2: fairx_exchange.data | 2023-05-03 22:39:56.074 Allow Support for Sierra Chart Data Feeds is enabled. | 2023-05-03 22:39:56.074 Current selected Data/Trading service: Rithmic Direct - DTC | 2023-05-03 22:39:56.074 Custom symbol settings values: enabled | 2023-05-03 22:39:56.074 Chart Update Interval: 100 | 2023-05-03 22:39:56.074 Intraday Data Storage Time Unit: 0 | 2023-05-03 22:39:56.074 Time Zone: +09:00:00 (JST+09) | 2023-05-03 22:39:56.074 2023-05-03 13:39:56 Local computer time in UTC | 2023-05-03 22:39:56.074 2023-05-03 22:39:56 Local computer time in SC Time Zone | 2023-05-03 22:39:56.074 2023-05-03 09:53:10 Server time in UTC | 2023-05-03 22:39:56.074 Local computer UTC time and Server UTC time difference: 4 seconds. | 2023-05-03 22:39:56.074 Program path: D:\Trading\APEX\ | 2023-05-03 22:39:56.074 Data Files path: D:\Trading\APEX\Data\ | 2023-05-03 22:39:56.074 OS Version Number: 10.0 | 2023-05-03 22:39:56.075 Locale Setting: C | 2023-05-03 22:39:56.075 DLLs: DelayedOrNot_64.dll, UserContributedStudies.dll, UserContributedStudies_64.dll | 2023-05-03 22:39:56.075 Allowed protected custom studies: | 2023-05-03 22:39:56.075 Crash reporter started: true | 2023-05-03 22:39:56.075 File >> Disconnect selected. | 2023-05-03 22:39:58.511 Rithmic Direct - DTC | Waiting for socket receive thread to end | 2023-05-03 22:39:58.512 DTC Client socket (1) | CloseSocket call. | 2023-05-03 22:39:58.512 DTC Client socket (1) | Max send buffers used during socket life: 4 | 2023-05-03 22:39:58.512 DTC Client socket (1) | Max send buffer size during socket life: 637 | 2023-05-03 22:39:58.512 DTC Client socket (1) | Shutdown started. Waiting for graceful close. | 2023-05-03 22:39:58.512 Denali Data Feed | Waiting for socket receive thread to end | 2023-05-03 22:39:58.512 DTC Client socket (3) | CloseSocket call. | 2023-05-03 22:39:58.513 Denali Data Feed | Disconnected from the server. | 2023-05-03 22:39:58.513 Rithmic Direct - DTC | Disconnected. | 2023-05-03 22:39:58.513 DTC Client socket (3) | Shutdown started. Waiting for graceful close. | 2023-05-03 22:39:58.513 DTC Client socket (1) | Socket gracefully closed by remote side. | 2023-05-03 22:39:58.772 DTC Client socket (1) | Closed. | 2023-05-03 22:39:58.772 Rithmic Direct - DTC | Using server connection: Apex-Chicago Area-Non-Aggregated | 2023-05-03 22:40:01.418 Rithmic Direct - DTC | Connecting to the server rsc.rithmic.com. Port 50528 | 2023-05-03 22:40:01.418 DTC Client socket (1) | Creating socket. Using TLS 1.2. | 2023-05-03 22:40:01.421 DTC Client socket (1) | New receive buffer size: 5242880 | 2023-05-03 22:40:01.421 DTC Client socket (1) | Connecting to IP: 216.57.156.163. | 2023-05-03 22:40:01.421 Rithmic Direct - DTC | Network connection to server complete. | 2023-05-03 22:40:01.673 Rithmic Direct - DTC | Starting socket receive thread. | 2023-05-03 22:40:01.673 Rithmic Direct - DTC | Setting DTC encoding to Binary | 2023-05-03 22:40:01.673 Rithmic Direct - DTC | Sending logon request message. | 2023-05-03 22:40:01.673 Rithmic Direct - DTC | Received logon response. | 2023-05-03 22:40:03.205 Rithmic Direct - DTC | Server Name: . | 2023-05-03 22:40:03.205 Rithmic Direct - DTC | Server protocol version: 8. Client protocol version: 8 | 2023-05-03 22:40:03.205 Rithmic Direct - DTC | Successfully connected. | 2023-05-03 22:40:03.205 Rithmic Direct - DTC | Trading is supported. | 2023-05-03 22:40:03.205 Rithmic Direct - DTC | Order cancel and replace is supported. | 2023-05-03 22:40:03.205 Rithmic Direct - DTC | OCO Orders supported. | 2023-05-03 22:40:03.205 Rithmic Direct - DTC | Symbol and Exchange Delimiter: . | 2023-05-03 22:40:03.205 Rithmic Direct - DTC | Connected to server complete. | 2023-05-03 22:40:03.205 Triggering next historical data download in queue. | 2023-05-03 22:40:03.206 Triggering next historical data download in queue. | 2023-05-03 22:40:03.206 Triggering next historical data download in queue. | 2023-05-03 22:40:03.206 Triggering next historical data download in queue. | 2023-05-03 22:40:03.206 No download requests in the queue to start downloads for. | 2023-05-03 22:40:03.208 No download requests in the queue to start downloads for. | 2023-05-03 22:40:03.208 No download requests in the queue to start downloads for. | 2023-05-03 22:40:03.208 No download requests in the queue to start downloads for. | 2023-05-03 22:40:03.208 Mapping MNQM3.CME to MNQM23. Service code: cme | 2023-05-03 22:40:03.248 Using symbol data fast lookup vector | 2023-05-03 22:40:03.248 Denali Data Feed | Starting real-time market data updates for: MNQM3.CME (MNQM23). ID: 1 Service code: cme | 2023-05-03 22:40:03.248 Denali Data Feed | Connecting to the server ds28.sierracharts.com. Port 10048 | 2023-05-03 22:40:03.248 Denali Data Feed | Requesting security definition data for: MNQM3.CME (MNQM23). ID: 1 | 2023-05-03 22:40:03.248 DTC Client socket (2) | Creating socket. | 2023-05-03 22:40:03.252 DTC Client socket (2) | New receive buffer size: 5242880 | 2023-05-03 22:40:03.252 DTC Client socket (2) | Connecting to IP: 142.215.18.147. | 2023-05-03 22:40:03.252 Added historical Intraday data request for MNQM3.CME to the queue. | 2023-05-03 22:40:03.255 Intraday data recording state for symbol MNQM3.CME is set to download 'Pending'. | 2023-05-03 22:40:03.255 Triggering next historical data download in queue. | 2023-05-03 22:40:03.255 Delaying start of download for MNQM3.CME. | 2023-05-03 22:40:03.266 Denali Data Feed | Network connection to server complete. | 2023-05-03 22:40:06.483 Denali Data Feed | Starting socket receive thread. | 2023-05-03 22:40:06.483 Denali Data Feed | Sending encoding request to server: Binary VLS. Compression: standard | 2023-05-03 22:40:06.483 Denali Data Feed | Setting DTC encoding to Binary VLS | 2023-05-03 22:40:06.749 Denali Data Feed | Sending logon request message. | 2023-05-03 22:40:06.749 Requesting market depth updates for: MNQM3.CME if supported. | 2023-05-03 22:40:08.233 Separate subscription for market depth updates not supported. MNQM3.CME | 2023-05-03 22:40:08.233 Denali Data Feed | Received logon response. | 2023-05-03 22:40:10.124 Denali Data Feed | Server Name: SC Realtime Server. | 2023-05-03 22:40:10.124 Denali Data Feed | Server protocol version: 8. Client protocol version: 8 | 2023-05-03 22:40:10.124 Denali Data Feed | Successfully connected. | 2023-05-03 22:40:10.124 Denali Data Feed | Trading is not supported. | 2023-05-03 22:40:10.124 Denali Data Feed | Restarting real-time data updates for symbol: MNQM3.CME -> MNQM23. Market Depth data restarted. | 2023-05-03 22:40:10.124 Denali Data Feed | Received security definition for symbol MNQM3.CME | 2023-05-03 22:40:10.436 Denali Data Feed | Market Depth data has been rejected for symbol: MNQM3.CME. Not authorized for market depth. | 2023-05-03 22:40:10.436 HD Request # 8 | Downloading Intraday chart data for MNQM3.CME to the file MNQM3.CME.scid. Service: cme | 2023-05-03 22:40:15.885 HD Request # 8 | Download start date-time: 2023-05-03 22:39:57.000000. File last date-time: 2023-05-03 22:39:57.349000 | 2023-05-03 22:40:15.886 HD Request # 8 | Using server: ds23.sierracharts.com port 10149 | 2023-05-03 22:40:15.886 Socket (4) | Creating socket. | 2023-05-03 22:40:15.886 Socket (4) | New receive buffer size: 5242880 | 2023-05-03 22:40:15.886 Socket (4) | Connecting to IP: 142.215.17.190. | 2023-05-03 22:40:15.886 HD Request # 8 | Setting DTC encoding to Binary VLS | 2023-05-03 22:40:16.348 HD Request # 8 | Sending historical data logon request message. | 2023-05-03 22:40:16.348 HD Request # 8 | Requesting Intraday data. Start date-time: 2023-05-03 22:39:57. Record interval: 0. Symbol: MNQM23 | 2023-05-03 22:40:17.728 HD Request # 8 | Decompressing data. | 2023-05-03 22:40:17.957 HD Request # 8 | Receiving Intraday data for MNQM3.CME starting at 2023-05-03 22:39:57.003000 | 2023-05-03 22:40:18.691 Socket (4) | CloseSocket call. | 2023-05-03 22:40:18.885 Socket (4) | Shutdown started. Waiting for graceful close. | 2023-05-03 22:40:18.885 Historical data download thread signaled to stop. | 2023-05-03 22:40:18.885 HD Request # 8 | Timestamp of first Intraday data file record written: 2023-05-03 22:39:57.741000. | 2023-05-03 22:40:18.885 HD Request # 8 | Received 954 Intraday data records from 2023-05-03 22:39:57.003000 to 2023-05-03 22:40:16.766004 (19.8 seconds. Delay: 2.1 seconds) and wrote 945 records for MNQM3.CME | 2023-05-03 22:40:18.885 HD Request # 8 | Add time&sales data | Remembered last file record date-time: 2023-05-03 13:40:16.766004 | 2023-05-03 22:40:18.890 Added 14 Time and Sales records to Intraday data file for MNQM3.CME after download. | 2023-05-03 22:40:18.890 HD Request # 8 | Completion time: 3s. | 2023-05-03 22:40:18.890 HD Request # 8 | Intraday data download complete for MNQM3.CME. Unique request ID: 8 | 2023-05-03 22:40:18.890 Removing historical data download ID 8. | 2023-05-03 22:40:18.890 Real-time Intraday chart data file updates started for MNQM3.CME | 2023-05-03 22:40:18.890 Intraday chart data file opened for MNQM3.CME | 2023-05-03 22:40:18.890 HD Request # 8 | Enabling Intraday chart updating for symbol. | 2023-05-03 22:40:18.890 Triggering next historical data download in queue. | 2023-05-03 22:40:18.890 No download requests in the queue to start downloads for. | 2023-05-03 22:40:18.890 Socket (4) | Socket gracefully closed by remote side. | 2023-05-03 22:40:19.114 Socket (4) | Closed. | 2023-05-03 22:40:19.114 Opened cached Intraday file: D:\Trading\APEX\Data\MNQM3.CME.scid. Thread ID: 12748 | 2023-05-03 22:40:20.574 HTTPS connection ID:3 to www.rithmic.com:443 for request ID:3 (4) | Creating socket. Using TLS 1.2. | 2023-05-03 22:40:21.417 HTTPS connection ID:3 to www.rithmic.com:443 for request ID:3 (4) | New receive buffer size: 32768 | 2023-05-03 22:40:21.417 HTTPS connection ID:3 to www.rithmic.com:443 for request ID:3 (4) | Connecting to IP: 38.79.0.89. | 2023-05-03 22:40:21.417 HTTPS connection ID:3 to www.rithmic.com:443 for request ID:3 (4) | New receive buffer size: 65536 | 2023-05-03 22:40:23.659 HTTPS connection ID:3 to www.rithmic.com:443 for request ID:3 (4) | Socket gracefully closed by remote side. | 2023-05-03 22:40:24.508 HTTPS connection ID:3 to www.rithmic.com:443 for request ID:3 (4) | CloseSocket call. | 2023-05-03 22:40:24.508 HTTPS connection ID:3 to www.rithmic.com:443 for request ID:3 (4) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2023-05-03 22:40:24.509 HTTPS connection ID:3 to www.rithmic.com:443 for request ID:3 (4) | Closed. | 2023-05-03 22:40:24.509 |
| [2023-05-03 16:13:37] |
| John - SC Support - Posts: 36350 |
|
Everything in your log is fine. So it sounds like you are getting the real-time data now, but it is behind by "a couple of minutes"? What exactly is occurring? Do you have any indication of a delay in the data on your Sierra Chart system? For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2023-05-04 07:18:29] |
| User85195 - Posts: 60 |
|
first time I noticed the delay was on Monday, my stoploss was triggered a couple of times when price clearly didn't touch it on the chart. so I opened a chart in RTraderPro for the same symbol in the same timeframe, and to my shock it was showing a different price and almost one full bar ahead of the chart in SC, and yet the timestamp in both charts were the same. this lasted until yesterday, when I noticed a switch. RTraderPro became the one with the delayed datafeed, a couple of minutes behind SC. I have no idea what is going on. both platforms were working fine before Monday. I didn't change any configurations in both platforms for as long as I could remember. a few days prior to the problem occurring, I did receive notifications asking me to connect to my live funded trading account in order to keep receiving real time data feed. I couldn't connect to AMP so I connected to IB instead. and the notifications disappeared so I thought it was done. but I started getting delayed datafeed not long afterwards. |
| [2023-05-04 09:44:02] |
| Sierra_Chart Engineering - Posts: 17201 |
|
Refer to: Prices / Data Falling Behind Check the Data Delay field and see how much of a delay there is: Working With Charts: Region Data Line / Chart Header Set "Global Settings >> Data/Trade Service Settings >> Common Settings >> Allow Support for Sierra Chart Data Feeds" to Yes. If it was not yes, reconnect to the data feed with File >> Reconnect. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2023-05-04 09:45:27
|
To post a message in this thread, you need to log in with your Sierra Chart account: