.trc → .sor
Convert .trc to .sor
Open the .trc in the browser and press Convert to .sor. A second row appears beside the first one: plain Bellcore, which opens in the instrument's own software and at your customer's desk.
Here files are converted one at a time. A whole project at once, with a .sor for every file, comes as the project archive on Professional.
Three formats under one extension
They have nothing in common, and what tells them apart is the signature inside the file rather than the extension. Each is converted its own way.
EXFO
"AppReg Format Ex" from the FTB platforms. It is not Bellcore, and the layout was measured on real files.
Anritsu T5
The format of the CMA4000 instruments from NetTest and Anritsu. Distances were checked against the vendor's own output.
Anritsu T6
The next revision of the same format, the CMA5000 instruments. Its signature differs from T5 by a single character, and the inside is built differently.
What travels into the new file, and what does not
Everything Bellcore has room for travels: the curve, the acquisition parameters, the event table, the header. What the source stated and the format cannot hold, a vendor threshold or a word for an event class that has no Bellcore code, goes into the journal inside the same file rather than being lost. The instrument's proprietary block does not travel: the file is assembled by us, and putting a vendor block into it would forge somebody else's signature.
Where the file came from is written in it
The conversion records in the journal which format the file was built from, when, by what, and what the source did not have at all. The original .trc stays untouched, and the second row in the list is a copy. There is no reverse, and .sor to .sor is refused on purpose: an instrument's file already has a provenance, and a "built from" stamp would replace a real history with an invented one.
Nearby
Converting is free and needs no account.