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: Keyboard Encoder question  (Read 1177 times)

0 Members and 1 Guest are viewing this topic.

Raleigh

  • Bean Counter
  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 271
  • Last login:August 04, 2025, 01:30:01 pm
  • 1-2-3 Kick, 1-2-3 Kick...
Keyboard Encoder question
« on: July 10, 2003, 01:57:36 pm »
I purchased a used hagstrom keyboard encoder, the KE-USB36 to be specific.  It works, I can plug in trackball or hook up bottons and they work, but I am unable to reprogram the buttons.  Every time I configure the buttons and then try to write it to the encoder it says "device I/O error".  I am running on win XP, don't know if it due to software, or if something on the encoder is broke/burnt out.  I emailed hagstrom to see if they had any advice on the matter, and they responded by telling me to send it to them and they would look at it and repair or upgrade it for $25 plus shipping.  I am not really wanting to dump more money into it, hopefully someone may have a suggestion/solution to this, i.e. what usually causes a "device I/O error" in general not specifically to this encoder.  Unfortunatly of the 36 inputs, only about 10 are configured which is why I can't just work with what is currently setup.  Thanks in advance for any guidance.
« Last Edit: July 10, 2003, 02:24:34 pm by Raleigh »

SirPeale

  • Green Mountain Man
  • Global Moderator
  • Trade Count: (+23)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 12963
  • Last login:August 04, 2023, 09:51:57 am
  • Arcade Repair in New England
    • Arcade Game and Other Coin-Op Projects
Re:Keyboard Encoder question
« Reply #1 on: July 10, 2003, 02:42:02 pm »
I'm not sure what program you use to program the encoder, but have you tried doing it on another OS?

Raleigh

  • Bean Counter
  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 271
  • Last login:August 04, 2025, 01:30:01 pm
  • 1-2-3 Kick, 1-2-3 Kick...
Re:Keyboard Encoder question
« Reply #2 on: July 10, 2003, 02:53:51 pm »
I use the software that comes with the encoder to program it, some specific KE-USB36 program that comunicates witht the encoder.  I have also tried it on win 2000 and got the same error.  The computers recognize it fine, its operational to the extent it is currently programed, but every time I try to write to the encoder it pops out the "device I/O error". Err!!  I got so frustrated that I hacked a keyboard just to play on my WIP cabinet, but definately want a keyboard encoder in it for the finished product.

RandyT

  • Trade Count: (+14)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 7014
  • Last login:August 04, 2025, 11:25:58 am
  • Friends don't let friends hack keyboards.
    • GroovyGameGear.com
Re:Keyboard Encoder question
« Reply #3 on: July 10, 2003, 11:10:23 pm »
The only thing I could suggest is that you try a different cable and if you are using an extension, try it without one.

The other possibility is that there is a real hardware problem, since you did state that only 10 are configured.  How can you be certain that the problem isn't that all of the inputs are configured and only 10 are functional?

If you've tried all the OS's that are supposed to be compatible with the software and swapped whatever hardware you can (to include trying it on a completely different computer), it's time to send it in for repair.

Good Luck,
RandyT
« Last Edit: July 11, 2003, 12:16:15 am by RandyT »

Raleigh

  • Bean Counter
  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 271
  • Last login:August 04, 2025, 01:30:01 pm
  • 1-2-3 Kick, 1-2-3 Kick...
Re:Keyboard Encoder question
« Reply #4 on: July 10, 2003, 11:59:03 pm »
Well I think I have tried just about everything, different O/S, different cables, a couple different computers.  Was just hoping that maybe on a longshot someone else had a similar problem with a resolution.  I have to lean towards there being problems with the encoder then.  In one last attemt I think I will take it to the office tomorow and try it on a range of computers, we have ones running on win 95 through XP and all sorts of different hardware configurations.  But looks like I will be sending it away to be fixed.  Thanks for taking the time to read my question/problem and thanks for the suggestions.

Raleigh

  • Bean Counter
  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 271
  • Last login:August 04, 2025, 01:30:01 pm
  • 1-2-3 Kick, 1-2-3 Kick...
Re:Keyboard Encoder question
« Reply #5 on: July 12, 2003, 01:35:30 am »
Well, took it into work, hooked it up to a computer with Windows 98 and it sure enough it wrote to it with no problems.  The user manual states "The KE-USB36 is compatible with operation systems which offer full support for USB devices compliant to USB 1.0 specifications."  I thought that XP wat USB 1.0 & 2.0 compliant, but I am no expert(tried it on two different computers running xp and one running 2000).  So I will just have to configure it at work, once it is configured it functions flawlessly on my XP, just can't write to it.  So with that resolved, back to finishing my cabinet.