This is the description of the Shell API bindings for the Real-Time Clock Bricklet. General information and technical specifications for the Real-Time Clock Bricklet are summarized in its hardware description.
An installation guide for the Shell API bindings is part of their general description.
The example code below is Public Domain (CC0 1.0).
1 2 3 4 5 6 7 8 9 10 | #!/bin/sh
# Connects to localhost:4223 by default, use --host and --port to change this
uid=XYZ # Change XYZ to the UID of your Real-Time Clock Bricklet
# Get current date and time
tinkerforge call real-time-clock-bricklet $uid get-date-time
# Get current timestamp
tinkerforge call real-time-clock-bricklet $uid get-timestamp
|
Download (example-callback.sh)
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 | #!/bin/sh
# Connects to localhost:4223 by default, use --host and --port to change this
uid=XYZ # Change XYZ to the UID of your Real-Time Clock Bricklet
# Handle incoming date and time callbacks
tinkerforge dispatch real-time-clock-bricklet $uid date-time &
# Set period for date and time callback to 5s (5000ms)
# Note: The date and time callback is only called every 5 seconds
# if the date and time has changed since the last call!
tinkerforge call real-time-clock-bricklet $uid set-date-time-callback-period 5000
echo "Press key to exit"; read dummy
kill -- -$$ # Stop callback dispatch in background
|
Possible exit codes for all tinkerforge
commands are:
argparse
module is missingThe common options of the call
and dispatch
commands are documented
here. The specific command structure is shown below.
call
real-time-clock-bricklet
[<option>..] <uid> <function> [<argument>..]¶Parameters: |
|
---|
The call
command is used to call a function of the Real-Time Clock Bricklet. It can take several
options:
--help
shows help for the specific call
command and exits--list-functions
shows a list of known functions of the Real-Time Clock Bricklet and exitsdispatch
real-time-clock-bricklet
[<option>..] <uid> <callback>¶Parameters: |
|
---|
The dispatch
command is used to dispatch a callback of the Real-Time Clock Bricklet. It can
take several options:
--help
shows help for the specific dispatch
command and exits--list-callbacks
shows a list of known callbacks of the Real-Time Clock Bricklet and exitsreal-time-clock-bricklet
<uid> <function>
[<option>..] [<argument>..]¶Parameters: |
|
---|
The <function>
to be called can take different options depending of its
kind. All functions can take the following options:
--help
shows help for the specific function and exitsGetter functions can take the following options:
--execute <command>
shell command line to execute for each incoming
response (see section about output formatting
for details)Setter functions can take the following options:
--expect-response
requests response and waits for itThe --expect-response
option for setter functions allows to detect
timeouts and other error conditions calls of setters as well. The device will
then send a response for this purpose. If this option is not given for a
setter function then no response is sent and errors are silently ignored,
because they cannot be detected.
real-time-clock-bricklet
<uid> <callback>
[<option>..]¶Parameters: |
|
---|
The <callback>
to be dispatched can take several options:
--help
shows help for the specific callback and exits--execute <command>
shell command line to execute for each incoming
response (see section about output formatting
for details)real-time-clock-bricklet
<uid> set-date-time
<year> <month> <day> <hour> <minute> <second> <centisecond> <weekday>¶Parameters: |
|
---|---|
Output: |
|
Sets the current date (including weekday) and the current time.
If the backup battery is installed then the real-time clock keeps date and time even if the Bricklet is not powered by a Brick.
The real-time clock handles leap year and inserts the 29th of February accordingly. But leap seconds, time zones and daylight saving time are not handled.
The following symbols are available for this function:
For <weekday>:
real-time-clock-bricklet
<uid> get-date-time
¶Output: |
|
---|
Returns the current date (including weekday) and the current time of the real-time clock.
The following symbols are available for this function:
For weekday:
real-time-clock-bricklet
<uid> get-timestamp
¶Output: |
|
---|
Returns the current date and the time of the real-time clock. The timestamp has an effective resolution of hundredths of a second and is an offset to 2000-01-01 00:00:00.000.
real-time-clock-bricklet
<uid> set-offset
<offset>¶Parameters: |
|
---|---|
Output: |
|
Sets the offset the real-time clock should compensate for in 2.17 ppm steps between -277.76 ppm (-128) and +275.59 ppm (127).
The real-time clock time can deviate from the actual time due to the frequency deviation of its 32.768 kHz crystal. Even without compensation (factory default) the resulting time deviation should be at most ±20 ppm (±52.6 seconds per month).
This deviation can be calculated by comparing the same duration measured by the
real-time clock (rtc_duration
) an accurate reference clock
(ref_duration
).
For best results the configured offset should be set to 0 ppm first and then a duration of at least 6 hours should be measured.
The new offset (new_offset
) can be calculated from the currently configured
offset (current_offset
) and the measured durations as follow:
new_offset = current_offset - round(1000000 * (rtc_duration - ref_duration) / rtc_duration / 2.17)
If you want to calculate the offset, then we recommend using the calibration dialog in Brick Viewer, instead of doing it manually.
The offset is saved in the EEPROM of the Bricklet and only needs to be configured once.
real-time-clock-bricklet
<uid> get-offset
¶Output: |
|
---|
Returns the offset as set by set-offset
.
real-time-clock-bricklet
<uid> get-identity
¶Output: |
|
---|
Returns the UID, the UID where the Bricklet is connected to, the position, the hardware and firmware version as well as the device identifier.
The position can be 'a', 'b', 'c', 'd', 'e', 'f', 'g' or 'h' (Bricklet Port). A Bricklet connected to an Isolator Bricklet is always at position 'z'.
The device identifier numbers can be found here.
real-time-clock-bricklet
<uid> set-date-time-callback-period
<period>¶Parameters: |
|
---|---|
Output: |
|
Sets the period with which the date-time
callback is triggered
periodically. A value of 0 turns the callback off.
The date-time
Callback is only triggered if the date or time changed
since the last triggering.
New in version 2.0.1 (Plugin).
real-time-clock-bricklet
<uid> get-date-time-callback-period
¶Output: |
|
---|
Returns the period as set by set-date-time-callback-period
.
New in version 2.0.1 (Plugin).
real-time-clock-bricklet
<uid> set-alarm
<month> <day> <hour> <minute> <second> <weekday> <interval>¶Parameters: |
|
---|---|
Output: |
|
Configures a repeatable alarm. The alarm
callback is triggered if the
current date and time matches the configured alarm.
Setting a parameter to -1 means that it should be disabled and doesn't take part in the match. Setting all parameters to -1 disables the alarm completely.
For example, to make the alarm trigger every day at 7:30 AM it can be configured as (-1, -1, 7, 30, -1, -1, -1). The hour is set to match 7 and the minute is set to match 30. The alarm is triggered if all enabled parameters match.
The interval has a special role. It allows to make the alarm reconfigure itself. This is useful if you need a repeated alarm that cannot be expressed by matching the current date and time. For example, to make the alarm trigger every 23 seconds it can be configured as (-1, -1, -1, -1, -1, -1, 23). Internally the Bricklet will take the current date and time, add 23 seconds to it and set the result as its alarm. The first alarm will be triggered 23 seconds after the call. Because the interval is not -1, the Bricklet will do the same again internally, take the current date and time, add 23 seconds to it and set that as its alarm. This results in a repeated alarm that triggers every 23 seconds.
The interval can also be used in combination with the other parameters. For example, configuring the alarm as (-1, -1, 7, 30, -1, -1, 300) results in an alarm that triggers every day at 7:30 AM and is then repeated every 5 minutes.
The following symbols are available for this function:
For <month>:
For <day>:
For <hour>:
For <minute>:
For <second>:
For <weekday>:
For <interval>:
New in version 2.0.1 (Plugin).
real-time-clock-bricklet
<uid> get-alarm
¶Output: |
|
---|
Returns the alarm configuration as set by set-alarm
.
The following symbols are available for this function:
For month:
For day:
For hour:
For minute:
For second:
For weekday:
For interval:
New in version 2.0.1 (Plugin).
Callbacks can be used to receive time critical or recurring data from the device:
tinkerforge dispatch real-time-clock-bricklet <uid> example
The available callbacks are described below.
Note
Using callbacks for recurring events is always preferred compared to using getters. It will use less USB bandwidth and the latency will be a lot better, since there is no round trip time.
real-time-clock-bricklet
<uid> date-time
¶Output: |
|
---|
This callback is triggered periodically with the period that is set by
set-date-time-callback-period
. The parameters are the same
as for get-date-time
and get-timestamp
combined.
The date-time
callback is only triggered if the date or time changed
since the last triggering.
The following symbols are available for this function:
For weekday:
New in version 2.0.1 (Plugin).
real-time-clock-bricklet
<uid> alarm
¶Output: |
|
---|
This callback is triggered every time the current date and time matches the
configured alarm (see set-alarm
). The parameters are the same
as for get-date-time
and get-timestamp
combined.
The following symbols are available for this function:
For weekday:
New in version 2.0.1 (Plugin).