Echelon ISI - Manual (Page 57)

55 ISI Programmer’s Guide
case isiNormal:
if (longPress) {
IsiDeleteEnrollment(assembly);
} else {
IsiOpenEnrollment(assembly);
}
break;
}
}
}
With the refinements to the quick start example introduced above the resulting
device will do the following:
• Participate in and honor all ISI messages relating to the device’s subnet/node
address.
• Use timing guidance received from a domain address server, if available, and
the application is linked with the IsiCompactS, IsiCompactSHb,
IsiCompactDa, IsiCompactDaHb, or IsiFull library; see Optimizing the
Footprint of ISI Applications for more details about the different ISI libraries.
• Open enrollment for connections with a width of 1, offering a connection with
a SNVT_switch network variable.
• Provisionally approve open enrollment messages for manual connections that
relate to a single standard network variable with a matching SNVT_switch
type.
A typical ISI application will proceed and provide further customization. Such
customization serves two purposes:
• A customized application can support more complex connection types, such as
complex compound assemblies or manufacturer-specific connections.
• Customized applications can be tailored to specific application needs.
Customizing ISI can lead to smaller memory footprint, compared to the
generic default implementations.
Further customization is discussed in Self-Installation Advanced Procedures .