ANT Forum

Subject: problems connecting to a blood pressure monitor that is sold with the ANT+ logo.

I hope, that one of Dynastream's staff can and may answer this.

I'm having problems with a blood pressure monitor that I've just bought. It's a "smartLAB profi+" which is distributed by German company HMM Diagnostics GmbH. They are listed as members of the ANT+ alliance. However, none of their appliances is listed in http://www.thisisant.com/modules/mod_product-directory.php .

Using the ANT-FS PC Host simulator (the ANT+ BPM device profile is ANTFS based), the bpm rejects all requests for pairing.
Besides it has some strange data in its LINK layer beacon (manufacturerID is 0, which is not specified in the FIT SDK, device type is 142 which isn't specified in FIT_DEVICE_TYPE as well).

Has this device been ANT+ certified?

Thanks in advance,
OMB

PS: I didn't find more ANT+ bpms but the HMM and "UA-851ANT" of A&D Medical (e.g. at http://www.nashmedical.com/UA_851ANT_Wireless_Blood_Pressure_Monitor_p/ad-ua-851ant.htm ).
Does somewhone know the A&D bpm?      

HMM has responded: there's a tiny little bug in their firmware :S
They'll fix that within a few weeks.

How about the "UA-851ANT" of A&D Medical (e.g. at http://www.nashmedical.com/UA_851ANT_Wireless_B...r_p/ad-ua-851ant.htm ).
Does somewhone know the A&D bpm?

I've found this video at YouTube, where ANT+Alliance demonstrates connectivity to health sensors. They use a pre-production A&D mock up:
http://www.youtube.com/watch?v=-Cfn38AVLC0

Thanks,
OMB      

Hello OMB,

our company works with both (HMM and AND) blood pressure meter.

Both devices are a little bit tricky to handle.

As you already know the HMM BPM has some bugs.
1) Device descriptor,
2) only works for point-to-point communication and goes in error mode when connecting to multiple receivers.

The AND BPM follows more the BPM profile.
1) Requires a proximity binding at the beginning of every power cycle.
2) Is difficult to bring the BPM into sleep mode.

If you have difficulties to get the data from the BPM, feel free to contact me.

Regards,
Berthold

*******@spantec.at      

I got my A&D UA-851ANT today and after some trial and error succeeded to have it talk to ANTFS-PC-Host and my software.

Thanks a lot to b_bleier and the folks at Dynastream for their advice.
OMB      

Hi,

I'm experiencing some kind of weird situation when I send the ant-fs command to download the FIT file available at index number 2, because the BPM responds with zeros!!!!!! The response of the download command is OK(the file exists), but it responds with zeros!! I don't know what I have to do to receive the FIT file. The STATUS BYTE1 of the beacon is 0x23 (so the data is available). It responds well when I request the directory structure with index 0. But when I request index 1(sub-directory or index2 (fit file) the response is a header and footer with zeros!!

So, what am I doing wrong?

Thanks for the help.      

Which BPM? The A&D or the HMM? Or the ANTFS Client Simulator?      

The A&D blood pressure monitor.      

If I remember right, I had a similar issue, when I had set the ulMaxDataLength parameter of ANTFS_Host.Download() to zero which should be interpreted as "no limit".
After increasing it to uint.MaxValue everything worked well.
Obviously a minor glitch in the A&D's ANTFS implementation.

I'm using the .NET API, but the lower level APIs should be similar.

Hope that helps,
OMB      

I agree with OMB.
datalength = 0 (unlimited) does not work.
Setting the datalength to maximum 0xFFFFFFFF (32 bit) works.

Regards,
Berthold      

Thank you so much! You guys rock!! :cheer:      

Hi I am trying to connect to the AND-UA851ANT blood pressure cuff using the Sony Ericcson phone which has the ANT enabled.

these are the parameters for my antChannelSetup

byte networkNumber = 1; ANT + network key
short deviceNumber = 0;
byte deviceType = 0x12; //ANT + blood pressure device
byte TransmissionType = 0x00; // Pairing search
short period = 8192; //Data shall be received at a rate of 4Hz
byte freq = 57; // 2457Mhz (ANT+ frequency)
byte channel = 0;
byte proxThreshold = 7;


After channel reset I receive this message
Rx:[01][6F][20]

after that I receive the following messages
//unknown - message
[03][40][00][74][00]

Assign Channel - response
[03][40][00][42][00]

Set Channel ID
[03][40][00][51][00]

Messaging period
[03][40][00][43][00]

Channel Freq
[03][40][00][45][00]

Search Timeout
[03][40][00][44][00]

Low priority channel search timeout
[03][40][00][63][00]

Set Proximity Search threshold
[03][40][00][71][00]

Open Channel
[03][40][00][4B][00]

//unknown - message
[03][40][00][74][00]

When the BP monitor goes into pairing mode. Is this the beacon?
I am trying to parse this message and know what this means.

[03][40][00][01][01]

Any help is appreciated.

- Albert      

Hi I am trying to connect to the AND-UA851ANT blood pressure cuff using the Sony Ericcson phone which has the ANT enabled.

these are the parameters for my antChannelSetup

byte networkNumber = 1; ANT + network key
short deviceNumber = 0;
byte deviceType = 0x12; //ANT + blood pressure device
byte TransmissionType = 0x00; // Pairing search
short period = 8192; //Data shall be received at a rate of 4Hz
byte freq = 57; // 2457Mhz (ANT+ frequency)
byte channel = 0;
byte proxThreshold = 7;


After channel reset I receive this message
Rx:[01][6F][20]

after that I receive the following messages
//unknown - message
[03][40][00][74][00]

Assign Channel - response
[03][40][00][42][00]

Set Channel ID
[03][40][00][51][00]

Messaging period
[03][40][00][43][00]

Channel Freq
[03][40][00][45][00]

Search Timeout
[03][40][00][44][00]

Low priority channel search timeout
[03][40][00][63][00]

Set Proximity Search threshold
[03][40][00][71][00]

Open Channel
[03][40][00][4B][00]

//unknown - message
[03][40][00][74][00]

When the BP monitor goes into pairing mode. I get the following packet
[03][40][00][01][01]

Is this the beacon? I am trying to parse this message and know what this means. Any help is appreciated.

How should this message be parsed and what is the next step in this.

- Albert      

Hi Albert,

The message [40][00][01][01] corresponds to the EVENT_RX_SEARCH_TIMEOUT event and is not the beacon from the AND BPM. It is important to note that the BPM ONLY beacons (for about 30 seconds I believe) when it is turned on, and after a blood pressure measurement has been taken. It does not beacon constantly.

Try taking a blood pressure reading, then open the channel right after the measurement finishes. If your channel parameters are configured correctly, you should be able to view the data coming from the BPM. Ensure that your search timeouts are appropriately configured so that the channel is not closing too early.

Another thing that might be an issue is the proximity search threshold. What bin number are you using for setting proximity search?

Best Regards,

Kassandra      

Hi Kassandra

Thanks for the reply. OK I will try to take a new reading and then try to communicate again.


The proximity bin I had was 7. What should be the value for this. I tried with 5 and encountered same results.

- Albert      

Hi Albert,

There is no pre-defined distance to proximity bin correlation, it may be useful for you to take a look at the Design Considerations section of the Proximity Search application note: http://www.thisisant.com/images/Resources/PDF/ANT_AN12_Proximity_Search.pdf

I suggest making sure that you can pair to the device without configuring proximity search, before you start playing with the different threshold bins, that way you know that your application is receiving the data appropriately.

I hope this helps,

Kassandra      

Hi Kassandra

I am getting the pairing beacon as per the Document you sent me. Thanks. But Now I am facing other problems. In response to the first beacon I send a link command with frequency 57, channel period 8192 and a serial number 0x1 0x2 0x5 ox5.

- when I try ANTSendAcknowledgedData the ANTReceiver raises an unknown exception. So I tried the ANT SendBurstTransferData methos

I receive a response that the transmission was successfull.

After that I still receive the beacon and there is no change in the beacon. From the document I understood that the client ( BP monitor) would change to the requested period and frequency and also it would start responding with different beacon. This did not happen.

Rx:[09][4E][03][43][2B][00][03][12][00][15][00] - beacon

Tx:[02][39][02][01][02][05][05] - link command

Rx:[09][4E][03][43][2B][00][03][12][00][15][00] - beacon
Rx:[03][40][03][01][05] - response that transmission completed
Rx:[09][4E][03][43][2B][00][03][12][00][15][00] - beacon
Rx:[09][4E][03][43][2B][00][03][12][00][15][00] - beacon
Rx:[09][4E][03][43][2B][00][03][12][00][15][00] - beacon
Rx:[09][4E][03][43][2B][00][03][12][00][15][00] - beacon
Rx:[09][4E][03][43][2B][00][03][12][00][15][00] - beacon
Rx:[09][4E][03][43][2B][00][03][12][00][15][00] - beacon
Rx:[09][4E][03][43][2B][00][03][12][00][15][00] - beacon
Rx:[09][4E][03][43][2B][00][03][12][00][15][00] - beacon
Rx:[09][4E][03][43][2B][00][03][12][00][15][00] - beacon
Rx:[09][4E][03][43][2B][00][03][12][00][15][00] - beacon
Rx:[09][4E][03][43][2B][00][03][12][00][15][00] - beacon

eventually the beacon stops and the client goes back to link mode.

What am I doing wrong?

- albert