Gadget II not detected

Let's start with some more info please:

• You're running ETCnomad on Windows. What's the operating systen?
• What's your version of Eos your running?
• The Gadget has an indicator LED, what does it show?

Thank you

I was running 3.2.8 on a PC (Windows 11)

I have since uninstalled and reinstalled 3.1.5.8 from the dongle.

There is no light coming on from the LED on the Gadet II, but if I hold up the Gadget, there is a blinking green LED coming from inside the gadget, as well as a solid green LED from inside the gadget.

Is this a new gadget? There are two hardware iterations, the classic Gadget II and a CPU2 version. If you bought it within the last 12 months check the bottom if it says CPU2.

In that case no LED could mean "Waiting for firmware". In Windows explorer check if you can see a drive you're not expecting to be there, probably labeled "BOOTLOADER".

Last question for now: are you running the Hog 4 PC software on this computer as well as Eos Nomad?

Hello! Yes, it was purchased in the past 12 months. On the bottom it does say CPU2 on the sticker.

I do not see a BOOTLOADER drive.

I am not running any other ETC software such as Hog 4.

Hi there! Could you please uninstall Eos fully and then reinstall Eos as Administrator? It could be the the drivers for the Gadget are getting blocked at install

Hey, not OP, but I've been having the same problem since updating to 3.2.7 and continued to have the problem when updating to 3.2.8. I've run all installs as admin, and even stepped back to 3.2.5 to see if that would fix the problem. Windows sees and recognizes the Gadget in the device manager, but EOS doesn't see it in the shell or in the console. When I originally acquired the Gadget I was running 3.2.5 and it worked immediately upon plugging it in.

Hey, not OP, but I've been having the same problem since updating to 3.2.7 and continued to have the problem when updating to 3.2.8. I've run all installs as admin, and even stepped back to 3.2.5 to see if that would fix the problem. Windows sees and recognizes the Gadget in the device manager, but EOS doesn't see it in the shell or in the console. When I originally acquired the Gadget I was running 3.2.5 and it worked immediately upon plugging it in.

Hi Robin,

When you went back to the Eos v3.2.5 version - did the Gadget work again? If not, then it appears, that the driver somehow got damaged in your windows files.

Let's start with some more info please:

• You're running ETCnomad on Windows. What's the operating system? Screenshot of the Windows About would be helpful. (System Information Page)
  
  
  
• What's your version of Eos your running now? Back to Eos v3.2.8?
• The Gadget has an indicator LED, what does it show?
• Can you post a photo of what exactly the Gadget is displayed as in the device manager?
  
  
  • What Driver Date / Version is listed there for it?
    Please post photo of yours:
    
    
• Can you open Concert on your laptop? Does the Gadget appear as a discovered device there? 
  

Hey Corey, thanks for the response. My Gadget was being detected and sorted under Hi-end Widgets. I uninstalled the driver for it listed there and now it works properly and is listed under USB Controllers. I forgot that I had installed Hog4 PC around the same time that I updated to 3.2.7. When I did it installed it's own drivers and hijacked the Gadget.

I've uninstalled Hog4 for now, however is there a way to have both on the system and both able to use the Gadget without conflicts like this?

I believe this should explain what you're seeing regarding Eos vs Hog.

https://support.etcconnect.com/ETC/Networking/Gadget_and_Gadget_II/Gadget_II_is_not_detected_by_Eos_and_shows_up_in_component_manager_as_High_End_Widgets