Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

disable the duty circle. #8

Closed
chrisj8727 opened this issue Sep 7, 2016 · 3 comments
Closed

disable the duty circle. #8

chrisj8727 opened this issue Sep 7, 2016 · 3 comments

Comments

@chrisj8727
Copy link

it is possible to disable the duty circle.
This is annoying especially during testing.
thanks in advance chris

@autopower
Copy link
Owner

What you mean by duty circle?

@chrisj8727
Copy link
Author

The duty cycle describes a statutory limit of the airtime of devices in the
868 MHz range. The objective of this scheme is to the function of all in
the 868 MHz range to ensure working devices. In the frequency range used by
us, the maximum transmission time of each unit 868 MHz is 1% of one hour
(so 36 seconds in an hour). The devices may be used in achieving the
1%-limit no longer send, until the time limit is over.

chris

2016-09-21 6:42 GMT+02:00 Michal Cheben notifications@github.com:

What you mean by duty circle?


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#8 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AO_CMQc8uD4-ZwYoTT-8QV4MlwhSOhHaks5qsLWbgaJpZM4J2y0P
.

@autopower
Copy link
Owner

Thermeq3 does not manipulate communication between device and cube in any way, so informatiom stored "in cube" is based on normal transmission between device and cube.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants