Home › Forums › The libraries hosted on the site › EByte LoRa e22 UART devices sx1262/sx1268 › Lora hat (raspberry) waveshare e22-900ts
Tagged: E22-900t22s
- This topic has 6 replies, 2 voices, and was last updated 11 months ago by
Renzo Mischianti.
-
AuthorPosts
-
-
12 June 2024 at 09:33 #30776
Hi everybody!
I’m stuck with basic communication on a couple of modules of the same type. I’ve bought them from Amazon and i’ve installed in stacked way to raspberry boards through 40 pin header. I control M0, M1 and read AUX by software. The boards are few cm far each other and antenna is that one provided.
The configuration seems ok from interface point of view, they responds as the manual says (downloaded from eebyte page).
Configuration is:
Module 1:(hw v2, sw tool says v1)
Address 0x0001, NetID 0x0F, Fixed point transmission, ch: 0x11. The remaining configurations are left by default.Module 2:(hw2 v2, sw tool says v1)
Address 0x0002, NetID 0x0F, Fixed point transmission, ch: 0x11. The remaining configurations are left by default.I tried several device configurations each one compatible with the communication, even connecting them with pc and software tool provided by waveshare.
In any case i cannot establish communication. Im not able to send a byte neither.
Anyone in the same situation?
Should i rewire modules to access spi directly to sx1262?Thank you in Advance, any help would be appreciated.
Ciao Enrico
-
12 June 2024 at 10:46 #30778
Hi ERicci,
To start a fixed-point communication, you need to configure the device properly.Please post your configuration sketch and the sender/receiver one.
First of all, I advise you to try a simple get configuration and post an image of the connection to the board.
Bye Renzo -
12 June 2024 at 11:01 #30779
And you use this library???
Bye RM -
12 June 2024 at 11:56 #30780
M0, M1 are managed by software, the switch are tied in such a way to have null modem connection with raspberry, accordingly to schematic in waveshare web page.
When configuration mode is active i set GPIO 27 output high and GPIO 22 output low
According to manual attached i send the following binary (non ASCII) bytes to the modules:1)
C0000900010F630011430000
the module reply with
C1000900010F6300114300002)
C0000900020F630011430000
the module reply with
C1000900020F630011430000When i wish to communicate i set GPIO 27 and GPIO 22 output low.
I don’t think it’s necessary the connection diagram since the module responds accordingly the manual at par. 7.1. Anyway the board is installed close to raspberry and connected through 40 pin header as said above.
Let me know if you need further info.
P.S.
i don’t even use python for my project. i started with C -
13 June 2024 at 08:42 #30784
Hi,
If you correctly set the M0 and M1, the configuration for fixed transmission with relative addresses for the sender and receiver is okay. If you send the correct packet to address the message to the other device, it must work.
If It does not work, you do something wrong in one of these steps:
– connection schema
– configuration of receiver and sender
– code of the transmitter
– code of the receiver
Bye Renzo-
This reply was modified 11 months, 1 week ago by
Renzo Mischianti.
-
This reply was modified 11 months, 1 week ago by
-
16 June 2024 at 09:53 #30810
Configuration
1)
C0000900010F630011430000
the module reply with
C1000900010F6300114300002)
C0000900020F630011430000
the module reply with
C1000900020F630011430000Test:
Module 1 sends the following
00020FAAAA
Module 2 does not receive anything.Configuration:
1)
C00009000000930011430000
the module reply with
C100090000009300114300002)
C00009000000930011430000
the module reply with
C10009000000930011430000Module 1 sends the following,
000000AAAA
Module 2 receives
AAAAAnyway, this is the risk to buy cheaper devices.
Im Happy the same, distance range is satisfactory.Thank you for your support.
-
17 June 2024 at 08:30 #30812
Hi,
I can’t check the configuration and the wiring without the library that translates the byte in instruction, but It’s very improbable that the problem is the module.But the configuration packet is 6 bytes so
C0 00 00 62 00 12
The sending packet for the address and channel you use seems incorrect.Try using the library to simplify all the processes and reduce the errors; if it works, try replicating the byte array packet.
Bye Renzo
-
-
AuthorPosts
- You must be logged in to reply to this topic.