The "U4" MCU doesn't support reading the current firmware, only writing a new firmware is possible. It's designed that way.
In the k-firmware documentation ttester-1.13k.Bohu.pdf at page 77 there is this:QuoteFor JFET transistors often the characteristic current Idss is specified, the current in the drainwhen the gate-source voltage is 0V. Here, however, the current is given by a 680 Ω load resistance atthe source side of the JFET. The load resistor generates a reverse voltage Vgs, which is also shown.With a 470kΩ load resistor at the source side of the JFET the Source-Drain current will be nearlyzero. With this circuit we can get the Gate-Source Cutoff voltage Vgs_off exactly enough, if thevoltage remain below 5V. With this two operating points we can estimate the current Igss with thenearly quadratic characteristic curve of the current. If the estimated current Idss stay below 40mA,a additional measurement is done without a additional resistor at the source pin. With the measuredvoltage at the source pin we can compute a additional current value. Now we can compute a betterestimated current Idss with this higher current valued, the gate-source voltage and with the knownquadratic current curve, if the value of 40mAis not exeeded. Due to the symmetrical design of theJFET transistors, the drain and source can not be distinguished.
So I think it's feasible
4) avr8 toolchain 3.6.2 + Arduino-IDE 1.8.13 avr binaries (gcc 7.3.0)
like 3), but with binaries replaced by IDE ones
TC1 - 644PA inside - which I already tried in november to get working. MLCCs, diodes and measurement Rs (to 0,1%) changed, U4 successfully flashed.
Tester powers on, makes one measurement and powers off. Powers off so fast, that's not possible to read the result. As I described in my old postings. Same with v1.40
T7 - 344PA inside - HW ist china factory, no MLCCs or something else changed. U4 successfully flashed.
If there is no part in it, tester did not find any part (which is correctly) and restarts automatically a new measurement. This will be done 5 times and power off.
If there is any part in it (e.g. a C), tester starts to measure, shows result for some secons and will repeat measurment like a loop. It will never stop. Only if part is removed (then it will try only 5 times like no part at the beginning) or battery is empty.
TC1 - 644PA inside - which I already tried in november to get working. MLCCs, diodes and measurement Rs (to 0,1%) changed, U4 successfully flashed.
Tester powers on, makes one measurement and powers off. Powers off so fast, that's not possible to read the result. As I described in my old postings. Same with v1.40
That's what the original firmware of U4 does. Presumably the reflashing of U4 went wrong.
Checking target MCU ...
MCU type: STC15L104W
F/W version: 7.2.5Q
Current H/W Option:
. Current system clock source is internal IRC oscillator
. IRC frequency: 11.999MHz
. Wakeup Timer frequency: 26.419KHz
. Do not detect the level of P3.2 and P3.3 next download
. Power-on reset, use the extra power-on delay
. RESET pin behaves as I/O pin
. Reset while detect a Low-Voltage
. Thresh voltage level of the built-in LVD : 2.42 V
. Inhibit EEPROM operation under Low-Voltage
. Hardware do not enable Watch-Dog-Timer
. Watch-Dog-Timer pre-scalar : 256
. Watch-Dog-Timer stop count in idle mode
. Program can modify the Watch-Dog-Timer scalar
. Do not erase user EEPROM area at next download
. Do not control 485 at next download
. Do not check user password next download
. TXD is independent IO
. TXD pin as quasi-bidirectional mode after reset
. P3.3 output HIGH level after reset
. Testing time: 2018-6-28
. MCU type: STC15L104W
F/W version: 7.2.5Q
Adjusting frequency ... [0.750"]
Adjusted frequency: 11.999MHz (-0.010%)
Re-handshaking ... Successful [0.125"]
Current Baudrate: 38400
Erasing MCU flash ... OK ! [0.343"]
MCU ID : F2D4246E1A6F8E
Programming user code ... OK ! [2.171"]
Programming OPTIONS ... OK ! [0.047"]
H/W Option upgrade to:
. Current system clock source is internal IRC oscillator
. IRC frequency: 11.999MHz
. Do not detect the level of P3.2 and P3.3 next download
. Power-on reset, use the extra power-on delay
. RESET pin behaves as I/O pin
. Reset while detect a Low-Voltage
. Thresh voltage level of the built-in LVD : 2.42 V
. Inhibit EEPROM operation under Low-Voltage
. Hardware do not enable Watch-Dog-Timer
. Watch-Dog-Timer pre-scalar : 256
. Watch-Dog-Timer stop count in idle mode
. Program can modify the Watch-Dog-Timer scalar
. Do not erase user EEPROM area at next download
. Do not control 485 at next download
. Do not check user password next download
. TXD is independent IO
. TXD pin as quasi-bidirectional mode after reset
. P3.3 output HIGH level after reset
. MCU ID : F2D4246E1A6F8E
. MCU type: STC15L104W
F/W version: 7.2.5Q
. Set frequency: 12.000MHz
. Adjusted frequency: 11.999MHz
. Trim error: -0.010%
Complete !(2020-08-08 07:25:25)
TC1 - 644PA inside - which I already tried in november to get working. MLCCs, diodes and measurement Rs (to 0,1%) changed, U4 successfully flashed.
Tester powers on, makes one measurement and powers off. Powers off so fast, that's not possible to read the result. As I described in my old postings. Same with v1.40
I checked PD1/PD2 with a scope. No signals, only level changes.
PD2 changed from 2,8V to 4.8V after switching on. PD1 from 3.0V to 0V. And both back after power off.
And also no effect if P1 + P2 is connected to GND or VCC. Time is still the same.
I checked PD1/PD2 with a scope. No signals, only level changes.
PD2 changed from 2,8V to 4.8V after switching on. PD1 from 3.0V to 0V. And both back after power off.
And also no effect if P1 + P2 is connected to GND or VCC. Time is still the same.
In that case the new U4 firmware should be running. The m-firmware can be configured to run just one probing cycle and then power off by setting CYCLE_MAX to zero (default is 5). What are your settings for CYCLE_DELAY, CYCLE_MAX and POWER_OFF_TIMEOUT?
Hi,
Got a GM328A with 1.12k and wondering how can I upgrade its firmware.
Is there a compiled 1.40m firmware for this so I could flash it?
Or, is there any document on how to compile the sources and get the flash files from this repository?
https://github.com/madires/Transistortester-Warehouse/tree/master/Firmware/m-firmware
Alternatively I see this one but I am not sure if it is a 1.40m
https://www.mikrocontroller.net/svnbrowser/transistortester/Software/trunk/mega328_GM328/
Is this 1.40m?
P.S.Never mind about how to compile, found this post that gives the steps
https://www.eevblog.com/forum/testgear/$20-lcr-esr-transistor-checker-project/msg1011926/#msg1011926
Spoke too soon, tried it but got errors so back to square one.
Hi,
Got a GM328A with 1.12k and wondering how can I upgrade its firmware.
Is there a compiled 1.40m firmware for this so I could flash it?
Or, is there any document on how to compile the sources and get the flash files from this repository?
https://github.com/madires/Transistortester-Warehouse/tree/master/Firmware/m-firmware
Alternatively I see this one but I am not sure if it is a 1.40m
https://www.mikrocontroller.net/svnbrowser/transistortester/Software/trunk/mega328_GM328/
Is this 1.40m?
P.S.Never mind about how to compile, found this post that gives the steps
https://www.eevblog.com/forum/testgear/$20-lcr-esr-transistor-checker-project/msg1011926/#msg1011926
Spoke too soon, tried it but got errors so back to square one.
Ok, finally managed to be able at least to compile the 1.40m from here, (used a virtualbox XP since in my W10 I could not)
https://github.com/madires/Transistortester-Warehouse/tree/master/Firmware/m-firmware
But now I'm faced with a more daunting task, to identify what settings are needed for the GM328A .
Are the exact settings for the GM328A (config.h, config_328.h) known or anyone done this before and can help here?
Check "clones" file for GM328 settings adn readme file also.
Check "clones" file for GM328 settings adn readme file also.
Thanks,
I have already seen the clones text, it does not have the exact GM328A.
And it looks to me that to out the proper settings there the schematic is needed, does anyone got the exact GM328A schematic?
What do you think about replacing 78L05 to MCP1703? Will the measurement more accurate?
If MCP1703 is assembled just need to comment #define HW_REF25 or anything else?
Maybe this one fits to your tester?
https://dragaosemchama.com/en/2019/04/gm328a-reverse-engineering-new-firmware-and-tetris/
Still one questions/sugesstion
I tried to test a brand new RGCL60TS60GC11. Only Diode is recordnized. I guess gate voltage is to low to switch the IGBT on?
What do you think about an small adapter PCB for testing IGBTs with higher gate voltage (even 15V ones). Higher voltage can be taken from boost converter and adjusted thru a e.g. LM317.