(02-18-2016, 03:20 PM)abuali129 Wrote: [ -> ] I put the mac address in scpcontrol.ini but still not connected
however I downloaded version [1.2.2.175]
here's screenshots of SCP monitor
connected to usb
![[Image: yhzq9nL.png]](https://i.imgur.com/yhzq9nL.png)
trying to connect Bluetooth
![[Image: pJ1pYfy.png]](https://i.imgur.com/pJ1pYfy.png)
and the led continue blinking for more than 10 minutes, here's the log of ScpService.log
http://www.mediafire.com/download/ruqg9g...ervice.log
ScpDriver.log
http://www.mediafire.com/download/jn5hx0...Driver.log
edit: here after ScpService.log led blinking goes off
http://www.mediafire.com/download/vkcwhy...ervice.log
Damn, your controller has Remote [00:00:00:00:00:00] which means scp cannot write your bt dongle mac id into your controller. It always stays at Remote [00:00:00:00:00:00].
Run ScpPair.exe and see Remote mac id. Enter some random mac id in the below text box and click set. If the Remote still says [00:00:00:00:00:00] then there is no chance of getting your controller working through bluetooth.
so what is "00:09:7A:B4:8A:25 "? it is not mac id?
set button in ScpPair.exe is greyed, i cannot press on it
(02-18-2016, 04:17 PM)abuali129 Wrote: [ -> ]so what is "01:09:7A:B4:8A:25 "? it is not mac id?
That is your controller mac id. Remote is the bt mac id which the controller needs to connect. If it is 00:00:00:00..... then it cannot connect or find bluetooth.
The process of wireless connection involves two ways.
First the scp tool writes bt mac id into controller memory (known as Remote in log)
Then when you disconnect the controller, the controller finds for that bt mac id.
On the other hand, scp tool has your controller id mac id (That is present in scpcontrol.dll or ini file in reloaded version).
When both finds each other then they pair and get connected.
Now your controller has 00:00:00:.... bt mac id (aka remote) in its memory and won't change when scp tool writes so how could it find the bt when disconnected?
I hope you have understood now but there are many controllers having such issue. Only a expert developer can solve it.
(02-18-2016, 04:20 PM)CRACING Wrote: [ -> ]That is your controller mac id. Remote is the bt mac id which the controller needs to connect. If it is 00:00:00:00..... then it cannot connect or find bluetooth.
set button in ScpPair.exe is greyed, i cannot press on it
(02-18-2016, 04:22 PM)abuali129 Wrote: [ -> ]set button in ScpPair.exe is greyed, i cannot press on it
Type a random mac id in the text box then the button will be enabled.
i.e 02:05:5B:B4:65:25
Edit: You have to stop scp service from windows services before running ScpPair.
(02-18-2016, 04:31 PM)CRACING Wrote: [ -> ]Type a random mac id in the text box then the button will be enabled.
i.e 02:05:5B:B4:65:25
same happened, the button still greyed
![[Image: AGd7pMG.png]](https://i.imgur.com/AGd7pMG.png)
another weird thing happening
ScpServer.exe shows it is disconnected but SCP monitor is connected
and the ds3 works fine
(02-18-2016, 04:35 PM)abuali129 Wrote: [ -> ]same happened, the button still greyed
Try stopping scp service in windows service and then run the SCP Par Tool.
Here is my controller. Default remote mac id says 00:10:34:54:78:99 and after I enter random mac id 01:02:03:04:05:06, it successfully writes.
[
attachment=59157][
attachment=59158]
(02-18-2016, 04:47 PM)abuali129 Wrote: [ -> ]Code:
2016-02-18 17:18:19.225 ++ C:\Program Files\ds3driver\ScpService.exe 1.2.2.175
2016-02-18 17:18:19.225 ++ C:\Program Files\ds3driver\ScpControl.dll 1.2.2.175
2016-02-18 17:18:21.807 ++ Microsoft Windows 10 Pro (6.2.9200.0 AMD64)
2016-02-18 17:18:21.823 -- Bus Open : Offset 0
2016-02-18 17:18:21.838 -- Bus Open : Path \\?\ROOT#SYSTEM#0001#{F679F562-3164-42CE-A4DB-E7DDBE723909}
2016-02-18 17:18:21.916 ## Mapper.Initialize() - Profiles [5] Active [Default] Mappings [0]
2016-02-18 17:18:21.963 -- Bus Plugin : Serial 1
2016-02-18 17:18:21.979 ++ Plugin Port #1 for [01:09:7A:B4:63:25]
2016-02-18 17:18:22.010 -- USB Device : HID_Worker_Thread Starting
2016-02-18 17:18:22.015 -- Started Device Instance [USB\VID_054C&PID_0268\5&212AC8FC&0&3] Local [01:09:7A:B4:63:25] Remote [00:00:00:00:00:00]
2016-02-18 17:18:22.051 -- Bluetooth : L2CAP_Worker_Thread Starting [82,02]
2016-02-18 17:18:22.066 -- Bluetooth : HCI_Worker_Thread Starting [81]
2016-02-18 17:18:22.087 -- Controller : UDP_Worker_Thread Starting
2016-02-18 17:18:22.094 << HCI_Reset [0C03]
2016-02-18 17:18:22.144 >> HCI_Command_Complete_EV [0E] [00] [HCI_Reset]
2016-02-18 17:18:22.403 << HCI_Read_BD_ADDR [1009]
2016-02-18 17:18:22.409 >> HCI_Command_Complete_EV [0E] [00] [HCI_Read_BD_ADDR]
2016-02-18 17:18:22.412 << HCI_Read_Buffer_Size [1005]
2016-02-18 17:18:22.417 >> HCI_Command_Complete_EV [0E] [00] [HCI_Read_Buffer_Size]
2016-02-18 17:18:22.419 -- 03FD, 30, 0004, 000A
2016-02-18 17:18:22.422 << HCI_Read_Local_Version_Info [1001]
2016-02-18 17:18:22.426 >> HCI_Command_Complete_EV [0E] [00] [HCI_Read_Local_Version_Info]
2016-02-18 17:18:22.429 -- Master 00:11:67:C4:B7:68, HCI_Version 3.0302, LMP_Version 3.0302
2016-02-18 17:18:22.432 << HCI_Write_Scan_Enable [0C1A]
2016-02-18 17:18:22.436 >> HCI_Command_Complete_EV [0E] [00] [HCI_Write_Scan_Enable]
2016-02-18 17:35:58.120 ++ Notify [Removal] [{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}] [\\?\USB#VID_054C&PID_0268#5&212AC8FC&0&3#{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}]
2016-02-18 17:35:58.132 -- Device Removal [01:09:7A:B4:63:25]
2016-02-18 17:35:58.141 -- USB Device : HID_Worker_Thread Exiting
2016-02-18 17:36:00.249 ++ Notify [Arrival] [{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}] [\\?\USB#VID_054C&PID_0268#5&212AC8FC&0&3#{E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}]
2016-02-18 17:36:00.249 -- DS3 Arrival Event
2016-02-18 17:36:00.249 -- Device Arrival [01:09:7A:B4:63:25]
2016-02-18 17:36:00.264 ++ Plugin Port #1 for [01:09:7A:B4:63:25]
2016-02-18 17:36:00.264 -- USB Device : HID_Worker_Thread Starting
2016-02-18 17:36:00.275 -- Started Device Instance [USB\VID_054C&PID_0268\5&212AC8FC&0&3] Local [01:09:7A:B4:63:25] Remote [00:00:00:00:00:00]
2016-02-18 17:36:00.283 ++ Paired DS3 [01:09:7A:B4:63:25] To BTH Dongle [00:11:67:C4:B7:68]
Its because of Remote [00:00:00:00:00:00]. It should have some numbers rather then zeros.
But the ps3 console writes into controller memory. It just the scp tool cannot write to some fake controllers.
See if you tell this to scp reloaded developer. May be he can debug more.