Products > Test Equipment
Fluke/Tektronix Bushealth Code: 192C/196C/199C/215C/225C/190 (I & II) THS3000
patpat:
I do not think a limiting bandwidth software restriction would be selective of amplitude and
sure not lead to a crash when triggered. This smells a hardware related issue.
I kept reading and I'm now glad you found the culprit.
About your SCMTool.exe not clear what it does,
does it download a CAL file from the instrument? does it upload it?, just for THS or Fluke too?
I lookead at QI/CI 25 they read/write the same memory position, ooks like it takes just a number,
but so far I couldn't find any relationship with bandwidth; why do you think is related to it?
Best,
Pat
squadchannel:
It is designed for THS, but can be used for other models by rewriting the cfg.
You can dump the flash with the attached cfg.
Drag and drop the .cfg into the .exe and it should dump automatically.
I have not tested fluke and I don't think it works.
Just enter UHM mode and execute the GB command.
I don't think it will corrupt anything, etc.
It takes time because it reads and saves one byte at a time.
dumpcal.cfg: Just the cal data backup takes less than a minute.
dumpflash.cfg: Backing up the entire flash takes longer, about 5 minutes.
It can be write flash, and there is a cfg, but I will publish it after some more research.
The reason for CI25 is that the firmware has data that is initialized and loaded when the checksum of the cal data does not match.
In the case of THS firmware, the THS3014 data is loaded (maybe. because Model Number for VER&CAL is THS3014).
After comparing that data with the 3024 data, we found that CI25 and CI90 are different.
CI90 rewrites $4000819C by 2 bytes. Little endian; 1229 for THS3024 and 1230 for THS3014, but what that means is not known.
CI25 rewrites $400080C4 by 1 byte; seems to accept 0-3, 2 for THS3024, 1 for THS3014.
Tried 0-3, same settings for SG, 250MHz, -20db, forgot to install the 50 ohm terminator.
I think 0=60MHz, 1=100MHz, 2=200MHz, 3=500MHz.
I forgot to get an image at ci 25,0, almost the same as at ci 25,1.
The attenuation will change, but other than that, I can't say for sure. It is very likely that the cal data does not fit either.
I also tried CI 25,3 (500MHz?) but nothing changes, it can't reach 500MHz, it is attenuated and completely flat.
In order CI 25 1, 2, 3.
patpat:
OK I understand how you program works, you can use GL or GW instead of GB (whatever gives you the most bytes),
remember is little-endian, and that should double or quadruple the transfer speed.
You can also invoke the UHM mode programmatically by calling:
EM
FLUKEUHM
XXXXXXXXXXXXXXX <<< Send them one a loop one at the time, waiting 20 tickcounts checking for the instrument answer "0"
Do your GB/GL/GW stuff
etc.
that's how FlashTool.exe Does it.
About the Cal transfer there are 2 modes specified in the FlashTool.ini file
CAL_TYPE=BLOCKS (default sends blocks as you saw)
or
CAL_TYPE=Normal (sends w/o blocks)
I'll try to see CI25 and CI90 and see if I get any data.
Best,
Pat
patpat:
I polished a bit the Calibration Backup and Restore tool,.
--
This tool is able to Backup and Restore Tektronix THS3024/3014 Calibration data.
Put all its components under an empty directory and run FlashTool.exe the tool will create
in the same directory a read only file named <SN>.CAL i.e. 404025132786.CAL (7Kb for a THS3024).
Save your backup file in more than one place.
To restore the Calibration data just run FlashTool.exe in the presence of the .CAL file and it’ll be
uploaded to the instrument.
To get another CAL file just erase the CAL file and run again FlashTool.exe
This tool is just a patched FlashTool.exe preventing the erase of the CAL file at the end of its job
and a special FlashTool.ini preventing the upload of any new firmware.
I'm also attaching my THS3024 CAL file
Navigation
[0] Message Index
[*] Previous page
Go to full version