ANT Forum

Hello,

I'm trying to monitor traffic bewteen 2 ANT nodes using ANTWare II.
I can successfully open the channel in scan mode and see traffic but how can I identify which node sends what? Where do I see if data is sent from the master or the slave node?

Here is a sample of my log:

Received BROADCAST_DATA_0x4E
:: 4e, 00-00-72-B8-0E-0B-0B-03-1E
Received BROADCAST_DATA_0x4E
:: 4e, 00-00-72-B8-0E-0B-0B-03-1E
Received BROADCAST_DATA_0x4E
:: 4e, 00-AC-01-00-00-00-00-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-00-72-B8-0E-0B-0B-03-1E
Received BROADCAST_DATA_0x4E
:: 4e, 00-DD-03-00-00-1A-00-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-DD-02-00-00-00-00-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-DD-03-00-00-1B-00-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-DD-03-00-00-1B-00-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-DD-03-00-00-1B-00-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-DD-02-00-00-00-00-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-AC-01-00-00-00-00-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-DD-03-00-00-1B-00-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-DD-03-00-00-1B-00-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-DD-03-00-00-1B-00-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-DD-03-00-00-1B-00-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-AC-01-00-00-00-00-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-AD-01-01-0C-00-00-19-43
Received BROADCAST_DATA_0x4E
:: 4e, 00-AD-01-01-0C-00-00-19-43
Received BROADCAST_DATA_0x4E
:: 4e, 00-AC-02-00-00-00-00-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-DD-02-00-00-00-00-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-DD-02-00-00-00-00-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-DC-01-00-00-00-50-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-DD-02-00-00-00-00-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-DD-02-00-00-00-00-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-DC-02-00-99-00-00-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-DD-03-00-00-1C-00-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-AC-02-00-00-00-00-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-AD-02-01-01-01-0E-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-DC-01-00-00-00-50-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-DD-02-00-00-00-00-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-DD-02-00-00-00-00-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-DC-02-00-99-00-00-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-DD-02-00-00-00-00-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-DD-02-00-00-00-00-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-DC-01-00-00-00-50-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-DD-03-00-00-1C-00-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-DD-03-00-00-1C-00-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-DD-02-00-00-00-00-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-DC-02-00-99-00-00-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-DD-02-00-00-00-00-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-DD-01-00-00-00-00-00-30
Received BROADCAST_DATA_0x4E
:: 4e, 00-DC-01-00-00-00-50-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-DD-02-00-00-00-00-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-DD-03-00-00-1C-00-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-DD-01-00-00-00-00-00-30
Received BROADCAST_DATA_0x4E
:: 4e, 00-DC-02-00-99-00-00-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-DD-01-00-00-00-00-00-30
Received BROADCAST_DATA_0x4E
:: 4e, 00-DD-03-00-00-1D-00-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-DD-01-00-00-00-00-00-31
Received BROADCAST_DATA_0x4E
:: 4e, 00-DC-01-00-00-00-50-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-DD-01-00-00-00-00-00-31
Received BROADCAST_DATA_0x4E
:: 4e, 00-DD-01-00-00-00-00-00-31
Received BROADCAST_DATA_0x4E
:: 4e, 00-DD-02-00-00-00-00-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-DD-03-00-00-1D-00-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-DC-01-00-00-00-50-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-DD-03-00-00-1D-00-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-DD-03-00-00-1D-00-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-DC-02-00-99-00-00-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-DD-01-00-00-00-00-00-31
Received BROADCAST_DATA_0x4E
:: 4e, 00-DD-01-00-00-00-00-00-31
Received BROADCAST_DATA_0x4E
:: 4e, 00-DC-01-00-00-00-50-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-DD-01-00-00-00-00-00-31
Received BROADCAST_DATA_0x4E
:: 4e, 00-DD-01-00-00-00-00-00-32
Received BROADCAST_DATA_0x4E
:: 4e, 00-DD-02-00-00-00-00-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-DC-02-00-99-00-00-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-DD-02-00-00-00-00-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-DD-01-00-00-00-00-00-32
Received BROADCAST_DATA_0x4E
:: 4e, 00-DC-01-00-00-00-50-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-DD-02-00-00-00-00-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-DD-02-00-00-00-00-00-00
Received BROADCAST_DATA_0x4E
:: 4e, 00-DD-01-00-00-00-00-00-32
Received BROADCAST_DATA_0x4E
:: 4e, 00-DC-02-00-99-00-00-00-00

Thanks,

Pyt      

Hi Pyt,

ANT messages do not distinguish their source except through their Channel ID and Network Key parameters so there are no simple flags to determine which messages came from a master or from a slave.

One suggestion I have is to make use of time stamps, which you can enable as extended messages for more accurate timings or just use the PC time stamps in the log which only have 15ms of resolution but may be good enough for your application.
The slave can only transmit back to the master by responding on each master channel transmission, so these timings will appear to be extremely close when the slave makes a back channel transmission.

For example using PC logs and the PC timestamp (15ms resolution):

With back channeled ack:
56.286 { 524002101} Rx - [A4][0E][4E][00][00][00][00][00][00][00][00][D1][80][21][00][01][01][94] //Master
56.535 { 524002350} Rx - [A4][0E][4E][00][00][00][00][00][00][00][00][D2][80][21][00][01][01][97] //Master
56.535 { 524002350} Rx - [A4][0E][4E][00][53][68][61][6E][65][20][47][2E][80][21][00][01][01][5D] //Slave
56.535 { 524002350} Rx - [A4][0E][4E][00][00][00][00][00][00][00][00][D2][80][21][00][01][01][97] //Master
56.785 { 524002600} Rx - [A4][0E][4E][00][00][00][00][00][00][00][00][D3][80][21][00][01][01][96] // Master

With back channeled broadcasts:
679.119 { 524918326} Rx - [A4][09][4E][00][00][00][00][00][00][00][00][A4][47] //Master
679.368 { 524918575} Rx - [A4][09][4E][00][00][00][00][00][00][00][00][A5][46] //Master
679.368 { 524918575} Rx - [A4][09][4E][00][01][00][00][00][00][34][00][00][D6] //Slave
679.618 { 524918825} Rx - [A4][09][4E][00][00][00][00][00][00][00][00][A6][45] //Master
679.867 { 524919074} Rx - [A4][09][4E][00][00][00][00][00][00][00][00][A7][44] //Master
680.117 { 524919324} Rx - [A4][09][4E][00][00][00][00][00][00][00][00][A8][4B] //Master
680.367 { 524919574} Rx - [A4][09][4E][00][00][00][00][00][00][00][00][A9][4A] //Master
680.382 { 524919589} Rx - [A4][09][4E][00][01][00][00][00][00][34][00][00][D6] //Slave (jump in time due to resolution)
680.616 { 524919823} Rx - [A4][09][4E][00][00][00][00][00][00][00][00][AA][49] //Master

Burst messaging can cause this issues as the scanning node won't be able to pick up all of them (the serial bus is too slow). Also you won't be able to distinguish between message types.

Cheers      

Hi Harrison,

Thanks for the information, it sounds like a good workaround.
Could you tell me how to enable extended messages in ANTWare II?

Thanks,

Pyt      

Hi Pyt,

There is a manual tab among the Device Level Function Tabs as described in the ANTware II Users Guide which you can find under the Software tab in the Downloads section.

There you can manually send the command to enable Extended Messaging with Timestamps as described in the ANT Message Protocol and Usage document.

It will be command 6E-00-20 (Lib Config).

Cheers