Program that can log from many multimeters.

[HKJ]

How can I get Setup to update when the window is open and you change modes? I tried the below code but it does not work

Oops, you cannot.

Try this version: http://lygte-info.dk/pic/Projects/TestController/TestController.jar
and use a :updatemodechange: tag in the info part

[klausES]

...If something is strange, try starting in debug mode, it may give an explanation on what is going on...

Thanks for the information.
I will do that if an error occurs again.

I see the SDG2122X in the device list.
If there is time for it, it would be nice if I could also use this for my SDG1062X. 

[MikeLud]

HKJ,

I just tried :updatemodechange: and it does not work, am I using it correctly?

Code: [Select]

#cmdSetup info Mode Mode
:read: FUNC?
:readmath: unQuote(value)
:updatemodechange:

How can I get Setup to update when the window is open and you change modes? I tried the below code but it does not work

Oops, you cannot.

Try this version: http://lygte-info.dk/pic/Projects/TestController/TestController.jar
and use a :updatemodechange: tag in the info part

[HKJ]

I see the SDG2122X in the device list.
If there is time for it, it would be nice if I could also use this for my SDG1062X. 

I have the 2122, not the 1062.
What you can do is to make a copy of the 2122 definition file and change 2122 to 1062 in the file and check if anything works.

[HKJ]

I just tried :updatemodechange: and it does not work, am I using it correctly?

I was a bit too fast, you can try again now.

[MikeLud]

HKJ,

I just redownloaded and tested but still no luck, can you confirm if I am using :updatemodechange: correctly.

Code: [Select]

#cmdSetup info Mode Mode
:read: FUNC?
:readmath: unQuote(value)
:updatemodechange:
Thanks
Mike

I just tried :updatemodechange: and it does not work, am I using it correctly?

I was a bit too fast, you can try again now.

[klausES]

Made.
It seems that it works with the SDG1062X. 
Limits would have to be changed (e.g. sine from max. 120 MHz to max. 60 MHz for SDG1062X).

What strikes me is that the output ON / Off on channel 2 does not respond (it works on channel 1).
If I activate Output Channel 2 manually on the device, the software even shows me that, just switch from the software, because it does not respond.

And at volt it only allows pp setting, which is missing for rms.

[tautech]

Made.
It seems that it works with the SDG1062X. 
Limits would have to be changed (e.g. sine from max. 120 MHz to max. 60 MHz for SDG1062X).

What strikes me is that the output ON / Off on channel 2 does not respond (it works on channel 1).
If I activate Output Channel 2 manually on the device, the software even shows me that, just switch from the software, because it does not respond.

And at volt it only allows pp setting, which is missing for rms.

Also a dB level when in 50 Ohm load output settings. 

Great work everyone. 

[HKJ]

I just redownloaded and tested but still no luck, can you confirm if I am using :updatemodechange: correctly.

You code looks correct, I will have to make a test definition and see what goes wrong, but that will first be tomorrow.

[HKJ]

Made.
It seems that it works with the SDG1062X. 
Limits would have to be changed (e.g. sine from max. 120 MHz to max. 60 MHz for SDG1062X).

What strikes me is that the output ON / Off on channel 2 does not respond (it works on channel 1).
If I activate Output Channel 2 manually on the device, the software even shows me that, just switch from the software, because it does not respond.

And at volt it only allows pp setting, which is missing for rms.

I have a bug. The button controls output 1 not 2, below is the correct code:

#cmdSetup buttons State Output_2
:write: c2:outp


I was a bit lazy with the definition of the SDG and left out a lot of stuff the generator can do.

[MikeLud]

HKJ,

Thanks for looking into.

I just redownloaded and tested but still no luck, can you confirm if I am using :updatemodechange: correctly.

You code looks correct, I will have to make a test definition and see what goes wrong, but that will first be tomorrow.

[klausES]

I didn't want to complain about it. Just as information to change these things when there is time.

[klausES]

...below is the correct code:

#cmdSetup buttons State Output_2
:write: c2:outp
...

Ok it works. 

[Messtechniker]

Next definition file (Ver 0.5) for the R&S HMC 8043 power supply. This time with extended popup functions.  Thanks to HKJ.

Next I will try to implement voltage and current tracking between channels 1 and 2. This SCPI stuff seems to be creeping up on me
And there is a Hameg HMO1022 waiting too.

Time to stop frying three resistors and toddle off to bed now.

[klausES]

Frequency limits for SDG1062X changed.

[HKJ]

V0.36 is up
It has a working :updatemodechange:
The HMC8043 is included (Thanks to Messtechniker)

And a new driver is included, it is designed to handle devices that returns a single ascii line with a value and optional a mode.
It is documented here: http://lygte-info.dk/project/TestControllerConfigDevice2%20UK.html

[tubularnut]

It is documented here: file:///D:/Devlop/lygte-info/project/TestControllerConfigDevice2%20UK.html

Can't see the file, I think it's only on your local drive?

[HKJ]

Oops, link is corrected.

[tubularnut]

Oops, link is corrected.

Thank you 

BTW. Been looking through all the projects on your website, very interesting and impressive 

[Messtechniker]

What's happened between version 032 and 036?

The HMC 8043 definition file of ver. 036 loads
and the popups operate but nothing shows up under "current values".
Entering INST OUT1;MEAS:Curr?;:INST OUT1;MEAS:VOLT?;:INST OUT1;MEAS:POW? in the command line shows the correct values
in the command line box.

Using the HMC 8043 definition file of ver. 036 with
ver. 032 works perfectly. So what's up?

The Keysight 34465A definition file works fully in both versions.

[HKJ]

What's happened between version 032 and 036?

?
Try start in debug and select current value, maybe that can give me a hint.

[MikeLud]

HKJ,

Just tried the new version and :updatemodechange: is working, thanks for add it. I am almost done with the advanced SDM3065X device file. Once the new device file is finish you will have almost 100% remote control of the DMM. After I finish the SDM3065X device file I will work on the other two Siglent DMM files.

V0.36 is up
It has a working :updatemodechange:
The HMC8043 is included (Thanks to Messtechniker)

And a new driver is included, it is designed to handle devices that returns a single ascii line with a value and optional a mode.
It is documented here: http://lygte-info.dk/project/TestControllerConfigDevice2%20UK.html

[HKJ]

Messtechniker try this definition file: http://lygte-info.dk/pic/Projects/TestController/R%26SHMC8043.txt
I change column selection a bit and because you had selectors in the #value lines, the columns was not selected.


MikeLud try remove "Mode" page selection after you #cmdSetup, then you will get the mode below all the pages.

[Marco1971]

Greetings from Italy...after starting in debug mode with my Fluke 89IV connected trough COM1 port...

";; Start thread for: COM1 - Fluke xxx
;; COM1: Set params: 9600
;; COM1: Tx: <ID.> 49 44 0D
;; COM1: Rx: timeout
;; COM1: Tx: <ID.> 49 44 0D
;; COM1: Rx: timeout
;; Stopping thread for: COM1 - Fluke xxx

;; Use "Load devices" page for selecting devices to load. Most devices will only load if they are connected and ready.
"

Marco

[HKJ]

Greetings from Italy...after starting in debug mode with my Fluke 89IV connected trough COM1 port...

";; Start thread for: COM1 - Fluke xxx
;; COM1: Set params: 9600
;; COM1: Tx: <ID.> 49 44 0D
;; COM1: Rx: timeout

I have seen two protocols for Fluke meters, try selecting Fluke287 and do another debug run.