Macros
#define	MBG_OWN_EVENT_CHASSIS 0xFF
	See MBG_EVENT_INFO::chassis_idx. More...

#define	MBG_OWN_EVENT_SLOT_TYPE 0xFF
	See MBG_EVENT_INFO::slot_type. More...

#define	MBG_OWN_EVENT_SLOT_TYPE_ID 0xFF
	See MBG_EVENT_INFO::slot_type_id. More...

#define	MBG_INV_EVENT_PORT 0xFF
	See MBG_EVENT_INFO::port_idx. More...

Detailed Description

It's very important to understand how to use event indexes properly. In general, think of a management master system (MMS) like a LANTIME that is able to send its own events like "NTP not sync" and that is even able to send/forward events from other IMS modules like "CLK1 Antenna Disconnected". In case it is an event of the MMS itself, indexes in MBG_EVENT_INFO should be set to its "own" values below. But in case it is an event of an "IMS slave card" like a GPS180 at least MBG_EVENT_INFO::slot_type and MBG_EVENT_INFO::slot_type_id should be set. Most events will likely not support a port or a foreign chassis, so set MBG_EVENT_INFO::port_idx to MBG_INV_EVENT_PORT and/or MBG_EVENT_INFO::chassis_idx to MBG_OWN_EVENT_CHASSIS. Please be aware that there are IMS modules like SSP100 that tend to be "IMS slave cards", but they are, in fact, MMS because most of the time they are not connected to the main CPU via USB and therefore they send their "own" events.