+1 888 340 6572
MultiCharts Project Management
previous_open_issue.png
Go to the previous open issue
previous_issue.png
Go to the previous issue (open or closed)
star_faded.png
Please log in to bookmark issues
bug_report_small.png
Open Bug report MC-2065

Time lag between IB TWS and MC price marker

action_vote_minus_faded.png
3
Votes
action_vote_plus_faded.png
next_issue.png
Go to the next issue (open or closed)
next_open_issue.png
Go to the next open issue
Description

Sometimes the chart window price marker (set to "trade") shows a time lag compared to IB TWS. There is no time lag for Bid / Ask, and the issue does not show in the DOM window.
When the time lag occurs, I can resolve it in most cases by restarting MultiCharts. I am not able to consistently reproduce the issue, which occurs around 20 - 30 % of MultiCharts launches. Once MultiCharts is launched and no time lag shows, it will not occur for the rest of the session.
My MC version is MC64 9.1 (Build 12587)
Please see the link below for a demo of the issue.

Steps to reproduce this issue

Launch IB TWS
Launch MultiCharts
Open Chart window with price marker set to "Trade"
Check TWS last price with MultiCharts last price marker for time lag

Comments (2)
#0
user-offline.png  Alex MultiCharts (Alex MultiCharts)
Jul 07, 2016 - 07:11

Hi,

Please send us an email to support@multicharts.com with the screenshot of the data feed settings in QuoteManager --> Tools --> Data Sources --> Interactive Brokers --> Settings.

#0
user-offline.png  Guest (Guest)
Sep 27, 2016 - 02:51

I couldn't open the demo video but it seems the same issue occurred to my MC.Net64 10 beta2. I will send you screenshots of the chart and IB settings.

History
Issue basics
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (2)
People involved
Times and dates
  • Posted at
  • Last updated
Issue details
  • Reproducability
    Not determined
  • Severity
    Critical
Attachments (2)
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates