On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshooting Tango+ not communicating with stress test system, including cable issues, port settings, software configuration, and connection failures.
Step-by-Step Troubleshooting
Ensure Patient Safety First
- If the device is in use during a stress test, stop the test and transition to manual BP monitoring or a backup device.
- Expected: Patient monitoring continues safely
- Why it matters: Loss of communication can prevent BP readings during critical testing
Verify the Reported Issue
- Confirm the Tango+ is not communicating with the PC or stress system.
- Check:
- No BP readings appearing on the PC
- Communication error messages in stress software
- Tango+ appears functional but not transmitting data
- Expected: Issue is clearly reproducible
- Why it matters: Confirms a true communication failure vs user workflow issue
Check Physical Communication Cable (Most Common Cause)
- Inspect the communication cable between the Tango+ and PC/system.
- Ensure cable is securely connected on both ends
- Look for bent pins, fraying, or loose connectors
- Reseat both ends firmly
- If available, swap with a known-good cable
- Expected: Stable connection established
- Why it matters: Loose or damaged cables are the most frequent cause of communication failure
Verify Correct Port Connection
- Confirm the cable is connected to the correct port on both the Tango+ and PC.
- Check for labeled COM/USB ports
- Ensure no adapters (USB-to-serial) are loose or failing
- Expected: Correct port alignment
- Why it matters: Incorrect port selection prevents communication even if hardware is functional
Check PC Software and COM Port Settings
- On the stress test system PC:
- Verify correct COM port is selected in the software
- Confirm Tango+ is assigned to the same port in device settings
- Check Device Manager for port recognition
- Expected: Tango+ appears as an active communication device
- Why it matters: Mismatched COM settings will block communication
Restart Both Devices
- Power cycle both the Tango+ and the connected PC/system.
- Turn off Tango+
- Restart PC/software
- Power Tango+ back on and reconnect
- Expected: Communication re-establishes
- Why it matters: Clears temporary software or handshake issues
Check for USB-to-Serial Adapter Issues (If Used)
- If using an adapter:
- Verify drivers are installed and functioning
- Try a different adapter if available
- Confirm adapter is recognized in Device Manager
- Expected: Adapter properly recognized and assigned a COM port
- Why it matters: Adapters are a frequent failure point in legacy communication setups
Verify Tango+ Communication Settings
- Check Tango+ internal settings (if accessible):
- Ensure communication mode is enabled
- Confirm correct protocol/output settings
- Expected: Device configured for external communication
- Why it matters: Incorrect settings prevent data transmission
Test with Alternate PC or Port
- If available:
- Connect Tango+ to a different PC or port
- Attempt communication using known working setup
- Expected: Helps isolate whether issue is device vs PC/system
- Why it matters: Differentiates between monitor failure and system-side issue
If the Problem Persists
All common external causes have been ruled out. The issue is likely internal (communication board, port failure, or internal interface fault).
Remove the device from service, label it Out of Service, and send for repair or bench evaluation.
Knowing when to stop prevents unnecessary risk and wasted troubleshooting time.
Clinical Use Tip
Do not troubleshoot communication issues during an active stress test. Always move the patient to a functioning system before troubleshooting.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Tango+ not communicating with stress test system; no BP readings displayed on PC."
Cause
What was observed during troubleshooting.
Example:
"Failed USB-to-serial adapter preventing communication between monitor and PC."
Resolution
What action was taken.
Example:
"Replaced adapter and verified proper COM port communication with stress system."
Helpful Details to Include (If Known)
- Cable condition and swap performed
- COM port settings verified
- Adapter used (if applicable)
- Software behavior/errors
- Device Manager recognition status
- Final communication status
Final Thought
Communication failures are often external and easily corrected with systematic checks. Focus on cables, ports, and settings first. Escalate only after confirming these. Proper documentation ensures faster resolution if the issue recurs.
That is successful troubleshooting.