Paging all BLE experts...

I've been messing around with this for some more, but no luck so far.  I am confused as to why my Edge 530 shows 30+ BLE scan results using BleScan (including the one I'm looking for), whereas my FR945 right next to it, shows 0 scan results. 

Running my own program in the simulator shows no scan results, just the real FR945 running BleScan.  Regardless of whether I simulate the Edge or FR. 

Do you get the same results between a real device and running the simulator for BleScan?  When I developed another data field, everything worked super great and I had a 100% correlation between simulator and real device.

Which of the 5 buttons on my FR945 constitutes the "Menu" button mentioned in the BleScan description?  Up/Down does what I expect, select switches to raw mode and Light/Power does nothing.

If the 945 isn't showing any scan results, try rebooting it.  Press and hold the light button for about 15 seconds and the watch will turn itself off, then turn it back on.

If you're not seeing anything on either device in the sim, try restarting the sim, maybe after unplugging/replugging the Nordic HW and making sure the sim is configured correctly for ble.

As gasterpod said, "menu" on a 5 button device is a long press of the middle left button

Thanks for the replies.  I found the menu option :).

Maybe I should have started with describing my environment.  I have developed a CIQ Data Field that connects directly to a BLE rowing power meter that uses a non-standard protocol.  That all works great.  But the device can't be connected to both the Garmin and the rower companion phone app at the same time.

The phone app has recently started rebroadcasting the data using more standard protocols.  One of these protocols is FTMS. I am trying to connect to that broadcast, so that users can use the original app as well as capture their training on their Garmin devices.

When I run the simulator and BleScan on my FR945, this is what happens:

1. I start the rower.
2. BleScan and simulator immediately sees the advertisement from the rower.
3. I connect the phone app to the rower.
4. Both simulator and BleScan stops seeing the advertisement because it is no longer advertising.
5. I start the FTMS broadcast feature on the phone app.
6. Neither BleScan on the FR945, not the simulator sees this advertisement.
7. However, BleScan on the Edge 350 DOES see it.

I doubt this has anything to do with the 20 byte truncation, since I see advertising packets that are bigger than 20 bytes in BleScan, and the one I'm interested in, shows as 19 bytes in BleScan.

I'm certain my simulator environment is set up correctly since I see some advertisements.

I think my next step is to write a bug report and see what Garmin has to say.

With BLE, it's typically 1 to 1.  Only one device can be paired to a device.  So it's the Garmin or the phone, but not both.

And with a phone, it probably has the additional wrinkle where the phone is already paired to the Garmin in the standard way, so your app can't also be paired with the phone.

Many have tried, but I'm not sure anyone has been able to pair with a phone using CIQ.  Been that way for years, and I'm sure there are already bug reports about it

For me this sounds like your device stops advertising after it is paired with the phone. Thus, Garmin can't see it.

Except that the edge 530 does see it. There is clearly something about the broadcast that the sim and 945 does not like. 

Same Garmin firmware version on 530 + 945? (currently x.75)

I am not concerned with multiple connections, and I've tried this various devices which have never been paired with my Garmins. 

And as @gasterpod points out, the Edge sees it.  Both devices are paired to my phone for Connect. Both devices are up to date.  The FR945 is enrolled in the beta program and got an update today, and the Edge got an update fairly recently, if I remember correctly.

Regarding pairing with a phone - not sure if you checked out the @OnlyTwo's link above.  That sounds promising but again the Edge sees it.  Although they are different device, probably with different firmware implementations.

I would still try rebooting the 945 (not just a power cycle).  That can clear up many odd things.