Telemetry not working with 3 sensor

[magnum3131]

Hi,

I use your library to make some sensor ( Temperature, GPS,...). if i plug only 2 sensors on the receiver with different slot everything is working perfectly.

But if i plug 3 sensors the telemetry on esp32 stop working, i have to stop one oh the three sensor to make it working again

Is there a limitation or something wich can explain these issue ?

Thanks
Julien

[BrushlessPower]

Hi Julien,

interesting issue. Never thought about using multiple ESP32 (or Atmega) Sensors.

i have an idea whats causing the issue:
the Sensors (the third) could trigger the Start/End of a SBUS(2) Frame in the other Sensors. That would cause many problems.

If i'am right the same should happen with a original Futaba Sensor.
i have to check the code and try to get the same behavior.

Could yo tell me with Sensors you use on which slot and which ESP?
Example:
ESP32 No.1 -> temp sensor Slot2, Voltage Sensor Slot3
ESP32 No.2 -> GPS Slot 8
ESP32 No3. -> .....

Do the ESP32 anything? Are they crashing? Error Messages?

[magnum3131]

Hi,
Thanks a lot for your answer
ESP32 1 => Slot 1 rpm sensor
ESP32 2 => Slot 3 rpm sensor
ESP32 3 => Slot 5 rpm sensor

I made a loop wich increase the RPM, i can see when the telemetry stop working. When i plug the third sensor the telemetry stop working immediatly. there is no message or crach on ESP32.

I'll test this evening ig i have the same problem if i plug a futaba sensor

Thanks
Julien

[magnum3131]

I did more test
The configuration is the following
Powerbox Spark Switch pro => slot 1 to 5
Powerbox Mercury => slot 8 to 23
ESP32-1 RPM => slot 6
ESP32-2 RPM => slot 7

Case 1
Powerbox Spark Switch pro + Mercury + ESP32-1 => Working

Case 2
Powerbox Spark Switch pro + Mercury + ESP32-2 => Working

Case 3
Powerbox Spark Switch pro + Mercury + ESP32-2 + ESP32-2 => Powerbox Sensor working but not the ESP32.

With other telemetry sensor i can only plug one ESP32

Thanks
Julien

[BrushlessPower]

Dear Julien,

thank you for testing. I have 3 ESP32 and i will build up the same test an try to find the problem.

I think it could be a Problem with the 1k resistor between RX and TX of every ESP32 on the SBUS. But i can only check it with an oscilloscope.

Cold you try another test (before i finish my test build)?
ESP32-1 with 2,3,4,5 RPM Sensors on SLOT 1 to 6
ESP32-2 with just one RPM Sensor on SLOT 7

You said "the Telemetry stop working". So my understanding is, that all three RPM Sensors stop working? This would really point to a problem with the 1k resistor.

[magnum3131]

Hi,
I'll test the new case this evening
I don't know if it could affect the SBUS2 Library but i have a 2.4 resistor between the TX/RX Pin

Thanks
Julien

[BrushlessPower]

hi,
2k4 Resistor is ok.
I had problems with a R7003SB. This one only worked with 1k. Thats why i recommend 1k.

Maybe its better to use a diode.

[magnum3131]

This is strange, the test with powerbox and esp32 has been done with a 7003sb on my plane

I'll try with a 7008
Julien

[magnum3131]

Hi,
I do your test
ESP32-1 with 2,3,4,5 RPM Sensors on SLOT 1 to 6
ESP32-2 with just one RPM Sensor on SLOT 7

It's working with the 7008sb but not with the 7003sb, only one sensor work with the 7003

You said "the Telemetry stop working". So my understanding is, that all three RPM Sensors stop working? This would really point to a problem with the 1k resistor. => Yes all three RPM stop working

Do you think we need to lower the value of the resistor ?

Thanks
Julien

[BrushlessPower]

Ok

i really think it's the value of the Resistor. You could try to increase it when using multiple ESP32
Today i will have a look on the scope.

The perfect solution would be a one wire Serial with switching RX/TX on one Pin.

[BrushlessPower]

So i got a View on the Scope and got back to the old Problem with 1k on R7003

1. The Resistor Value has to be small enough that the TX Pin can Pull High Signal on the SBUS (when transmitting Telemetry)
2. The Resistor Value should be as big as possible that the Servo Data is not pulled down to much (when receiving SBUS Frame and other telemetry)

for the R7008 4k7 and 1k was ok on my test
for the R7003 1k was ok on my test

But, when we connect multiple ESP32 on the same SBUS the Resistor Values are not valid any more

with three ESP32 (each with 1k) the Pull Down Resitance is 1k/3 = 333R -> thats much to low
and the pull up resistance i still 1k for each ESP32 to transmit his slot. But it has to work against the other 2 ESP32 with 500R

so at the End: The resistor Solution is not the Best
Did you have some diodes there?
You should add a diode between TX and the 1k. Anode to TX, Cathode to Resistor.

TX------>|----1k-----SBUS

RX-------------------SBUS

The Diode should have a low Forward Voltage Drop. I have tested it with a BAV21 and a high Drop (1V Voltage Drop) and it's working.

[magnum3131]

Hi,

Thanks a lot for your expertise, for resuming i have to change my 2.4k resistor for a 1k and i have to add a diode. I need to place an order to test all this.

For the diode i found the 1N4148 which have a drop down of 0.7 or maybe a schottky diode with a lower drop down, I need to check a reference for a schottky.

Thanks a lot, I'll let you know when i'll have everything for testing

Other question what kind of oscilloscope do you use ?

Thanks
Julien

[BrushlessPower]

The 1N4148 should be fine

Maybe you can also order a Schottkey with a high reverse Voltage (more than 10V). But this is something about try an error.

I use a PicoScope 2405A.
But the cheap PicoScope 2204A is also fine. But 2 Channel are not enough for my tasks.

Did you notice Issue #34 ?

[magnum3131]

Hi,

I order all the stuff, i hope i'll receive next week. I had to find a solution because in my club we try to do ESP32 hardware which can work with Futaba (1k on TX) and Jeti (Jeti need a 2.4k resistor on the RX pin)

For the arduino core I am in 1.0.4, the 1.0.6 is available i hope the bug is not present in this version

Thanks a lot
Julien

[BrushlessPower]

The solution with diode should also work with with 2k4.

i have the feeling that the 1.0.6 is more stable. I had a lot of issues with 1.0.5 and the are fixed with 1.0.6

p.s.
withe Jeti Telemetry you mean EXBUS?
Not EX?
until now, i cant find a good solution for ESP32 with EX Telemetry because the ESP32 cant handle 9 Data Bits

[magnum3131]

Yes ex bus
I use this library
https://github.com/Sepp62/JetiExBus
Julien

[BrushlessPower]

any news here?

[magnum3131]

Hi,Not yet, i'am in HallydayI'll let you KnowlesThanksJulien

[ericlangel]

@magnum3131

could you try the new Version of the library?
Some issues are solved (nothing real important)
and a new Feature is coded: reading Sensor Values of all SBUS Sensors on the Bus

and you have some ESP32 on the SBUS and a Powerbox Spark Switch pro and Powerbox Mercury

[magnum3131]

Hi Éric,Of course i can, What kind of informations do you need ? Thanks JulienLe 23 juil. 2021 14:56, ericlangel ***@***.***> a écrit : @magnum3131 could you try the new Version of my library? Some issues are solved (nothing real important) and a new Feature is coded: reading Sensor Values of all SBUS Sensors on the Bus and you have some ESP32 on the SBUS and a Powerbox Spark Switch pro and Powerbox Mercury —You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or unsubscribe.

[ericlangel]

i have attached the new library and an Example sketch.

please change the SBUS2 Pins to your used SBUS2 Pins.
leave Pin 16 and 17 unconnected -> that is another topic

Now use my SBUS2 Library as usual.
You will get some prints for Sensor Slot 0 to 7. You can extend it to Slot31
The Output on console should show the value used for the emulated RPM Sensor
And Slot0 (RX Voltage) and your other Sensors with their Slot Number

If that is working, we can go to the next Topic.

SBUS2.zip

[ericlangel]

@magnum3131

i have a new Library Version which should work with 1k resistor and multiple Sensors (without diode or Voltage loss)
the TX Pin is just active (OUTPUT) when sending Telemetry Data. After that its disabled (INPUT/Floating).

It's not fully tested, but the first Test looks good

Please tell me if you want to test?

[magnum3131]

Hi Eric, Yes i want to test, if it's working i don't need to change my hardware i have already done I'll be able to test it this weekend Thanks a lot Julien Le mardi 3 août 2021, 10:50:01 UTC+2, ericlangel ***@***.***> a écrit : @magnum3131 i have a new Library Version which should work with 1k resistor and multiple Sensors (without diode or Voltage loss) the TX Pin is just active (OUTPUT) when sending Telemetry Data. After that its disabled (INPUT/Floating). It's not fully tested, but the first Test looks good Please tell me if you want to test? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

[ericlangel]

[edit] File removed

here the update
for explanation: the example sketch also sends sbus2 Frames on Serial2 -> so leave Pin 16 and 17 unconnected or use your sketch and just update the sources

[magnum3131]

Thanks a lot, I have to modify it because i use Pin 16&17 on my ESP32  Julien Le mardi 3 août 2021, 15:48:19 UTC+2, ericlangel ***@***.***> a écrit : SBUS2.zip here the update for explanation: the example sketch also sends sbus2 Frames on Serial2 -> so leave Pin 16 and 17 unconnected or use your sketch and just update the sources — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

[ericlangel]

ok, you could erase all Serial2 code in the example sketch

or use your old sketch and just update the library sources

[ericlangel]

tonight i realized that the zip file i gave you wont work.

because Change TX to Float and back to TX is hardcoded to GPIO 26
i will change it and upload again

[magnum3131]

OK thanksJulien Le 4 août 2021 08:33, ericlangel ***@***.***> a écrit : tonight i realized that the zip file i gave you wont work. because Change TX to Float and back to TX is hardcoded to GPIO 26 i will change it and upload again —You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications on the go with GitHub Mobile for iOS or Android.

[magnum3131]

Hi Eric, I found the line with pinMatrixOutDetach and pinMatrixOutAttach, i adapted it to my pin. I have the same problem with your library, it's only working with 2 ESP32 and some time with only one The error are : Error! -> rx_fifo_len = 128 Value = F, 0, 4, 60, 58, F8, 7, 96, BC, 1, 10, 80, 0, 4, 20, 0, 1, 8, 40, 0, 2, 10, 80, 0, 34, 0, 0, 0, 0, 0, 0, 4, 0, 4, 61, 1, FC, 3, 60, 1, 79, 3, 0, 4, 0, 4, 0, 4, 0, 4, 0, 4, 0, 4, 0, 4, 0, 4, 0, 4, 0, 4, 0, 0, 0, 0, 0, 0, A4, 3, 40, 3F, 0, 0, 0, 0, 6C, 3, 40, 3F, 0, 0, 0, 0, E8, 3, 0, 0, 0, 0, 0, 0, 2, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 6C, 3, 40, 3F, 0, 0, 0, 0, E8, 3, 0, 0, 0, 0, 0, 0, 1, 0, 0, 0, 0, 0, 0, 0, 0,  [HEX]Error! -> rx_fifo_len = 128 Value = F, 0, 4, 60, 58, F8, 7, 96, BC, 1, 10, 80, 0, 4, 20, 0, 1, 8, 40, 0, 2, 10, 80, 0, 34, 0, 0, 0, 0, 0, 0, 4, 0, 4, 61, 1, FC, 3, 60, 1, 79, 3, 0, 4, 0, 4, 0, 4, 0, 4, 0, 4, 0, 4, 0, 4, 0, 4, 0, 4, 0, 4, 0, 0, 0, 0, 0, 0, A4, 3, 40, 3F, 0, 0, 0, 0, 6C, 3, 40, 3F, 0, 0, 0, 0, E8, 3, 0, 0, 0, 0, 0, 0, 2, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 6C, 3, 40, 3F, 0, 0, 0, 0, E8, 3, 0, 0, 0, 0, 0, 0, 1, 0, 0, 0, 0, 0, 0, 0, 0,  [HEX]Error! -> rx_fifo_len = 128 Value = F, 0, 4, 60, 58, F8, 7, 96, BC, 1, 10, 80, 0, 4, 20, 0, 1, 8, 40, 0, 2, 10, 80, 0, 34, 0, 0, 0, 0, 0, 0, 4, 0, 4, 61, 1, FC, 3, 60, 1, 79, 3, 0, 4, 0, 4, 0, 4, 0, 4, 0, 4, 0, 4, 0, 4, 0, 4, 0, 4, 0, 4, 0, 0, 0, 0, 0, 0, A4, 3, 40, 3F, 0, 0, 0, 0, 6C, 3, 40, 3F, 0, 0, 0, 0, E8, 3, 0, 0, 0, 0, 0, 0, 2, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 6C, 3, 40, 3F, 0, 0, 0, 0, E8, 3, 0, 0, 0, 0, 0, 0, 1, 0, 0, 0, 0, 0, 0, 0, 0,  [HEX]Error! -> rx_fifo_len = 128 Value = F, 0, 4, 60, 58, F8, 7, 96, BC, 1, 10, 80, 0, 4, 20, 0, 1, 8, 40, 0, 2, 10, 80, 0, 34, 0, 0, 0, 0, 0, 0, 4, 0, 4, 61, 1, FC, 3, 60, 1, 79, 3, 0, 4, 0, 4, 0, 4, 0, 4, 0, 4, 0, 4, 0, 4, 0, 4, 0, 4, 0, 4, 0, 0, 0, 0, 0, 0, A4, 3, 40, 3F, 0, 0, 0, 0, 6C, 3, 40, 3F, 0, 0, 0, 0, E8, 3, 0, 0, 0, 0, 0, 0, 2, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 6C, 3, 40, 3F, 0, 0, 0, 0, E8, 3, 0, 0, 0, 0, 0, 0, 1, 0, 0, 0, 0, 0, 0, 0, 0,  [HEX]Error! -> rx_fifo_len = 128 Value = F, 0, 4, 60, 58, F8, 7, 96, BC, 1, 10, 80, 0, 4, 20, 0, 1, 8, 40, 0, 2, 10, 80, 0, 34, 0, 0, 0, 0, 0, 0, 4, 0, 4, 61, 1, FC, 3, 60, 1, 79, 3, 0, 4, 0, 4, 0, 4, 0, 4, 0, 4, 0, 4, 0, 4, 0, 4, 0, 4, 0, 4, 0, 0, 0, 0, 0, 0, A4, 3, 40, 3F, 0, 0, 0, 0, 6C, 3, 40, 3F, 0, 0, 0, 0, E8, 3, 0, 0, 0, 0, 0, 0, 2, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 6C, 3, 40, 3F, 0, 0, 0, 0, E8, 3, 0, 0, 0, 0, 0, 0, 1, 0, 0, 0, 0, 0, 0, 0, 0,  [HEX]Error! -> rx_fifo_len = 128 Value = F, 0, 4, 60, 58, F8, 7, 96, BC, 1, 10, 80, 0, 4, 20, 0, 1, 8, 40, 0, 2, 10, 80, 0, 34, 0, 0, 0, 0, 0, 0, 4, 0, 4, 61, 1, FC, 3, 60, 1, 79, 3, 0, 4, 0, 4, 0, 4, 0, 4, 0, 4, 0, 4, 0, 4, 0, 4, 0, 4, 0, 4, 0, 0, 0, 0, 0, 0, A4, 3, 40, 3F, 0, 0, 0, 0, 6C, 3, 40, 3F, 0, 0, 0, 0, E8, 3, 0, 0, 0, 0, 0, 0, 2, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 6C, 3, 40, 3F, 0, 0, 0, 0, E8, 3, 0, 0, 0, 0, 0, 0, 1, 0, 0, 0, 0, 0, 0, 0, 0,  [HEX] ThanksJulien Le mercredi 4 août 2021, 08:33:27 UTC+2, ericlangel ***@***.***> a écrit : tonight i realized that the zip file i gave you wont work. because Change TX to Float and back to TX is hardcoded to GPIO 26 i will change it and upload again — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

[BrushlessPower]

hi julien,

i forgot to upload the new version.
There are so many changes the last weeks.

I have no plan which version u are using

i upload as soon as possible

[magnum3131]

Hi,Thanks a lot. I'll wait the new version for testing with multiple esp32JulienLe 9 août 2021 15:47, BrushlessPower ***@***.***> a écrit : hi julien, i forgot to upload the new version. There are so many changes the last weeks. I have no plan which version u are using i upload as soon as possible —You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications on the go with GitHub Mobile for iOS or Android.

[ericlangel]

Here the actual Version
It's like a pre release, but i have not tested with multiple Sensors.
There are now some more Examples for the different use cases.
Atmega328P is not updated

removed file

[magnum3131]

Hi Éric,I'll test it this evening Thanks JulienLe 17 août 2021 08:33, ericlangel ***@***.***> a écrit : Here the actual Version It's like a pre release, but i have not tested with multiple Sensors. There are now some more Examples for the different use cases. Atmega328P is not updated SBUS2.zip —You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications on the go with GitHub Mobile for iOS or Android.

[ericlangel]

SBUS2.zip

This one works just with 1k between RX and TX and both RX's connected
ESP32 No1 = Simulation Mode + Slot 7
ESP32 No2 = Normal Mode with Slot 1 to 19 (without Slot7)

All Slots are displayed
All Signal Levels are ok
removed Error Prints

[magnum3131]

Hi Eric, The result of the test :ESP32-1 : Port 1 RPM sensorESP32-2 : Port 2 RPM sensor ESP32-3 : Port 3 RPM sensor With a 2.4K between RX and TX (My esp32 were already soldered with a 2.4k) It only works with 1 ESP32, the SBUS 2 stop working at the time i plug a second ESP32 I'll do more test this evening with a 1k resistor and also with a diode ThanksJulien  Le mardi 17 août 2021, 09:27:33 UTC+2, ericlangel ***@***.***> a écrit : SBUS2.zip This one works just with 1k between RX and TX and both RX's connected ESP32 No1 = Simulation Mode + Slot 7 ESP32 No2 = Normal Mode with Slot 1 to 19 (without Slot7) All Slots are displayed All Signal Levels are ok removed Error Prints — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

[ericlangel]

i will test it with a real futaba RX (not ESP32 Simulation Mode)

maybe something else was crashing. i have to make my sbus cable with a plug. so that i can dis/connect the ESP32 to see if there are faults

[ericlangel]

hi julien,

i had the same issue. When connecting/disconnecting the ESP32 to the SBUS2 Port the USART Interrupt crashed.

i fixed that issue:
SBUS2.zip

For Future Test: Enable the CoreDebugLevel for ESP32 to "Info". Then you will get Error Messages when something goes wrong on the SBUS Stuff.

i had a look on the Scope with ESP32, 1k and R7003
SBUSFrame (and Slot0) are at 3.3V
The RPM Sensors from ESP32-1 and ESP32-2 are at 2.0V

That's OK
But i would recommend 1k when using R7003.
With R7008 the 2k4 could be fine.

What i want to say.....in my DIY ESC with Futaba and Jeti Telemetry i have used 1k. And the Jeti Telemetry is fine with it

[magnum3131]

Hi Eric, It's better with the new version. it's working with 4 ESP32 (Slot 1,2,3, 4) on R7008SB with a 2.4K resistor. Sometime it's locking few second and the following error is displayed (ESP32 in info mode) I][SBUS_usart_ESP32.cpp:284] uart_intr_handle(): [SBUS2][Info] Receive Error[I][SBUS_usart_ESP32.cpp:284] uart_intr_handle(): [SBUS2][Info] Receive Error[I][SBUS_usart_ESP32.cpp:284] uart_intr_handle(): [SBUS2][Info] Receive Error I'll try this evening with a R7003SB with in installed on my plane with other sensor (Powerbox Mercury & Spark switch Pro) Thanks a lot Julien Le mercredi 18 août 2021, 10:42:10 UTC+2, ericlangel ***@***.***> a écrit : hi julien, i had the same issue. When connecting/disconnecting the ESP32 to the SBUS2 Port the USART Interrupt crashed. i fixed that issue: SBUS2.zip For Future Test: Enable the CoreDebugLevel for ESP32 to "Info". Then you will get Error Messages when something goes wrong on the SBUS Stuff. i had a look on the Scope with ESP32, 1k and R7003 SBUSFrame (and Slot0) are at 3.3V The RPM Sensors from ESP32-1 and ESP32-2 are at 2.0V That's OK But i would recommend 1k when using R7003. With R7008 the 2k4 could be fine. What i want to say.....in my DIY ESC with Futaba and Jeti Telemetry i have used 1k. And the Jeti Telemetry is fine with it — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

[ericlangel]

Nice that it is working

this error should just occur when connecting/disconnecting an ESP32 to the SBUS.
it really should not occur in normal operation.

could you look how often it is displayed?
everytime the same ESP?
it could be also an issue of not enough signal voltage (maybe better to use 1k?)

[magnum3131]

Hi Eric, I did more test on my plane, the equipement is the following one :2 x R7003 (connected to powerbox Mercury, Telemetry connected to the 7003 Master)Port 1 to 5 => Powerbox Sparkswitxh ProPort 8 to 23 => Powerbox Mercury with GPSPort 24 => ESP32 with 2.4k resistor => Working wellPort 25 => ESP32 with 2.4k resistor => Working until there is change state on sparkswitch proThe errors are[I][SBUS_usart_ESP32.cpp:350] uart_intr_handle(): [SBUS2][WARNING] Invalid Slot ID[I][SBUS_usart_ESP32.cpp:284] uart_intr_handle(): [SBUS2][Info] Receive Error[I][SBUS_usart_ESP32.cpp:350] uart_intr_handle(): [SBUS2][WARNING] Invalid Slot ID[I][SBUS_usart_ESP32.cpp:284] uart_intr_handle(): [SBUS2][Info] Receive Error[I][SBUS_usart_ESP32.cpp:350] uart_intr_handle(): [SBUS2][WARNING] Invalid Slot ID[I][SBUS_usart_ESP32.cpp:284] uart_intr_handle(): [SBUS2][Info] Receive Error[I][SBUS_usart_ESP32.cpp:284] uart_intr_handle(): [SBUS2][Info] Receive Error[I][SBUS_usart_ESP32.cpp:284] uart_intr_handle(): [SBUS2][Info] Receive Error[I][SBUS_usart_ESP32.cpp:284] uart_intr_handle(): [SBUS2][Info] Receive Error[I][SBUS_usart_ESP32.cpp:284] uart_intr_handle(): [SBUS2][Info] Receive Error[I][SBUS_usart_ESP32.cpp:284] uart_intr_handle(): [SBUS2][Info] Receive Error Port 26 => ESP32 with 2.4k resistor => same comportment of slot 25 with same error, i thing that 2.4k resistor is too mutch. i'll try with 1K ThanksJulien Le mercredi 18 août 2021, 16:50:05 UTC+2, ericlangel ***@***.***> a écrit : Nice that it is working this error should just occur when connecting/disconnecting an ESP32 to the SBUS. it really should not occur in normal operation. could you look how often it is displayed? everytime the same ESP? it could be also an issue of not enough signal voltage (maybe better to use 1k?) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

[ericlangel]

Hi Julien,

the Errors seems to be Bytes that are not read correctly. I think that is an issue from the 2k4.
It would be really great if you could test it again with 1k.

I will add some more detailed Error Messages to the Log to make the debugging easier.
I will upload it to the git repo for everyone. It seems that it is stable enough for a release

[magnum3131]

Hi Eric, I change the resistor to a 1K, it's working with 4 ESP32. I have to check because sometimes the ESP32 lock on SBUS2_Setup and loop on reboot. I'll try to debug it Thanks Julien Le lundi 23 août 2021, 11:50:56 UTC+2, ericlangel ***@***.***> a écrit : Hi Julien, the Errors seems to be Bytes that are not read correctly. I think that is an issue from the 2k4. It would be really great if you could test it again with 1k. I will add some more detailed Error Messages to the Log to make the debugging easier. I will upload it to the git repo for everyone. It seems that it is stable enough for a release — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

[BrushlessPower]

Hi Julien,
could you post the backtrace error message?

[magnum3131]

Hi, This is the error, it can loop 10 or more before it start. Some time i need to switch Off the ESP32 ThanksJulien rst:0x3 (SW_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)configsip: 0, SPIWP:0xeeclk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00mode:DIO, clock div:2load:0x3fff0018,len:4load:0x3fff001c,len:1216ho 0 tail 12 room 4load:0x40078000,len:10944load:0x40080400,len:6360entry 0x400806b4Guru Meditation Error: Core  1 panic'ed (Cache disabled but cached memory region accessed)Core 1 register dump:PC      : 0x40143664  PS      : 0x00060034  A0      : 0x4008eab4  A1      : 0x3ffc0490  A2      : 0x3ffc30b4  A3      : 0x3ffba264  A4      : 0x00000000  A5      : 0x40094a54  A6      : 0x00000000  A7      : 0x1300025c  A8      : 0x800812a4  A9      : 0x3ffc0470  A10     : 0x00000002  A11     : 0x00000101  A12     : 0x00000001  A13     : 0x00001000  A14     : 0x3ffc7cd4  A15     : 0xffffefff  SAR     : 0x00000010  EXCCAUSE: 0x00000007  EXCVADDR: 0x00000000  LBEG    : 0x00000000  LEND    : 0x00000000  LCOUNT  : 0x00000000  Core 1 was running in ISR context:EPC1    : 0x4008f233  EPC2    : 0x00000000  EPC3    : 0x00000000  EPC4    : 0x40143664 ELF file SHA256: 0000000000000000 Backtrace: 0x40143664:0x3ffc0490 0x4008eab1:0x3ffc04b0 0x4008f230:0x3ffba190 0x400859db:0x3ffba1b0 0x40092336:0x3ffba1d0 PC: 0x40143664: timer_set_alarm at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/driver/timer.c line 169 EXCVADDR: 0x00000000 Decoding stack results 0x40143664: timer_set_alarm at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/driver/timer.c line 169 0x4008eab1: spi_flash_restore_cache at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/spi_flash/cache_utils.c line 288 0x4008f230: spi_flash_read at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/spi_flash/flash_ops.c line 569 0x400859db: esp_dport_access_stall_other_cpu_end at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/esp32/dport_access.c line 126 0x40092336: xEventGroupSetBits at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/event_groups.c line 577 Le mercredi 25 août 2021, 17:48:16 UTC+2, BrushlessPower ***@***.***> a écrit : Hi Julien, could you post the backtrace error message? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

[magnum3131]

Hi also having this one, ThanksJulien Guru Meditation Error: Core  1 panic'ed (Cache disabled but cached memory region accessed)Core 1 register dump:PC      : 0x40144c68  PS      : 0x00060034  A0      : 0x4008ebbc  A1      : 0x3ffc0580  A2      : 0x3ffc31a4  A3      : 0x3ffba264  A4      : 0x3ffc8c28  A5      : 0x40094b98  A6      : 0x00000000  A7      : 0x1300025c  A8      : 0x800812e0  A9      : 0x3ffc0560  A10     : 0x00000002  A11     : 0x00000101  A12     : 0x00000001  A13     : 0x00001000  A14     : 0x3ffc7e04  A15     : 0xffffefff  SAR     : 0x00000010  EXCCAUSE: 0x00000007  EXCVADDR: 0x00000000  LBEG    : 0x00000000  LEND    : 0x00000000  LCOUNT  : 0x00000000  Core 1 was running in ISR context:EPC1    : 0x4008f341  EPC2    : 0x00000000  EPC3    : 0x00000000  EPC4    : 0x40144c68 ELF file SHA256: 0000000000000000 Backtrace: 0x40144c68:0x3ffc0580 0x4008ebb9:0x3ffc05a0 0x4008f33e:0x3ffba190 0x40085ae3:0x3ffba1b0 0x4009247a:0x3ffba1d0 PC: 0x40144c68: uart_clear_intr_status at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/driver/uart.c line 310 EXCVADDR: 0x00000000 Decoding stack results 0x40144c68: uart_clear_intr_status at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/driver/uart.c line 310 0x4008f33e: spi_flash_op_block_func at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/spi_flash/cache_utils.c line 82 0x40085ae3: ipc_task at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/esp32/ipc.c line 62 0x4009247a: vPortTaskWrapper at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/port.c line 143 Le mercredi 25 août 2021, 17:48:16 UTC+2, BrushlessPower ***@***.***> a écrit : Hi Julien, could you post the backtrace error message? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

[ericlangel]

Maybe i have an idea whats happening.
Did it also happen with 2 ESP's?
Or just with 4?
or just when another Sensor is used?

The sketches running on the ESP's are the example sketch just with different Slot's and Sensors?
No Flash(FFAT/SPIFFS/.....) Write/Reads?
No EEPROM Write Read?

[magnum3131]

Hi Eric, This is a GPS Sketch i use with the SBUS2 library. For the moment the problem occur when the ESP32 is plugged to the receiver (sometimes it start sometimes no). For the test there is only one sensor. I store ID value in flash EEPROM, as i remember i don't have this problem with the old library. I'll continue my test with the default skecth ThanksJulien    Le jeudi 26 août 2021, 11:52:20 UTC+2, ericlangel ***@***.***> a écrit : Maybe i have an idea whats happening. Did it also happen with 2 ESP's? Or just with 4? or just when another Sensor is used? The sketches running on the ESP's are the example sketch just with different Slot's and Sensors? No Flash(FFAT/SPIFFS/.....) Write/Reads? No EEPROM Write Read? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

[ericlangel]

If you write the EEPROM before SBUS_Setup() it is OK.

if you want to write EEPROM in Runtime, you have to disable SBUS before write and enable after write EEPROM

see #30

i have the same issue on my diy ESC with ESP and sbus lib
here is the working code:

SBUS_disable();
EEPROM.write( ... );
EEPROM.commit();
SBUS_enable();

i will try to test it here with 2 ESP's
the problem with plugging is:

maybe you plug in (or sbus is ready) in the middle of a Frame.
This should causes an invalid frame and should be fine with the next Frame.

But i'am actual not sure what the timer Intterupt do
I think it is started right after sbus_stetup and maybe crashes....i have to test it.

[magnum3131]

Hi Éric, i only have reading after the setup. I'll remove them for testThanks JulienLe 26 août 2021 12:17, ericlangel ***@***.***> a écrit : If you write the EEPROM before SBUS_Setup() it is OK. if you want to write EEPROM in Runtime, you have to disable SBUS before write and enable after write EEPROM see #30 i will try to test it here with 2 ESP's the problem with plugging is: maybe you plug in (or sbus is ready) in the middle of a Frame. This should causes an invalid frame and should be fine with the next Frame. But i'am actual not sure what the timer Intterupt do I think it is started right after sbus_stetup and maybe crashes....i have to test it. —You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications on the go with GitHub Mobile for iOS or Android.

[magnum3131]

Hi, I clear my code in order to do all my read and write EEPROM before the SBUS2_SETUP it's still crashing when the radio is on and i switch on the ESP32 connected to the receiver. The error is the following one (occurs 1 to 9 times)Guru Meditation Error: Core  1 panic'ed (Cache disabled but cached memory region accessed)Core 1 register dump:PC      : 0x40144cc0  PS      : 0x00060034  A0      : 0x4008ebbc  A1      : 0x3ffc0580  A2      : 0x3ffc31a8  A3      : 0x3ffba264  A4      : 0x00000000  A5      : 0x40094b98  A6      : 0x00000000  A7      : 0x1300025c  A8      : 0x800812e0  A9      : 0x3ffc0560  A10     : 0x00000002  A11     : 0x00000101  A12     : 0x00000001  A13     : 0x00001000  A14     : 0x3ffc7e04  A15     : 0xffffefff  SAR     : 0x00000010  EXCCAUSE: 0x00000007  EXCVADDR: 0x00000000  LBEG    : 0x00000000  LEND    : 0x00000000  LCOUNT  : 0x00000000  Core 1 was running in ISR context:EPC1    : 0x4008f344  EPC2    : 0x00000000  EPC3    : 0x00000000  EPC4    : 0x40144cc0 ELF file SHA256: 0000000000000000 Backtrace: 0x40144cc0:0x3ffc0580 0x4008ebb9:0x3ffc05a0 0x4008f341:0x3ffba190 0x40085ae3:0x3ffba1b0 0x4009247a:0x3ffba1d0 PC: 0x40144cc0: uart_clear_intr_status at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/driver/uart.c line 310 EXCVADDR: 0x00000000 Decoding stack results 0x40144cc0: uart_clear_intr_status at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/driver/uart.c line 310 0x4008f341: spi_flash_op_block_func at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/spi_flash/cache_utils.c line 82 0x40085ae3: ipc_task at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/esp32/ipc.c line 62 0x4009247a: vPortTaskWrapper at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/port.c line 143 Thanks Julien Le jeudi 26 août 2021, 12:17:35 UTC+2, ericlangel ***@***.***> a écrit : If you write the EEPROM before SBUS_Setup() it is OK. if you want to write EEPROM in Runtime, you have to disable SBUS before write and enable after write EEPROM see #30 i will try to test it here with 2 ESP's the problem with plugging is: maybe you plug in (or sbus is ready) in the middle of a Frame. This should causes an invalid frame and should be fine with the next Frame. But i'am actual not sure what the timer Intterupt do I think it is started right after sbus_stetup and maybe crashes....i have to test it. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

[ericlangel]

hi magnum,

first: we should move this to direct email. because i would like to see your testsketch and try it here

email: brushlesspower@protonmail.com

second: what do you mean with " i switch on the ESP32 connected to the receiver"?

is the ESP32 powered by receiver 5v?
is the receiver powered by ESP?
different power sources?
SBUS2 Cable already connected?
a lot of things.....

i tried it with connecting/Disconnecting SBUS cable -> no crash
i tried with plug in ESP32 to receiver (3pol servo cable)
i didn' try powering esp32 and receiver from different sources.....

Please write me an email with some more informations what you are doing and with your code. Then i can reproduce it here.