-
Notifications
You must be signed in to change notification settings - Fork 23
Main Excel
Go to Wiki Home.
Go to Explanation data files.
The main Excel file is the one placed in the data root folder, named Classic-Repair-Toolbox.xlsx or Classic-Repair-Toolbox.v2.0.0.xlsx. This file depicts the different hardware in CRT, and it has the configuration for all supported oscilloscopes.
The Excel file, alongside the board Excel files, is versionized meaning the version number represents the file will work from FROM this version and onwards.
The Excel file has only two worksheets, so it is pretty simple compared to the board files.
These are the columns and how to understand them:
Exact same name as shown in the Hardware drop-down list in CRT.
The exact same hardware name can be represented on multiple rows, if it has different boards.
Keep the name short, so it can fit in the drop-down.
Exact same name as shown in the Board drop-down list in CRT.
The same board name should not be represented more than once per hardware.
Keep the name short, so it can fit in the drop-down.
This is typically the model number or for a Commodore system it is the "assy" (yeah, weird naming).
Path and filename to the specific hardware/board Excel data file.
Use relative path from the Data folder.
A small note describing characteristics of the hardware - maybe special recognition points.
Currently this data is not displayed anywhere, but it should be one day.
These are the columns and how to understand them:
The brand name of the oscilloscope vendor.
Ideally an entire series/family can be covered, but this could also be individual oscilloscope models.
Default port suggested for network connectivity. Can be changed in the "Oscilloscope" tab.
The debounce time is a pacing value that tells CRT how long to wait before it talks to your oscilloscope between commands. Note that this is by far not all commands, but only some (e.g. image handling). It is also used for keyboard debouncing.
SCPI command for identifying the scope.
For my Rigol scope it will show this:
Vendor: RIGOL TECHNOLOGIES
Model: DS2202A
Serial: *************
Firmware: 00.03.06
SCPI command for giving the next error in the system error queue.
SCPI command to query if the scope is ready for the next command.
SCPI command for clearing statistics/status values in scope.
SCPI command to query the scope what its trigger/acquisition state is right now. This could be Running, Waiting or triggered etc.
SCPI command to stop the scope here-and-now (freeze the acquisition).
SCPI command to stop the scope at the next trigger point.
SCPI command to resume the acquisition.
SCPI command to query the trigger mode - e.g. Edge or alike.
SCPI command to query the trigger level (voltage).
SCPI command to set the trigger (will be both the trigger mode and the trigger level).
SCPI command to query the T/DIV (time per division).
E.g. 1uS mean each horizontal division is 1 micro second.
SCPI command to set the T/DIV (time per division).
SCPI command to query the V/DIV (volts per division).
E.g. 1V mean each vertical division is 1V.
SCPI command to set the V/DIV (volts per division).
SCPI command to dump the current image from scope via network. This is quite different per vendor and even per scope.
A list of all the T/DIV being available for the scope.
E.g. 1uS mean each horizontal division is 1 micro second.
A list of all the V/DIV being available for the scope.
E.g. 1V mean each vertical division is 1V.
Warning
If some of the SCPI commands (in the Excel file) it states {0} which you should see as the actual value passed. The value is handled by CRT.
There are a few important things to know generally for these Excel files.
- You should not have empty rows in the middle of your data, as this will be considered as end of data.
- If there is a yellowish highlight in the data cell, it means the data needs to be validated or corrected manually.
- No formatting (colors, bold or italic etc.) will be carried over from Excel to CRT UI.
- All paths uses
/instead of\(to support Linux and macOS). - Treat all folders and filenames as case-sensitive (to support Linux and macOS)
- Check logfile after startup, as it will reveal any errors with the data files.
Go to Wiki Home.
Go to Explanation data files.