Hello guest, if you read this it means you are not registered. Click here to register in a few simple steps, you will enjoy all features of our Forum.
This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Transmitter not being recognized by windows as a controller, but inputs are working
#1
I feel like I'm going crazy here. I spent a solid 2 hours going through teaching myself how betaflight works, what COM ports are, how to connect my FC to the PC via Betaflight, downloaded and used the Impulse RC Driver Fixer,etc etc. I have struggled to get this working and finally got it to the point where it was correctly showing up as usb_hid_cdc = on which is what all the tutorials say is the final step. My issue is that this seemingly has done NOTHING. The transmitter does not show up as a controller on Windows (In the Game Controllers settings window) and doesnt show up in my Sim or on Steam.


I have googled this a million different ways and everyone seems to either have issues with getting the transmitter to be recognised by Betaflight (which I know isnt my problem because it is showing the inputs correctly), or forgetting to do the little CLI command, BUT NOT THIS. What am I missing? I'm tearing my hair out here.

I have tried updating my firmware, 2 different ways (using the Online automatic method, and by finding a file from a tutorial to manually upload). I then struggled to rebind my transmitter but I finally got that going again. I lost and found one of the tiny screws I needed to remove because I couldnt find something that could reach the BIND button. I hate this so much.

Please help me I'm losing my mind. 4 hours on this, I just want to be frustrated at my flying ability, not this impossible tech troubleshooting nonsense.
I'm using a Tinyhawk2 with E6 transmitter. My Tinyhawk is connected to the PC with a usb controller, the transmitter is not. The transmitter is fully charged and has a solid green light. The inputs from it are all correctly showing on Betaflight.
Reply
Login to remove this ad | Register Here
#2
What exactly are you having issues with?

It sounds like your radio is successfully bound to your Tinyhawk (ie you see stick movements in BF configurator receiver tab) which is a good sign. For future reference, as the TH2 has an SPI receiver, you can put it into bind mind from BF configurator. Depending on the version of BF, there may be a BIND button on the screen in the receiver tab, or you can go into the CLI tab and type bind_rx (the command maybe different for older version, you can type "help" to show all the commands).

You do not need to plug in your transmitter to your PC, unless you want to update something or plan to use it for a simulator which could be a littlle more complex and require the correct drivers.

If you are not getting video in your goggles, you need to make sure you plug in the lipo to the drone, and if your goggles have a scan/search button it should hopefully take you to the correct channel. Otherwise check the VTX tab in BF and on some drones you can set the video band/channel there and match it in your goggles.

Drone setup can be a little overwhelming when things are not working, sometimes you need to take a break and then come back later.
Reply
#3
(31-Jan-2024, 12:48 AM)mstc Wrote: What exactly are you having issues with?

It sounds like your radio is successfully bound to your Tinyhawk (ie you see stick movements in BF configurator receiver tab) which is a good sign. For future reference, as the TH2 has an SPI receiver, you can put it into bind mind from BF configurator. Depending on the version of BF, there may be a BIND button on the screen in the receiver tab, or you can go into the CLI tab and type bind_rx (the command maybe different for older version, you can type "help" to show all the commands).

You do not need to plug in your transmitter to your PC, unless you want to update something or plan to use it for a simulator which could be a littlle more complex and require the correct drivers.

If you are not getting video in your goggles, you need to make sure you plug in the lipo to the drone, and if your goggles have a scan/search button it should hopefully take you to the correct channel. Otherwise check the VTX tab in BF and on some drones you can set the video band/channel there and match it in your goggles.

Drone setup can be a little overwhelming when things are not working, sometimes you need to take a break and then come back later.

Thanks for the reply! Totally agree about it getting overwhelming and needing a break sometimes. I woke up in a cold sweat this morning and bounced out of bed ready to try more things and its just making me more and more frustrated....

You're right though, it DOES sound like its successful, but I cannot get the transmitter to work as a game controller on my PC for use in the Sim.
The inputs all work on BF, and I can set usb_hid_cdc = on, but then when I enter save and the FC reboots, my PC doesnt recognise it as a joystick controller.
It seems that there are 0 people out there that have experienced this because I have clicked on what feels like 100s of posts and ready so many comments and everyone's controller just seems to work at this stage. I cant work out why mine doesnt.

I have tried messing around with reinstalling drivers with Zadig, I have used the ImpulseRC driver fixer several times. I have tried to bring everyone back to stock and start from scratch. Nothing works. Granted, I dont REALLY know what I'm doing, I'm jsut following advice from people online who have had similar issues.

https://imgur.com/a/NMvgZAr Here is a shot of my Device Manager, I think it may be an issue that after I set usb_hid_cdc = on that the FC still shows up as a COM port? (Its the COM6 one that is the real one, the COM7 one doesnt do anything). Really not sure if this is helpful information.

If you have ideas of how I can get this to work, undo something small I may have done causing this issue, or just a best guess of what to try next that would be so awesome. I KNOW this can work because I've used this exact hardware on my previous PC, theres just something small I'm missing here.
Reply
#4
It seems the Emax radio does NOT connect to the PC as an input device, you have to connect the Tinyhawk FC to your PC to act as a go between to make the link. What a convoluted way, personally I would not want to leave an AIO plugged into the PC for a long time except maybe if you had a spare board with a dead ESC. There are plenty of other better budget radios that you can plug directly into your PC and use with simulators without going through such fuss which might be worth considering.

If you really want to do it though, maybe these video will help.

Reply
#5
(31-Jan-2024, 07:39 AM)mstc Wrote: It seems the Emax radio does NOT connect to the PC as an input device, you have to connect the Tinyhawk FC to your PC to act as a go between to make the link. What a convoluted way, personally I would not want to leave an AIO plugged into the PC for a long time except maybe if you had a spare board with a dead ESC. There are plenty of other better budget radios that you can plug directly into your PC and use with simulators without going through such fuss which might be worth considering.

If you really want to do it though, maybe these video will help.


Thanks, yeah I know all of that. I have been trying to do the exact method in these videos and dozens more like them. None of them can help me with my final hurdle which is that enabling the usb_hid_cdc = on DOES NOT activate the transmitter as a controller. The transmitter inputs work in BF but entering that command doesnt do what its supposed to do. I'm at a dead end here. The really annoying thing is that I've done all this before and its worked so I know it can be done. I just cant work out what I'm missing.
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  Where can I find the Mamba F722_2022A controller factory presets? phelipems 2 135 10-Apr-2024, 03:55 PM
Last Post: phelipems
  Betaflight Configurator Windows - Bluetooth Connection norseman73 1 214 17-Mar-2024, 02:55 PM
Last Post: SnowLeopardFPV
Sad Mac/Betaflight no longer recognises Flight Controller after flashing Sev 1 221 02-Mar-2024, 03:31 PM
Last Post: Sev
  There is no beeper signaling that the transmitter is turned off. Plohish 6 203 29-Feb-2024, 12:38 AM
Last Post: hugnosed_bat
  No Transmitter Inputs (Crossfire) ETDroneHome 9 428 31-Oct-2023, 06:59 PM
Last Post: SnowLeopardFPV


Login to remove this ad | Register Here