All custom PIDs result in <unsupported parameter>

[reactor2]

Defect Description:
Creating any custom PID results in <unsupported parameter>

Reproduction
1) Select to create user defined PID
2) In the function edit box enter:
[PID.6001]
3) Save and close
4) Start scanner
5) Notice that custom PID resolves to <unsupported parameter>

Details
VCM Scanner 2.24.57

[reactor2]

Figured it out.

Whenever you create a custom PID make sure you scanning the variables you are referencing in the custom PID AND make sure they are in order. I would say this is definitely a bug, but it is what it is. For certain, <Unsupported Parameter> is basically worthless, it would be nice if it told us why the parameter is unsupported.

[LS2GO]

Thanks reactor2 !! I'm having the same problem, would be awesome to have at least a workaround. Imma test this next time in the garage