Echelon ISI - Manual (Page 26)

ISI Programmer’s Guide 24
Device DAS
IsiStartDeviceAcquisition()
enters device acquisition mode
IsiAcquireDomain()
starts domain acquisition
and sends the DIDRQ
domain request message
Respond to the DIDRQ
domain request message
with a DIDRM domain
response message
Collect all domain response
messages for 1.5s
Application receives isiWink
event and provides visual or
audible feedback to the user
IsiStartDeviceAcquisition() signals that
the user confirmed acquisition of the
correct device via a Connect button or
other user interface
Respond to user confirmation by
sending a DIDCF domain
confirmation message to device
Device joins
domain as
advised by DAS
The device automatically cancels domain acquisition if it receives multiple, but
mismatching, domain response messages in step 4. This may happen if multiple
domain address servers with different domain addresses are in device acquisition
mode, and all respond to the device’s query.
Devices should support the domain acquisition process whenever possible (device
resources permitting) over the Fetch Device process described below—the domain
acquisition process provides a more robust process with features such as
automatic retries and other desirable side effects, like automatic connection
reminders.
The IsiCancelAcquisition() function causes a device to leave domain acquisition
mode. The cancellation applies to both device and domain acquisition. After this
function call is completed, the ISI engine calls IsiUpdateUserInterface()with the
IsiNormal event. On a domain address server, use the IsiCancelAcquisitionDas()
function instead.