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

[Kurt_!]

I already had this code in there...
I'll keep trying...
Thanks

[KungFuJosh]

I already had this code in there...
I'll keep trying...
Thanks

What did you use for the model info? Paste the code here for review. Also run TestController in debug mode and share the log of it starting up.

[HKJ]

Josh is not correct in the driver to use, because the device streams data, that put some serious limits on what drivers can be used.

The easiest one to use is the single value https://lygte-info.dk/project/TestControllerConfigDevice2%20UK.html#Single_value driver. It is not designed to control the device, only to show the data. I believe you might still get away with defining/sending commands to the device, but it is not something that is really supported.

If the device had required a command to read the data the ascii driver would be perfect for it and fairly easy to implement.

[Gertjan]

Unfortunately, I haven't gotten it to work yet.
It requires a bit of skill.
The device only accepts specific commands.
(Only for FA.3) It constantly outputs data (see image).

Hi Kurt,

When trying to figure out the command set of this counter, maybe an important clue is in the start of the posted manual:

Key Features
    .......
5. With USB port, connect to PC, data format compact version of HP53131 mode

So, start reading the HP 53131A manual.    (HP 53131A is an industry standard)

regards, Gertjan

[KungFuJosh]

Josh is not correct in the driver to use, because the device streams data, that put some serious limits on what drivers can be used.

I assume that ascii is correct because the manual states:

4.5 Config command
Default baud rate is 9600bps, ascii encoding
$

The manual also gives examples of other commands including: $S* Read statistics data

So there are read and mode commands available, hence the suggestion for creating scpiCmd to control everything:

Code: [Select]

$R* Press RST key, return KEY RST ROK<CR><LF>
$M* Press MODE key, return KEY MODE MOK<CR><LF>
$G* Press GATE key, return KEY GATE GOK<CR><LF>
$E3434* Open high precision mode
$E3535* Close high precision mode, all input frequency is 8 digits/second
$CXX* XX:0-63, setting LCD contrast, save in EEPROM,
return SET LCD CONTCOK<CR><LF>
$BXXXXX* setting baudrate, XXXXX 00480, 00960, 01920, 03840, 05760, 11520, Power off
without save, return BOK<CR><LF>
$S* Read statistics data
The following instructions are powered off and saved:
$E2020* Power up select CH1 frequency mode
$E2121* Power up select CH1 frequency statistics mode
$E2222* Power up select CH2 frequency mode
$E2323* Power up select CH2 frequency statistics mode
$E3030* CH1 select 50R
$E3131* CH1 select 1MOHM
$E3232* BEEP ON.
$E3333* BEEP OFF
$E3636* Open CH1 LPF
$E3737* Close CH1 LPF
$E4040* Select CH1=50R,input 10MHz, 0dBm,calibration of power meter, used with $E4141*
command
$E4141* Select CH1=50R,input 10MHz, -20dBm, calibration of power meter
Thanks,
Josh

[KungFuJosh]

So, start reading the HP 53131A manual.    (HP 53131A is an industry standard)

I already made a driver for the 53131A / 53132A. That would be convenient if there's some overlap between the devices.

Thanks,
Josh

[KungFuJosh]

The function and scpiCmds all work, the problem is enabling the function using a scpiCmd, independent of the scpiCmd calling the function. I made the addFuncGlobal a #pgm# command:
#scpiCmd EnablegetMeasUnit #pgm#
addFuncGlobal("getMeasUnit","""


If I manually enable that, it works fine. The problem is, I don't know how to enable the global function automatically.

For example, initCmd does not work:
#initCmd MeasDefault;EnablegetMeasUnit

It shows the command execution in the log, but the global function doesn't work until I manually run the EnablegetMeasUnit cmd. After I manually execute that, everything works as it should.

I will have to do some testing on that.

Have you had a chance to check on this? If it won't work, I will need to revert to the larger driver file.

On the other hand, this gave me an idea for another feature request.

Here's the idea: like the #initCmd, but for when you open the #cmdSetup, you could have something like #cmdSetupInit to run commands either before or after the #cmdSetup popup is synchronized. Ideally, before or after could be a tag like :loadbefore: or :loadafter:.

Thanks,
Josh

[HKJ]

I assume that ascii is correct because the manual states:

The issue is that it streams data, not all drivers can handle that.
You can see supported drivers here: https://lygte-info.dk/project/TestControllerConfigDevice%20UK.html#Control_toggleButton

I check out my new "Dummy" driver by trying to implement the SingleValue protocol for this counter, it is rather simple:

Code: [Select]

#idString Wuton, Wuton Fa-3/G6
#name Wuton Fa-3/G6
#handle FA3
#port com
#driver SingleValue

#value Frequency Hz SI FA


[KungFuJosh]

I check out my new "Dummy" driver by trying to implement the SingleValue protocol for this counter, it is rather simple:

Code: [Select]

#idString Wuton, Wuton Fa-3/G6
#name Wuton Fa-3/G6
#handle FA3
#port com
#driver SingleValue

#value Frequency Hz SI FA


That's actually kinda awesome for simple devices. If you can still setup #cmdMode buttons or #cmdSetup to work with that, then that's even better.

Thanks,
Josh

[HKJ]

Have you had a chance to check on this? If it won't work, I will need to revert to the larger driver file.

No, I have sort of worked on my Dummy driver.

Here's the idea: like the #initCmd, but for when you open the #cmdSetup, you could have something like #cmdSetupInit to run commands either before or after the #cmdSetup popup is synchronized. Ideally, before or after could be a tag like :loadbefore: or :loadafter:.

Maybe.

[HKJ]

That's actually kinda awesome for simple devices. If you can still setup #cmdMode buttons or #cmdSetup to work with that, then that's even better.

It is supposed to be simple, but it do not allow for sending commands.

But notice the two letters FA, if they change for different mode, it is possible to define multiple columns.

[KungFuJosh]

That's actually kinda awesome for simple devices. If you can still setup #cmdMode buttons or #cmdSetup to work with that, then that's even better.

It is supposed to be simple, but it do not allow for sending commands.

But notice the two letters FA, if they change for different mode, it is possible to define multiple columns.

It sounds like a good fallback, but if he can get it to work with ascii driver, he'll have a lot more control of the device...vs. no control of the device.

[HKJ]

It sounds like a good fallback, but if he can get it to work with ascii driver, he'll have a lot more control of the device...vs. no control of the device.

Not the ascii driver, it do not support streaming, but asciiBlock do.

[KungFuJosh]

It sounds like a good fallback, but if he can get it to work with ascii driver, he'll have a lot more control of the device...vs. no control of the device.

Not the ascii driver, it do not support streaming, but asciiBlock do.

Cool! There's more driver options than I was aware of.

It sounds like asciiBlock is the way to go.

[HKJ]

Cool! There's more driver options than I was aware of.

There is 9 official drivers, it varies what mode and what protocols they support.

[HKJ]

If somebody wants to play with the Dummy comm driver to give ideas, I can upload a new beta (The one in the current beta is missing the user interface, it is partially implemented now).
For now it can be used with all drivers that communicates in ascii, not with binary communication.

It is mostly useful to test aspect of TC definitions/functions and to implement simple drivers without the actual device. Both things I do regularly.

[Kurt_!]

I've made a bit of progress.
It's already logging.
But I have a picture. Are there still problems?
How do I display the frequency?



#idString BG7TBL,FA-3 6GH+
#name BG7TBL FA-3 6GH+
#handle FA-3 6GH+
#port com3
#baudrate 9600N81
#driver Ascii
#askValues Frequenz

Do I need a virtual frequency generator......
 

[HKJ]

I've made a bit of progress.
It's already logging.
But I have a picture. Are there still problems?
How do I display the frequency?

com3 is not a valid port specification, it is only com and then you put com3 in the address field in TC

Why don't you try the code I posted a bit earlier?

[HKJ]

Unfortunately not so good

The code I posted needs to go into a file in the devices directory (It is in ...\documents\TestController)

[Kurt_!]

I was too quick to post.
It's working now.
I changed the name...
I still need to test something.
Thanks




Ps.:It's a problem, unfortunately, I often have other things to do. That's where errors creep in.

[HKJ]

I was too quick to post.
It's working now.
I changed the name...
I still need to test something.

I wonder if the two letters before the value changes according to mode, if that is the case a couple more columns needs to be defined for the values (TC will automatic select the correct one).

[flash2b]

Updated Yokogawa 7551, 7552, 7561, 7562 and 7563 definition file.

I have added all the offered Math functions that these devices offer. Also there are some bug fixes in this updated definition compared to 1.00.



HKJ, please update the definition with the one below for the next release of the wonderful TestController.

[ Specified attachment is not available ]

[HKJ]

Updated Yokogawa 7551, 7552, 7561, 7562 and 7563 definition file.

I have added all the offered Math functions that these devices offer. Also there are some bug fixes in this updated definition compared to 1.00.

HKJ, please update the definition with the one below for the next release of the wonderful TestController.

I have updated the file, it will be included, thanks.

[Kurt_!]

I was too quick to post.
It's working now.
I changed the name...
I still need to test something.

I wonder if the two letters before the value changes according to mode, if that is the case a couple more columns needs to be defined for the values (TC will automatic select the correct one).

She doesn't know exactly what you mean...
Unfortunately, it's still pretty rough.
Maybe I haven't found everything yet.
I don't have that much time or inclination after all...
Unfortunately, no precise frequency display and diagram?
It would be great if someone could add something...

[HKJ]

She doesn't know exactly what you mean...
Unfortunately, it's still pretty rough.
Maybe I haven't found everything yet.

Before the frequency there is the letters FA, maybe they change to FB if you use the second input?
I may also be able to show period time, my guess would be PA and PB for that.
But the above is only a guess, I would like to know, then I can include the definition with TC