Search results

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 turning interrupts on and off, it could make a mess of...

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

Which radio are you using? Is there any setup required in the radio to make it activate the USB port? Pete

You didn't increase the size of the sizes[] array from 4 to 16. 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; //xy=1062.8570823669434,945.7143230438232...

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 the library and it seems to work with a T4.0 and...

I use 1k, but I've just determined that the ibus_sensor sketch isn't sending anything. More digging required. Pete

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 properly. Pete

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

No rush :D You're welcome and I hope it works. 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 on itself and reading/printing the received data...

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 the hardware registers of the T3.2. It will not be...

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 going on here, see "Kinetis Peripheral Module...

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 you posted some, or all, of the error messages. Pete

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

It appears that tft.init() will call spi.begin() which might conflict with what your call to SPI.begin() does. Try commenting out your call to SPI.begin() and see if it makes any difference. Pete

It might be wise to increase the size of the array unless you are sure you'll only ever have 8.3 formatted filenames. Pete

if (file_unix_time < last_file_unix_time) { last_file_unix_time = file_unix_time; file_to_delete = entry.name(); Serial.printf("\r\nFile name %s %s\r\n", entry.name(), file_to_delete); } I think that file_to_delete is saving a pointer to a string...

if (screenTimer = 27) { should be if (screenTimer == 27) { Pete

Great!

In the IDE you have to set the USB type as keyboard. In the menu choose Tools. Then from the dropdown choose USB Type. From the next dropdown choose Keyboard. Recompile. Should work now. Pete

Presumably, somewhere in the Serial.println code, it turns interrupts back on which allows the code to proceed. If it isn't called, interrupts stay off and the print buffer fills up and then println hangs. [edit] I suspect that if instead there was just one println immediately before the for...

I doubt that sending midi notes will affect the sequence. It is more likely to need a Program Change or Control Change message. Which midi software are you using and does it have any documentation? Pete

The code you posted sends a MIDI NoteOn when you press a button and a MIDI NoteOff when you release the button. The message is sent to whatever you have connected the Teensy USB port to. What is the Teensy USB connected to? What is playing "a sequence"? Pete

FYI I tried your code on a Teensy 2 connected to Windows 10 and with a piece of wire as a button on Pin 0. MIDI-Ox on Windows sees the midi messages. So the code works as advertised. There must be something wrong with how you are detecting the MIDI message. Pete

What have you connected the Teensy USB to in order to receive/detect the midi messages? The code is sending note C4 on MIDI Channel 2 (internal channel 1). If you're sending to a synthesizer/DAW/whatever, it must be set receive the correct channel. Pete

Try changing patchCord2 so that it outputs to the headphones. You'll then be able to hear whether there's anything coming out of bandPassFilter1. Pete

Post the code which produced the errors in your message #17. You've got some misplaced braces somewhere. Pete

Hmmm. Or maybe not. That would give a different error message. Pete

What you've done is add a loop() function inside the loop function like this: void loop() { // put your main code here, to run repeatedly: int velocity = 80; // Velocity int note=20; // Piano note void loop() { // put your main code here, to run repeatedly: usbMIDI.sendNoteOn(note...

Instead of sensing when the input is HIGH, you need to sense when it CHANGEs from HIGH to LOW or from LOW to HIGH. Post your code (in code tags please - use the </> icon) Pete

Do you have the SDTEST2.WAV file in the root directory of the SD card? And is the SD card in the appropriate slot as selected in the code? Pete

If polyphony is reached, you steal the oldest voice, but you don't turn it off. Just before you retrigger the oldest voice with the new note, use noteOff to turn off the old voice. Pete

It probably was, which is why the rest of the code and the message turned into italicized text. @AaronNY: when you post code, please enclose it in code tags (which can be generated using the </> icon) to avoid this problem. Pete

Just run the Guitar example and listen to the output on headphones. Pete

Try this sketch which is an I2C scanner modified so that it should see the SGTL5000 on the audio card at address 0x0A. // 240919 Do an I2C scan which should find the audio card's SGTL5000 // at address 10 (0xA) #include <Audio.h> #include <Wire.h> #include <SD.h> #include <SPI.h> const...

I haven't used a micromod but it appears to use the same pinouts as the T4.0 and T4.1. The SD SCK signal is on Teensy pin 13. This is the same pin as that used for the LED. So, if you are using the SD, you can't use pin 13 for the LED output. You'll have to work around it by connecting a LED and...

Ooooops. I thought it was a typo or something. Pete

Change AudioPlaySdWavX to AudioPlaySdWav Pete

I believe you will also need a 4.7k pullup resistor from the signal pin to 3v3. You can test your setup by running the Examples/OneWire/DS18x20_Temperature sketch. The code defaults to pin 10 but it is trivial to change this. Here's output from running this code using a Teensy2.0 which has 6...

This is a modified version of the Part_1_05_Do_More_While_Playing audio tutorial example. button0 stops the current file and plays the next one button1 is a toggle which pauses the current file or resumes playing it button2 stops the current file and plays the previous one Pete //...

Before you enable the audio, allocate some memory: AudioMemory(8); The message "Unplug the accessory using too much power" suggests that there's a problem with your soldering somewhere. Can you post a clear photo of your audioboard? Pete

It will also include the underscore characters. 2024_05_16.csv Pete

hello3 downloaded and executed with no problems, same as previous one.

Windows 10 Pro and Kaspersky Anti-virus. No problem with download and execution in Powershell. Pete

Two things I'd check - does pin 6 of the H11L1 have 3.3V? - the jumper which connects to the Teensy Pin 0 would have to be laying flat under the audio board. Have you bent the jumper pin at a right angle so that it will make proper contact with the breadboard pin? Pete

You've set the dc1 amplitude to zero, so printing the dc1 peak will be zero and multiplying zero by anything will give you zero out from the multiplication too. At least, that's what I get when I run your code. Try setting dc1 amplitude to 0.5 and then it will print: in=0.50 out=0.25 Pete