TCB not being found by OP Config

[Jib]

I’m guessing this has something to do with the USB drivers

I downloaded the setup executable for the FTDI VCP for Windows 10, ran it as an administrator, the installation program says both the Bus/D2XX Driver and the VCP Driver are Ready to use.

When I plug the TCB into my computer, nothing is detected by Windows.

When I open OP Config, only COM1 is listed, and it is a communication port. I try to connect, it attempts and fails. When I try to do Snoop, it connects, but no text is output in the Debug window. When I try to connect from there anyways, it also does not work.

I have tried installing the driver a second time, while the TCB is plugged in, but no change. I have tried restarting the computer, but that doesn’t do anything either.

I see in the pictures in the Wiki a USB Serial Port is created, but that is not happening with me.

The TCB is getting power, I have a PWM RX plugged into it via a PPM converter, it’s getting power, the orange USB LEDs briefly flash upon plugging the TCB into the computer. The green and red LEDs flash a little and then go dark. Only the blue LEDs flash remains blinking.

Any suggestions?

[Sub]

Hi,
I have had this issue quite a while back now,
It was for me traced back to an inferior USB cable connector not making the correct connection, i tried a better quality one and it connected and was found by the comm port.
There is a lot of info on Lukes Open Panzer forum site relating to and fixes for non connection for info.
Hope this helps.
Sub

[Sub]

Hi,
Forgot to mention make sure dipswitch 5 is in the ON
Position as this allows communication between the Pc and the board.
Sub.

[Jib]

YES! So I just figured this out on my own just now and came to post it, but you were right.

I have experienced this before when trying to transfer data to my radio (TX16S), some USB cords can only transmit power, but not data. This is what was happening to me here. The USB cable I first pulled out powered the TCB when I plugged it into the computer, but nothing else happened. I went and looked to make sure the USB drivers were installed, restarted the computer multiple times, trouble shooted why USB devices wouldn’t be recognized, etc.

Then I changed the cord and heard the magical sound of something being connected and recognized by windows. Started OP Config, and boom, there was COM3, connected, everything seems to be working perfectly now.

Now on to configuring the DasMikro!

[tankme]

I was also going to mention the cable issue, but for some reason I hit refresh and never got back to typing it in.

Glad you got it straightened out though. I will say, once you get your TCB configured...make a backup copy of the config and save it to your computer. Some firmware updates have blown away my configs. Having a backup saves a ton of time.

[Jib]

Thanks for the heads up about the settings getting reset.

I’ve had the same thing happen to me with the Elmod FusionX, which also allows you to save setting profiles. Hopefully I’ll remember to do this with the TCB.

Now I’m having a similar USB connection problem with the TBS software not connecting to the DasMikro Mini. At least I’m making progress. I think there’s another driver I need that’s not the same FTDI one I just installed for the TCB. I’m combing through Rad’s post about the TBS now. He’s made mentions to a driver, but I haven’t found a specific name yet.

[Jib]

So this is not the right area to post this, but I’m going to add it here in case anyone is in the same situation as me in trying to set up the DasMikro Mini and wondering why it isn’t recognized when you plug the Mini into your computer via the USB programmer from DasMikro

You need to go to this website

https://www.silabs.com/developer-tools ... =downloads

and click on the CP210x Windows Drivers link to download the correct driver.

My DasMikro Mini connected and worked as expected after this.