Dear Paul,
This is a problem with SAM 2014.1.14 and the SAM SDK 2014-1-21. SSC requires the variables that you see listed in SDKtool, and there are separate input variables that SAM uses, and in the case of the CSP models, also TRNSYS variables. Some of the variables you see in the SamUL list are variables in SAM's user interface that are not used by SSC.
In the new version of SAM, currently in Beta testing (SAM 2014.9.30), we've completely rewritten the underlying code to eliminate this extra layer of code and associated variables between the user interface and SSC. The SAM inputs browser in the Beta version lists SSC variable names and their values, which makes what you are trying to do a little easier. We've also replaced the TRNSYS simulation engine for the CSP models with a new engine so that all of the calculations happen in the SSC environment.
Furthermore, in the new version of SAM, we've replaced SamUL with the LK scripting language. That means that SAM and SDKtool use the same scripting language.
We plan to develop a tool to export LK script from the SAM user interface that you can then run directly in SDKtool, but that is not yet available.
So, my recommendation would be switch to the new version of SAM -- you can start now with the Beta version. I realize that will involve some work to recreate SAM files and port your SamUL script to LK. We plan to release the new version in mid-November.
Otherwise, if you have a list of the long user-interface variable names from SAM 2014.1.14 for which you need SSC equivalents, you can send me the list, and I will try to match them up.
Thanks,
Paul.