Gadget II Not working. Firmware update wanted.

I'm attempting to set up a Gadget II.

Initially i had a solid green led indicating a successful USB connection, but I had no DMX output (running from either an iMac 10.13.3 OS or a Windows 10 PC) via ETCNomad. I have the current version of Nomad.

I attempted to update firmware and drivers via the PC but couldn't get it to update to the 1.4.2 version. In the maintenance dialog for I/O Firmware Upgrade it never recognized the Gadget when selecting that option. The recognized devices window immediately below that button would recognize it, but when updating via that method it wouldn't change any versions or seem to actually update anything. It would then be in Bootloader as a drive. If I unlplugged and replugged as well as restarted Nomad it would bring me back to where I started.

Eventually I tried a trick of copying the proper firmware (the older 1.0.0.something, not the new 1.4.2 version that I've downloaded) into the Bootloader drive. This seemed to work and the LED blinked red for some time. Eventually (about 20 minutes) of this and I tried running the update methods from the how-to that comes with the IO firmware (1.4.2). No luck.

At this point, the Gadget II now has a solid red light (indicating it's not connecting at all?) and is not recognized anywhere on either computer. I've tried reboots, unplugging the Gadget II (and letting it sit for a few minutes) and about everything else I can think of. 

Do I have a dud, or is there some simple trick I'm missing?

Parents
  • Update, I've got it back to connecting (though that took more creative problem solving than is probably advisable).

    Now I just need to update past the 1.1.0.9.0.4.s19 that it is currently and get it to 1.4.2.

    Is the 1.4.2 firmware update I'm looking at something that is specifically for the Gadget I, or is this actually a Gadget II software?

  • Yup, the Gadget 2 is not 1.4.2, you were trying to install a firmware version that is incompatible with your Gadget...
    Out of curiosity, what made you think you absolutely have to install 1.4.2?
  • OK, that makes sense. I was trying to update the firmware because that was the only path to solve this particular issue that I’ve seen online and the forums. There isn’t much documentation that comes up when searching and ETsee website for gadget 2.

    I have managed to get it working on the PC at this point, though I am not sure what did it. I’m still unable to get the gadget to send out DMX when connected to the Mac. Do you have any suggestions for that?

  • ah, uhm, i'm terribly bad with the bitten fruit kind of computers ;) sorry.

    you could always call tech support. if it's not an emergency you might want to wait for office hours...

    For technical support in the Americas,
    please call 608-831-4116
    or toll-free in the U.S. at 800-688-4116
    service@etcconnect.com

    For technical support in Europe, The Middle East & Africa
    please call (+44) 20 8896 1000
    techservltd@etcconnect.com

    For technical support in Germany, Austria, Switzerland, Eastern Europe & Russia
    please call (+49) 8024 4700-0 during working hours or (+49) 171 733 15 33 for emergency cases after hours.
    techserv-hoki@etcconnect.com

    For technical support in Asia,
    please call (+852) 2799 1220
    techservasia@etcconnect.com
  • To update folks, ETC tech support is stellar, they call back on questions (which is likely why the forums don't have a ton of information on some things):

    I had the Gadget II showing up in the I/O section of the Nomad software, and it shows up when I run System Report (via the apple in the upper left hand of any Mac) as a USB Console I/O HS (the dongle is Sentinal HL). We also had confirmed connection inside of a Primary show. Holding Tab and pressing 99 brings up diagnostics, which showed connecting/disconnecting when plugging and unplugging the Gadget II.

    The end fix was under the Eos Family Welcome Screen - Settings - Local I/O. We need both "Enable" and "Default Output Protocol" checked. This enables the DMX output by default in the Patch settings, which was our easy fix. Something that should normally be defaulted (but might not be re-set during a reload of the software, which we did), but which leaves the patch without DMX by default.

    So, easy fix! One check mark! Thanks for the phone assistance ETC!

  • Hey Reid! Quick correction: that checkbox should NOT get re-enabled when updating software—I misspoke on the phone earlier. I am glad we got you up and running again!
Reply Children
No Data
Related