OctoPrint-FirmwareUpdater VS libwdi

After reading some more seems like you CAN do it, but I was either too scared or didn't know about it in Mid-2021

Firmware Updater Useful for flashing firmware to printer without having to use sd card. Frees up an sd card for me

I have 2 skr 1.4 turbo boards and before I switched to klipper I always updated my firmware using the firmware updater plug in for octoprint. On the github page it guided you through setup for that board family. https://plugins.octoprint.org/plugins/firmwareupdater/

I followed the install instructions from this link. I installed the python 3 compatible version of heat shrink.

Method 3 (Through Octopi) - I installed Anaconda to download the firmware updater for Octopi found here (https://plugins.octoprint.org/plugins/firmwareupdater/) but cannot install it through the command line. I get "python setup.py egg_info did not run successfully.". Tried upgrading pip to no avail.

if you have an Raspberry pi you can try https://plugins.octoprint.org/plugins/firmwareupdater/

I'm not sure if this OctoPrint plug-in works with the neptune 2 but it's worth a shot. https://plugins.octoprint.org/plugins/firmwareupdater/

You need a plugin called Firmware Updater.

Only if you already have Binary File Trainsfer setting enabled in Marlin. So you might be stuck since that's not normally enabled. But when it is enabled, it does work. I only update via octoprint anymore. https://github.com/OctoPrint/OctoPrint-FirmwareUpdater/blob/master/doc/marlinbft.md

They probably use WCID, which is a mechanism for devices to tell Windows that they are compatible with the generic WinUSB driver. Zadig is useful for older versions of windows, non-WCID devices, and when you want to override that auto-specified driver.

Here's more information from the author of Zadig: https://github.com/pbatard/libwdi/wiki/WCID-Devices

If you do that'll bring you here where you'll find everything you ever wanted to know about WCID.

Using this config files from zadig's github page, it (in my case) got all the correct settings from the start and all I need to do is click replace driver. Place the zadig.ini files in the same directory as your zadig.exe. You might have to choose the correct device.

USB descriptors are supported only up to 8.1 according to your link. And libwdi/zadig is useful links for me, thank you very much! I'll be used ones in my other projects. But I don't need to new USB driver in Windows due to I'll get much more problems with put all together in LabView. I want to use standard WIndows USB-Serial that always present and directly supported via VISA. The NI-VISA isn't using specific protocols for USB. The VISA is just an intermediate level for most of the serial protocols in the NI ecosystem. I'm operating low-level USB packets, commands, responses in the same manner as in C for example but from LabView. But I have to generate the specific INF file which needs for recognition of VISA for each one of the specific instances with a unique USB PID/UID. The problem is mandatory signing such INF files in Windows10 and I'm looking for any way to avoid this.