Enable temp and accel

[CE]

I have a beacon from Wellcore, w912, with NRF51822QFAAH0. I use NRF Connect and I see the temp and accel sensors but I dont know how to enable them. Is there a manual you can direct me to or give me the values I need to enable, set range, and more so I can use my two beacons.

[CE]

I'm just learning. Acctually I can "see" the accel sensor on the chip/board, it's that rectangular shiny thing close to SW1?

I didn't know that Wellcore has their own software, or firmware. The beacon has nRF5_SDK_11.0.0_89a8197 as "Software Revision String".

I thought that the beacon came with some kind of function that answered an app for example when asked for data, also sending at intervalls defined through some outer software. But you are saying that each company has their own firmware on the chip and that is what answers the app for example Lightblue. And they can lock the sensors with their firmware.

Isn't there a enable code in the standard firmware, if so why would they want to change it?

I have tried to get the information from Wellcore, I even sent a video showing my beacons, but so far I haven't got any info from them. Still hoping. Otherwise, the alternative is to remove the firmware and put my own. And I suppose you have some standard firmware I can use?

I'm building an app that use the temp and accel, it's my first shot with a beacon. I appreciate all help I can get.

[CE]

Actually the shiny tnig seems to be an on/off switch. But good news from Wellcore, they asked for a picture of the chip and when they had studied it they told me that temp and accel is not on my chip. I find it strang that NRF Connect finds them and shows values and even stranger that they could see that I dont have a temp-sensor, you said it is always there on 51822, right. So why cant I get values from temp, I guess temp is what the chip need to shut down if it's to hot or cold?

[awneil]

CE said:

I find it strang that NRF Connect finds them and shows values

Not strange at all - that's the whole point of the BLE standardised attributes and services!

This allows a device to advertise that it has a "temperature" facility - while being completely independent of how that is implemented.

https://www.bluetooth.com/specifications/gatt/generic-attributes-overview

https://www.bluetooth.com/specifications/gatt

It's a bit like USB: when you plug a USB device into your PC, it identifies it through the standard USB processes & protocols

CE said:

So why cant I get values from temp, I guess temp is what the chip need to shut down if it's to hot or cold

Again, that's a question for Wellcore.

[CE]

You lost me: "I find it strang that NRF Connect finds them and shows values " you:"Not strange at all - that's the whole point of the BLE standardised attributes and services!"

So it's standard to show something that does not exist? So why don't humidity turn up or other sensors?

[awneil]

The point is, it's all down to software.

If Wellcore have created software which says it has a "temperature", then nRFConnect will display that.

There is no way for nRFConnect to know whether the report is purely fictitious!

Again, you really need to discuss this with Wellcore.

If you cannot get adequate support from Wellcore, then consider an alternative manufacturer.

[CE]

OK, I'm buiding an app that use temp and accel, the only two beacons I have at the moment are W912s from Wellcore, can I erase Wellcores firmware and replace it with something standard that at leats give me internal temperature?

[CE]

If this thread is closed (got an email saying that) then I just want to thank you guys for your answes, it tought me a lot about beacons. I'm putting these Wellcore w912 aside and wait for new beacons with 52832s and hopefully the sensors I'm more interrested in; temperature and humidity.