0

nRF52 Feather no BLE Device name for Scratch-Link scan
Moderators: adafruit_support_bill, adafruit

Please be positive and constructive with your questions and comments.

nRF52 Feather no BLE Device name for Scratch-Link scan

by funseeker111 on Fri Jun 11, 2021 7:46 am

nRF52 Feather no BLE Device name for Scratch-Link scan

I’m making a Scratch extension with the nRF52 Feather(nRF52832) module.

Currently my Scratch extension for the nRF52 Feather(nRF52832) module can communicate and work normally.
one thing that I don’t know how to solve is that no device name appears in the JSONRPC message.

https://rsbry.github.io/bleDeviceName/2 ... st_gui.JPG
https://rsbry.github.io/bleDeviceName/2 ... ssages.JPG

Though the name, BBC micro:bit[--], can be seen in the JSONRPC message with the same SW, Scratch-Link on Windows 10.
When I check it with nRF App and Bluefruit App, both the BBC micro:bit and Bluefruit52 show the device name.
https://rsbry.github.io/bleDeviceName/2 ... d_scan.JPG

If the Scratch-Link can not show the BBC micro:bit’s device name then I will say it is the Scratch-Link’s error but it can.
Even though my ble device ( nRF52 Feather) doesn’t show the device name in the JSONRPC message it can be connected and communicate. The only filter is the service uuid.
https://rsbry.github.io/bleDeviceName/2 ... filter.JPG
https://rsbry.github.io/bleDeviceName/2 ... h-link.JPG

Scratch uses the device name as a way to differentiate in case several students use it in the same space.

Anything will be helpful and I hope to get some clues.

funseeker111
 
Posts: 3
Joined: Sun Feb 10, 2019 4:15 am

Re: nRF52 Feather no BLE Device name for Scratch-Link scan

by adafruit2 on Tue Jun 15, 2021 4:26 pm

no idea but we do know that Scratch 'locks' down their API for their partners (e.g. micro-bit) and non-partners can't really connect hardware so it may not be possible :/ becoming a partner is not free

adafruit2
Site Admin
 
Posts: 20112
Joined: Fri Mar 11, 2005 7:36 pm

Re: nRF52 Feather no BLE Device name for Scratch-Link scan

by funseeker111 on Wed Jun 16, 2021 5:53 am

About official version, as you said it can be right, there are only a few official extensions.

But my question is about a custom extension, and that is open source.
In my personal opinion I think it is not the cause.
nRF52 Feather module can be connected and communicate normally.
Only thing is about the BLE device name.

Thinking of the FW, I saw one difference from the micro:bit that about UUID 0x2A01 the nRF52 Feather module shows ‘[0] Unknown’ though the micro:bit shows ‘[512] Generic Tag’, like following image.
https://rsbry.github.io/bleDeviceName/2 ... d_scan.JPG

funseeker111
 
Posts: 3
Joined: Sun Feb 10, 2019 4:15 am

Please be positive and constructive with your questions and comments.