Jump to content
IGNORED

Developing USB adaptor for Colecovision & Intellivision controllers


dualcam

Recommended Posts

I bought two for myself. :)

 

After lots of scrubbing I got one of my SA controllers working 100% so I'll look into making MESS configuration files for that, the standard CV controllers, and the Intellivision controllers.

 

I have the real systems too so I'll see what I can do about Turbo on the SA controller (didn't know we could use that!).

 

Voch

Edited by Voch
Link to comment
Share on other sites

I just tried the SA controller and Turbo in my real CV and it's no-go, but it makes some sense.

 

The default configuration is Expansion Module #2 (steering wheel and gas pedal) plugged into Port #1 (for analog steering control) and a standard controller plugged into Port #2 (stick for shifting and keypad for game selection).

 

Using a single SA controller in Port #1, the only thing that worked was the gas pedal by pressing BOTH the SA controller's top two buttons, so that's likely the signal sent from the Expansion Module #2's actual gas pedal. The keypad did nothing when I tried to select a game (the game could be programmed to read only the keypad from Port #2, which makes sense) and the dial and joysticks did nothing (I thought the dial might at least steer, but nope...admittedly I didn't spin it a ton like you did, dualcam...the actual steering controller must be much more precise?).

 

The dial inside my SA controller is a disc with two magnets on it perpendicular to two wires. I believe the induction of those magnets over the wires sends the signal that the dial has been rotated. I'm trying to open my steering wheel controller (unsuccessfully...damn stripped screw, but I'll keep working on it) to find out how it sends a signal, but I'm sure it's either something like a potentiometer like Atari paddles or it digitally reports its position like the Atari steering controller.

 

EDIT: found a schematics page for some CV stuff: http://www.theadamresource.com/schematics/

Edited by Voch
Link to comment
Share on other sites

Does the SA spinner, Driving or Roller controller emulation work in MESS? If so, how do you do it? My assumption would be they would use the mouse, but that does seem to do anything. I am changing the controller type.

 

I don't see anything but the digital inputs in MESS 0.145 for ColecoVision. Input (this System) just has pad1/pad2 0-9/./# and P1/P2 up/down/left/right/button1/button2. They could theoretically be added but they're not part of the driver right now. The Input (general) has lots of generic digital and analog inputs but it's up to the driver to respond to them, and it may not.

 

EDIT: The MESS Intellivision driver seems to have all 16 of the disc directions though as well as the pads and three distinct fire buttons (upper, lower-left, lower-right). I'd need to try a game that uses all 16 directions to see if it's necessary to actually map them...the defaults are just to map up/down/left/right.

Edited by Voch
Link to comment
Share on other sites

The SA spinner is 2 magnets and 2 reed switches (magnet just pulls together two strips of metal) that then connect to DB9 pins 7 & 9. It sends pulses in what is called a "quadrature" format.

 

I personally don't have a driving controller, but based on this diagram I found on -

http://home.comcast.net/~tjhafner/Expansion%20Module-2%20-%20Driving%20Controller.gif

it uses the same pins 7 & 9 that the SA spinner uses. Throttle is pin 6 which is standard controller left/right side switch. Pin 3 looks to act as an enable or power on only when it is plugged into the console, and stop battery drain when not plugged in.

 

A beta tester is going to try his driving controller later this week. Work is going on behind the scenes on a version of blueMSX with SA spinner and driving controller support.

 

Appreciate someone working out MESS support. I have found it frustrating at times and have lost most of my interest for it, but realize a lot of people what to use it.

 

Tom

Link to comment
Share on other sites

OK...you know all that stuff already. :)

 

I'm not too worried about not necessarily having driving and Roller Controller support on my Vision-daptors (they just shipped...thank you!) as I'm generally a MESS user. Testing with my actual CV my Roller Controller works fine (the only game that works with it is Slither?...crappy game anyway) but I lack the D-size batteries to try my driving controller at the moment.

Link to comment
Share on other sites

I have received a report of someone having trouble with Sears Super Video Arcade (Intellivision II style) controllers. Not sure why those would be any different. Please try out your Vision-daptors with what controllers you have (Coleco/Int/Sears) and let me know whether positive or negative on how they work.

 

I am going to hold off sending any more out until I can find out if there is an issue here.

 

Tom

Link to comment
Share on other sites

Here's my first attempt at Vision-daptor ColecoVision and Intellivision configuration files for the parent drivers for MESS. Put these files into your MESS cfg directory and make them read-only.

 

To use a clone system in MESS like the Intellivision II for example, copy the config to be the same name as the driver (intv.cfg -> intv2.cfg).

 

 

For ColecoVision the MESS defaults worked for Player 1 joystick and button 1, so I mapped Player 1 button 2 and keypad and all of Player 2's controls. I haven't yet tried mapping my Super Action Controller.

 

SDLMESS for Mac OS X ColecoVision command line:

 

./mess64 coleco -video opengl -skip_gameinfo -mouse -joystick -rompath <romDirectory> -cart <cartPath>

 

 

For Intellivision the MESS defaults worked for Player 1 disc and buttons (confirmed the butttons with Nova Blast, which uses all three buttons uniquely, and I have the overlay to confirm), so I mapped Player 1 keypad and all of Player 2's controls.

 

SDLMESS for Mac OS X command line:

 

./mess64 intv -video opengl -skip_gameinfo -mouse -joystick -rompath <romDirectory> -cart <cartPath>

coleco.zip

intv.zip

Link to comment
Share on other sites

On Mac Books, the joystick is being mistaken for a touch stick/pad. The USB HID spec has provision for “pointer” devices that manipulate the cursor. The Vision-daptor though is not identifying itself as a pointer device, but probably because the Mac is seeing that the joystick is bundled together with a keyboard in a single device, it going ahead and treating it as such anyway. As long as the Vision-daptor is plugged in, the Mac Book built-in touch pad is being over-ridden.

 

The only solution I see is to drop the sending of controller keypad keys as keyboard key presses, and using joystick buttons for those instead. This has been tested to work fine on a Mac Book.

 

So from this point on, the Vision-daptors will ship with “joystick-only” firmware. However, I will be posting the original joystick+keyboard version along with the joystick-only on the web site, and people can download and use which they want.

 

If you have one of the original joystick+keyboard versions and like that, only use Win/Linux, or are otherwise OK with the Mac Book issue, then there is not a need for you to go back and change it.

 

Tom

Link to comment
Share on other sites

Just to clarify - "joystick-only" firmware means the controller disc/stick, side buttons, and keypad will appear to the computer as joystick axis and buttons. The controller keypad is still supported. Didn't want anyone to think this meant I was dropping support of the controller keypad.

 

Tom

Link to comment
Share on other sites

I'm doing a few tweaks with the "joystick-only" MESS configurations so they'll use both the new joystick mappings *and* the MESS key defaults where applicable.

 

For example, on the Intellivison the Player 1 ENTER keypad key defaults to ENTER_PAD (the Enter key on the keypad), but I'll make it ENTER_PAD *or* JOYCODE_1_BUTTON15 (or whatever the joystick-only Vision-daptor key is) so if you don't have the Vision-daptor plugged in at that time the MESS default will still work.

 

These new "joystick-only" settings are actually easier to map to MESS because they exactly match the Vision-daptor defaults for the ColecoVision stick/Intellivision disc and the fire buttons and only the keypads really need mapping.

Link to comment
Share on other sites

Here's the Vision-daptor "joystick only" MESS configurations for ColecoVision (coleco) and Intellivision (inty, inty2) for MESS, but sadly overriding the MESS defaults instead of "or"-ing with them (couldn't get that to work), so they're Vision-daptor-only for the keypads. Install them in the MESS cfg folder and if you want make them read-only so they're not overwritten when you run MESS without the Vision-daptors connected.

 

To use these with a MESS clone system, for example "ColecoVision (Thick Characters)", called colecoa, copy the coleco.cfg to colecoa.cfg and change the <system name="coleco"> line in the copied cfg file to <system name="colecoa">.

Vision-daptor MESS cfg (joystick-only).zip

Link to comment
Share on other sites

WIth the new "joystick only" firmware and the need to now pretty much always map the controller keypad in the emulator, I noticed something I had missed before. The Vision-daptor shows the status of the DIP switches on joystick buttons 5 & 6. This can confuse the emulator into picking those when trying to do input mapping.

 

So I changed the firmware to only show the DIP switches when in "controller test mode". All 'daptor's shipping out with the "joystick only" firmware will already have this fix. For those with the original firmware, you many not encounter this as they are already a good match to the input emulators are looking for and you may not run into the need to do mapping. But I changed this version as well, and the links on the firmware page are these latest versions.

 

Have also noticed some emulator "quirks". Like when mapping up/down/left/right in blueMSX, it reports those as joystick buttons 29-32 which is *not* what the Vision-daptor is sending, but it still plays. And Nostalgia reports NONE, ESC, 1 (keyboard keypress) when mapping the side buttons, though what the 'daptor is sending is the first three joystick buttons. I think will put some notes on the web site about these I as run into them.

 

Tom

Link to comment
Share on other sites

Just to make sure I had the final version I grabbed the latest joystick-only firmware from your page and rezapped my 'daptors. Thanks for the ability to have a joystick-only as the default...it's made my Mac much happier and it's been easier to map (the buttons and sticks/discs are perfect in MESS without any extra mapping...all I had to do was the keypads).

 

Here's my final MESS configurations for the joystick-only firmware. Feel free to host these on your page, dualcam. If I get MESS running on Windows sometime I'll can make ones for the keyboard firmware too.

 

The MESS ColecoVision driver doesn't have ways to map the Super Action controller's extra features (two more fire buttons and the spinner) or the driving controller so they're not mapped in these configuration files.

 

To use these with a MESS clone system, for example "ColecoVision (Thick Characters)", called colecoa, copy the coleco.cfg to colecoa.cfg and change the <system name="coleco"> line in the copied cfg file to <system name="colecoa">. Another example is the "Intellivison II" clone system, using inty2 for inty.

coleco.zip

intv.zip

Edited by Voch
Link to comment
Share on other sites

WIth the new "joystick only" firmware and the need to now pretty much always map the controller keypad in the emulator, I noticed something I had missed before. The Vision-daptor shows the status of the DIP switches on joystick buttons 5 & 6. This can confuse the emulator into picking those when trying to do input mapping.

 

So I changed the firmware to only show the DIP switches when in "controller test mode". All 'daptor's shipping out with the "joystick only" firmware will already have this fix. For those with the original firmware, you many not encounter this as they are already a good match to the input emulators are looking for and you may not run into the need to do mapping. But I changed this version as well, and the links on the firmware page are these latest versions.

 

Have also noticed some emulator "quirks". Like when mapping up/down/left/right in blueMSX, it reports those as joystick buttons 29-32 which is *not* what the Vision-daptor is sending, but it still plays. And Nostalgia reports NONE, ESC, 1 (keyboard keypress) when mapping the side buttons, though what the 'daptor is sending is the first three joystick buttons. I think will put some notes on the web site about these I as run into them.

 

Tom

 

Question on this - I finished my MAME cabinet today. I plugged in all the USB adapters I have and set all the controls for the emulators. Trouble is I have to leave the INTV/CV adapter unplugged. When it is plugged in Windows sees "6" always on. When I try to configure my controls(like ZSNES for example) it sets all my controls to J15(because the "6" is always seen).

 

Will the firmware update you came up with turn this off so I can leave it plugged in with the rest of the adapters? It's the only one for my cabinet that doesn't work and has to be connected each time I want to use it.

Link to comment
Share on other sites

Yes :)

 

You could also run into a similar issue if you have a Coleco SA controller plugged in. Joystick buttons 7 & 8 are the spinner, and those will be on/off depending on the spinner position. So you would either need to rotate the spinner until both 7 & 8 are off before mapping, or use a standard controller when doing the mapping.

 

Tom

Link to comment
Share on other sites

Yes :)

 

Thanks much for the update. I flashed it this morning and have been playing AD&D Tarmin through GameEx all day. All 4 adapters are now plugged in and running beautifully after configurations. I have 2600-daptor, Vision-daptor, Super SmartJoy SNES and Retro-Bit NES adaptors running on top of my X-Arcade Tankstick. Everything is beautiful. :)

 

Will have to post pics today or tomorrow. I finally got my setup completed(for now!). :)

 

Thank you again for a great product!

Link to comment
Share on other sites

I posted in to wrong topic, pardon the dupe for those who've already seen.

 

Hi Gang,

 

Have tested my Visiondapters and all is great with Coleco and original Intellivision controllers [iNTV1].

 

I know they are not inexpensive but don't miss out as I did in past with other efforts by not ordering extra. Strike while the iron is hot is the lesson I've learned with custom adapters.

 

I dealt with Tom a bit off-line and he was able to create custom firmware that allows Visiondapter support for TI 99 4/a Joysticks! I'm using the same exact sticks my cool Mom {may she rest in peace} purchased for me 30+ years ago to play Tombstone City, Alpiner, Tunnels Of Doom, Zero Zap, and more using MESS.

 

The 99/4a firmware is not on his site but contact him, if you're a TI fan you'll be glad you did. Oh and call your Mom if your still lucky enough to be able, I would give anything if I could again.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...