Device not from RedBearLab error

Ask, and ye shall receive.
brumac57
Posts: 3
Joined: 06:03, 04 Apr 2016

Device not from RedBearLab error

Postby brumac57 » 06:16, 04 Apr 2016

Hi,

I have a RedBear Nano board
A week ago I compiled BLENano_SimpleControls with MBED dragged and dropped onto the Nano
Installed the Evothings workbench and viewer.
ran the simplecontrols app

All worked fine.

Now (a week later) I can scan for the Nano (comes up as "Biscuit") and when I attempt to connect I get
"Device is not from RedBearLab"

The workbench log - "Error reading services: EASYBLE_ERROR_SERVICE_NOT_FOUND 713d0000503e4c75ba943148f18d941e"

I have rebooted both PC and phone
cleared the phone viewer app cache
uninstalled/reinstalled latest viewer and work bench
deleted/recompiled/reinstalled app/nano code
I haven't altered one bit of code or UUIDs

windows 7 32 bit
android 5 on samsung SM-G9001

I'm stumped!
Any suggestions?

Cheers Bruce

Fredrik
Site Admin
Posts: 196
Joined: 15:00, 18 Nov 2013

Re: Device not from RedBearLab error

Postby Fredrik » 11:45, 04 Apr 2016

713d0000503e4c75ba943148f18d941e is app.RBL_SERVICE_UUID, as found in app.js of redbearlab-simplecontrol. It should be present on any device running the BLENano_SimpleControls program.

Since one app thinks it is not, let's get a second opinion. Run the example "BLE Discovery", scan the device in question and post the workbench log here.

brumac57
Posts: 3
Joined: 06:03, 04 Apr 2016

Re: Device not from RedBearLab error

Postby brumac57 » 06:04, 06 Apr 2016

Hey thanks
I tried running the simplecontrol app in the evothings viewer on ios9.3 apple
similar problem device not redbear, actually it didn't see the nano as "biscuit" but "nrf5x"

also I have 2 nano boards - both exhibit same behaviour

this is the log from android version of BLEdiscovery

LOG: Received Event: deviceready
LOG: startScan
LOG: Stopping scan...
LOG: scan result: -44 Biscuit FA:D2:2D:2D:D2:1F
LOG: scan result: -99 undefined F0:DB:EB:17:39:03
LOG: Stopping scan...
LOG: connect(FA:D2:2D:2D:D2:1F)
LOG: connect 3 state 2
LOG: connected, requesting services...
LOG: s1: 0 00001800-0000-1000-8000-00805f9b34fb. 3 chars.
LOG: c4: 00002a00-0000-1000-8000-00805f9b34fb. 0 desc.
LOG: properties: PROPERTY_READ PROPERTY_WRITE
LOG: writeType: WRITE_TYPE_DEFAULT
LOG: c5: 00002a01-0000-1000-8000-00805f9b34fb. 0 desc.
LOG: properties: PROPERTY_READ
LOG: writeType: WRITE_TYPE_DEFAULT
LOG: c6: 00002a04-0000-1000-8000-00805f9b34fb. 0 desc.
LOG: properties: PROPERTY_READ
LOG: writeType: WRITE_TYPE_DEFAULT
LOG: s2: 0 00001801-0000-1000-8000-00805f9b34fb. 1 chars.
LOG: c7: 00002a05-0000-1000-8000-00805f9b34fb. 1 desc.
LOG: properties: PROPERTY_INDICATE
LOG: writeType: WRITE_TYPE_DEFAULT
LOG: d9: 00002902-0000-1000-8000-00805f9b34fb
LOG: s3: 0 0000a000-0000-1000-8000-00805f9b34fb. 1 chars.
LOG: c8: 0000a001-0000-1000-8000-00805f9b34fb. 1 desc.
LOG: properties: PROPERTY_READ PROPERTY_NOTIFY
LOG: writeType: WRITE_TYPE_DEFAULT
LOG: d10: 00002902-0000-1000-8000-00805f9b34fb

Fredrik
Site Admin
Posts: 196
Joined: 15:00, 18 Nov 2013

Re: Device not from RedBearLab error

Postby Fredrik » 11:39, 06 Apr 2016

OK, I'm seeing 3 services on the device: 0x1800, 0x1801 and 0xa000.

The first two are the standard GAP services and may be ignored.

The third is most likely an mbed example service. To work with that service you'll need not the simplecontrols app, but the mbed-Evothings-CustomGATT app mentioned on that page.

brumac57
Posts: 3
Joined: 06:03, 04 Apr 2016

Re: Device not from RedBearLab error

Postby brumac57 » 01:32, 08 Apr 2016

OK thanks, I will look into it.
Something strange is going on, because the app previously worked.

Cheers


Return to “Questions and answers”

Who is online

Users browsing this forum: MSN [Bot] and 4 guests