DirtiHarri

This is a guideline for install and fixing FBV Control/Monkey 6 detection issues using the FBV MKII Express on Windows 11. Step 1: A. Install FBV Control, Monkey 6, and firmware form Line 6 download page (all current versions). https://line6.com/software/ B. Follow directions in link to allow firmware update offline in Monkey 6 (default.cfg attachment is below): https://line6.com/support/page/kb/general-faq/line-6-monkey-pending-retirement-r1083/ C. Update Firmware in Monkey 6 with firmware file. D. Calibrate device i. Hold D while powering on the FBV. Upon release, the pedal display will read 1. ii. Press and hold the pedal toe switch until the 7 segment display changes to 2. This should occur instantly. iii. Set the heel to the heel (minimum) position, press the D button. The 7 segment display will change to 3. iv. Set the toe position (maximum) and press the D button. The tuner LEDs above the 7 segment display will light. v. Move the pedal and verify that the tuner LEDs sequentially turn off as the pedal moves to the minimum position, and refills when moved to the maximum position. vi. Press D to exit (may need to reconnect). Step 2: Fix for re-enumeration to avoid reconnecting the cable after computer shutdown/reboot. A. locate the .inf file name and location in the directory. i. open device manager. ii. Find FBV Express MKII in Sound, video and game controllers. Right click and select properties. iii. Click on the Events tab. In the "Description" column, there is "Device configured (wdma_usb.inf)" This is the file we need to edit to solve the re-enumeration problem. iv. Locate the wdma_usb.inf file by opening file explorer and selecting you local disk (should be C: drive). v. in search bar, type wdma_usb.inf and find the directory. Should be in a windows directory. B. Copy wdma_usb.inf and save somewhere as a backup in case you make a mistake. (edit windows permissions as necessary) i. in order to have permission to edit the file directory, open a command prompt as admin and enter command with specified directory path (could just be C:\windows if the file is in the windows directory). command 1: takeown /F "C:\Path\To\Your\File.inf" command 2: icacls "C:\Path\To\Your\File.inf" /grant yourusername:F command to find your username: whoami C. Once you have permissions set for the directory, open the wdma_usb.inf file in notepad ++ for easy editing. D. In FBV MKII Express Properties in device manager, go to details tab. Under property pulldown menu, select hardware Ids. Copy you VID and PID to paste in the code below. (Should look similar to this: USB\VID_XXXX&PID_XXXX&REV_0100&MI_00) E. Find the manufacturer name under "Manufacturer" in the property pull down menu. Mine is (Generic USB Audio) F. Find the device name in the property pull down menu. (should be: FBV Express Mk II) G. Enter necessary code where needed: [Strings] ; Non-Localizable MSFT="Microsoft" REG_BINARY = 0x00000001 ; Localizable MfgName="(Generic USB Audio)" USB\VID_XXXX&PID_XXXX&REV_0100&MI_00.DeviceDesc="FBV Express Mk II" USB\VID_XXXX&PID_XXXX&REV_0100.DeviceDesc="FBV Express Mk II" ; Non-Localizable Altec.Mfg="Altec Lansing" [Manufacturer] %MfgName%=Generic_Devices [Generic_Devices] %USB\VID_XXXX&PID_XXXX&REV_0100&MI_00.DeviceDesc%=USB_Install, USB\VID_XXXX&PID_XXXX&REV_0100&MI_00 note: Only enter the code in the wdma_usb.inf where needed. Do not copy and paste and expect it to work. Double check and make sure Your VID, PID, manufacturer name, and device name are correct. H. Enter this code at the bottom. These are install instructions. [USB_Install] CopyFiles=USB_CopyFiles AddReg=USB_AddReg [USB_CopyFiles] usbdevice.sys [USB_AddReg] ; Add any specific registry entries here if necessary I. Save or replace with the edited wdma_usb.inf file in the original windows directory you found it in. (if permission error, make sure to return to step 2B for directions. Step 3: Uninstall FBV MKII Express in device manager to ensure a fresh driver install upon reboot. A. Find FBV MKII Express in Device Manager and go to properties. B. Go to the driver tab and disable and enable the device. You can do this with a devcon command if you have WDK installed. (here are the directions to download devcon: https://learn.microsoft.com/en-us/windows-hardware/drivers/devtest/devcon) The commands would look something like this: command 1: "C:\Program Files (x86)\directory\to\devcon\folder\x64\devcon.exe" disable "USB\VID_XXXX&PID_XXXX&REV_0100&MI_00" timeout /t 2 /nobreak >nul command 2: "C:\Program Files (x86)\directory\to\devcon\folder\x64\devcon.exe" enable "USB\VID_XXXX&PID_XXXX&REV_0100&MI_00" note: you can verify if it worked by checking the device status in the FBV MKII Express device manager properties. If the status is not working, then you are ready for a reboot to install the driver. Step 4. Reboot and run FBV Control as administrator by right clicking and selecting run as admin. This process worked for me and I was able to solve the re-enumeration problem. Hope this helps. default.cfg

Problem: The FBV MKII Express pedal is not recognized by FBV control, nor Monkey 6 software after rebooting computer. This is caused by a number of programming errors from of the Line 6 software. Here is the main source of the problem: 1. Re-enumeration of the Device When the device is first connected, Windows attempts to identify it and assign the correct driver. Sometimes, the initial connection fails to establish the proper communication channel. Unplugging and replugging forces the system to re-enumerate the device, which is essentially a re-initialization process. This can give Windows another chance to properly recognize the device and install the correct driver (or reapply an already installed one). 2. Clearing Communication Errors If the device was experiencing a temporary communication issue, replugging it can clear that error, as the system will treat it as a new connection. This might happen if there was a timing issue or conflict when the device was initially detected, especially if other peripherals or drivers were also being initialized at the same time. 3. Driver Re-assignment Sometimes, Windows will default to a generic driver on the first connection, and replugging the device prompts the system to search for the correct driver again. If Line 6 software is installed and running, it can reassign the correct driver during this second detection attempt. 4. Windows USB Port Initialization USB ports can sometimes have issues with initializing devices correctly on the first connection. By unplugging and reconnecting, you force the USB port to reset and reinitialize, which might resolve any conflicts or errors in recognizing the device. A unplugging and plugging the device will temporarily fix this issue, however the problem will continue when the computer is turned off/rebooted. In order to avoid damaging cable and device female connector from repeated reconnection, I have found a temporary solution through command prompt. Step 1: Download Devcon Steps to Use DevCon: Download and Install DevCon: DevCon is part of the Windows Driver Kit (WDK), but you can also find standalone versions of the tool online. Here's how to get it from the Microsoft website: Visit: DevCon tool documentation. You might need to install the Windows Driver Kit (WDK) if you haven't already. Alternatively, you can search for the tool on trusted sources. Find the Device ID: To use DevCon, you need to know the Device ID of your FBV Express MKII. Open Device Manager. Right-click the FBV Express MKII device and select Properties. Go to the Details tab and select Hardware Ids or Device Instance Path from the dropdown. Copy the device's ID (for example, USB\VID_0E41&PID_5055&MI_00\9&1999b05a&0&0000). Use DevCon to Disable and Enable the Device: Open Command Prompt as Administrator (search for "cmd" in the Start menu, right-click, and select Run as Administrator). Use the following commands to disable and then re-enable the device: Disable the device: devcon disable "DeviceID" - Replace "DeviceID" with the Device ID you copied earlier. - Replace "devcon" with the "directorypath/devcon.exe" Re-enable the device: devcon enable "DeviceID" This sequence mimics unplugging and replugging the device by disabling it and then re-enabling it without needing to physically disconnect it. Notes: If the devcon command does not work, you need to locate the devcon.exe directory and use the directory in place of the "devcon" command in the command prompt. Once this command is successfully ran, you will notice the FBV MKII Express in device manager will not run correctly, nor will FBV control detect the device. This causes the driver to no longer be detected by windows. Step 2: reboot computer Windows will automatically reinstall driver and re-enumerate the device. The device should now be detected by FBV control and monkey 6. Suggestions to line 6: Please create a proper .inf file for the FBV MKII Express rather than having it use a generic usb audio driver to avoid FBV control and monkey 6 not detecting the device because of re-enumeration problems after shutdown/reboot sequence.