Main Restorations Software Audio/Jukebox/MP3 Everything Else Buy/Sell/Trade
Project Announcements Monitor/Video GroovyMAME Merit/JVL Touchscreen Meet Up Retail Vendors
Driving & Racing Woodworking Software Support Forums Consoles Project Arcade Reviews
Automated Projects Artwork Frontend Support Forums Pinball Forum Discussion Old Boards
Raspberry Pi & Dev Board controls.dat Linux Miscellaneous Arcade Wiki Discussion Old Archives
Lightguns Arcade1Up Try the site in https mode Site News

Unread posts | New Replies | Recent posts | Rules | Chatroom | Wiki | File Repository | RSS | Submit news

  

Author Topic: Ultimate I/O stuck in Keyboard mode after firmware reflash — no LED, PID_0412  (Read 57 times)

0 Members and 1 Guest are viewing this topic.

mark0804

  • Trade Count: (0)
  • Jr. Member
  • **
  • Offline Offline
  • Posts: 2
  • Last login:November 05, 2025, 09:23:48 pm
  • I want to build my own arcade controls!
Hi all,

I’m troubleshooting an I-PAC Ultimate I/O board that’s currently stuck in Keyboard mode after a firmware reflash. Hoping someone here has seen this behaviour or can offer insight.
🧰 Setup & Background
  • Board visually resembles the I-PAC2 layout shown on Ultimarc’s site
  • Previously worked in XInput mode, LED was active, inputs responsive
  • WinIPAC V2 used for mapping and firmware upload
  • After reflash, board now shows as “Ultimate I/O” in WinIPAC V2 (Board attached: uio)
  • LED no longer lights up, hotkey combos don’t work, and XInput won’t activate
🧪 USB Descriptor Info
  • Device Manager shows:
    USB\VID_D209&PID_0412&REV_0056
    USB\VID_D209&PID_0412
  • This PID isn’t listed for standard I-PAC2 or Ultimate I/O — possibly a newer revision?
📎 Screenshots Available
  • WinIPAC V2 layout and status bar
  • Firmware uploader window
  • Device Manager with VID/PID
  • joy.cpl test panel
  • Photo of the board itself
📬 Support Request
I’ve contacted Ultimarc and requested the correct .ufw firmware for Ultimate I/O with multi-mode support. In the meantime, I’d love to hear from anyone who’s:
  • Seen PID_0412 before
  • Recovered from a similar firmware lock
  • Has tips for restoring LED/XInput functionality
Thanks in advance — happy to share screenshots or test suggestions.

Cheers,
Mark
Perth, Western Australia