MotiveWave historic data issue

Discussion in 'Trading' started by heispark, Mar 16, 2020.

  1. heispark

    heispark

    I provided my log files to Jason. So, please check who's responsible for that. I use the same Rithmic account (via AMP Futures) for total 5 applications including Bookmap, Sierra Chart, R|Trader, Journalytix and MotiveWave. And ONLY MotiveWave had this issue. Check if you are using the latest Rithmic API. Except MW, the others use Rithmic Singapore server (Asian users need to use it). MW doesn't have option to select Rithmic sever, so I use default server setup. It might be the reason. However, even when I used Rithmic default or Aurora servers, I never had such issue in other applications. By the way, seconds based chart still doesn't work. This is Tokyo open session and data volume should be low. Please watch this video:



    I am also contacting Rithmic now. Hopefully, they can confirm if it's really their fault.
     
    Last edited: Mar 16, 2020
    #11     Mar 16, 2020
  2. heispark

    heispark

    Sorry for the rant but I have to point out something. Yes, my view to MW has been changed from positive to negative after some time I purchased it. There have been many issues and I helped MW by reporting bugs and suggestions I found. Many of them are still not fixed or once fixed but rolled back later. For example, while I have an open position with bracket orders (SL and TP), if I click "Break Even" button, I expect only previous SL is replaced by breakeven stop order.
    2020-03-17_10-10-19.png
    Instead, if I select "Cancel Existing Orders" option, it removes both TP and SL and set BE (instead of removing only SL). If I don't select this option, I will end up with duplicate orders (order reversing). Any scalping trader using break even quickly after market moves in his favor would understand that it should replace only SL. This is kinda common sense stuff. See how Sierra Chart or other platforms work. Often, I find MW is away from industry standards or common sense as if developers have never traded themselves before..... Quite disappointing.
     
    #12     Mar 16, 2020
  3. heispark

    heispark

    I suspect if it's MW's backfill server issue:

    2020-03-17_13-56-51.png

    Need to check if the latest Rithmic API is being used....
     
    #13     Mar 17, 2020
  4. heispark

    heispark

    By the way, DOM wasn't affected. DOM displayed accurate bid/ask data. Only chart drawing was affected by this issue. Just for your information.
     
    #14     Mar 17, 2020
  5. MotiveWave

    MotiveWave Sponsor

    We don't use the Rithmic Singapore server, so that is probably why you're seeing a difference.
     
    #15     Mar 17, 2020
  6. MotiveWave

    MotiveWave Sponsor

    Please don't use Elite Trader as a MotiveWave Support desk. This just delays you getting help. If you are having an issue, please email our Support Team.
     
    #16     Mar 17, 2020
  7. MotiveWave

    MotiveWave Sponsor

    Support for the Rithmic Singapore server was added in our version 6.1.13, released March 25th.
     
    #17     Apr 10, 2020