Products > Test Equipment

Rigol DP832 - Firmware list and bugs

<< < (126/153) > >>

skander36:

--- Quote from: Gandalf_Sr on March 14, 2020, 11:04:45 am ---I will have time to look at this over the next week, how do I find out what port number my 34461A is running on?

--- End quote ---
Try 5025 .
But don't commit data if the script doesn't finished ok.
Just restart from switch .

garrettm:
I noticed that you used

*rst

more than once... That resets the instrument back to the "default state." Don't use that. It's not needed. Only *cls is needed, it clears any errors present that the instrument might hang on. And to be honest, even *cls isn't needed, but its good practice to clear errors to avoid possible issues.

From what I've seen of the Putty output you should be good to go. :fetch? return only a SINGLE value each time. That's GOOD! If you placed the DMM into current measurement and then used the remote commands to change it back to voltage, which is what I assume you did, then THAT IS GOOD! You now need to figure out the same thing for the rest of the methods: i.e. local voltage and remote and local current measurement setups. In your case, just replace all local methods in the script with the remote ones.

Finally, you just need to put all that BACK into the the TelnetCal.java file and recompile it and then run the NEWLY complied script. Again, there is no reason the script won't work if you can do it manually.

skander36:

--- Quote from: garrettm on March 14, 2020, 11:24:14 am ---
if that works as expected, then we need to:

1) manually Telnet into the DP832 and clear the cal constants using

:calibration:start 11111,ch1
:calibration:clear ch1,all.

2) Close Putty to terminate the Telnet connection and then run the script with option 3 voltage calibration for ch1 and option 0 for both ch2 and ch3.

The :calibration:clear ch1,all command will fix any bugs that are present and allow the voltage calibration to work correctly. Then upload the output of the script. If you can manually send commands, then the script can do the same. But if they don't work, then it can't either.

--- End quote ---

Done but same problem . Stall at the same point.

skander36:

--- Quote from: garrettm on March 14, 2020, 12:05:35 pm ---I noticed that you used

*rst

more than once... That resets the instrument back to the "default state." Don't use that. It's not needed. Only *cls is needed, it clears any errors present that the instrument might hang on. And to be honest, even *cls isn't needed, but its good practice to clear errors to avoid possible issues.

From what I've seen of the Putty output you should be good to go. :fetch? return only a SINGLE value each time. That's GOOD! If you placed the DMM into current measurement and then used the remote commands to change it back to voltage, which is what I assume you did, then THAT IS GOOD! You now need to figure out the same thing for the rest of the methods: i.e. local voltage and remote and local current measurement setups. In your case, just replace all local methods in the script with the remote ones.

Finally, you just need to put all that BACK into the the TelnetCal.java file and recompile it and then run the NEWLY complied script. Again, there is no reason the script won't work if you can do it manually.

--- End quote ---

For the moment I'll be glad to see if the voltage works and for what reason and after that current callibration will come .
But I dont understand how is voltage reading and interpreted to see why I'm not getting output in script running ...
And I don't understand why are remote and local methods and when and why they are changed (called) ...

garrettm:

--- Quote from: skander36 on March 14, 2020, 12:05:58 pm ---Done but same problem . Stall at the same point.

--- End quote ---

Interesting... I can't say what the issue is unless I was able to see your setup.


--- Quote ---But I dont understand how is reading of the voltage interpreted to see why I'm not getting output in script running ...
--- End quote ---

The actual method doing the reading is below. It uses readLine(), which returns a String. All Telnet and SCPI stuff is done by Strings.

  public String read() throws InterruptedException {
    String s = null;
    try {
      s = in.readLine();
    } catch (IOException e) {
      System.out.println("An IO exception occurred");
      Thread.sleep(2000);
      System.exit(1);
    }
    return s;
  }

If you are talking about removing the + signs, I think I went over that already. Otherwise there isn't much going on here. If the script was able to print a measurement, then reading the output buffer of the DMM is working. Though something is causing the next read to fail. Either *OPC? is always returning 0, causing an infinite loop or a null string is being received, but that should throw an error.


--- Quote ---And I don't understand why are remote and local methods and when and why they are changed ...
--- End quote ---

The remote methods are for configuring the DMM for automated measurements. The local methods are for in between automated measurements so you can see the DMM screen update normally. The change over between voltage and current is based on a guess for what the next measurement will be. This is so the DMM will be set to measure current as you move the banana plugs from the voltage terminals to the current terminals without needing to do anything.

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