Simultaneous use of Sensor and AntPlus APIs.

How are you trying to generate data in the sim?  Simulation>Activity Data? If you are playing back a fit file, does it have the data you are looking for?

The 7.2.1 seems to have an issue with data simulation, so you may want to stick with playing back a fit file.

Hey Jim.  thanks for the quick response.
I am connecting my devices as ANT+ sensors (In CIQ simulator: Settings->Manage Ant+ sensors)

Either way though, the issue is present on my physical device (Garmin 830) - I cannot simultaneously get data from Sensor and AntPlus libraries.

So after further experimentation it seems like using Sensor API is stopping AntPlus events from firing properly both in the simulator (using ANT+ sensors rather than FIT file playback) and Edge830.

I have a bikepower listener as follows:

class antplus_bpwr_listener extends AntPlus.BikePowerListener
{
	hidden var m_sensor;
	function initialize(sensor)
	{
		m_sensor = sensor;
		BikePowerListener.initialize();
	}
	
	function onMessage(msg)
	{
	 	if (msg.messageId == 0x4E)
		{
			logging.log("0x4E from device number " + msg.deviceNumber);
		}
	}

    function onCalculatedPowerUpdate(data) {
        logging.log("Recieved power value = " + data.power);
		m_sensor.addData(data.power);
    }
}

The "OnCalculatedPowerUpdate" event fires fine until I enable sensor events, i.e. as soon as I call this:

Sensor.enableSensorEvents(method(:onSensor));

it stops working.

Weirdly the "onMessage" event still fires, so I can see a broadcast message coming from my bikepower sensor, but the data is not there.  I have tried removing bikepower from the list of enabled sensors, but that generally causes the bike power sensor to disconnect.

So it seems like unless I write my own decoder for the bikepower ANT messages I'm a bit stuck.

I appreciate its a bit of an odd combination of requirements, but it is very limiting.  Is this a bug?
I'm using SDK 7.1.0

One more thing - part of my troubles stem from the fact that Sensor.speed doesn't necessarily come from the ANT+ speed sensor, so if I am testing indoors, with a simulated ANT+ speed sensor the sensorInfo.speed value is not reported at all (it is null).  
So in short I need to:

• Use Sensor.sensorInfo for speed and heartrate data.
• Use AntPlus to report the power meter and speed sensor deviceId.
• Manually decode the ANT messages in the AntPlus.BikeSpeedListener onMessage event (since onBikeSpeedUpdate doesn't fire).

If anyone knows of a better way to achieve this I'm all ears!  

Since when the manage ant sensors menu works? Last time I checked everyone wrote that it never worked

It works, just not very well.  I rely heavily on it because of my application. 
Trouble is that when you open it nothing happens - it takes a long time to find devices.  
For me the best way is to stop the debugger executing, leaving the CIQ simulator window open (but no longer showing your UI), then try.  That way it picks up the ANT+ sensors in a few seeconds.  You can then restart your code and it will be able to see the ANT+ data.
Whilst my code is executing it can take 2-3 minutes which is frustrating.

flocsy🤠 said:

Since when the manage ant sensors menu works?

For me, it works flawlessly.
I build the datafield (for Edge devices) and once it is shown in the sim, I often have to connect Varia radar for testing purpose. Finds radar and light within seconds, then pair and it works. (that’s since 4.2. I‘m now on 7.2.1)

I think it depends what else you are doing - I suspect I struggle because I am using ANT Generic channel as well which seems to slow the simulator ANT search down way more than it should.

Aaaahhhhh! It works! It NEVER worked for me, but now I understand why. It is not intended for what I need. In fact it works exactly as the real watch in the following way:

each ANT device is either paired to the watch / paired in ANT+ Sensors manager

OR

is detectable with GenericChannel

This is why it never worked for me, because I always Run my app and that opens the simulator window, where I tried to do something with the ANT manager, but it was always too late, because by that time my app connected to it.

BUT this will be now useful for something I wanted to do for a long time: see a good way to determine (and display) the source of the ActivityInfo.currentHeartRate