That is strange - I guess there should be a check in the module for packet size (although I thought it automatically split longer packets into several short ones).
It has been suggested that you could add a 0.1uF tant/ceramic capacitor across the power pins of the NRF module to help with unreliability - but I don't think that is the problem here - the modules have a CRC check I believe, so if you're receiving bad data it's either getting it from another NRF module (not yours), or the wrong data is being sent in the first place.
Is it possible that you're not sending strings, but arrays? I imagine the NRF module could get a bit confused there as I think it is designed to only handle strings.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
That is strange - I guess there should be a check in the module for packet size (although I thought it automatically split longer packets into several short ones).
It has been suggested that you could add a 0.1uF tant/ceramic capacitor across the power pins of the NRF module to help with unreliability - but I don't think that is the problem here - the modules have a CRC check I believe, so if you're receiving bad data it's either getting it from another NRF module (not yours), or the wrong data is being sent in the first place.
Is it possible that you're not sending strings, but arrays? I imagine the NRF module could get a bit confused there as I think it is designed to only handle strings.