Tektronix MDO3000 Series - X/Y Mode S/W Bug  - Page 1
Forum section: electronics / testgear

author: AJ3G
author_rank: Regular Contributor
timestamp: January 30, 2022, 01:32:33 pm
content: All:Wondering if someone without the latest firmware can check a software glitch for me. In the latest revision of the software, if you mismatch your horizontal scale in X/Y Mode you get an error message. The scope then basically locks up and will not recover after pressing Menu Key. In some instances it take two or three reboots, while pressing the Default Setting to get the scope to function normally again. Since I do not want to roll back to the old firmware, I was hoping someone who has the revision before the latest might check this for me.Tektronix Applications & After Sales Support has been horrendous as of late (read previous post on this), so I doubt even if I put in a bug fix request anything will be done about it.Thanks,Rich

author: TekForever
author_rank: Contributor
timestamp: February 01, 2022, 04:51:05 pm
content: Can you walk me through the steps you do in order to duplicate this?

author: AJ3G
author_rank: Regular Contributor
timestamp: February 01, 2022, 06:19:28 pm
content: Thanks for your response!Basically, I enter into the X/Y Mode via the Aquire Function. I then move the amplitude controls for each channel for a mismatch (i.e. CH1 & CH2). I also change the time base. I am triggered from CH1. I ultimately get an error message as described before, which hitting the menu/clear button does nothing for. The scope will then hang, and will require a reboot.The only way to stop the hang is to press Defualt Setup right after booting.Rich

author: TekForever
author_rank: Contributor
timestamp: February 01, 2022, 07:13:45 pm
content: Does the error message displayed say this?"Settings conflictSet the XY Display to Off in order to use the following features:<long list>Push Menu off to remove this message."

author: AJ3G
author_rank: Regular Contributor
timestamp: February 01, 2022, 07:55:34 pm
content: Yes - but are you able to manipulate the controls once that flag is up? In my case it locked the scope up. Pressing Menu would have an effect after waiting for over a minute, but then the same flag again.Rich

author: TekForever
author_rank: Contributor
timestamp: February 01, 2022, 08:18:55 pm
content: That error flags when you attempt to use a blocked feature while using X-Y mode (Such as the ones listed on the long list). On the MDO3k I used to duplicate this, it was phantom-pushing the Set/Clear Mark button underneath the Pan/Zoom knobs. I found this out by going back to the default set up, messing with the horizontal scale knob until the setting triggered.After I went in and cleaned the front panel contacts and the front panel flex cable contacts (that runs behind the buttons next to the screen) with IPA, it didn't happen again.If I had to guess, based on my experience with these models and previous models that had similar issues, it might be your front panel malfunctioning due to dirty contacts and *maybe* misaligned spring-tabs. These tabs need to make contact with the metal chassis, if they don't it can cause issues with the FP. The front panel can cause a lot of strange issues on these models because of its design.If this is a work scope though I'd just get them to send it in to Tektronix.

author: AJ3G
author_rank: Regular Contributor
timestamp: February 01, 2022, 08:25:21 pm
content: Tekforever:This scope only has about 300 or so hour on it. I would be surprised if it were a Keypad FP problem. Pressing other buttons does eventually work, but one has to wait for what seems like a millennium for the commanded keystroke to take. The only time I see this type of behavior from an error message is when that specific flag is raised while in X/Y Mode. In all other instances of an error, the MENU key works to resolve the issue or at least works right away after pressing it.Rich

author: TekForever
author_rank: Contributor
timestamp: February 01, 2022, 08:31:19 pm
content: Hmm.On the MDO3k I used, the Menu Off button worked fine. It was on FW 1.26.I just updated it to 1.30 and I haven't encountered the same issue either. If I try to force the error by pushing a "forbidden" function, it can clear out easily by pushing Menu Off.

author: AJ3G
author_rank: Regular Contributor
timestamp: February 01, 2022, 09:19:35 pm
content: That is good information - I do have all the software/modules installed. When I was running in X/Y I did have the Frequency Counter up, and was looking at Freq & Vp_p for both channels one and two.If 1.30 is the latest, then that is what I am running. I downloaded it about six weeks ago tops..

author: TekForever
author_rank: Contributor
timestamp: February 01, 2022, 09:40:54 pm
content: If I get another chance, I'll try to use the Freq counter and all the measurements mentioned. I think there's another MDO3k with downrev around here.

author: AJ3G
author_rank: Regular Contributor
timestamp: February 01, 2022, 09:46:55 pm
content: Thanks - I will look forward to hearing your findings. I suppose its not the end of the world. I have saved a few configurations, so when it happens I simply hold the Defualt Config key, and then use one of my presets. It took me a while to get it out of this loop, because the scope would reboot, and then come back into the same fault condition.Rich

author: TekForever
author_rank: Contributor
timestamp: February 02, 2022, 03:30:01 pm
content: Hey, got a chance to use another MDO3k with 1.26 here. I tried it out using your settings but I really haven't had any issues, and even when I force that error I get nothing.

author: AJ3G
author_rank: Regular Contributor
timestamp: February 02, 2022, 07:23:42 pm
content: Thanks for the quick response - I have not had much need for X/Y Mode until recently. I need to see if I want to go back to an old update or just live with it. As long as I have the presets its not a big issue, but until I loaded a few that I use this error was forcing me back into a default setting or when the scope rebooted, and attempted to go back into the last configuration and again alert to the error, thus locking up the scope.Rich