Closed OK2MOP closed 2 months ago
Hi OK2MOP, thanks a lot for the tips, if you want you can do a pull request with the fix of the README. Thanks Renzo
Thanks for detailed information OK2MOP also same issue happening E32 lora modüles. Old version and new versions cannot communicate each other until up to air rate 9.6kbps.
Hello, In the photo above, I have two LoRa modules: one is a standard E22, and the other is an E22 V2. I designed a board with two RP2040 processors. I can program the board with the standard E22 through serial print, but when I try to program the one with the E22 V2, it only returns "FFFFFFF". I am using the same code to program both. Can you help me with this issue?
Hello, this is not a bug in library itself, just a warning and maybe suggestion for enhancement (adding the check or documentation). The new V2.1 modules (PCB versions 10498-V1.1 and 10497-V1.0) - and after confirming from EBYTE also the V2.0 modules - do not correctly set up speeds 0.3k and 1k2 and silently ignore the setting (they probably stay at the 2k4 speed like E220s). It seems the SX127x has been replaced in them by LLCC68 inside, which does not support spreading factors needed by these modes.
They can be identified by querying register 0x82 (C1 82 01), which returns 0x40 instead of 0x10 or 0x11 seen in previous versions. Older modules set to these speeds cannot communicate with the V2.1 ones on these speeds and vice versa.
I had this just confirmed from EBYTE, my guess is that they are in fact re-labeled E220-400T30D/E220-900T30D modules with modified interface to observe E22 communication protocol and register map
So my suggestion is adding a warning to README.md concerning those speeds.