search

jahbini / researchPad

Cordova based app for iPad for gesture and BLE capture for medical research.
1 stars 0 forks source link

App uses UUID and Serial number for identification #93

Closed MrSniffer closed 7 years ago

MrSniffer commented 7 years ago

I added a Serial No field to the FW of two Tags. When I run the app, the UUID is used to match/lookup the name in the lower screen, e.g. where the vectors display. And the Serial number is used to display the name at the upper portion of the display.

The system should just use the burned in serial number if present, and default to UUIDs only if it is a "stock" ROM.

jahbini commented 7 years ago

fixed in next app release. However, the serial number stuff is not available at first -- the complete connection must be made to the sensor so that the serial number request can be made.

That means, the funky UUID stuff will be displayed until some time after the connect button is pressed.

MrSniffer commented 7 years ago

Does this mean that the symbolic name for the sensor should appear twice in the backend sensortag list on the server?

jahbini commented 7 years ago

yes, no. Maybe so.

This happens in the server — it may see both identifiers. The UUID one should have a check to delete that entry after the dust settles.

So let’s keep that one up on github. However, my focus is getting the app side 100% or better.

Yes, there are some odd things on he server side — like no delete for tags. odd.

J-

On Nov 2, 2016, at 4:06 AM, MrSniffer notifications@github.com wrote:

Does this mean that the symbolic name for the sensor should appear twice in the backend sensortag list on the server?

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/jahbini/stagapp/issues/93#issuecomment-257644229, or mute the thread https://github.com/notifications/unsubscribe-auth/ABfNi_gi2mZBU4VR3ToD6YAN0fMFktgZks5q53-KgaJpZM4Klk5R.

jahbini commented 7 years ago

And now there is a "delete" on the server for sensor specific info.

MrSniffer commented 7 years ago

  1. I notice that the HW UUIDs appear each time the app sees my devices, even after deleting the UUIDs on the server.

  2. I tried to use the Assigned Name field on the server to set a text string for my sensors. Used to work in the old version.

I think I am missing something about how this is all supposed to work correctly.

jahbini commented 7 years ago

1) yes. 2) Huh? or maybe ‘no, nawthing. Thursday’ (a common Saipan response from a clerk)

The logic at the moment is to ask the server about this Tag very early in the discovery/connection phase. That was if the server knew important info about the tag based on it’s UUID. Since the UUID is not good for identity, that early request is causing the naming problems.

I will attempt, 'One Time, and One Time Only", to see if delaying this first server request till later in the discovery sequence is possible with the current drivers.

Cross your fingers.

Jim

On Nov 30, 2016, at 8:40 AM, MrSniffer notifications@github.com wrote:

I notice that the HW UUIDs appear each time the app sees my devices, even after deleting the UUIDs on the server.

I tried to use the Assigned Name field on the server to set a text string for my sensors. Used to work in the old version.

I think I am missing something about how this is all supposed to work correctly.

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/jahbini/stagapp/issues/93#issuecomment-263723694, or mute the thread https://github.com/notifications/unsubscribe-auth/ABfNi7DxOnUTchxPR5aasdAWeFmL6tyxks5rDKnUgaJpZM4Klk5R.