Error on calling 'OnBarUpdate' method on bar 0

[elliot5]

I have made the changes and still have the same out of range errors.....

[NinjaTrader_ZacharyG]

Hello everington_f,

Please provide your updated script so I may investigate further.

[elliot5]

WIth platformsupport now. Regards

[NinjaTrader_ZacharyG]

Hello everington_f,

I am not experiencing any out of range run-time errors with the updated script that you have provided me.

Please completely remove the strategy and then re-add it. Once the strategy has been re-added, test once more.

If you are still running into this run-time error:

Can you please provide additional details on how you are testing this script on your end?

Are you adding this strategy on a chart or through the Strategies tab of the Control Center?

If on a chart, what are the settings that you have set in the Data Series window? You can access this by right-clicking the chart and selecting Data Series.

Can you provide what instrument you are testing on? Can you provide the parameters that you are using for your strategy?

[elliot5]

Added on a chart JPM daily 390 minutes US Equities RTH.... this time looked like it was going to work but then gave the error again after about a 20 second pause - parameters are .
on price change
lookback 256
bars required 50
immediate submit
entries per direction 1
unique entries

[elliot5]

I have it working now having run the strategies from the strategies tab. Do you know why running from charts is problematic? Regards

[NinjaTrader_ZacharyG]

Hello everington_f,

I am not seeing any run-time errors occur when testing the strategy on a chart.

What I would suggest is adding a print statement before each of your conditional statements. This way, we can narrow down what conditional statement is causing the run-time error as the print will be able to print out first before the line of code that causes the error to occur executes.

As an example, you can place

Print("About to run line 125");

before line 125. If an error appears right after that, we're able to narrow down what section's causing the error.

Make sure that the NinjaScript Output window (New -> NinjaScript Output) is open before testing.