Troubleshooting Counter Routing Between 6052E DAQ Cards

Brian Holt2 min read
Data AcquisitionOther ManufacturerTroubleshooting
Licensed PE Working through this on a live machine? A Maine-licensed engineer can take it from here — included with IMD hardware, by the hour for everything else. Book an engineer

Define the Counter-Routing Problem

The system contains two 6052E DAQ cards. One card must generate a counter signal, while the second card must receive that signal for edge detection. Attempts to configure this arrangement produce a resource is in use error.

The available evidence does not identify the occupied resource. Treat counter allocation, signal routing, and physical interconnection as separate checks until the code and wiring reveal where the conflict occurs.

Collect the Missing Configuration Evidence

Required evidence Engineering decision
Counter configuration code for both cards Determine which resources each operation reserves and whether one resource is requested twice.
Wiring between the cards Confirm how the generated signal is intended to reach the receiving card.
Presence or absence of an RTSI connection Determine whether an inter-card routing path has been provided.

The source does not state the software API, driver version, counter identifiers, terminal names, routing command, or exact wiring. Do not select those details by assumption.

Diagnose the Resource Conflict

  1. Review the code for both cards and identify every counter and routing resource requested by the generation and edge-detection operations. Look for a resource assigned to more than one active operation.
  2. Document the physical wiring and verify whether the two cards have an RTSI connection. If no RTSI connection exists, do not assume that an inter-card route requested by the code is physically available.

The error supports a resource-allocation conflict, but it does not prove whether the cause is duplicate counter use, an occupied route, or an incomplete inter-card connection. The code and wiring are required to distinguish these cases.

Verify the Final Configuration

After correcting the identified allocation or connection issue, run the generator on the first card and confirm that the second card detects the resulting edges without producing the resource is in use error. Verify both outcomes: successful signal generation and successful edge detection.

If the error remains, capture the exact operation that fails and the resources already active at that point. That isolates whether the conflict occurs during counter creation, route configuration, or edge-detection setup.

FAQ

Why do two 6052E DAQ cards report resource is in use?

The evidence indicates that a requested resource is already occupied, but it does not identify which one. Review both cards' code to find duplicate counter or routing allocations.

Do two 6052E DAQ cards need an RTSI connection?

Confirm whether an RTSI connection exists before relying on an inter-card route. The available evidence raises RTSI as a required diagnostic check but does not establish the final routing configuration.

How do I verify counter transfer between 6052E cards?

Run counter generation on the first card, confirm edge detection on the second card, and verify that no resource is in use error occurs. If it fails, record the exact failing operation and all resources active at that time.

Back to blog