This is the description of the MATLAB/Octave 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 MATLAB/Octave API bindings is part of their general description.
The example code below is Public Domain (CC0 1.0).
Download (matlab_example_simple.m)
1function matlab_example_simple()
2 import com.tinkerforge.IPConnection;
3 import com.tinkerforge.BrickletRealTimeClock;
4
5 HOST = 'localhost';
6 PORT = 4223;
7 UID = 'XYZ'; % Change XYZ to the UID of your Real-Time Clock Bricklet
8
9 ipcon = IPConnection(); % Create IP connection
10 rtc = handle(BrickletRealTimeClock(UID, ipcon), 'CallbackProperties'); % Create device object
11
12 ipcon.connect(HOST, PORT); % Connect to brickd
13 % Don't use device before ipcon is connected
14
15 % Get current date and time
16 dateTime = rtc.getDateTime();
17
18 fprintf('Year: %i\n', dateTime.year);
19 fprintf('Month: %i\n', dateTime.month);
20 fprintf('Day: %i\n', dateTime.day);
21 fprintf('Hour: %i\n', dateTime.hour);
22 fprintf('Minute: %i\n', dateTime.minute);
23 fprintf('Second: %i\n', dateTime.second);
24 fprintf('Centisecond: %i\n', dateTime.centisecond);
25
26 if dateTime.weekday == BrickletRealTimeClock.WEEKDAY_MONDAY
27 fprintf('Weekday: Monday\n');
28 elseif dateTime.weekday == BrickletRealTimeClock.WEEKDAY_TUESDAY
29 fprintf('Weekday: Tuesday\n');
30 elseif dateTime.weekday == BrickletRealTimeClock.WEEKDAY_WEDNESDAY
31 fprintf('Weekday: Wednesday\n');
32 elseif dateTime.weekday == BrickletRealTimeClock.WEEKDAY_THURSDAY
33 fprintf('Weekday: Thursday\n');
34 elseif dateTime.weekday == BrickletRealTimeClock.WEEKDAY_FRIDAY
35 fprintf('Weekday: Friday\n');
36 elseif dateTime.weekday == BrickletRealTimeClock.WEEKDAY_SATURDAY
37 fprintf('Weekday: Saturday\n');
38 elseif dateTime.weekday == BrickletRealTimeClock.WEEKDAY_SUNDAY
39 fprintf('Weekday: Sunday\n');
40 end
41
42 % Get current timestamp
43 timestamp = rtc.getTimestamp();
44 fprintf('Timestamp: %i ms\n', timestamp);
45
46 input('Press key to exit\n', 's');
47 ipcon.disconnect();
48end
Download (matlab_example_callback.m)
1function matlab_example_callback()
2 import com.tinkerforge.IPConnection;
3 import com.tinkerforge.BrickletRealTimeClock;
4
5 HOST = 'localhost';
6 PORT = 4223;
7 UID = 'XYZ'; % Change XYZ to the UID of your Real-Time Clock Bricklet
8
9 ipcon = IPConnection(); % Create IP connection
10 rtc = handle(BrickletRealTimeClock(UID, ipcon), 'CallbackProperties'); % Create device object
11
12 ipcon.connect(HOST, PORT); % Connect to brickd
13 % Don't use device before ipcon is connected
14
15 % Register date and time callback to function cb_date_time
16 set(rtc, 'DateTimeCallback', @(h, e) cb_date_time(e));
17
18 % Set period for date and time callback to 5s (5000ms)
19 % Note: The date and time callback is only called every 5 seconds
20 % if the date and time has changed since the last call!
21 rtc.setDateTimeCallbackPeriod(5000);
22
23 input('Press key to exit\n', 's');
24 ipcon.disconnect();
25end
26
27% Callback function for date and time callback
28function cb_date_time(e)
29 fprintf('Year: %i\n', e.year);
30 fprintf('Month: %i\n', e.month);
31 fprintf('Day: %i\n', e.day);
32 fprintf('Hour: %i\n', e.hour);
33 fprintf('Minute: %i\n', e.minute);
34 fprintf('Second: %i\n', e.second);
35 fprintf('Centisecond: %i\n', e.centisecond);
36
37 if e.weekday == com.tinkerforge.BrickletRealTimeClock.WEEKDAY_MONDAY
38 fprintf('Weekday: Monday\n');
39 elseif e.weekday == com.tinkerforge.BrickletRealTimeClock.WEEKDAY_TUESDAY
40 fprintf('Weekday: Tuesday\n');
41 elseif e.weekday == com.tinkerforge.BrickletRealTimeClock.WEEKDAY_WEDNESDAY
42 fprintf('Weekday: Wednesday\n');
43 elseif e.weekday == com.tinkerforge.BrickletRealTimeClock.WEEKDAY_THURSDAY
44 fprintf('Weekday: Thursday\n');
45 elseif e.weekday == com.tinkerforge.BrickletRealTimeClock.WEEKDAY_FRIDAY
46 fprintf('Weekday: Friday\n');
47 elseif e.weekday == com.tinkerforge.BrickletRealTimeClock.WEEKDAY_SATURDAY
48 fprintf('Weekday: Saturday\n');
49 elseif e.weekday == com.tinkerforge.BrickletRealTimeClock.WEEKDAY_SUNDAY
50 fprintf('Weekday: Sunday\n');
51 end
52
53 fprintf('Timestamp: %i\n', e.timestamp);
54 fprintf('\n');
55end
Download (octave_example_simple.m)
1function octave_example_simple()
2 more off;
3
4 HOST = "localhost";
5 PORT = 4223;
6 UID = "XYZ"; % Change XYZ to the UID of your Real-Time Clock Bricklet
7
8 ipcon = javaObject("com.tinkerforge.IPConnection"); % Create IP connection
9 rtc = javaObject("com.tinkerforge.BrickletRealTimeClock", UID, ipcon); % Create device object
10
11 ipcon.connect(HOST, PORT); % Connect to brickd
12 % Don't use device before ipcon is connected
13
14 % Get current date and time
15 dateTime = rtc.getDateTime();
16
17 fprintf("Year: %d\n", dateTime.year);
18 fprintf("Month: %d\n", java2int(dateTime.month));
19 fprintf("Day: %d\n", java2int(dateTime.day));
20 fprintf("Hour: %d\n", java2int(dateTime.hour));
21 fprintf("Minute: %d\n", java2int(dateTime.minute));
22 fprintf("Second: %d\n", java2int(dateTime.second));
23 fprintf("Centisecond: %d\n", java2int(dateTime.centisecond));
24
25 if java2int(dateTime.weekday) == 1
26 fprintf("Weekday: Monday\n");
27 elseif java2int(dateTime.weekday) == 2
28 fprintf("Weekday: Tuesday\n");
29 elseif java2int(dateTime.weekday) == 3
30 fprintf("Weekday: Wednesday\n");
31 elseif java2int(dateTime.weekday) == 4
32 fprintf("Weekday: Thursday\n");
33 elseif java2int(dateTime.weekday) == 5
34 fprintf("Weekday: Friday\n");
35 elseif java2int(dateTime.weekday) == 6
36 fprintf("Weekday: Saturday\n");
37 elseif java2int(dateTime.weekday) == 7
38 fprintf("Weekday: Sunday\n");
39 end
40
41 % Get current timestamp
42 timestamp = rtc.getTimestamp();
43 fprintf("Timestamp: %d ms\n", java2int(timestamp));
44
45 input("Press key to exit\n", "s");
46 ipcon.disconnect();
47end
48
49function int = java2int(value)
50 if compare_versions(version(), "3.8", "<=")
51 int = value.intValue();
52 else
53 int = value;
54 end
55end
Download (octave_example_callback.m)
1function octave_example_callback()
2 more off;
3
4 HOST = "localhost";
5 PORT = 4223;
6 UID = "XYZ"; % Change XYZ to the UID of your Real-Time Clock Bricklet
7
8 ipcon = javaObject("com.tinkerforge.IPConnection"); % Create IP connection
9 rtc = javaObject("com.tinkerforge.BrickletRealTimeClock", UID, ipcon); % Create device object
10
11 ipcon.connect(HOST, PORT); % Connect to brickd
12 % Don't use device before ipcon is connected
13
14 % Register date and time callback to function cb_date_time
15 rtc.addDateTimeCallback(@cb_date_time);
16
17 % Set period for date and time callback to 5s (5000ms)
18 % Note: The date and time callback is only called every 5 seconds
19 % if the date and time has changed since the last call!
20 rtc.setDateTimeCallbackPeriod(5000);
21
22 input("Press key to exit\n", "s");
23 ipcon.disconnect();
24end
25
26% Callback function for date and time callback
27function cb_date_time(e)
28 fprintf("Year: %d\n", e.year);
29 fprintf("Month: %d\n", java2int(e.month));
30 fprintf("Day: %d\n", java2int(e.day));
31 fprintf("Hour: %d\n", java2int(e.hour));
32 fprintf("Minute: %d\n", java2int(e.minute));
33 fprintf("Second: %d\n", java2int(e.second));
34 fprintf("Centisecond: %d\n", java2int(e.centisecond));
35
36 if java2int(e.weekday) == 1
37 fprintf("Weekday: Monday\n");
38 elseif java2int(e.weekday) == 2
39 fprintf("Weekday: Tuesday\n");
40 elseif java2int(e.weekday) == 3
41 fprintf("Weekday: Wednesday\n");
42 elseif java2int(e.weekday) == 4
43 fprintf("Weekday: Thursday\n");
44 elseif java2int(e.weekday) == 5
45 fprintf("Weekday: Friday\n");
46 elseif java2int(e.weekday) == 6
47 fprintf("Weekday: Saturday\n");
48 elseif java2int(e.weekday) == 7
49 fprintf("Weekday: Sunday\n");
50 end
51
52 fprintf("Timestamp: %d\n", java2int(e.timestamp));
53 fprintf("\n");
54end
55
56function int = java2int(value)
57 if compare_versions(version(), "3.8", "<=")
58 int = value.intValue();
59 else
60 int = value;
61 end
62end
Generally, every method of the MATLAB bindings that returns a value can
throw a TimeoutException. This exception gets thrown if the
device did not respond. If a cable based connection is used, it is
unlikely that this exception gets thrown (assuming nobody unplugs the
device). However, if a wireless connection is used, timeouts will occur
if the distance to the device gets too big.
Beside the TimeoutException there is also a NotConnectedException that
is thrown if a method needs to communicate with the device while the
IP Connection is not connected.
Since the MATLAB bindings are based on Java and Java does not support multiple return values and return by reference is not possible for primitive types, we use small classes that only consist of member variables. The member variables of the returned objects are described in the corresponding method descriptions.
The package for all Brick/Bricklet bindings and the IP Connection is
com.tinkerforge.*
All methods listed below are thread-safe.
| Parameters: |
|
|---|---|
| Returns: |
|
Creates an object with the unique device ID uid.
In MATLAB:
import com.tinkerforge.BrickletRealTimeClock;
realTimeClock = BrickletRealTimeClock('YOUR_DEVICE_UID', ipcon);
In Octave:
realTimeClock = java_new("com.tinkerforge.BrickletRealTimeClock", "YOUR_DEVICE_UID", ipcon);
This object can then be used after the IP Connection is connected.
| Parameters: |
|
|---|
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 constants are available for this function:
For weekday:
BrickletRealTimeClock.WEEKDAY_MONDAY = 1
BrickletRealTimeClock.WEEKDAY_TUESDAY = 2
BrickletRealTimeClock.WEEKDAY_WEDNESDAY = 3
BrickletRealTimeClock.WEEKDAY_THURSDAY = 4
BrickletRealTimeClock.WEEKDAY_FRIDAY = 5
BrickletRealTimeClock.WEEKDAY_SATURDAY = 6
BrickletRealTimeClock.WEEKDAY_SUNDAY = 7
| Return Object: |
|
|---|
Returns the current date (including weekday) and the current time of the real-time clock.
The following constants are available for this function:
For weekday:
BrickletRealTimeClock.WEEKDAY_MONDAY = 1
BrickletRealTimeClock.WEEKDAY_TUESDAY = 2
BrickletRealTimeClock.WEEKDAY_WEDNESDAY = 3
BrickletRealTimeClock.WEEKDAY_THURSDAY = 4
BrickletRealTimeClock.WEEKDAY_FRIDAY = 5
BrickletRealTimeClock.WEEKDAY_SATURDAY = 6
BrickletRealTimeClock.WEEKDAY_SUNDAY = 7
| Returns: |
|
|---|
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.
| Parameters: |
|
|---|
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.
| Returns: |
|
|---|
Returns the offset as set by setOffset().
| Return Object: |
|
|---|
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. There is also a constant for the device identifier of this Bricklet.
| Parameters: |
|
|---|
Sets the period with which the DateTimeCallback callback is triggered
periodically. A value of 0 turns the callback off.
The DateTimeCallback Callback is only triggered if the date or time changed
since the last triggering.
Added in version 2.0.1$nbsp;(Plugin).
| Returns: |
|
|---|
Returns the period as set by setDateTimeCallbackPeriod().
Added in version 2.0.1$nbsp;(Plugin).
| Parameters: |
|
|---|
Configures a repeatable alarm. The AlarmCallback 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 constants are available for this function:
For month:
BrickletRealTimeClock.ALARM_MATCH_DISABLED = -1
For day:
BrickletRealTimeClock.ALARM_MATCH_DISABLED = -1
For hour:
BrickletRealTimeClock.ALARM_MATCH_DISABLED = -1
For minute:
BrickletRealTimeClock.ALARM_MATCH_DISABLED = -1
For second:
BrickletRealTimeClock.ALARM_MATCH_DISABLED = -1
For weekday:
BrickletRealTimeClock.ALARM_MATCH_DISABLED = -1
For interval:
BrickletRealTimeClock.ALARM_INTERVAL_DISABLED = -1
Added in version 2.0.1$nbsp;(Plugin).
| Return Object: |
|
|---|
Returns the alarm configuration as set by setAlarm().
The following constants are available for this function:
For month:
BrickletRealTimeClock.ALARM_MATCH_DISABLED = -1
For day:
BrickletRealTimeClock.ALARM_MATCH_DISABLED = -1
For hour:
BrickletRealTimeClock.ALARM_MATCH_DISABLED = -1
For minute:
BrickletRealTimeClock.ALARM_MATCH_DISABLED = -1
For second:
BrickletRealTimeClock.ALARM_MATCH_DISABLED = -1
For weekday:
BrickletRealTimeClock.ALARM_MATCH_DISABLED = -1
For interval:
BrickletRealTimeClock.ALARM_INTERVAL_DISABLED = -1
Added in version 2.0.1$nbsp;(Plugin).
Callbacks can be registered to receive time critical or recurring data from the device. The registration is done with "set" function of MATLAB. The parameters consist of the IP Connection object, the callback name and the callback function. For example, it looks like this in MATLAB:
function my_callback(e)
fprintf('Parameter: %s\n', e.param);
end
set(device, 'ExampleCallback', @(h, e) my_callback(e));
Due to a difference in the Octave Java support the "set" function cannot be used in Octave. The registration is done with "add*Callback" functions of the device object. It looks like this in Octave:
function my_callback(e)
fprintf("Parameter: %s\n", e.param);
end
device.addExampleCallback(@my_callback);
It is possible to add several callbacks and to remove them with the corresponding "remove*Callback" function.
The parameters of the callback are passed to the callback function as fields of
the structure e, which is derived from the java.util.EventObject class.
The available callback names with corresponding structure fields 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.
| Event Object: |
|
|---|
This callback is triggered periodically with the period that is set by
setDateTimeCallbackPeriod(). The parameters are the same
as for getDateTime() and getTimestamp() combined.
The DateTimeCallback callback is only triggered if the date or time changed
since the last triggering.
The following constants are available for this function:
For weekday:
BrickletRealTimeClock.WEEKDAY_MONDAY = 1
BrickletRealTimeClock.WEEKDAY_TUESDAY = 2
BrickletRealTimeClock.WEEKDAY_WEDNESDAY = 3
BrickletRealTimeClock.WEEKDAY_THURSDAY = 4
BrickletRealTimeClock.WEEKDAY_FRIDAY = 5
BrickletRealTimeClock.WEEKDAY_SATURDAY = 6
BrickletRealTimeClock.WEEKDAY_SUNDAY = 7
Added in version 2.0.1$nbsp;(Plugin).
In MATLAB the set() function can be used to register a callback function
to this callback.
In Octave a callback function can be added to this callback using the
addDateTimeCallback() function. An added callback function can be removed with
the removeDateTimeCallback() function.
| Event Object: |
|
|---|
This callback is triggered every time the current date and time matches the
configured alarm (see setAlarm()). The parameters are the same
as for getDateTime() and getTimestamp() combined.
The following constants are available for this function:
For weekday:
BrickletRealTimeClock.WEEKDAY_MONDAY = 1
BrickletRealTimeClock.WEEKDAY_TUESDAY = 2
BrickletRealTimeClock.WEEKDAY_WEDNESDAY = 3
BrickletRealTimeClock.WEEKDAY_THURSDAY = 4
BrickletRealTimeClock.WEEKDAY_FRIDAY = 5
BrickletRealTimeClock.WEEKDAY_SATURDAY = 6
BrickletRealTimeClock.WEEKDAY_SUNDAY = 7
Added in version 2.0.1$nbsp;(Plugin).
In MATLAB the set() function can be used to register a callback function
to this callback.
In Octave a callback function can be added to this callback using the
addAlarmCallback() function. An added callback function can be removed with
the removeAlarmCallback() function.
Virtual functions don't communicate with the device itself, but operate only on the API bindings device object. They can be called without the corresponding IP Connection object being connected.
| Return Object: |
|
|---|
Returns the version of the API definition implemented by this API bindings. This is neither the release version of this API bindings nor does it tell you anything about the represented Brick or Bricklet.
| Parameters: |
|
|---|---|
| Returns: |
|
Returns the response expected flag for the function specified by the function ID parameter. It is true if the function is expected to send a response, false otherwise.
For getter functions this is enabled by default and cannot be disabled,
because those functions will always send a response. For callback configuration
functions it is enabled by default too, but can be disabled by
setResponseExpected(). For setter functions it is disabled by default
and can be enabled.
Enabling the response expected flag for a setter function allows to detect timeouts and other error conditions calls of this setter as well. The device will then send a response for this purpose. If this flag is disabled for a setter function then no response is sent and errors are silently ignored, because they cannot be detected.
The following constants are available for this function:
For functionId:
BrickletRealTimeClock.FUNCTION_SET_DATE_TIME = 1
BrickletRealTimeClock.FUNCTION_SET_OFFSET = 4
BrickletRealTimeClock.FUNCTION_SET_DATE_TIME_CALLBACK_PERIOD = 6
BrickletRealTimeClock.FUNCTION_SET_ALARM = 8
| Parameters: |
|
|---|
Changes the response expected flag of the function specified by the function ID parameter. This flag can only be changed for setter (default value: false) and callback configuration functions (default value: true). For getter functions it is always enabled.
Enabling the response expected flag for a setter function allows to detect timeouts and other error conditions calls of this setter as well. The device will then send a response for this purpose. If this flag is disabled for a setter function then no response is sent and errors are silently ignored, because they cannot be detected.
The following constants are available for this function:
For functionId:
BrickletRealTimeClock.FUNCTION_SET_DATE_TIME = 1
BrickletRealTimeClock.FUNCTION_SET_OFFSET = 4
BrickletRealTimeClock.FUNCTION_SET_DATE_TIME_CALLBACK_PERIOD = 6
BrickletRealTimeClock.FUNCTION_SET_ALARM = 8
| Parameters: |
|
|---|
Changes the response expected flag for all setter and callback configuration functions of this device at once.
This constant is used to identify a Real-Time Clock Bricklet.
The getIdentity() function and the
IPConnection.EnumerateCallback
callback of the IP Connection have a deviceIdentifier parameter to specify
the Brick's or Bricklet's type.
This constant represents the human readable name of a Real-Time Clock Bricklet.