# Ebyte E78-868LN22S

**URL:** <https://www.thethingsnetwork.org/forum/t/ebyte-e78-868ln22s/70144>\
**Category:** Hardware\
**Created:** [December 26, 2024, 1:06am UTC](https://www.thethingsnetwork.org/forum/t/ebyte-e78-868ln22s/70144 "2024-12-26T01:06:43Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![jochenstromberg](https://www.thethingsnetwork.org/forum/letter_avatar_proxy/v4/letter/j/c2a13f/32.png) [@jochenstromberg](https://www.thethingsnetwork.org/forum/u/jochenstromberg)\
**Post date:** [December 26, 2024, 1:06am UTC](https://www.thethingsnetwork.org/forum/t/ebyte-e78-868ln22s/70144/1 "2024-12-26T01:06:44Z")

</div>

Hi there,

i got some Ebyte E78-868LN22S SW Version 4.0, the datasheet seems to be older than the firmware…  
I tried to set it up in a german lorawan so 868MHz, in both methods OTAA / ABP. Nothing to see in my console for the device nor the gateway. the module doesn’t even draw more current when I await it to connect to gateway. I’ver the break out board USB version as well as the single chip with DIY breakout, same behviour.

So may question is, anybody had a successfull join and datatransfer with those modules?  
In addition i’ve a CDEBYTE E78-DTU(900LN22) which is working just fine.

Any suggestions anyone? Looking forward for some support, thanks in advance!!

BR Jochen

---

<div class="post-metadata">

**Author:** ![al1fch](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/al1fch/32/46861_2.png) [@al1fch](https://www.thethingsnetwork.org/forum/u/al1fch)\
**Post date:** [December 27, 2024, 9:44am UTC](https://www.thethingsnetwork.org/forum/t/ebyte-e78-868ln22s/70144/2 "2024-12-27T09:44:12Z")

</div>

HI jochenstromberg !

About two years ago I was successful with some E78 868LN22S modules in OTAA and ABP modes  
I live in France (868MHz) , my TTIG gateway is in the attic  
Modules came from EBYTE/CDEBYTE chop on Aliexpress  
No firmware changed for the inside ASR6501 chip

As I look to log notes I see that :

Device used LoRaWAN version 1.0.2, Regional Parameters 1.0.2 rev B  
AT+CGMM? reported E78-900M22S _(but E7868LN22S seen on module’s metal lid)_  
AT+CGMR? reported SF V1.0

Alain

---

<div class="post-metadata">

**Author:** ![jochenstromberg](https://www.thethingsnetwork.org/forum/letter_avatar_proxy/v4/letter/j/c2a13f/32.png) [@jochenstromberg](https://www.thethingsnetwork.org/forum/u/jochenstromberg)\
**Post date:** [December 27, 2024, 2:12pm UTC](https://www.thethingsnetwork.org/forum/t/ebyte-e78-868ln22s/70144/3 "2024-12-27T14:12:17Z")

</div>

Thanks to Alain,

That ist exact what i saw…

I have the USB breakouts with Firmware 4.0 which does Not Work. I got two stamps / barr Chips with FW 3.0 those Work. Furthermore i tested a DTU 78 steal cased device, using also an E78 868 ln 22s with a Special DTU Firmware in Alpha state, working properly also.

For gateway i am using a sensecap.

I requested some Firmware Infos at Ebyte, WE will See how their Support will react…

I am located in middle Germany near Frankfurt

---

<div class="post-metadata">

**Author:** ![jochenstromberg](https://www.thethingsnetwork.org/forum/letter_avatar_proxy/v4/letter/j/c2a13f/32.png) [@jochenstromberg](https://www.thethingsnetwork.org/forum/u/jochenstromberg)\
**Post date:** [December 28, 2024, 10:24am UTC](https://www.thethingsnetwork.org/forum/t/ebyte-e78-868ln22s/70144/4 "2024-12-28T10:24:14Z")

</div>

so some more details:  
not working version is:  
TX:AT+CGMM?  
RX:+CGMM=E78-868LN22S  
OK

TX:AT+CGMR?  
RX: +CGMR=v4.0  
OK

Working one in “steel metal case” E78-DTU:  
Lora 1.0.2/ 1.2.0.b  
TX:AT+CGMM?  
RX:+CGMM=E78-DTU  
OK

TX:AT+CGMR?  
RX:+CGMR=1.0.1-20221202\_Alpha  
OK

working one as “stamp / bare chip”:  
Lora 1.0.1 1.0.1  
TX:AT+CGMM?  
RX:+CGMM=E78-868LN22S  
OK

TX:AT+CGMR?  
RX:+CGMR=v3.0  
OK

---

<div class="post-metadata">

**Author:** ![descartes](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/descartes/32/47220_2.png) [@descartes](https://www.thethingsnetwork.org/forum/u/descartes)\
**Post date:** [December 28, 2024, 12:19pm UTC](https://www.thethingsnetwork.org/forum/t/ebyte-e78-868ln22s/70144/5 "2024-12-28T12:19:32Z")

</div>

Please format the log output with the \</\> - it makes it much easier to read.

As you’re able to get the serial output, perhaps consider showing us what actually happens which is the heart of the matter - show us the serial output of a join attempt.

---

<div class="post-metadata">

**Author:** ![snatch](https://www.thethingsnetwork.org/forum/letter_avatar_proxy/v4/letter/s/5fc32e/32.png) [@snatch](https://www.thethingsnetwork.org/forum/u/snatch)\
**Post date:** [January 13, 2025, 5:36am UTC](https://www.thethingsnetwork.org/forum/t/ebyte-e78-868ln22s/70144/6 "2025-01-13T05:36:51Z")

</div>

I’ve tested the E78-868LN22S(6601) in germany **without problems**.  
I checked the version of the module which gives me:

> +CGMI=Ebyte  
> +CGMM=E78-868LN22S  
> +CGMR= **v4.0**

-Low Power Consumption (CLPM) does not work at all got \<+CME ERROR:1\>  
-Downlink queue works for me not as expected

---

<div class="post-metadata">

**Author:** ![jochenstromberg](https://www.thethingsnetwork.org/forum/letter_avatar_proxy/v4/letter/j/c2a13f/32.png) [@jochenstromberg](https://www.thethingsnetwork.org/forum/u/jochenstromberg)\
**Post date:** [January 14, 2025, 7:03pm UTC](https://www.thethingsnetwork.org/forum/t/ebyte-e78-868ln22s/70144/7 "2025-01-14T19:03:25Z")

</div>

Hi Snatch,

that sounds quite promising. I got following parameters:

```auto
+CGMI=Ebyte
OK
+CGMM=E78-868LN22S
OK
+CGMR=v4.0
OK

```

So exactly the same, are there any other parameters you nedeed to set? Are you using it on an own PCB or on the preconfigurated USB Testboard?

Which device settings are you using in the TTN Console?

@descartes: sorry missed your answer, there is no further serial output:

```auto
AT+CJOIN=1,0,10,8
gives me (after some time) a:

OK
+CJOIN:FAIL

```

is there any hint getting more detailed information from the device?  
can’t find any reaction in the console of gateway or device…

In general I tested my gateway with several EByte devices as descripted above, even the chip familiy with FW Version 3 is working, I can’t catch the point what’s wrong here,.Even I’ve two identical USB Boards assembled by Ebyte and sourced from their webshop, so I don’t think they are faked or whatever…

Still looking forward finding the root cause.

BR Jochen

---

<div class="post-metadata">

**Author:** ![descartes](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/descartes/32/47220_2.png) [@descartes](https://www.thethingsnetwork.org/forum/u/descartes)\
**Post date:** [January 14, 2025, 11:14pm UTC](https://www.thethingsnetwork.org/forum/t/ebyte-e78-868ln22s/70144/8 "2025-01-14T23:14:22Z")

</div>

> [@jochenstromberg](#):
>
> is there any hint getting more detailed information from the device?

Not from me. I use eByte SX126x modules occasionally but I’m not a user of AT based modules.

> [@jochenstromberg](#):
>
> can’t find any reaction in the console of gateway or device…

Can you look on the gateway logs - the internal ‘what’s just happened’ bit - to see if anything is being heard by the gateway, even if it’s not passing the CRC check.

An OK join request that’s heard by the gateway would appear in the gateway console on TTN. So that’s the first step to solve. Maybe an antenna issue. Maybe the firmware is borked - can you downgrade to v3.

What do @ebyteiot have to say?

Given the cost of the modules, you may want to move on to something like the Seeed Wio-E5 based module.

---

<div class="post-metadata">

**Author:** ![snatch](https://www.thethingsnetwork.org/forum/letter_avatar_proxy/v4/letter/s/5fc32e/32.png) [@snatch](https://www.thethingsnetwork.org/forum/u/snatch)\
**Post date:** [January 20, 2025, 3:25pm UTC](https://www.thethingsnetwork.org/forum/t/ebyte-e78-868ln22s/70144/9 "2025-01-20T15:25:17Z")

</div>

If got standalone module and usb-testboard - both working.  
Modules are configured as described in manual from Ebyte.  
AT+CAPPEUI=\<you’re key\>  
AT+CDEVEUI=\<you’re key\>  
AT+CAPPKEY=\<you’re key\>  
AT+CCONFIRM=0  
AT+CCLASS=2  
AT+CULDLMODE=2  
AT+CSAVE  
AT+IREBOOT=0  
…  
Have you maybe swapped CAPPEUI with CDEVEUI? (That was my first fault ;))

---

<div class="post-metadata">

**Author:** ![jochenstromberg](https://www.thethingsnetwork.org/forum/letter_avatar_proxy/v4/letter/j/c2a13f/32.png) [@jochenstromberg](https://www.thethingsnetwork.org/forum/u/jochenstromberg)\
**Post date:** [January 21, 2025, 5:18pm UTC](https://www.thethingsnetwork.org/forum/t/ebyte-e78-868ln22s/70144/10 "2025-01-21T17:18:08Z")

</div>

Hi all,

thanks for your advices, tried once more, no progress made, double checked the correct usage of the parameters with Ebytes “DTU-78” config tool, not 100% perfect for this devices but at least the join credentials appear in the correct boxes.  
anything to set with those jumpers for VCC? What is about the stand by LED, @snatch any peripheral jumper wires used on the USB break out?

little bit lost, as the chip only solutions work as desired, the preassembled break out won’t…

I guess this is my last try, before i’ll try to resolder another chip onto the break out… See what’s happening then.

---

<div class="post-metadata">

**Author:** ![snatch](https://www.thethingsnetwork.org/forum/letter_avatar_proxy/v4/letter/s/5fc32e/32.png) [@snatch](https://www.thethingsnetwork.org/forum/u/snatch)\
**Post date:** [January 22, 2025, 5:19am UTC](https://www.thethingsnetwork.org/forum/t/ebyte-e78-868ln22s/70144/11 "2025-01-22T05:19:01Z")

</div>

The jumper is set to 3.3V and a red led is on when powered on and an antenna is always used.
