+1 888 340 6572 GET STARTED
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-62

Spikes when turning on auto trading on Zen-Fire symbols, if the symbols are set to "Collect Data" in Quote Manager

action_vote_minus_faded.png
0
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

Spikes when turning on auto trading on Zen-Fire symbols, if the symbols are set to "Collect Data" in Quote Manager

Steps to reproduce this issue
  • Add following Zen-Fire symbols to the QM database:
    YMZ0 - CBOT
    ZNZ0 - CBOT
    ZBZ0 - CBOT
    ESZ0 - CME
    NQZ0 - CME
    6EZ0 - CME
    6BZ0 - CME
    TF FMZ0010! - NYBOT
     
  • Plot a chart for ESZ0 from Zen-Fire, 3000 contracts resolution. 
  • Add signals to the chart (even empty signal)
  • Turn on "Collect Data" option in QuoteManager.
  • Configure auto trading with Zen-Fire (important!).
  • When you turn on the auto trading, spikes will appear.
  • Can be reproduced during trading hours.
Comments (0)
History
Issue basics
  • Type of issue
    Bug report
  • Category
    Not determined
  • Targeted for
    MultiCharts 7.0 (RELEASED)
  • Status
    Released
  • Priority
    Not determined
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (3)
People involved
  • Posted by
    user-offline.png  Dave (Dave)
  • Owned by
    Not owned by anyone
  • Assigned to
    Not assigned to anyone
  • Subscribers
    2 subscriber(s)
    Click here to show the list of subscribers
Times and dates
  • Posted at
  • Last updated
Issue details
  • Reproducability
    Not determined
  • Severity
    Normal
Attachments (1)
  • /pm/public/files/show/51
    screenshot-1.jpg uploaded Nov 23, 2010 by Dave (Dave)
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates