Issue link: https://iconnect007.uberflip.com/i/1502623
48 SMT007 MAGAZINE I JULY 2023 group developing the AOI for board assem- blies' group, email answers@ipc.org. Heartbeat Getting Worked Up? Since its introduction, the Heartbeat mes- sage has enabled devices to send periodic heartbeat messages at a configurable inter- val, typically every few minutes, and for pas- sive connectivity verification. For version 1.7, additional fields have been added to this mes- sage to provide repeated active fault and recipe information in every heartbeat message. With this upgrade, system will now be able to col- lect this important information without need- ing to wait for the values to change so that a new GetActiveFaultsResponse or RecipeActivated me s sage would b e s ent . The s e addit ional optional fields in the Heartbeat message are: • ActiveFaults, which is a list of any active faults on the endpoint with information like the FaultOccurred message • ActiveRecipes, which is a list of the identifiers of any active recipes on the endpoint with information like the RecipeActivated message. e IPC-CFX message CFX.Production.Recipe Activated as originally written reports only ExpectedCycleTime, but not the Expected- WorkTime. e newly added ExpectedWork- Time property enables the collection and reporting of the total amount of productive time (milliseconds) that is expected to pro- cess one unit or a group of units (e.g., carrier, panel PCB), assuming no blocked or starved conditions at the station. Together with existing messages such as WorkStarted/Work Completed, this data can be used for real-time performance tracking and analysis. Making the Leap into Sustainability As sustainability in electronics manufacture becomes more prevalent, EMS companies will need to identify ways to control energy usage in their facilities. Although SMT equipment may inherently include energy savings capa- bilities and state-specific wake-up times for resuming its activities, those pieces of equip- ment can't activate an energy-saving state on their own. Conversely, supervisory systems know production plans, scheduled downtime, etc., but they will not know a piece of equip- ment's energy savings capabilities. e standard now closes this communica- tion gap with a series of new messages: • Using CFX.GetEndpointInformation Request/Response, supervisory systems can Request equipment capabilities concern- ing energy management, with an equip- ment Response message providing a list of sleep states with three parameters: Name of the sleep state › Percentage of saved energy › Wake-up time to get back to productive state • Using CFX.ResourcePerformance.Change SleepStateRequest, supervisory systems can control energy management state of equip- ment by requesting the device to change to a sleep state or back to productive • Using CFX.ResourcePerformance.Energy Consumed, equipment will regularly report detailed information about its energy usage and power consumption • Alternatively, the supervisory system can query equipment's energy usage and power consumption using CFX.Resource Performance.EnergyConsumptionRequest/ Response, with the equipment Response message providing detailed information about its energy usage and power con- sumption e inclusion of these messages is essential for the accurate measurement, control, and management of energy-related sustainability issues, now recognized by industry as a key requirement going forward.