Support Board
Date/Time: Tue, 26 Nov 2024 12:34:09 +0000
SC crashes when submitting attached orders to IB
View Count: 1360
| [2014-04-29 15:16:48] |
| MotoMoto - Posts: 47 |
|
Hi, I have only encountered this problem the last few days. Previously it all worked. since the IB issue came up last Friday. Plus I dont often use attached orders for every trade. SCv1128, IB TWS v944.3b version Basically it operates fine normally, but when i have attached orders it crashes the system. Plus I notice that if I am trading 5 contracts it only sends in stop and targets for 1 contract. Any ideas? thanks. |
| [2014-04-29 15:58:37] |
| |
|
Refer to help topic 17 here: Http://www.sierrachart.com/index.php?l=doc/helpdetails17.html Plus I notice that if I am trading 5 contracts it only sends in stop and targets for 1 contract. If you are using Attached Orders this would be because there has been a partial fill of the parent order for 1 contract.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2014-04-30 09:58:29] |
| MotoMoto - Posts: 47 |
|
Hi I will have to wait until there is a bit more volume to safely test this live on the same instrument - on SIM there does not seem to be a problem. I just tested using 2 contracts on the ES live, it appeared to be fine. However, in this instance, I had no advanced custom studies on this chart, but i will go through and take them out of all charts in the system just to test. (EDIT: there was one in one chart in the background not being used [ALMA], otherwise I am only using [HighestHigh/Lowest Low over N Bars], [Parabolic], [Kiwis Trailing Stop], and [Range Bar predictor] in different charts) Also, this was not a partial fill. I was filled 100%, but the stops and targets only showed 1 contract, and the moment the initial trade occured was when the system crashed. I immediately checked the IB TWS and it showed 5 contracts long, but each attached order only had 1 contract in it. When I reloaded SC then it also showed 5 long, and only 1 contract per attached order. The only thing I could come up with is that there was some delay - yesterday in the NQ seemed particular gappy, thin and with data delays - but that was what I could see with the visual eye, and the parital fill might have been 1 + 4 contracts. I will test again today and see if this remains. FYI - I downloaded the new version, and I have no problems with the hard drive - it appears to be fine, and no problems opening chartbooks Thanks. EDIT: crashed as soon as I did a live trade in NQ with IB TWS, when using the attached orders. When not using attached orders the trades dont seem to cause a problem. I will try and delete the offending chart window and reload - and/or try another chart trade window. EDIT: attached orders on the same instrument with different trade windows and charts - one crashes the system the other does not: delete offending chart! Conclusion: - something screwy with a single chart when using attached orders with its trade window. Deleted - offending chart and reloaded the same chart underlying, populated it with the same indicators and spreadsheet - so far so good. Date Time Of Last Edit: 2014-04-30 13:06:48
|
| [2014-04-30 14:24:16] |
| MotoMoto - Posts: 47 |
|
Unfortunately it crashed again...and the same issue occurs. I have made sure the targets and stop amounts match, but it still sends in the incorrect attached orders. I have used a different pre-saved attached order that I have used with no problems in the past. When there are no attached orders there are no problems. Using a different chart gives me the same problems with the same underlying NQ, it appears NQ is the issue. Given IB upgraded/downgraded their systems last week and this was a problem - could it have something to do with that? Date Time Of Last Edit: 2014-04-30 14:26:19
|
| [2014-04-30 15:24:32] |
| |
|
We are looking into the crash problem today. We have another report of this.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2014-04-30 16:50:08] |
| |
|
We have discovered the source of the problem. It has to do with when there are partial fills of the parent order. Even if they occur rapidly and you are not aware of them. We are releasing a new version in about 15 minutes. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2014-04-30 17:49:50] |
| |
|
We have been doing some additional work on the new version before the release. We will be releasing version 1130 in about 10 minutes.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2014-04-30 17:50:11
|
| [2014-04-30 18:45:14] |
| |
|
Version 1130 is now released.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2014-04-30 19:10:01] |
| MotoMoto - Posts: 47 |
|
Downloaded - first attempt seems to work OK. I dont know if it was a partial fill, but it works. Thanks. |
| [2014-04-30 19:10:53] |
| |
|
The problem is definitely corrected. We know exactly what was causing it. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2014-05-01 14:29:42] |
| MotoMoto - Posts: 47 |
|
hi...yes corrected in that it does not crash and it also updates the correct amounts. However, I noticed a new issue you want to look at. Today I sold 5 NQ at the bid, resulting in.... -1@3576.25 -2@3576.5 -1@3576.5 -1@3576.5 Avg price of 3576.45 I had an attached order stop of 8T (8 tics) This should have given a stop of 3578.5 (I can confirm this if I put an away from market order in. However, the stop in SC and IB TWS was placed at 3579.5 --- a total of 12T (12 tics) away. Why would this occur? thanks. EDIT: sold two lots of 5 also - both were filled at sales at 3593.5 - however, one stop was at 3594.5, the other stop at 3595.5 both with the same attached orders....the sales occurred as I wanted to sell 10 and deliberately pushed the sell at bid button twice. Date Time Of Last Edit: 2014-05-01 15:08:58
|
| [2014-05-01 18:37:09] |
| |
|
Not sure why this would be. We need to test this.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2014-05-01 18:50:33] |
| |
|
We are not seeing a problem with this and we do not believe this is a problem with Sierra Chart incorrectly setting Attached Order prices. There have been no changes which would cause something like this. And as we said, we cannot duplicate this. Make sure the tick size for the symbol is set correctly in Chart >> Chart Settings. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
To post a message in this thread, you need to log in with your Sierra Chart account: