HMS FlexRay CCM, Руководство по программированию

Страница: 26 / 71

Copyright IXXAT Automation GmbH
UCI Programming Manual FlexRay, V1.13
External interfaces
26
5.1.4.5 GetTxEventHandle
Via the method GetTxEventHandle() the event handle for the TX FIFO can be
obtained. This event tells that at least one FlexRay Message was transmitted suc-
cessfully.
Prototype:
virtual HRESULT __stdcall GetTxEventHandle ( PHANDLE phTxEvent );
Parameters:
phTxEvent OUT Pointer to store the handle for event notification.
Return value: UCI error codes
5.1.4.6 Start
The FlexRay controller previously configured via
Init()
is set to Running mode via
this function and thus participates in the communication.
Start
can only be called after the FlexRay controller has been initialized via
Init()
and is in init/stopped mode. See Fig. 4-1
Prototype:
virtual HRESULT __stdcall Start( void );
Parameters: none
Return value:
UCI error codes
5.1.4.7 GetMsg
With this method FlexRay messages can be read out of the RX FIFO. Therefore a
valid destination pointer to
UCI_FLXMSG structure has to be handed over. If a
message is available it is copied to the memory provided by the structure.
The
GetMsg()
method returns different types of messages:
•
Data messages
•
Status messages (for each FlexRay cycle)
The different messages can be identified by wMessageType in the UCI_FLXMSG
union structure. According to this value the correct internal union structure has
to be used.
GetMsg()
can only be called after initialization of the FlexRay controller via
Init()
(init/stopped or running mode). See Fig. 4-1
Prototype:
virtual HRESULT __stdcall GetMsg( PUCI_FLXMSG pMsg );