Valid names for SETUP ?
I have the HF-6065 with beta 31 firmware installed. I am using LCS V188.8.131.52
I am using the SETUP command to initialize the HF-6065. But some of the keywords listed in the API documentation aren't accepted, and either cause an error message from LCS, or else the script doesn't work right after I load it into the HF-6065
If I use only the keywords given in the examples and the factory-default scripts, SETUP works.
For example, the following SETUP script works perfectly:
RESBANDW:2 VIDBANDW: 0
But when I added two additional parameters (ANTTYPE and CABLETYPE), then it won't work:
RESBANDW:2 VIDBANDW: 0
Is it possible to get a list of parameter names which can be used in SETUP?
I have the programmer's guide dated 2010-09-14. Although it lists names for all of the environment variables, not all of these names are known to the assembler in LCS (V184.108.40.206)
Specifically, LCS knows the names of the environment variables from 01h to 0Ch, 20h, 30h to 32h, 41 to 43h, and 60h. As far as I can tell, these are the only environment variables that can be used in the SETUP function.
It is possible to use STORESET and the absolute address of the environment variable to setup other values. For example, I set up a button to toggle the internal preamp on and off by using the following code:
But this will not work at all if I enter the name "PREAMPEN." It will only work when I use the actual address (16 dec, 10h)
FYI, a good way to find out how LCS processes assembly language source code is to enter some assembly language statements, then compile and write to the HF. Next, click the "New Read" button in LCS file manager to read back the object file (binary data) back from the HF. LCS then "disassembles" the binary data back into a "source code" listing. Note that LCS will only insert the names for parameters it knows about. Unknown environment variables will be printed out with their absolute addresses instead of their names. Note that the LCS "New Read" disassembler sometimes generates decimal numbers rather than hex. Decimal values appear like the "16" above in "LOADSET 16." When LCS disassembles a parameter into into a hex value, it always writes it out as "50h" (for example).
I hope this is helpful to other HF and LCS users!