07-21-2020, 12:26 PM
Sorry, I missed your post and a colleague just drew my attention to it.
You are right. It seems like it should just work on the older SensorTag and I have no idea why it should fail. A first thought is that maybe the older SensorTag does not allow setting a rate before the sensor has been enabled, so maybe just switching the first two config entries might already help. But then again, the errors on Android and iOS suggest that the characteristic is not even available (even though both errors have a different wording, they are both triggered if the UUID is not in the list of characteristics), which I find very strange.
So, I see two options:
a) You can try the app nRF Connect to see the characteristic is available and if you can set it manually.
b) You can indeed send the SensorTag to me, so I can find the problem (I would suggest to contact me via staacks@physik.rwth-aachen.de in this case).
You are right. It seems like it should just work on the older SensorTag and I have no idea why it should fail. A first thought is that maybe the older SensorTag does not allow setting a rate before the sensor has been enabled, so maybe just switching the first two config entries might already help. But then again, the errors on Android and iOS suggest that the characteristic is not even available (even though both errors have a different wording, they are both triggered if the UUID is not in the list of characteristics), which I find very strange.
So, I see two options:
a) You can try the app nRF Connect to see the characteristic is available and if you can set it manually.
b) You can indeed send the SensorTag to me, so I can find the problem (I would suggest to contact me via staacks@physik.rwth-aachen.de in this case).