Welcome Guest,Register Now
Log In

ANT Forum

Welcome guest, please Login or Register

   

gsc 10 + suunto mini + demo_net

Rank

Total Posts: 12

Joined 0

PM

Hi there,

I am trying to get data from a GSC 10 which I use in conjunction of a Suunto mini USB stick. I am unable to receive data with the sample application DEMO_NET. I set the application to slave (1) then I also managed to get Request Capabilites, Request Version, Request Channel ID, Request USB Descriptor. However the application does not receive any data from the GSC 10.

Both work fine with the Display Simulator, it retrieves information from the sensor and displays the speed and cadence. From the application I have got the following information:

device ID=24369,
transmission type=1,
device type=121
Period=8086.

I have downloaded the ANT+ device profile for Bike speed and cadence and found out that some values are different:

device ID=0,
transmission type=0,
device type=123
Period=8118.

Which set of values should I use in order to get the data in the demo_net sample application?

Is there anyway I can get all the necessary data to set the sample application (demo_net) from the Display Simulator application. I wanted to breakpoint through the code of the Display Simulator but when i tried to open it with the Visual studio 2010 the application converted the solution to VS 2010. When I tried to build the Display simulator I get the following error :
Error 13 error LNK1316: duplicate managed resource name '...\\antplus_simulator_src\\antplus_simulator_src\\Debug\\ANT+SensorSimulator\\ANTPlusSim.%(Filename).resources
How can I fix this error?


Can someone help me with getting the parameters I need to get the sample application demo_net to work so I can retrieve data from the sensor like in the Display simulator?

Many Thanks
Seb      
Avatar
RankRankRankRank

Total Posts: 296

Joined 0

PM

The GSC10 is a combined bike speed and cadence sensor.
Have a look in the profile for the correct device type and tramsmission interval settings for that sensor type.
The 0 for device id and transmission type is a wildcard that lets the slave connect to any master (= sensor) of the specified device type.      
Rank

Total Posts: 12

Joined 0

PM

Ok, I am going to try this.
Do I (someone) need to find out about the network key? is this unique to each manufacturer? If yes how do I get it?      
Avatar
RankRankRankRank

Total Posts: 296

Joined 0

PM

Did you already find the forum search - in the upper right?
Searching for "network key" yields several helpful results.

To make things even easier for you smile :
You find a link to the network keys here: http://www.thisisant.com/pages/ant/ant-device-profiles (you need to be an ANT+ adopter to access that page).

May I suggest that you read the document "ANT Message Protocol and Usage" that the "Bike Speed and Cadence" refers to in chapter 2 "Related Documents" - if you've not already done so.
That'll give you a solid foundation for working with ANT+.      
Rank

Total Posts: 12

Joined 0

PM

Cool,
Thanks I managed to get everything to work.

However the Bike speed and Cadence Ant+ device profile document did not provide the correct values to communicate with the sensors. I had to use the values I got from the display simulator.

Thanks for your help

S      
Rank

Total Posts: 12

Joined 0

PM

I have been trying to increase the speed at which the device sends data to the computer but Have been unsuccessful.

in the demo_net example I tried to add this code

if(channel0.setChannelPeriod(0x1FB6 ,500))
Debug.WriteLine("radio frequency set");
else
throw new Exception("Error configuring Radio frequency");

just after the setting the channel frequency but the code throws an error.


What is the way to increase the time period between each set of data. the display simulator has a much faster rate which i'd like to get in my application

thanks      
Rank

Total Posts: 12

Joined 0

PM

also the demo_net sends a lot of Rx Fail any idea why this is happening?      
Rank

Total Posts: 12

Joined 0

PM

Hi,

I have managed to the period to work it's currently set to 8118.

However I get one good reading and the rest is Rx Fail.

If I increase the period I get less reading (which normal) but only only reading is actual data the rest is RX fail.
If I decrease the period I get more reading but only one is actual dat the rest is Rx Fail.

What I trying to get is more valuable reading from the sensor so i can update my app more frequently. As I said in a previous post the display sensor seems to be doing this very successfully.

What the settings I need to look at?

Seb      
Avatar
RankRankRankRank

Total Posts: 662

Joined 2012-10-09

PM

It is not possible to change how often the sensor transmits data: the channel period is fixed, as specified in the device profile.

In order to receive all the data that the sensor is sending, the channel period configured in your receiver must match that of the sensor, and should be exactly the one specified in the profile. Getting multiple Rx fails is often a symptom of mismatched channel periods.

When configuring the channel period, please keep the following in mind
* When using the PC libraries, it is not necessary to encode the value as little Endian, as this is done internally by the libraries.
* Make sure you are configuring the channel period for the right sensor type. For the bike speed and cadence profile, you can have a speed only sensor, a cadence only sensor and a bike speed and cadence (combined) sensor.

It seems you already got it working with the simulator - make sure you are looking at the right section of the profile corresponding to the sensor you are intending to communicate with. The parameters in the simulator do match those in the device profile.
.      
Rank

Total Posts: 12

Joined 0

PM

@ alejandra - thanks the tips I did manage to change the periode. I had read the wrong part of the document hence the wrong values in the software.      
Rank

Total Posts: 12

Joined 0

PM

Hi,

I am experiencing a strange problem. I start/init the device and its channel in between each session but when the bike wheel is spinning really fast when I end a session by quitting the channel and the device, on the next session I am still (from what it seems) geting data from the previous session. Is that even possible?

This does not seem to happen when the wheel spins slowly.

Is the Garmin sensor holding data? are they data floating in the air?

I can't seem to figure out what it is.

Many thanks