how to added fixed address and channel

[cyberumut]

how to added fixed address and channel ?

i need address & channel as in the picture

[nopnop2002]

Where is your drawing from?

I can't find it in the SX1276/77/78/79 datasheet.

[cyberumut]

ebyte modules Isn't this header structure global? targetAddr | TargetChannel | Data how can i apply this on sx1278

Where is your drawing from?

I can't find it in the SX1276/77/78/79 datasheet.

[nopnop2002]

Where can I get your documentation?

tell me the url.

this is LoRa Packet Structure

[cyberumut]

https://www.cdebyte.com/products/E22-400T30D/4#Downloads

check it manual .pdf

LoRa Packet Structure

[nopnop2002]

EBYTE's E22 module uses different frequencies depending on the channel.

you can use any frequency you like in menuconfig

[cyberumut]

module in hand is sx1278 ,not ebyte module I want to define address and channel on sx1278 how can i do ?

EBYTE's E22 module uses different frequencies depending on the channel.

you can use any frequency you like in menuconfig

[nopnop2002]

This diagram you showed is from EBYTE.

You're using EBYTE's SX1278, right?

[cyberumut]

no i dont using eybte module . I just want to set up addressing and channel structure like it

This diagram you showed is from EBYTE.

You're using EBYTE's SX1278, right?

[nopnop2002]

The LoRa specification does not have channels or addresses.

EBYTE modules channel is same as frequency

For modules other than EBYTE, change the frequency if you use the concept of channels.

I recommend reading the SX1278 datasheet.

[cyberumut]

If we add such a structure to the header. I think it can work if we parse the header on the other device or i selected channel 4
Frequency= 410.125 + CH 1M
410.125+ 41M using channel 414.125 example . it needs to be calculated

The LoRa specification does not have channels or addresses.

EBYTE modules channel is same as frequency

For modules other than EBYTE, change the frequency if you use the concept of channels.

[nopnop2002]

I do not understand your content.

The LoRa packet structure is the following structure and Header is optional.

The LoRa packet structure and header content are strictly specified and cannot be changed.

Header
Depending upon the chosen mode of operation two types of header are available. The header type is selected by the
ImplicitHeaderModeOn bit found within the RegModemConfig1 register.

Explicit Header Mode
This is the default mode of operation. Here the header provides information on the payload, namely:
 The payload length in bytes.
 The forward error correction code rate
 The presence of an optional 16-bits CRC for the payload.
The header is transmitted with maximum error correction code (4/8). It also has its own CRC to allow the receiver to
discard invalid headers.

Implicit Header Mode
In certain scenarios, where the payload, coding rate and CRC presence are fixed or known in advance, it may be
advantageous to reduce transmission time by invoking implicit header mode. In this mode the header is removed from the
packet. In this case the payload length, error coding rate and presence of the payload CRC must be manually configured
on both sides of the radio link.
Note With SF = 6 selected, implicit header mode is the only mode of operation possible.

[nopnop2002]

EBYTE LoRa modules and non-EBYTE LoRa modules may not be able to communicate with each other.

This is because EBYTE has the concept of addresses, but LoRa modules other than EBYTE do not.

Presumably the EBYTE address is sent as part of the LoRa payload. This is an EBYTE-specific payload.

EBYTE-specific payloads cannot be interpreted correctly by non-EBYTE LoRa modules.

[cyberumut]

i got it now thank u bro

EBYTE LoRa modules and non-EBYTE LoRa modules may not be able to communicate with each other.

This is because EBYTE has the concept of addresses, but LoRa modules other than EBYTE do not.

Presumably the EBYTE address is sent as part of the LoRa payload. This is an EBYTE-specific payload.

EBYTE-specific payloads cannot be interpreted correctly by non-EBYTE LoRa modules.