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:Wow, your view of MotiveWave greatly changes depending on the day. There are tons of posts where you rave about MotiveWave.
Aside from that, MotiveWave does not provide data. Calling this thread "MotiveWave historic data issue" is very misleading. MotiveWave connects to API's provided to us by brokers and data service providers. The error message you posted is relayed directly from the broker or data feed you are using.
You mentioned you were trying to connect to Rithmic. Given the current volatility of the markets, many feeds are experiencing issues during the very volatile periods. It appears that the Rithmic servers did have an issue, which they have now fixed.
You know MotiveWave Support always works hard to make sure any issues are fixed as quickly as possible, when it is something on the MotiveWave side, and we work with the broker or data feed when it is not clear which side the issue is on.
You also know that we implement new features very quickly. Saying we're not for serious traders is completely false. Please keep this in mind in the future, before posting an unwarranted escalating rant against MotiveWave like this again in the future.
This was not a MotiveWave issue.
I am also contacting Rithmic now. Hopefully, they can confirm if it's really their fault.
Last edited: