stock777

still broken after all updates applied

Have a custom paintbar (scan) placed in a chart. Watches bid/ask size, Working ok, all data is reported in Alert window , but seems to randomly lose the ability to populate the Alert window with the alert data. I get UNKNOWN for symbol, and no bid/ask (zeros), when triggered Seems to work when first inserted in the chart, and then break after ?

Whatever the problem is, they are taking their time fixing it

thats wrong. look at the gaps . there are a bunch of other exchanges below the nbbo , much closer in price As is said, the TOS feed is correct you know I never complain unless there a real problem ?

There are a bunch of exchanges missing. IBKR only shows NASDAQ none of the others . Only market makers besides that. IBKR moved to the IEX, maybe something to do with that , no idea about FTCH Same patter with FTCH , only nasdaq

This is probably their problem not yours, but I see a few symbols that do not properly display all the price levels (they are missing) in some names, the TOS platform seems correct but not the api you use Look at IBKR , FTCH

Yep, as you said, just needed to subscribe, no charge

ok, I thought it had something to do with the Apex thing. Will check out the subs

Last two days don't think Im getting any news from Ameritrade I know they changed something on their end , as they cancelled the APEX account status for everyone, but not sure why news would be affected. Any idea?

I was entering the symbol directly in the watchlist. What would be the reason for multiple instances in the same list ?

I notice you can enter the same symbol twice in a port. Is this a bug or a feature ? ?

ok, good. figured it would be an ez fix.

i sent just the log via email to the support address, you prefer doing it from within mt ?

I'll send the log. Comes right up when I manually tell it to relog, so my guess is the auto retry routine isn't doing the same thing, or its timing out

Been having some Internet issues, nothing to do with MT IB recovers cleanly, but Ameritrade does not. Have to manually go to SOURCES screen , and RELOG to get the stream back up. Maybe tweak that so it works on its own?

Got it , makes sense

OK, I see how this works. I've not done a lot with the code as yet so still figuring it out. The indicator parms are set outside the code, and the output assigned to a named variable.

Happened to look at this indicator NumberOfTrades_Bar , and see that it supports bid/ask filters. Works fine for adding to charts. When I used the paintbar editor to add this scan, it does expose the bid only , ask only parm , BUT it does not actually have this as a feature when the code is produced. Was this just left out or something else going on ?

Thanks for quick turnaround

The first chart is the backfill from ameritrade, the second from IB for today As you can see ,a completely different volume profile. Actually, they are the same , proportionally , but one is 1.5 times the other. So there a problem with one of them .

I think this is a recent issue. Getting the backfill from Amtd and then realtime from IB is going to distort volume charts if the data if totally different. Ameritrade bars look high. Here's what I see Backfilling MT with AMTD for ES, I see a bunch of bars well OVER 10,000 on the minute scale for the first few hours Looking at the same ES data on the Thinkorswim platform , the bars are never over 7000 IB backfill looks normal. Could be a data issue from amtd or something in MT I'll send pics when I get a chance, unless you can duplicate it on your end.

I see ameritrade is backfilling. Was there a change at somepoint Comparing the IB to Amtd back fills, there is a big diff in the volume profile . I seem to be having trouble getting a symbol to backfill with a specific source, without changing the DEFAULT for all symbols. It does it one time using backfill using XXX, but doesn't stick ?

only ib backfills futures as far as i know

Might be related to that volume bug that was fixed. The volume bars on ES look wrong (too high) on backfill, vs realtime bars. Multiplier issue probably.

whoops, yes , used the support email as the target ill post it elsewhere and give you the link