Teensy 4.1 as USBHost for radio CAT control help needed

EddieLeo

Member
I am trying to use a Teensy 4.1 to control a radio via the Teensy Host USB port. My understanding and experience of all issues USB is very poor, and finding basic information and guidance seems to be difficult to find, but here is where I'm at.
To verify basic hardware integrity independent of the radio, I connected a mouse to the Host USB port and ran the HIDDevice.ino sketch. It successfully displays a great deal of data (mostly meaningless to me at this point) however, it did clearly indicate "*** Device Connected ***" with the identifying data for the device.
Then I connected the radio to the Host USB port and ran the same test. Again, lots of information which included detecting that it was a Silicon Labs CP2105 Dual USB to UART Bridge Controller with vendor ID, product ID version etc., however, unlike with the mouse connection, it never displayed a Device Connected message.
For some reason, I am unable to copy and paste the information from the serial monitor window which I assume would be pertinent. Not sure what that's about.
So, my questions are:
What would be the next step?
Apparently this is not a "well known" device and hence not supported in USBHost_t36 - is that correct?
Where can I find guidance on how to add support for this device?
After being able to connect to the device, I'm sure I'll have a whole new set of questions, but one step at a time.
Any suggestions or guidance would be appreciated.
 
I am using a Teensy 4.1 to interface with CAT to an Elecraft K3. I am not using the USB port but instead I am using a hardware serial port. This is working very well.

73,

Don K9AQ
 
I am using a Teensy 4.1 to interface with CAT to an Elecraft K3. I am not using the USB port but instead I am using a hardware serial port. This is working very well.

73,

Don K9AQ
I have no doubt that would work fine as the RS232 interface is rudimentary. I'm curious to hear what your use case with the K3 is. I also have a K3, but the radio I am wanting to connect to via USB is an FT-891 which is USB only. The 891 has a very limited front panel UI as compared to the K3.
 
I guess I have not asked the right questions here, so let me try a few different questions.
1. I am under the impression that to make a USB connection, the device must be recognizable by USBHost_t36.
Is that correct, or is that a wrong assumption?
2. USBHost_t36 supports a CP210X device. Is that a unique device type, or does the "X" indicate a "family" of devices that
might include the CP2105?
3. It appears that the purpose of the enumeration process is to provide details on how the host device must interact the end device,
but I have yet to find an explanation in layman's terms of how to interpret that information and use it to create the necessary driver code.
Can anyone point me to a source of information that would help understand this?
I am spending time studying up on the USB spec and how it all works, and it seems to be coming into focus, but with no actual experience
using it, my understanding is incomplete. I'm willing to put in the work, but my time is limited, and a 650 page USB spec document
is not the friendliest resource.
 
I have no doubt that would work fine as the RS232 interface is rudimentary. I'm curious to hear what your use case with the K3 is. I also have a K3, but the radio I am wanting to connect to via USB is an FT-891 which is USB only. The 891 has a very limited front panel UI as compared to the K3.
I am using a TTL to USB with the FDTI chip set. It works great.
I have no doubt that would work fine as the RS232 interface is rudimentary. I'm curious to hear what your use case with the K3 is. I also have a K3, but the radio I am wanting to connect to via USB is an FT-891 which is USB only. The 891 has a very limited front panel UI as compared to the K3.
I using the interface to read the frequency data with the FA command. This also works with Thetis, which I use with my Hermes Lite 2.
 
Back
Top