Handheld meter robustness testing

[joeqsmith]

Took about an hour but the phone eventually decided to connect to the meter.  This will need to be addressed at some point.

I tried a few different tests with the phone and the same firmware Dave tested with.   I placed the meter into a metal desk drawer (to act as my RF shield).  I then started to walk away with the meter until the connection started to slow down.   I kept if there for several second to try and force the same errors.   This test showed no errors in the data.   

I decided to use a lower value resistor (920 ohms) to see if this would cause a problem.   Nothing odd was recorded.

I then moved the meter about 12 meters from the phone and let it record with the 920 ohm resistor attached for about 1.5 hours.   Again, nothing odd was reported. 

[joeqsmith]

Back to the 1k resistor.  First three 1 count shifts are my fingers shunting it for an index when I placed the meter into the cabinet.    Next 1 count is at 32500 is again my fingers to show when I took the phone and started to walk around the building.  The last 5 count drop is after returning to the meter and again shunting the test resistor.   

So nothing I have done has allowed me to replicate that 10X problem.   Are you sure you are using the same version Android application?

***
Added image

[EEVblog]

So nothing I have done has allowed me to replicate that 10X problem.   Are you sure you are using the same version Android application?

I have no idea what you are using, but I'm using a Google Pixel 8 Pro with Android 15.
Migth try it at home to rule out interference from anything at the lab.

[joeqsmith]

So nothing I have done has allowed me to replicate that 10X problem.   Are you sure you are using the same version Android application?

I have no idea what you are using, but I'm using a Google Pixel 8 Pro with Android 15.
Migth try it at home to rule out interference from anything at the lab.

The Android application I am using is 1.0.58. Is that what you have?

***
I had taken it to work and set it up there.  Its a good test bench as there are several BLE and wi-fi devices constantly running.  Ear buds, speakers, phones...  It's a good mix.   That was how I took all this recent data.   

[EEVblog]

The Android application I am using is 1.0.58. Is that what you have?

Yes.

I had taken it to work and set it up there.  Its a good test bench as there are several BLE and wi-fi devices constantly running.  Ear buds, speakers, phones...  It's a good mix.   That was how I took all this recent data.

My lab is literally surrounded on all sides by other offices with god knows what BLE and other devices.

[joeqsmith]

Too bad.  That was my last idea.   I can believe my phone is causing the application to have a difficult time connecting but I don't think it explains why I am not seeing those glitches you mention.

[joeqsmith]

This is looking at the time between readings when I had the meter in my cabinet.  Normally it sends at 5Hz or every 200ms.   The one was stalled for over 1.6 seconds.  It seems like this would be far worse that what you were doing.   

[joeqsmith]

Dave,  if you use your phone to link to the meter, then select the About, Version Information, BM8xBT.  What does it report for the BLE version?   

Mine reports 0.1.17 but talking with Brymen, it's possible you have something newer, which may explain a lot.

[EEVblog]

Dave,  if you use your phone to link to the meter, then select the About, Version Information, BM8xBT.  What does it report for the BLE version?   
Mine reports 0.1.17 but talking with Brymen, it's possible you have something newer, which may explain a lot.

0.1.20

[joeqsmith]

0.1.20

It sounded like that's the latest.  Once updated, I will test again and post the results. 

[joeqsmith]

Dave,

When you select the version and it shows the BLE version, go ahead and select that BLE version.  It will ask if you want to update the firmware.  If you select the auto download, does it succeed, or do you get an "Error Not Network"?

[joeqsmith]

We are still working through the problems of upgrading the radio's firmware.  They have provided the latest image and Android applications but so far with my BLU G64 Andoid phone, no luck.   The last three times I tried to connect to the meter took 1 hour, 1.5 hours and 50 minutes.  The fastest I have had it connect was maybe 10 minutes.  Because their programmer seems to drop to connection as part of the process,  it can't recover.   

I offered to include a programmer in my Windows application under NDA, but no luck.  Looks like they are working on a new revision which I hope to have next week. 

With Dave not having the connection problems but seeing that 10X glitch, I am hoping that we start to see some consistency between the two setups once I get that radio updated. 

I have no doubt that by the time the meter is available to the public, we will have these problems solved.  Over the years, Brymen has proven to be very responsive.  Stay tuned.

[EEVblog]

When you select the version and it shows the BLE version, go ahead and select that BLE version.  It will ask if you want to update the firmware.  If you select the auto download, does it succeed, or do you get an "Error Not Network"?

Yep, same error.

[joeqsmith]

That's good to know.   

A small update.  Brymen has ordered a BLU G64 phone like the one I procured for these tests.  Hopefully they are able to replicate the connection problems I am seeing.  I am not expecting to hear back from them for another week or so.