niwPSPtoPC v1.1.0

niwPSPtoPC 1.1.0

Version 1.1.0 makes the PSP client substantially more energy-efficient and
resilient while expanding Windows diagnostics, recovery and release quality.

Highlights

Lower PSP power use

The PSP now uses its full 333/333/166 MHz clock profile only while starting,
joining Wi-Fi, discovering the PC or recovering a lost connection. After a
valid pairing acknowledgement it switches to 111/111/55 MHz for steady-state
controller streaming.

Ten seconds after pairing, the client turns off the LCD backlight without
suspending the console. Wi-Fi, controller sampling and UDP streaming continue
normally. SCREEN or HOME restores the saved brightness; the client also
restores it automatically before reconnecting or exiting.

The brightness functions are resolved dynamically through the CFW user bridge.
The EBOOT does not directly import the kernel display driver, preserving normal
user-mode homebrew loading. If brightness control is unavailable on a
particular CFW, controller streaming continues without automatic backlight
control.

Safer networking and automatic recovery

The PSP client now detects an access-point outage, closes the stale UDP socket,
reconnects with capped exponential backoff, recreates the socket and rediscovers
the Windows receiver. HOME remains responsive throughout recovery.

Pairing-ACK processing is limited to 32 datagrams per sender cycle. This keeps
malformed or hostile LAN traffic from trapping the PSP in an unbounded
nonblocking receive loop.

The documentation now covers compatible 2.4 GHz WPA2-PSK connections provided
by recent ARK-4 and ARK-5 CFW releases. niwPSPtoPC only requires a working PSP
network profile, an IPv4 address and local reachability to the PC. WPA3-only
networks remain unsupported, and Wi-Fi client isolation must be disabled.

More reliable Windows controller output

The virtual Xbox 360 target remains present across temporary PSP disconnects.
Inputs are neutralized after 0.5 seconds of silence, while the PSP session is
released after 1.75 seconds. Duplicate and out-of-order packets never roll
gameplay input backward.

Backend failures are classified and recoverable. The application performs one
delayed automatic retry and also exposes a manual retry without restarting the
UDP receiver.

Connection Doctor 2.0

Connection Doctor now combines protocol milestones with native Windows
diagnostics:

• active IPv4 interfaces and network profile category;
• UDP bind and packet-health metrics;
• matching Windows Firewall rule state;
• common VPN and client-isolation guidance;
• pairing, acknowledgement and virtual-gamepad milestones;
• a copyable diagnostic report.

The GUI also provides persistent settings for the bind address, UDP port and
optional PSP IPv4 allowlist.

Release and supply-chain hardening

The release pipeline now uses immutable GitHub Action commit pins, Dependabot,
cancellable branch CI, tag-to-version and tag-ancestry validation, build
provenance attestations and idempotent asset uploads. The Windows executable
contains and verifies a PerMonitorV2 manifest and version metadata sourced from
the product version.

Compatibility

• PSP-1000, PSP-2000, PSP-3000 and PSP Go with compatible CFW;
• PSP Street/E1000 is unsupported because it has no Wi-Fi hardware;
• Windows 10 or Windows 11 x64;
• ViGEmBus 1.22.0 for the virtual Xbox 360 controller.

ViGEmBus has been retired by its maintainers. Version 1.1.0 continues to use
its final signed Windows 10/11 release because it remains the backend required
by vgamepad.

Upgrade instructions

1. Close the previous Windows application and exit the PSP client.
2. Replace the complete niwPSPtoPC directory under PSP/GAME.
3. Replace the Windows executable with the 1.1.0 build.
4. Keep an existing config.ini if it contains a valid UDP port and a send
   rate from 15 through 60 Hz.
5. Start either side first, select the PSP Wi-Fi profile and enter the new
   five-character pairing code in the Windows application.

No protocol or configuration migration is required. Version 1 packet decoding
remains available for diagnostics; current clients use protocol version 2.

Security

Use niwPSPtoPC only on a trusted local network. Controller packets are not
encrypted, and UDP port 47999 must not be forwarded to the Internet. If the PSP
firmware requires legacy WPA, use a dedicated or isolated SSID without access
to sensitive devices. Regardless of encryption, the PSP and PC must be allowed
to communicate directly.

Verification

The release consists of separate Windows and PSP ZIP archives plus
SHA256SUMS.txt. Compare each downloaded archive against the published SHA-256
value before installation. GitHub build-provenance attestations are produced
for the Windows executable and release archives.