-
Notifications
You must be signed in to change notification settings - Fork 10
Adding a function to register a callback function for retrieving a global timestamp #55
Conversation
This comment has been minimized.
This comment has been minimized.
990c261
to
6433958
Compare
This comment has been minimized.
This comment has been minimized.
6433958
to
fc6c29f
Compare
Codecov Report
@@ Coverage Diff @@
## master #55 +/- ##
==========================================
- Coverage 95.73% 95.41% -0.32%
==========================================
Files 24 24
Lines 867 872 +5
==========================================
+ Hits 830 832 +2
- Misses 37 40 +3
Continue to review full report at Codecov.
|
…obal timestamp. This is necessary because right now we are relying on the RTC within the SAMD MCU which is instantiated (RTCZero) within the ArduinoIoTCloud library and reference within ArduinoCloudThing via extern devlaration. Due to the extern binding this is a very brittle dependency which can be easily destroyed, it is therefore better to explicitly register a function which provides the time (this can be serviced by the TimeService class available in ArduinoIoTCloud
fc6c29f
to
85078a0
Compare
Codecov Report
@@ Coverage Diff @@
## master #55 +/- ##
==========================================
- Coverage 95.73% 95.41% -0.32%
==========================================
Files 24 24
Lines 867 872 +5
==========================================
+ Hits 830 832 +2
- Misses 37 40 +3 Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## master #55 +/- ##
==========================================
- Coverage 95.73% 95.41% -0.32%
==========================================
Files 24 24
Lines 867 872 +5
==========================================
+ Hits 830 832 +2
- Misses 37 40 +3
Continue to review full report at Codecov.
|
…poch type timestamp In #55 the possibility for retrieving a epoch type timestamp via a registered callback function has been introduced, the changes in arduino-libraries/ArduinoIoTCloud#93 register such a function which allows us to to remove the hidden dependency to RTCZero altogether
…poch type timestamp In #55 the possibility for retrieving a epoch type timestamp via a registered callback function has been introduced, the changes in arduino-libraries/ArduinoIoTCloud#93 register such a function which allows us to to remove the hidden dependency to RTCZero altogether
…poch type timestamp In #55 the possibility for retrieving a epoch type timestamp via a registered callback function has been introduced, the changes in arduino-libraries/ArduinoIoTCloud#93 register such a function which allows us to to remove the hidden dependency to RTCZero altogether
…poch type timestamp In arduino-libraries/ArduinoCloudThing#55 the possibility for retrieving a epoch type timestamp via a registered callback function has been introduced, the changes in #93 register such a function which allows us to to remove the hidden dependency to RTCZero altogether
This is necessary because right now we are relying on the RTC within the SAMD MCU which is instantiated (RTCZero) within the ArduinoIoTCloud library and reference within ArduinoCloudThing via extern devlaration. Due to the extern binding this is a very brittle dependency which can be easily destroyed, it is therefore better to explicitly register a function which provides the time (this can be serviced by the TimeService class available in ArduinoIoTCloud.
Successfully tested on PROD with