<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Damir Ban on Medium]]></title>
        <description><![CDATA[Stories by Damir Ban on Medium]]></description>
        <link>https://medium.com/@damir.ban?source=rss-8d8f9c8fc388------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*XVIBDeTLoJqsJXb-0vwG7A.jpeg</url>
            <title>Stories by Damir Ban on Medium</title>
            <link>https://medium.com/@damir.ban?source=rss-8d8f9c8fc388------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 02:08:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@damir.ban/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[ANT+ in mobile software QA landscape]]></title>
            <link>https://medium.com/greypbikes/ant-in-mobile-software-qa-landscape-74bf1dc83d50?source=rss-8d8f9c8fc388------2</link>
            <guid isPermaLink="false">https://medium.com/p/74bf1dc83d50</guid>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[fitness-equipment]]></category>
            <category><![CDATA[connectivity]]></category>
            <category><![CDATA[testing-tools]]></category>
            <dc:creator><![CDATA[Damir Ban]]></dc:creator>
            <pubDate>Thu, 24 Nov 2022 18:12:53 GMT</pubDate>
            <atom:updated>2022-12-05T08:31:00.892Z</atom:updated>
            <content:encoded><![CDATA[<p>On the technology side of Greyp Bikes, it was always about combining different aspects of cycling and technology to give our customers a more connected and involving experience with their e-bike. But there is only so much that you can fit in a time &amp; budget-constrained hardware project before you need to release it to the market. What you can keep evolving and improving in shorter iterations once the product is out is the software. For the mobile app development team, this means that integrations with other hardware products, which cannot be resolved through the hardware already released on the e-bike, can also fall into our domain. Examples of these are speed and cadence sensors, cycling computers, power meters, different wearables, electronic shifters and such.</p><p>There is a fairly large number of devices on the bike components or fitness market that we would potentially like to integrate. For that reason, we investigate different solutions to simulate and mock the communication before actually investing in physical devices to polish the final integration. Historically, the communication protocol of choice in that space was ANT, backed and pushed by Garmin. This protocol later evolved into ANT+.</p><h3>ANT+ in general</h3><p>ANT (Advanced and Adaptive Network Technology) is a short-range wireless communication protocol with an emphasis on extremely efficient power usage on the radio level. The requirement was to prolong the battery lifespan in small sensors or remote devices that draw power from 3V button cell batteries.</p><p>ANT was invented by Dynastream Innovations, now part of Garmin. At the time when Dynastream Innovations introduced the first speed and distance monitor for runners in 2000, there were no wireless protocols for communicating sensor data to watch receivers nor were they capable of running on a watch battery. So, to get their first products to the market it was necessary to develop this new protocol.</p><p>It is now the underlying protocol of evolved ANT+, a communication interface standard for ultra-low power devices.</p><p>ANT+ ecosystem has a concept of device profiles to standardize sets of information that can be shared between different devices supporting the same profile. Each profile has some minimum certification requirements to ensure compliance between different manufacturers’ implementations. Data packet payloads, master and slave channel setup and other specifics are described in those documents.</p><p>Each profile also has standardized Activity Icons, to visually help customers understand what the device supports.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/920/1*3BucGozGkCXWnznNWr9VIQ.jpeg" /><figcaption>Some of ANT+ activity icons</figcaption></figure><h3>Test set up</h3><p>Initially, we wanted to set up the bare bones simple app to receive data from wireless shifting groupset and display it. During the preparations, we found out that the actual number of mobile phones that have ANT+ chipset on Android phones is quite small and growing obsolete, but even more concerning was that there is absolutely no support on the iOS side. At that point, from the mobile apps development team’s perspective, it was clear that we will not integrate with ANT+. Nonetheless, some knowledge of the tools and protocol is nice to have for other applications inside the company, so we proceeded with test setup to see how we might utilize it in QA and troubleshooting tasks.</p><h3>Environment, devices &amp; tooling</h3><p>To be able to confirm we can send and receive test telemetry in both ways — to and from devices, there are some prerequisites — test computer with ANT+ interface on which to create and monitor the telemetry, some devices with ANT+ enabled hardware to serve as telemetry sources or destinations, depending on the use case, and tools or scripts to prepare, send and receive data.</p><p><strong>ANT+ USB dongle</strong></p><p>Plugged in Lenovo T series laptop, this little piece of hardware contains the ANT transceiver and enables communication with other devices.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xiaa88iUAyjVtf2LFrP9Pw.jpeg" /><figcaption>ANT+ USB dongle</figcaption></figure><p><strong>SRAM ASX Force wireless groupset</strong></p><p>Modern mid to high-end groupsets from leading manufacturers always have a wireless shifting option. Usually, the internal control protocols for remote wireless shifting are proprietary, but they still expose some data over BLE and ANT+. We already had <a href="https://www.sram.com/en/sram/road/series/sram-force-etap-axs">ASX Force</a> on some of our test e-bikes, so decided to test with those.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C-gWFl-I2BeMLSKe3pLcHA.jpeg" /><figcaption>Slightly beaten up ASX Force derailleur, but still shifting perfectly</figcaption></figure><p>ANT+ available information from this system (Ant+ Shift profile):</p><ul><li>gear selection</li><li>number of shifts</li><li>battery status</li></ul><p><strong>Garmin Forerunner 45 watch</strong></p><p>Entry-level fitness tracker/smartwatch with the option to connect heart rate monitor, speed and cadence sensors over ANT+.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LjlDvl0QjG2-BOu3E0x9WA.jpeg" /><figcaption>Garmin Forerunner 45</figcaption></figure><p><strong>SimulANT+</strong></p><p>From the QA side of things, we were looking into scripting options, preferably in Python. As there were no actively maintained libraries available that suited our use cases, we chose <a href="https://www.thisisant.com/news/simulant-next-generation-ant-simulation-tool-now-available">SimulANT+</a> and the scripts that came with it. It is a GUI tool provided by Garmin, only available for Windows. It has a set of prepared scripts for the most common simulation scenarios, written in <a href="https://ironpython.net/">IronPython</a>. They can be easily adapted to suit the needs of particular testing scenarios and you can load and run them through the tool. SimulANT+ provides the option to trace ANT+ traffic between devices in raw format, as well as show the configuration and data in a human-readable format for easy interpretation and monitoring.</p><h3>Use cases</h3><p><strong>A.<em> Test how to observe the electronic shifter battery status and gear selection on the test laptop over ANT+.</em></strong></p><p>ANT+ device profiles often come in pairs. Profiles that are implemented in the devices that are the source of some data usually have <em>Sensor</em> in the name, while the devices which receive and show that data to the user use the word <em>Display</em>. In the case of wireless bike shifters, the profile that we are using in the SimulANT+ is Shifting Display.</p><p>Pre-requisites:</p><ol><li>Plug in ANT+ USB dongle in laptop.</li><li>Download and install ANT+ drivers if the device is not automatically recognized.</li><li>Download and install SimulANT+ tool.</li></ol><p>Steps:</p><ol><li>Open SimulANT+ and confirm ANT device is visible. In our case Dev0:USB2 in the screenshot below.</li><li>Load Shifting Display profile through Add Simulator.</li><li>Under Actions section click on TurnOn button.</li><li>Shift gears on the test bike and observe Current Gear — Rear values under Data Pages → Shift System Status section in Properties pane.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2ccZPfSGDdOOXedMEHlrOg.jpeg" /><figcaption>SimulANT+ interface. Shifting Display profile loaded, observing the gear changes from SRAM ASX Force system.</figcaption></figure><p><strong>B. <em>Test how to send the simulated telemetry information from the test laptop to Garmin watch over ANT+.</em></strong></p><p>With the same pre-requisites as in the previous example open the SimulANT+. This time it will serve as a source.</p><p>Steps:</p><ol><li>Open SimulANT+ and confirm ANT device is visible.</li><li>Load Heart Rate Sensor profile through Add Simulator.</li><li>Under Actions section click on TurnOn button.</li><li>On the Forerunner 45 navigate to Settings and <a href="https://www8.garmin.com/manuals/webhelp/forerunner45/EN-US/GUID-87B163D1-9CDD-4705-9E6F-0B4324C54950.html">pair</a> this simulated Heart Rate Sensor.</li><li>Under Script section, select hr_SensorSweep.py and click on Run. This script is sweeping from 45 to 200 and back. The values and intervals can be adjusted in the code. You can monitor the values in the Properties section, Configuration → Heart Rate (bpm).</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WI3nwGBO1xjjb_C4hpwFRQ.png" /><figcaption>Snippet from hr_SensorSweep.py script</figcaption></figure><p>6. Start the Activity on the watch and observe the simulated heart rate is showing properly.</p><h3>Conclusion</h3><p>Despite some pretty interesting choices from Garmin’s side (IronPython and Windows-only tools) we managed to mock / simulate different ANT+ devices quickly and without problems in both ways. Prospect of using ANT+ to expand the connectivity of our applications seemed like a good idea, but the lack of support in that domain was somewhat surprising.</p><p>As it currently stands, Garmin is no longer isolated as a top player in the segment and with the rise in popularity of BLE (pushed mostly by the mobile devices vendors) it seems that the future for ANT+ and direct communication with mobile phones is sealed. Available libraries for mobile development are almost non-existent, and the list of Android mobile phones with ANT-compatible chipsets is looking more and more obsolete. Most of the devices on that list are from Samsung, but even there we don’t see ANT+ hardware support in the devices coming to the market in the past 2 years. Apple never had any intention to natively support it. So if you are a developer or tester in the Android / iOS world, the chances are you will never see this protocol in your life. But if you are working on embedded systems in the fitness-related industry, you most likely will, so we hope you found some useful information here, to get you started.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=74bf1dc83d50" width="1" height="1" alt=""><hr><p><a href="https://medium.com/greypbikes/ant-in-mobile-software-qa-landscape-74bf1dc83d50">ANT+ in mobile software QA landscape</a> was originally published in <a href="https://medium.com/greypbikes">greypbikes</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>