As you learned in yesterday's lesson, discovery is a special procedure that a Niagara AX installation technician follows to easily add driver device components and control point components to his or her Niagara AX station. Yesterday's lesson instructed you on how to design your driver to automatically add device components to your driver's network. You did this by defining four Niagara AX components in Java and making associations amongst them and your driver's network:
If you are creating a driver that follows a serial, master-slave protocol then you likely modified the device id that you previously created and made it serve also as the device discover parameters. You likewise modified the ping request and ping response that you previously created and made them serve also as the device discover request and device discover response.
Alternatively, you may have decided to create a separate device discovery parameters, device discovery request, and device discovery response classes.
In both cases, you created a new class for the device discovery preferences structure.
By doing this, the developer driver framework uses these classes and associations in your driver to perform the discovery feature on your network's Ddf Device Manager.
If you follow the steps in today's lesson and update your driver accordingly, then the developer driver framework on which your driver is built, will automatically perform all details for the point discovery process. After following today's procedure, your driver will support discovery of data points within your device. Today's procedure is very similar to yesterday's procedure, although slightly more complicated.
Copyright © 2000-2016 Tridium Inc. All rights reserved.