If the ‘call’ed indicator has the timeframe command in it, I think that causes the parse error.
Its best to write the code directly in the strategy file, this avoids the longer execution times with the calling process.
However, it can work if the TIMEFRAME command is in the strategy file and the call is from the timeframe block, but it will be longer to execute.
Also the indicator file has to be suitably set up as a general indicator which works with any timeframe its put on.
Keeping the execution time down , helps when back-testing.
2 users thanked author for this post.