Hi everyone,
more or less by chance, I connected my 1st gen SensorTag CC2541 to phyphox and successfully performed a measurement (amb & ir temp). IR is messed up because of the missing calibration (CC2541 uses a tmp006, CC2560 a tmp007), but ambient works fine.
My old CC2541 was already advertising as I tried a new experiment so I accidentally chose it instead of the CC2650. Why was I so surprised? Because in any other test runs phyphox returned the attached errors (English one is android on a nexus 4 and German one is iOS 13 on an iPhone). I first thought this is because they completely differ regarding the gatt table, but both use the same base uuid F0000000-0451-4000-B000-000000000000 and for temperature:
and even the same resolution: 10 ms. Range 300 ms (0x1E) to 2.55 sec (0xFF). Default 1 second (0x64).
So why did it work this time? The thing is, that I forgot to set the period in the bluetooth configuration. In any other cases I tried setting it and phyphox returned the errors. Immediately, I opened the standard IR temperature experiment from the phyphox editor and I was able to reproduce the issue: as long as phyphox tries to set a different period, the error is returned. As soon as I delete it from the configuration, it works. Am I missing something?
@phyphox team: is this a known issue? If you have the resources to also look into it and since we are practically neighbors (I'm from cologne) I'd be happy to bring/send one 1st gen SensorTag over to Aachen for further development!
In the meantime I'll try to adapt the standard IR temperature experiment to the tmp006 sensor and take a closer look at the other sensors in the CC2541's gatt table and compare them to the CC2650. Any help is much appreciated! Sebastian
PS: I used the CC2650 users guide and this one from the internet archive for the CC2541.
more or less by chance, I connected my 1st gen SensorTag CC2541 to phyphox and successfully performed a measurement (amb & ir temp). IR is messed up because of the missing calibration (CC2541 uses a tmp006, CC2560 a tmp007), but ambient works fine.
My old CC2541 was already advertising as I tried a new experiment so I accidentally chose it instead of the CC2650. Why was I so surprised? Because in any other test runs phyphox returned the attached errors (English one is android on a nexus 4 and German one is iOS 13 on an iPhone). I first thought this is because they completely differ regarding the gatt table, but both use the same base uuid F0000000-0451-4000-B000-000000000000 and for temperature:
Code:
Type UUID Access Size (bytes)
Data AA01* R/N 4
Notification R/W 2
Configuration AA02* R/W 1
Period AA03* R/W 1So why did it work this time? The thing is, that I forgot to set the period in the bluetooth configuration. In any other cases I tried setting it and phyphox returned the errors. Immediately, I opened the standard IR temperature experiment from the phyphox editor and I was able to reproduce the issue: as long as phyphox tries to set a different period, the error is returned. As soon as I delete it from the configuration, it works. Am I missing something?
@phyphox team: is this a known issue? If you have the resources to also look into it and since we are practically neighbors (I'm from cologne) I'd be happy to bring/send one 1st gen SensorTag over to Aachen for further development!
In the meantime I'll try to adapt the standard IR temperature experiment to the tmp006 sensor and take a closer look at the other sensors in the CC2541's gatt table and compare them to the CC2650. Any help is much appreciated! Sebastian
PS: I used the CC2650 users guide and this one from the internet archive for the CC2541.