Dependencies
The DS2000A Upgrade Utility depends on several 3rd party software components. The portable edition does not install these prequisites, you need to do it manually.
The application was built on the .Net 4.5 framework. This means you need to have either .Net 4.5 or 4.5.1 in order to be able to run it.
|
Communication with the DS2000A devices is accomplished via the NI Visa instrument drivers. You need to have the 5.4 or later version.
|
VISA resource network discovery is performed using the mDNS protocol. The discovery service is provided by Apple Bonjour 3.
|
network discovery
DS2000A series DSOs can be detected in your LAN by two methods: VXI or mDNS discovery. DS2000A Upgrade Utility relies in the latter, since it is the faster, more modern and streamlined solution.
If you want to make your device detectable, first you need to configure it properly. Find out its IP address, and enter it in a web browser. There you will see the "Network configuration" pages of your DSO. Go to the "Network settings" page, and enter a (service) name and hostname. Make sure the "mDNS" checkbox is checked. Then click on the "Apply settings" button. On the "Network information" page you can verify the new settings.
And that should be the end of the procedure ... but unfortunately it is not, due to a bug in the DS2000A firmware (v00.02.01.00.03). For some odd reason, on most occasions, the DSO forgets to save the new mDNS settings to its non-volatile storage. I.e. they are lost on the next startup. And here comes the tricky part: I could not yet found any reasonable logic or pattern as to what exactly causes the the settings to get actually stored when they get stored.
I tried many different combinations of the following actions (followed by reboot), and after about 1-2 hours of of trying, somehow managed to make it work.
If you want to make your device detectable, first you need to configure it properly. Find out its IP address, and enter it in a web browser. There you will see the "Network configuration" pages of your DSO. Go to the "Network settings" page, and enter a (service) name and hostname. Make sure the "mDNS" checkbox is checked. Then click on the "Apply settings" button. On the "Network information" page you can verify the new settings.
And that should be the end of the procedure ... but unfortunately it is not, due to a bug in the DS2000A firmware (v00.02.01.00.03). For some odd reason, on most occasions, the DSO forgets to save the new mDNS settings to its non-volatile storage. I.e. they are lost on the next startup. And here comes the tricky part: I could not yet found any reasonable logic or pattern as to what exactly causes the the settings to get actually stored when they get stored.
I tried many different combinations of the following actions (followed by reboot), and after about 1-2 hours of of trying, somehow managed to make it work.
- Changing the service name and hostname
- Toggling the "mDNS" checkbox
- Clicking the "Initiate" button
- Toggling "Auto-IP"
- Changing the password
- Waiting after startup
- Waiting after applying the settings
Error Management
Communication errors in Quick configuration mode
Whenever a VISA communication error occurs in Quick configuration mode, the connection to your DSO will be terminated. You will need to reconnect in order to be able to perform further actions.
Errors in Wizard mode
If an error is encountered when committing (clicking "Next" in) a wizard page, the commit operation will be ignored and the current wizard page will remain visible.
Error log
The Utility logs each and every runtime error. Even unhandled exceptions are logged, before the application terminates. The log file is located in [installation flder]\Temp\ErrorLog.txt
Whenever a VISA communication error occurs in Quick configuration mode, the connection to your DSO will be terminated. You will need to reconnect in order to be able to perform further actions.
Errors in Wizard mode
If an error is encountered when committing (clicking "Next" in) a wizard page, the commit operation will be ignored and the current wizard page will remain visible.
Error log
The Utility logs each and every runtime error. Even unhandled exceptions are logged, before the application terminates. The log file is located in [installation flder]\Temp\ErrorLog.txt