TBOS Tester configuration files

Configuration (.cfg) files are used by TBOS Tester to let you know the meaning of each TBOS alarm/status and command point for your particular equipment. Each point can be described with up to 16 characters of text. These descriptions appear on TBOS Tester's individual display point grids. Figure 1 shows for example the point descriptions for an NEC RC28D multiplexer.

Figure One: TBOS Tester alarm display screen with point descriptions.
Active alarms are in reverse video. The descriptions are contained in
"configuration files", which you can load prior to running a test.

The point descriptions from the configuration file also appear in the event log (Figure 2) provided the "descriptive logs" option is enabled.

Figure Two: TBOS Tester event log window with point descriptions.

Because different types and models of monitored equipment use the same TBOS point to mean or to do different things, .cfg files differ from one type of equipment to the next. For example, Alarm Display 1 Point 1 for an NEC RC28D multiplexer indicates a high speed interface fault ("Online HTx Fail"), whereas the same point for an AT&T DDM-1000 announces a power supply problem ("Pwr Unit NE").

Do I need a .cfg file for my equipment to run a test?

No! You do not have to have a .cfg file for your specific type and model of equipment in order to test it using TBOS Tester. As explained in the Overview of TBOS Telemetry, TBOS protocol exchanges between the alarm remote and the monitored equipment do not contain equipment-specific point definitions, but deal simply in which displays and which points are active or not. It is up to the central monitoring system computer to match up alarm points with their meanings in order to generate a useful alarm message. This matching function is precisely what TBOS Tester uses .cfg files to do.

To avoid confusion when you do not have a .cfg file for your equipment, use the default .cfg file ("tbos.cfg") which does not contain any point descriptions. As with all config files, the alarm grid on screen will display point numbers (1 through 64) instead of blank cells if you press the Spacebar (Figure 3). Then test as you would normally. If any points are in alarm they will appear in reverse video. If you need to know what the alarmed points mean, just consult the documentation for the equipment under test. You can always make a .cfg file for your equipment or ask TSA to do it, as discussed later.

Figure Three: TBOS Tester alarm display window with point numbers. Simply press
the Spacebar to switch between point numbers and descriptions.

How do I load the .cfg file for my equipment?

TBOS Tester ships with a library of configuration files that pertain to many common types and models of monitored equipment. Use the LOAD:FILE function to access them. From the main TBOS Tester menu, choose LOAD and from the submenu choose FILE. A list of configuration files will appear (Figure Four). Use the cursor control keys to highlight the equipment you want to test and press <Enter>. In Display, Respond and Monitor Modes the alarm/status point descriptions are displayed, while in Command mode the command point descriptions appear.

Figure Four: TBOS Tester LOAD:FILE screen

I have different types of equipment on the same port. What do I do?

The config library contains files that are equipment specific. You can create new config files that are specific to your installation or application by "cutting and pasting" individual display pages of point descriptions from one file to another. The LOAD:PAGE function is provided for this purpose; please refer to Chapter 3 of the TBOS Tester User's Manual for step by step guidance using the config file editing features.

My equipment is not listed. What now?

I have more questions...

You can find out more about the TBOS protocol in general by consulting the TBOS Overview. To learn more about testing TBOS installations check the article entitled Testing TBOS Serial E-telemetry Installations and Systems. For more about TBOS Tester software and hardware package that enables you to install, troubleshoot and monitor TBOS systems using a PC or laptop, click here.

If you prefer, you can e-mail TSA with any and all of your questions regarding TBOS Tester (or about TBOS in general), or call us at any time on (919) 553-8267. We look forward to serving you!

TBOS Tester

configuration file library and FAQs

Contents

What are TBOS Tester configuration files?

Do I need a .cfg file for my equipment to run a test?

How do I load the .cfg file for my equipment?

I have different types of equipment on the same port. What do I do?

My equipment is not listed. What now?

I have more questions...