The Usb Device Not Recognized
Dwaine Hawke
The upcoming CCS Theia 1.1.0 release (early July) will have optional support for more device families, including CC13x2. We currently have an alpha build that you can try if you are interested. If so, please start a private E2E conversation with me.
As soon as you try to sign in to existing account (that used to work fine on my older Samsung Galaxy 20), after entering password, it goes to 2 quick screens: We don't recognize this device, then flips quickly to Login Denied.
It has not been resolved unfortunately. I was able to send in a bug report from the phone. Once the error comes up, you shake the phone back and forth several times for a bug form to come up to submit.
I had a second backup email address and when I started the app, instead of using an existing account, I created a new one using the backup email address. All set now. I didn't enable 2FA, as I think that's the cause of the problem, the fact it can't hit your old phone after you've replace it!
I have the same problem since a few weeks with the upper left USB Port. It just works for charging devices but not for transfering any data no matter if I use Windows 10 or Fedora 38. The confusing thing is that if I connect my 1TB Extension Card it works but any other device does not. I also tried disabling and re-enabling all I/O Ports in the BIOS Settings but it changed nothing. My next try would be to disconnect the battery, press the power button a few times so there is really no energy left and reconnect it again.
I was in the process of filling out a support ticket when I was recommended by Framework to checkout this page. It suggested updating my BIOS so I did, and now no more pop-ups! Pretty nice when the support system works haha.
After installing HX EDIT 3.61 bundle I Then installed updater 1.27. From there i updated my helix with firmware 3.60. After installing the firmware I immediately received a message that my usb device is not recognized and it disconnected from my pc. My cable is good. This is the 2nd time it has done this. After the first time it did it to me I uninstalled everything and started over and it did it again. It seems like its a driver issue.
Update 1: I am able to get it to show the driver in device manager using the front usb ports but not the back mother board ports now after it goes to sleep and I wake it up. Only problem now is that it seems like it times out and disconnects.
Update 2: I noticed that my pc can only read my helix for a little while on the front usb ports but disconnects after awhile but It makes no sound that it detects it on the back motherboard usb ports.
That is weird that the POD GO works. My helix will disconnect from HX Edit from time to time and I understand is a known issue. But not as much as it sounds like yours is dissconnecting. Not sure about anything else. Have you tried this on a different computer? Are you able to access one?
This has to be something with the internal configuration of USB ports on different PCs. I have my studio Helix Floor unit connected to one of my main USB ports on the rear of my ASUS PC, sometimes for hours (even overnight sometimes by mistake) and it's never timed out so it's not likely a driver problem, but simply how some manufacturers interface to the USB ports as either a direct connection to the bus versus an internal hub. I'm also on Windows 10 so it's not likely to be the OS itself, but I could see how having certain configurations of the OS or security software could play into it. I have had my Helix Floor stop working as an audio interface on occasion but that's easily fixed by selecting a different audio device such as the internal sound card on the PC then when I reselect the Helix as my audio device it functions fine.
I found a thread somewhere that said to recycle power on both the pc and helix and not just shut down and turn back on so I shut both units down and removed the power cables and eveything else and pressed/clicked on their power buttons to remove any left over power then fired them back up and now my pc recognizes the helix in the back usb ports.
Evey thing seemed to be working fine for a number of hours which was a huge relief but then hx edit did disconnect from helix after a few hours. The good part was that the helix did not disconnect from the pc. I could still see the driver in the device manager and I was not getting an error that the "usb device is not recognized" which is good.
I did however click on the driver in the device manager and clicked on properties and the driver said that it Driver version 1.0.0.7 So i figured that the old driver wasnt over written during the update. So i decided to download version 1.97.0.2 because i see that it corrects a number of windows 10 issues and install that. The problem is that I it still shows up as 1.0.0.7 driver date 12/7/2020 after installing 1.97.0.2 even after i tried to uninstall the device and remove the driver. Is this normal? This may be the whole issue that I need to remove the old driver but it wont go away. I am disconnecting the helix from the pc when trying to remove the driver.
OK so last update on this hopefully! I'm just posting this in case someone else runs into these issues. Hopefully this will help. Ive been using line 6 stuff for awhile now and I noticed I had a lot of old drivers that were never removed still loaded... Including firehawk stuff.. which my go to amp was "Brit 45" I remember I unpacked that thing and in a few short hours after screwing around with a preset I was on stage lovin life lol
Anyway the more i deleted and uninstalled the better things seemed to get. I got it to the point where the computer wasn't disconnecting the helix every 2 minutes by saying "USB DEVICE NOT RECOGNIZED" but HX EDIT was still disconnecting from the HELIX periodically but I could still see the driver in the Device manage unlike before when it would say Unknown device or whatever..
So i backed everything up as much as possible, Uninstalled everything line 6 and did a "Reset this pc". I was tempted to choose "Remove everything" but chose "Keep my files". I figured if it didn't workout then I would go full reformat. After that i downloaded the HX 3.61 update and installed everything listed in the bundle. Once I did that I fired everything up and it gave me connection issues! ugh!
I looked at all the divers and stuff that it installed and I saw A driver for HX STOMP. I figured I don't need that so I uninstalled that and restarted and Ive been stable ever since! Been a few days now.. WHEEEEW!
Well, you must have been connected to your Helix LT when HX Edit detected the update was available. Then when you have the latest HX Edit installed the first thing you are prompted to do before going any further is to create a backup of your entire device. Once you have done that, you can commence the update. You must have bypassed that option?
You are again correct: The directions do not mention the updater. I was checking that the device was visible via USB. It is. Multiple functions work through USB (speakers attached to the XLR outputs are available and work, and the Line6 Updater sees the device). My purpose in opening the updater was to verify the connection. HXEdit does not see the device whether the Line6 Updater is open or not. So, the Line6 updater being open is not the cause of HXEdit not seeing the device.
Here's the punchline: I have another PC with HXEdit installed. I connected the Helix to that PC and it does recognize the device. The first PC still does not recognize the device. My best theory is that something happened during the installation that messed with the drivers. I am going to reinstall and see if that fixes it.
BTW, I do have many backups of my Helix at various stages in development of my patches. I did not get to the point of getting prompted for a backup. I would always take that option. I have put in a lot of work.
Hello, I got my new xcarve put together and i am trying to connect with easel but i keep getting message that usb device not recognized. I had my father in law over messing with driver stuff but we had no luck. any pointers?
I went to arduino and followed the steps on inventables. When it comes to part in tools where you select Arduino in the port mine says COM3. If i go into device manager there it says something like controller 3 i think? I am at work and computer is at home. I did not go onto next step because it is not the same.
I have Luban updated to 13.5.2, I have the latest firmware installed for my A350, and I am now presented with having to choose my device type and module every time I connect. This just started happening today.
I have used CubeMX to generate the USB CDC driver. I connect my board to a computer and the device manager recognize it as: ''STMicroelectronics Virtual COM Port (COM15)'', but it has a error message: ''This device cannot start. (Code 10)''.
I've set up a few simple lighting profiles and switched between them seeing if I could replicate the problem again and thus far it's working without a hitch. Must have just been a driver issue with the initial install, if the situation changes in the future I will inform.
The USB Device message, it will start popping up every half second or so for 5ish seconds, stop for a bit, then start doing it all over again. The lights function fine, but the message popping up like that is unbearable.
I am receiving the same issue. I'm not sure where mine arose as I haven't narrowed it down that much, but figured I might post to see if we could come up with something common between our systems and nail this issue down. I'll be using the keyboard at work tomorrow which will be on Fedora 20, so we'll see how it performs on that OS. I'll reply with results.
03c5feb9e7