esp32-S3 Can bus not working

Nickz1969
Posts: 4
Joined: Wed Dec 11, 2024 10:58 pm

esp32-S3 Can bus not working

Postby Nickz1969 » Wed Dec 11, 2024 11:14 pm

I have 2 esp32-s3 modules
on the bottom of the module it is marked
MON16R8 Can bus works on this module.
MCN16R8 Can bus does not work on this module.
All other markings are identical on both modules.

Both running the same Code.

Does anybody know the difference between the 2 or how to get the MCN16R8 module working with the Can bus.

Nickz1969
Posts: 4
Joined: Wed Dec 11, 2024 10:58 pm

Re: esp32-S3 Can bus not working

Postby Nickz1969 » Fri Dec 13, 2024 12:24 am

to update on what i have found.
MO is revision v0.1 of the chip.
MC is revision v0.2 of the chip.

I still don't understand why the can bus does not work on the later revision.

Nickz1969
Posts: 4
Joined: Wed Dec 11, 2024 10:58 pm

Re: esp32-S3 Can bus not working

Postby Nickz1969 » Sat Dec 14, 2024 11:31 am

So I this forum a community form or a official ESPRESSIF run?

At this point I am so angry, I have spent nearly a year writing code for the ESP32S3 using the Can bus. Recently to find, as I have just restocked my hardware that there has been a revision of the chip that has moved backwards to a point the Can bus is useless, the implementation for people like me is totally not understandable.
I cannot find any helpful information or working examples that actually work.

I have some what working version, But its so slow, and will only read the first 3 address on the network of 15 addresses.

I have use the available examples to receive the data.

Maybe someone can show me how to filter address range using the TWAI we are now forced to use.
Example my perfectly working firmware on the MON v0.1 revision used this for the filter "CAN0.watchForRange(864, 992);"
Maybe some other TWAI examples with human readable setting that someone simple like me can use.

Nickz1969
Posts: 4
Joined: Wed Dec 11, 2024 10:58 pm

Re: esp32-S3 Can bus not working

Postby Nickz1969 » Mon Dec 30, 2024 9:20 am

Seeing as I have had no response to my query, my best option was throw out the ESP32 hardware and use a capable processor for the task. The STM32 does what I needed, I should have just used that in the beginning.

Who is online

Users browsing this forum: Bing [Bot], PetalBot and 2 guests