Shop OBEX P1 Docs P2 Docs Learn Events
Help Needed: Gamecube Controller Interface — Parallax Forums

Help Needed: Gamecube Controller Interface

VanceCustomsVanceCustoms Posts: 4
edited 2010-03-30 19:07 in Propeller 1
I downloaded the Gamecube v1.2 object from the object exchange. I wired my gamecube controller properly. I compiled and loaded the demo program into the EEPROM. I ran the demo. With a controller plugged in, there is nothing but zeros on the TV screen for all of the buttons. With the controller un-plugged, (data line open) numbers change at fast speed, indicating all the buttons are being pressed over and over. Plug the controller back in - all zeros.

Has anybody else used the Gamecube v1.2 object with any luck? I don't even know what to check for. The pin must be getting read, its just with the controller actually plugged in there is no communication established. And without it plugged in, there is random Smile data - which makes sense I guess with the data pin "floating".

Any help??? What should I be checking?

Thanks,

Josh

Comments

  • CassLanCassLan Posts: 586
    edited 2010-01-31 14:43
    I would agree that the pins are probably floating when not plugged in. You sure your supplying proper power? to the controller?

    Vance, you are aware that diagram of connections is for the console side, not the controller?

    And Welcome to the forums!!

    Rick

    EDIT - Also it shouldn't be giving garbage data or floating because you should have the pull up resistor on the single data line right?

    ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
    PrEditor·- Text Editor


    NYC Area Prop Club







    Post Edited (CassLan) : 1/31/2010 2:56:37 PM GMT
  • VanceCustomsVanceCustoms Posts: 4
    edited 2010-01-31 20:56
    I know the controller is getting power, because when I plug in a wireless "wavebird" controller the power LED lights up. It only uses 3.3v, GND, and the data line. Those are the only 3 lines I am using. I disregarded the 5v line.

    I have a 1k resistor in series with the data line. I just re-read the comments in the .spin file and it does say "pull-up".... I guess I didn't catch that. I have so many other devices connected at the same time that require series resistors, that I forgot that some things need pull-up resistors... which are obviously different. Duh. I will go try that.

    Thank you for the reply!
  • VanceCustomsVanceCustoms Posts: 4
    edited 2010-02-01 00:49
    I tied the data line straight to the propeller pin, and connected the 1k resistor at the same point, and tied it to 3.3v for a pull up resistor. I am still receiving no data on the TV. Nothing but 0 0 0 0 0 0 0 0 ....

    I am pretty sure their is communication between the wireless Gamecube controller and the receiver because the every time I press a button, the LED on the receiver blinks indicating that a button was pressed. I also tried a standard wired controller just to eliminate the possibility of the wireless controller adding some unknown complication... but same result: 0 0 0 0 0 0 ...

    What else should I be doing?
  • ArchonArchon Posts: 2
    edited 2010-03-30 17:12
    I am having the exact same problem, what pin are you using for the communications line? Looking at the spin code its hard to determine which pin the prop is utilizing for data.

    I've tested the controller itself and it seems to be broadcasting a signal but the Prop isn't reading it. Has anyone had a successful experience with this code?
  • VanceCustomsVanceCustoms Posts: 4
    edited 2010-03-30 19:07
    I have been working on other parts of my robot since then. I gave up on the controller for awhile. But tomorrow I am going to hook it up to a digital storage oscilloscope (by itself) and record the waveforms of the data output. I am then going to connect the GC controller to the robot circuitry and record more waveforms. This will tell me if the robot is receiving the correct waveforms. Hopefully with this comparison of data, I can determine what kind of pull-up, pull-down, etc. resistor is needed. Maybe these is other noise introduced somehow by other parts of my (and maybe yours?) circuit. Maybe I need some kind of capacitor to filter this noise? Maybe something else is going on that I haven't even thought of yet. I won't know until tomorrow.

    I will post anything that I figure out.

    Josh
Sign In or Register to comment.