Search results

seems to work fine with 3 lines per inverter output, thanks! the final testing will be next week, but at home it worked very well.

Thanks, that is good insight. I will build a prototype with 1 or 2 inverters, I don't expect very long distances on the output trace, but I will only know for sure when I am at the museum.

I know, but I need to feed 21 strips in groups of 7, so three data pins each with seven outputs. I thought about 3 74hct14 to get 5 each, then one more hex inverter to make 2 additional outs for each of the three lines. That last „shared“ inverter could also be a 74hc14, right?

thanks, I found 3 74hct14n in my drawer. for 3x7 outputs I need a fourth though, since I can only drive 5 strips per IC. for the additional outputs a 74ac14 should also be ok, since I already pushed the signal with a 74hct14n inverter, right? (I would use the inverted output of the 3 74hct14) I...

thanks, I may even have them laying around somewhere.

here is the link for the amazon thingy...

hi there, I have yet another ws2812 project that involves 21 led strips each 1.5 to 2m long. they will consist of 3 groups of 7 strips. each of the strips in a group will receive the same color and pattern info, so I can use the same pin to control them. this way I will only use one pin per 7...

This project turned out to be simpler and more fun than I thought. In a nutshell it is just an infrared frame (to get touch from a monitor) mounted on a piece of wood and connected via USB-Host to a Teensy 4. The Teensy 4 has some WS2812 LEDs and buttons connected. The Leds show the X-Y position...

I used the spectra-symbol softpots, they have lengths of up to 1000mm, but I used 500mm. This makes for a somewhat "short scale" bass with a scale of 666mmm, but I like it. Also the 500mm pots are considerably cheaper and easier to get then the 750mm model. Make sure not to use the thinpot line...

thanks, I found the adc examples in teensyduino, don't know why I did not see them before...

hi there, this might be pretty basic, but every search points me to the audio library which I think is not the way to go here (but maybe it still is) I want to read an analog signal on a teensy 4.1 which has no audio shield and most pins already used. I don't need audio out, but I need a...

and I spoke to soon! It works fine as long as only 4 midi devices and the mouse are connected, as soon as I connect 5 midi devices and the mouse, it does not work anymore, the mouse does not send any values out... here is again the code (working with 4 connected midi devices, but not 5) //cpu...

thanks for your answer. the solution was much more simple... I had the mouse1.mouseDataClear(); statement in my function before doing anything with the values, which resulted in no changing values of course... accidentally I had the DataClear portion commented out in the first sketch, and that...

hi, I am trying to connect several midi-devices and a mouse (hid) to the same hub and interact with all of them via USBHost on a teensy 4.1 If I upload just the mouse code, the mouse works. If I upload just the midi code the midi devices work. If I try to combine both, only the midi stuff...

ok, if I upload the mouse sketch from the USBhost examples, the frame acts just like a mouse, spitting out x and y values, again obviously no multitouch. I guess I will have to enable multitouch output by sending some specific USB-packets to the frame....

I have connected a USB infrared touch frame to the host port on a teensy 4.1 and I am running the HIDDeviceInfo Sketch to gather some info, below is the Serial output from the startup and then a finger and later two fingers moving in the frame. The touch frame works out of the box on Linux and...

ok, thanks for your answer. I found these a2b/teensy posts around the net: https://ez.analog.com/a2b/f/q-a/569487/master_-ad2428-with-teensy https://forum.pjrc.com/index.php?threads/cs42448-tdm-input.53369/ (post nr. 13) I was under the impression that the a2b standard had been out for quite...

hi there, is it somehow possible to read a a2b stream of audio-data into teensy4 and work with the data? here is a link of the technology: https://www.analog.com/en/applications/technology/a2b-audio-bus.html I am unsure if I would need additional hardware for this, and if it would be at all...

ok, the thread is getting a bit long to follow :) did you also try this after Paul posted the first fix?

yes, if the host could be forced to run at 12mbit, the problems would most likely go away, since Arturia would switch to a different communication.

If I am not mistaken a USB-Midi Device these days is backwards compatible in most cases, so if you insert a cheap HUB, the Arturia may well use a low-power and low-speed mode compatible with Usb 1.1 standards... The teensy on the other hand has a full-blown 480Mbit host port.

yes sorry, you are of course right. I got a bit over excited by the fact that the other bug was resolved. I will have to check but I don't think I have 4 or 5 teensies ready to set this up, but I will check. Otherwise I can write the code, but I won't know if it fails :)

Hi Paul, I had some time to test your fix (both with just ehci.cpp replaced and with beta3) and I can confirm that I get no more hanging notes after switching programs! So your fix indeed seems to work. I have not jet been able to do a long test to see if there are some downsides to this fix...

thanks for this fix, I am abroad and will only be able to check this out the next week. I will post here with my findings...

great! thanks for confirming and checking out. this looks indeed like the same bug. if you can further write a function that receives midi note-on and off messages on the clients *after* the program changes you should see that those messages are garbled (hanging notes, etc.)

Thanks for your answer. Obviously I did not formulate my original post clearly enough. This is not an issue with the synths, and I can wait as long as I want after a ProgramChange, MIDI is still garbled after I issue multiple PC messages to different synths without delay() in between. It is an...

Hi there, I spent the last couple of weeks narrowing down an issue I had with a rather complex USBHost MIDI Setup. (Arduino 2.10 Teensy 1.58.1) Basically I have 5 USB-Midi Devices, A DIN Midi Device and regular USB-Midi all on a Teensy 4.1 one of the usb-midi devices that is connected sends...

any news on this?

hi there, these are some things to remember when migrating projects from 3.x teensy boards to 4.x boards. probably not a complete list, just the things I stumbled over, that are not that well documented (if at all) -analogReadResolution() only works for 8 10 and 12 bits, I had it set to 11 on...

yes, I just did this and it works flawlessly now. I will open another thread and describe what other changes I had to do to the code when migrating from teensy 3.6 to 4.1

and here: https://forum.pjrc.com/threads/69671-Teensy-4-0-4-1-web-pages-need-a-warning-about-INPUT_DISABLE-on-Analog-Inputs i agree it should be mentioned somewhere

this seems very similar to my problem with jumping values, i will try setting the pinmode to input.... https://forum.pjrc.com/threads/68621-ADC-voltage-measurements-wrong-and-jumping-on-Teensy-4-1?p=292724

thanks for your answer. hmm, might have to switch back to teensy 3.6 then. this sudden jump does not at all seem to be noise, it does not jump fourth and back between values, it just jumps at half the supply voltage and continues from there smoothly if i turn the pot further.

as a small addendum. I also tried setting the analog resolution to 11 bit in setup() analogReadResolution(11);, but this is ignored, it still uses 12 bits.

hi there, I migrated a project from a teensy 3.6 to a teensy 4.1 and I noticed a very strange problem: I have set analogRead resolution to 12 bit, and whenever I read an analog pin that should have a gradual increase or decrease there is a sudden jump in the readings at about half the max...

worked like a charm, thanks! i posted in the blog section about it

hi there, just a quick update on this project (still no video) :-( I have changed the midi output of this bass back to normal usb-MIDI client, since I can use it with a laptop directly when I am on the road (touring). Since I wanted a future proof design I also had to change out the teensy 3.6...

well at this point it is probably easiest to hire someone with teensy knowledge to look at the issues. pay him something and make him sign an agreement not to share any code bits... if it did compile at some point it should not be such a big task to get it running again. or share the error...

hi there, for a project I really need all 18 analog inputs from a teensy 4.1 and i2c. until recently I was under the impression that this was not possible but now I see that some of the sdcard socket pins can act as sda and scl pin as well... so as long as I don't use the sdcard functionality...

thanks for your answer. yes I am aware that the teensy has no HDMI out, but maybe the display driver board is "common" and can be somehow hijacked by a teensy... or as I wrote maybe someone else has a suggestion for a similar size screen that I could use with a teensy..

hi there, could a screen like this: https://www.waveshare.com/11.9inch-hdmi-lcd.htm be used with a teensy 4.1? what latency could I expect from the touch interface? since this is usb based I guess it needs some kind of driver, and since it works on windows and linux I think it will be fairly...

sure, then use the analogwrite and ramp it up. not sure why you asked about analogwrite being similar to digitalwrite then? since you want the ramp up it should actually not behave like digitalwrite :)

analogWrite is 10bit by default i believe, so a value of 256 would be rather dim even more so a value of 128. if you want to blink a LED (just on and off) it is simpler to use digitalWrite (the blink example) /* Blink ADAPTED with elapsedMillis for nonblocking blink Turns an LED on for...

and i also measured the 5v line on the HUB. with all devices connected and booted it reads 4.91v. note though that the teensy does not get power from the HUB (which i could enable by means of a jumper) but from the macbook or Mac mini i am connecting it to.

and i managed to catch another example of a "no device working" example. this time i pulled the plug on the teensy soon enough to still catch the beginning of the serial stream. Interface_16x16 Example USB2 PLL running reset waited 6 USBHS_ASYNCLISTADDR = 0 USBHS_PERIODICLISTBASE = 20003000...

and here is one that misses the minitaur: USB2 PLL running reset waited 6 USBHS_ASYNCLISTADDR = 0 USBHS_PERIODICLISTBASE = 20003000 periodictable = 20003000 port change: 10001803 connect begin reset port change: 18001205 port enabled end recovery new_Device: 480 Mbit/sec new_Pipe...

if i enable debug (don't know why i did not think about that before) i get this on a "normal" boot, where everything works: USB2 PLL running reset waited 6 USBHS_ASYNCLISTADDR = 0 USBHS_PERIODICLISTBASE = 20003000 periodictable = 20003000 port change: 10001803 connect begin reset port...

will check that, although only the two axolotis and the typhon take power from the hub, the pulse2 and the minitaur have separate supplies.

ok, since my last post was a bit broad and (therefore) got no answers/ideas, i will try to clarify. i have a 7 port usb hub connected to a teensy 4.1 which is running the following code: (heavily based on the 16x16 example) #include <MIDI.h> // access to serial (5 pin DIN) MIDI #include...

i know this has been a long time ago, but your error most likely is that you need a USBHost usbHost; MIDIDevice_BigBuffer usbHostMidi(usbHost); //<- to host a 480mb device you need the bigbuffer object... elapsedMillis wait;