Program that can log/control many multimeters and other devices.

[HKJ]

Is there a way to get that from a SCPI command? If I could use stuff like :CHAN1:STATe == ON that would work.

You can do that, but I will not recommend it due to performance reasons.

Either that or if you made it work with defined variables (:setvar: CH1 ON etc).

I have been thinking about that and may make it.

[KungFuJosh]

Is there a way to get that from a SCPI command? If I could use stuff like :CHAN1:STATe == ON that would work.

You can do that, but I will not recommend it due to performance reasons.

Either that or if you made it work with defined variables (:setvar: CH1 ON etc).

I have been thinking about that and may make it.

So, in your opinion, it seems the latter option is the best option for me. I think I agree.

Thanks,
Josh

[KungFuJosh]

My definition is ready for when the advCombobox supports set variables. I set it up so a variable called CHsOn has the 4 channels in sequence with Y or N values.

Activating or deactivating channels updates the variable.

Then I can set (for example) the maximum memory depth:
327.2M is CHsOn==YNNN
164M is CHsOn==NYNN || CHsOn==NNYN || CHsOn==NNNY
82M is CHsOn==NNYY || CHsOn==YYYN || CHsOn==YYNY || CHsOn==YNYY || CHsOn==NYYY

Thanks,
Josh

[flash2b]

Another update to TC, now v2.84

Params is: label foregroundcolor backgroundcolor expression icon command

Use attached device with these settings in the dummy driver to test it:

This new 2.84 version does not log (I can setup logging, but TC hangs) when I have a setup menu open or a setup menu opened and was closed. Version 2.77 does not have this problem.

[HKJ]

This new 2.84 version does not log (I can setup logging, but TC hangs) when I have a setup menu open or a setup menu opened and was closed. Version 2.77 does not have this problem.

I do not see this problem and I have not been in that part of the code either.

[flash2b]

This new 2.84 version does not log (I can setup logging, but TC hangs) when I have a setup menu open or a setup menu opened and was closed. Version 2.77 does not have this problem.

I do not see this problem and I have not been in that part of the code either.

But I am not kidding, it just hangs.... nothing on the debug log. The log button also does not get red. I see that TC does the internal askMode but then it hangs.

Java 8u461 64 bit on Windows 10.

What can I do to identify the problem since everything is ok on v2.77 for me. Same definition. Please help....

[HKJ]

But I am not kidding, it just hangs.... nothing on the debug log. The log button also does not get red.

I do not like that kind of bug, they are mostly impossible to find.
I am testing with the Dummy I published before, but I have extended it a bit and I am also testing with R&S HMC8043 and do not see any issues.

[flash2b]

Tested with my Hameg and Yokogawa defintions, same problem.

When I start logging right away, no problem. But when I have invoked the setup menu (open or open and then close) logging does not work.

I noticed that starting logging right away, the button gets RED color immediately, while when a setup menu is open it takes a few seconds (on 2.77).

[HKJ]

Tested with my Hameg and Yokogawa defintions, same problem.

I can upload the current TC and Dummy definition and you can test with them also.

[flash2b]

Yes please

[HKJ]

Yes please

This version of Dummy can return a value using the read command, i.e. logging is a horizontal line.
The TC download is updated.

[flash2b]

Driver does not load: ;; Dummy Device "Dummy,Dummy" do not match answer: "null"

Code: [Select]

Starting
;; jSerialComm version: 2.11.2
Could not find advcomboboxhot
;; Start thread for: Dummy - TCTest
Tx input: *IDN?
Rx after processing: null
;; Dummy Device "Dummy,Dummy" do not match answer: "null"
;; Stopping thread for: Dummy - TCTest

[HKJ]

Driver does not load: ;; Dummy Device "Dummy,Dummy" do not match answer: "null"

Try once more, I do have a issue with initially creating the definition file.

[flash2b]

Same, and I am using v2.85 which also hangs the logging when a setup menu has been invoked.

[HKJ]

Same, and I am using v2.85 which also hangs the logging when a setup menu has been invoked.

It creates attached file in ...\Documents\Testcontroller\Settings

I suspect something may be wrong with your Java

[flash2b]

It did not create that file. If I copy the file in that directory, the same problem exists.

I just reinstalled Java 1h ago...

[HKJ]

It did not create that file. If I copy the file in that directory, the same problem exists.

I just reinstalled Java 1h ago...

I do not know what to say or do, I have not had any problems, neither running the .jar file standalone or in my development system.

[flash2b]

Well I guess I am stuck on v2.77 for now 

v2.84 and v2.85 do not work for me. Is there a location where I can download 2.78 true 2.83 so I can determine where the problem occurred the first ?

[HKJ]

Well I guess I am stuck on v2.77 for now 

v2.84 and v2.85 do not work for me. Is there a location where I can download 2.78 true 2.83 so I can determine where the problem occurred the first ?

I do not keep the different .jar versions, I only keep the source for all full releases.

[flash2b]

I have retested it with the SDG2000x definition, and there is no problem there. So it may be related to the ascii driver only.

If i use my Hameg HM8112 definition, which is very simple. And if I type askMode? , range? and intTime? on the TC command line directly, logging is not affected. Well the setup menu uses only these 3 scpiCmd's so I am puzzled.

If i invoke the Log button on TC, it will become Stop Log in red straight away. This is different when a setup menu from an ascii definition is opened/was opened. It always takes 1-2 seconds, it was always that way. It does not happen with the SDG2000x definition which is not ascii.

[HKJ]

I have retested it with the SDG2000x definition, and there is no problem there. So it may be related to the ascii driver only.

If i use my Hameg HM8112 definition, which is very simple. And if I type askMode? , range? and intTime? on the TC command line directly, logging is not affected. Well the setup menu uses only these 3 scpiCmd's so I am puzzled.

If i invoke the Log button on TC, it will become Stop Log in red straight away. This is different when a setup menu from an ascii definition is opened/was opened. It always takes 1-2 seconds, it was always that way. It does not happen with the SDG2000x definition which is not ascii.

You can try moving the dummy definition to the ascii base, if it locks there is something I can look for.

[HKJ]

My definition is ready for when the advCombobox supports set variables. I set it up so a variable called CHsOn has the 4 channels in sequence with Y or N values.

Activating or deactivating channels updates the variable.

Then I can set (for example) the maximum memory depth:
327.2M is CHsOn==YNNN
164M is CHsOn==NYNN || CHsOn==NNYN || CHsOn==NNNY
82M is CHsOn==NNYY || CHsOn==YYYN || CHsOn==YYNY || CHsOn==YNYY || CHsOn==NYYY

The current test version includes #scpiCmd vars and advComboBoxHot, use return0(printLog(getVarList(2))) to list them (0=Global, 1=local, 2=parent). I put the other script parser in as parent that prevent any issues if they are used concurrent.
You must use: CHsOn=="YNNN"
But why not: inList(CHsOn,"NNYY YYYN YYNY YNYY NYYY")

[flash2b]

Change SCPIx to ascii in your dummy driver

Code: [Select]

;; jSerialComm version: 2.11.2
;; Start thread for: Dummy - TCTest
;; Dummy: Tx <pgm>
;; Dummy: Script start
;; Dummy: Script end <>
;; Found TCTest on Dummy

Loaded the driver !! It did not create the settings file.

The dummy setup menu also works, and does not influence the logging.

I hope others will also retest their definitions or will shed some light on what needs to be changed.

[HKJ]

Change SCPIx to ascii in your dummy driver

Code: [Select]

;; jSerialComm version: 2.11.2
;; Start thread for: Dummy - TCTest
;; Dummy: Tx <pgm>
;; Dummy: Script start
;; Dummy: Script end <>
;; Found TCTest on Dummy

Loaded the driver !! It did not create the settings file.

The dummy setup menu also works, and does not influence the logging.

This means I do not know where to look, the ascii driver works.

You may even be able to redefine the dummy so it matches your device, starting usually only requires a few commands.
Note: You can change the configuration file for dummy, by specifying a name in the address field on the load page.

[flash2b]

Well... that is very disappointing. Since it worked in v2.77 and now I feel it is my fault that is doesn't anymore.......