Ipac controller issue

[segaman40]

I have installed a new Ipac controller, PS2 version into a cabinet previously wired with another non-standard USB controller, so most of the existing wiring was already in place, I simply redirected the various wires to their places on the controller.  I did change 5 buttons to the illuminated type, powered from a spare molex, there doesn't seem to be any issues there though.  On booting the PC, the FE, Hyperspin came on OK, but all I could do was to spin the menu up/down with the P1 joystick, no other buttons worked.  I checked each switch with it's corresponding place on the controller with a multimeter, and all checked out as it should.  I saw on the Ultramarc website, that when using a PS2 controller, I'd need to ensure the USB keyboard support, or Legacy USB support, was disabled in the PC's bios.  The nearest I could see in the bios under 'Integrated controls' was 'onchip USB KBC controller' so I disabled that, but it didn't make any difference.

So notwithstanding the default settings don't work, when I try to design a panel that replicates mine, and then try to programme it, I get the message 'Can't open the driver' - this error I thought was caused by the 'onchip USB KBC controller being enabled, but as I say,it didn't make any difference when I disabled that.

All that works is the P1 joystick up/down, and thats all.  I have DL the Passmark keyboard test, again recommended on the Ultramarc site, so I'll look later to see what that yields, but I must be missing something basic, any help please?

[drventure]

I believe theres  a light on the IPAC that should come on when it powers up. Is that light on?

You say the joystick up and down works, but that's not actually connected to the ipac is it?

If those inputs ARE connnected to the ipac, then you're ipac has to be working, at least partially.

Next thing to check is your grounds. Are they all daisy chained properly and connected to a ground on the ipac? It's easy to miss one or to break a connection on the ground chain and then nothing will work.

[segaman40]

Yes, the Ipac has an LED in the centre, provided this flashes twice on boot up, then remains on, I think this signifies all is OK, the Ultramarc site has a whole number of potential errors, depending on the number of flashes after boot up, so I think alls OK as far as thats concerned.

The joystick is connected, as it should be, the wires from the joystick up and down go to points 3 & 4 on the controller, for P1 that is of course.  So yes, you're right, I mentioned in the initial post that all I could do is to spin the Hyperspin menu up and down, they're the only ones that work correctly.

As far as the grounds are concerned, I did check with the multimeter that all positive connections on the switches and joysticks gave a positive response on the controller, and I also checked out every GND connection in the same way, so I checked them all one by one, and as I'm sure you know, you only get the audible response provided you test the same piece of wire.

But, I know what you mean, it's really odd that two connections work as they should.  Before I appreciated fully about notepad identifying the key depressions, I do know all the P2 switches, all 6 buttons, are mapped as they should be, as they registered as they should in notepad.  I don't think it's a GND issue because the P1 joystick buttons up/down are just a part of the daisy chain loop.

Whether this Passmark keyboard test will help, I don't know. I'll see later on when I get the chance to install it.

[drventure]

I usually use the ultimarc programming application to check the functioning and mapping.

If you run it and put it in table mode, you should be able to see each key you press light up, including the joy up/down.

If the joy inputs light there, but none of the others do, they either aren't mapped, or (pretty rare) the ipac is only working partially.

one other thing. You should have the ipac connected to the PC and your PS2 keyboard connected to the ipac passthrough. In the past,  if I had a USB keyboard connected, and tried to program the ipac, I'd get driver errors.

Once I removed the USB keyboard and connected an old PS2 keyboard, I could program the ipac successfully. You may need to reboot in between though.

[AndyWarne]

The OP did confirm by email that the Passmark test showed all controls work.

I think this might be another of the large number of support requests we get which turn out to be Hyperspin issues.

[segaman40]

It does indeed look like the issues are SW related,I had double checked all the wiring connections, but it just seemed odd to me that there must be lots of people all running Hyperspin on their cabinets, and those cabinets will have an ipac controller installed.  My message to Andy was twofold really, one in case he might see something glaring out that I was missing, but also I couldn't understand why the message 'can't open the driver' comes up when I try to reassign the design panel in accord with what the Passmark keyboard test recorded.

In fairness, Andy did respond immediately and suggested I perhaps install Mame, or at least some neutral software other than Hyperspin, just to at least determine whether the default settings are OK.  I think this is a good suggestion, there are no faults evident on the controllers LED, the wiring checks out on a MM, the cabinet does show up up in the keyboard test, so what he suggests makes sense, but like I say above, someone must have this issue sorted out.  I have also tried on the Hyperspin site, there are some good people over there, very helpful and I like Hyperspin very much, so I'll keep trying.  This site is very good too, and I'll be a regular visitor from now on and thanks for the suggestions in the replies.

[Peja]

I assume this isn't the problem but I will advise you anyways.  Check to make sure your chipset drivers are installed in your device manager.  Make sure there aren't any devices that are coming up with the unknown device in there as well.

I had problems with my ipac and other peripherals on my control panel and reinstalling my chipset drivers seemed to fix most of them.  Now my hyperspin works for the most part, just need to find time next week to install hyperlaunch 3.


Good Luck.

[segaman40]

' Make sure there aren't any devices that are coming up with the unknown device in there as well.'

This was another issue that I had been aware of, and it wasn't a factor, but thanks anyway.  I'm quite sure now the Ipac controller is working properly, from it's own LED monitoring to the Passmark keyboard test.  The problems lie within Hyperspin and while I'm sure many have this sorted, I believe many don't, or at least may well have their HS just partially working as you say.  I have used other FE's without too much trouble, but there's just something about HS that bugs me, I like the finished article, I now think also that there are many who for some reason, don't like it at all. perhaps because it can be problematical.  Ah well, thanks for your comments, back to the cabinet.........wonder whether it'll fit through the window (inspired by a video of TNT throwing their unwanted gear off the top of a building lol)

[Peja]

I get what you are saying.....Hyperspin is great looking once it is all configured and ready to go, but getting there and maintaining it is a lot of work.  The other few FE I have tried didn't seem to be that complicated either.

Do you have the newest version of Hyperlaunch?  I was asking questions about my install over at their forums and in order to be up to snuff, I need the newest version which is pretty much a reinstall of everything.  The one guy said the only thing I will be taking with me from the old install is the roms.  All legal roms of course. 


If you are going to fix the problem, you may as well be on the newest version. 

Good Luck.

[segaman40]

Haven't really looked into this Peja, but since your post I looked and thought what the..............   My current version is 2.25 I think, or something like that.  I looked at a Utube video and it's a complete revamp, again, looks superb, but will take a bit of getting through, I won't even have time to look again for the next few days, but then I'll try again

[Peja]

I'm right there with ya.  It is a complete revamp and the person over at the Hyperspin forums told me to wait until after the weekend to install it if I have guests coming into town as it isn't a simple setup. 

It looks like a lot of reading and configuring but once it is done, it should be better.  At least that is what I am hoping.  I did like the change list of things that were improved though so I suppose it is worth it to install.

Good luck to us over the next week or two.

[DeLuSioNal29]

For kicks. I would install a simple front end like Mala or Maximus Arcade to test your setup.

[segaman40]

''It looks like a lot of reading and configuring but once it is done, it should be better.  At least that is what I am hoping.  I did like the change list of things that were improved though so I suppose it is worth it to install.''

Yeah, thanks again Peja, quite a daunting task, till it's done at least, and good luck to you mate, you'll probably get into it before I do, so all the best.  The video on Utube was about 45 minutes long, I didn't watch much or it, and even that, the guy says it's a 'brief' look at things, and he knows all about it being involved in it's evolution.

[segaman40]

For kicks. I would install a simple front end like Mala or Maximus Arcade to test your setup.

I'm going to stick Mame on when I get chance after the weekend, but as I say, I'm pretty sure the issues are within HS.  I have been running MA on another cabinet for a few years now, it is good and reliable, but a bit dated perhaps now.  They really have an opportunity now to expand MA, there'e a lot of potential there and their forums do ask for giving it a kick, but whether they will?  I was about to move onto MaLa when I came across HS, I was impressed when I saw MaLa Blue on someone's machine.

But yes, I'll probably put MA on just to see, cheers