Main > Main Forum
KADE miniArcade 2.0 beta release
PL1:
--- Quote from: Slippyblade on July 24, 2017, 01:54:01 pm ---Is there a "For Dummies" on this yet?
I loved the original KADE. I still have a couple of the minimus AVRs just for it. However, my eyes glaze over completely reading this thread.
--- End quote ---
MiniArcade 2.0 Mapper software won't work with those old Minimus AVRs, but it will work with 32u4 boards, including that Arduino Pro Micro you bought several years ago.
Bad news: If you try to wing it, you'll probably get lost/frustrated trying to use the new Mapper software like the old Loader software. :banghead:
Good news: Like plazma mentioned, there is a User Guide PDF in the .zip file with step-by-step directions.
More good news: We have received an official exemption from the Man Card Bureau -- nobody's Man Card will be pulled/confiscated for reading this User Guide and following the directions. :duckhunt
Read it from the beginning so you get the new/different terms/concepts that you will need to know for the 16 step programming process on pgs 4-5.
LMK if you have any further questions or if I failed to explain anything clearly. :cheers:
Scott
Slippyblade:
Cool, thanks Scott and Plaz. I'll give that PDF a read.
Just to verify though, KADE 2.0 can be used in a similar fashion as the original KADE just with more functionality? So I could actually build, say, a star wars yoke from scratch and use KADE 2.0 as the interface?
PL1:
--- Quote from: Slippyblade on July 24, 2017, 07:32:59 pm ---Just to verify though, KADE 2.0 can be used in a similar fashion as the original KADE just with more functionality? So I could actually build, say, a star wars yoke from scratch and use KADE 2.0 as the interface?
--- End quote ---
Yes. ;D
- Enable analog axes F7 and F6. (page 4, step 2)
- Assign a different port to Button Mapping ID 2 (Button 3) since port D6 isn't available on the Pro Micro board. (page 5, step 6)
There's a chart showing the available ports and labeling on the Pro Micro board on page 12.
- Program the board using AVRDUDE. (pages 13-14) *** LMK if the procedure isn't clear enough. ***
- Wire the buttons to the ports you selected in Mapper and a daisy-chain ground.
- Wire the potentiometers.
-- 5v and ground on tabs 1 and 3 (Arduino pins VCC and GND, swap if the axis is backward)
-- X-axis wiper to port F7 (Arduino pin A0)
-- Y-axis wiper to port F6 (Arduino pin A1)
Scott
djfender:
--- Quote from: PL1 on July 24, 2017, 02:21:40 pm ---I understand that the default pin/port order can be extremely confusing. :dizzy:
It was one of the first issues I brought up to Bruno when he invited me to join him on this project.
If he's so inclined, I'll let him comment on why reassigning/rerganizing/redocumenting all the default pins/ports wouldn't be worth the considerable investment of time and effort.
From a user's point of view, the important thing to remember is that there are several fixed function ports (D7=Shift, B7=Shift Lock), but you can assign any available input port to any output.
I did exactly that for many of the preset mapping (.DAT) files. (See pg. 2 of the User Guide)
For your convenience, there is a "Port_Order.dat" mapping file that has all the ports in alphanumeric order.
If you prefer starting from a blank slate, there is a "Blank.dat" mapping file that sets all Button Mapping IDs to blank.
--- Quote from: djfender on July 24, 2017, 10:18:20 am ---Pin 0 (PD2),2(PD1) and 3(PD0) and 11(PB7) are empty here. thus making my workaround a "Software issue" as some of these aren't available in the default mattairtech build.
Also on the Leonardo, Our ICSP is -Not- Tied to the side pins, thus they'd be PB1 to 3 and I've used these willy nilly in sketches before, therefore there's 3 extra pins, Without hacking up the arduino to free the RX and TX LED.
--- End quote ---
Those pins are all available on the MattairTech board, but most are assigned to other functions.
Fixed function:
PB7 is dedicated shift lock
Ports that can be changed to inputs at the expense of losing console outputs:
The "RJ45" pins (orange squares below) are assigned to autosense/autoswitch between various consoles, making all of the consoles on pgs. 6-7 of the User Guide plug-and-play without reprogramming the board.
You can change these "RJ45" ports from console outputs to control inputs (User Guide pg. 4, Step 2)
PB0 - used by PS1/PS2 consoles (you overlooked this one)
PB1 - used by PS1/PS2 consoles
PB2 - used by PS1/PS2 consoles
PB3 - used by PS1/PS2 consoles
PD0 - used by Wii/WiiU/NES Classic consoles
PD1 - used by most pre-USB consoles
Port you mentioned that is already an input:
PD2 - Assigned to Button Mapping ID 11, used as an input for PS1/PS2, PS3, and XBox.
--- Quote from: djfender on July 24, 2017, 10:18:20 am ---We could swap pin 6 and 13 as 13 possesses its own resistor as this is by default the LED on most arduinos (On my setup pressing "select" grounds said LED and turns it off!)
--- End quote ---
Setting aside the coding/documentation effort involved in swapping just those two pins, how do you plan to make that board-mounted LED visible to users?
If someone wants a visual indicator of whether normal or shifted functions are activated, a separate LED that they can mount where they choose seems like the the most flexible approach and it works right now with any of the 32u4 boards without recoding and without changing the documentation.
Scott
--- End quote ---
oh jeez. the blank.dat fixed all of my silly problems. haha...time to put all my cables back :banghead: :notworthy: :hissy: :laugh2:
PL1:
--- Quote from: djfender on July 25, 2017, 01:07:08 am ---the blank.dat fixed all of my silly problems. haha...time to put all my cables back
--- End quote ---
Glad it worked out for you. ;D
Please feel free to export and post your .dat file for anyone else wanting to use a Leonardo. :cheers:
Most of the current batch of .dat files and pinout images in the "docs" folder are for the miniArcade daughterboard, MattairTech, and Teensy AVRs.
I still need to find a good layout, make .dat files and make pinout images for the Arduino Leonardo/Micro/Pro Micro boards -- they're a lot more work because not all pins/ports are available on them.
Scott
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version