Products > Test Equipment

Keithley DMM7510, SMU 2450 & 2460 problems

<< < (6/29) > >>

HighVoltage:

--- Quote from: boborich on December 14, 2016, 11:27:20 am ---I downgraded to 1.5 yesterday and seems to be much better than 1.6. Haven't got any blue screen or lock up so far. Recommend you try that before the new FW come out.

--- End quote ---
Good to know.

My DMM7510 came with FW v1.5 installed and had no issues.
This confirms that the problems increased with the FW v1.6

dr.diesel:
Two updates from Tekley:

When I asked specifically about the AZ bug:

"I am waiting on an analysis from our engineering team in regard to performance/autozero; not sure it's a bug unless I missed something. In the meantime, I'll suggest some ways to reduce noise (flicker was mentioned). Autozero is designed to reset drift from the 0.000 reference, but it comes at a time expense. To reduce noise levels, you can increase NPLC, turn on Line Sync -both under Menu->Settings (under Measure)- and use a moving average filter -see Menu->Calculations (under Measure)->Filter."

And then:

"REGARDING BLUE SCREENS AND LOCKUP CONDITIONS:

We have confirmed blue screen and lockup conditions and are testing a hot fix for v1.6.1a firmware. This hot fix would be available for all touchscreen products. The hot fix will not be a general download because it is not a standard firmware release. We will be making it available to customers who have a critical need and are not able to use the next-rev-down firmware on their instrument. This hot fix will be incorporated into a future standard firmware release.

We encourage you to down-rev your firmware as a first attempt to correct the situation.
To down-rev your firmware from v1.6.1a, you can retrieve the most recent prior rev:
2450 http://www.tek.com/source-measure-units/2450-software-12
2460 http://www.tek.com/source-measure-units/2460-software-1
2461 http://www.tek.com/source-measure-units/2461-software
DMM7510 http://www.tek.com/digital-multimeter/dmm7510-software

If you have a critical need for the hot fix, please send me a private message with your email address for follow-up (click on Private messages [X] in the top right corner of the page, select Compose Message)."

maxwell3e10:
I switched to earlier version of firmware, but the problem with triggers is still present. Attached is the .tsp set up file, renamed .txt to allow download. It is actually just  a text file anyway.

The triggers are programmed from the front panel. The goal is to make measurements every 100 msec for 100000 samples. The program works, but it has never reached 100000 samples, usually stops somewhere between 5000 and 30000, at a random number.

Perhaps someone can upload this script and try to run it on their meter, to see if its a common problem.

HighVoltage:
Just to update everyone on this issue.
I have updated my 2450 SMU successfully to the hot fix (interim) FW version 1.6.3b  and the blue screen has not happened so far.
All looks good so far.

Keithley is planning to release a full FW update right after the holidays.

bson:

--- Quote from: plesa on December 04, 2016, 11:40:12 am ---I do not think they do not want to fix it but I expect that software team is shared across platforms and they are limited by resources for maintenance.

--- End quote ---
Of course, no one sits around and waits for a bug report to appear in their in basket and leaps to it...  Bugs are added to the scheduled and prioritized work of any engineering group and handled as they get to it.  However, HOW bugs are prioritized, and what's considered critical enough to drop other work and fix ASAP is telling of how customer-focused an organization is vs how engineering-focused it is.  (Engineers hate being broadsided like this and are very uncomfortable with context switching, especially when they're neck deep in working on a new product and have it entirely in their mind.  Not fun to have to switch this to some other product they haven't touched in a while and get back into that.  Tends to bias the views when prioritizing.)

As for inadequate information, if there's not enough in the report, such as engineering needs a reproducible test, then they should ask for it - reach out to the customer and ask.  But in a lot of organizations engineers aren't permitted to communicate directly with customers.  This is totally ack basswards - engineers should talk to customers when they need technical information and not have to go through product.  Product should prioritize bugs!  The reverse is anathema to customer response.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod