|
| 1 | +<?xml version="1.0" encoding="utf-8"?> |
| 2 | +<topic id="2c4b4d97-d5ec-44ef-846e-d8849c278fad" revisionNumber="1"> |
| 3 | + <developerConceptualDocument |
| 4 | + xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5" |
| 5 | + xmlns:xlink="http://www.w3.org/1999/xlink"> |
| 6 | + |
| 7 | + <!-- |
| 8 | + <summary> |
| 9 | + <para>Optional summary abstract</para> |
| 10 | + </summary> |
| 11 | + --> |
| 12 | + |
| 13 | + <introduction> |
| 14 | + <!-- Uncomment this to generate an outline of the section and sub-section |
| 15 | + titles. Specify a numeric value as the inner text to limit it to |
| 16 | + a specific number of sub-topics when creating the outline. Specify |
| 17 | + zero (0) to limit it to top-level sections only. --> |
| 18 | + <!-- <autoOutline /> --> |
| 19 | + |
| 20 | + <para> |
| 21 | + The AntRadioInterface class library defines interfaces and classes that implementations support and clients utilize. |
| 22 | + Implementations will derive and implement the interfaces appropriate to the underlying hardware that supports the ANT |
| 23 | + radio protocol. Clients will interact with an implementation of the AntRadioInterface to communicate with ANT devices. |
| 24 | + </para> |
| 25 | + <para> |
| 26 | + Implementations at a minimum implement the IAntRadio and IAntChannel interfaces and derive concrete classes from |
| 27 | + AntResponse and DeviceCapabilities. Implementations may optionally support IAntConfiguration, IAntControl, IAntUsbRadio, |
| 28 | + ICrypto, and IFitSettings interfaces. |
| 29 | + </para> |
| 30 | + <alert class="tip"> |
| 31 | + <para> |
| 32 | + Implementations are free to implement the interfaces the underlying hardware supports. Even specific methods of required |
| 33 | + interfaces can and should throw NotImplementedException() if hardware doesn't support a particular method. This informs |
| 34 | + the application developer that the client and implementation are not aligned regarding expected functionality. |
| 35 | + </para> |
| 36 | + </alert> |
| 37 | + </introduction> |
| 38 | + |
| 39 | + <!-- Add one or more top-level section elements. These are collapsible. |
| 40 | + If using <autoOutline />, add an address attribute to identify it |
| 41 | + and specify a title so that it can be jumped to with a hyperlink. --> |
| 42 | + <section address="Section1"> |
| 43 | + <title>Interfaces and Classes</title> |
| 44 | + <content> |
| 45 | + <!-- Uncomment this to create a sub-section outline |
| 46 | + <autoOutline /> --> |
| 47 | + <para> |
| 48 | + These interfaces/classes largely mirror the Garmin/Dynastream ANT Message Protocol and Usage specification. |
| 49 | + </para> |
| 50 | + </content> |
| 51 | + <sections> |
| 52 | + <section> |
| 53 | + <title>AntResponse and DeviceCapabilities</title> |
| 54 | + <content> |
| 55 | + <para> |
| 56 | + Mandatory. Implementations will derive from these classes and provide constructors that take the underlying |
| 57 | + hardware data as an argument to populate the properties exposed by these classes. |
| 58 | + </para> |
| 59 | + </content> |
| 60 | + </section> |
| 61 | + <section> |
| 62 | + <title>IAntRadio</title> |
| 63 | + <content> |
| 64 | + <para> |
| 65 | + Mandatory. Methods that must be implemented are InitializeContinuousScanMode(), GetChannel(), GetDeviceCapabilities(), |
| 66 | + RequestMessageAndResponse() and the properties NumChannels, ProductDescription, SerialNumber and Version. |
| 67 | + </para> |
| 68 | + </content> |
| 69 | + </section> |
| 70 | + <section> |
| 71 | + <title>IAntChannel</title> |
| 72 | + <content> |
| 73 | + <para> |
| 74 | + Mandatory. SendExtAcknowledgedData/SendExtAcknowledgedDataAsync methods must be implemented; they are integral to |
| 75 | + working with ANT devices. The only property is ChannelNumber which should be assigned a value relevent to the |
| 76 | + implementation. |
| 77 | + </para> |
| 78 | + <alert class="tip"> |
| 79 | + <para> |
| 80 | + Implementors: Consider using locks for methods that transmit data to ANT devices. The intent is to prevent overwriting the channel |
| 81 | + ID and data until the transmission succeeds or times out. |
| 82 | + </para> |
| 83 | + </alert> |
| 84 | + </content> |
| 85 | + </section> |
| 86 | + <section> |
| 87 | + <title>IAntConfiguration</title> |
| 88 | + <content> |
| 89 | + <para>Optional. Implementors will provide methods to configure the ANT radio.</para> |
| 90 | + </content> |
| 91 | + </section> |
| 92 | + <section> |
| 93 | + <title>IAntControl</title> |
| 94 | + <content> |
| 95 | + <para>Optional. Implementors will provide methods to control general operation of the ANT radio.</para> |
| 96 | + </content> |
| 97 | + </section> |
| 98 | + <section> |
| 99 | + <title>IAntUsbRadio</title> |
| 100 | + <content> |
| 101 | + <para>Optional. Implementors will provide methods and properties specific to ANT radios connected to USB ports.</para> |
| 102 | + </content> |
| 103 | + </section> |
| 104 | + <section> |
| 105 | + <title>ICrypto</title> |
| 106 | + <content> |
| 107 | + <para>Optional. Implementors will provide methods to configure cryptographic functions used by the ANT radio.</para> |
| 108 | + </content> |
| 109 | + </section> |
| 110 | + <section> |
| 111 | + <title>IFitSettings</title> |
| 112 | + <content> |
| 113 | + <para>Optional. Implementors will provide methods to manage the ANT radio fitness equipment state.</para> |
| 114 | + </content> |
| 115 | + </section> |
| 116 | + </sections> |
| 117 | + </section> |
| 118 | + |
| 119 | + <relatedTopics> |
| 120 | + <codeEntityReference>T:SmallEarthTech.AntRadioInterface.IAntRadio</codeEntityReference> |
| 121 | + <codeEntityReference>T:SmallEarthTech.AntRadioInterface.IAntChannel</codeEntityReference> |
| 122 | + <codeEntityReference>T:SmallEarthTech.AntRadioInterface.AntResponse</codeEntityReference> |
| 123 | + <codeEntityReference>T:SmallEarthTech.AntRadioInterface.DeviceCapabilities</codeEntityReference> |
| 124 | + <codeEntityReference>T:SmallEarthTech.AntRadioInterface.IAntConfiguration</codeEntityReference> |
| 125 | + <codeEntityReference>T:SmallEarthTech.AntRadioInterface.IAntControl</codeEntityReference> |
| 126 | + <codeEntityReference>T:SmallEarthTech.AntRadioInterface.IAntUsbRadio</codeEntityReference> |
| 127 | + <codeEntityReference>T:SmallEarthTech.AntRadioInterface.ICrypto</codeEntityReference> |
| 128 | + <codeEntityReference>T:SmallEarthTech.AntRadioInterface.IFitSettings</codeEntityReference> |
| 129 | + <!-- One or more of the following: |
| 130 | + - A local link |
| 131 | + - An external link |
| 132 | + - A code entity reference |
| 133 | +
|
| 134 | + <link xlink:href="Other Topic's ID"/> |
| 135 | + <link xlink:href="Other Topic's ID">Link inner text</link> |
| 136 | +
|
| 137 | + <externalLink> |
| 138 | + <linkText>Link text</linkText> |
| 139 | + <linkAlternateText>Optional alternate link text</linkAlternateText> |
| 140 | + <linkUri>URI</linkUri> |
| 141 | + </externalLink> |
| 142 | +
|
| 143 | + <codeEntityReference>API member ID</codeEntityReference> |
| 144 | +
|
| 145 | + Examples: |
| 146 | +
|
| 147 | + <link xlink:href="00e97994-e9e6-46e0-b420-5be86b2f8270" /> |
| 148 | + <link xlink:href="00e97994-e9e6-46e0-b420-5be86b2f8278">Some other topic</link> |
| 149 | +
|
| 150 | + <externalLink> |
| 151 | + <linkText>SHFB on GitHub</linkText> |
| 152 | + <linkAlternateText>Go to GitHub</linkAlternateText> |
| 153 | + <linkUri>https://GitHub.com/EWSoftware/SHFB</linkUri> |
| 154 | + </externalLink> |
| 155 | +
|
| 156 | + <codeEntityReference>T:TestDoc.TestClass</codeEntityReference> |
| 157 | + <codeEntityReference>P:TestDoc.TestClass.SomeProperty</codeEntityReference> |
| 158 | + <codeEntityReference>M:TestDoc.TestClass.#ctor</codeEntityReference> |
| 159 | + <codeEntityReference>M:TestDoc.TestClass.#ctor(System.String,System.Int32)</codeEntityReference> |
| 160 | + <codeEntityReference>M:TestDoc.TestClass.ToString</codeEntityReference> |
| 161 | + <codeEntityReference>M:TestDoc.TestClass.FirstMethod</codeEntityReference> |
| 162 | + <codeEntityReference>M:TestDoc.TestClass.SecondMethod(System.Int32,System.String)</codeEntityReference> |
| 163 | + --> |
| 164 | + </relatedTopics> |
| 165 | + </developerConceptualDocument> |
| 166 | +</topic> |
0 commit comments