DAP Technology 1394, Operation Manual

Page: 117 / 458

Recorder
117 Copyright © DapTechnology B.V., 2005-2019 - All Rights Reserved., 5/20/2019
condition may be entered.
A condition can be set by specifying a condition and a value. In the example above for instance, a
condition is set on the Source field.
A packet only fits the Set if all specified conditions (and that are not disabled) are true for the packet.
In the example above for instance, a packet does not fit the Set if the Source field is not equal to 0xFFC1.
The Header Values table has the following columns:
· Field. The Field column displays the header-field name. Note that only those fields are enabled that are
present in all the selected types in the Primary-Packets box. Fields not enabled are displayed with a
gray color.
·
Cond. Here a compare type can be selected. You define a compare type by clicking in this field and
select the type from the combo box. You can select the following types:
· == condition met if the packet-field value equals the specified Value.
·
!= condition met if the packet-field value does not equal the specified Value.
·
<= condition met if the packet-field value is less than or equal to the specified Value.
· >= condition met if the packet-field value is greater than or equal to the specified Value.
You can also select an 'empty' operation, meaning that the field condition has to be removed.
Selecting this will also remove the field Value.
Note that for each byte in the packet, only one condition may exist, unless the condition is '=='. You
can for instance not put a '<=' condition on the Transaction Label field if there is also a condition other
than '==' on the Retry Code field. If both conditions are '==', there is no problem. The software will
inform you about possible conflicts as soon as you try to Apply the settings.
·
Value.Here you can specify the value for the condition. You can enter values in decimal or hexadecimal
notation. If you clear this field, the compare type in the Cond. columns will be removed too. Together
with the compare type from the Cond. columnm it specifies the condition the packet field should have to
fit the Set.
· Mask. Before the packet field is compared with the Value, a logical and is performed with this optional
Mask value. It can be used to mask one or more bits before the compare is done. For each bit in the
mask with value 0, the corresponding bit in the packet field and the corresponding bit in the specified
Value will be cleared before they are compared. If, in the example above, a mask value of 0x003F was
specified for the Source field, then effectively only the lower 6 bits are compared because all other bits
will be zero-ed by the mask operation.
Data Values
Here you can specify additional data-field conditions. Basically, it works the same as the header-field
conditions, but because the format and size of data fields are not fixed, a powerful packet-data editor has
been added. Here you can select the format for all kinds of data-payload types.
In the example above for instance, the CommandOrb format (part of the SBP2 support) has been
selected as the packet payload format. This gives you some fields on which conditions can be set. In the
example above, the conditions are such that a packet will fit the set only if the rq_fmt field equals "SBP2
standard", the direction field equals "Read", the speed field equals "S100" and the 'data size' field is
greater than or equal to 1024. Note that some values can be selected by selecting a symbolic value from
a combo box, so you do not have to look up these values. If you want to know the values of these
symbolic names, you can look inside the 'Layout' tab, or you can use a right mouse click and select the
'Decimal'-values option for instance.
For some formats, there may be a data field for which you can define a separate sub-format in an
additional tab. Here you can also add additional conditions for the fields in that sub-format. In the
CommandOrb format example above for instance, the 'command' field can be sub-formatted in an
additional tab. In the example below this additional 'command' tab has been selected. The 12-bytes
command is shown here. Now you can select a separate format for this 12-bytes command. In the
example, we chose the 'Simplified direct access' command set, which is part of the SCSI specifications.
This format can show all SCSI commands that are part of that set. When you select another operation
code, the format will adapt to the format for that particular command. This way it is very easy to add
additional conditions on fields that are specific for a command set and specific to a command from that
set. In the example below for instance, additional conditions are added so that only a READ(10) command
that has also a 'transfer length' field value of 1024 or more fits the set.