Page 22 of 40 FirstFirst ... 121314151617181920212223242526272829303132 ... LastLast
Results 211 to 220 of 400

Thread: xbox360 chatpad, awsome backlit mini keyboard

  1. #211
    Newbie
    Join Date
    Jan 2004
    Posts
    17
    http://www.pinnaclegameprofiler.com/...pic.php?t=3282

    http://a3w.ivory.ne.jp/softwares/xpcc_en.html

    I found these Links i was so happy to get my 360 controller to work, but im sad the Chatpad wont work i was gonna get it too

  2. #212
    Newbie AnimeCommander's Avatar
    Join Date
    May 2008
    Posts
    31
    Quote Originally Posted by Grumbel View Post
    I haven't tried it, but I only looked at the source, but from the looks of it the Xbox360 controller never connects to the PC, instead the Xbox360 controller connects to the Xbox360, which then launches a networked connection to which the PC then connects, the controller events are send over the network connection to the PC.

    So while interesting, it doesn't help with reverse engineering the chatpad, since the PC never talks to the controller, its all handled on the Xbox360 side.
    I'm no programmer, so I'm just throwing ideas out there:

    Then there should be some code on the communication from the chatpad to the 360. He had to take that code and have the 360 forward it to the PC. The 360 app has code to understand the chatpad and the PC app has code to understand the chatpad data on the network connection. So, in theory, you'd have to figure out what is done on either end of the network connection. What does the 360 do to the signal to make the PC able to understand it on the network connection?

  3. #213
    Newbie
    Join Date
    Jun 2008
    Posts
    40
    Quote Originally Posted by AnimeCommander View Post
    Then there should be some code on the communication from the chatpad to the 360.
    That code is all on the Xbox360 side inside the XNA runtime and there is no way to get your fingers on that easily. All that gets send over the network are simple key presses, there is no code that communicates with the chatpad directly, as that is all in XNA. And XNA itself doesn't help you here either, because its a all high-level stuff, i.e. you do a Keyboard.GetState() and you are done, there is no way to dive into the inner working how how GetState actually gets the state or to track what gets send over the USB bus.

    Finding somebody who has a USB protocol analyzer and can snoop the communication between Xbox360 and gamepad would be helpful.

  4. #214
    Newbie
    Join Date
    Jul 2006
    Posts
    10

    Why not normal keyboard ?

    hi guys
    while the technitian work to find a solution like reprogramming the PIC ( a pieces that i know the existance since i read this post. )

    i just want to bring a little dumb approach for the problem.

    you know, many keyboard have been made withing all the year of personal computing trought all technology we can now see many USB and ps/2 keyboard. i cannot beleive that we're unable to find a keyboard working with USB or what that doesnt have a seamless matrix ?! ok i know that actual keyboard have more than 100 keys but if we able to map 80 or 90% of the key the rest can be remapped on windows...

    well i might be away from the road but it's one idea i got !

  5. #215
    Newbie
    Join Date
    Feb 2008
    Posts
    4

    *#@!!

    ....guys....are you damaged? I posted a link to the source code of a firmware replacement months and months ago, but people continues crying "we'll never reach to do it" until some jz321 comes out claiming my work as his own... the first and unique firmware replacement for ChatPad is mine: use it as you like (it's open source) but notice i'm not paid for it, leave me glory at least!

  6. #216
    Newbie AnimeCommander's Avatar
    Join Date
    May 2008
    Posts
    31
    Quote Originally Posted by jean80 View Post
    ....guys....are you damaged? I posted a link to the source code of a firmware replacement months and months ago, but people continues crying "we'll never reach to do it" until some jz321 comes out claiming my work as his own... the first and unique firmware replacement for ChatPad is mine: use it as you like (it's open source) but notice i'm not paid for it, leave me glory at least!
    Yes, I am "damaged". Please move along and try not to stare too much. Thank you.

    Anyway, you posted a full replacement with links that now seem to not work. I've read your thread at ps2dev.org as it and the youtube link are the only ones still working. You've replaced the firmware on the chatpad it's self. From what I've understood of this thread, we're trying to get the PC to recognize the chatpad as is. That would make it much easier for the less technical to gain the use of it. If in your workings you have found why the chatpad appears nonexistent to the PC, by all means, share it. Your efforts, although appreciated, are for a very specialized use. I would think all the parts, time, and work would negate the benefit of such a small inexpensive keyboard for the PC. I could buy one of the same size and features for the PC for the equivalent in cash and have it simply 'plug and go'.

    Please explain you work in more detail if it really does help us get the PC to recognized the chatpad through the controller (wireless preferably over wired) as is.

  7. #217
    Newbie
    Join Date
    Feb 2008
    Posts
    4
    Yes, I am "damaged". Please move along and try not to stare too much. Thank you.
    Don't expect me to apologize: you all know what i did mean.

    I'm not here to teach anything...if you really want to use my code, open it and learn how it works (yes, links quitted working 2 days ago due to mantainance problems...but that's not the main point). If you feel that's too much work for you then resolve your problem another way: i'm not claiming you MUST use my work. I'm only saying that my firmware do exactly what that troll says: it outputs ascii characters, scan codes and it's ready to have ps2 implementation, too. But when i said to look at it the first time, no one did care; au contraire now everyone seem to wait for him. My message was mainly aimed at a person who probably knows nothing about reverse engineering but can boast of his "great knowledge" showing off my work or some derivate just because you all are too bored to bother read a post or follow a link.
    Consider that if an open-source scene do still exist, it's because some people are still correct.
    Now jz321 don't come saying that your work is parallel to mine: i don't believe in coincidences. At first i wondered:"maybe he's on my same way..", but then i read carefully your post: maybe you don't know, but icProg is not able to program pic16f883 and you're probably saying you used it (that's impossible) because you misunderstood a post of mine in wich i remember i was talking about it. At the very end, PicPgm, too is not able to do it, or at least it's not able to do it without my configuration add-on that has a comment "pic16f883 configuration for chatpad hack by jean", distributed together with my openKeyboard firmware package. Ps2 implementation is absent from my firmware because i don't need it so hard and i was waiting for feedback about its need. Maybe you was waiting for me to do it.
    PPS:TO ALL YOU GUYS: how can someone of you say that having chatpad reflashed takes too long when we are speaking in a 15 pages topic???? Believe me if you trust my skill: chatpad seems to implement an high-speed proprietary comm protocol that accidentally runs over pic's RX-TX lines. It requires veeeeery long to reverse its software completely and write some sort of driver on PC side. Way more long than building a programmer and reflashing firmware.
    Said so, do whatever you want.

  8. #218
    Newbie
    Join Date
    Jul 2006
    Posts
    10
    well i didn't know that my "dump post" would provoke someone.

    Jean80 i readed your "chatpad.c" and i understand a small part of it.. but anyways i know what this code do. but, sorry if my post provoke you. i was only trying to submit a dumb approach... to solve the main problem of this discution.

    cause like others, i want to see that pad in my car connected to ps/2 or USB

    i don't know why but i've wished that keypad would be easy to mod, like th original Xbox controler that we have to skinn the cable, fit it to USB and TA-DA...

    if someone can complete Jean work Go ahead here's the code :

    Code:
    // FIRMWARE REPLACEMENT FOR CHATPAD's pic16f883.....
    // see attached documents to learn more
    // first release from jean (jean[at]ecando.it www.ecando.it)
    // for the Open Keyboard Project
    // thanks alot to Gidi (who owns an half of my chatpad)
    // and my sweethart piceta; they helped me handling
    // cable knots while testing.
    
    const char map[4][49] = { //////// CHARACTER MAPPING MATRIX
    // normal char press
    {56,  57,  48,  13, 112,  44,   0,
      0,   0,   0,  46,  32, 109,   0,
      0, 122, 120, 118,  99,  98, 110,
     97, 115, 100, 103, 102, 104, 106,
    113, 119, 101, 116, 114, 121, 117,
     49,  50,  51,  53,  52,  54,  55,
    107, 105, 111,   0,   0, 108,   8},
    
    // shifted
    {56,  57,  48,  13,  80,  44,   0,
      0,   0,   0,  46,  32,  77,   0,
      0,  90,  88,  86,  67,  66,  78,
     65,  83,  68,  71,  70,  72,  74,
     81,  87,  69,  84,  82,  89,  85,
     49,  50,  51,  53,  52,  54,  55,
     75,  73,  79,   0,   0,  76,   8},
    
    // green alt
    {56,  57,  48,  13,  41,  58,   0,
      0,   0,   0,  63,  32,  62,   0,
      0,  96,  39,  45, 187, 124,  60,
    126, 154, 123, 168, 125,  47,  39,
     33,  64, 128,  37,  35,  94,  38,
     49,  50,  51,  53,  52,  54,  55,
     91,  42,  40,   0,   0,  93,   8},
    
    // red alt
    {56,  57,  48,  13,  61,  59,   0,
      0,   0,   0, 191,  32, 181,   0,
      0, 230, 156,  95, 231,  43, 241,
    225, 223, 240, 165, 163,  92,  34,
    161, 229, 232, 254,  36, 253, 249,
     49,  50,  51,  53,  52,  54,  55,
    169, 236, 242,   0,   0, 248,   8}
    };  ////////// END OF MAPPING MATRIX
    
      unsigned char AMask = 0;
      unsigned char BMask = 0;
      unsigned char data[] = {0,0,0,0,0,0,0};
      unsigned char oldData[] = {0,0,0,0,0,0,0};
      unsigned char sc = 0;
      unsigned char idx = 0;
    
      // alternates (shift,green,red) mapping to translation map
                            // 0  1  2  3  4  5  6  7
      unsigned char alts [] = {0, 1, 2, 2, 3, 3, 3, 3};
      unsigned char alt;
    
    void main() {
    
      OSCCON = 0x67;                    // 01100111 - 0110 stands for 4Mhz internal clock
    
      ANSEL  = 0;                       // Configure AN pins as digital I/O
      ANSELH = 0;
      
      PORTA  = 0;                       // init port A
      TRISA  = 0;                       // 1 = input
      
      PORTB       = 0;                  // initialize PORTB
      TRISB       = 255;                // designate PORTB as all input
      OPTION_REG = 0;                   // pull-ups enabled
    
      PORTC       = 0;                // initialize PORTC
      TRISC       = 0;                // designate PORTB 0-7 as output
    
      USART_Init(9600);              // Initalize USART (9600 baud rate, 1 stop bit, no parity...)
                                     // hope will override 0s set with PORTC=...
    
    //----- TEST ------------------------
        USART_Write('O');
        USART_Write('K');
        USART_Write('.');
        USART_Write('.');
        Delay_ms(100);
    //------------------------------------
    
      do {
         idx = 0;
         sc = 0;
         PORTC = 1;
    
         oldData[0] = data[0];
         oldData[1] = data[1];
         oldData[2] = data[2];
         oldData[3] = data[3];
         oldData[4] = data[4];
         oldData[5] = data[5];
         oldData[6] = data[6];
    
         for (AMask=1; AMask<128; AMask<<=1){
             PORTA = ~AMask;
             data[sc] = ~PORTB;
             for (BMask=1; BMask<128; BMask<<=1){
                 if (data[sc]&~oldData[sc] & BMask) USART_Write(map[alt][idx]);
                 idx++;
             }
             sc++;
         }
    
         alt = alts[data[2]&1|((data[1]&1)<<1)|((data[0]&64)>>4)];
      } while (1);                   // endless loop
    
    }

  9. #219
    Newbie
    Join Date
    Oct 2006
    Posts
    3
    I have read all 15 pages because I too am interested in getting the chatpad to work. Jean80's work in decoding the chatpad is impressive.

    What I really want is a chatpad with a usb interface because I want to use it with my Nokia n800 tablet which has usb host; there's no other I/O on it that would be useful. The chatpad is superior to the Sony version because it has number keys. I've also considered a "nano" usb keyboard but it's too big.

    I guess I could use Jean80's new firmware and then get a usb-serial converter? It'd be nice if the PIC could do a simple usb slave mode.

  10. #220
    Newbie
    Join Date
    Oct 2006
    Posts
    3
    damn, reading the ps2dev site it appears jean80 took down his download site. anyone got an archive of it?

Similar Threads

  1. PDA Mini Keyboard
    By BriansNSane in forum Input Devices
    Replies: 1
    Last Post: 02-08-2006, 07:17 PM
  2. FS....Super Mini Electron luminescent Keyboard
    By Letsride in forum Classified Archive
    Replies: 9
    Last Post: 06-13-2005, 02:18 AM
  3. Industrial mini keyboard -ebay
    By g60 in forum Classified Archive
    Replies: 0
    Last Post: 04-18-2001, 06:51 PM
  4. Backlit Keyboard
    By Caviar in forum General Hardware Discussion
    Replies: 1
    Last Post: 04-03-2001, 09:35 PM
  5. backlit keyboard
    By blkdragon6 in forum General Hardware Discussion
    Replies: 1
    Last Post: 12-03-1999, 11:47 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •