EcoTune Automation
BAS Network ProbeDesktop Capture · MS/TP analyzer & device explorer
Beta Listen-only
0frames/s
Not connected
Before you connect: close BQT, YABE or any other program that is using the adapter (only one program can open a COM port at a time). Pick your adapter in the Chrome/Edge pop-up; it is usually listed as "Silicon Labs CP210x" or "USB Serial".

Overview

Live health of the trunk at a glance

Last 2 min

See what is really happening on an MS/TP trunk

Plug a USB-to-RS-485 adapter into any MS/TP trunk and this page decodes the traffic live: CRC errors, who is on the token ring, routers and network numbers, and plain-English findings. Listening never disturbs the network. The Devices tab can also join the token ring so you can open a device, see every point inside it, and write to it, the way BQT and YABE do.

Free demo and analyzer views work without a license. Connecting to a real adapter needs a license — enter or get one.
1
Wire it inConnect the adapter's A/B (or +/−) terminals to the trunk's A/B. Listening is harmless, but reversed polarity shows no frames.
2
Close other toolsQuit BQT / YABE so the COM port is free.
3
Pick the baud rateUse what the trunk runs at, or try Auto-detect.
4
ConnectClick Connect adapter and choose the port. Traffic appears within a second or two.

Frames per second

Last two minutes. Blue = valid frames, red = frames with a CRC error.
ValidCRC errors

Capture health

A quick read from the counts below. Heuristic, not a standard.

Frame mix

Counted since connect.

Live bus monitor

Newest frames first. The Traffic tab has the full log, filters and export.

What the capture is telling you

Hints built from counts and addresses. They point you at where to look and are not proof of a cause.

Station activity

Frames sent by each station in each of the last 60 seconds. Brighter cell = more frames that second.

Top talkers

Share of all frames sent, by MAC.

Ring snapshot

Token passes in the last 15 seconds.

Application layer

BACnet messages decoded from data frames.

Devices

Find devices, read every point and write values

BACnet client

Device explorer

Listening only
Joining makes this page a normal MS/TP master: it answers the ring's poll, takes the token, sends its requests, and passes the token on. Pick a MAC that no other device uses. Until you press Join ring, nothing is transmitted.

Devices

0

Write log

Every write this page sent in this session.
TimeDeviceObjectPropertyValuePriorityResult

BACnet/IP

Discover, read and write devices over BACnet/IP — including routed networks and BBMD

Not connected

Network Helper

Modbus

Read and write registers over Modbus RTU, through a USB-to-RS-485 adapter

Not connected

Connection

Ring map

Which masters hold the token and where it goes next

Last 15 s

Token ring

Masters sit around the circle in address order. Solid arrows show where the token was passed in the last 15 seconds. Faint dotted arrows are older passes. Amber dashed arrows skip a master that was seen earlier.
Heard recentlyQuiet 10 s+Missing 30 s+Offered the token, never heard from

Ring status

Responders (not on the ring)

Devices that only answer when asked. Slaves, or masters that have not joined.

Stations

Every station heard on the trunk

Since connect

Stations heard on this trunk

Everything that has transmitted, plus masters that were offered the token. Device instance and vendor appear when the device sends an I-Am (for example after a Who-Is from a front end).
MACRoleStatusFramesToken sentToken rec'dPFMDataData CRC errDeviceVendorLast heard

Traffic

Frame-by-frame log with filters and CSV export

Since connect
0 framesi
Time (s)TypeFromToLenDetailsData (hex)
Header-CRC errors show the address bytes that arrived, but they are corrupt and cannot be trusted, so they are never counted against a device. Times are when your computer received the bytes, not on-wire timing.

Routing

Routers, networks and devices behind them

Since connect

Networks reachable through routers

Learned from I-Am-Router-To-Network announcements and from traffic that arrives with a source network number.
NetworkVia MACHow learnedSeen

Network-layer messages

Router chatter counted since connect.

Devices behind routers

Seen in routed I-Am messages. Their MAC is the address on their own network.
NetworkMAC on that networkVia MACDevice instanceVendor

Findings

Plain-English hints from the capture

Since connect

Findings

Every item is a hint from traffic patterns. Keep the capture running for a few minutes; intermittent faults often need time to show up.