Author Topic: Metcal MX-5200 and MX-5000 firmware and data-EEPROM information thread  (Read 13140 times)

0 Members and 1 Guest are viewing this topic.

Offline benj38Topic starter

  • Regular Contributor
  • *
  • Posts: 81
  • Country: us
Re: Metcal MX-5200 and MX-5000 firmware and data-EEPROM information thread
« Reply #25 on: October 18, 2019, 12:39:19 pm »
@Mike
I could not get the high point to allow me to do anything; the med point gave me maybe one second where it would accept anything, and even for the low point one has to be as fast as a demon to press the button when the displayed power is at a given value. I guess the obvious explanation is that they use a static load instead of a soldering tip for setting this at the factory.

I would have thought that the power draw corresponds to predictable absolute values out of the detection circuit (especially since the bar-graph is just a relative indicator and not a real measurement), and thus there would be no need to calibrate the bar-graph.

That said, some findings from the posts #msg2730662, and #msg2743296 certainly support this conjecture.
« Last Edit: October 18, 2019, 12:49:13 pm by benj38 »
 

Offline benj38Topic starter

  • Regular Contributor
  • *
  • Posts: 81
  • Country: us
Re: Metcal MX-5200 and MX-5000 firmware and data-EEPROM information thread
« Reply #26 on: October 19, 2019, 02:50:19 pm »
After playing with the service menu I can add the following information.

1. The clock (Rtc) option is completely useless: once set, it never advances as time passes, and it is completely forgotten when power is lost. Indeed, the only information about the clock stored in the data-EEPROM is a single bit indicating whether to show it or not.

2. The bit controlling the display of the clock, as well as the bit controlling the two options under the "Comm" menu are stored (together with the bit flagging whether the bar-graph is  "standard"  or "ultrafine" -- see OP) in the low nibble of the byte at address 01, as follows:
  Communication serial mode is stored in bit 1. It is 0 for "On Event" and 1 for "polled".
  Clock display is stored in bit 2. It is 0 for "off", and 1 for "on".
  Bar graph scale is stored in bit 3. It is 0 for "standard" and 1 for "ultrafine"
Thus, for example, if all flags are set the low nibble at address 01 will be 0E.

3. The "Cal" option in the service menu is responsible for all the rest of the data-EEPROM non-zero bytes except for the first 4 bytes. Using a glass of cold water to dip the tip in I managed to draw enough power (readings in the 600s) to allow me to get the option to also set the "Cal Hi Poi..." that eluded me before (see previous message in thread). Note that there was no real way for me to chose a particular number to set as the power-draw was constantly changing, so the calibration was to basically random values in the allowed range.  I Have performed a calibration of all three points (the unit does not save anything unless all points are done together), and then read the data-EEPROM, and then reset it. I repeated this 3 times, with the following results:

00 00 09 01 D6 12 85 3A 5D F4 11 BF 00 00 5C 42
00 00 09 01 45 76 8C 3A CB B0 18 BF 00 00 5C 42
00 00 09 01 48 A4 6E 3A 22 17 03 BF 00 00 5C 42

For comparison, here is the state after a reset:

00 00 09 01 07 16 93 B8 54 20 4E 3E 5F 01 22 C1


Observe that:
 a. Each calibration completely rewrote the values in addresses 04 to 0F.
 b. Addresses 07, and 0B to 0F were written to the same values on all three attempts, thus only 6 bytes are different between different calibrations. This looks reasonable since the number presented on the LCD (and presumably stored) for each of the three points is a 4 digit decimal number (however, the low-point number was less than decimal 100 - which would indicate at least one 00 byte, so the encoding is probably not direct, but translated to the domain of the LCD control).
 c. Addresses 00 to 03 were unchanged - this was to be expected for addresses 00 to 02, but leaves the question open as to what is the 01 at address 03 is used for.

The most interesting point is that a fourth calibration attempt yielded very similar results except that it also wrote FF to address 01, thus completely confusing the unit as to which channel(s) had a hand-piece connected to it.

In summary, it looks like most of the service menu is half-baked, and probably the only useful option is the "reset".
« Last Edit: October 19, 2019, 03:01:20 pm by benj38 »
 

Offline Zucca

  • Supporter
  • ****
  • Posts: 4308
  • Country: it
  • EE meid in Itali
Re: Metcal MX-5200 and MX-5000 firmware and data-EEPROM information thread
« Reply #27 on: October 23, 2019, 04:47:10 pm »
@zucca, do you mind resetting your data using the service menu and posting the result? It is quite curious why your data is so different than ours (I remind you that ChuckDarwin has firmware 1.33 like you did).

Hi Ben,

thanks for the awesome investigation.
My unit is now at 1.36, should I do the test  anyway?

Take care,

Z
Can't know what you don't love. St. Augustine
Can't love what you don't know. Zucca
 

Offline benj38Topic starter

  • Regular Contributor
  • *
  • Posts: 81
  • Country: us
Re: Metcal MX-5200 and MX-5000 firmware and data-EEPROM information thread
« Reply #28 on: October 24, 2019, 01:53:57 pm »
@Zucca
Resetting your unit and posting the resulting data-EEPROM was supposed to help us eliminate three options:
  • The reset does not erase all the data-EEPROM. If that is the case, then even though you have the same code as me, the reset may not result in the same data-EEPROM.
  • The reset writes data to the EEPROM that may depend on analog information read from the board which is influenced by the settings of the trimmers on the board.
  • Data specific to a unit may be present in the code. Thus, even though both you and ChuckDarwin had the same version (1.33), your code is different than his, and thus may yield different data-EEPROM after a reset.
I find the third option highly unlikely, and it is the only option that in order to reason about you have to do two resets, one with my 1.36 code you have, and the other with the 1.33 code. The other two options are not very likely, but possible, and can be eliminated if you use the current 1.36 code and a reset yields the same data-EEPROM as mine.

In short, if you have the energy for one reset, use the current 1.36 code; otherwise, do one with the 1.36 code, and another with the 1.33.
« Last Edit: October 24, 2019, 01:59:24 pm by benj38 »
 

Offline Zucca

  • Supporter
  • ****
  • Posts: 4308
  • Country: it
  • EE meid in Itali
Re: Metcal MX-5200 and MX-5000 firmware and data-EEPROM information thread
« Reply #29 on: October 24, 2019, 03:18:20 pm »
Sure Sir!  ;)

I will be on vacation for the next two weeks, please be patient a little bit.  :popcorn:
Can't know what you don't love. St. Augustine
Can't love what you don't know. Zucca
 

Offline eeviking

  • Regular Contributor
  • *
  • Posts: 99
  • Country: dk
Re: Metcal MX-5200 and MX-5000 firmware and data-EEPROM information thread
« Reply #30 on: October 30, 2019, 03:53:38 pm »
Great thread guys. I just fixed two broken MX-5000's  :-+

One with bar graph not working/showing weird stuff, probably corrupted eeprom data. So it just needed a factory reset.  :-DD
Do I need to do a cal after factory reset?

The second one had no output, replacing shorted D12 fixed that.  :-+
It also had some LCD bleeding. Fund a new blue 16x2 display laying around so replaced it while I was in there.
Btw. trimmer RV1 is the display contrast.

Firmware is 1.21 and v1.22 any point in upgrading?

Anyone need a MX-5000? I have a spare  ;D

 

Offline benj38Topic starter

  • Regular Contributor
  • *
  • Posts: 81
  • Country: us
Re: Metcal MX-5200 and MX-5000 firmware and data-EEPROM information thread
« Reply #31 on: November 01, 2019, 04:27:08 pm »
@eeviking No need to do any calibration after a factory reset. The only data the reset overwrites that was calibrated at the factory is the bar graph display. To calibrate that you need a special load unit, for which we have no specs. Thus, it can only be done at the factory. However, the preset defaults that you get from the reset are pretty good, and the slight loss of accuracy in the bar-graph is really of little importance, as the bar-graph is used almost by anybody as an indicator rather than as an accurate measuring device.
 

Offline comka

  • Newbie
  • Posts: 5
  • Country: 00
Re: Metcal MX-5200 and MX-5000 firmware and data-EEPROM information thread
« Reply #32 on: November 04, 2019, 04:08:30 pm »
Excellent communication,
Who can compare the initial factory calibration and after reset.
And where is this one stored?
 

Offline benj38Topic starter

  • Regular Contributor
  • *
  • Posts: 81
  • Country: us
Re: Metcal MX-5200 and MX-5000 firmware and data-EEPROM information thread
« Reply #33 on: November 05, 2019, 03:14:24 pm »
Excellent communication,
Who can compare the initial factory calibration and after reset.
Currently, we are waiting for Zucca to do that (I can't since my EEPROM was corrupt when I started this investigation).

And where is this one stored?
I am not sure I am getting your question. The unit-specific bar-graph factory calibration data is stored in the MCU data-EEPROM. This data is overwritten by the reset procedure with default values that, almost certainly, are stored in the flash code (and are thus the same for all units with the same firmware version).
 

Offline Zucca

  • Supporter
  • ****
  • Posts: 4308
  • Country: it
  • EE meid in Itali
Re: Metcal MX-5200 and MX-5000 firmware and data-EEPROM information thread
« Reply #34 on: November 05, 2019, 03:48:13 pm »
Firmware is 1.21 and v1.22 any point in upgrading?

I upgraded my MX-5200 from 1.33 to 1.36 and I saw no differences.
The only thing I got was the feeling to have the last firmware.
Who knows what are the differences?  :-//

It looks like the 1.2x are the MX-5000 Firmware, and the 1.3x are  for the MX-5200.

Currently, we are waiting for Zucca to do that (I can't since my EEPROM was corrupt when I started this investigation).

I promise to do the job in the next two days or so.
Can't know what you don't love. St. Augustine
Can't love what you don't know. Zucca
 

Offline comka

  • Newbie
  • Posts: 5
  • Country: 00
Re: Metcal MX-5200 and MX-5000 firmware and data-EEPROM information thread
« Reply #35 on: November 05, 2019, 09:49:03 pm »
I am not sure I am getting your question. The unit-specific bar-graph factory calibration data is stored in the MCU data-EEPROM. This data is overwritten by the reset procedure with default values that, almost certainly, are stored in the flash code (and are thus the same for all units with the same firmware version).

I was wondering what bits of data were responsible for it.
That's interesting. it is possible to make changes so that the bar-graph is displayed as a percentage. So it’s easier to calibrate it. :)

Who knows what are the differences?  :-//


There are assumption that 1.36 and 1.37 correct sleep error.
To affirm  I can not, not have an MX-5200.
Didn't want to check the assumption?
 

Offline Zucca

  • Supporter
  • ****
  • Posts: 4308
  • Country: it
  • EE meid in Itali
Re: Metcal MX-5200 and MX-5000 firmware and data-EEPROM information thread
« Reply #36 on: November 05, 2019, 09:51:33 pm »
Ah there is a 1.37 FW for the MX5200, good to know.
Can't know what you don't love. St. Augustine
Can't love what you don't know. Zucca
 

Offline cs.dk

  • Supporter
  • ****
  • Posts: 642
  • Country: dk
Re: Metcal MX-5200 and MX-5000 firmware and data-EEPROM information thread
« Reply #37 on: November 10, 2019, 09:42:55 am »
Ah there is a 1.37 FW for the MX5200, good to know.

Yup, there is. Mine is 1.37 :-+
 

Offline comka

  • Newbie
  • Posts: 5
  • Country: 00
Re: Metcal MX-5200 and MX-5000 firmware and data-EEPROM information thread
« Reply #38 on: November 11, 2019, 05:11:57 pm »
Ah there is a 1.37 FW for the MX5200, good to know.

Also available... 1.37 FW
 

Offline Zucca

  • Supporter
  • ****
  • Posts: 4308
  • Country: it
  • EE meid in Itali
Re: Metcal MX-5200 and MX-5000 firmware and data-EEPROM information thread
« Reply #39 on: November 25, 2019, 11:07:48 pm »
Please forgive my unacceptable embarrassing delay.

Here attached the 1.36 after factory reset.

Can you share the 1.37 FW?

Thanks!
Can't know what you don't love. St. Augustine
Can't love what you don't know. Zucca
 

Offline benj38Topic starter

  • Regular Contributor
  • *
  • Posts: 81
  • Country: us
Re: Metcal MX-5200 and MX-5000 firmware and data-EEPROM information thread
« Reply #40 on: November 30, 2019, 08:26:33 pm »
@Zucca, thanks for posting the reset data flash.
Being identical to my data EEPROM after a reset, it confirms all of our conjectures :)
 
The following users thanked this post: Zucca

Offline prescout

  • Newbie
  • Posts: 1
  • Country: ua
Re: Metcal MX-5200 and MX-5000 firmware and data-EEPROM information thread
« Reply #41 on: April 21, 2020, 11:15:07 am »
here is my dumps
 
The following users thanked this post: Zucca

Offline Zucca

  • Supporter
  • ****
  • Posts: 4308
  • Country: it
  • EE meid in Itali
Re: Metcal MX-5200 and MX-5000 firmware and data-EEPROM information thread
« Reply #42 on: April 22, 2020, 10:41:19 am »
Thanks and welcome prescout!

Which firmware versions have your units?
Can't know what you don't love. St. Augustine
Can't love what you don't know. Zucca
 

Offline anthony_linac

  • Newbie
  • Posts: 1
  • Country: gb
Although this is about firmware I was also wondering about hardware. I noticed someone stated 1.3 firmware is mx5200 - has anyone found any actual hardware differences between the mx5000 and mx5200? Ie. Is it possible to get both outputs on at the same time with an mx5000 simply by upgrading the firmware? I have just acquired and mx5000 and this thread piqued my interest
 

Offline Zucca

  • Supporter
  • ****
  • Posts: 4308
  • Country: it
  • EE meid in Itali
mx5000 simply by upgrading the firmware?

No, otherwise it would be already documented here. They are two different HW.
Can't know what you don't love. St. Augustine
Can't love what you don't know. Zucca
 

Offline Zucca

  • Supporter
  • ****
  • Posts: 4308
  • Country: it
  • EE meid in Itali
Re: Metcal MX-5200 and MX-5000 firmware and data-EEPROM information thread
« Reply #45 on: November 19, 2022, 06:18:59 pm »
Success, upgraded to 1.36 from 1.33!

Just to inform the world that since I did the upgrade I am experiencing an sporadic problem: the tips are sometimes not recognized as original ones.


I am going back to the original 1.33....
Can't know what you don't love. St. Augustine
Can't love what you don't know. Zucca
 

Offline thm_w

  • Super Contributor
  • ***
  • Posts: 6384
  • Country: ca
  • Non-expert
Re: Metcal MX-5200 and MX-5000 firmware and data-EEPROM information thread
« Reply #46 on: November 21, 2022, 11:05:48 pm »
Yeah we don't even have release notes for what changed no? The iron heats up when turned on, thats all I need.
Profile -> Modify profile -> Look and Layout ->  Don't show users' signatures
 

Offline jeryray

  • Newbie
  • Posts: 4
  • Country: us
  • 33 Years at ABC Network Rf Engineering
    • Lectrorepair
Re: Metcal MX-5200 and MX-5000 firmware and data-EEPROM information thread
« Reply #47 on: April 21, 2024, 07:01:08 pm »
Anyone know why the MX5200 FW 1.37 does not always remember you last used 2 ports?

I have 5 of these 2x 1.37 that sometimes power up with only port 1 active?
JRC
 

Offline thm_w

  • Super Contributor
  • ***
  • Posts: 6384
  • Country: ca
  • Non-expert
Re: Metcal MX-5200 and MX-5000 firmware and data-EEPROM information thread
« Reply #48 on: April 22, 2024, 09:28:39 pm »
Anyone know why the MX5200 FW 1.37 does not always remember you last used 2 ports?

I have 5 of these 2x 1.37 that sometimes power up with only port 1 active?

No need to post twice.
OK so you have 5 units, and 2 are 1.37 that lose the setting. But what firmware on the others?
Have you tried the factory reset procedure mentioned above?
Profile -> Modify profile -> Look and Layout ->  Don't show users' signatures
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf