The PixelPlant hardware is an add-on board family for microEnable IV. At the moment, two boards are available: PixelPlant100 and PixelPlant200 which differ in FPGA and RAM size.
To develop an applet for using the PixelPlant Px100 / Px200 hardware, two separate design parts have to be created:
-
A base design for the microEnable IV board
-
A design for PixelPlant
Both parts need to be handled in two separate VisualApplets design files. Both designs, PixelPlant and microEnable IV, have to be build, so that two HAP files are generated. Finally, both parts (HAP files) have to be merged into one hardware applet (HAP file).
For data transfer between the microEnable IV applet and the PixelPlant applet, operators TxLink and RxLink have to be used. TxLink operators transmit the data to a PixelPlant board, RxLink operators receive data from the PixelPlant. The PixelPlant part has to contain the corresponding RxLink and TxLink operators to pick the data from the microEnable IV and transmit it back. Each RxLink / TxLink operator has a channel ID parameter which selects the corresponding RxLink / TxLink operator on microEnable IV. Theses channel ID parameters as well as the link formats have to match on both, PixelPlant and microEnable IV.
The merging of two applets is explained in the next section.
Merging PixelPlant and microEnable IV designs can be done by using the HAP Merger utility. Access it by → . The utility dialog asks for the microEnable IV HAP file and its corresponding PixelPlant HAP file. Pressing the "Merge" button generates a HAP file containing both design parts. This merged HAP file is used to be loaded on the frame grabber.
Please note: The channel ID of corresponding RxLink / TxLink pairs have to match on both applets as well as the link formats. The hardware applet merger will not merge the HAPs if a mismatch is detected.
Prev
