(01-31-2014, 10:23 PM)Scarlet.Crush Wrote: [ -> ]@Zolcillonca:
Code:
public enum Ds3Battery : byte { None = 0x00, Dieing = 0x01, Low = 0x02, Medium = 0x03, High = 0x04, Full = 0x05, Charging = 0xEE, Charged = 0xEF };
Your controller shows 241 (decimal) => 0xF1.
I highly doubt that any firmware localisation would change an enumeration constant.
When a genuine DS3 shows strange behaviour it is usually fixed by a pinhole reset. Do you feel a slight click when you press the reset button?
----------------------------------------------------------------------
OMG
I finally made it Work the solution was so stupid.
So I was completely puzzled of why I was unable to use the controller on BT but was working perfectly fine on USB.
The responsible was the USB cable I was using. I was about 10 secs away of opening the Gamepad to see why the hell this was not working.
I mean it is a new Gamepad, on mint condition, 1 week old
purchased on an Official Sony Store and it was not working
also of course the dongle I have is compatible with this Software. The light at the end of the tunnel was that damn number 241 on the battery status. According to Scarlet that meant that something was wrong with the battery.
When I plugged the controller on the USB port the number 1 led blinked for like 15 secs while the monitor said charging and then it lit solid with the 241 number, I thought that number + solid light meant fully charged, but I was wrong.
With a philips screwdriver in my hand and about to open the damn thing to see if there is actually a battery inside or if it is not connected or if there is a cut wired on it, something stopped me, and I remembered that I had another mini USB cable from and old cell phone, so I said to myself why not ? its easier to test that than to disassemble this thing.
As soon as I plugged the controller with the new cable something different happened the red light on led number 1 did not stop blinking after 10 secs it continued blinking for 2 hours.
What did this mean ? that the other damn cable even if it allowed me to play with the controller through USB and also allowed the controller to be recognized by windows it wasn't allowing to charge the damn thing.
So of course when I unplugged the gamepad to see if it will pair with the dongle since it never received a charge in the first place of course it will never pair because the battery was on CERO and of course without energy the controller will never pair/work
So with the new cable after 2 hours of charging when I unplugged the cable BAM !!
in less than 3 secs it was paired with the dongle
Since I don't own a PS3 I didn't have the option to check if the controller was OK or if it was charged, I was relying on the idea that the controller was fine and the cable was a good one.
So yeah its strange that a cable work in half, because if it would have never worked in the first place I would have picked the other cable long ago. But this cable was working at 50 %.
So I wanted to share this experience maybe it would help someone that is struggling with this, maybe like me it doesn't have a console to test the gamepad and it is just testing it on a PC for the first time.
So apparently the controller gets its power from a different lane on the cable that is not the one where data goes ?
So Scarlet what about:
public enum Ds3Battery : byte { Change the Cable Bro !! = 0xF1 };
Just Joking !!
Anyways thx Scarlet for this great Software !!
Regards Zolcillonca