Synchronized A2B and CAN FD Bus Logging

Automotive Audio Bus (A2B) is a digital audio bus from Analog Devices used in vehicle infotainment, microphones and speaker systems. When an audio fault appears, the cause is frequently a CAN event at the same instant: a mode change, a diagnostic request, an amplifier enable or a power transition. Two separate log files make that correlation hard to prove.

The Lab CAN Pro records A2B events and CAN traffic into a single log with one timestamp, by connecting over Qwiic to the Flextech AKT A2B Bus Monitor. This page explains how the setup works, how to enable it, how the events appear in the log, and what the trigger modes do.

Why one shared timeline matters

  • Ordering. A dropout, pop or silence on the audio bus often follows a CAN event by milliseconds. With one clock you can see which happened first instead of inferring it.
  • Evidence. A single file showing the CAN request and the A2B response is far easier to hand to a supplier or a colleague than two logs and an explanation.
  • Fewer tools. One capture chain replaces two, with nothing to align afterwards.
  • Intermittents. Faults that appear once in an hour of driving are the hardest to catch. Buffered triggering keeps only the window around the event.

What you need

  • Lab CAN Pro. The Qwiic interface is specific to this model; Desk CAN Pro does not have it.
  • A Flextech AKT Pocket A2B Bus Monitor, with the “AKT Automation powered by Lua” option. That option is bought from Flextech AKT with the Bus Monitor and is required — without it the Bus Monitor reports that Lua is not available and the interface will not run. Both the A2B 1.0 and A2B 2.0 versions of the Bus Monitor are supported.
  • The SeRoSys Qwiic cable to link the two, or a standard Qwiic cable with the red wire cut (see below).
  • SLSS CANAnalyser, included with the hardware.
  • The SeRoSys Lua script, Serosys-Bus_Monitor--GPIO_triggered_buffer.lua, free from the downloads page under Scripts and Automation. It is copied to the microSD card in the Bus Monitor — not the card in the dongle.
  • A microSD card in the Lab CAN Pro if you want to log without a PC attached.

The red wire on a third-party Qwiic cable must be cut

The Qwiic connector follows the SparkFun Qwiic standard, so the pinout is the common one rather than anything proprietary. A standard Qwiic cable bought anywhere, though, carries four wires including 3.3 V power on the red one. Here both devices are independently powered, so that wire can backfeed between the two modules and cause erratic behaviour on either the dongle or the Bus Monitor. If you supply your own cable, cut the red wire. The SeRoSys Qwiic cable is supplied ready for this pairing.

Two ways to log A2B and CAN together

Software-connected loggingStandalone logging
What it isDongle and Bus Monitor both connected to a PC running SLSS CANAnalyser. A2B and CAN data are captured live and merged chronologically in the Incoming Data and Logfile Recorder tabs.No PC. The two devices log on their own from USB power, and the dongle is reconnected to the software afterwards for analysis.
Lua scriptLoaded once per session with Run selected script, or set to autostart.Must be set to autostart, since there is no PC to start it.
Recording typesContinuous capture in the software.Constant logging (everything), or triggered pre-buffered logging — only the window before each trigger, plus a matching audio WAV file.

Setting up the Qwiic link

In SLSS CANAnalyser, open Hardware Configuration with the gear icon and select the Qwiic (I²C) Interface tab.

  1. Tick Enable connection to A2B Bus Monitor. This is required for the dongle to reach the Bus Monitor at all.
  2. Choose the COM port described as FlexTech AKT Comm Port and press Connect. The box lists the .lua files found on the Bus Monitor’s microSD card.
  3. Select Serosys-Bus_Monitor--GPIO_triggered_buffer.lua.
  4. Press Run selected script for a one-off session, or Set as autostart to have the Bus Monitor run it every time it powers up. Autostart writes a shell.cmd file to the card and is required for standalone logging.
  5. Check that the Output of the A2B Bus Monitor box fills with the SeRoSys interface banner. If it stays empty, or says Lua is not available, the cable or the Lua option is the problem.
  6. Open the SD card window and, under Advanced logging features, tick Enable A2B logging over qwiic. A2B events are not recorded until this is set.

Set the ID display format to Hexadecimal in the main toolbar. A2B events are reported under IDs of the form 0xA2Bxxx, which are much harder to read in decimal or binary.

Power the SeRoSys dongle first, then the Bus Monitor. When the Lua script starts it sends an I²C message over the Qwiic cable to check the link, and if the dongle is not up yet that check fails. Keep USB cables short: the Bus Monitor needs a stable 5 V and at least 150 mA, and a long cable can drop it below that.

How A2B events appear in the log

A2B rows sit in the same message list as CAN traffic and are identified by a data type marker, alongside the markers used for the other bus types:

  • [STD] and [EXT] for CAN 2.0 and CAN 2.0 extended IDs
  • [FD] and [FD] [BRS] for CAN FD, with and without bit rate switching
  • [LIN], [SR], [CCS] and [ECS] for LIN frames and checksums
  • [A2B] for A2B events
  • [GPIO] for GPIO pin status changes

Because they share the list, the ordinary tools apply: the same microsecond timestamps, the same interval column showing the delta between messages, and the same filtering. You can filter down to the A2B rows and the handful of CAN IDs you care about and read the sequence directly.

For register access events the raw data bytes carry the node address, the I²C address, the I²C data byte and a read/write indicator. The Designation column decodes that into readable form — for example A2B Register Access (I2C_REG), Node 0, Address CLK2CFG (0x5A), Access mode WRITE, Data 0x81 — so you are not decoding bytes by hand.

A2B Event ID reference

Every A2B event is logged under a unique ID of the form 0xA2Bxxx, where xxx is the A2B Event ID. This is the full list as of SLSS CANAnalyser 1.2.8.

IDEvent
0xA2B001Bias OK
0xA2B002Bias OK removed
0xA2B003A2B Discovery
0xA2B004A2B NEWSTRCT
0xA2B005A2B RegisterAccess (I2C_REG)
0xA2B006A2B Peripheral I2C Transaction (I2C_PERIPHERAL)
0xA2B007A2B Downstream Frame Error (SCF)
0xA2B008A2B Upstream Frame Error (SRF)
0xA2B009A2B Slave Error
0xA2B010A2B Interrupt (IRQ)
0xA2B011A2B Sequence Error
0xA2B012A2B SPI Transaction
0xA2B013Bias reverse detected
0xA2B014Bias reverse removed
0xA2B015Bus locked
0xA2B016Bus unlocked
0xA2B032Bus Monitor GPIO trigger message. The Designation column holds the filename counter of the linked WAV file.
0xA2B4095Buffer overflow error

Triggered pre-buffered logging, with matching audio

Constant logging records everything, which on a long session produces a file that is tedious to search. Triggered pre-buffered logging keeps only what matters: each time an external trigger fires, the last few seconds or minutes of CAN and A2B traffic are written to the dongle’s SD card, and an audio WAV file covering the same window is written to the Bus Monitor’s SD card. Everything else is discarded. This is the mode for the complaint that begins “it made a noise” — you get the bus traffic and the sound for the same moment.

In the SD card window, set Log file recording mode to Always log, use A2B Bus Monitor GPIO to trigger a buffer file, choose the GPIO and the Pre-trigger duration, then save the configuration to the dongle.

The trigger goes on the Bus Monitor, not the dongle

For this mode the button — or any other qualifying electrical input that pulls the pin to ground — connects to GPIO0 or GPIO1 and GROUND on the Flextech Bus Monitor. A button wired to the SeRoSys dongle will not trigger it. The Bus Monitor’s I/O LED turns red for one second on each trigger received, which is the quick way to confirm the wiring before a test.

GPIO0 and GPIO1 must match in two places

The GPIO number is set both in the software and in the Lua script, and the two must agree. The default is GPIO0, which needs no edit. To use GPIO1, open the Lua script in a text editor and change the number on this line only:

local used_trigger_gpio = 0  -- the Bus Monitor GPIO pin for the standalone trigger activation

Set it to 1 for GPIO1, save the file back to the Bus Monitor’s microSD card, and select the same GPIO in the software. A button on the other GPIO records nothing.

Each press creates a separate recording and the trigger re-arms immediately, so one session can capture several events. Unfinalized recordings accumulate across sessions and even across days, so a test can be run over several sittings and processed in one go.

Finalizing a standalone session

While logging, the dongle writes to a temporary _tlb sub-directory on its SD card, and that data is not yet a readable log. Reconnect the dongle to SLSS CANAnalyser and open the SD card window: if any triggers were set, the software offers to finalize the pending recordings, converting them into SLSS_Triggered_Log_xxxx.txt files that open like any other log, with A2B and CAN messages merged chronologically.

The last entry of every triggered log is event 0xA2B032, and its Designation column holds the filename counter of the matching WAV file in the SLSS_wav_files directory on the Bus Monitor’s SD card. A counter of 10 means the WAV file whose name ends in 10 is the recording for that log.

Finalize before you clear anything. The dongle and the Bus Monitor keep independent file counters, and the link between a log and its audio lives in the finalized log. If the WAV files are cleared from the Bus Monitor before the CAN logs are finalized, its counter restarts at 1 and several logs end up pointing at the same WAV number. Deleting individual files at any other time is harmless, because the number is fixed in the log at the moment of recording.

Declining the finalization prompt loses nothing. The software asks again each time you open the SD card window, and new recordings are added to the pending ones. Finalization can take several minutes for long or numerous recordings, which is why it is offered rather than done automatically.

Logging with no PC attached

The Lab CAN Pro writes to its own micro-SD card, so an A2B and CAN session can run in a vehicle with no laptop connected. This is covered in more depth in the guide to standalone CAN logging and live bus playback, and the general approach to recording is in the CAN bus logger guide.

Two practical notes for unattended sessions. Offline logs use a proprietary .TXT format written by the dongle; a text file copied onto the card by hand appears in the file list but cannot be opened or played back. And do not power the Lab CAN Pro from USB and from pin 9 B+ at the same time.

Status LEDs and troubleshooting

A solid green Status LED on the Bus Monitor means the startup check passed and the link is good. You can simulate the failure case, and so confirm the setup before a test, by unplugging the Qwiic cable and watching for the red blink.

SymptomLikely causeWhat to do
Status LED blinks red for about 5 seconds, then the Bus Monitor restartsThe Lua script’s startup check could not reach the SeRoSys hardware over the Qwiic (I²C) cable.Check the cable is fully seated at both ends and that the red wire has been cut. If the script was started with Run selected script the Bus Monitor will not retry, so reconnect and run it again; if it was set to autostart, the cycle repeats until the cable problem is fixed and then clears itself.
Erratic behaviour from either device once the Qwiic cable is connectedThe red wire of a third-party Qwiic cable was not cut, so 3.3 V is backfeeding between the two modules.Cut the red wire, or use the SeRoSys Qwiic cable.
A high-pitched sound from the Bus MonitorInadequate USB power.Use a shorter USB cable and a supply that holds a stable 5 V at 150 mA or more.
Status LED solid green, but no WAV file is createdNo trigger reached the Bus Monitor, or the session was set to constant logging, which does not store WAV files.Press the button and confirm the I/O LED flashes red for one second. Check the button is on the GPIO selected in both the software and the Lua script.
No finalization prompt when the SD card window opensNo trigger was set during the session, so the temporary data was discarded; or the logs were already finalized.Confirm the I/O LED flashed on each press while logging.
No SLSS_Triggered_Log files on the SD card after loggingThe card was removed before finalization, so the data is still in the _tlb sub-directory.Put the card back in the dongle, connect to the software, open the SD card window and finalize.
Several logs reference the same WAV file numberWAV files were cleared from the Bus Monitor before the CAN logs were finalized, restarting its counter.In future sessions, finalize the CAN logs first, then clear the cards.

Typical use cases

  • Chasing audio dropouts that coincide with a CAN mode change or a diagnostic session.
  • Validating amplifier or microphone node behaviour against the CAN commands that drive it.
  • Capturing intermittent faults on a long drive with a button-triggered buffer, so the technician presses once when it happens.
  • Confirming startup and shutdown ordering between the audio chain and vehicle power events.
  • Catching A2B line faults — downstream and upstream frame errors, bias reversal, bus lock and unlock — against what the vehicle network was doing at that instant.
  • Handing a supplier one file that shows the request and the response rather than two that have to be aligned.

How this fits with other A2B tools

Analog Devices publishes its own A2B bus analyzer tooling, which goes deeper on the audio bus itself: node discovery, register level inspection and A2B-specific diagnostics. If your question is purely about the A2B network, that is the right instrument.

The SeRoSys setup answers a different question. It is for engineers whose problem sits at the boundary between the audio bus and the vehicle network, where the value is having both on one timeline rather than exhaustive detail on either. The two are complementary, and plenty of benches will have both.

Frequently asked questions

Does this work with Desk CAN Pro?

No. A2B logging needs the Qwiic interface, which is on the Lab CAN Pro only. The technical specifications page compares the two models.

Do I need the SeRoSys Qwiic cable specifically?

Not necessarily, but any standard Qwiic cable must have its red wire cut before use in this setup, or 3.3 V can backfeed between the two powered modules and cause erratic behaviour. The SeRoSys Qwiic cable is supplied ready to use and is the one we test with.

Is anything extra needed on the Flextech side?

Yes. The “AKT Automation powered by Lua” option has to be bought with the Bus Monitor. Without it the Bus Monitor reports that Lua is not available and the interface will not run. Contact Flextech AKT to unlock it on an existing unit.

Does it work with A2B 2.0?

Yes. The interface works with Flextech Bus Monitor versions supporting either A2B 1.0 or A2B 2.0.

Are the A2B and CAN timestamps genuinely from one clock?

Yes. A2B events enter the same message list as CAN frames and carry the same timestamps, which is the point of the setup. There is no post-processing step to align two files.

Can I record audio as well as bus data?

Yes, when the buffered log is triggered from a GPIO input on the Flextech Bus Monitor. A WAV file covering the same window is stored on the Bus Monitor, and the finalized CAN log names the matching file.

Can I connect the trigger button to the SeRoSys dongle?

Not for this mode. The trigger input for A2B pre-buffered logging is GPIO0 or GPIO1 on the Flextech Bus Monitor, because the Bus Monitor is what records the matching WAV file.

What happens if the button is never pressed during a session?

Nothing is kept. The dongle writes to the temporary _tlb directory, and that data is deleted the next time the dongle is connected to the software. No triggered log and no WAV file are created.

Where is the detailed interface documentation?

The SLSS CANAnalyser Pro Software A2B Qwiic interface addendum covers the interface in full, with a screenshot of every step, and is on the downloads page along with the main user manual and the Lua script.

Where can I get help?

Through customer support. If you are evaluating the setup for a specific vehicle programme, tell us what you are trying to capture and we will tell you honestly whether this is the right tool.

Shopping Cart
Scroll to Top