- This topic has 4 replies, 3 voices, and was last updated 2 months ago by
.
-
Posts
-
-
Hello Renzo!
Ebyte stopped manufacturing E32 915T modules. From what I understand now for that frequency I should use E32 900T, which ranges from 862 to 928Mhz.
Already got some 915T modules working perfectly. Now I’m trying to communicate the 900T with the 915T.
I’m using 916Mhz in 915T modules with
#define FREQUENCY_915
#define CHANNEL 0x10In the 900T modules I am using
#define FREQUENCY_868
#define CHANNEL 0x36.
serial log.
HEAD: 11000000 192 C0
AddH: 0
AddL: 3
Chan : 54 -> 916MHzAs can be seen theoretically I’m on the same channel with the 2 modules, but I can’t communicate between them.
Question, can the modules interoperate in the way I’m looking to do with your library?
thank you for your library.
-
hello,
I noticed that an update has been uploaded in the library for 1.5.11 including #elif defined(FREQUENCY_900)
#define OPERATING_FREQUENCY 850.
I did some tests with this model still trying to communicate 900T with 915T.
I continue to keep the 915T module with the codes working, however the 900T changed the channel to 0x42 trying to enter 916Mz, the frequency that the 915T is operating. In the serial I have a return that the module would be at 916Mz.
HEAD: 11000000 192 C0
AddH: 0
AddL: 3
Chan : 66 -> 916MHzthis way I still can’t communicate 915T with 900T.
Is there any other test I can run to get communication between modules?
thanks -
-
-
Hi Edge,
to show the frequency as you need, you must put one of these define before the library include.#define FREQUENCY_868 #include "LoRa_E32.h"Bye RM
-
- You must be logged in to reply to this topic.
