FHEM > English Corner

CUL not enough credit

(1/2) > >>

kennybl:
Hello,

I am improving my app to control the MAX! heater thermostats and it sometimes works perfect.
The only problem is when i try to change the temperatures a few times after each other.

My log shows the not enough credit messages:


--- Code: ---2021.04.10 11:21:09 2: cm, CUL not enough credit! credit10ms is 32, but we need 110. Waiting 78 seconds. Currently 1 messages are waiting to be sent
2021.04.10 11:22:30 2: cm, CUL not enough credit! credit10ms is 3, but we need 110. Waiting 107 seconds. Currently 1 messages are waiting to be sent
2021.04.10 11:24:20 2: cm, CUL not enough credit! credit10ms is 3, but we need 110. Waiting 107 seconds. Currently 3 messages are waiting to be sent
2021.04.10 11:26:09 2: cm, CUL not enough credit! credit10ms is 3, but we need 113. Waiting 110 seconds. Currently 4 messages are waiting to be sent
2021.04.10 11:28:02 2: cm, CUL not enough credit! credit10ms is 3, but we need 110. Waiting 107 seconds. Currently 4 messages are waiting to be sent
2021.04.10 11:29:51 2: cm, CUL not enough credit! credit10ms is 3, but we need 110. Waiting 107 seconds. Currently 5 messages are waiting to be sent
2021.04.10 11:31:41 2: cm, CUL not enough credit! credit10ms is 3, but we need 110. Waiting 107 seconds. Currently 6 messages are waiting to be sent
2021.04.10 11:33:30 2: cm, CUL not enough credit! credit10ms is 3, but we need 110. Waiting 107 seconds. Currently 7 messages are waiting to be sent
2021.04.10 11:35:20 2: cm, CUL not enough credit! credit10ms is 3, but we need 110. Waiting 107 seconds. Currently 8 messages are waiting to be sent
2021.04.10 11:37:09 2: cm, CUL not enough credit! credit10ms is 3, but we need 110. Waiting 107 seconds. Currently 9 messages are waiting to be sent
2021.04.10 11:38:59 2: cm, CUL not enough credit! credit10ms is 3, but we need 110. Waiting 107 seconds. Currently 9 messages are waiting to be sent
2021.04.10 11:40:48 2: cm, CUL not enough credit! credit10ms is 3, but we need 110. Waiting 107 seconds. Currently 10 messages are waiting to be sent
--- Ende Code ---

In my code i check the desired temperature from my database. If that is not the same as the MAX thermostat, i try to update it to the desired temperature.
The problem is when the 2 temperatures are not the same and the credits are empty, my program keeps trying to change the desired temperatures on the radiator thermostats so i keep getting more and more requests.

Is there a better way to improve this, i saw this (https://blog.mjwconsult.co.uk/modifying-cul-firmware-to-increase-send-limit-for-eq3-max-heating-thermostats/) but i am not sure if this will work on an arduino (Devices/CUL is changed, i use Devices/NanoCul), and also i don't know if this is "legal"?

Thanks for the help



Update:

Also, to just change 1 desired temperature, the cul uses 100 credits, is this normal? It seems a lot but maybe it is normal

KölnSolar:

--- Zitat --- also i don't know if this is "legal"?
--- Ende Zitat ---
That is the problem: it isn't. At least in Germany.  :'(
If you don't care about the legal requirements, it is just the small software issue.  ;)

kennybl:
I am not sure how "bad" it would be, normally the temperatures are changed a few times a day but the problem is that when i change the temperatures a few times after each other (or different rooms at the same time) i get these problems.

Is it normal that changing 1 temperature costs 100 credits? I think the cul has 900 per minute? I don't fully understand the credits.
How can i change the code to accept more on the nanoCUL?

rudolfkoenig:

--- Zitat ---I think the cul has 900 per minute?
--- Ende Zitat ---
Nope, it is 900 per 15 Minutes (aka 900 Seconds), and it is decreased by one for each 10ms of transmission.

It is the 1% rule: a sender on this frequency range ist not allowed to transmit for more than 1% of the time, if it is not doing LBT (Listen before Talk). AFAIK the interval it is not specified, so it is not clear if the 1% is meant for one minute, hour, or day. I choose 900, as "shouting" for 9 seconds without a break seemed more than enough for me. Changing this number to a larger value is probably still legal, but it is more likely to cause problems if you are not "alone".

kennybl:
Okay, thank you for explaining. Is there a way to figure out how many credits are used for what process?
I can get the amount of remaining credits and i can check if the value is more than for example 100, i can request an update, otherwise wait. But i have no idea how i can check how many credits are needed for what change

Navigation

[0] Themen-Index

[#] Nächste Seite

Zur normalen Ansicht wechseln