This is the description of the C# API bindings for the Real-Time Clock Bricklet 2.0. General information and technical specifications for the Real-Time Clock Bricklet 2.0 are summarized in its hardware description.
An installation guide for the C# 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 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 | using System;
using Tinkerforge;
class Example
{
private static string HOST = "localhost";
private static int PORT = 4223;
private static string UID = "XYZ"; // Change XYZ to the UID of your Real-Time Clock Bricklet 2.0
static void Main()
{
IPConnection ipcon = new IPConnection(); // Create IP connection
BrickletRealTimeClockV2 rtc =
new BrickletRealTimeClockV2(UID, ipcon); // Create device object
ipcon.Connect(HOST, PORT); // Connect to brickd
// Don't use device before ipcon is connected
// Get current date and time
int year; byte month, day, hour, minute, second, centisecond, weekday; long timestamp;
rtc.GetDateTime(out year, out month, out day, out hour, out minute, out second,
out centisecond, out weekday, out timestamp);
Console.WriteLine("Year: " + year);
Console.WriteLine("Month: " + month);
Console.WriteLine("Day: " + day);
Console.WriteLine("Hour: " + hour);
Console.WriteLine("Minute: " + minute);
Console.WriteLine("Second: " + second);
Console.WriteLine("Centisecond: " + centisecond);
if(weekday == BrickletRealTimeClockV2.WEEKDAY_MONDAY)
{
Console.WriteLine("Weekday: Monday");
}
else if(weekday == BrickletRealTimeClockV2.WEEKDAY_TUESDAY)
{
Console.WriteLine("Weekday: Tuesday");
}
else if(weekday == BrickletRealTimeClockV2.WEEKDAY_WEDNESDAY)
{
Console.WriteLine("Weekday: Wednesday");
}
else if(weekday == BrickletRealTimeClockV2.WEEKDAY_THURSDAY)
{
Console.WriteLine("Weekday: Thursday");
}
else if(weekday == BrickletRealTimeClockV2.WEEKDAY_FRIDAY)
{
Console.WriteLine("Weekday: Friday");
}
else if(weekday == BrickletRealTimeClockV2.WEEKDAY_SATURDAY)
{
Console.WriteLine("Weekday: Saturday");
}
else if(weekday == BrickletRealTimeClockV2.WEEKDAY_SUNDAY)
{
Console.WriteLine("Weekday: Sunday");
}
Console.WriteLine("Timestamp: " + timestamp + " ms");
Console.WriteLine("Press enter to exit");
Console.ReadLine();
ipcon.Disconnect();
}
}
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 | using System;
using Tinkerforge;
class Example
{
private static string HOST = "localhost";
private static int PORT = 4223;
private static string UID = "XYZ"; // Change XYZ to the UID of your Real-Time Clock Bricklet 2.0
// Callback function for date and time callback
static void DateTimeCB(BrickletRealTimeClockV2 sender, int year, byte month, byte day,
byte hour, byte minute, byte second, byte centisecond,
byte weekday, long timestamp)
{
Console.WriteLine("Year: " + year);
Console.WriteLine("Month: " + month);
Console.WriteLine("Day: " + day);
Console.WriteLine("Hour: " + hour);
Console.WriteLine("Minute: " + minute);
Console.WriteLine("Second: " + second);
Console.WriteLine("Centisecond: " + centisecond);
if(weekday == BrickletRealTimeClockV2.WEEKDAY_MONDAY)
{
Console.WriteLine("Weekday: Monday");
}
else if(weekday == BrickletRealTimeClockV2.WEEKDAY_TUESDAY)
{
Console.WriteLine("Weekday: Tuesday");
}
else if(weekday == BrickletRealTimeClockV2.WEEKDAY_WEDNESDAY)
{
Console.WriteLine("Weekday: Wednesday");
}
else if(weekday == BrickletRealTimeClockV2.WEEKDAY_THURSDAY)
{
Console.WriteLine("Weekday: Thursday");
}
else if(weekday == BrickletRealTimeClockV2.WEEKDAY_FRIDAY)
{
Console.WriteLine("Weekday: Friday");
}
else if(weekday == BrickletRealTimeClockV2.WEEKDAY_SATURDAY)
{
Console.WriteLine("Weekday: Saturday");
}
else if(weekday == BrickletRealTimeClockV2.WEEKDAY_SUNDAY)
{
Console.WriteLine("Weekday: Sunday");
}
Console.WriteLine("Timestamp: " + timestamp);
Console.WriteLine("");
}
static void Main()
{
IPConnection ipcon = new IPConnection(); // Create IP connection
BrickletRealTimeClockV2 rtc =
new BrickletRealTimeClockV2(UID, ipcon); // Create device object
ipcon.Connect(HOST, PORT); // Connect to brickd
// Don't use device before ipcon is connected
// Register date and time callback to function DateTimeCB
rtc.DateTimeCallback += DateTimeCB;
// Set period for date and time callback to 5s (5000ms)
rtc.SetDateTimeCallbackConfiguration(5000);
Console.WriteLine("Press enter to exit");
Console.ReadLine();
ipcon.Disconnect();
}
}
|
Generally, every method of the C# bindings that returns a value can
throw a Tinkerforge.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 plugs the
device out). However, if a wireless connection is used, timeouts will occur
if the distance to the device gets too big.
Since C# does not support multiple return values directly, we use the out
keyword to return multiple values from a method.
The namespace for all Brick/Bricklet bindings and the IPConnection is
Tinkerforge.*
.
All methods listed below are thread-safe.
BrickletRealTimeClockV2
(string uid, IPConnection ipcon)¶Parameters: |
|
---|---|
Returns: |
|
Creates an object with the unique device ID uid
:
BrickletRealTimeClockV2 realTimeClockV2 = new BrickletRealTimeClockV2("YOUR_DEVICE_UID", ipcon);
This object can then be used after the IP Connection is connected.
BrickletRealTimeClockV2.
SetDateTime
(int year, byte month, byte day, byte hour, byte minute, byte second, byte centisecond, byte weekday)¶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:
BrickletRealTimeClockV2.
GetDateTime
(out int year, out byte month, out byte day, out byte hour, out byte minute, out byte second, out byte centisecond, out byte weekday, out long timestamp)¶Output Parameters: |
|
---|
Returns the current date (including weekday) and the current time of the real-time.
The timestamp represents the current date and the the current time of the real-time clock converted to milliseconds and is an offset to 2000-01-01 00:00:00.0000.
The following constants are available for this function:
For weekday:
BrickletRealTimeClockV2.
GetTimestamp
()¶Returns: |
|
---|
Returns the current date and the time of the real-time clock converted to milliseconds. The timestamp has an effective resolution of hundredths of a second and is an offset to 2000-01-01 00:00:00.0000.
BrickletRealTimeClockV2.
SetOffset
(short offset)¶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.
BrickletRealTimeClockV2.
GetOffset
()¶Returns: |
|
---|
Returns the offset as set by SetOffset()
.
BrickletRealTimeClockV2.
GetSPITFPErrorCount
(out long errorCountAckChecksum, out long errorCountMessageChecksum, out long errorCountFrame, out long errorCountOverflow)¶Output Parameters: |
|
---|
Returns the error count for the communication between Brick and Bricklet.
The errors are divided into
The errors counts are for errors that occur on the Bricklet side. All Bricks have a similar function that returns the errors on the Brick side.
BrickletRealTimeClockV2.
SetStatusLEDConfig
(byte config)¶Parameters: |
|
---|
Sets the status LED configuration. By default the LED shows communication traffic between Brick and Bricklet, it flickers once for every 10 received data packets.
You can also turn the LED permanently on/off or show a heartbeat.
If the Bricklet is in bootloader mode, the LED is will show heartbeat by default.
The following constants are available for this function:
For config:
BrickletRealTimeClockV2.
GetStatusLEDConfig
()¶Returns: |
|
---|
Returns the configuration as set by SetStatusLEDConfig()
The following constants are available for this function:
For config:
BrickletRealTimeClockV2.
GetChipTemperature
()¶Returns: |
|
---|
Returns the temperature as measured inside the microcontroller. The value returned is not the ambient temperature!
The temperature is only proportional to the real temperature and it has bad accuracy. Practically it is only useful as an indicator for temperature changes.
BrickletRealTimeClockV2.
Reset
()¶Calling this function will reset the Bricklet. All configurations will be lost.
After a reset you have to create new device objects, calling functions on the existing ones will result in undefined behavior!
BrickletRealTimeClockV2.
GetIdentity
(out string uid, out string connectedUid, out char position, out byte[] hardwareVersion, out byte[] firmwareVersion, out int deviceIdentifier)¶Output Parameters: |
|
---|
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.
BrickletRealTimeClockV2.
SetDateTimeCallbackConfiguration
(long period)¶Parameters: |
|
---|
Sets the period with which the DateTimeCallback
callback is triggered
periodically. A value of 0 turns the callback off.
BrickletRealTimeClockV2.
GetDateTimeCallbackConfiguration
()¶Returns: |
|
---|
Returns the period as set by SetDateTimeCallbackConfiguration()
.
BrickletRealTimeClockV2.
SetAlarm
(short month, short day, short hour, short minute, short second, short weekday, int interval)¶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:
For day:
For hour:
For minute:
For second:
For weekday:
For interval:
BrickletRealTimeClockV2.
GetAlarm
(out short month, out short day, out short hour, out short minute, out short second, out short weekday, out int interval)¶Output Parameters: |
|
---|
Returns the alarm configuration as set by SetAlarm()
.
The following constants are available for this function:
For month:
For day:
For hour:
For minute:
For second:
For weekday:
For interval:
Callbacks can be registered to receive time critical or recurring data from the device. The registration is done by appending your callback handler to the corresponding event:
void MyCallback(BrickletRealTimeClockV2 sender, int value)
{
System.Console.WriteLine("Value: " + value);
}
realTimeClockV2.ExampleCallback += MyCallback;
The available events 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.
BrickletRealTimeClockV2.
DateTimeCallback
(BrickletRealTimeClockV2 sender, int year, byte month, byte day, byte hour, byte minute, byte second, byte centisecond, byte weekday, long timestamp)¶Callback Parameters: |
|
---|
This callback is triggered periodically with the period that is set by
SetDateTimeCallbackConfiguration()
. The parameters are the
same as for GetDateTime()
.
The following constants are available for this function:
For weekday:
BrickletRealTimeClockV2.
AlarmCallback
(BrickletRealTimeClockV2 sender, int year, byte month, byte day, byte hour, byte minute, byte second, byte centisecond, byte weekday, long timestamp)¶Callback Parameters: |
|
---|
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()
.
The following constants are available for this function:
For weekday:
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.
BrickletRealTimeClockV2.
GetAPIVersion
()¶Output Parameters: |
|
---|
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.
BrickletRealTimeClockV2.
GetResponseExpected
(byte functionId)¶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:
BrickletRealTimeClockV2.
SetResponseExpected
(byte functionId, bool responseExpected)¶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:
BrickletRealTimeClockV2.
SetResponseExpectedAll
(bool responseExpected)¶Parameters: |
|
---|
Changes the response expected flag for all setter and callback configuration functions of this device at once.
Internal functions are used for maintenance tasks such as flashing a new firmware of changing the UID of a Bricklet. These task should be performed using Brick Viewer instead of using the internal functions directly.
BrickletRealTimeClockV2.
SetBootloaderMode
(byte mode)¶Parameters: |
|
---|---|
Returns: |
|
Sets the bootloader mode and returns the status after the requested mode change was instigated.
You can change from bootloader mode to firmware mode and vice versa. A change from bootloader mode to firmware mode will only take place if the entry function, device identifier and CRC are present and correct.
This function is used by Brick Viewer during flashing. It should not be necessary to call it in a normal user program.
The following constants are available for this function:
For mode:
For status:
BrickletRealTimeClockV2.
GetBootloaderMode
()¶Returns: |
|
---|
Returns the current bootloader mode, see SetBootloaderMode()
.
The following constants are available for this function:
For mode:
BrickletRealTimeClockV2.
SetWriteFirmwarePointer
(long pointer)¶Parameters: |
|
---|
Sets the firmware pointer for WriteFirmware()
. The pointer has
to be increased by chunks of size 64. The data is written to flash
every 4 chunks (which equals to one page of size 256).
This function is used by Brick Viewer during flashing. It should not be necessary to call it in a normal user program.
BrickletRealTimeClockV2.
WriteFirmware
(byte[] data)¶Parameters: |
|
---|---|
Returns: |
|
Writes 64 Bytes of firmware at the position as written by
SetWriteFirmwarePointer()
before. The firmware is written
to flash every 4 chunks.
You can only write firmware in bootloader mode.
This function is used by Brick Viewer during flashing. It should not be necessary to call it in a normal user program.
BrickletRealTimeClockV2.
WriteUID
(long uid)¶Parameters: |
|
---|
Writes a new UID into flash. If you want to set a new UID you have to decode the Base58 encoded UID string into an integer first.
We recommend that you use Brick Viewer to change the UID.
BrickletRealTimeClockV2.
ReadUID
()¶Returns: |
|
---|
Returns the current UID as an integer. Encode as Base58 to get the usual string version.
BrickletRealTimeClockV2.
DEVICE_IDENTIFIER
¶This constant is used to identify a Real-Time Clock Bricklet 2.0.
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.
BrickletRealTimeClockV2.
DEVICE_DISPLAY_NAME
¶This constant represents the human readable name of a Real-Time Clock Bricklet 2.0.