I don't deny that somehow Velocity MAY have sent some 'bad' data to SC. Who knows. Not me. But, I do know that SC "hung" on that, it didn't move forward gracefully -- if the event was indeed triggered by bad data of some sort via the feed.
Exiting and reloading SC should have overcome any problem, but didn't. So that is how I knew it was in the data file, and once deleted, problem solved. A bit stunned SC is saying the data file has nothing to do with it. Honestly, I don't care who is right or wrong -- I just want it to not happen again and be reproduced by them and then fixed.
Due to time constraints, please do not PM me if your question can be resolved or answered on the forum.
Need help? 1) Stop changing things. No new indicators, charts, or methods. Be consistent with what is in front of you first. 2) Start a journal and post to it daily with the trades you made to show your strengths and weaknesses. 3) Set goals for yourself to reach daily. Make them about how you trade, not how much money you make. 4) Accept responsibility for your actions. Stop looking elsewhere to explain away poor performance. 5) Where to start as a trader? Watch this webinar and read this thread for hundreds of questions and answers. 6) Help using the forum? Watch this video to learn general tips on using the site.
If you want to support our community, become an Elite Member.
The following 2 users say Thank You to Big Mike for this post:
I had the same problem earlier this evening with IQFeed. I didn't delete the file, but I did restart my computer.
Not sure if it is related, but I lost the IB API yesterday as well. IB posted a message saying that connection was lost to ISPs Comcast, Roadrunner, and Bright Speed. Comcast said something about an update that wasn't completed installed. At the time, I had other internet and could connect to the IB webtrader. Apparently IB worked with Comcast to resolve it, though Comcast managed to shut me down completely as well for a while reconfiguring and restarting my modem.
The reason I mention this is that I've never had problems with either IQFeed or IB and suddenly I have problems with both within a few hours. Perhaps it is possible that it is an internet problem?
There was something similar when they first got the Rithmic feed going. It was not a hanging problem, but it was inserting bad data due to something they did not understand with the Rithmic API. I do not know if it was a Rithmic or SC fix, but they did eventually fix it once the problem was understood.
I'll bet its not a data issue, but a timestamp issue. Are there any timestamps out of order or in the future in the data file? The file is a binary file, so you can not just look at it. Perhaps you could post the file here, and I can parse it quick.
My SC TT connection froze a couple times this week for a few seconds, once while I was in a trade which was more than a little nerve racking. I was in chart trader mode and not DOM mode, but my SC IB kept going no problems, so I assumed it was a Velocity/TT data problem. I don't have a lot of experience with TT and never used it with NT, but the SC IB setup has been 100% reliable for the past 5 weeks, so I keep my SC IB going in case I have to place an emergency hedge.
I've had three other problems with SC TT as well. Last wednesday I could not place an order on the March contract, it told me that there was no symbol. This was after I had already traded with it and had not made any changes to my setup. It ended up being fortunate because I would have stopped out on the trade. So I tried to switch to the April contract and it would not receive live data. Consequently, I had to switch back to trading through IB for the day. Later that night I was able to place orders on the March contract and receive live data on the April contract, so again I assumed it was a Velocity/TT problem. Then yesterday, I was up about 15 ticks on a trade and so I picked up my stop to move it to break even when the price jumped back on me. It stopped within a few ticks of my entry and because I had my trigger on the order already I tried to quickly drop it across the price to close it out, but the order did not trip. Naturally, the price jumped up again and stopped me out before I could do anything. I've done this procedure before in SIM mode and it worked ok, so I just thought maybe you can't do it when connected to TT. But then today I was up in a position again and I tried to move the stop to breakeven and the stop would not move at all. I had to cancel it and replace it. Fortunatately it didn't jump back on me this time, but that's obviously what happened to me yesterday as well. I don't know if anyone else has had this problem or not.
Conclusion so far is that SC with IB has been considerably more robust than SC with TT, which has suprised me. I would have expected the opposite.