| TRICK 7 TO TRICK 10 VARIABLE SERVER COMMAND DIFFERENCES KEY : |  |  |  |  |  |  |  |
| Bold = Default behavior |  |  |  |  |  |  |  |
| Green = New Trick 10 feature or implementation is different than Trick 7 |  |  |  |  |  |  |  |
| Blue = Need a Trick 10 interface routine |  |  |  |  |  |  |  |
| Orange = Not implemented in Trick 10 / presumably not needed |  |  |  |  |  |  |  |
| Red Bold = Not implemented in Trick 10 / needs to be fixed |  |  |  |  |  |  |  |
TRICK 7 | TRICK 10 | DESCRIPTION |  |  |  |  |  |  |
var_add <variable_name> ; | trick.var_add("<variable_name>") | ADD A VARIABLE TO LIST OF REGISTERED VARIABLES FOR VALUE RETRIEVAL |  |  |  |  |  |  |
var_add <variable_name> {<units>} ; | trick.var_add("<variable_name>", "<units>") | A VAR_ADD THAT CAUSES THE RETURNED VALUE TO BE IN SPECIFIED UNITS |  |  |  |  |  |  |
var_ascii ; OR var_binary ; OR var_binary_nonames ; | trick.var_ascii() OR trick.var_binary() OR trick.var_binary_nonames() | RETURN VARIABLE VALUES IN ASCII OR BINARY FORMAT |  |  |  |  |  |  |
| trick.var_byteswap(True|False) | WHEN VAR SERVER AND CLIENT ARE ON DIFFERENT MACHINE ARCHITECTURES WITH DIFFERENT INTERNAL NUMBER REPRESENATION (ENDIANNESS), BYTESWAP RETURNED VALUES* |  |  |  |  |  |  |
var_clear ; | trick.var_clear() | REMOVE ALL VARIABLES FROM LIST OF REGISTERED VARIABLES FOR VALUE RETRIEVAL |  |  |  |  |  |  |
var_cycle = 0.1|<sec> ; | trick.var_cycle(0.1|<sec>) | SET FREQUENCY AT WHICH REGISTERED VARIABLE VALUES ARE RETURNED |  |  |  |  |  |  |
var_debug = <0|1|2|3> ; | trick.var_debug(0|1|2|3) | PRINT TO TERMINAL INCREASING AMOUNTS OF DEBUGGING INFORMATION |  |  |  |  |  |  |
var_exists <variable_name> ; | trick.var_exists("<variable_name>") | RETURN BOOLEAN 0 OR 1 AS TO WHETHER THE SPECIFIED VARIABLE EXISTS |  |  |  |  |  |  |
var_exit ; | trick.var_exit() | EXIT THE VARIABLE SERVER FOR THIS CLIENT |  |  |  |  |  |  |
var_mcast <multicast_address> <port> ; | NOT IMPLEMENTED | CAUSES RETURNED VALUES TO BE DIVERTED TO MULTIPLE CLIENTS AT SPECIFIED ADDRESS/PORT |  |  |  |  |  |  |
var_pause ; | trick.var_pause() | PAUSE THE CYCLIC RETRIEVAL OF REGISTERED VARIABLE VALUES |  |  |  |  |  |  |
var_remove <variable_name> ; | trick.var_remove("<variable_name>") | REMOVE A VARIABLE FROM LIST OF REGISTERED VARIABLES FOR VALUE RETRIEVAL |  |  |  |  |  |  |
var_send; | trick.var_send() | REQUEST VALUES TO BE SENT IMMEDIATELY (USEFUL DURING VAR_PAUSE OR BEFORE VAR_CLEAR) |  |  |  |  |  |  |
var_sync = <Yes|No> ; | trick.var_sync(0|1|2) | RETURN VARIABLE VALUES IN SYNC WITH SIM EXECUTION FRAME (TRICK10: 0 is ASYNCHRONOUS, 1 IS DATA SYNC BUT WRITTEN ASYNC, 2 IS DATA & WRITE SYNC) |  |  |  |  |  |  |
var_units <variable_name> {<units>} ; | trick.var_units("<variable_name>", "<units>") | CAUSES THE RETURNED VALUE (OF A PREVIOUS VAR_ADD) TO BE IN SPECIFIED UNITS |  |  |  |  |  |  |
var_unpause ; | trick.var_unpause() | CONTINUE (CANCEL PAUSE OF) THE CYCLIC RETRIEVAL OF REGISTERED VARIABLE VALUES |  |  |  |  |  |  |
|  | * NOTE ABOUT HANDSHAKING |  |  |  |  |  |  |

THE TRICK7 VARIABLE SERVER USES HANDSHAKING AT CONNECTION TIME IN ORDER TO KNOW
WHETHER THE CLIENT AND SERVER ARE DIFFERENT AND REQUIRE BYTESWAPPING. BECAUSE
THIS IS RARE, THE TRICK10 VARIABLE SERVER DOES NOT USE HANDSHAKING. SO REMOVE ANY HANDSHAKING YOUR CODE DOES TO CONNECT TO THE VARIABLE SERVER IN TRICK10 (E.G.,
IF CONNECTING VIA TRICKCOMM (tc_connect) SET THE DEVICE'S DISABLE_HANDSHAKING
FLAG TO TRUE.)