Causes:
This is typically caused by updating the firmware on your QuNexus and then not updating the
presets. A firmware update also restores the factory presets to their original states. If you’ve
created your own custom presets using the QuNexus Editor you will need to resend them to
your QuNexus.
Solution:
Update your presets!
To do this, simply send each preset to the desired QuNexus preset slot (A, B, C, or D) in the
QuNexus Editor while your QuNexus is connected (make sure it says “Connected” just above
the QuNexus logo). Once the update is done your QuNexus should be back to normal.
4.3.2 Firmware Update Freezes or Doesn’t Work
It is possible that when trying to update the firmware on your QuNexus the update process
freezes and does not complete. This problem is pretty much exclusive to Windows machines,
most often Windows 8.
Typical behavior is that the firmware update will begin, the shift button will light up blue on the
QuNexus, but nothing else ever happens - it just kind of hangs there. It will seem like the only
thing that can be done is to cancel the firmware update and try again.
Causes:
Why this problem happens is more of a mystery than the other potential problems. Windows 8
users experience this the most, so there is likely something that the editor does that it doesn’t
like very much. You may also want to check and make sure that you don’t
have a bad USB
cable
- it may just be that the bad cable is disconnecting your QuNexus during the firmware
update. You also might want to try plugging in your QuNexus after opening the editor, not
before.
Solution:
If firmware updates are freezing on your machine it may help to try this:
•
Open the QuNexus Editor and connect the QuNexus
•
Begin the firmware update - either by the automatic prompt that pops up, or by going to
the Hardware menu and selecting “Update Firmware”
•
When the update begins and the progress bar appears,
disconnect the QuNexus
for a
second or two and then
reconnect
it
•
You should get a message that your firmware is out of date and needs an update - do so
•
This time the update should go through without issue
58
