KyleK29

I don't recommend doing it manually. Here's what the Configurator put out for what I believe is your settings. LONG - % Equity Risk Version, 1%, DAS DEMO Broker, 4:1 Margin: StopPrice=Price-0.01;DefShare=BP*0.97;Share=DefShare*0.25*Price*0.01;Price=Ask-Price+0.01;SShare=Share/Price;Share=DefShare-SShare;DefShare=DefShare+SShare;SShare=Share;Sshare=DefShare-SShare;Share=0.5*SShare;TogSShare;ROUTE=LIMIT;Price= Ask+0.03;TIF=DAY+;BUY=Send;DefShare=400;TriggerOrder=RT:STOP STOPTYPE:MARKET PX:StopPrice-0.3 ACT:SELL STOPPRICE:StopPrice QTY:Pos TIF:DAY+; SHORT - % Equity Risk Version, 1%, DAS DEMO Broker, 4:1 Margin: StopPrice=Price+0.01;DefShare=BP*0.97;Share=DefShare*0.25*Price*0.01;Price=Price-Bid+0.01;SShare=Share/Price;Share=DefShare-SShare;DefShare=DefShare+SShare;SShare=Share;Sshare=DefShare-SShare;Share=0.5*SShare;TogSShare;ROUTE=LIMIT;Price=bid-0.03;TIF=DAY+;SELL=Send;DefShare=400;TriggerOrder=RT:STOP STOPTYPE:MARKET PX:StopPrice+0.3 ACT:BUY STOPPRICE:StopPrice QTY:Pos TIF:DAY+; If these don't work for you, you'll need to go into DAS -> Main Menu (Top Bar) -> Setup -> Other Configuration, check the option "Don't Delete History Logs" and "Log Debug Message". Close and restart DAS. Go test the hotkeys in a trade where it fails. Then PM me the content of the log file in the C:\DAS Trader Pro\LOG\ directory, it should be named for the date, e.g. YYMMDDLog.txt --> 200707Log.txt would be today.

For the STOP routing / StopType, use LIMIT or MARKET (preferably market, it's safer). The reason is that these are routed differently, even with IBCO. If you manually set it up in montage you'll notice the STOP Route type doesn't have SMRTM or SMRTL. So when a hotkey tries to populate that, it can't find a match and fails. Try this one for IB: StopPrice=Price-0;DefShare=BP*0.97;Price=Ask-Price+0.01;SShare=50/Price;Share=DefShare-SShare;DefShare=DefShare+SShare;SShare=Share;Sshare=DefShare-SShare;Share=0.5*SShare;TogSShare;ROUTE=SMRTL;Price= Ask+0.05;TIF=DAY+;BUY=Send;DefShare=400;TriggerOrder=RT:STOP STOPTYPE:MARKET PX:StopPrice-0.05 ACT:SELL STOPPRICE:StopPrice QTY:Pos TIF:DAY+; If I'm understanding this correctly, you want to have multiple risk positions (e.g. multiple "strategies" in play)? So for example, you enter a stock at $20.00, with a $19.80 stop price and qty 50. The stock moves in your favor and sets up for another strategy, and you add at $21.00, with another stop at $20.50 and a qty of (example) 50. Your position / open orders looks like: STOCK, Qty: 100, $20.50(avgcost) OPEN STOP, $19.80, Qty: 50 OPEN STOP, $20.50, Qty: 50 Something like that? I'll have to remember to try this tomorrow, I have an idea on what might be causing an issue but I need to test it. Few things, can you confirm you have 6:1 leverage (margin) on this account? Default is 4:1. The hotkeys you pasted are setup for 6:1 and a mismatch in leverage to the account can cause anomalies. Second, can you add a Trigger Order window and try again, see if a trigger order is being created? It's under Main Menu -> Trade -> Trigger Order .... this window works like the Open Orders window and will populate the status of active (not triggered) TO's. If you find a working setup for CMEG, please do post your config so I can roll it in as the recommended. CMEG is the odd-duck, as they have certain things that mess with the hotkeys. I've heard some users have luck setting the Time in Force to --> TIF=DAY; instead of the default TIF=DAY+. Apparently that solves some rejection issues with them.

What montage swap did you want? I had a few, but I discontinued them as they were either replaced by native DAS functions or not ever used. -Kyle

No, not from DAS directly, but I've never asked them specifically about this stuff. If you submit bugs, be sure to use the bugs[at]dastrader.com and not the support[at]dastrader.com ... I have noticed they won't reply to a bug report unless they need more additional information, so if you submit a good bug report they tend not to reply. I've had 3 bugs fixed in the last two weeks, so they do tend to move quickly on the beta side. I use a simplified report template: BUG TITLE OS: DAS Version: (version # and build datetime from Help > About) Description of Issue: User Expected Outcome: Attachments:

I think I remember seeing one other fix outside of the 1000 character limit. I wouldn't mind seeing your .htk file that has the 100 character length for the script portion. Here's one with various scenarios and how it's formatted for me: :Escape_Characters_Basic_Latin_Unicode:~ 187:! " # $ % & ' ( ) * + , - . / 0 1 2 3 4 5 6 7 8 9 : ; < = > ? @ A B C D E F G H I J K L M N O P Q R S T U V W X Y Z [ \ ] ^ _ ` a b c d e f g h i j k l m n o p q r s t u v w x y z { | } ~7E :Maximum_Length_Test_Extra:~ 998:TTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTEEEEE EEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEESSSS SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSTTTT TTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTEEEEEE EEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEESSSSSSSSS SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSST TTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTT TTTTTTTTTTTTTTTTTTTTTTTTEEEEEEEEEEEEEEEEEEEEEEEEEEE EEEEEEEEEEEEEEEEEEEEEEEFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFFTESTTTTTTTTTTTTTTTTTTTTTTT TTTTTTTTTTTTTTTTTTTTTTTTEEEEEEEEEEEEEEEEEEEEEEEEEEE EEEEEEEEEEEEEEEEEEEEEEEEESSSSSSSSSSSSSSSSSSSSSSSSSS SSSSSSSSSSSSSSSSSSSSSSSSSTTTTTTTTTTTTTTTTTTTTTTTTTT TTTTTTTTTTTTTTTTTTTTTTTEEEEEEEEEEEEEEEEEEEEEEEEEEEE EEEEEEEEEEEEEEEEEEEESSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS SSSSSSSSSSSSSSSSSSSSSSSSSSSSTTTTTTTTTTTTTTTTTTTTTTT TTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTT TTEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE EFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFTESTTTTTTTTTTTTTTTTTTTTTTT :Line1Test1_Well_Well_Well Copy:Route=Limit;Share=Pos*0.25;Price=StopPrice-AvgCost;Price=Price*1.25; :ItemD:DefShare=DefShare+0 :ItemC:DefShare=DefShare+0 :Item:~7E DefShare=DefShare+0 ~7E Alt+Ctrl+F10:ACF10_Long_Test_Maybe:~ 501:#Hashtag_Again; CXL BELOWAVGCOST;StopPrice = Price; Share=Price*100;Price=AvgCost;SShare=Price*100;Shar e=Share-SShare;Price=Share;Price=Share/100;Share=Po s * Price;Price=Ask-StopPrice;SShare=Share / Price; DefShare=BP*0.97;Share=DefShare-SShare;DefShare=Def Share+SShare;SShare=Share;SShare=DefShare-SShare;Sh are=0.5*SShare; Share=Share*1; Price=Ask+0.05;TogSS hare;TIF=DAY+;ROUTE=SMRTL;BUY=SEND;DefShare=10; Tri ggerOrder=RT:STOP STOPTYPE:MARKET PX:StopPrice ACT: SELL STOPPRICE:StopPrice QTY:Pos TIF:DAY+; Ctrl+B:SaveTest:SaveLayout Ctrl+E:MAXIMUM_SHARED_LINKED_TITLE_IS_HERE_TO_STAY_AND_CAN_BE_CONSIDERED_GREAT_GLORIOUS_ADVENTURE_OF_MEN_#:Prefs="Testing how I can make this more appealing" Ctrl+K:Hashtag Test With #Ae5123kls:WPos X Y Ctrl+R:SampleG WIth Spaces:#HASHTAG; Testing_this; Price=111; Ctrl+Shift+E:SampleB:~ 237:Route=Limit;Share=Pos*0.25;Price=StopPrice-AvgCost; Route=Limit;Share=Pos*0.25;Price=StopPrice-AvgCost; Price=Price*1.25;Price=AvgCost-Price;Price=Round2;T IF=DAY+;BUY=Send;Price=Price*1.25;Price=AvgCost-Pri ce;Price=Round2;TIF=DAY+;BUY=Send Ctrl+Shift+F:SampleA:~ 118:Route=Limit;Share=Pos*0.25;Price=StopPrice-AvgCost; Price=Price*1.25;Price=AvgCost-Price;Price=Round2;T IF=DAY+;BUY=Send Ctrl+Shift+M:ItemB:DefShare=DefShare+0 TAB:Line1Test1_Well_Well_Well:Route=Limit;Share=Pos*0.25;Price=StopPrice-AvgCost;Price=Price*1.25; Alt+Ctrl+B:Maximum_Length_Test:~ 962:TTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTEEEEE EEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEESSSS SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSTTTT TTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTEEEEEE EEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEESSSSSSSSS SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSST TTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTT TTTTTTTTTTTTTTTTTTTTTTTTEEEEEEEEEEEEEEEEEEEEEEEEEEE EEEEEEEEEEEEEEEEEEEEEEEFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFFTESTTTTTTTTTTTTTTTTTTTTTTT TTTTTTTTTTTTTTTTTTTTTTTTEEEEEEEEEEEEEEEEEEEEEEEEEEE EEEEEEEEEEEEEEEEEEEEEEEEESSSSSSSSSSSSSSSSSSSSSSSSSS SSSSSSSSSSSSSSSSSSSSSSSSSTTTTTTTTTTTTTTTTTTTTTTTTTT TTTTTTTTTTTTTTTTTTTTTTTEEEEEEEEEEEEEEEEEEEEEEEEEEEE EEEEEEEEEEEEEEEEEEEESSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS SSSSSSSSSSSSSSSSSSSSSSSSSSSSTTTTTTTTTTTTTTTTTTTTTTT TTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTT TTEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE EFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF _1_ _2_ _3__ Alt+Ctrl+D:SampleBBB2:~ 103:Character Counter is a 100% free online character c ount calculator that's simple to use. imple to use. ; Alt+Ctrl+Shift+F2:MAXIMUM TITLE IS HERE TO STAY AND I WILL NOT BE OVERSOLD ON HOW LONG THIS 1234 MAYBE A LITTLE MORE :DefShare=0; DefShare=0; DefShare=0; DefShare=0; DefShare=0; DefShare=0; DefShare=0; DefShare=0; Tilde (~) is the only character I can see different, as it shows as ~7E (0x7e is the hex code for that, so it makes sense) .. have you found any other? *EDIT* I see the 100 char now single line that you're talking about now. I guess I never tried anything between 51 and 100.

In testing this morning, I noticed DAS has managed to get in a significant request. To sum it up, it allows a single hotkey to cast not only a STOP order on fill (how we currently do it), but also price target orders with each order canceling / updating the position of the STOP when filled. You might not see a beta configuration tool for this for a bit, as I have to get a wrangle on the syntax and how I plan to handle the configuration options, but it's cool enough that I felt like sharing. If you're like me and use set Limit Orders to take profit (versus a scale-out hotkey like Andrew), this is a pretty useful addition.

For this, I didn't use any tools. I just looked at my .htk file and noticed the structured pattern. Is that a sign of being a major nerd? I think it might be .... I should note, I'm using the beta 5.5.0.5 (and now 5.5.1.0) so the structure may have changed a little .. I believe they made a change in 5.5.0.4 to increase the available character limit in the scripts. But I will say that doing any type of script creation is never a waste of time as you learn *a lot* by doing it. So the time may not have been worth the actual result, but it was worth the knowledge gained. Just my opinion. The new version of the Hotkey configurator will do the install for you. It uses a special uniqueID slug in the hotkey (that DAS ignores) which goes to a database and pulls the hotkey command, so you can then just login to the Hotkey Configuration tool and make your updates, upload your .htk file, and get a returned configured hotkey file. It will streamline the process and remove the Excel requirement because it's a web app. It also allows me to add better knowledge base / help and form entry for users. After I finish that, I plan to release my DAS Utilities package for Python which will have Config / Hotkey and Log parsers, plus a custom TTS alert example (so you can script alerts as you see fit). It'll be open-source and should make any creators life a lot easier as it gives a framework for this stuff.

If you have no intention to do Options, just go with the same package setup as the BBT one. Otherwise, you can do the $150 (Non-Pro) DAS data package and swap out the options for the ARCABook at the same price.

Ahhh, I didn't see it. Just wanted to relay it along.

Just to give some food for thought on this, but the Hotkey file is compromised of a defined structure. So the structure is like this: {*keycombo-as-string*}:{Title-as-string (max length: 99}:{script-as-string, max 51 bytes} \n (new lines are not rendered in notepad) If you go over the 51 byte limit, it adds a value to signify the total length of the command (including spaces). So this: ROUTE=ARCAM;ACCOUNT=TRIB8359;Share=200;TIF=DAY+;BUY=Send ..hotkey script is 57bytes, and what the program sees is this: ROUTE=ARCAM;ACCOUNT=TRIB8359;Share=200;TIF=DAY+;BU To do a multi-line (longer) command up to 999 bytes, you have to add the length in bytes. Format is this: {*keycombo-as-string*}:{Title-as-string (max length: 99}:~ {length of script}:{script-as-string, first 51 bytes} \n (new lines are not rendered in notepad) {51 byte chunk of script}\n {51 byte chunk of script}\n .. repeat until the end of the Hotkey Script. Using yours as an example, the correct syntax is this: Ctrl+Shift+2:Buy 200 Shares at Market:~ 57:ROUTE=ARCAM;ACCOUNT=TRIB8359;Share=200;TIF=DAY+;BU Y=Send What is most likely happening and why it changes when you tweak it in the DAS editor versus a text editor is that DAS is correcting for the hidden characters (new line, tab, etc). A slight issue in syntax can throw it off. Additionally, if you're editing while DAS is running, you have to open the Hotkey editor to load the changes into the memory space. They're only loaded on program initialization otherwise. If you're trying to create a dynamic hotkey; one where another program changes values; you have to do so by editing the values in memory directly. It's 100% doable, but takes a lot of knowledge. I had a working script that would automatically trail a Stop order to a moving average by a set offset as a prototype. It was just too cumbersome for distribution.

This (the price discrepancy) is fixed in the next release.

NASDAQ TotalView is the Full Depth Order Book data for NASDAQ, it includes Level 1, Level 2, and all quotes / transactions (time & sales). Others are: ARCA (NYSE), BATS/EDGA/EDGX, and then an assortment of smaller ones. Each data feed is the main feed for a particular exchange(s), so TotalView would have more complete data on NASDAQ stocks.

I've never personally seen this issue, have you tested a fresh install? Backup your DAS folder (I usually just .zip the entire C:\DAS Trader Pro directory) and then rename it. Install a fresh copy of DAS and do the minimal setup that allows you to test this (e.g. don't worry about all the different layouts / windows). See if the same thing occurs. If it doesn't occur, you could start fresh again and reconfig everything, or revert to your old install and then delete the chart(s) it's doing it on, create new charts, and relink them to the relevant montage. My guess is you stumbled upon some unknown bug that has the chart linked to multiple data sources. Or a mixture of config options that cause the anomaly.

Hi Jason, Great visual write-up. Regarding the bug .. I think this is more of a labeling issue than a bug in the formula. The % of Buying Power is to do a slight offset to the calculated maximum affordable shares for buying power (default is 0.97). The intention of that value was to act as a buffer for an 'Insufficient Buying Power' error people would get without it, it's why by default it's 0.97. Reversing the leverage to get equity occurs off of this value. I can see where a user might expect different behavior in certain situations. Looking at the settings in the quoted screenshots. If you have $5,000 equity with 4:1 margin (Total BP of $20,000) and you only wish to use 49% of the total Buying Power (maximum), then your effective Buying Power is $9,800, when we recalculate for Margin that becomes an equity of ~$2,450. With a max-account-risk of 1% of this refactored equity, it becomes a max $Risk of $24.50. This matches up with the share size given when you account for rounding. To get the 1% risk of $5000, you'd want to set this value to 100% (or more likely the 0.97 default). I'll adjust the instructions for it on the next version so users better understand it's intention.

Hi Taylor, I know a long time back there was an issue with a Streamdeck going rogue and firing all the hotkeys, I thought they updated that in software, but I remember reading on the Elgato forums that some users had to RMA their devices (faulty) ... you may want to contact their support. I've used my StreamDeck going on 18 months and have never had this issue .. but I don't have predefined share totals, so it wouldn't be able to send a valid order in my case. Now, you can implement a few protection mechanisms within DAS. If you go into DAS Main Menu -> Setup -> Trading Settings, set these: X - Check duplicated new order (same order in 10 seconds) -> This prompts you if a duplicate order is sent rapidly. X - Price Check -> Choose values that make sense for you. This won't do much in this case if your hotkeys define a price. X = Checkmark You could also add a modifier key to your hot scripts that is not reflected in the StreamDeck. Example: You'd set a hotkey in DAS to SHIFT+CTRL+1, set the StreamDeck to send CTRL+1. With this setup, you'd have to hold down SHIFT on the keyboard while you hit a button on the StreamDeck. As an added measure, you could also add to your Hotkey scripts a '; FocusWindow CHART;' at the end of all your current hotkeys that can buy / sell stock. CHART would be a name you give a particular Chart or something like the Market Viewer, via the Right-Click Window -> Config -> Name). This way if you get a rapid firing of hotkeys in the future, only one will be able to actually fire off because the window focus would move to something else and the other buy / sell hotkeys would fail until you manually bring the focus back to the montage. When you go live, you should also set up your maximum loss with DAS (it's a form you file), that will minimize actual risk because they'll sell everything / reject orders if you hit that level. I do it like this (example values): -$60 PnL --> Alert --> Speak 'Max Loss Warning' (this signifies I have room for one more full R loss) -$90 PnL --> Alert --> Speak 'Max Loss STOP' (this tells me to stop trading) -$120 PnL --> DAS Risk Form --> Auto Stop / Reject I give an additional 1R buffer between the point I'm supposed to Stop (self discipline) and the point DAS will turn the account off for the day and liquidate positions, to account for the higher-than-my-account commissions DAS calculates in.

I'm not sure if you're still around Shannon, but those hotkeys look correct. Did you generate them via the Excel or use them from somewhere else? Miscalculations can happen usually from two things -- 1) Accidentally fired a long order with a short hotkey (double-clicked above the price action on a long order) or 2) The estimated Buying Power factor isn't correct for your broker. IBCO and DEMO are 4:1, but CMEG can be as high as 6:1 or sometimes 3:1 .. it's why it's important to use the Excel sheet for those scenarios. I'd need the log files to properly see what's happening on that. I have an assortment of requests in with DAS to address stuff like this, they were accepted, but I don't know when development would begin. I'll be doing a video set on using the Scale-In hotkeys since a (currently in testing) update will add a few of them (Refactor Risk Scale-In, and Thor's Free Roll Scale-In) and I know users could use a little more guidance on their usage. In general, if you change the position (scale-in or scale-out/take-profit), you have to update the Stop. There currently isn't an option for DAS to do this for you. I've requested additions to be added to make this much easier in the future. You're better off using a Trigger Order for the second portion of that, they have the distinct advantage of being able to get data values in the future. Like this: LONG: CXL ALLSYMB; ROUTE=LIMIT; PRICE=BID-0.05; PRICE=Round2; Share=Pos*0.25; TIF=DAY+; SELL=Send; TriggerOrder=RT:STOP STOPTYPE:MARKET PX:StopPrice+0.3 ACT:SELL STOPPRICE:AvgCost QTY:Pos TIF:DAY+; SHORT: CXL ALLSYMB;ROUTE=LIMIT;Price=ASK+0.05;Price=Round2;Share=Pos*.25;TIF=DAY+;BUY=Send; TriggerOrder=RT:STOP STOPTYPE:MARKET PX:StopPrice+0.3 ACT:BUY STOPPRICE:AvgCost QTY:Pos TIF:DAY+; As a note, this Trigger order doesn't use the PX value at all, but it's there to prevent some errors in certain versions. Also, there's specific hotkeys for adding additional risk to an existing position. They'll be covered in a video when I finish the new hotkey for Thor and I'll go over how to scale-in. Special thanks to Justin and the other members who have been helping in this thread. I don't always make it back in a timely manner, so I really appreciate it!

Hi Girish, Sorry for the delay in replying, I decommissioned the old server and I'm currently building up a new server as I needed more power to handle all the data I'm adding. I'll post to the forums when I expose the gap list for users. -Kyle

Skip this post if you don't have a StreamDeck and / or aren't comfortable doing custom macros in your SD config. Advanced Uses: If you're adventurous and own a StreamDeck, you can do the swap automatically (so place once and then return to your default). In this example, I have the following DAS Config: Default Line: ALT+D (this is: HorizontalLine, DotLine, Black, 1px) Green Line: ALT+G (this is: HorizontalLine, DotLine, Green, 2px) Horizontal Line Tool: CTRL+ALT+L Using a StreamDeck extension "SuperMacro" (by BarRaider), I setup a "Super Macro" (type) hotkey in Stream Deck with this script in the Short-Press Macro box: {{CTRL}{ALT}{L}} {{ALT}{G}} {{LBUTTON}} {{ALT}{D}} Now, when I'm on the chart, I hover my mouse pointer over where I want to place a special line (like Moving Averages on the Daily Chart), I can simply hit my GREEN-LINE Button and it'll: Trigger the Line Tool --> { {CTRL}}{ALT}{L} } Set Line Config to Green --> { {ALT}{G} } Send the Left Mouse Button --> { {LBUTTON} } Set Line Config back to my Default Line { {ALT}{D} } Thus, it's a one key operation to place the special color line.

Ever wanted to swap line styles on the fly and make a rainbow on your chart? You can do that in 5.5.0.0+. The hotkey isn't the easiest to understand, so I very quickly made a web utility for you (link below). How to Use: Go to URL: http://kaelmedia.com/projects/das-line-config/ Select a Line Type, default is HorzLine Select a Line Style, default is SolidLine Select a Color, default is Barney Select a Width, default is 1 Hit "Generate" Glance at the preview window and see if it is what you wanted. If it is, hit the "Copy" button and it'll be placed in your computers Clipboard. If you wish to share you creation, press the "Share" button and a special link will be placed on your clipboard to post in the forums. Example: http://kaelmedia.com/projects/das-line-config/?hotkey=ConfigTrendLine horzline dotline:035aab:1; Paste the copied hotkey (looks like: ConfigTrendLine horzline dotline:035aab:1; ) into your DAS Hotkey Configuration. Optionally, bookmark or save the line so you can edit it in the future (it adds the settings to the browsers URI/URL). How the Hotkey Works: The hotkey as designed will swap the DEFAULT config for the Line Type chosen, each type has one default stored for the user. So if trigger a hotkey with a horizontal line with a blue color, your very next (and all following lines) horizontal line you trigger on the chart will be that configuration (blue). Because of this, I have a "default line" hotkey and a series of colored hotkeys, this allows me to toggle back and fourth. Advanced Uses: Go HERE.

First, check your Setup -> Trader Settings -> "Price Check" value .. this can sometimes reject your order if it's outside your configured parameters. Make sure you're using LIMIT (or SMRTL) orders as well. To do the Bid+%OfStockPrice, you'd do something like: Price = Bid * 1.005; Price=Round2; That's BID * 0.5% (half a percent). So if the BID equals $55.42, it'd calculate as: 55.70 (55.6971 --> Round2 --> 55.70).

You can't do it programmatically / automatic at the moment. I have a feature request in with the developers to allow us to do this with a new set of hotkeys. There *is* a legacy feature in DAS that does it for you, but it's very odd in how you have to set the initial order and doesn't always work (at least for me), so I wouldn't recommend using that. The only other way is the way peterB mentioned and that is by Canceling out the orders and then putting a new one in.

Just to help me shape this. What do you people want to see in terms of information? Would you rather have a breakdown of the math behind them and then show how they work in DAS, or would you like a more detailed breakdown of the actual hotkey (as ugly as they are)? I'd assume the former is better for most as it's a "concept -> application" presentation, keeping to the important bits in a concise manner. Any other hotkeys / DAS features you want me to go over, please post here. I have a list going. For this presentation there will be a new version of the hotkeys / configuration rolling out, so even if you're familiar you may want to check it out. I've also discussed with DAS on some modifications, but I'm not sure what the timeline is on those.

There's a built-in less known about hotkey for that called ShareCap. You could try to add it as ShareCap=1000; at the beginning of your hotkey. Test in sim though, as I haven't tested it. It's very limited because of the user-accessible memory areas. In the Excel Configuration there's a couple that will put 1:1, 2:1, and 3:1 (etc.) price targets. DAS has indicated that they're willing to make changes to allow to us to do more of this natively. I'll add your request to the list I have going for their devs. There's a few other methods you can do to get values in and out of DAS, but they're really complex and I would not recommend anyone using them. One way is to use a secondary program (you write it) and the OS's native clipboard (to pass data back/fourth). The other way is to search and replace the bytes in active RAM. Are you with IBCO and was this during a LIVE trade? I believe IBCO on the short side does 3:1 margin, not 4:1. So if you use the 4:1 margin hotkeys with them when short (and live), it'll calculate your Buying Power incorrectly. As Brandon said, this is usually caused by Buying Power. His math is correct, you weren't able to take the full $20 risk on this and ended up with a much lesser risk, but still ~2:1 return. My guess is the problem exists in the first part of the hotkey config where it does the BP/equity calculations. If you didn't generate your own hotkeys via the Excel Configuration sheet, I highly recommend you do that. The ones people copy and paste aren't setup for everyone, they're specific to the person who created them (and their account variables, such as their margin-ratio which can different from broker to broker). I'd say 90% of the math issues come from this fact.

That's a feature you'd likely have to request them add to the PriceMarker Chart Study. Right now, it only has "Last Bar High" (and Low / Open / Close. Last Bar is the current active bar). You'd want to request one for "First Bar" and then you'd just add the study to a 1min chart.

Some users asked about this in chat a while back and as I was writing up the documentation on how to do a dual-copy of DAS Trader Pro -- one version for Sim and another for Live -- I realized that it had some complexity which may have made it difficult for some end-users. So to remedy this, I wrote a script to do it for you. I did this with batch / powershell commands (it's been awhile, so not eloquent at all) so that users can see what is going on (no tomfoolery with your accounts). What Does It Do: It's a Windows 10 (if Mac users exist, your mileage may vary) script that will: Makes a mostly symbolic copy of your DAS Trader Pro install (it'll copy over the Config.cfg file, since we need to change a few things) --> If your DAS install is C:\DAS Trader Pro\ it'll create a C:\DAS Trader Pro_Sim\ folder. By default, only the theme folder and .exe exist in the new folder install (the SIM version will check for a version change on the .exe and copy it over as needed for when updates occur), the rest is symbolically linked via the file-system to the main install. This is done so that items carry over their settings (Trendlines, Desktop Layout, Hotkeys, etc.). This is beneficial because if you use the default config then all layout, chart, trendlines, hotkeys, and other options stored outside of the Config.cfg file will be the same in both versions. You can change this behavior with options (more on that in setup below). Right now, options exist for: Desktop Layout (default.dsk), and the Hotkey File (hotkey.htk). Change the background of the simulator install (for better visual recognition). [optional] Add A Sound Alert for the Simulator version when a LIVE account trade is made in it [auditory recognition]. [optional] Add a Sound Alert for the Live version when a Simulator account trade is made in it. Example Image Notes / Prerequisites: If you set your account via as part of hotkey scripts (e.g. "ACCOUNT=U#######") you will want to change those values in your hotkey.htk file and also toggle the config.ini setting for separate_hotkey_file to "separate_hotkey_file=1" (instructions below). I assume most users won't need to this do. How Do I Use It?: Glad you asked. Download the zip file linked below and then follow the instructions here. As a precaution, I recommend you make a backup copy of your DAS install. Easiest way is to go to the folder that contains your DAS install, right-click it, and select "Send to Compressed Zip" .. if your install is in C:\, you'd right-click the "DAS Trader Pro" folder there. Unzip the downloaded file to a directory. If you use the DAS default install location of "C:\DAS Trader Pro\" - and / or - wish to have the defaults, skip to step 3. If you don't use that location, continue reading this part. Go into extracted directory and edit "config.ini": Config Available: ⓐ directory=C:\DAS Trader Pro This is the location of your DAS install. By default, it's C:\DAS Trader Pro as that is the DAS default. ⓑ separate_desktop_file=0 This is if you want to have separate Desktop.dsk files for SIM and LIVE. By default, it's the same layout. To use separate desktop files, set this as: separate_desktop_files=1 ⓒ separate_hotkey_file=0 This is if you want to have a separate Hotkey.htk file for SIM and LIVE. By default, it's the same file. To use separate hotkey files, set this as: separate_hotkey_file=1 ⓓ add_sound_alerts_sim=0 This is if you want to have a sound alert added to your DAS SIM, for this to work properly there will be additional setup (see section "Sound Alerts - SIM Account"). What it does is add an audible alert if you trade with your LIVE ACCOUNT in the SIM ACCOUNT. To use, set to: add_sound_alerts_sim=1 ⓔ add_sound_alerts_live=0 This is if you want to have a sound alert added to your DAS LIVE, for this to work properly there will be additional setup (see section "Sound Alerts - LIVE Account"). What it does is add an audible alert if you trade with your SIM ACCOUNT in the LIVE ACCOUNT. To use, set to: add_sound_alerts_live=1 Right Click "Setup.bat" --> Run-As Administrator a) On Windows Admin Prompt Click "Yes" b) On the command window that opens, make sure it does not give an error. If prompted, type the letter "Y" and hit enter. c) If no error messages, hit enter again to close the command window. Launch DAS using the shortcut created on the desktop as "DasTrader - SIM Account" --> Under ... Blue w/ S is the SIM account. Yellow w/ L is the Live account. You're not done ... go to Additional Setups section. Additional Setup: There's some brief changes we need to make within DAS for this to work properly. Open the "LIVE" version of DAS (the yellow icon). Login and on the top menu bar select "Setup" -> "Order Templates" On the "Account" box, select your LIVE account (for IB users it's likely something like U#######). Hit "Apply This Setting To All Exchanges." [optional] If you enabled the SIM trade in Live Account alert in config.ini, read the next line, otherwise skip to #5. For the Alert to work, go into Top Menu Bar -> Tools -> Alert & Trigger -> Double Click "WARN-LIVEACCOUNT" -> Double Click the "Value" box next to the "Acc" item (it should say "U1111111") -> Set this to your LIVE account. Image helper here. Close DAS. Open the "SIM" version of DAS (the blue icon). Login and on the top menu bar select "Setup" -> "Order Templates" On the "Account" box, select your SIM account (for IB users it's likely something like TRIBT####). Hit "Apply This Setting To All Exchanges." For the Alert to work, go into Top Menu Bar -> Tools -> Alert & Trigger -> Double Click "WARN-SIMACCOUNT" -> Double Click the "Value" box next to the "Acc" item (it should say "U1111111") -> Set this to your SIM account. Image helper here. Close DAS. Download: v1.00 - 1/14/2020 - outdated .. v1.01 - 8/7/2020 - DAS_DASSim_Separation_Script_V1.1.zip Changelog: v1.00 - 1/14/2020 - Release of initial script. v1.01 - 8/7/2020 - Quick rework of the script to be in its own .EXE, this may help with any issues for permissions. Known Issues: v1.00 - 1/14/2020 - My father never really played catch with me as a child, but besides that, there doesn't seem to be any that I'm aware of with the script at the moment. /joke