Feature Description
The device is detected by Intiface but is currently not recognized:
“Device J-AresIII found”
“No viable protocols for hardware …, ignoring”
I investigated the device with nRF Connect and collected the following information:
BLE Name:
J-AresIII
Manufacturer Data:
Company 65440 (0xFFA0)
Services:
FFA0
FFA1 Write Without Response
FFA2 Notify
FF12
FF15 Read, Write Without Response
FF14 Notify
FF15 returns:
464F544100 (“FOTA”)
The device works normally with the JoyHub app.
Manual testing showed that the following commands sent to FFA1 are accepted:
a003ff000000aa -> vibration starts
a00300ff0000aa -> vibration stops
Because these commands work, the device appears to be related to an existing JoyHub / Truform protocol family rather than using a completely unknown protocol.
I have not yet determined the intensity control commands, but I am available to provide additional logs or perform further testing if needed.
Feature Description
The device is detected by Intiface but is currently not recognized:
“Device J-AresIII found”
“No viable protocols for hardware …, ignoring”
I investigated the device with nRF Connect and collected the following information:
BLE Name:
J-AresIII
Manufacturer Data:
Company 65440 (0xFFA0)
Services:
FFA0
FFA1 Write Without Response
FFA2 Notify
FF12
FF15 Read, Write Without Response
FF14 Notify
FF15 returns:
464F544100 (“FOTA”)
The device works normally with the JoyHub app.
Manual testing showed that the following commands sent to FFA1 are accepted:
a003ff000000aa -> vibration starts
a00300ff0000aa -> vibration stops
Because these commands work, the device appears to be related to an existing JoyHub / Truform protocol family rather than using a completely unknown protocol.
I have not yet determined the intensity control commands, but I am available to provide additional logs or perform further testing if needed.