Hyper999's PS3 rapid fire V1

[Modded Matt]

12/6/10 this is a re-release of hyper999's PS3 rapid fire. It has been fully tested and proved working on all modles other than the V4 as that board is unavailable to the RND team ATM

a complete download package can be found here:download

First of all i would like to say a special thanks to
geraldrubalcava
Hazer
modded matt
802chives
who were all involved in the development of this code
and last but not least
RDC for his involvement in the development and his board scans

--------------------------------------------------------------------------------

How to use this code

you can edit the speed of each mode in this code just like in bmu by editing the value of FIRERATE1,2,and3 shown here;

Code: [Select]

;***** FIRERATES *****************************************************
FIRERATE1             equ        .167         ;6 sps
FIRERATE2             equ        .250         ;4 sps
FIRERATE3             equ        .125         ;8 sps
;to get desired speed divide 1000 by your desired sps then enter
;it here and recompile and reprogram the code
;Example: 1000/4 = .250
;**********************************************************************change the values to anything from 1 to 255 to suit your needs by downloading the source text file then open in notepad save as a .ASM file.
next open it in mplab and change the values in the code
then recompile by selecting Project> Quick build
finally program the generated hex file into a pic12f683 and install.

--------------------------------------------------------------------------------

When installed to change mode simply tap the tact switch to toggle modes

mode 0 - OFF
mode 1 - led turns on       
mode 2 - led blinks twice 
mode 3 - led blinks thrice

--------------------------------------------------------------------------------

Coming soon
Rapid fire on r2 l1 and l2
burst fire
updateable settings via serial comms
then who knows what else


--------------------------------------------------------------------------------

What We Need From You

bug reports
information on what speed suits what game


--------------------------------------------------------------------------------

I am not responsible for any damage caused to yourself or your console or your controller by installing / using this code

[Modded Matt]

reserved for board schematics

[xSLICKVICx]

does this work on black ops?

[rafaliyo86]

yes, it does. Not as well like mw2 but works

[skittles916]

Hmmmm...... i must be doing something wrong..... as i have tried both on vx4 and the msup4.05 and neither works....

i know the vx4 problems are still the same but i cant find out why my msup4.05 isnt working... checked the wires and all....

[Modded Matt]

i think u have done something wrong, but please go and read the top line ofth thread. everyonehas stated there is no change in the operation of th v4only relocation of  test points. send me your controller and i will verify or fix it for you and send it back

[robert27841]

reserved for board schematics

hi the v4 dose not work

[rockandink]

Got all this installed and up-and-running, but in this version of code, should there be issues with the LED lighting?  e.g.,  faintly lit when off, off for Mode 1, Solidly lit after Mode 3... that kind of thing?  Or, did I get my wiring reversed?

btw, this entire setup with making my own PIC serial programmer and programming and wiring WORKED on the first attempt.  Great vault of info here.

[rockandink]

Quick question... Is the LED wired the same in all controller versions?

[hyper999]

as far as i'm aware yes, though i'm not very aware as it were. on the pad where it wasnt working have you tried both sides of the led?

[rockandink]

... have you tried both sides of the led?

Not yet.  I'm at work, so I don't have my PS3 to link up.

But, when I press the PS button, the 4th LED doesnt flash along with the others--will try the other side of the LED and report back.

[hyper999]

hmmm.... try it although it sounds like on whatever board version you have the led is switched differently and the code will need editing.

[Modded Matt]

I used an external led.

[geraldrubalcava]

recently i got some money and finaly decided to but a new controller hopefully with 4.0 board and make a video and pdf of the process of all my steps. and i do trust my soldering skills and my hacker ability to try to make a clear video and pdf. and if i dont run into any trouble on the 4.0 bard then i can officialy say that it does work for the 4.0 board. It may just be that most people trying this for the first time are getting these new controllers and may not have experience on these. so i will make it a goal within the next week to document every process.

[platanomangu]

im new with the codes, but how can i change the speed to

FM----15 sps
SM----10 sps
TM----5   sps

?????

[platanomangu]

im new with the codes, but how can i change the speed to

FM----15 sps
SM----10 sps
TM----5   sps

?????

anybody??

[rafaliyo86]

anybody??

You have to open the .ASM file in MPLAB and change the firerates

[Modded Matt]

read the origional post, namely this part:

How to use this code

you can edit the speed of each mode in this code just like in bmu by editing the value of FIRERATE1,2,and3 shown here;

Code: [Select]
;*****   FIRERATES *****************************************************
FIRERATE1             equ        .167         ;6 sps
FIRERATE2             equ        .250         ;4 sps
FIRERATE3             equ        .125         ;8 sps
;to get desired speed divide 1000 by your desired sps then enter
;it here and recompile and reprogram the code
;Example: 1000/4 = .250
;**********************************************************************change the values to anything from 1 to 255 to suit your needs by downloading the source text file then open in notepad save as a .ASM file.
next open it in mplab and change the values in the code
then recompile by selecting Project> Quick build
finally program the generated hex file into a pic12f683 and install.

[yasin]

recently i got some money and finaly decided to but a new controller hopefully with 4.0 board and make a video and pdf of the process of all my steps. and i do trust my soldering skills and my hacker ability to try to make a clear video and pdf. and if i dont run into any trouble on the 4.0 bard then i can officialy say that it does work for the 4.0 board. It may just be that most people trying this for the first time are getting these new controllers and may not have experience on these. so i will make it a goal within the next week to document every process.

Any updates?
Did you test this code on the vx4.0?

[platanomangu]

read the origional post, namely this part:

How to use this code

you can edit the speed of each mode in this code just like in bmu by editing the value of FIRERATE1,2,and3 shown here;

Code: [Select]
;*****   FIRERATES *****************************************************
FIRERATE1             equ        .167         ;6 sps
FIRERATE2             equ        .250         ;4 sps
FIRERATE3             equ        .125         ;8 sps
;to get desired speed divide 1000 by your desired sps then enter
;it here and recompile and reprogram the code
;Example: 1000/4 = .250
;**********************************************************************change the values to anything from 1 to 255 to suit your needs by downloading the source text file then open in notepad save as a .ASM file.
next open it in mplab and change the values in the code
then recompile by selecting Project> Quick build
finally program the generated hex file into a pic12f683 and install.

thank you. is working perfect on MW2

[rafaliyo86]

thank you. is working perfect on MW2

What speed do you use for MW2? 10 or 15?

[platanomangu]

What speed do you use for MW2? 10 or 15?

FIRERATE1   equ   .40          ;25 sps
FIRERATE2   equ   .20          ;50 sps
FIRERATE3   equ   .100          ;10 sps

[rafaliyo86]

25sps and 50sps work online???

[skittles916]

Anything on vx4?

im sorry i dropped off the radar for the last 5 months, and i havent been able to touch or even resolder my v4 or v3

wondering what others are still having problems with em or not?

[platanomangu]

Anything on vx4?

im sorry i dropped off the radar for the last 5 months, and i havent been able to touch or even resolder my v4 or v3

wondering what others are still having problems with em or not?

if you are talking about the motherboard MSU_VX4_009Bottomrevised2.jpg, my works plus i have another controller  too

[Modded Matt]

25sps and 50sps work online???

not really this is an illusion, anything over say 25 confuses the controller and causes studdering, but once you get high enough, the controller will see everyother pulse, so peploe say yea, use 50, butt he controller sees 25sps.

[Hazer]

So....

After donating my only VX3.5 to AskaCapper, I have a VX4_0.10 that came with the PS3 I used for testing. Since no one has investigated this 'issue' I decided to download hypers code and try it out.

It works exactly as it should, except for the LED. The LED is backwards:

Mode 1: on
Mode 2: off
Mode 3: blinks then off
Mode 4: blinks twice then off.

I am soldering it to the side of the LED that is not the common (toward the bottom of the controller). I looked through the scans of all the different versions, they all seem to be same. This is not a big deal as the code can be changed to flip the LED output.

As for the RF signal: It works just fine. I had it under the scope for an hour. I pressed R1 as hard as I could. No issues. I dont have a game to play for hours to test R1, but I will keep testing the contorller every day for awhile to see if I can get this 'lock-up' situation to occur that others have reported.

I am using the analog stick power source. If you people keep using the rumble pad, you will regret it. The motor is a major power draw, and is still susceptable to reverse current when the motor shuts off. Its a very noisy power source and it WILL make the PIC puke itself eventually.

I am very surprised. When I hooked this up, I expected to see something wierd. Maybe something different between the VX3.5 and this VX4.0, but they are exactly the same. The power source measures the same. It takes the same load without problems. The pulse train for the buttons is the exact same. No matter what I did, I could not see a single thing wrong under the scope or in the game. I have no idea what everyone keeps saying that the VX4.0 does not work. Since every single controller version operates the exact same electrically, I highly doubt there are some VX4.0 that are diffferent than other VX4.0s (and different than all the other versions as well).

For all of you reporting problems, I have more doubt about your install/PIC programming than with this code.

As far as I am concerned, I have just confirmed that this code works on the VX4.0.

PS: has anyone else wired directly to the LED as shown in the pictures and had teh LED behave the way its supposed to (as opposed to how I described it above)?

[hyper999]

So....

After donating my only VX3.5 to AskaCapper, I have a VX4_0.10 that came with the PS3 I used for testing. Since no one has investigated this 'issue' I decided to download hypers code and try it out.

It works exactly as it should, except for the LED. The LED is backwards:

Mode 1: on
Mode 2: off
Mode 3: blinks then off
Mode 4: blinks twice then off.

I am soldering it to the side of the LED that is not the common (toward the bottom of the controller). I looked through the scans of all the different versions, they all seem to be same. This is not a big deal as the code can be changed to flip the LED output.

As for the RF signal: It works just fine. I had it under the scope for an hour. I pressed R1 as hard as I could. No issues. I dont have a game to play for hours to test R1, but I will keep testing the contorller every day for awhile to see if I can get this 'lock-up' situation to occur that others have reported.

I am using the analog stick power source. If you people keep using the rumble pad, you will regret it. The motor is a major power draw, and is still susceptable to reverse current when the motor shuts off. Its a very noisy power source and it WILL make the PIC puke itself eventually.

I am very surprised. When I hooked this up, I expected to see something wierd. Maybe something different between the VX3.5 and this VX4.0, but they are exactly the same. The power source measures the same. It takes the same load without problems. The pulse train for the buttons is the exact same. No matter what I did, I could not see a single thing wrong under the scope or in the game. I have no idea what everyone keeps saying that the VX4.0 does not work. Since every single controller version operates the exact same electrically, I highly doubt there are some VX4.0 that are diffferent than other VX4.0s (and different than all the other versions as well).

For all of you reporting problems, I have more doubt about your install/PIC programming than with this code.

As far as I am concerned, I have just confirmed that this code works on the VX4.0.

PS: has anyone else wired directly to the LED as shown in the pictures and had teh LED behave the way its supposed to (as opposed to how I described it above)?

1. LOL
2. Thank you
3. Yes the LED is backwards on some, when I wrote the code I was wrongly informed that the LEDs are setup the same on all boards but I have discovered since that this is not the case so it needs a 50% dutycycle like the 360 version does.


Over summer I was gonna make a new version of this code with a beefier PIC and use a timer for delays in order to simplify the code... but my PS3 killed itself.

[Modded Matt]

Hazer, you are the man!! I used an external led when testing this, and to be honest I felt like I was cheating on my wife when i had that awful ps3 controller in my hand so I didn't spend alot of time with it.

[magic_man185]

Yea tell me about it matt.  I am currently working on some code, but between a 75 mile each way drive, and spending time with my fiance, I don't get too much time to code.  I got the bulk of my code done a couple of weeks ago, she was busy studying for big exams.