The following are the functional limitations of the Analyzer hardware.
|Affects (HW ver)
|Fixed (HW ver)
|No support of power over USB-C
|Power delivery for the Analyzer unit over USB-C port is currently not supported. Power the unit using the supplied 12V adapter
The following are the know issues with the Analyzer software.
|Affects (SW ver)
|Fixed (SW ver)
|No progress shown for Application Update Download on Linux
|Progress % will not be shown after clicking update application. The update will download and install in the background after a short time. Progress can be seen if the A2B Bus Analyzer is launched from a Terminal command prompt.
|License Activation may not succeed if using a VPN
|Under certain rare circumstances the license activation mechanism may fail if the computer is connected to a VPN. In case of problems users should disconnect their VPN.
|If the firmware goes into a bad state, then pressing Reset button on the enclosure only resets the A2B Bus Analyzer board and not the firmware.
|Power-cycle the board to full reset the A2B Bus Analyzer.
|Higher TDM modes such as TDM16/32 are not fully tested
|Audio might be noisy while sinking the audio channels for these TDM modes when A2B Bus Analyzer is acting as an Emulator.
|Simultaneous use of File In and File Out options on Monitor or Emulator can cause audio distortion
|When using A2B Bus Analyzer as a Monitor or as an Emulator (Main/Sub), using both File In (sourcing WAV from PC) and File Out (recording bus audio as WAV) simultaneously in any project feature can cause distortion in sourced and recorded audio due to too much data throughput between the device and the PC.
|Bus Monitor not always available after discovering a mixed topology with AD242x and AD243x on the network
|In a system with a mix of AD242x/3x nodes, if Bus Monitor is used when the Analyzer is acting as a Main node, then Bus Monitor may not always be available after discovering the network
|A2B Bus Analyzer displays AD243x register bit fields in “Advanced register”/“Regs Any Node” tab while emulating AD242x sub-node
|A2B Bus Analyzer uses a AD243x transceiver and simulates a AD242x sub-node. In the advanced register tab, when AD242x sub-node is simulated, the UI eliminates the AD243x specific registers. But for a register which is common to both AD242x and AD243x, additional bit fields of AD243x show-up even for AD242x. Customers have to refer AD242x technical reference manual to get register description.
|When emulating a main node, sub only registers cannot be accessed in the “Advanced register” tab
|The A2B Bus Analyzer UI keeps a single list of registers which can be accessed when emulating a node. This means that when emulating main only registers that are either common to main and sub nodes or main-only registers are displayed. For this reason in the advanced register tab, while you can read/write registers from the sub nodes, you cannot access registers that do not exist in main like the mailbox registers. In order to use those registers, you can use the SDK, which accepts any valid register address.
|A2B Bus Analyzer modifies volume control for SPDI/F digital input
|A2B Bus Analyzer when used as either monitor or emulator, modifies the audio level for SPDI/F digital interface through volume control. Users need to be careful while testing bit exactness of digital audio.
|UASDK C++ emulator register_example returns an error on Linux
|The C++ emulator_register example provided in the UASDK attempts to write a value of 5 to the TESTMODE register. On Linux this causes a USB timeout and the a2ba_sdk_emulator_register_access function returns A2BA_SDK_FAILED. Rather than writing a value of 5, writing a value of 4 should behave as expected.
|USB channel from the UI may contain an unknown offset or be incorrect for streams over 32
| The UI sets up the USB channels (both in and out) as the index of the streams in the levels being displayed. This results in unexpected offsets for customers which are dependent on the channels used.
This also can lead to errors where the stream number is greater than 32 but the FW only supports 32 so the channel number is invalid.
As a workaround customers can use the SDK where they can choose the channel numbers.
|File Out fails on macOS when more than one A2B Bus Analyzer is connected
| If more than one A2B Bus Analyzer is connected on macOS then there is no way to distinguish the USB audio devices from one another, therefore it cannot be guaranteed that the correct device is chosen.
From the SDK, the APIs a2ba_sdk_monitor_audio_file_out_start and a2ba_sdk_emulator_audio_file_out_start APIs will return A2BA_SDK_FEATURE_INACTIVE.
From the UI, enabling File Out shows an error message.
|File Out may not work when using RDP on Windows
| When attempting to use File Out from Remote Desktop on Windows, the USB Audio device is not present in Device Manager and is therefor not available to record audio from. From the SDK, the a2ba_sdk_monitor_audio_file_out_start and a2ba_sdk_emulator_audio_file_out_start APIs will return A2BA_SDK_FEATURE_INACTIVE. From the UI, enabling File Out shows an error message.
In order to get file out to work correctly you must set the Remote Audio Settings in the Local Resources tab in the Remote Desktop Connection options to “Play on remote computer” before connecting to the remote machine. For more detailed steps see Bus Monitoring > Audio > Audio Traffic and Controls > Recording Audio to File in the User Guide.
|File Out does not work when using SSH on macOS
|When attempting to use File Out from SSH no audio is present in the resulting file. This is because Terminal displays a popup requesting access to the device.
|Bus Monitor Standalone Mode captures only up to 8 Monitor slots
|Current release supports only 8 Bus Monitor slots during BMSA audio capture in SD card, priority given to first 8 downstream slots. Which means, if actual stream configuration of Monitor in BMSA has 10 downstream slots and 10 upstream slots, all 20 slots are displayed in the audio traffic. However, audio is captured only for the first 8 downstream slots and first 2 upstream slots.
|User does not have an option to choose which slots to capture in Bus Monitor Standalone Mode
|Slot order to capture is hardcoded with priority given to first 8 downstream slots followed by upstream slots as long as total count is < 8.
|A stream cannot be selected for both left and right in Line and SPDIF
|From the UI, for Line/SPDIF, the user does not have an option to select the channels (right or left) and same stream cannot be selected as both left and right which was supported in previous versions (3.1.0 and before). The first stream selected is always left and the second always right.
|Emulator Audio Sourcing and Levels do not work for more than 16 streams
|When A2B Bus Analyzer is used as an Emulator and more than 16 streams are configured for Sourcing via USB or LoopBack, the audio levels are not shown and no audio is sourced from the emulator.
|A2B Bus Analyzer, Codec/SPDIF Source/Sink Audio might not be bit exact and may have momentary spectral artifacts
|Due to various clock sources and sinks, A2B Bus Analyzer does clock skewing adjustment which may momentarily cause spectral artifacts. The audio data might also not be bit exact.
|A2B Bus Analyzer, USB Source/Sink Audio might not be bit exact and may have momentary spectral artifacts.
|As USB Audio runs asynchronous to the processor clock .A2B Bus Analyzer does clock skewing adjustment which may momentarily cause spectral artifacts. The audio data might also not be bit exact.
|Monitor: NACK, SRF and SCF events may not be displayed
|While the SDK was able to detect SRF and SCF events correctly, the UI did not display then correctly in the monitor event trace. NACK was not detected correctly by the SDK or the UI.
|A2B Bus Analyzer File Out record does not work in non-English language devices
|Version 3.2.0 of the A2B Bus Analyzer replaced the way file out is done in order to be able to support more than two channels. This version required the Audio Devices in Device Manager to be called “Microphone (A2B Bus Analyzer)” and/or “Speakers (A2B Bus Analyzer)”. In windows devices in other languages file out does not work since the device is not found.
|Emulator: Peripheral programming delay does not operate correctly
|Peripheral programming which was included in version 3.2.0 has an issue with the delay commands. Instead of delaying the number of ms specified in the data, it delays the number of bytes that the data contains. For example a delay of 0xff would only delay 1ms.
|File Out on Windows truncates data to 16 bits
|The output of File Out is only 16 bits by default on Windows because the default audio driver used is MME which truncates audio to 16 bits. You may override the default driver used by setting the A2BA_HOST_API environment variable either system wide or in the command prompt with which you launch the A2B Bus Analyzer. See “How can I specify which Windows audio driver is used to save audio to a file? How can I capture all 32 bits?” in the FAQs for a description of possible values.
|UI is not responsive when switched between monitor and emulator tabs - when dataEnabled is 0
|The UI was hanging when a network with streams which does not have data enabled is passed to the UI.
|SPI based discovery fails for Hardware revisions 2.3.0 and above
|Using SPI based discovery for Main Node Emulation fails for Hardware revisions 2.3.0 and above
|Monitor error statistics not consistent
|Monitor error events reported in event log and statistics are not consistent. Some events are missed in statistics but reported in error log.
|Internal sine tone generated for Hardware revisions 2.3.0 and above shows incorrect dB levels
|Internal sine tone generated for Hardware revisions 2.3.0 and above shows incorrect dB levels. This may manifest as inconsistency between levels shown in monitor and emulator for the same stream.
|High gain (> 70%) for Line OUT saturates the audio
|Line OUT gain set to more than 70% saturates the audio in both monitor and emulator modes