RSSi Testing

Former Member
Former Member
I am working on the ANT protocol for a product we've developed, called RunScribe [a shoe-worn running sensor], and am seeing some issues on Fenix 5 watches with our ANT [not +] Connect IQ datafield app. Performance is *solid* on the 935, 235, and 735XT.

I'm interested in quantifying the RSSi from the pods, and have searched the forum, finding mostly older threads on this topic.

I generally use my USB-m ANT Stick, along with Dynastream's ANTWare II program to see packets, but as I understand it, the USB-m stick doesn't support RSSi.
Wondering what the best option is? I've looked at the N5 mentioned in 2015 threads, but am wondering if there is anything more recent that would be a better fit for the job?

Thanks!
-Tim
  • I don't know about the ANT-m stick support.

    The North Pole Engineering Wasp and Wasp Utility show RSSI live. The RSSI value would range from about -2 (almost touching) to -50 at about 15 feet away.

  • It seems like the RSSI provides something useful on a Fenix 3 watch but not on the simulator (with an ANT-m stick)

    I put the following code inside my onMessage(msg) function of the Generic ANT Channel.

    var rssi = msg.rssi;
    Sys.println("RSSI: " + rssi);


    The Sim produced the following output. It seemed to only get 1, 0, or null.

    RSSI: null
    RSSI: null
    RSSI: null
    RSSI: null
    RSSI: null
    RSSI: null
    RSSI: null
    RSSI: null
    RSSI: null
    RSSI: null
    RSSI: null
    RSSI: null
    RSSI: null
    RSSI: null
    RSSI: null
    RSSI: 0
    RSSI: 0
    RSSI: 1
    RSSI: 1
    RSSI: 0
    RSSI: 0
    RSSI: 0
    RSSI: 0
    RSSI: 0
    RSSI: 0
    RSSI: 1
    RSSI: 1
    RSSI: 0
    RSSI: 0
    RSSI: 0
    RSSI: 0
    RSSI: 0
    RSSI: 0
    RSSI: null
    RSSI: null
    RSSI: 0
    RSSI: 0
    RSSI: null
    RSSI: null
    RSSI: 1
    RSSI: 1
    RSSI: null
    RSSI: null
    RSSI: 1
    RSSI: 1
    RSSI: null
    RSSI: null
    RSSI: 1
    RSSI: 1
    RSSI: null
    RSSI: null
    RSSI: 1
    RSSI: 1
    RSSI: 1
    RSSI: 1
    RSSI: 1
    RSSI: 1
    RSSI: 1
    RSSI: 1
    RSSI: 1
    RSSI: 1
    RSSI: 1
    RSSI: 1
    RSSI: null
    RSSI: null
    RSSI: null
    RSSI: null
    RSSI: null
    RSSI: null
    RSSI: null
    RSSI: null
    RSSI: null
    RSSI: null
    RSSI: null
    RSSI: null
    RSSI: null
    RSSI: null
    RSSI: null



    The same code on a Fenix 3 watch produced this output. 200 was close, 177 was far away.

    RSSI: null
    RSSI: null
    RSSI: 186
    RSSI: 210
    RSSI: null
    RSSI: 210
    RSSI: null
    RSSI: null
    RSSI: null
    RSSI: null
    RSSI: null
    RSSI: 210
    RSSI: 211
    RSSI: 212
    RSSI: 212
    RSSI: 190
    RSSI: 191
    RSSI: 189
    RSSI: null
    RSSI: 211
    RSSI: 206
    RSSI: 201
    RSSI: 199
    RSSI: 202
    RSSI: 200
    RSSI: null
    RSSI: 201
    RSSI: 185
    RSSI: 191
    RSSI: 199
    RSSI: 197
    RSSI: 196
    RSSI: 192
    RSSI: 185
    RSSI: 188
    RSSI: 191
    RSSI: 192
    RSSI: 199
    RSSI: 200
    RSSI: 183
    RSSI: 183
    RSSI: 183
    RSSI: 184
    RSSI: 184
    RSSI: 184
    RSSI: 185
    RSSI: 188
    RSSI: 183
    RSSI: 188
    RSSI: 186
    RSSI: 189
    RSSI: 178
    RSSI: 183
    RSSI: 188
    RSSI: 188
    RSSI: 187
    RSSI: 187
    RSSI: 186
    RSSI: 186
    RSSI: 184
    RSSI: 184
    RSSI: 179
    RSSI: 164
    RSSI: 177
    RSSI: null
    RSSI: 166
    RSSI: 171
    RSSI: 169
    RSSI: null
    RSSI: 169
    RSSI: 159
    RSSI: 161
    RSSI: 175
    RSSI: 172
    RSSI: 164
    RSSI: 178
    RSSI: 175
    RSSI: 176
    RSSI: 177
    RSSI: 177
    RSSI: 177
    RSSI: 177
    RSSI: 177
    RSSI: 177
    RSSI: 178
    RSSI: 175
    RSSI: 180
    RSSI: 179
    RSSI: 181
    RSSI: 180
    RSSI: 178
    RSSI: 181
    RSSI: 180
    RSSI: 182
    RSSI: null
    RSSI: 181
    RSSI: 185
    RSSI: 188
    RSSI: null
    RSSI: 200
    RSSI: 202
    RSSI: 204
    RSSI: 204
    RSSI: 202
    RSSI: 202
    RSSI: 206
    RSSI: 201
    RSSI: 202
    RSSI: 201
    RSSI: 199
    RSSI: 198
    RSSI: 198
    RSSI: null
    RSSI: 192
    RSSI: 196
    RSSI: 192
    RSSI: 204
    RSSI: 202
    RSSI: 195
    RSSI: 200
    RSSI: 203
    RSSI: 194
    RSSI: 203
    RSSI: 203
    RSSI: 203
    RSSI: null
    RSSI: null
    RSSI: null
    RSSI: null
    RSSI: null
    RSSI: null
    RSSI: null
  • I am working on the ANT protocol for a product we've developed, called RunScribe [a shoe-worn running sensor], and am seeing some issues on Fenix 5 watches with our ANT [not +] Connect IQ datafield app. Performance is *solid* on the 935, 235, and 735XT.

    I'm interested in quantifying the RSSi from the pods, and have searched the forum, finding mostly older threads on this topic.

    I generally use my USB-m ANT Stick, along with Dynastream's ANTWare II program to see packets, but as I understand it, the USB-m stick doesn't support RSSi.
    Wondering what the best option is? I've looked at the N5 mentioned in 2015 threads, but am wondering if there is anything more recent that would be a better fit for the job?

    Thanks!
    -Tim


    Hi Tim,

    bought the footpods last night - and i've a fenix5... there are still issues with that combination?