Search results

In the following examples the addresses ''10.5.1.1'' and ''10.5.2.1'' name two such interfacess. ifconfig tap0 10.5.1.1/24 up

== Step 1: Find Host and TCP port == Element count: 1

addr=`echo $line | sed -e 's/.*inet addr:\([0-9\.]*\).*/\1/'` bcast=`echo $line | sed -e 's/.*Bcast:\([0-9\.]*\).*/\1/'`

* <CODE>N to 1 Low Value</CODE> * <CODE>N to 1 High Value</CODE>

<table border="1"> <tr><td>NOA<td>ULONG<td>Yes<td>1<td>Yes<td>No<td>No<td>No

feature to be introduced in EPICS 3.15.1 (not yet released). Rule #1 means that it is only safe to read, write, or de-reference the BPTR field f

...N is used as the specifier of which link to process. For instance, if SELN=1, then LNK1 will be processed. :* If bit 1 of SELN is set, LNK2 is processed.

<TABLE BORDER="1"> <TD>DOL1<TD>Desired Output Link 1<TD>INLINK<TD>Yes<TD>0<TD>Yes<TD>Yes<TD>No<TD>No<TR>

...place the value in RVAL. For these devices record processing sets VAL = (0,1) if RVAL is (0, not 0). Devices support modules may optionally read a value <TABLE BORDER="1">

...record processing and these fields, see Scanning Specification, Chapter 1, 1. A few records have unique fields that also affect how they process. These <TABLE BORDER="1">

The normal use for this record type is to store a simple bit (0 or 1) value to be sent to a Digital Output module. It can also be used to write <TABLE BORDER="1">

<TABLE BORDER="1"> <TABLE BORDER="1">

The RARM field causes the device to re-arm when this field is set to 1. <TABLE BORDER="1">

== STEP 1: Create GPIB application == ## 1 Register all support components

<TABLE BORDER="1"> ...eveloper's Guide''', chapter libCom / calc / Infix Expression Syntax (19.2.1 for EPICS 3.14.11). The length of the CALC field has changed in recent rele

<TABLE BORDER="1"> <TABLE BORDER="1">

field(INPJ, [1, 2, 3, 4, 5])

<TABLE BORDER="1"> which will be used. If SELN==0, then no link will be used; if SELN==1, then OUTA will be used, and so on.

<TABLE BORDER="1"> <TD>ASLO<TD>Adjustment Slope<TD>DOUBLE<TD>Yes<TD>1<TD>Yes<TD>Yes<TD>No<TD>Yes<TR>

...ach representing a bit of the word. These fields (B0-B9, BA-BF) are set to 1 if a bit is set, and 0 if not. <TABLE BORDER="1">

<TABLE BORDER="1"> <TD>NELM<TD>Number of elements in array<TD>USHORT<TD>Yes<TD>1<TD>Yes<TD>No<TD>No<TD>No<TR>

<TABLE BORDER="1"> <TABLE BORDER="1">

...s when reading the hardware register. It is initialized to ((1 << NOBT) - 1) by record initialization. The user can configure the NOBT field, but the <TABLE BORDER="1">

<TABLE BORDER="1"> ...eveloper's Guide''', chapter libCom / calc / Infix Expression Syntax (19.2.1 for EPICS 3.14.11).

...s ready to accept a request. The client monitors WFLG and when WFLG equals 1, the client-server action is performed (a private matter between server and <TABLE BORDER="1">

...out to hardware. If a bit field is non-zero, it is interpreted as a binary 1. On the other hand, if it is zero, it is interpreted as a binary 0. <TABLE BORDER="1">

<TABLE BORDER="1"> ...T alarm with a severity of INVALID is raised, and return status is set to -1.

<TABLE BORDER="1"> <TABLE BORDER="1">

<TABLE BORDER="1"> <TABLE BORDER="1">

<TABLE BORDER="1"> ...from 0-11 which corresponds to the value field to be used (0 means use A; 1 means use B, etc.). How the NVL field is configured determines, in turn, SE

...will be processed. There are three scanning methods for database records: (1) periodic, (2) event, and (3) passive. ...s. If the 1 second scan records take 100 milliseconds to process, then the 1 second scan period will start again 900 milliseconds after completion. The

<TABLE BORDER="1"> <TABLE BORDER="1">

<TABLE BORDER="1"> <TABLE BORDER="1">

<TABLE BORDER="1"> <TABLE BORDER="1">

<TABLE BORDER="1"> <TABLE BORDER="1">

<TABLE BORDER="1"> <TABLE BORDER="1">

...red mainline" workflow given in the [http://doc.bazaar.canonical.com/bzr.2.1/en/user-guide/distributed_intro.html Bazaar User Guide]. bzr merge -c -1 ../fix-123

...curity level in the record description, and limits us to only levels 0 and 1. Some sites may want finer control over accesses: being able to put indivi