Scheduling in <=16.1 R10 may crash Connexion

An issue was discovered which causes Connexion to crash under the following conditions:

1. Utilize a device which supports a polling period as well as scheduling (Reader devices).

2. Use Days & Hours scheduling mode

3. Enable all days and hours

4. Use a polling period equal to or greater than one hour.

Please disable scheduling (as day & hour scheduling which includes all periods is functionally the same), or, create a schedule with some blocks excluded.

Versions after 16.1R10 will throw an invalid configuration exception if days & hours is selected with all blocks included.