Installing Code for PiFace Real Time Clock

Are those all of the comments that are returned? Having a glance at the install script it seems there should be a piece saying to reboot and another demonstrating how to set the clock etc... If these are missing it would indicate that the install script has not completed correctly.

Has the install script created the /etc/init.d/pifacertc file? check by typing cat /etc/init.d/pifacertc into a terminal window, there should be around 37 lines of text print out into the terminal as a result.

If the installer hasnt completed succesfully it should be easy enough to replicate the procedure manually, everything is provided in that script to do that.

p.s.the comments 1,2 and 3 that appear ate just the install script telling you where it is up to. Comment 4 is an instruction to you to run raspi-config, as I said above, there should also be more text below this

Thanks for the response of the many users over the last 48 hrs. 
Dear lucie tozer:

Let me respond directly to your suggestion:

I opened the /etc/init.d/pifacertc file in from the File Manager
and typed cat /etc/init.d/pifacertc at the terminal.
Both ways yielded:

# !/bin/sh
### BEGIN INIT INFO
# Provides:   pifacertc
# Required-Start:    udev mountkernfs $remote_fs raspi-config
# Required-Stop:  
# Required-Start:    S
# Default-Stop:
# Short Description: Add the PiFace RTC
# Description:          Add the PiFace RTC
### END INIT INFO

. /lib/lsb/init-functions

case "$1" in
   start)
       log_success_msg "Probe the i2c-dev"
       modprobe i2c-dev
       # Calibrate the clock ( default: 0x47).  See datasheet or MCP7940N
       log_success_msg "Calibrate the clock"
       i2cset -y 0x6f 0x08 0x47
       log_success_msg "Probe the mcp7941x driver
       modprobe i2c :mcp7941x
       log-success-msg "Add the mcp7941x device in the sys filesystem"
       #https://www.kernel.org/doc/Documentation/i2c/instantiating-devices
       echo mcp7941x 0x6f > /sys/class/i2c-dev/i2c-0/device/new_device
       log-success-msg "Synchronise the system clock and hardware RTC"
       hwclock --hctosys
       ;;
   stop)
       ;;
   restart)
       ;;
   force-reload)
       ;;
   #)
      echo "Usage: $0 start" >&2
      exit 3
      ;;
esac

I opened the /etc/init.d/rc.local file in from the File Manager
and typed cat /etc/init.d/rc.local at the terminal.
Both ways yielded:

# !/bin/sh
### BEGIN INIT INFO
# Provides:     rc.local
# Required-Start:      $ all
# Required-Stop:  
# Required-Start:      2 3 4 5
# Required-Stop:
# Short Description:  Run /etc/rc.local if it exist 
### END INIT INFO

PATH=/sbin:/usr/sbin:/bin:/usr/bin

./lib/init/vars.sh
./lib/lsb/init-functions

do_start () {
      if [ -x /etc/rc.local ]; then
                [ "$VERBOSE" !=no ] && log_begin_msg "Running local boot scripts (/etc/rc.local)"
                /etc/rc.local
                ES=$?
                [ "$VERBOSE" !=no ] && log_end_msg $ES
                return $ES
      fi
}
case "$1" in
      start )
         do_start
         ;;
      restart | reload | force-reload)
            echo "Error: argument "$1" not supported" >&2
            exit 3
            ;;
      stop | status )
            # No-op
            exit 0
            ;;
      *)
            echo "Usage: 0 start|stop" >&2
            exit 3
            ;;
esac

I appreciate you speedy response to continue with my problem. To re-summarize my total experience with Installing the PiFace Real Time Clock here's additional, more-specific information.

I had successully installed previous RPi 2's and one of my RPi 0's all running the current Rasbian Jessie software following these websites:

Starting Website to Add PiFace Real Time Clock
http://www.piface.org.uk/products/piface_clock/

Two Links (located towards bottom of site) were followed:

1. Documentation (downloaded pdf File)

2. PiFace Real Time Clock on GitHub
https://github.com/piface/PiFace-Real-Time-Clock

The previous installation on a RPi Zero (which was successfull) did not generate a /etc/init.d/pifacertc  file
and during the boot phase, I did see a line:
[Failed (in red): Failed to start /etc/rc.local compatibility.
but evidently the clock installed correctly.
The text for the rc.local files on this device and the RPi Zero device that failed are identical.

My PATH to install on the failed device is briefly described next:

pi@raspberrypi ~$ ls
Downloads  (among other files)
pi@raspberrypi ~$ cd Downloads
install-piface-real-time-clock.sh  (in bold yellow/green color)
chmod +/ install-piface-real-time-clock.sh  (returns prompt)
sudo ./install-piface-real-time-clock.sh (problems occur)
returns:
Create a new pifacertc init script to load time from PiFace RTC
Adding /etc/init.d/pifacertc .
Install the pifacertc init script
Enable I2C by adding:

raspi-config

then navigate to "Advanced Options" > I2C
and select 'yes' to enable the ARM I2C interface. Then *reboot* ans set the clock with:

sudo date -s "10 JAN 2014 10:10:30"
sudo hwclock --systohc
Downloads $

(end of PATH return)

I type the command:
sudo reboot.
During the boot phase, I noted the following 2 lines:
 
[FAILED] Failed to start LSB: Add the PiFace Device
See "systemct1 status pifacertc service" for details

In fact, I have configured another RPi Zero device in a separate electrical system and tried the install and the same failure occurs.

This begs two questions:
1. How to Run command to "See systemct1 status pifacertc service for details" and
2. Relative to the long-winded response from the terminal after the sudo ./install ... command (PATH above), what should the new pifacertc script contain, why add another /etc/init.d/pifacertc . , and how to install it. It does not detail any of these returns. Finally, you have indicated that the install script may not have completed correctly. Based on all of the above, did the script complete successully or do I need to create another script of which Iis unknown to me.

Dear lucie tozer:

If you've arrived here without abandoning me I appeciate it. I just don't understand why an installation can proceed in entirely two different paths on identical systems but yielding different file structures. I'm sure its my mistake and I am confident I'll find the solution through your and many others help. Thanks again. Frank

Swap SD cards and if the problem moves, then the problem is on that card and is not identical!

Clem

Swap SD cards and if the problem moves, then the problem is on that card and is not identical!

Clem