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

[KungFuJosh]

Holy crap, Batman! I just clicked the Minimum column in Scales for chart by mistake...I had no idea that TC had an option for Center/Span in manual range settings. That's awesome! 

[KungFuJosh]

I ran into a problem. I recall reading that TC only supports 1 GPIB device at a time. However, having GPIB even listed in the GPIB section makes it so I can't use my SMIQ06B via USB serial port.

I removed the Proligix USB GPIB from the GPIB list, and the SMIQ works again.

Is this a limitation? I wanted to use both devices together (SMIQ + 53132A).

By changing the line:
#port     com 5025 LXI GPIB
To:
#port     com

Both devices work together now. Does that option existing disable the serial port from working too?

Anyway, if somebody has this issue, there's the workaround. I don't want to change the SMIQ definition file though, since GPIB is still a valid option.

Thanks,
Josh

[KungFuJosh]

Don't blame me for that 1000M 😉😉

And I will not blame your for this one, I first step to next SI prefix if the value is above 1000, but even a very small amount above will get your the next prefix. If you really don't like it you can specify something like 1.00000001G, but personally I prefer the 1000M

Is it possible for you to make an option in TC that decides whether SI steps at 1000 or the next value above 1000? I'm almost done with the definition for the 53132A counter, which has 50Ω or 1MΩ input. I really don't like the 1000k there, and there's no way for me to change the value.

Alternatively, you could make a variant of SI that does that, but I assume that would be more effort.

Thanks,
Josh

[KungFuJosh]

One more question.

Is it possible to change the word Set? In the attached case, I would prefer it said Save or Recall instead of Set.



Thanks,
Josh

[jmurray]

I have the handle set: #handle   53132A
But TC abbreviates it to: 132A

Can I disable that somehow? I know adding something in front will preserve it, but I'd prefer to keep it simple...just not that simple.

Thanks,
Josh

From what I can recall, handles always need to start with a letter. Which is why it's dropping the first two numbers.

[jmurray]

Hi HKJ,

Another oddball UI question:

Is there any possibility we could see the implementation of a third argument for combobox/comboboxhot list items?
It would be great to have an optional expression for each list item that determines whether or not it is displayed in the list.

Otherwise it seems there's a need for 31x31 combobox and selector entries!

I've attached an example of what I'm thinking of:

[HKJ]

I have the handle set: #handle   53132A
But TC abbreviates it to: 132A

Can I disable that somehow? I know adding something in front will preserve it, but I'd prefer to keep it simple...just not that simple.

I have no idea why the handle is shorted.

[HKJ]

Holy crap, Batman! I just clicked the Minimum column in Scales for chart by mistake...I had no idea that TC had an option for Center/Span in manual range settings. That's awesome! 

Do I?
I had forgotten that, but year clicking the heading will switch between min/max and center/span.

[HKJ]

I ran into a problem. I recall reading that TC only supports 1 GPIB device at a time. However, having GPIB even listed in the GPIB section makes it so I can't use my SMIQ06B via USB serial port.

I removed the Proligix USB GPIB from the GPIB list, and the SMIQ works again.

Is this a limitation? I wanted to use both devices together (SMIQ + 53132A).

By changing the line:
#port     com 5025 LXI GPIB
To:
#port     com

Both devices work together now. Does that option existing disable the serial port from working too?

Anyway, if somebody has this issue, there's the workaround. I don't want to change the SMIQ definition file though, since GPIB is still a valid option.

That is not supposed to affect anything and you can have multiple GPIB devices, but each one can only have one device connected.

TC try to reserve port for GPIB, before reserving ports for regular devices, could that be the reason?

[HKJ]

Is it possible for you to make an option in TC that decides whether SI steps at 1000 or the next value above 1000? I'm almost done with the definition for the 53132A counter, which has 50Ω or 1MΩ input. I really don't like the 1000k there, and there's no way for me to change the value.

Alternatively, you could make a variant of SI that does that, but I assume that would be more effort.

It is a rather minor detail and I do not really like to modify it.

[HKJ]

One more question.

Is it possible to change the word Set? In the attached case, I would prefer it said Save or Recall instead of Set.

Yes:

:buttontext: Text for a "Set" button
https://lygte-info.dk/project/TestControllerConfigDevice%20UK.html#Tags

[HKJ]

Hi HKJ,

Another oddball UI question:

Is there any possibility we could see the implementation of a third argument for combobox/comboboxhot list items?
It would be great to have an optional expression for each list item that determines whether or not it is displayed in the list.

Otherwise it seems there's a need for 31x31 combobox and selector entries!

I've attached an example of what I'm thinking of:

I can see what you want, but I am not sure it is feasible to modify the combobox.

There is another (undocumented) combobox called comboboxfill and comboboxfillhot, they uses a command from a :read: tag to fill the box. This may not directly fix it, but with #scpiCmd name? #pgm# you can make your own local SCPI command that returns what you want filled into the combobox. I recommand the #pgm# version because it means you can use programming to build your answer.
You can then list the control on :update: tags when you want the list updated.

And a warning: Do not call other scpiCmd from the programming, it will give issues.

[KungFuJosh]

I ran into a problem. I recall reading that TC only supports 1 GPIB device at a time. However, having GPIB even listed in the GPIB section makes it so I can't use my SMIQ06B via USB serial port.

I removed the Proligix USB GPIB from the GPIB list, and the SMIQ works again.

Is this a limitation? I wanted to use both devices together (SMIQ + 53132A).

By changing the line:
#port     com 5025 LXI GPIB
To:
#port     com

Both devices work together now. Does that option existing disable the serial port from working too?

Anyway, if somebody has this issue, there's the workaround. I don't want to change the SMIQ definition file though, since GPIB is still a valid option.

That is not supposed to affect anything and you can have multiple GPIB devices, but each one can only have one device connected.

TC try to reserve port for GPIB, before reserving ports for regular devices, could that be the reason?

Do you want me to send you a debug log or something? #port com works fine, and I'm only using the SMIQ on virtual serial port COM1. If I have the rest included (5025 LXI GPIB), it fails as long as there's a GPIB adapter defined for the other device.

Thanks,
Josh

[HKJ]

I ran into a problem. I recall reading that TC only supports 1 GPIB device at a time. However, having GPIB even listed in the GPIB section makes it so I can't use my SMIQ06B via USB serial port.

I removed the Proligix USB GPIB from the GPIB list, and the SMIQ works again.

Is this a limitation? I wanted to use both devices together (SMIQ + 53132A).

By changing the line:
#port     com 5025 LXI GPIB
To:
#port     com

Both devices work together now. Does that option existing disable the serial port from working too?

Anyway, if somebody has this issue, there's the workaround. I don't want to change the SMIQ definition file though, since GPIB is still a valid option.

That is not supposed to affect anything and you can have multiple GPIB devices, but each one can only have one device connected.

TC try to reserve port for GPIB, before reserving ports for regular devices, could that be the reason?

Do you want me to send you a debug log or something? #port com works fine, and I'm only using the SMIQ on virtual serial port COM1. If I have the rest included (5025 LXI GPIB), it fails as long as there's a GPIB adapter defined for the other device.

A debug log it working and one of it failing may be useful.

[KungFuJosh]

A debug log it working and one of it failing may be useful.

You're right, I don't think it says anything useful, but I'll get it to you anyway.

ETA: Never mind. I can't get it to stop working anymore. I changed the line back to #port     com 5025 LXI GPIB and it still works fine. 

So, yeah, definitely nothing useful. 🤣

[KungFuJosh]

From what I can recall, handles always need to start with a letter. Which is why it's dropping the first two numbers.

Where did you read that? It's true, that using a letter gets it to not cut off any numbers. However, adding two numbers works better because then it just shows the correct number.

For example, 5553132A shows 53132A. Still odd though.

I have no idea why the handle is shorted.

It seems this is a common issue for HPAK handles. For example, 34465A is KS34465A or K34465A. If I removed the prefix letters, then it shows 465A instead of 34465A.

Thanks,
Josh

[HKJ]

From what I can recall, handles always need to start with a letter. Which is why it's dropping the first two numbers.

Where did you read that? It's true, that using a letter gets it to not cut off any numbers. However, adding two numbers works better because then it just shows the correct number.

He is right that handles are supposed to start with a letter, this is because they are used to name variables and they must start with a letter, not a number. BUT TC will sanitize a handle name before using it for a variable, i.e. all leading number are stripped, but that is only done for variable use.
I wonder if it is something in my initial resolving of handles that does it. The resolving is adjusting handles to allow multiple devices with same handle to be loaded. It adds a two digit number to the handle and is not supposed to do anything else, but I wonder.

Matching var names (Due to the sanitizing) will not be detected by TC and will lead to wrong results!

[KungFuJosh]

Okay, well, I have a new toy to write a driver for (CNT-90 series), so here's the 532XXA driver (removed), and a minor update to the SMIQ driver.

Thanks,
Josh

[jmurray]

Hi HKJ,

Another oddball UI question:

Is there any possibility we could see the implementation of a third argument for combobox/comboboxhot list items?
It would be great to have an optional expression for each list item that determines whether or not it is displayed in the list.

Otherwise it seems there's a need for 31x31 combobox and selector entries!

I've attached an example of what I'm thinking of:

I can see what you want, but I am not sure it is feasible to modify the combobox.

There is another (undocumented) combobox called comboboxfill and comboboxfillhot, they uses a command from a :read: tag to fill the box. This may not directly fix it, but with #scpiCmd name? #pgm# you can make your own local SCPI command that returns what you want filled into the combobox. I recommand the #pgm# version because it means you can use programming to build your answer.
You can then list the control on :update: tags when you want the list updated.

That sounds promising. Presumably it will fill the box with a list of items that are separated by comma or space.
However, if it uses a :read: tag to fill the box, how does it know which item from the list to pre-select on a read? Or is that not available for this type?

And a warning: Do not call other scpiCmd from the programming, it will give issues.

I should ask - is this a new development? I have a device definition (nearly finished, but have had other priorities) that does exactly this, but works fine. I haven't tested it with the very latest version of TC.

Example:

Code: [Select]

;--- Generic function to parse string of existing settings into array, update individual array element, and parse back to string

#scpiCmd parseArray #pgm#
var existingSettings = array(deviceRead(handle, cmd));
existingSettings[index] = newValue;
var newSettings = "";
var i = 0;
for i = 0 to size(existingSettings) - 2 do
newSettings = newSettings + existingSettings[i] + " ";
endfor;
newSettings = newSettings + existingSettings[size(existingSettings) - 1];

;--- Defined commands/functions to set individual fixed settings

#scpiCmd SET:FIX:TEMP #pgm# (value)
var newValue=limit(value, MinTemperature, MaxTemperature);
index=0;
var cmd="GET:FIX?";
deviceRead("", "parseArray");
deviceRead(handle, "SET:FIX? " + newSettings)

[KungFuJosh]

I mostly finished the CNT-90 definition file (removed, not final). However, I'd like to add support for the Fluke and Tek variants. Can anybody with a PM6690 or FCA3000 please share the *IDN? response from their counters?

The CNT-90 file is mostly the same as the 531XXA file with a few small differences (should work in both native or compatible mode). I made an updated version of the 53132A file (attached, maybe final) with Gate options added in Setup.

ETA: Outdated attachment removed.

Thanks,
Josh

[HKJ]

That sounds promising. Presumably it will fill the box with a list of items that are separated by comma or space.
However, if it uses a :read: tag to fill the box, how does it know which item from the list to pre-select on a read? Or is that not available for this type?

I remembered wrong, :read: work as usual, the SCPI commands to fill replaces the list.
Here is an example from the sound card driver (That was the reason I added these items):

#cmdSetup comboboxFillHot Device
:read: audiodevice?
:write: audiodevice
:update: Bits Sample_rate
audiodevices?

And a warning: Do not call other scpiCmd from the programming, it will give issues.

I should ask - is this a new development? I have a device definition (nearly finished, but have had other priorities) that does exactly this, but works fine. I haven't tested it with the very latest version of TC.

No, the issue is that each device only has one programming environment for #scpiCmd and it cannot handle two execution threads, only one. And i misspoke a bit, it is the #pgm# items that are hands off, not all SCPI commands.

[HKJ]

Okay, well, I have a new toy to write a driver for (CNT-90 series), so here's the 532XXA driver (not final), and a minor update to the SMIQ driver.

They will all be included, thanks.

[KungFuJosh]

Can some people test this out? Added support for Tek FCA3000/FCA3100, and Fluke PM6690.

Please let me know if there are variations besides these:
FLUKE, PM6690,
TEKTRONIX, FCA3000,
TEKTRONIX, FCA3100,

ETA: This is still not final. I need to add readings for the other modes I added, currently only supports Frequency (same with 531XXA).

ETA: Outdated attachment removed.

Thanks,
Josh

[KungFuJosh]

These are both hopefully final. All modes function as they're supposed to now, including correctly updating current values. I tested on the 53132A and CNT-90XL. I'd appreciate if others could test too.

Thanks,
Josh



PS. I don't know if it's expected behavior or not, but I needed:
#askModeMathFormat unQuote(replace(replace(value," ","-"),",","-"))

For both devices the mode responses had spaces and commas. The spaces made the mode changes fail, even though they had underscores in the #values at the time.

I removed the commas because I assumed they would interfere with the askValues string.

[HKJ]

These are both hopefully final. All modes function as they're supposed to now, including correctly updating current values. I tested on the 53132A and CNT-90XL. I'd appreciate if others could test too.

I have updated them (Thanks)

PS. I don't know if it's expected behavior or not, but I needed:
#askModeMathFormat unQuote(replace(replace(value," ","-"),",","-"))

For both devices the mode responses had spaces and commas. The spaces made the mode changes fail, even though they had underscores in the #values at the time.

I removed the commas because I assumed they would interfere with the askValues string.

Spaces and commas tend to split the modes into separate modes, TC can be in multiple modes at a time.
I.e.:

"hi you" will register as two modes active at the same time: hi and you
"hi-you" will register as one mode: hi-you