i was wondering if there is a way to configure a teensy board to act as a double usb client, so that i can connect two hosts. i guess it is not possible, but maybe i am wrong :) my application:
i have a usb-host...
i was able to find the teensy4 on the hub, i had to use the USBSerial_BigBuffer userial() statement, which is part of the newest USBHost library (but not jet included in 1.53). just in case anyone hits the same...
yes! i can confirm my teensy4 is now found with the BigBuffer in place. i just replaced the USBHost library in my 1.53 install with the GitHub version. I can also confirm that serial communication does not slow down my...
i may have found the problem... teensy4 needs the USBSerial_BigBuffer userial(myusb); for serial communication as well, at least that is indicated on Github in the usbhost examples. my version of teensyduino does not...
no problem! any other insights? should the above code be working i.e. should a serialnr. be printed to the teensy 3.6 console? do i need to set anything special on the teensy4 side?
thanks, i am aware of that.
i have the hub nicely working on the teensy 3.6, all my synths and the teensy4 are connected to it. look at the code snippets above, they contain the hub portion and the midi ports.
this...
i have the following setup:
-a teensy 3.6 with a 7 port usb hub
-a teensy 4 (configured as midi + serial) connected to said hub
-several usb-midi devices connected to said hub
i have it almost all working! all...
ok, since i will need this to be working rather soonish... i thought about using serial communication instead of midi to send data from teensy 3.6 to teensy 4. could this be a workaround for now? at least my code...
well, this was much simpler then i thought it would be.
here are two simple programs that show the problem quite well. an ascending set of notes sent out to all ports on a hub and a teensy 4 with some simple code and...
yes, it happened on unmodified USB code, which is why i started to modify it :-)
for starters i can just upload the whole code of the two boards, and as time permits i will work on smaller versions. the teensy 3.6...
actually setting the tx and rx buffer in usb_desc.h is not a good idea :-) usb-midi communication is also messed up when connected to a macbook air, messages come in as wrong types or simply don't come in at all.
sorry to resurrect this.
so i got a strange problem where my midi controller (a teensy 3.6 sending out via usb-host) becomes very sluggish as soon as i send midi to a connected teensy 4.0
receiving midi from the...
actually i used a teensy 3.6 as host, and had a teensy 4.0 connected to one of the hubs ports. but a teensy 4 as host should also work. the library is really quite easy to use, my 2 small problems were quickly resolved...
Find latest posts