> but my 58503B still reports no leap second pending as of > this morning, 15 hours after the event. Maybe they added a "fool-me-once, shame-on-you: fool-me-twice, shame-on-me!" algorithm to the Smartclock code w.r.t. leap seconds! Tim.