Error message: Module MAX: CUL "My-MAX-CUL": Warning: Too short packet received: LOVF

English Forums Hardware
#1

I see this error very often, and I think it’s hindering messages getting to my thermostats. Any idea how to fix this?

4/15/16 18:26:00.677 Module MAX: CUL “My-MAX-CUL”: Warning: Too short packet received: LOVF

04/15/16 18:26:00.678 RPC client: Info: Calling RPC method “error” on server 192.168.1.109.
04/15/16 18:26:00.679 Module MAX: CUL “My-MAX-CUL”: Warning: Too short packet received: LOVF

04/15/16 18:26:00.681 RPC client: Info: Calling RPC method “error” on server 192.168.1.109.
04/15/16 18:26:03.674 Module MAX: CUL “My-MAX-CUL”: Info: Sending (My-MAX-CUL, WOR: yes): 193C0010FD72EC12DE0F00001920550845204520452045204520
04/15/16 18:26:03.678 Module MAX: CUL “My-MAX-CUL”: Warning: Too short packet received: LOVF

04/15/16 18:26:03.679 RPC client: Info: Calling RPC method “error” on server 192.168.1.109.
04/15/16 18:26:09.627 Module MAX: CUL “My-MAX-CUL”: Info: Sending (My-MAX-CUL, WOR: yes): 191E0010FD72EC12DF070006143C505414785090512045204520
04/15/16 18:26:09.630 Module MAX: CUL “My-MAX-CUL”: Warning: Too short packet received: LOVF

04/15/16 18:26:09.631 RPC client: Info: Calling RPC method “error” on server 192.168.1.109.
04/15/16 18:26:12.625 Module MAX: CUL “My-MAX-CUL”: Info: Sending (My-MAX-CUL, WOR: yes): 19060010FD72EC137FB700035B20546C44CC5514452045204520
04/15/16 18:26:12.629 Module MAX: CUL “My-MAX-CUL”: Warning: Too short packet received: LOVF

04/15/16 18:26:12.630 RPC client: Info: Calling RPC method “error” on server 192.168.1.109.
04/15/16 18:26:12.667 Module MAX: CUL “My-MAX-CUL”: Info: Sending (My-MAX-CUL, WOR: yes): 191E0010FD72EC12DF070006143C505414785090512045204520
04/15/16 18:26:12.669 Module MAX: CUL “My-MAX-CUL”: Warning: Too short packet received: LOVF

04/15/16 18:26:12.669 RPC client: Info: Calling RPC method “error” on server 192.168.1.109.
04/15/16 18:26:15.624 Module MAX: CUL “My-MAX-CUL”: Info: Sending (My-MAX-CUL, WOR: yes): 193C0010FD72EC12DE0F00001920550845204520452045204520
04/15/16 18:26:15.628 Module MAX: CUL “My-MAX-CUL”: Warning: Too short packet received: LOVF

04/15/16 18:26:15.628 RPC client: Info: Calling RPC method “error” on server 192.168.1.109.
04/15/16 18:26:15.665 Module MAX: CUL “My-MAX-CUL”: Info: Sending (My-MAX-CUL, WOR: yes): 19060010FD72EC137FB700035B20546C44CC5514452045204520
04/15/16 18:26:15.667 Module MAX: CUL “My-MAX-CUL”: Warning: Too short packet received: LOVF

04/15/16 18:26:15.667 Module MAX: CUL “My-MAX-CUL”: Info: Sending (My-MAX-CUL, WOR: yes): 191E0010FD72EC12DF070006143C505414785090512045204520
04/15/16 18:26:15.668 RPC client: Info: Calling RPC method “error” on server 192.168.1.109.
04/15/16 18:26:15.670 Module MAX: CUL “My-MAX-CUL”: Warning: Too short packet received: LOVF

04/15/16 18:26:15.671 RPC client: Info: Calling RPC method “error” on server 192.168.1.109.
04/15/16 18:26:18.664 Module MAX: CUL “My-MAX-CUL”: Info: Sending (My-MAX-CUL, WOR: yes): 193C0010FD72EC12DE0F00001920550845204520452045204520
04/15/16 18:26:18.666 Module MAX: CUL “My-MAX-CUL”: Info: Sending (My-MAX-CUL, WOR: yes): 19060010FD72EC137FB700035B20546C44CC5514452045204520
04/15/16 18:26:18.668 Module MAX: CUL “My-MAX-CUL”: Warning: Too short packet received: LOVF

#2

Update: This seems to happen when I send any putParamset, probably after the 2nd message. Even if I haven’t sent anything for a number of days.

#3

Hey,

LOVF means, the duty cycle limit is reached. You can only send very few MAX! packets until this happens. The main problem is the long preamble of wake on radio packets (1 second). Alltogether any device is only allowed to send 1 % of an hour. That’s only 32 packets when every packet is a wake on radio packet (most packets are). The CUL splits the hour in four parts, so you can send about 8 packets per 15 minutes. So there are only two legal options:

[ul]
[li] Use a second CUL for some devices.[/li]
[li] Send less packets.[/li][/ul]

Cheers,

Sathya