Hi, sorry I haven't been in touch in a day or so. My internet went down. Something about paying the bill? ... IDK ... Anyway...
Thanks. Working with the PS/2 protocol is actually sort of amusing so far. And I could probably recycle the routines for some other things too. So I do get some small reward out of doing this. I also didn't really know that it was a bi-directional protocol. That is useful information, I could use that as an alternative to some RS232 serial projects probably, though I don't really need to.
Look i am happy to build the circut and i will just put in a IC socket and program a chip to test if it doesnt work ill toss it in the bin and get another happy to do it.
OK, Yeah, I may as well have you build the circuit right now anyway, as it will most likely be the same no matter what the software does, so there is no real reason not to. Originally, I was thinking of making you a layout first, then doing the code. That way you could build it at the same time I was making the software, maximize usable time. But it takes me a little while to get you a working layout using my layout creation process, even though the circuit is so simple.
*OFF TOPIC*
I was actually considering asking you if you wanted to maybe do some programming for an idea I had, to sort of "pay off" this help I am giving you. No obligation, I'm mostly doing this for myself anyway, and I don't even know what kind of programming you can do. This would be mostly windows GUI programming I suspect. My idea is making a "circuit layout creation tool", based on dot matrix prototyping board and an electronics graphic library I am putting together. So it's mostly manipulating *.PNG graphics elements, on a grid, with transparency. It could easily get much more fancy honestly, but that's all it needs to be. I'll PM you the details later.
*OFF TOPIC*
Anyway, below is the layout for the circuit you need to build, I used my manual method for making it up. As you can see, the results are quite graphical and quite easy to follow. The down side is the large investment of time it takes to make the layout by hand. It will probably take you less time to make the circuit than it took me to draw this up.
(Note that your exact parts may appear slightly different than what is shown here)
For making it, you will need...
One(1) PIC12X508. (It would be best if it was FLASH, but it looks like you only have the "12
C508's", which are PROM... You may need TONS)
One(1) 8-pin DIP socket.
One(1) Small section of solderable protoboard, at least 7x9 holes.
One(1) Short PS/2 cable, with at least wires/pins 1-3-4-5. For data, ground, Vcc, and clock wires.
One(1) 0.1-1μF decoupling cap. Film/ceramic, doesn't really matter.
One(1) Small signaling LED, 5~10mA. (good for diagnostics, we could use more too)
One(1) 1/4 or 1/8 watt resistor, at 470 Ohms, (for the LED.)
Two(2) 1/4 or 1/8 watt resistors, in the range of 4.7K to 10K ohms. Matching, but otherwise not too critical.
Some wire, solder, flux, soldering iron, digital multimeter, clean work space, and assorted general use tools for clean up and construction.
Let me know when your done building that, or if you need help. I will be doing some hardware tests on my end until I'm convinced a test has a decent probability of success.
Also, use your programmer to rip the blank memory from one of your PICs and post it please. I still need the calibration value, and for some reason what you have sent me so far doesn't have it. You may want to research into how to get that directly from your programmers software. That would be less error prone than looking at the ripped hex honestly.
epicfatigue
sorry about the poor recording, here are the drivers in action i had to make because microsoft doesnt support windows XP64 anymore.... or like ever
:Video:
That looks great. Yeah, I remember not having wireless xbox 360 drivers that worked for PC in general being a problem for quite a while. Always had to use the wired ones and the support there was bad too, couldn't do much with the controller. I ended up making an adapter for the original Xbox controllers and using a hacked driver instead. Worked better than anything else I had ever used up to that point.
Actually (LOL) once upon a time, long before the above, I took apart a PlayStation controller and wired the buttons of that to a regular old PS/2 keyboard. I of course had to wire some of the buttons to things like CTL-SHIFT-Shift et cetera and so forth, so I could hit more than one button at a time. But believe it or not it actually worked fantastically, blew my mind.