How can you tell that it is doing this?
Just to be sure, you add, for example,
Serial.print("p2 ");
in front of
Serial.println(digitalRead(2));
and similarly for the other pins.
What is "complex" about it? If it involves more delays and/or...
Starting yesterday (May 27, 2025) the forum began having problems, showing "An error occurred while the page was being generated".
After some investigation, the problem turned out to be a "xf_session_activity" table grew too large. Apparently...
Have you tried slower speeds? e.g. 9600?
Perhaps there's a mismatch of polarity or voltage between the two devices?
Do you have a link to a reference manual for the MSPM0?
Pete
For the first part of your question, I think this will work.
BTW - Should the fourth entry be playArrayWav5 (or playArrayWav4)?
AudioPlayArrayResmp playArrayWav1; //xy=1061.4284744262695,905.7142791748047
AudioPlayArrayResmp playArrayWav2...
I may have figured it out. I've attached a zip of the src directory from IBusBM library. It contains IBusBM.cpp and IBusBM.h although only IBusBM.cpp has changed. It turned out to be much easier than I had imagined.
I wrote my own sketch to test...
Not yet. The examples compile but ibus_sensor indicates it is sending info but ibus_singlemonitor only prints zeros.
Need to ponder it more. It may be something to do with the half-duplex protocol and I haven't wired the two processors together...
I was just in the process of modifying two of the examples to disable the timer. Now to add pins to a T4.0 so that I can try a T4.0 and T4.1 chatting to each other with the ibus_sensor and ibus_singlemonitor examples.
Pete
At first glance this doesn't look like it would be anywhere near as easy to convert because it uses timer interrupts.
I'll have a deeper look but don't get your hopes up :unsure:
Pete
I had another, closer, look at the link you provided in #8 and the two versions of that library both seem to support T4.0 and T4.1.
Can't you use either of those?
Pete
@pierrotm777
I had a look at the library you posted in #1 and have modified it so that it appears to work on a Teensy 4.0 or Teensy 4.1
I tested it on a T4.1 by using Serial2 (instead of Serial3 because it's easier to reach) and looping it back...
Yes, the problem isn't with the Smartmatrix library.
The problem is that the original code written by Eli Curtz (i.e. all the code in your RGB_DMD_Branco directory) is written specifically for the Teensy 3.2 and uses code which directly accesses...
You may be using the correct SmartMatrix library for a T4, but your own code is still expecting a T3.
For example in Boardinfo.ino you have:
/*
Read the MAC address
http://forum.pjrc.com/threads/91-teensy-3-MAC-address
To understand what's...
This:
IntervalTimer myTimer;
Should be at the top of your file. It is a declaration, not an executable statement.
Declaring myTimer within the setup() function means that the myTimer instance will disappear when the setup function ends.
Pete
It would be more useful to post the code you tried to use on the T4.
Have you read the file MIGRATION.md in the SmartMatrix-master directory? It describes some changes that are required to get that library working on a T4.
It would also help if...
The fact it can decode some of the text suggests that both ends are at the same baud rate.
But the receiving end doesn't seem to be able to keep up with the transmission.
What is receiving the text?
Pete