User`s guide

3 Signals and Parameters
Note If your model has the output of a Mu x block connected to the input of
an xPC Target Scope block, the signal might not b e observable. To ensure that
you can observe the signal, add a unity gain block (a Gain block with a gain of
1) between the Mux block and the xPC Target Scope block.
Using xPC Target Scope Blocks from Referenced Models
You cannot add any type of xPC Target scope to a referenced model. Doing
so causes an error. You can add only an xPC Target scope to the topmost
model. If you want to log signals from referenced models, you can do so with
the logging mechanism in xPC Target Explorer or with the xPC Target scope
objects.
Scope of Type Host
For a scope of type host, the scope acquires the first N samples into a buffer.
You can retrieve this buffer into the scope object property
sc.Data.Thescope
then stops and waits for you to manually restart the scope.
The number of samples
N to log after triggering an event is equal to the value
you entered in the Number of Samples parameter.
SelectthetypeofeventintheBlockParameters: Scope (xPC Target) dialog
boxbysettingTrigger Mode to
Signal Triggering, Software Trigge ring ,
or
Scope Triggering.
ScopeofTypeTarget
For a scope of type target,loggeddata(sc.Data and sc.Time)isnot
accessible over the comman d-line interface on the h ost PC. This is because
the scope object status (
sc.Status)isneversettoFinishe d. Once the scope
completes one data cycle (time to collect the number of samples), the scope
engine automatically restarts the scope.
If you create a scope object, for example,
sc = getscopes(tg,1) for a scope
of type
target, and then try to get the logged data by typing sc.Data,you
get an error message:
Scope # 1 is of type 'Target'! Property Data is not accessible.
3-50