USB/IP adapter laboratory
NFG Connect v0.10

Main tests · Remote screen tests

This is a separate, customer-operated USB transport test.

It uses usbipd-win and usbip-win2 on two Windows PCs. NFG SESSION codes, website cancellation and the screen relay do NOT control this external USB link. The helper runs until stopped or its parent NFG app closes, then attempts to detach/unshare. Verify cleanup. Production integration with NFG authorization and cross-shop routing remains unfinished.

Do not use this for ECU programming, flashing, live vehicle control, or a working customer's truck. Start with an expendable device, then an adapter on a safe test bench with the manufacturer's read-only diagnostic utility.

NFG-managed helper stop

When started with Enable USB (LAN/VPN) in v0.10, Disable USB connection requests normal cleanup using a local stop signal. Policy-refresh failure, owner denial, inactivity and closing NFG also request stop. This controls only that launched helper; it is not remote per-device control. Standalone helpers remain independent. Verify detach/unbind in the console.

1. Two PCs and an isolated network

2. Download and install prerequisites

From a regular PowerShell window in the extracted kit folder, run:

.\Download-USB-Test-Drivers.ps1 -Role Customer
# On the technician PC instead:
.\Download-USB-Test-Drivers.ps1 -Role Technician

The script downloads pinned official packages, compares SHA-256, and requires a Valid Windows Authenticode result. It does not install or change execution/signing policies. If PowerShell blocks the script, record the error; use the official release page for manual download and inspect Properties → Digital Signatures rather than weakening system protection.

usbipd-win 5.3.0, x64 MSI. Run it manually from USB-Prerequisites. Default path: C:\Program Files\usbipd-win.USBip 0.9.8.1, x64 installer. Run it manually. Default path: C:\Program Files\USBip. This release has extensive upstream changes and a reported serial-number-setting issue; regression testing is required.
PCPackage / official source
Customer
Technician

Keep default install paths for this helper. Follow reboot prompts. No vendor binaries are redistributed inside the NFG ZIP; downloads come directly from their publishers. Their licenses and installation terms apply. Download hashes were checked on the build host; Windows signatures/driver loading still need validation on your PC.

3. Restrict the customer's firewall

The usbipd installer creates a service and a local-subnet firewall allowance. Before sharing, restrict it to the intended technician. On the CUSTOMER PC, open administrator PowerShell and use the technician's actual private LAN/VPN IP:

.\Configure-USB-Test-Firewall.ps1 -TechnicianIP 192.168.1.25

Replace that example. The script displays the change and requires typing SCOPE. It disables the vendor's broad default rule and adds a selected-peer TCP 3240 rule for Private/Domain profiles only. It does not disable Windows Firewall, change profiles, or enable a public rule. Review any other custom firewall rules separately. VPN interfaces marked Public will not be covered; have your network administrator configure the intended isolated path. Do not change this to allow all addresses.

4. Start one adapter test

  1. Customer: run Install.cmd first, then launch NFG-USB-Test.exe from the installed NFG folder, or click USB transport test in the updated NFG app. Approve the Windows administrator prompt. Choose action 1 to inspect devices.
  2. Customer: relaunch, choose action 2. Enter the exact BUSID shown for the test adapter (for example 1-2). Do not select a hub, system keyboard, network adapter or valuable storage. Already shared devices are refused. Confirm the network was scoped and type START for this exact device.
  3. Leave the customer helper open. Sharing disconnects local use when the technician attaches. The console prints a recovery unbind command. The test stops on Q/Ctrl+C or when its parent NFG app closes.
  4. Technician: launch the helper, choose action 3, enter the customer's private LAN/VPN IPv4 address. Review the exported devices and enter the customer-approved BUSID. Type START.
  5. The helper uses a one-shot attach, with no persistence requested. It records the imported port. Check Device Manager, then use the adapter vendor's local utility for identification/read-only communication. NFG does not implement RP1210, J2534 or J1939 itself.
  6. Stop the technician helper with Q, then the customer helper with Q. Confirm detach/unbind succeeded. In usbipd list the device should no longer be shared; in usbip port it should no longer be imported.

Do not close the console using X or terminate it during a test. Forced exit/crash can bypass cleanup, and usbipd sharing can survive a reboot. Use recovery actions 5 (customer unbind one BUSID) and 6 (technician detach one port). No broad detach-all or unbind-all action is used.

5. Acceptance checklist

IDWhat to verify
U01Installer hash/signature checks; correct Windows x64 build; drivers load without disabling Windows protections.
U02Only intended peer can reach TCP 3240. Public address input is refused. Wrong IP/device is not used.
U03Customer lists and shares only the selected BUSID; technician sees that exact adapter and imports it.
U04Device Manager recognizes the imported device and its correct manufacturer driver. Local customer use is exclusive.
U05On a safe bench, vendor utility identifies the adapter. Record actual model, firmware, driver, diagnostic software version, Windows builds and result.
U06Read-only J1939/RP1210 test, only if supported by that exact adapter and the vendor utility. Record whether messages are received. Transport enumeration alone is NOT a J1939 pass.
U07Q/Ctrl+C and parent-app closure clean up both endpoints. Verify no persistent share or imported port remains.
U08On an expendable device, test cable/network loss and recover with targeted detach/unbind. Repeat over the intended encrypted inter-shop VPN. Record loss/latency and every error.

Qualify NEXIQ USB-Link 2, USB-Link 3, each VOCOM variant and each DLA variant separately. No all-model compatibility is claimed. Use the manufacturer's matching drivers; the NEXIQ downloader in this kit is not a driver for other brands. Fill USB-Adapter-Matrix.csv.

6. Cleanup and reports

After confirming all devices are unshared/detached, remove the temporary customer rule from administrator PowerShell:

Remove-NetFirewallRule -Name NFG-USB-Test-Peer

The broad vendor rule remains disabled intentionally. Leave it disabled or have your administrator review the final network configuration. Uninstall the third-party packages through Windows Settings if no longer needed.

The helper saves USB-*.txt under Documents\NFG-Connect-Test-Reports for the Windows account running the elevated helper. Review logs before sharing: they may contain local device identifiers and IPs. Send the relevant USB log, USB-Adapter-Matrix.csv and completed Test-Results.csv. Nothing uploads automatically.

NFG Tuning account linking remains blocked

The live identity project is nksexbdztbrhugeufinu. The connected Supabase account still has no permission to inspect it. Reconnect Supabase using an account authorized for that project before mandatory linking can be implemented and tested. The other project named “NFG Tuning” is not substituted. Existing signup remains on nfgtuning.com.

Publisher documentation

Customer USB/IP server · Windows USB/IP client · Client release notes. Reviewed October 23, 2026.