Wi-Fi Communication Improvements in RaceStudio 3 and AiM Device Firmware
AiM Technical Knowledge Base — July 2026
What this article covers
Over the past weeks we have carried out an in-depth review of the Wi-Fi communication between RaceStudio 3 and AiM devices — data loggers, dash displays and SmartyCam cameras. The starting point was a set of symptoms that some of our customers had reported, and that we were able to reproduce and study in detail: switching from one device to another could occasionally take much longer than expected, data transfers could be interrupted before completion, and in some cases a device would appear “busy” or stop responding until it was switched off and back on.
The outcome of this work is a series of improvements on both sides of the link: in RaceStudio 3 and in the device firmware. This article explains, in plain terms, what was happening and what has been improved, so that you know what to expect after updating.
The short version: update RaceStudio 3 and, when available for your devices, the firmware. Each update improves the connection on its own, and they work best together.
A little background
When you connect your PC to an AiM device over Wi-Fi, the device acts as a small Wi-Fi access point: your PC joins the device’s own network, exactly as it would join an office or home network. From that moment on, several actors cooperate: RaceStudio 3, the Windows networking components, the Wi-Fi adapter of your PC, and the firmware inside the device. A weakness in any one of them can show up as a slow connection or an interrupted download — which is why this review covered the whole chain rather than a single component.
What we improved in RaceStudio 3
Background network scanning no longer disturbs the connection
While your PC is connected to a device, Windows periodically scans the airwaves in the background, looking for other Wi-Fi networks. During these scans the Wi-Fi radio briefly tunes away from the device’s channel. That short absence was enough, in some circumstances, to interrupt a data transfer in progress — and, in unlucky cases, to leave the device holding a half-open communication session, so that it appeared “busy” or unresponsive afterwards.
RaceStudio 3 now temporarily suspends this background scanning on the Wi-Fi adapter it is using to talk to a device, and restores it automatically as soon as the session ends (or if RaceStudio 3 is closed). RaceStudio 3 has also stopped performing periodic scans of its own: the network list is refreshed on demand instead. The practical effect is a much more stable link during firmware updates, data downloads and configuration transfers.
If a device ever does remain in that “busy” state — something the improvements make far less likely — switching it off and on again restores it completely.
More robust connection handling
We reviewed the way RaceStudio 3 establishes and supervises connections and corrected several weaknesses: situations where two operations could compete for the Wi-Fi adapter at the same time and, in rare cases, freeze the application; retry policies that, by insisting too quickly, could occupy the single communication slot a device offers and make things worse rather than better; and recovery paths that did not always leave the connection in a clean state. Connection attempts are now properly serialized, retries are more considerate towards the device, and failures are detected and reported promptly instead of lingering.
More robust data transfers
The low-level reading and writing routines have been reviewed as well. Some rare error conditions were previously not handled correctly: a transfer could appear to start successfully when it had not, or a failure could be reported at the wrong moment, masking its real cause. These paths now handle all outcomes explicitly. In addition, on PCs with more than one network card (for example a laptop connected to a wired network while talking to a device over Wi-Fi), RaceStudio 3 now strictly binds its device traffic to the Wi-Fi adapter actually connected to the device, so that no packet can ever take the wrong route through another network.
What is being improved in the device firmware
Devices no longer announce a DNS server
When a PC joins a device’s Wi-Fi network, the device assigns it a network address. Together with that address, the firmware also announced a “DNS server” — a service that AiM devices do not actually provide and that the communication with RaceStudio 3 never needed. On most PCs this announcement was simply ignored. But on computers that belong to a corporate network (a Windows domain), or that have several network adapters active at the same time, Windows takes the announcement seriously and performs some internal DNS housekeeping when leaving the device’s network. Since the announced server does not exist, that housekeeping could stall for tens of seconds — and this delay added itself on top of the effects described above, making the switch from one device to another feel very slow on exactly those PCs.
Upcoming firmware versions simply no longer make this announcement, removing the cause at its root. This benefits every version of RaceStudio 3, and also any other software or mobile device that connects to an AiM instrument.
One thing to be aware of: Windows remembers the network settings of each Wi-Fi network it has joined. After updating a device’s firmware, the very first connection to it may therefore still use the previously remembered settings; from the second connection onwards the improvement takes full effect. No action is required on your part — it settles by itself.
Communication session handling
The firmware review also addressed some corner cases in the way devices manage their communication sessions — for example when a session is cut short by an external event and the PC later tries to reconnect. Upcoming firmware versions handle these situations more gracefully, reducing the chance of a device remaining busy after an interrupted operation.
Compatibility: updates help in any combination
These improvements are fully modular and provide cumulative benefits in any combination:
Scenario |
Stable connections and transfers |
Fast device switching |
|---|---|---|
RaceStudio 3 updated only |
Yes — background scanning suspended during sessions, more robust connection handling and data transfers, with all devices (including those that will never receive a firmware update) |
Partially — some causes of slow switching are removed, but the DNS-related delay described above remains on the affected PCs until the device firmware is updated |
Device firmware updated only |
Yes — more graceful handling of interrupted sessions, with all versions of RaceStudio 3 and any other client |
Yes — the DNS announcement is gone, so the switching delay disappears for every client (full effect from the second connection onwards) |
Both updated (recommended) |
Best — each fix addresses a different link of the same chain |
Best — switching between devices typically completes in a few seconds |
A note for teams with company-managed PCs
The DNS-related delay described above only affects computers that are part of a corporate Windows domain or that keep a second network adapter connected. If your team uses PCs managed by an IT department and you experience slow device switching before the firmware updates reach your devices, your IT staff can also mitigate the issue at the operating-system level; they can contact AiM technical support for the relevant configuration notes.
Summary
Some Wi-Fi issues — slow switching between devices, interrupted transfers, devices appearing busy — have been traced to their root causes across RaceStudio 3, Windows networking behaviour and the device firmware.
RaceStudio 3 has been improved: background scanning is suspended during communication, connection handling is more robust, and data transfers are safer, with device traffic strictly bound to the correct network adapter.
Upcoming device firmware no longer announces a DNS server and handles interrupted sessions more gracefully.
All improvements are effective on their own and complementary when combined. After a firmware update, allow the second connection for the full benefit.
As always, we recommend keeping both RaceStudio 3 and your device firmware up to date. If you have any questions or continue to experience connection issues after updating, please contact AiM technical support.