<reponame>clockspot/master-clock
# Running mode. If true, it outputs to GPIO
piMode = False

# Paths for log and persistent storage for slave-displayed time. Make sure the files (if present, otherwise the containing directory) are writable by the user that will be running the daemon.
logPath = '/var/log/master-clock/master-clock.log'
logDebug = False
# Note, you can monitor the log in real time with tail -f [logPath]
slavePath = '/var/log/master-clock/master-clock-slavetime.txt'
slaveWriteRealTime = True
# True writes after every impulse (except during fast forward), but this may affect the life of storage media; False writes only when the app closes, but this means it'll need calibration after any power loss

# Slave clock control
slavePin = 23 #Broadcom pin ID
slaveInterval = 30 #seconds between impulses (normal operation, includes impulse duration)
slaveImpulse = 0.3 #seconds impulse duration
slaveRecover = 0.4 #seconds between impulses (fast forwarding, excludes impulse duration)
slaveHrs = 12 #Is it a 12-hour or 24-hour display?
#slaveIsBipolar = False #TODO support this with two GPIO pins
slaveHold = 2 #If the slave is no more than X hours ahead (disregarding date), wait for real time to catch up, instead of advancing all the way around. If your slave displays the day/date (e.g. Solari Emera/Dator), you may prefer to set this to 0, as the slave is unlikely to get ahead of real time (without being set forward manually).

# Seconds/status meter control
meterPin = 18 #Broadcom pin ID that supports PWM - set to False if you have no meter
# Meter calibration points, display value vs PWM duty cycle value. Use calibrate-meter.py to find points for your meter. This also defines the range of your meter scale. (If it starts at zero, you can omit (0,0); it will be assumed.)
meterCal = [(59,94)] #This default defines a 60-second scale, more or less, on a 3VDC meter (since Pi GPIO is 3.3V).
# Meter ballistics: when making a relatively large change to the meter display, quadratic easing is applied to prevent the needle from moving too violently (pegging, wobbling)
meterChg = 10 #min change in pwm duty cycle that will trigger ballistics
meterStp = 4 #apply ballistics in this many steps
meterLag = 0.18 #seconds between ballistics steps
# Running mode. If true, it outputs to GPIO
piMode = False

# Paths for log and persistent storage for slave-displayed time. Make sure the files (if present, otherwise the containing directory) are writable by the user that will be running the daemon.
logPath = '/var/log/master-clock/master-clock.log'
logDebug = False
# Note, you can monitor the log in real time with tail -f [logPath]
slavePath = '/var/log/master-clock/master-clock-slavetime.txt'
slaveWriteRealTime = True
# True writes after every impulse (except during fast forward), but this may affect the life of storage media; False writes only when the app closes, but this means it'll need calibration after any power loss

# Slave clock control
slavePin = 23 #Broadcom pin ID
slaveInterval = 30 #seconds between impulses (normal operation, includes impulse duration)
slaveImpulse = 0.3 #seconds impulse duration
slaveRecover = 0.4 #seconds between impulses (fast forwarding, excludes impulse duration)
slaveHrs = 12 #Is it a 12-hour or 24-hour display?
#slaveIsBipolar = False #TODO support this with two GPIO pins
slaveHold = 2 #If the slave is no more than X hours ahead (disregarding date), wait for real time to catch up, instead of advancing all the way around. If your slave displays the day/date (e.g. Solari Emera/Dator), you may prefer to set this to 0, as the slave is unlikely to get ahead of real time (without being set forward manually).

# Seconds/status meter control
meterPin = 18 #Broadcom pin ID that supports PWM - set to False if you have no meter
# Meter calibration points, display value vs PWM duty cycle value. Use calibrate-meter.py to find points for your meter. This also defines the range of your meter scale. (If it starts at zero, you can omit (0,0); it will be assumed.)
meterCal = [(59,94)] #This default defines a 60-second scale, more or less, on a 3VDC meter (since Pi GPIO is 3.3V).
# Meter ballistics: when making a relatively large change to the meter display, quadratic easing is applied to prevent the needle from moving too violently (pegging, wobbling)
meterChg = 10 #min change in pwm duty cycle that will trigger ballistics
meterStp = 4 #apply ballistics in this many steps
meterLag = 0.18 #seconds between ballistics steps
# Running mode. If true, it outputs to GPIO # Paths for log and persistent storage for slave-displayed time. Make sure the files (if present, otherwise the containing directory) are writable by the user that will be running the daemon. # Note, you can monitor the log in real time with tail -f [logPath] # True writes after every impulse (except during fast forward), but this may affect the life of storage media; False writes only when the app closes, but this means it'll need calibration after any power loss # Slave clock control #Broadcom pin ID #seconds between impulses (normal operation, includes impulse duration) #seconds impulse duration #seconds between impulses (fast forwarding, excludes impulse duration) #Is it a 12-hour or 24-hour display? #slaveIsBipolar = False #TODO support this with two GPIO pins #If the slave is no more than X hours ahead (disregarding date), wait for real time to catch up, instead of advancing all the way around. If your slave displays the day/date (e.g. Solari Emera/Dator), you may prefer to set this to 0, as the slave is unlikely to get ahead of real time (without being set forward manually). # Seconds/status meter control #Broadcom pin ID that supports PWM - set to False if you have no meter # Meter calibration points, display value vs PWM duty cycle value. Use calibrate-meter.py to find points for your meter. This also defines the range of your meter scale. (If it starts at zero, you can omit (0,0); it will be assumed.) #This default defines a 60-second scale, more or less, on a 3VDC meter (since Pi GPIO is 3.3V). # Meter ballistics: when making a relatively large change to the meter display, quadratic easing is applied to prevent the needle from moving too violently (pegging, wobbling) #min change in pwm duty cycle that will trigger ballistics #apply ballistics in this many steps #seconds between ballistics steps