TradeStation · EasyLanguage
Strategies, indicators and RadarScreen columns written in EasyLanguage, plus changes, fixes and conversion of existing code. This is the work the rest of this page describes.
Hire an EasyLanguage developer for TradeStation strategies, indicators and RadarScreen columns — or to change, fix and convert the EasyLanguage code you already have.
Strategies, indicators and RadarScreen columns — and the EasyLanguage code you already rely on.
Nordman Algorithms writes EasyLanguage for traders who use TradeStation. Our EasyLanguage developers work from trading rules, a written specification or just a plain description, or from existing code that needs changes or fixes.
The work covers strategies, indicators, the functions behind them, and RadarScreen columns. Each one is checked on your symbols and settings before delivery, and you receive the EasyLanguage source and all rights to it.
What we take on, what we consider case by case, and what is covered on another page.
Strategies, indicators and RadarScreen columns written in EasyLanguage, plus changes, fixes and conversion of existing code. This is the work the rest of this page describes.
Looking for a PowerLanguage developer? PowerLanguage is closely related to EasyLanguage, so we are open to MultiCharts projects. We review the code first and confirm whether it is work we can take on.
For TradeStation API integrations and external trading applications, see our TradeStation development page.
Three kinds of TradeStation work, written by our EasyLanguage programmers from your rules.
Automated strategies with entry and exit rules, position sizing and stops, ready for backtesting in TradeStation.
Indicators, including ShowMe and PaintBar studies, and the custom functions behind them.
Custom columns that show your conditions across a list of symbols, including chart indicators adapted for RadarScreen with their values checked against the chart.
An EasyLanguage developer working on the strategies and indicators you already have.
New conditions, inputs, filters and alerts added to an existing strategy or indicator, without changing what already works.
Verification errors, strategies that do not trade as expected, indicators that plot the wrong values, and differences between historical calculation and real-time behaviour — traced to the cause in the code and corrected where the code allows.
EasyLanguage logic rebuilt in Pine Script, NinjaScript or MQL4/5, and logic from those platforms rebuilt in EasyLanguage. We compare the results, allowing for differences in data and sessions.
Describe what you need and send the EasyLanguage source if there is existing code. We will review your requirements and existing code, then outline the scope and next steps.
We agree the rules, the symbols and settings you use, and the acceptance checks with you before any code is written.
Send a description of the rules or the change you need, and the EasyLanguage source if there is existing code.
Receive the EasyLanguage source, the file ready to import into TradeStation, and a guide to every input. We walk through the specified behaviour and provide technical support under the agreed terms.
Work with EasyLanguage programmers who also build for other trading platforms.
We also write Pine Script, NinjaScript and MQL4/5, which helps when logic has to move between TradeStation and another platform.
Requirements, deliverables, fixed price and acceptance examples are agreed before development begins.
An NDA is available on request. Source code and full IP ownership are transferred on delivery.
Installation help, input explanations and technical answers within the agreed support scope.
Feedback from clients across our custom trading software projects.
Practical answers about EasyLanguage code and TradeStation.
Yes. A strategy can act as prices change within the bar rather than waiting for it to close. It then behaves differently in backtests than in live trading, so we agree how it will be tested before development begins.
Yes, if you have its EasyLanguage source. We go through the existing code first, then add or change what you need so the parts that work keep working.
No. Protected code cannot be opened or edited without the original source. If you have the rules or examples of how it behaved, we can tell you whether it can be written again.
Yes. We rebuild EasyLanguage logic in Pine Script, NinjaScript or MQL4/5, and the other way round, then compare the results, allowing for differences in data and sessions between platforms.
Case by case. PowerLanguage is closely related to EasyLanguage, so many MultiCharts strategies and indicators are close to what we write for TradeStation. Send the code or a description and we will confirm whether we can take it on. MultiCharts .NET, which uses C#, is a separate case.
For TradeStation API integrations and external trading applications, see our TradeStation development page.
A description of the rules or the change you need, and the EasyLanguage source if there is existing code. Chart screenshots help as well.
Send your rules, or the EasyLanguage code and what should change. We will review it and outline the scope and next steps.