Kontrol S61 MK3 Firmware Update Issue

greylight · 2023-11-16T12:29:56+00:00

There was an error rendering this rich post.

I would like some advice on how to go about updating the firmware for the S61 MK3. About two weeks ago I received my S61 and attempted to update the firmware. Everything went fine until an image like this popped up. Not my image but it was the exact same, just a different installed firmware version I do believe.

I did not know how to power cycle so I clicked retry and closed the updater and retried again to only get the same messaging. Eventually I googled how to power cycle and did that. Then I hit retry and got this exact message. This is from my PC.

At this point I found the trouble shooting guide which at the bottom stated if you see this the product is basically bricked. So, I returned it to the place of purchase and have a new one that will be sent to me tomorrow.

How do I make sure this does not happen again? What steps do I need to take to install this without issue?

Here is my current plan:

Use external power supply this time.
Use a USB C hub to connect to computer this time.

In this process when is it safe to quit the updater? When is it safe to retry?

Here is my system info:

Windows 10 Pro 22H2 Version (Edit - I am on the latest version of Windows and did see the DFU Entry)

i9-12900k

64 GB 3600 DDR4

980 PRO NVMe M.2 SSDs direct into motherboard

Motherboard: ASUS Prime Z690-P D4 (Wi-Fi)

Graphics Card: GeForce RTX 3060 Ti 8GB

1000W Power Supply

I hope someone here can give guidance or maybe the firmware updater has been updated since and this will not be an issue. I really want this to work...really lost at this point.

Find more posts tagged with

Firmware

S61 MK3

Accepted answers

greylight

So my update finally worked!

I think the issue is with my motherboard and the USB C port. I had to get a 65 watt power supply and a cable that was capable of 65 watts. Then I had a USB C to USB 3 dongle plugged into a 3.0 port.

Once I did all that the update ran and did not immediately fail. The update for whatever reason took about 10 minutes and then a moment for the reboot and all is well now.

This is what I used incase anyone runs into the same issue.

Thank you to everyone that assisted and stuck around for my song and dance!

All comments

PoorFellow

https://community.native-instruments.com/discussion/comment/108354#Comment_108354

Very glad the you got it sorted. I did initially also consider mentioning the possibility of the having to use an USB-C to USB 3.0 A adapter , but thought it better to save for if your initial second go attempt did not succeed , especially because it would have been asking you to go buy more stuff that you then might not have needed. Also ,as I wrote in my first answer then it all appear as rather much hit-and-miss depending on the techs involved (chip-set driver , whatever) . And then on top of that then my my own experience with USB 3.0 A to USB-C adapters are that alas a lot of them are not of sufficient quality and in fact then for a phone of mine I had to buy two or three to get one that worked with my phone (actually ended up with one of the same brand as the phone). So in the end then sometimes then because some manufacturer somewhere in the chain of tech do not completely meet specifications or have another or too loose interpretation of same then it all just doesn't work no matter what you do !

Anyway , I am glad that you finally got your setup and your keyboard to work ! Congratulations on that and on your bright idea of trying an/that adapter !

PoorFellow

@Matthew_NI , seeing that you are on-line and in case you are still working on this type of problem then I will just 'ping' you to let you know that the case in this thread were another one were solution for the user were to use an USB-C to USB 3.0 A adapter !

Matthew_NI

Indeed.

USB-C can be fickle, on certain machines. This can affect all peripherals, but particularly ones sending lots of data back and forth, such as a display or our keyboard(s). I've seen this affect about 100 USB-C monitors across an entire business, and am bound by NDA but it appears specific to certain models of computer.

A high majority of the support issues we've responded to (including things like failure to update, connections to software not occurring, inconsistent performance) have been solved with brute force workarounds of the in-built USB-C connection. Meaning: the use of a USB-C hub to bypass the problematic connection on the direct-in ports, and or other method that are effectively the same (adapter).

PoorFellow

https://community.native-instruments.com/discussion/comment/109012#Comment_109012

Thank you for the frank feedback. 🙂

(reminds me of this play "The Importance of Being Earnest, A Trivial Comedy for Serious People" and the movies derived from it) 😉

mchbox

Hello All,

Unfortunately all you said doesn't work, I got brand new S61 MK3, tried to firmware update on MacBook Pro M2, it failed and now I have all the time "Something went wrong, please re-run update"

I tried to restart keyboard and then again update, no luck, what is interesting in comparison to Windows, it recognises keyboard but with the firmware version 0.0.1, so I can hit update, but it fails after 20 seconds, and still have the same on the keyboard screen "Something went wrong…"

I had additional USBC power adapter during update, I do it during another tries , no luck :(

I logged a ticket with support, hope there is some solution on it, cause I've even not manage to get to play on instrument cause it got bricked like that at the beginning.

Regards,

Quick links

Unanswered questions