Time-of-Day Event Not Activating

Compare the time shown on the controller display to a known accurate time source. If the clock is incorrect, access the clock-setting menu and adjust. Observe whether the time holds after a power cycle.

Expected: Controller clock matches real time and retains setting after power cycle.

Evidence to note: meter-reading

A clock that resets or drifts significantly suggests a depleted backup battery or failing memory on the controller. Inspect the board for a coin-cell or soldered battery. If the battery is user-replaceable, replace it and retest. If soldered or absent, note the condition for technician review.

Expected: Clock retains time across power cycles after battery service.

Evidence to note: meter-reading

Navigate to the controller status or information screen. Record the displayed firmware version. If the version is 432.08 or later, the combined six-event programming structure should be available. If earlier, the legacy four-event-per-type structure applies and the COMBO option will not appear.

Expected: Firmware version identified and recorded.

Evidence to note: note

If the firmware is earlier than 432.08, determine whether a firmware update is available from the manufacturer. Firmware updates should only be applied using manufacturer-approved tools and procedures. Do not attempt firmware flashing without manufacturer-approved update package and stable power.

Expected: Decision made on whether to proceed with firmware update or work within legacy feature set.

Evidence to note: note

Enter the time-of-day event programming menu. For each programmed event, confirm the event type is set to the intended mode (OFF, INHIBIT, FREEVEND, DISCOUNT, or COMBO). Confirm start and end times are correct. Confirm the event number being checked matches the intended slot.

Expected: Event type, start time, and end time are confirmed correct.

Evidence to note: note

Correct the event type, start time, or end time as needed. After programming, exit the menu fully and re-enter to verify the settings were saved.

Expected: Corrected settings are retained after exiting and re-entering the menu.

Evidence to note: note

Set a test event to activate two minutes in the future with a short duration. Observe whether the machine behavior changes at the designated time (for example, price changes for discount, or product becomes unavailable for inhibit). Confirm the behavior reverts when the event window ends.

Expected: Machine behavior changes at the scheduled start time and reverts at the scheduled end time.

Evidence to note: note

Repeat the test with a longer window and verify clock accuracy throughout. If the event still does not activate, the controller may not be processing the schedule correctly.

Expected: Determines whether the issue is timing-related or a processing failure.

Evidence to note: note

If firmware cannot be updated, use the available legacy event slots. Document the limitation and plan schedules around the four-event-per-type structure.

Expected: Functional scheduling using available legacy features.

Evidence to note: note

The time-of-day event is activating correctly. Document the final configuration and firmware version for future reference.

Expected: Scheduled events operate as intended.

Evidence to note: note

The controller is not retaining settings, not activating events, or otherwise behaving inconsistently with expected firmware capabilities. Stop and hand off to a qualified technician or the manufacturer for controller-level diagnosis.

Expected: Technician receives documented history of observations and test results.

Evidence to note: note