Delphi/Lazarus - Real-Time Clock Bricklet 2.0

This is the description of the Delphi/Lazarus 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 Delphi/Lazarus API bindings is part of their general description.

Examples

The example code below is Public Domain (CC0 1.0).

Simple

Download (ExampleSimple.pas)

 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
program ExampleSimple;

{$ifdef MSWINDOWS}{$apptype CONSOLE}{$endif}
{$ifdef FPC}{$mode OBJFPC}{$H+}{$endif}

uses
  SysUtils, IPConnection, BrickletRealTimeClockV2;

type
  TExample = class
  private
    ipcon: TIPConnection;
    rtc: TBrickletRealTimeClockV2;
  public
    procedure Execute;
  end;

const
  HOST = 'localhost';
  PORT = 4223;
  UID = 'XYZ'; { Change XYZ to the UID of your Real-Time Clock Bricklet 2.0 }

var
  e: TExample;

procedure TExample.Execute;
var year: word; month, day, hour, minute, second, centisecond, weekday: byte;
    timestamp: int64;
begin
  { Create IP connection }
  ipcon := TIPConnection.Create;

  { Create device object }
  rtc := TBrickletRealTimeClockV2.Create(UID, ipcon);

  { Connect to brickd }
  ipcon.Connect(HOST, PORT);
  { Don't use device before ipcon is connected }

  { Get current date and time }
  rtc.GetDateTime(year, month, day, hour, minute, second, centisecond, weekday,
                  timestamp);

  WriteLn(Format('Year: %d', [year]));
  WriteLn(Format('Month: %d', [month]));
  WriteLn(Format('Day: %d', [day]));
  WriteLn(Format('Hour: %d', [hour]));
  WriteLn(Format('Minute: %d', [minute]));
  WriteLn(Format('Second: %d', [second]));
  WriteLn(Format('Centisecond: %d', [centisecond]));
  WriteLn(Format('Weekday: %d', [weekday]));
  WriteLn(Format('Timestamp: %d ms', [timestamp]));

  WriteLn('Press key to exit');
  ReadLn;
  ipcon.Destroy; { Calls ipcon.Disconnect internally }
end;

begin
  e := TExample.Create;
  e.Execute;
  e.Destroy;
end.

Callback

Download (ExampleCallback.pas)

 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
76
program ExampleCallback;

{$ifdef MSWINDOWS}{$apptype CONSOLE}{$endif}
{$ifdef FPC}{$mode OBJFPC}{$H+}{$endif}

uses
  SysUtils, IPConnection, BrickletRealTimeClockV2;

type
  TExample = class
  private
    ipcon: TIPConnection;
    rtc: TBrickletRealTimeClockV2;
  public
    procedure DateTimeCB(sender: TBrickletRealTimeClockV2; const year: word;
                         const month: byte; const day: byte; const hour: byte;
                         const minute: byte; const second: byte; const centisecond: byte;
                         const weekday: byte; const timestamp: int64);
    procedure Execute;
  end;

const
  HOST = 'localhost';
  PORT = 4223;
  UID = 'XYZ'; { Change XYZ to the UID of your Real-Time Clock Bricklet 2.0 }

var
  e: TExample;

{ Callback procedure for date and time callback }
procedure TExample.DateTimeCB(sender: TBrickletRealTimeClockV2; const year: word;
                              const month: byte; const day: byte; const hour: byte;
                              const minute: byte; const second: byte;
                              const centisecond: byte; const weekday: byte;
                              const timestamp: int64);
begin
  WriteLn(Format('Year: %d', [year]));
  WriteLn(Format('Month: %d', [month]));
  WriteLn(Format('Day: %d', [day]));
  WriteLn(Format('Hour: %d', [hour]));
  WriteLn(Format('Minute: %d', [minute]));
  WriteLn(Format('Second: %d', [second]));
  WriteLn(Format('Centisecond: %d', [centisecond]));
  WriteLn(Format('Weekday: %d', [weekday]));
  WriteLn(Format('Timestamp: %d', [timestamp]));
  WriteLn('');
end;

procedure TExample.Execute;
begin
  { Create IP connection }
  ipcon := TIPConnection.Create;

  { Create device object }
  rtc := TBrickletRealTimeClockV2.Create(UID, ipcon);

  { Connect to brickd }
  ipcon.Connect(HOST, PORT);
  { Don't use device before ipcon is connected }

  { Register date and time callback to procedure DateTimeCB }
  rtc.OnDateTime := {$ifdef FPC}@{$endif}DateTimeCB;

  { Set period for date and time callback to 5s (5000ms) }
  rtc.SetDateTimeCallbackConfiguration(5000);

  WriteLn('Press key to exit');
  ReadLn;
  ipcon.Destroy; { Calls ipcon.Disconnect internally }
end;

begin
  e := TExample.Create;
  e.Execute;
  e.Destroy;
end.

API

Since Delphi does not support multiple return values directly, we use the out keyword to return multiple values from a function.

All functions and procedures listed below are thread-safe.

Basic Functions

constructor TBrickletRealTimeClockV2.Create(const uid: string; ipcon: TIPConnection)

Creates an object with the unique device ID uid:

realTimeClockV2 := TBrickletRealTimeClockV2.Create('YOUR_DEVICE_UID', ipcon);

This object can then be used after the IP Connection is connected (see examples above).

procedure TBrickletRealTimeClockV2.SetDateTime(const year: word; const month: byte; const day: byte; const hour: byte; const minute: byte; const second: byte; const centisecond: byte; const weekday: byte)

Sets the current date (including weekday) and the current time with hundredths of a second resolution.

Possible value ranges:

  • Year: 2000 to 2099
  • Month: 1 to 12 (January to December)
  • Day: 1 to 31
  • Hour: 0 to 23
  • Minute: 0 to 59
  • Second: 0 to 59
  • Centisecond: 0 to 99
  • Weekday: 1 to 7 (Monday to Sunday)

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:

  • BRICKLET_REAL_TIME_CLOCK_V2_WEEKDAY_MONDAY = 1
  • BRICKLET_REAL_TIME_CLOCK_V2_WEEKDAY_TUESDAY = 2
  • BRICKLET_REAL_TIME_CLOCK_V2_WEEKDAY_WEDNESDAY = 3
  • BRICKLET_REAL_TIME_CLOCK_V2_WEEKDAY_THURSDAY = 4
  • BRICKLET_REAL_TIME_CLOCK_V2_WEEKDAY_FRIDAY = 5
  • BRICKLET_REAL_TIME_CLOCK_V2_WEEKDAY_SATURDAY = 6
  • BRICKLET_REAL_TIME_CLOCK_V2_WEEKDAY_SUNDAY = 7
procedure TBrickletRealTimeClockV2.GetDateTime(out year: word; out month: byte; out day: byte; out hour: byte; out minute: byte; out second: byte; out centisecond: byte; out weekday: byte; out timestamp: int64)

Returns the current date (including weekday) and the current time of the real-time clock with hundredths of a second resolution.

The timestamp represents the current date and the the current time of the real-time clock converted to milliseconds.

The following constants are available for this function:

  • BRICKLET_REAL_TIME_CLOCK_V2_WEEKDAY_MONDAY = 1
  • BRICKLET_REAL_TIME_CLOCK_V2_WEEKDAY_TUESDAY = 2
  • BRICKLET_REAL_TIME_CLOCK_V2_WEEKDAY_WEDNESDAY = 3
  • BRICKLET_REAL_TIME_CLOCK_V2_WEEKDAY_THURSDAY = 4
  • BRICKLET_REAL_TIME_CLOCK_V2_WEEKDAY_FRIDAY = 5
  • BRICKLET_REAL_TIME_CLOCK_V2_WEEKDAY_SATURDAY = 6
  • BRICKLET_REAL_TIME_CLOCK_V2_WEEKDAY_SUNDAY = 7
function TBrickletRealTimeClockV2.GetTimestamp: int64

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.

Advanced Functions

procedure TBrickletRealTimeClockV2.SetOffset(const offset: shortint)

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.

function TBrickletRealTimeClockV2.GetOffset: shortint

Returns the offset as set by SetOffset.

function TBrickletRealTimeClockV2.GetAPIVersion: array [0..2] of byte

Returns the version of the API definition (major, minor, revision) 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.

function TBrickletRealTimeClockV2.GetResponseExpected(const functionId: byte): boolean

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 send and errors are silently ignored, because they cannot be detected.

See SetResponseExpected for the list of function ID constants available for this function.

procedure TBrickletRealTimeClockV2.SetResponseExpected(const functionId: byte; const responseExpected: boolean)

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 send and errors are silently ignored, because they cannot be detected.

The following function ID constants are available for this function:

  • BRICKLET_REAL_TIME_CLOCK_V2_FUNCTION_SET_DATE_TIME = 1
  • BRICKLET_REAL_TIME_CLOCK_V2_FUNCTION_SET_OFFSET = 4
  • BRICKLET_REAL_TIME_CLOCK_V2_FUNCTION_SET_DATE_TIME_CALLBACK_CONFIGURATION = 6
  • BRICKLET_REAL_TIME_CLOCK_V2_FUNCTION_SET_ALARM = 8
  • BRICKLET_REAL_TIME_CLOCK_V2_FUNCTION_SET_WRITE_FIRMWARE_POINTER = 237
  • BRICKLET_REAL_TIME_CLOCK_V2_FUNCTION_SET_STATUS_LED_CONFIG = 239
  • BRICKLET_REAL_TIME_CLOCK_V2_FUNCTION_RESET = 243
  • BRICKLET_REAL_TIME_CLOCK_V2_FUNCTION_WRITE_UID = 248
procedure TBrickletRealTimeClockV2.SetResponseExpectedAll(const responseExpected: boolean)

Changes the response expected flag for all setter and callback configuration functions of this device at once.

procedure TBrickletRealTimeClockV2.GetSPITFPErrorCount(out errorCountAckChecksum: longword; out errorCountMessageChecksum: longword; out errorCountFrame: longword; out errorCountOverflow: longword)

Returns the error count for the communication between Brick and Bricklet.

The errors are divided into

  • ACK checksum errors,
  • message checksum errors,
  • framing errors and
  • overflow errors.

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.

function TBrickletRealTimeClockV2.SetBootloaderMode(const mode: byte): byte

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:

  • BRICKLET_REAL_TIME_CLOCK_V2_BOOTLOADER_MODE_BOOTLOADER = 0
  • BRICKLET_REAL_TIME_CLOCK_V2_BOOTLOADER_MODE_FIRMWARE = 1
  • BRICKLET_REAL_TIME_CLOCK_V2_BOOTLOADER_MODE_BOOTLOADER_WAIT_FOR_REBOOT = 2
  • BRICKLET_REAL_TIME_CLOCK_V2_BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_REBOOT = 3
  • BRICKLET_REAL_TIME_CLOCK_V2_BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_ERASE_AND_REBOOT = 4
  • BRICKLET_REAL_TIME_CLOCK_V2_BOOTLOADER_STATUS_OK = 0
  • BRICKLET_REAL_TIME_CLOCK_V2_BOOTLOADER_STATUS_INVALID_MODE = 1
  • BRICKLET_REAL_TIME_CLOCK_V2_BOOTLOADER_STATUS_NO_CHANGE = 2
  • BRICKLET_REAL_TIME_CLOCK_V2_BOOTLOADER_STATUS_ENTRY_FUNCTION_NOT_PRESENT = 3
  • BRICKLET_REAL_TIME_CLOCK_V2_BOOTLOADER_STATUS_DEVICE_IDENTIFIER_INCORRECT = 4
  • BRICKLET_REAL_TIME_CLOCK_V2_BOOTLOADER_STATUS_CRC_MISMATCH = 5
function TBrickletRealTimeClockV2.GetBootloaderMode: byte

Returns the current bootloader mode, see SetBootloaderMode.

The following constants are available for this function:

  • BRICKLET_REAL_TIME_CLOCK_V2_BOOTLOADER_MODE_BOOTLOADER = 0
  • BRICKLET_REAL_TIME_CLOCK_V2_BOOTLOADER_MODE_FIRMWARE = 1
  • BRICKLET_REAL_TIME_CLOCK_V2_BOOTLOADER_MODE_BOOTLOADER_WAIT_FOR_REBOOT = 2
  • BRICKLET_REAL_TIME_CLOCK_V2_BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_REBOOT = 3
  • BRICKLET_REAL_TIME_CLOCK_V2_BOOTLOADER_MODE_FIRMWARE_WAIT_FOR_ERASE_AND_REBOOT = 4
procedure TBrickletRealTimeClockV2.SetWriteFirmwarePointer(const pointer: longword)

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.

function TBrickletRealTimeClockV2.WriteFirmware(const data: array [0..63] of byte): byte

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.

procedure TBrickletRealTimeClockV2.SetStatusLEDConfig(const config: byte)

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:

  • BRICKLET_REAL_TIME_CLOCK_V2_STATUS_LED_CONFIG_OFF = 0
  • BRICKLET_REAL_TIME_CLOCK_V2_STATUS_LED_CONFIG_ON = 1
  • BRICKLET_REAL_TIME_CLOCK_V2_STATUS_LED_CONFIG_SHOW_HEARTBEAT = 2
  • BRICKLET_REAL_TIME_CLOCK_V2_STATUS_LED_CONFIG_SHOW_STATUS = 3
function TBrickletRealTimeClockV2.GetStatusLEDConfig: byte

Returns the configuration as set by SetStatusLEDConfig

The following constants are available for this function:

  • BRICKLET_REAL_TIME_CLOCK_V2_STATUS_LED_CONFIG_OFF = 0
  • BRICKLET_REAL_TIME_CLOCK_V2_STATUS_LED_CONFIG_ON = 1
  • BRICKLET_REAL_TIME_CLOCK_V2_STATUS_LED_CONFIG_SHOW_HEARTBEAT = 2
  • BRICKLET_REAL_TIME_CLOCK_V2_STATUS_LED_CONFIG_SHOW_STATUS = 3
function TBrickletRealTimeClockV2.GetChipTemperature: smallint

Returns the temperature in °C 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.

procedure TBrickletRealTimeClockV2.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!

procedure TBrickletRealTimeClockV2.WriteUID(const uid: longword)

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.

function TBrickletRealTimeClockV2.ReadUID: longword

Returns the current UID as an integer. Encode as Base58 to get the usual string version.

procedure TBrickletRealTimeClockV2.GetIdentity(out uid: string; out connectedUid: string; out position: char; out hardwareVersion: array [0..2] of byte; out firmwareVersion: array [0..2] of byte; out deviceIdentifier: word)

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' or 'd'.

The device identifier numbers can be found here. There is also a constant for the device identifier of this Bricklet.

Callback Configuration Functions

procedure TBrickletRealTimeClockV2.SetDateTimeCallbackConfiguration(const period: longword)

Sets the period in ms with which the OnDateTime callback is triggered periodically. A value of 0 turns the callback off.

The default value is 0.

function TBrickletRealTimeClockV2.GetDateTimeCallbackConfiguration: longword

Returns the period as set by SetDateTimeCallbackConfiguration.

procedure TBrickletRealTimeClockV2.SetAlarm(const month: shortint; const day: shortint; const hour: shortint; const minute: shortint; const second: shortint; const weekday: shortint; const interval: longint)

Configures a repeatable alarm. The OnAlarm 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:

  • BRICKLET_REAL_TIME_CLOCK_V2_ALARM_MATCH_DISABLED = -1
  • BRICKLET_REAL_TIME_CLOCK_V2_ALARM_INTERVAL_DISABLED = -1
procedure TBrickletRealTimeClockV2.GetAlarm(out month: shortint; out day: shortint; out hour: shortint; out minute: shortint; out second: shortint; out weekday: shortint; out interval: longint)

Returns the alarm configuration as set by SetAlarm.

The following constants are available for this function:

  • BRICKLET_REAL_TIME_CLOCK_V2_ALARM_MATCH_DISABLED = -1
  • BRICKLET_REAL_TIME_CLOCK_V2_ALARM_INTERVAL_DISABLED = -1

Callbacks

Callbacks can be registered to receive time critical or recurring data from the device. The registration is done by assigning a procedure to an callback property of the device object:

procedure TExample.MyCallback(sender: TBrickletRealTimeClockV2; const param: word);
begin
  WriteLn(param);
end;

realTimeClockV2.OnExample := {$ifdef FPC}@{$endif}example.MyCallback;

The available callback property and their type of parameters 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.

property TBrickletRealTimeClockV2.OnDateTime
procedure(sender: TBrickletRealTimeClockV2; const year: word; const month: byte; const day: byte; const hour: byte; const minute: byte; const second: byte; const centisecond: byte; const weekday: byte; const timestamp: int64) of object;

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:

  • BRICKLET_REAL_TIME_CLOCK_V2_WEEKDAY_MONDAY = 1
  • BRICKLET_REAL_TIME_CLOCK_V2_WEEKDAY_TUESDAY = 2
  • BRICKLET_REAL_TIME_CLOCK_V2_WEEKDAY_WEDNESDAY = 3
  • BRICKLET_REAL_TIME_CLOCK_V2_WEEKDAY_THURSDAY = 4
  • BRICKLET_REAL_TIME_CLOCK_V2_WEEKDAY_FRIDAY = 5
  • BRICKLET_REAL_TIME_CLOCK_V2_WEEKDAY_SATURDAY = 6
  • BRICKLET_REAL_TIME_CLOCK_V2_WEEKDAY_SUNDAY = 7
property TBrickletRealTimeClockV2.OnAlarm
procedure(sender: TBrickletRealTimeClockV2; const year: word; const month: byte; const day: byte; const hour: byte; const minute: byte; const second: byte; const centisecond: byte; const weekday: byte; const timestamp: int64) of 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.

The following constants are available for this function:

  • BRICKLET_REAL_TIME_CLOCK_V2_WEEKDAY_MONDAY = 1
  • BRICKLET_REAL_TIME_CLOCK_V2_WEEKDAY_TUESDAY = 2
  • BRICKLET_REAL_TIME_CLOCK_V2_WEEKDAY_WEDNESDAY = 3
  • BRICKLET_REAL_TIME_CLOCK_V2_WEEKDAY_THURSDAY = 4
  • BRICKLET_REAL_TIME_CLOCK_V2_WEEKDAY_FRIDAY = 5
  • BRICKLET_REAL_TIME_CLOCK_V2_WEEKDAY_SATURDAY = 6
  • BRICKLET_REAL_TIME_CLOCK_V2_WEEKDAY_SUNDAY = 7

Constants

const BRICKLET_REAL_TIME_CLOCK_V2_DEVICE_IDENTIFIER

This constant is used to identify a Real-Time Clock Bricklet 2.0.

The GetIdentity function and the OnEnumerate callback of the IP Connection have a deviceIdentifier parameter to specify the Brick's or Bricklet's type.

const BRICKLET_REAL_TIME_CLOCK_V2_DEVICE_DISPLAY_NAME

This constant represents the human readable name of a Real-Time Clock Bricklet 2.0.