Yeah, that's a pity for sure...
I checked the Programmer’s Reference Guide and there is indeed no mentioning of pot/fader readouts...and weird that it does send out messages at power-up.
This statement from the...
After watching your last video, I have the feeling that this issue is LaunchControl related.
It looks like when the faders are at maximum at powerup, that fader state is not correctly registered.
At 0:15 through 0:20...
With respect to Q&A #2: could it be that the Teensy is just not ready yet? Although you state that with faders not at max (like 126) it works OK.
Is it possible to post your complete code? I have a Teensy 4.1 here...
I assume this related to your question in this other thread:
A few questions to get the picture more clear:
1. "The problem is that the LaunchControl XL sends the slider and potentiometer positions at startup,...
Yes, with the Teensyduino supplied Audio library, the DAC operates at 16 bit, 44.1kHz.
With the OpenAudio_ArduinoLibrary, you can take it up to 24bit and higher sample rates. Although a sample rate higher than 48kHz is...
Yep, shown here:
Yeah it's a bit noisy, the scope trigger was hardly able to show a stable image. Here is a screenshot of the scope with a 1sec persistence:
You may want to check out this thread where I...
Here are the logic analyzer images measured on pins 7, 20 & 21:
First a complete LR sample:
Then zoomed in around the BCLK sequence:
For reference is the output in CSV format. Took a 5ms sample:
Hi Richard, you're not accidently mixing me up with Paul Stoffregen, founder of PJRC.com, do you? I don't have shop...
Also I don't have a Teensy 3.6 so can't tell you about its DAC quality.
Anyway, I tested your...
From the Netherlands:
Pinging 162.254.150.250 with 32 bytes of data:
Reply from 162.254.150.250: bytes=32 time=110ms TTL=48
Reply from 162.254.150.250: bytes=32 time=108ms TTL=48
Reply from 162.254.150.250: bytes=32...
Interesting question. Actually I have no idea. But I can imagine that this could work since the PT8211 is a very basic DAC.
I would not be surprised if there is just an ordinary 16 bit shift-register where the DIN data...
Difficult to say what exactly is going on. But I suspect the switch is the culprit. Looking at the different corrosion spots, I can imagine that the internal contacts of the hook-switch may be affected as well,...
I would be seriously surprised when the chip is able to run at 2V5 supplied from the regulator.
Please have a look at this page for the rather complex power-up sequence.
A quick scan of the datasheet shows that the...
Put your multimeter in DC voltage measurement mode and connect the negative lead to pin GND and the positive lead to pin 0. With the headset on the hook you should measure ~3.3Vdc since pin 0 is pulled-up. When you lift...
Thanks for the info.
So apparently the code in void setup() is completely run since we see the message "Mode switched to: Ready".
The next message that is expected to show is "Handset lifted". That can only happen...
A few checks first:
1. Are you indeed using the exact same code as on Github: https://github.com/playfultechnology/audio-guestbook/blob/main/audio-guestbook.ino?
2. Is the wiring exactly like this picture? I suspect...
You may want to turn on "show verbose output" in File > Preferences:
Then you will see much more information in the bottom "Output" window:
You can select all data from the output window and report it here...
Your board seems to have a hardware problem.
From this page:
Do you see something out of the ordinary around the bootloader chip like loose solder particles?
Are any parts missing from the backside of the...
Agree, for the Audio Adapter rev D2 you end up with the default SPI pins.
How would the SPI driver know that pins do not work if you specifically assigned those to other valid pins? Ah OK, I see: Teensy 4 has only...
Shouldn't "#define SDCARD_SCK_PIN 14" be changed to "#define SDCARD_SCK_PIN 13" also?
Same for "#define SDCARD_MOSI_PIN 7" to "#define SDCARD_MOSI_PIN 11".
Paul
Welcome to the forum!
You may have missed the Forum Rule at the top of this page: "Always post complete source code & details to reproduce any issue!"
It helps a lot when you post your code so that other forum...
The code example you found for the DAC8568 will work perfectly fine for the DAC8168 as well.
These DAC's are very similar - the datasheet states: "The DAC7568, DAC8168, and DAC8568 are drop-in and function-compatible...
Yeah, U2 looks a bit weird . Don't know what to think about it...
But I also noticed that the regulator housing misses a little chip in the bottom-right corner:
Paul
Hmm, that is too bad.
I suppose you already did a close visual examination of the whole PCB?
Is the 3V3 regulator or any other part getting hot?
Location of U4:
Paul
I don't think you want the signal amplitude to be part of the equation. I can imagine that will lead to strange effects.
Probably it's just playing with the track factor until you find a satisfying formula.
Did some...
Bonjour,
Calculating your best solution: if track = 0, then new_FC = note_freq. If track = 1, then new_FC = centered_FC. I don't think that is what you want.
Isn't the formula just new_FC = note_freq * track, where...
Different Teensy's have different system clocks.
Do you really need a pulse that is derived from the system clock? Perhaps you can use a PWM signal with a very small duty-cycle?
Please see this page for more...
Looking at the schematic of the MDT board, the only (external) connections on the Teensy 3V3 output are the PCM5102 board and the SPI Flash.
Can you take those boards out and check whether the 3V3 returned to normal?...
The 3V3 regulator on the Teensy is short-circuit protected so it should not fail easily.
Can you isolate the Teensy from the rest of the circuit/PCB and then test it again?
Paul
Need a bit more context to fully understand, and perhaps answer your question.
If I understand correctly, keyboard tracking means that the LP-filter cutoff frequency changes with the frequency of the note played.
E.g....
There is additional Arduino stuff to be found here: C:\Users\<yourname>\AppData\Local\Arduino15.
This is also where the file preferences.txt resides.
Not sure whether this directory is also emptied when an uninstall...
Wasn't familiar with the term "vectorization of a library" but if I understand correctly it means "optimized for a specific architecture"?
If so, then I believe that CMSIS-DSP actually is vectorized for M7, according...
Not being a DSP expert by any means, but the CMSIS-DSP library is part of the Teensyduino installer. Look for the file "arm_math.h".
The CMSIS-DSP library supports correlation.
See also this recent thread.
Paul
Before adding a schmitt-trigger, I would focus on why the output of the optocoupler is not as clean as expected.
You stated that the signals on low-side of the opto are "a clean Low and High". I assume you measured...
My suggestion would be to look at ILI9341-based displays.
Lots of vendors of these displays and plenty software support, also on this forum.
You could start here.
Paul
So the original issue is not an issue anymore?
Did you perhaps try the minimal code in my message #10?
Looking and listening to your video, it seems the display driver and audio library are fighting for priority.
...
There should be no need to configure the DAC - the board should just work out of the box.
Since I've been using the board with a Teensy 3.2 succesfully, I hooked it up to a Teensy 4.1:
This is the code:
//...
No, it's not. MIDI-OX does not support hot-plugging of MIDI devices - you have to manually open the MIDI input after insertion of the USB cable.
Then I tried to measure the time it takes for the browser-based...
For a decent hint or explanation more information is needed. It looks like pin 22 sees a lot of noise or maybe the level of the measured signal is too low.
What exact optocoupler are you using? How is that optocoupler...
I'm not surprised that the monitor misses one or more initial messages when the USB cable is plugged in. Perhaps MIDI-OX is faster, I will try that some time this weekend.
Paul
Great!
Did you perhaps have a change to monitor the output of your Icon with respect to the command that disables the Scorpio controls when connected?
There seems to be a MIDI Controller message 0x78 that sets...
One last thought: looking at the SMD packages of the 74LVC, which are pretty small, could it be that Y pin accidentally solder-bridged to the GND pin?
Paul
Is it possible to disconnect the 74LVC Y pin from Teensy pin 12? Just to make sure that pin 12 is not pulling the Y signal to GND?
Otherwise I can only conclude that the 74LVC has passed away.
Paul
Just to be sure: are all your grounds hooked up together?
Is the external 5V supply also connected to Teensy pin VIN? Or is the Teensy powered over USB?
Paul
Hooked up a Teensy 4.1 and PT8211 board from PJRC:
Uploaded your code from message #3 and this is what the oscilloscope shows:
No pulses on left (or right) channel present...
Never seen these pulses when using the PT8211. How does the pulse look like when you zoom in on the pulse?
Did you check whether the pulses are also present on the power pins of the PT8211?
Furthermore, there are fake...
To check, I hooked up a Teensy 4.0 and some buttons and potmeter to see whether it's working.
It seems to output the correct MIDI messages, see this MIDI-OX output:
Pressed the buttons on pin 4, 5, 6, 7, 8, 9,...
I assume that when using the Icon M+, the "BANK <" & "BANK >" buttons switch 8 faders at a time?
Found 2 sources here and here] that talk about bank switching over the Mackie MCU protocol. The latter source states :...
Thanks for your reply.
Yes, that's also stated in Scorpio & Icon Platform M+ Operational Guide.
Note: Once the Scorpio establishes connection with the Platform M+,
faders and trims 1-12 are disabled on the Scorpio...
Happy to hear that it is working!
Just curious on how this works with your Scorpio: do you need to set the Scorpio to some kind of "remote control mode" and then you're able to control the buttons and channel faders...
Not being familiar with the Mackie MCU protocol but a bit with MIDI in general, decided to look into this stuff.
On this page I found the mapping for the faders:
Then looked into the Doxygen documentation of the...
Yes, the Teensy LC will be fully booted and executing its program earlier than the RPI will.
A possible solution could be to have the Teensy wait for the RPI by means of the Serial.available() function. The RPI, after...
Yes, true. Interestingly, on page 3 of the article referenced by the OP, the code for the Teensy 3.5 only calculates direction and speed, not distance (yet).
To me it's a 3-bit Gray code without state '000' and...
The regulator on the T4.1 that supplies the 3V3 is short-circuit tolerant.
But the CPU, powered by that same 3V3 regulator, would definitely not be happy with even a momentary 5V on its power pins.
Paul
Find latest posts