I saved a configuration file to a USB flash drive on my B2902A. It is a simple setup: Linear voltage sweep on Ch1 with current limit. This is being used to test I-V curves on LEDs. At the point I saved it, everything was working fine and the IV graph is perfect on the display.
Saving it to USB Flash seems OK. Recalling it seems OK (it loads) and it seems to set all the parameters correctly as best as I can tell (including sweep enabled with multiple points). However, when I hit the trigger key to initiate a sweep (after reloading the configuration setting from a fresh power up), nothing happens. No matter what I try, I can't seem to get it to sweep again. Only shutting off the power and reprogramming the limits from scratch can reset it.
I am using the most current firmware version 1.01144.9870 and I've attached two configuration files for reference.
It seems that either the configuration file isn't saving all the appropriate parameters or it's corrupting them upon import (or not importing everything that matters).
Basically, the USB flash is useless if I can't recall the settings intact. What else can I try? Something definitely seems buggy here and I've tried it multiple times, even changing the file names I'm saving. Same issue each time. I can't force a triggered sweep after reloading the settings.
Perhaps unrelated (or not), it doesn't maintain the X/Y min max values on the display graph, so that information is lost and has to be manually reset.
I also have several other suggestions for the B2902A that would make it much more useable. How can I get in contact with the Product Manager for this (I believe it's designed in Japan?) -- I believe I can help make this a better product with some minor firmware enhancements but I need to establish communication with the product management and design team. It's not clear that anyone from the SMU product team is reading these forums -- I'm not even sure where to post these since there is no SMU forum and they seem to be posted in random forums.
Thanks. I did hear back from an applications engineer in Colorado who is in touch with the Hachioji facility where this is designed. The bug has been confirmed and apparently a fix is already in the works. I expect to see a beta version soon and will post an update confirming the fix once I've verified it. Thanks for checking in Matt. By the way, how can we get a dedicated forum going for semiconductor test/SMU type devices? There really isn't a good section yet for this. Can you get one of the forum moderators to open a new section for Source Measure Units and other component test products?
By the way, how can we get a dedicated forum going for semiconductor test/SMU type devices? There really isn't a good section yet for this. Can you get one of the forum moderators to open a new section for Source Measure Units and other component test products?
Greg, I'm the T&M eMarketing Manager and have responsibility for the Technical Forum. The discussion with our Hachioji facility has already begun (we talked again this weekend) and they are escalating to their management team.
The SMUs are a popular product area, and the new B2900-series has greatly increased the number of Agilent SMUs. I require each Forum to have a Moderator who can actively answer questions within 24 hours. The team is discussing who can be an owner/moderator.
Thank you for reporting this bug to the Agilent Contact Center (800-829-4444). The bug has now been fixed in the latest B2900 firmware update (version 2.0.1225.1717) and is available on Agilent.com. Here is the direct link to the firmware update.
The zip download includes a Readme.txt with instructions for updating the system. I tested this on my B2900 here and confirmed that the configurations now load correctly, with the manual trigger settings intact.
Please let us know if you run into any additional questions. Agilent support can be reached at 800-829-4444 or send your support requests to USA_Orders@agilent.com.
Agilent Applications Engineer
Thank you for the prompt attention to this fix. I will test the new release and update my findings here. I really appreciate the closed-loop feedback on this. Great customer service and attention from the factory. Much appreciated. From the Read Me, looks like some other good fixes in this release as well. I look forward to testing it.