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

[flash2b]

Logging that way is no such fun  , the fun starts when using the Param Sweeper when you sweep through the full frequency range of your LCR meter !

Like this

[mawyatt]

@mawyatt,

Check this setting...

Thanks,
Josh

Finally got back to this for a few minutes but need to run soon.

Got our old PC Laptop with Win 10 and installed TC, and had to instal Java also. Getting the same behavior as with Mac???

Installed a 34465A and it's working fine, so something to do with IM3536 interface.

BTW our Gateway is OFF, which shouldn't make a difference. We can "see" the IM3536 and read back some values, but can't change anything and when attempting the 4 parameters change, each goes to Off, none of the other function seem to work either.

Any ideas what might be causing this??

Best

[HKJ]

Finally got back to this for a few minutes but need to run soon.

Got our old PC Laptop with Win 10 and installed TC, and had to instal Java also. Getting the same behavior as with Mac???

Installed a 34465A and it's working fine, so something to do with IM3536 interface.

BTW our Gateway is OFF, which shouldn't make a difference. We can "see" the IM3536 and read back some values, but can't change anything and when attempting the 4 parameters change, each goes to Off, none of the other function seem to work either.

Any ideas what might be causing this??

When having issues, try start TC with the debug bat file, it might give some useful information and it can be posted here.

[mawyatt]

When having issues, try start TC with the debug bat file, it might give some useful information and it can be posted here.

I did so, and can see when the IN3536 is returning 5 parameters instead of 4, the leading one is 0, and followed by the proper values select on the instrument. This explains the downshift of the measured parameters. Not sure my the IM3536 is returning 5 results with a leading 0 tho.

Edit: Just tried with a USB instead of LAN connection, still have the leading extra 0, however the other functions appear to be changeable and working OK? So seem some part of this is due to LAN?

Need to leave for awhile, but will get back to this soon.

Best

[KungFuJosh]

When having issues, try start TC with the debug bat file, it might give some useful information and it can be posted here.

I did so, and can see when the IN3536 is returning 5 parameters instead of 4, the leading one is 0, and followed by the proper values select on the instrument. This explains the downshift of the measured parameters. Not sure my the IM3536 is returning 5 results with a leading 0 tho.

Edit: Just tried with a USB instead of LAN connection, still have the leading extra 0, however the other functions appear to be changeable and working OK? So seem some part of this is due to LAN?

Need to leave for awhile, but will get back to this soon.

Best

That is odd behavior. @Martin72 has his IM3536-10 working fine over LAN.

Are you running the latest firmware on yours?

Do you have some custom configuration running on your IM3536?

On the IM3536, set all 4 parameters off, then select 1 parameter at a time (with all others off) and see what response you get from :MEAS?.

Thanks,
Josh

[mawyatt]

That is odd behavior. @Martin72 has his IM3536-10 working fine over LAN.

Are you running the latest firmware on yours?

Do you have some custom configuration running on your IM3536?

On the IM3536, set all 4 parameters off, then select 1 parameter at a time (with all others off) and see what response you get from :MEAS?.

Thanks,
Josh

We have the latest firmware V1.09.

Getting single values with :MEAS? always returns a leading 0, wether any Parameters are Active or Off. If Parameters are Active then always a leading 0 is returned. If in USB mode, then the 4 Parameters can be changed but always returns a leading 0, LAN sets Parameters to "Off" when addressed.

Indeed puzzling

BTW this is with a PC not the Mac.

Best

[KungFuJosh]

We have the latest firmware V1.09.

Getting single values with :MEAS? always returns a leading 0, wether any Parameters are Active or Off. If Parameters are Active then always a leading 0 is returned. If in USB mode, then the 4 Parameters can be changed but always returns a leading 0, LAN sets Parameters to "Off" when addressed.

Indeed puzzling

BTW this is with a PC not the Mac.

Best

Mac or PC shouldn't matter. Your device won't be aware of the OS when it sends a response to a query.

What is your :MODE? response?

My guess is that you have something extra active.

Do you have any other functions active, like the Comparator or BIN?

You can try *RST;:PRES from the command tab prompt and see if that clears it out. I considered having that be defaulted in the definition, but I wouldn't like it, as I tend to setup my experiment, or want to go back to it whether or not I'm using TC.

Thanks,
Josh

[BigBoss]

I tried the software a bit with my Fluke 45, but it doesn't recognise the multimeter.
I can talk to my Fluke 45 via PuTTY. It responds to commands on RS-232. Did I do something wrong?

[KungFuJosh]

I tried the software a bit with my Fluke 45, but it doesn't recognise the multimeter.
I can talk to my Fluke 45 via PuTTY. It responds to commands on RS-232. Did I do something wrong?

From the definition file it says:

Configuration must be 9600N81 and echo = off for communication to work.

[mawyatt]

We have the latest firmware V1.09.

Getting single values with :MEAS? always returns a leading 0, wether any Parameters are Active or Off. If Parameters are Active then always a leading 0 is returned. If in USB mode, then the 4 Parameters can be changed but always returns a leading 0, LAN sets Parameters to "Off" when addressed.

Indeed puzzling

BTW this is with a PC not the Mac.

Best

Mac or PC shouldn't matter. Your device won't be aware of the OS when it sends a response to a query.

What is your :MODE? response?

My guess is that you have something extra active.

Do you have any other functions active, like the Comparator or BIN?

You can try *RST;:PRES from the command tab prompt and see if that clears it out. I considered having that be defaulted in the definition, but I wouldn't like it, as I tend to setup my experiment, or want to go back to it whether or not I'm using TC.

Thanks,
Josh

We are in LCR Mode. LAN is doing something and highly intermittent, then seems to also mess up the USB connection. Just did a power down and then a RST and CLR on Power Up which seems to help so far. USB seems to allow Parameter Adjustment almost every time, LAN doesn't. We had this IM3536 working well under USB and RS232 a few years ago using Python, so suspecting something associated with LAN. With Python we always did a RST and CLR before doing anything else, so probably should follow that every time we switch from USB to LAN and back, maybe even Power Down/Up until we get this misbehavior resolved.

Anyway, makes some progress...Thanks for the help!!

Best

[KungFuJosh]

Getting single values with :MEAS? always returns a leading 0, wether any Parameters are Active or Off. If Parameters are Active then always a leading 0 is returned. If in USB mode, then the 4 Parameters can be changed but always returns a leading 0, LAN sets Parameters to "Off" when addressed.

Do you still get a leading 0 with all parameters disabled?

We are in LCR Mode. LAN is doing something and highly intermittent, then seems to also mess up the USB connection. Just did a power down and then a RST and CLR on Power Up which seems to help so far. USB seems to allow Parameter Adjustment almost every time, LAN doesn't. We had this IM3536 working well under USB and RS232 a few years ago using Python, so suspecting something associated with LAN. With Python we always did a RST and CLR before doing anything else, so probably should follow that every time we switch from USB to LAN and back, maybe even Power Down/Up until we get this misbehavior resolved.

What happens if you set the Gateway?

Try the attached and see if it's any different for you. You will need to remove the other one from the Devices folder.

Thanks,
Josh

[mawyatt]

What happens if you set the Gateway?

Try the attached and see if it's any different for you. You will need to remove the other one from the Devices folder.

Thanks,
Josh

If we issue a RST after a switch from USB to LAN and/or back the leading 0 is gone!!

It seems that when in LAN using the Setup causes things to get messed up, like all the Current Values are 0 with no updates, none of the Parameters 1-4 can change, as this causes them to display Off. The IM3536 is still correct with Parameters and collecting data, we see just timeouts on the Read commands. Direct commands sent are not recognized and acted upon.

If we Reconnect from the Load device menu, then data is read and displayed again, direct commands work, and we can change Parameters with Direct Command. As soon as we invoke Setup from the Commands menu all data collecting stops and no Direct Commands work, we just see <No data (timeout)?> If we Reconnect then data flow and Direct commands return.

Seems something with invoking Setup is breaking the IM3536 interface connection when in LAN.

I'll give the new file a try a little later.

EDIT: Just tried the file and results are the same. Something with Setup is causing the issue with the Interface when using LAN. Also not sure what you mean about Gateway, if we set anything the LAN connection turns it OFF.

Best

[KungFuJosh]

Seems something with invoking Setup is breaking the IM3536 interface connection when in LAN.

If that is the case, then running in Debug mode will hopefully tell us why. On your Windows computer, that's easy to do. There's a file called testControllerDebug.bat in the TC directory that you can run that will automatically start debug mode.

Thanks,
Josh

[flash2b]

I have some suggestions to improve the recently published LCR definitions by KungFuJosh for the Tonghui (+ other brands) and HIOKI series. If you agree with my suggestions, you can make adjustments to make the definitions even better, up to you.

The main topic to improve upon is the variable frequency sweep range of these devices. I see in the definitions there is no actual readback of the set frequency nor that the frequency is logged using a #value statement.

This becomes important when you want to use the Param Sweeper (or the upcoming Steps) popup. Without logging frequency you can still sweep through the range of your LCR meter, however you will not be able to change the X axis to frequency which is needed for e.g. impedance graphs like I shown before. It is stuck to time in this case.

Now I also see that not all devices from the Tonghui series support real continuous frequency adjustment (the HIOKI does so no problem there), but stepped frequency adjustment. This is true for the TH2830 (34 points), TH2831 (37 points) and TH2832 (15025 points) (+other brands). So for these the set frequency is not always exactly the same as the readback set frequency. This could (potentially) screw up your measurement if you are not aware and will visualize itself during a sweep. To prevent this also it is better to log the readback frequency by adding a command to the #askValue statement and a #value statement to store it.

So my suggestion for improvement is to add frequency logging and readback to the LCR definitions which enable impedance graphing capability with the Param Sweeper and better measure for non real continuous frequency adjustment devices (explained above).

I have done it in my Owon LCR2000 definitions (=real continuous frequency adjustment) like this:

Code: [Select]

#askValues FETCH:MAIN?;FETCH:MON1?;FETCH:MON2?;FREQ?
#value Frequency Hz SI freq
I hope my reasoning is clear enough described and, like I said, up to you to implement it.

[HKJ]

The main topic to improve upon is the variable frequency sweep range of these devices. I see in the definitions there is no actual readback of the set frequency nor that the frequency is logged using a #value statement.

Param sweeper has a option to include the value directly from param sweeper, i.e. it do not matter if the device logs it or not.
The disadvantage with including more values is that it slows the maximum logging rate down. It may or it may not matter, that depends on a lot of factors.

[flash2b]

Yes, but that is the set value and not the read value, which in case of the devices mentioned is not always 1:1. Also when I log without (Param Sweeper), I do not have it so including it makes sure I have the real value.

Which option is it in the Param Sweeper, and does the (coming) Steps also has this option ?

[HKJ]

Yes, but that is the set value and not the read value, which in case of the devices mentioned is not always 1:1.

Hopefully it will be the same, but it may not be, especially if the device do not support the setting.

Which option is it in the Param Sweeper, and does the (coming) Steps also has this option ?

It is the log option on the 3 pages device pages.
I have not made it yet for steps, but I plan on doing it.
The documentation for steps is nearly done: https://lygte-info.dk/project/TestControllerPopupSteps%20UK.html that documentation do not exactly describe the test version (There are minor differences), but covers the next version of TC.

[flash2b]

Furthermore if about your concern about speed, running multiple Grid Panels to the same device while logging also slows down logging and they also run independently from a different data set. That is why I use grid panels sparsely.

[flash2b]

Which option is it in the Param Sweeper, and does the (coming) Steps also has this option ?

It is the log option on the 3 pages device pages.
I have not made it yet for steps, but I plan on doing it.
The documentation for steps is nearly done: https://lygte-info.dk/project/TestControllerPopupSteps%20UK.html that documentation do not exactly describe the test version (There are minor differences), but covers the next version of TC.

This one

[HKJ]

Furthermore if about your concern about speed, running multiple Grid Panels to the same device while logging also slows down logging and they also run independently from a different data set. That is why I use grid panels sparsely.

Grid panel tries to sample 5 or 6 times/sec, it will share samples with logging, but will also do its own sampling in between and that can slow logging slightly down.

[HKJ]

This one

Yes.

[flash2b]

Furthermore if about your concern about speed, running multiple Grid Panels to the same device while logging also slows down logging and they also run independently from a different data set. That is why I use grid panels sparsely.

Grid panel tries to sample 5 or 6 times/sec, it will share samples with logging, but will also do its own sampling in between and that can slow logging slightly down.

It is a pity that you cannot config the update rate as a user.

[HKJ]

It is a pity that you cannot config the update rate as a user.

Different popups has different logging rate, but it is all a suggestion and they may not reach it.
I never wanted to clutter the configuration up with minor settings.
At the current time I am looking at the "Output map" from steps, do it need a setting for size. I did consider adding a menu when pressing the button, but I like that it popup up fast without extra selections.

[flash2b]

Related to the "non real continuous frequency adjustment", it seems the international brandname Techmize where Tonghui is selling now under calls it "continuous frequency adjustment" without quoting the (set) points anymore so might also be a new revision. Maybe someone can confirm this on an old and/or new device ?

[mawyatt]

If that is the case, then running in Debug mode will hopefully tell us why. On your Windows computer, that's easy to do. There's a file called testControllerDebug.bat in the TC directory that you can run that will automatically start debug mode.

Thanks,
Josh

Yes we are using the TC debug mode per HKJ suggestion. Will look into this more later today.

Best