DG GRYPHON S3, User Manual, Page: 28 / 38

GRYPHON
®
- S3
MANUAL
© 2006
28
SD_CARD a device, or channel , for physically accessing an automotive / industrial
automation network. These devices are resident on the Gryphon.
SD_CLIENT a user application, e.g., a network monitor program. Client processes can be
running either on the Gryphon, or more typically, on a PC connected to the
Gryphon over TCP/IP.
SD_SCHED a message scheduler process, running on the Gryphon.
SD_RESP a message responder process, running on the Gryphon.
Here are some scenarios for routing of GC frames in a Gryphon Network:
• CAN frames detected on a CAN bus, sent from an SD_CARD (CAN channel) to an
SD_CLIENT (user program)
• CAN frames to be transmitted over a CAN bus, sent from an SD_CLIENT to an
SD_CARD
• A channel speed change request sent from an SD_CLIENT to an SD_CARD
• A request for scheduler services, sent from an SD_CLIENT to an SD_SCHED
5.2 GC frames
As stated previously, each GC frame is assigned a unique source and destination address before it is
sent over the Gryphon Network; with some exception, such as broadcast.
Some of the most commonly used types of GC Frame are:
FT_DATA these frames encapsulate the frames of the in-vehicle network protocols. Typically,
they are routed by the Gryphon server between processes of type SD_CARD and
SD_CLIENT.
FT_EVENT these frames are used to notify clients of the occurrence of various events and error
conditions detected by the Gryphon, e.g., when a service requested by the client has
been completed, or when an error condition has been detected on one of the
channels.
5.3 Gryphon time and timestamps
The Gryphon time is a 64-bit unsigned integer. The user can set and retrieve this value via the GC
Protocol. The user can also change this value when setting the Linux system time via the Gryphon