pulses_get() locks at low frequencies

[robert-hh]

pulses_get() gets into a kind of lock state, if pulses with a period of > 20000us are applied and the time out was set to an appropriate large value, like 30000. It does not simply return wrong values, but from one "overflow" event on it returns the value pair 19879, 0 irrespective of the signal applied to the input. Only hard reset fixes that. Possible fix:
In line 107 of modpycom.c set:
rmt_rx.rx_config.idle_threshold = 0xffff;
That results in a more robust behavior. For pulses of > 32768 us a wrong value will be reported, but after returning to shorter pulses, they will be reported correctly.

[robert-hh]

I raised a PR for that.