Xtium-CLHS PX8 User's Manual Xtium-CLHS PX8 Reference • 47Transfer EventsTransfer events are the ones related to the transfer module. Transfer events provide feedback onimage transfer from onboard memory frame buffers to PC memory frame buffers.• Start of FrameStart of Frame event generated when the first image pixel is transferred from on-boardmemory into PC memory.The Sapera event value is CORXFER_VAL_EVENT_TYPE_START_OF_FRAME.• End of FrameEnd of Frame event generated when the last image pixel is transferred from on-boardmemory into PC memory.The Sapera event value is CORXFER_VAL_EVENT_TYPE_END_OF_FRAME.• End of TransferEnd of Transfer event generated at the completion of the last image transfer from on-boardmemory into PC memory. Issue a stop command to the transfer module to complete atransfer (if transfers are already in progress). If a frame transfer of a fixed number ofimages is requested, the transfer module will stop transfer automatically. The Sapera eventvalue is CORXFER_VAL_EVENT_TYPE_END_OF_TRANSFER.Trigger Signal ValidityThe ACU ignores external trigger signal noise with its programmable debounce control. Programthe debounce parameter for the minimum pulse duration considered as a valid external triggerpulse. For more information see Note 1: General Inputs / External Trigger Inputs Specifications.Supported Transfer Cycling MethodsThe Xtium-CLHS PX8 supports the following transfer modes, which are either synchronous orasynchronous. Note that the Xtium does not make any use of the trash buffer. Images areaccumulated in on-board memory in a FIFO type manner. When no memory is available for a newimage to be stored, the image is discarded and the CORACQ_VAL_EVENT_TYPE_FRAME_LOST isgenerated. On-board memory can get filled up if the rate at which the images are acquired isgreater than the rate at which the DMA engine can write them to host buffer memory. On-boardmemory can also get filled-up if there are no more empty buffers available to transfer the on-boardimages.When stopping the image acquisition, the event CORXFER_VAL_EVENT_TYPE_END_OF_TRANSFERwill occur once all images currently in the on-board memory are transferred to host buffer memory.Note that if the application does not provide enough empty buffers, the Xtium event will not occurand an acquisition abort will be required.• CORXFER_VAL_CYCLE_MODE_SYNCHRONOUS_WITH_TRASHBefore cycling to the next buffer in the list, the transfer device will check the next buffer'sstate. If its state is full, the transfer will keep the image in on-board memory until the nextbuffer’s state changes to empty. If the on-board memory gets filled, frame lost events willbe generated.• CORXFER_VAL_CYCLE_MODE_SYNCHRONOUS_NEXT_EMPTY_WITH_TRASHWhen starting an acquisition, the buffer list is put in an empty buffer queue list in the exactorder they were added to the transfer. Whenever a user sets a buffer to empty, it is addedto the empty buffer queue list, so that after cycling once through the original buffer list, thebuffers acquired into will follow the order in which they are put empty by the user. So in thismode, the on-board images will be transferred to host buffer memory as long as there arebuffers in the empty buffer queue list. If the on-board memory gets filled, the frame lostevent will start occurring.• CORXFER_VAL_CYCLE_MODE_ASYNCHRONOUSThe transfer device cycles through all buffers in the list without concern about the bufferstate.