Hi,
Yes, that’s always going to be difficult when the code is not accessible, but that won’t stop me, here,s what I’m thinking based around my earlier comments above. Using the Guessing and Assuming technique, systematic approach to formulate questions and throwing a spanner in the works!…..
The code above/below the ‘call’ does not set any of the ‘call’s parameters, only literal values – so they are fixed! – that’s convenient, and the only return is used in the logic of the ‘if’ statements. The other code does not appear problematic especially with respects to the error message, nothing else implied. Therefore focusing on the ‘call’.
The ‘call’ to the indicator returns ‘2’ parameter’s and accepts ’19’ parameter values and is calculated on ‘Close’ data.
- Have you set the minimum required ‘unit’ setting for the indicator to be able to do its calculations.
Looking at the return parameters, since there’s only two, your ‘ignore’ ing the 1st, which I think may give a changing value with respect to each bar change, and the 2nd your using, appears to return ‘1’ or ‘-1’.
- What is the number range of this 2nd param, what happens if its ‘o’ or another value, can it be etc.
- Why not use the 1st, what is it, what’s it’s range, etc.
Now the input param’s, that’s a lot, I’m assuming you now what they are since you have put in values for them.
- Is there ’19’ param, too many, too little
- What type of number do these each expect
- Boolean, integer, decimal , etc
- What range do these number expect, the range should be limited in the indicator, but if not, could allow you to set a value beyond its capacity to calculate properly and create a runtime error which inadvertently trigger the main error.
- Are the numbers you’ve chosen correct, extreme, ball park, as advertised,
- If you don’t want to use a param, has it a default value, do certain params rely of other params, ect
Some of the questions posed could be found in the indicators documentation, watch out for things that are ‘not’ said or implied! don’t assume here and expect spelling mistake. You can build up a picture of what you actually know, so you can focus on what you don’t, and assuming a typo is done once do other reference differ or agree.
Warning – if your testing make sure you disable the ability of the code to trade, and/or replace with a visual representation in the chart panel of correct logic operation.
Other answers can be found by testing, this should give you other error messages, which could validate certain things. Looking at it from the point of view which error comes first, the one you create against the main error. By deleting one piece of the code, one of the following points, replacing and trying another.
- delete 1st return param ‘ignored,’
- delete a call param
- add a extra return param
- add a extra call param
- Since an array index need an integer, set all your input ‘call’ params to integers, does that make a difference.
- is ‘BladeSCALPER’ spelled right
Try the ‘call’ in a different file, set up visual output of return values, use 1st return as well, if value’s wildly differ on screen, offset the logic with value to show both in similar position range. i.e. param 1 (param @ 12,345) ….. param2(12400+param2 ) =12401(1),12399(-1) you can zoom in or just look at the scale or cursor labels. This will give further detail on the data values inside ‘call’ indicator, maybe there’s something you see and add another piece to the puzzle.
Based on the error message and my earlier comments on array indexes, if that’s right, then a combination of PRT setting, along with the trade instrument you using, the indicator code, and your purchased indicator, set the seen of the problem.
All this is something you can do, it may help solving the problem, no guarantees, but in the long run will help in other situations. If you get rid of the main error by changing stuff, then that need focused scrutiny to determine why, and what difference has occurred.
If you fail to find your own solution, at least you will be in a better position to ask a list of systematic probing questions to the seller.
Can’t think of anything else, to summarize generally, if you can logically learn, and get ahead of the problem you’ll get closer to identifying the problem. Then, you’ve got another problem, ‘The solution!’. Feel free to ask about anything you find.
Goodluck!
.
