Hi HKJ,
I am using the counter in the single-shot mode, it takes one measurement in each logging interval.
I do not believe that is a good idea, but if it is the only way, you have to use it.
Test controller can have multiple threads fetching data from a device (mostly they will coordinate the reading).
The problem with these Racal-Dana's is that the buffer is cleared after a read-out. So after the first read-out, there is nothing left to fetch for the next read-out...
I am using mouse-over tips (using the :tip: tag ) in the menu’s. For a few tips, I would like to divide a long line of text into 2 short lines (in other words, add a CR/LF halfway the line). I searched your documentation, but could not find the solution. How can I achieve this?
I have not really done anything to support it, but Java has a trick to make multiline:
:tip: <html>Line 1<br>Line 2<br>Line 3
A couple of other html tags are supported (it is a very old version of html Java supports).
This works like a charm. Thank you!
The Racal-Dana 1998 has a twin model, the 1999. Only difference is that the Racal-Dana 1999 does not have the “Ratio B/A” function. And of course it returns “1999” when asked for the model name, instead of “1998”. So I added meta definitions, to make this configuration file also work for the Racal-Dana 1999.
But I do not have a Racal-Dana 1999 for testing, so I can not check if I did the #meta and #metadef statements right. Could you have a look if I did the meta definitions right?
At first glance it looks correct.
If you want to see the final definition you can put this line:
#metaDebug save
below the #metadef tag, this will write the processed definition to disk.
I tested with "#metaDebug save", and the result looks fine.
Thank you, this make me more confident that the definition file will also work with a Racal-Dana 1999.
There is one issue remaining, a “beauty flaw”… (meaning: not essential, but would be nice to solve...)
The Racal-Dana 1998 puts the value of a finished measurement in a read-out buffer. This buffer is cleared when it is read out, or when a new measurement is started.
So, one has to first read-out the result of the previous measurement, and then trigger a new measurement. This is what the configuration file is doing with #askValues , and it works fine.
However, when something else reads out the buffer, (the “Current values” tab, or the “Readout” popup), this readout clears the buffer, so the buffer is empty when the logging routine tries to read out the buffer. This results in missing values in the logging table….
This is especially a problem because the counter is often used with long gate-times of 1 or 20 sec. (To get high resolution). And of course the logging interval has to be a bit longer than the gate-time.
With short gate times, there is time to take an extra measurement, but with these long gate-times there is not…..
First I tried to solve this by storing the measured value in a variable, which is subsequently read out by TestController. However, the problem is that TestController uses the same read-out command (#askValues) for the logging and the other read-out functions. And for the logging it is necessary to trigger the next measurement after the read-out with this command, which of course spoils it when used for the other read-out functions….
Is there a way around this?
A solution could be to use the values in the table for the other TestController read-outs (At the moment this only works when the table is updated rather fast, not with these slow logging intervals)
For now the solution is simply not to use the current values tab, or the Readout popup while logging...
Regards, Gertjan.