E32 and ESP32 not working, but on Arduino it`s OK – Same Code

[phnahes]

Hello, how are you?

I bought some 433Mhz / 1W E32 modules, at two different times.

The new ones, for some reason, cause the controller to crash, unlike the previous ones that work perfectly, I tested them in different ways and on different boards, nothing makes them work.

I used the example codes from the library itself and I can’t get it to work, all of this when connected to the ESP32, because when I connect it to the Arduino, everything works correctly.

An interesting observation is that I have an ESP32, with an identical e32 board, and everything works, I exchanged between the new E32 and the old E32, and nothing works, it seems to me that there is something with their hardware, or firmware, I don’t know. .

Attached are some images showing the difference between them, and the result of when it works and when it doesn’t.

Doing some tracing, I noticed that the problem always happens when trying to talk to the card, for example in:

e32ttl.getConfiguration(), or in e32ttl.setConfiguration()

And the status code of the board that doesn’t work is always 9, with a timeout error.

Remembering that on Arduino, this all works perfectly!

Can you help me?

• This topic was modified 1 year, 6 months ago by phnahes.
• This topic was modified 1 year, 6 months ago by phnahes.

[Renzo Mischianti]

Hi phnahes,
It’s possible that you connect on Arduino the power pin of e32 to 5v and to the esp32 to the 3.3v?
Bye Renzo

[phnahes]

Yes, of course!!
I did the changes, but not works yet…

On Arduino, the new e32 board, works, but not receive the package of old e32 board… (but ok, the 5v is connected there, on arduino)

When I connect the new e32 board on ESP32, both with 5v and 3.3v the same problem occurs, this bellow:

12:41:09.096 -> Guru Meditation Error: Core 1 panic'ed (LoadProhibited). Exception was unhandled.
12:41:09.159 ->
12:41:09.159 -> Core 1 register dump:
12:41:09.192 -> PC : 0x4008921b PS : 0x00060a30 A0 : 0x800d365d A1 : 0x3ffcadc0
12:41:09.288 -> A2 : 0x3ffcadde A3 : 0x00000000 A4 : 0x00000006 A5 : 0x3ffcadde
12:41:09.383 -> A6 : 0x00002580 A7 : 0x0800001c A8 : 0x800e0154 A9 : 0x3ffcad90
12:41:09.479 -> A10 : 0x00000002 A11 : 0x3f4005c5 A12 : 0x00000001 A13 : 0x00000010
12:41:09.575 -> A14 : 0x00000011 A15 : 0x0000e100 SAR : 0x0000000a EXCCAUSE: 0x0000001c
12:41:09.671 -> EXCVADDR: 0x00000000 LBEG : 0x40089a6d LEND : 0x40089a7d LCOUNT : 0xffffffff
12:41:09.768 ->
12:41:09.768 ->
12:41:09.768 -> Backtrace: 0x40089218:0x3ffcadc0 0x400d365a:0x3ffcadd0 0x400d482b:0x3ffcae20 0x400e1a3e:0x3ffcae70
12:41:09.865 ->
12:41:09.865 ->
12:41:09.865 ->
12:41:09.865 ->
12:41:09.865 -> ELF file SHA256: 74cd7170a2883735
12:41:09.929 ->

 

Looking at the e32 boards, the only difference is the “10408-v1.1” behind for the new ones, and “10498-v1.1” for the old ones.

This numbers, It makes any sense for you?

Thank you for your help! 🙂

[phnahes]

@reef,  It works on 3.3v, thank you very much for the information!!!

But it still doesn’t communicate with the old one, I’ve already configured it with the same parameters and the same channel, H and L address.

Do you have any other ideas?

The receiver:
10:32:48.757 -> —————————————-
10:32:48.789 -> HEAD : 11000000 192 C0
10:32:48.821 ->
10:32:48.821 -> AddH : 1
10:32:48.853 -> AddL : 5
10:32:48.853 -> Chan : 23 -> 433MHz
10:32:48.885 ->
10:32:48.885 -> SpeedParityBit : 0 -> 8N1 (Default)
10:32:48.917 -> SpeedUARTDatte : 11 -> 9600bps (default)
10:32:48.949 -> SpeedAirDataRate : 10 -> 2.4kbps (default)
10:32:49.013 -> OptionTrans : 1 -> Fixed transmission (first three bytes can be used as high/low address and channel)
10:32:49.109 -> OptionPullup : 0 -> TXD, RXD, AUX are open-collectors
10:32:49.173 -> OptionWakeup : 0 -> 250ms (default)
10:32:49.237 -> OptionFEC : 0 -> Turn off Forward Error Correction Switch
10:32:49.301 -> OptionPower : 0 -> 30dBm (Default)
10:32:49.333 -> —————————————-

The sender:

Is the same, just change the
-> AddH : 1
-> AddL : 1

• This reply was modified 1 year, 6 months ago by phnahes.

[Renzo Mischianti]

Hi,
no, restore to an external 5v power supply and try to change the pullup resistor o try to remove It.
Bye Renzo

[phnahes]

No way, I tested and everything with the same behavior 🙁

[phnahes]

Interestingly, I can communicate between the new and the old, thanks to your tip, thank you.

When I supply 3.3v to the ESP32, and without any pull-up resistors, the crash disappears and it works (in the new one).

And the old one, 5v, doesn’t communicate with the new ones, BUT, when I fed it with 3.3v too, they started communicating with the old one.

This behavior is really strange, isn’t it?

I remember a thread you talked about the differences between v8 and v8.1, here it doesn’t seem to be a v8.1, but would it explain this behavior?

Thank you for your help.

[Renzo Mischianti]

Hi,
It’s very strange; It’s more likely that there are some problems with the power supply and the pull-up resistor.
Bye Renzo

[phnahes]

I found the problem… really some difference in the new ones!
It is no longer necessary to use the pull up resistors, if I use the ESP32 it freezes, but without them it works fine.

Another point is that it is no longer possible to use an “air data rate” with value 0.3, minimum is 2.4

Thanks a lot for you help!!

[Renzo Mischianti]

Hi,
thanks for your feedback, I think your information can be very useful.
Bye Renzo

[Author]

Posts