Welcome Guest,Register Now
Log In

ANT Forum

Welcome guest, please Login or Register

You are here: Forum Home → ANT+ Forums → ANT+ Bike Power → Thread

   

Custom calibration program with custom ANT+ messages

Rank

Total Posts: 4

Joined 2010-07-23

PM

I am developing a calibration program for a power meter that will be specific to the particular power meter. If I implement custom messages that will be recognized by the embedded hardware (i.e. sending a specific calibration value to the sensor) and the calibration program, will this violate the adopters agreement? All other messages that other than the calibration messages will be concurrent with the ANT+ power profile.

Thanks      
Avatar
RankRankRankRank

Total Posts: 296

Joined 0

PM

As far as I understand (and remember some remarks in the specs and this forum) the profiles define the REQUIRED set of messages for a device implementing a profile. You must implement the mandatory messages and all implemented messages must conform to the spec of that particular messages.
You may however freely define additional proprietary messages - which e.g. Tanita does for their BC-1000 weight scale that just implements the one mandatory message of the weight scale profile and sends other data in proprietary messages. They still claim to fulfil the profile and Dynstream staff has defended that in this forum as being perfectly legal.

However, if your needs are not far away from the Bike Power profile and your device could open up a new class of Bike Power devices, you should maybe contact Dynastream to add your needs as a new flavour of Bike Power devices to the profile.

Cheers,
OMB      
Avatar
RankRankRankRank

Total Posts: 662

Joined 2012-10-09

PM

Just to add to OMB's thorough answer, if you do decide to use custom messages, please make sure that you use page numbers in the manufacturer specific range.      
RankRankRankRank

Total Posts: 122

Joined 2010-10-25

PM

I hope this extra 'special' calibration is not somthing your users will want to be doing regualarly, or have to do to be able to use your device. Having to use something custom outside of the spec to use the device will effectivly break interoperability even if you implement everything else as per the spec.

Ifor