开云体育

First of all this is really weird case. I never seen this type of issue. Are you waiting for next valid order id event before starting with other things? But if you really want to Hack it then use

IB doesn't cease to amuse. I am baffled. Yesterday, the last executed orderId was 161178. Today,??ibapi.wrapper: ANSWER nextValidId {'orderId': 161044} No need to say, this caused a major headache

Thanks for your insights re: the position changes, and I'll look into the delays further.

I ran unattended for a few years to 2020 and I am interested in doing so again with a different algorithm and substantially different code-base. I used to use Linode, Ubuntu + ubuntu desktop,

In my experience position changes are coming even sooner than execution details. But this is stocks, not sure about FX, but anyway make sure the delay is not on your side, as 5mins sounds like too

I'm used to TWS reporting the position sizes and position lists in a delayed manner, say 2-3 seconds after reporting that an entry or exit order was filled, but recently it's been more like 5 minutes

Nevermind... Apparently the documentation folder in the unzipped file is not the only documentation. Elsewhere IB says... "It is important to note that the connection is only insecure between the user

Is there a way to get data from TWS API to construct the probability chart that is available in the Probability Lab? Thought I'd check before I build it manually. Thanks!

Hi Brian, It is secure on localhost. Using such self-signed certs are at least as secure as the CA signed ones, since it uses the same encryption technology. The self-signed certs are just not

Yeah, you are right, apologies for pushing further confusion about this topic, I should have been more careful commenting on a feature that I only played around with too little to fully understand. --

I'm making the transition from TWS API to Client Portal API. When I login to https://localhost:5000 the Edge browser says Client Portal API is not secure. Why? Does this even matter? If it does

That shouldn't be too hard. Something like this: * Pick a good time for TWS/IBKR restart based upon the trading schedule for the instruments you are working with. For example some time between 16:00

Hey there Jurgen, thanks a lot for your input, it has really helped me see this problem in a different way. What's the best way I could approach a scheduled full disconnect right before TWS restarts

Thanks Gordon! I will take @btw advice as you say. Your opinion is exactly why I am in this problem: The fact that I need my program to go through the required TWS restart is what's got me struggling

I have followed this post for a while now. Gordon and btw provided a lot of great and relevant advice already, but what you (makeitrain512) are trying to do is pretty advanced. I am wondering whether

@btw give the best path: you should start from a working example and increase complexity gradually. Splitting issues to do small studies set, one topic at a time,? then assemble what mastered from

Not surprising, hence the recommendation from @Hilmar, We don't know your testing condition and benchmark. Keep in mind that even a few instruments are traded only once a day. (or even not at all!),

I did a test by running my python program with TWS offline and the results are as follows: 1 - From line 1 to 89 TWS was offline so it was not able to connect with anything. 2- Proceed to login into

Thanks Gordon and bespalex. The value of profit_order_ID was assigned outside of the wrapper but after following bespalex's suggestion to print its value within orderStatus, I found?that the

I would blend your code with the working code.? Add yours block by block until something doesn't work. Or do nothing.? I can't remember a problem in 20+ years unless there's been a power failure.