<< Click to Display Table of Contents >> Navigation:  Recipes > Recipe Send To

 

This box is only displayed when there is more than one identical instrument that the recipe could be sent to, and allows the Source and Target instrument(s) to be selected:

 

 

This will only send instrument variables to the specified instrument, it will not affect SpecView User Variables, however, see below.

 

Problems during download

 

 

For Recipes which include User Variables:

 

Recipe Send-To is intended to send from one instrument to one or more other instruments...but there is only one set of User Variables.

Consequently, normally, any User Variables that are in the recipe are NOT sent at all because it could be misleading - if a recipe is sent to 2 instruments, then the User Variables would be written to twice.

 

However, there are some cases where sending to a User Variable is useful:

 

1) If a profile has a SpecView-checked Hi-Limit-policeman (stored in a User Variable) that varies depending on the recipe downloaded. Once downloaded, the Strategy copies the single User Variable to the correct one for the instrument based on which device the recipe was sent to.

 

2)  When manually (not via Strategy) doing a Recipe Send or Recipe Send-To there is no way to tell if it was successful or if the recipe download was aborted by the user part way through. 

So putting a Boolean User Variable at the end of the recipe download (using Recipe Levels) will mean that if it gets all the way through it, then the Boolean will be set (indicating it was completed).

 

Note: The default is NOT to send-to User Variables.

To allow this add to SETTINGS.INI in the [RUNTIME] section:

 

           RecipeSendToUserVars=1