Products > Test Equipment
Fluke/Tektronix Bushealth Code: 192C/196C/199C/215C/225C/190 (I & II) THS3000
squadchannel:
--- Quote from: patpat on October 17, 2024, 11:13:08 pm ---You uploaded 190II_V11_46 binary to THS3024:
How did you do it? burning Flash or serial?
--- End quote ---
Serial. can write by using EXTENSION COMMAND.
I have tried the write commands available in UHM mode, such as PB and WB, but they do not seem to work for flash areas.
0 is returned for ACKN, which seems to be normal, but when I read it in RB, it is not written.
--- Quote from: patpat on October 17, 2024, 11:13:08 pm ---Remember editing the flashtool.ini of the 190II_V11_46.exe with the decrypting tool
should be enough for flashing the scope in the regular way.
--- End quote ---
it will work if I rewrite flashtool.ini, but the EXTENSION COMMAND is different for the 190II and THS.
Since we do not know how this will affect the scope, used the THS one for EXTENSION COMMAND and the 190II one for the data to be written.
--- Quote from: patpat on October 17, 2024, 11:13:08 pm ---You say that the THS with Fluke FWis unusable: why?
wouldn't be just like using a Fluke 190 only in "Scope" mode (No Meter Button)?
--- End quote ---
As mentioned, the keypad layout is different.
It can be used to some extent, but the lower buttons(v) on the trigger level serve a different purpose.
If the keypad layout can be changed, it can be used.
Waveform acquisition is working fine, as is saving, etc. Calibration data can also be used without modification from THS.
WC and RC data is attached in #18. https://www.eevblog.com/forum/testgear/fluketektronix-bushealth-code-192c196c199c215c225c190-(i-ii)-ths3000/msg5680847/#msg5680847
If it is all data, it is in #11. https://www.eevblog.com/forum/testgear/fluketektronix-bushealth-code-192c196c199c215c225c190-(i-ii)-ths3000/msg5677207/#msg5677207
patpat:
This is the WC command format in hex
where each chunk is of the form
[Header][Payload][Trailer]
[233080nnnn][Payload][xxyy0D300D]...[233080nnnn][Payload][xxyy0D300D]
nnnn=payload size
xxyy=some sort of checksum
Edit01
The capture not making distinction between TX and RX bytes makes me think that the previous Trailer
might include an ACK from the scope then could be
[Header][Payload][Trailer]{Scope ACK}
[233080nnnn][Payload][xxyy]{0D300D}...[233080nnnn][Payload][xxyy]{0D300D}
squadchannel:
In 190II firmware, BUSHEALTH can be enabled with the CI 17 command; Medical does not seem to be enabled.
However, when in BUSHEALTH mode, the screen whiteouts. it is possible to turn BUSHEALTH off with the F4 key.
It appears to be an incomplete mode.
The CI 14 command rewrites $4000816C by 2bytes.
I tested this on a V11.46'ed THS3024. Not sure how it works with the real 190II. :-//
mains voltage in japan.
It is unfortunate that the METER mode is not available in THS firmware.
CI 14 is a command that can limit the languages that can be selected. $4000816C 2bytes change.
THS uses a different language list than 190II. (not available S.CHINESE and T.CHINESE in 190II)
the CI 60 can change the input type of the scope.
0=4ch
1=2ch+DMM
2=4ch
CI 60 command rewrites $400080BF by 1bytes.
2ch+DMM is a model with both DMM and scope functions.
set to CI 60,1 (2ch+DMM), the DMM mode can be used in THS.
I could not measure the resistance, but it beeps in Continuous mode.
I immediately put it back in because I think I will break the frontend if I go too deep. (THS is 0.)
patpat:
Good Findings,
Confirmed
CI 17,110195
is the way to activate Bushealth in Fluke both 199C and 190 families,
I wonder if THS having a different UI even has the option available or it was never included.
When is the blank screen triggered? does it on its own or after some keyboard interaction?
I can also confirm that the "Medical" option does not work on 199C
In THS there's not [Meter] button but I wonder if there's not Serial commands controlling the UI
Best,
Pat
squadchannel:
The Meter button unfortunately resides in a key matrix that is not assigned in THS.
The red text is where it differs from THS.
When BUSHEALTH enters the mode, it automatically starts the diagnostics.
The program for that diagnostic screen seems to be incomplete and appears to be a white screen.
It seems that the screen is only white, but the keys can be operated, and pressing the F4 key to turn it off will return the screen to its original state.
Also, the scope gets stuck when WIRING INFO is pressed. Overall bushealth mode seems to be an incomplete program.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version