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

[KungFuJosh]

I have some suggestions to improve the recently published LCR definitions by KungFuJosh for the Tonghui (+ other brands) and HIOKI series.

Thanks for the suggestions. I have plans to do more with these meters, including possibly monitoring the frequency. However, as HKJ mentioned, it's not necessary for the param sweeper. Both brands use FREQ? for frequency, so pretty simple to use.

I was considering adding it as 5th optional measurement for frequency tracking. That way it won't necessarily impact speed, but it's not a high priority as it isn't that helpful outside of sweeping.

Newer firmware versions on the TongHui models do allow arbitrary frequency input (to some degree - numberInt at least). TH/ST LCRs stuck on older firmware won't be as fun.



Hmm, this gives me an idea @HKJ will love. What do you think about the ability to add a SCPI command to track manually? Something like:

Code: [Select]

#scpiTrack handle scpi #value
#scpiTrack ST2832 FREQ? #value M5_Freq Hz SI
Thanks,
Josh

[flash2b]

Well I've experienced the frequency point behavior myself on a Tonghui TH2830 (on a demo somewhere), but it might that newer units or newer firmware removed the annoying frequency points.Techmize does not state it anymore.

You cannot use Param Seeper on cmdSetuo numberInt controls by the way.

My Owon LCR2020 (lowest in the Range) has a resolution of 10 mHz across the programmable continuous spectrum

[HKJ]

You cannot use Param Seeper on cmdSetuo numberInt controls by the way.

Correct, but on steps you can put in linear sweeps on int, but is has to be a #interface control.

[KungFuJosh]

Well I've experienced the frequency point behavior myself on a Tonghui TH2830 (on a demo somewhere), but it might that newer units or newer firmware removed the annoying frequency points.Techmize does not state it anymore.

Yup, that would have been an older firmware. I don't think they even advertised the change. But you can see in the 2830/2832 thread there was a point when the firmware changed the frequency input limitations.

You cannot use Param Seeper on cmdSetuo numberInt controls by the way.

That's good to know, thanks.

My Owon LCR2020 (lowest in the Range) has a resolution of 10 mHz across the programmable continuous spectrum

TongHui is weird. Even the TH2832 specifies 20 Hz to 200 kHz, with 15025 points. That's about 13 Hz resolution, which is odd. It appears that reality is also 10mHz resolution:

Code: [Select]

;; Found Sourcetronic ST2832 on USB Serial Device (COM10) (COM10) sn: Ver 1.0.0
FREQ?
;; 4.00020e+02
That might also be the result of the "newer" firmware.

Hioki specifies 5 digits with a minimum of 10mHz resolution.

So, yeah, numberInt would be wrong regardless.

Thanks,
Josh

[flash2b]

Dear HKJ,

I have added support for the Anbai AT810A and Applent AT810A in my existing LCR definitions. 2 more devices for TC and 12 updated ones.

With #removeMatch it is even more easy to take not supported stuff out of a definition. 

On top of this I also updated all other devices that this definition support and since I converted the TXT file to UTF-8-BOM I now use proper symbols like  Ω, Δ, Δ%, θ_°  and θ_r.

[ Attachment Invalid Or Does Not Exist ]

[flash2b]

The conversion from ANSI to UTF-8-BOM is very easy.

For Notepad++ just load your file, go to Encoding and change ANSI to UTF-8-BOM, and save the fie. I have no idea how other editors do this.

Windows Notepad can do it as well, Save As, Encoding, UTF-8 with BOM.

It enables the use of special symbols in TestController definitions, like Ω and °. #metaDebug save does not support it, but don't be alarmed, internally TC does do it properly. Also some logging does not support it, forgot which.

[HKJ]

Dear HKJ,

I have added support for the Anbai AT810A and Applent AT810A in my existing LCR definitions. 2 more devices for TC and 12 updated ones.

With #removeMatch it is even more easy to take not supported stuff out of a definition. 

On top of this I also updated all other devices that this definition support and since I converted the TXT file to UTF-8-BOM I now use proper symbols like  Ω, Δ, Δ%, θ_°  and θ_r.

Updated/added, thanks.

[flash2b]

Oh... I tried using getDeviceInfo(handle) I was sad to see getDeviceInfo(handle).version was not supported directly. I was hoping it returned a space separated string which I could attack with getElement, but it returns a struct instead which needs a var assignment to get it working. I did not want any var in this particular definition so I did not use it.

[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

Got some more time with this using TC Debug on PC. Here's 2 files showing the debug details of when using USB and LAN as the connection. This is the end of invoking Setup from the Command tab, then changing Parameter 4. Note that USB shows a number of lines with a IM3536: Script start while the LAN shows no IM3536: Script start and a few lines after such without the additional HEX data with Tx command.

Anyway, this seems to be why the LAN connection isn't allowing any IM3536 changes (Rx Timeout), while the USB does.

Here's the USB:

IM3536: Tx <MeasType4 Z>
IM3536: Script start
IM3536: Tx <:PAR4 Z>
COM8: Tx: <:PAR4 Z.> 3A 50 41 52 34 20 5A 0A
IM3536: Tx <PAR4?>
COM8: Tx: <PAR4?.> 50 41 52 34 3F 0A
COM8: Rx: <Z> 5A
IM3536: Rx <Z>
IM3536: Tx <PAR4?>
COM8: Tx: <PAR4?.> 50 41 52 34 3F 0A
COM8: Rx: <Z> 5A
IM3536: Rx <Z>
IM3536: Script end <>
IM3536: Tx <:PAR4?>
COM8: Tx: <:PAR4?.> 3A 50 41 52 34 3F 0A
COM8: Rx: <Z> 5A
IM3536: Rx <Z>

And the LAN:

IM3536: Tx <MeasType4 X>
IM3536: Tx <:PAR4?>
IM3536: Rx Timeout

Best

[KungFuJosh]

@mawyatt,

Try the attached instead. It seems like your ethernet connection might not be great, and it's timing out. I've increased the #readingDelay from 1 second to 5 seconds. If that's not enough, try increasing that line to 10 and see if that solves the connection issue.

Look for this line in the attached definition (if needed to edit):

Code: [Select]

#readingDelay 5
I'll make 5 seconds default in the next version if it works for you.

Thanks,
Josh

[mawyatt]

@mawyatt,

Try the attached instead. It seems like your ethernet connection might not be great, and it's timing out. I've increased the #readingDelay from 1 second to 5 seconds. If that's not enough, try increasing that line to 10 and see if that solves the connection issue.

Look for this line in the attached definition (if needed to edit):

Code: [Select]

#readingDelay 5
I'll make 5 seconds default in the next version if it works for you.

Thanks,
Josh

That doesn't work, neither does 10 seconds. It apparently has something to do with the Send command structure. See below where the USB command structure is totally different than the LAN.

USB mode issuing a Display Off command

IM3536: Tx <:DISP OFF>
COM8: Tx: <:DISP OFF.> 3A 44 49 53 50 20 4F 46 46 0A
IM3536: Tx <:DISP?>
COM8: Tx: <:DISP?.> 3A 44 49 53 50 3F 0A
COM8: Rx: <OFF> 4F 46 46
IM3536: Rx <OFF>


USB mode issuing a Display On command

IM3536: Tx <:DISP ON>
COM8: Tx: <:DISP ON.> 3A 44 49 53 50 20 4F 4E 0A
IM3536: Tx <:DISP?>
COM8: Tx: <:DISP?.> 3A 44 49 53 50 3F 0A
COM8: Rx: <ON> 4F 4E
IM3536: Rx <ON>


LAN mode issuing a Display Off command (Fails)

IM3536: Tx <:DISP OFF>
IM3536: Tx <:DISP?>
IM3536: Rx Timeout

LAN mode issuing a Display On command (Fails)

IM3536: Tx <:DISP ON>
IM3536: Tx <:DISP?>
IM3536: Rx Timeout


Our limited understanding of how TC works with the IM3536 indicates that when Setup is invoked with LAN, the connection is lost with the IM3536. This explains the return of all 0s [ Debug shows <No data (Timeout?)> ] in the 4 Parameters values under Current Values  tab. However prior to invoking Setup, the communication is working as expected (proper Parameters values).
 
Best

[KungFuJosh]

That doesn't work, neither does 10 seconds. It apparently has something to do with the Send command structure. See below where the USB command structure is totally different than the LAN.

LAN mode issuing a Display Off command (Fails)

IM3536: Tx <:DISP OFF>
IM3536: Tx <:DISP?>
IM3536: Rx Timeout

LAN mode issuing a Display On command (Fails)

IM3536: Tx <:DISP ON>
IM3536: Tx <:DISP?>
IM3536: Rx Timeout

There's no difference in commands structure. What you're seeing is the way TC transmits/echoes data. The problem is, you're not getting anything over ethernet in that case.

I'd try removing the IM3536 from the device list completely (no duplicates or other connection types).
Try a different IP on the IM3536, and make sure there are no IP conflicts.
Then add the IM3536 back to the device list, and see if the connection issue persists.

Here's an example of my LCR with a good ethernet connection:

Code: [Select]

IM3570: Tx <getallModes?>
IM3570: Tx <none?>
IM3570: Rx <LP1,X2,Q3,Z4>
:DISP OFF
IM3570: Tx <:DISP OFF>
123.456.789.123: Tx: <:DISP OFF.> 3A 44 49 53 50 20 4F 46 46 0A
:DISP ON
IM3570: Tx <:DISP ON>
123.456.789.123: Tx: <:DISP ON.> 3A 44 49 53 50 20 4F 4E 0A
Thanks,
Josh

ETA: PS. You mentioned previously that you didn't have the Gateway set on your IM3536. That could be a problem. The Gateway should have your router's IP.

[mawyatt]

There's no difference in commands structure. What you're seeing is the way TC transmits/echoes data. The problem is, you're not getting anything over ethernet in that case.

I'd try removing the IM3536 from the device list completely (no duplicates or other connection types).
Try a different IP on the IM3536, and make sure there are no IP conflicts.
Then add the IM3536 back to the device list, and see if the connection issue persists.

Here's an example of my LCR with a good ethernet connection:

Code: [Select]

IM3570: Tx <getallModes?>
IM3570: Tx <none?>
IM3570: Rx <LP1,X2,Q3,Z4>
:DISP OFF
IM3570: Tx <:DISP OFF>
123.456.789.123: Tx: <:DISP OFF.> 3A 44 49 53 50 20 4F 46 46 0A
:DISP ON
IM3570: Tx <:DISP ON>
123.456.789.123: Tx: <:DISP ON.> 3A 44 49 53 50 20 4F 4E 0A
Thanks,
Josh

ETA: PS. You mentioned previously that you didn't have the Gateway set on your IM3536. That could be a problem. The Gateway should have your router's IP.

TC can write and read to/from the IM3536 as the TC collects data for the 4 Parameters and displays results. So TC is seeing and communicating with the IM3536, it's only when Setup is invoked the connection is broken???

Best

[KungFuJosh]

TC can write and read to/from the IM3536 as the TC collects data for the 4 Parameters and displays results. So TC is seeing and communicating with the IM3536, it's only when Setup is invoked the connection is broken???

When you load the setup, it sends ALL the read commands for everything visible in the setup popup. That's a lot of stuff for a bad connection to handle.

Your log from the setup popping up showed that it made it through a bunch of the command? stuff, then started timing out.

Changing the reading timeout to longer should have fixed that if it was just going too quick for the connection, but your connection seems to be inconsistent.

My guess is that the connection quality is bad, or there's some kind of conflict with communication. If you don't want to change the IP, then make sure the IP is reserved in your router for the LCR. You could also try restarting your router and the LCR. Maybe try a different cable with the LCR.

Thanks,
Josh

PS. Sometimes replacing the device in the device list in TC makes fixing things easier.

[flash2b]

LAN mode issuing a Display Off command (Fails)

IM3536: Tx <:DISP OFF>
IM3536: Tx <:DISP?>
IM3536: Rx Timeout

LAN mode issuing a Display On command (Fails)

IM3536: Tx <:DISP ON>
IM3536: Tx <:DISP?>
IM3536: Rx Timeout

Try adding a :updatedelayed: 0.3

in this one

#cmdSetup buttonsOn Display Main
:read: :DISP?
:write: :DISP
:updatedelayed: 0.3
:string:
:nogrid:
:color: blue
Off OFF
On ON
:tip: Enable or disable display.

I have seen SCPI devices before that do not like quick read-write-read

If this improved that function, it can be added to other similar commands.

Do you have a load balancer between the LCR device and the PC/Mac running TC? The other cause can be a network configuration (load balancing, traffic shaping, fallback, firewall) leading to no answer/timeout.

[mawyatt]

Thanks Josh and flash.

Tried different addresses and adding a delay, no difference!! Also all instruments on the LAN are powered down, only the IM3536 is powered On.

Started looking at each individual IM3536 commands (think we found an error, see below) tried them from command line. Found that some don't respond and timeout with a <null> turn.

Here are some examples of timeout commands:

LEV:CHEC:LIM
DCR:LEV
DCR:LEV:VOLT
DCR:LEV:CVOLT
DCR:LIM
DCR:LIM:VOLT
DCR:LIM:CURR

These all timeout however the IM3536 is still connected and can return proper measurement values as shown in Current values tab. BTW these also timeout under USB connection, however USB seems to work with Setup, LAN doesn't!!

We can read and write various commands by command line and they work as expected, however once Setup is invoked the LAN interface to the IM3536 is apparently lost (even *IDN? times out) and doesn't recover after exiting Setup and a "Reconnect" is required.

Something in the Setup initiation is breaking the LAN connection to the IM3536.

Anyway, will keep digging into this as time permits altho somewhat hampered by not being Network, Interface and SCPI savie

Best

[HKJ]

LEV:CHEC:LIM
DCR:LEV
DCR:LEV:VOLT
DCR:LEV:CVOLT
DCR:LIM
DCR:LIM:VOLT
DCR:LIM:CURR

TC requires a ? after the command or it will not expect an answer.
The SCPIx driver has ways around that, with a couple of txrx commands to put in front of the actual command.
List of them are here: https://lygte-info.dk/project/TestControllerConfigDevice2%20UK.html#Commands_to_write_and_read_values

[KungFuJosh]

Here are some examples of timeout commands:

LEV:CHEC:LIM
DCR:LEV
DCR:LEV:VOLT
DCR:LEV:CVOLT
DCR:LIM
DCR:LIM:VOLT
DCR:LIM:CURR

These all timeout however the IM3536 is still connected and can return proper measurement values as shown in Current values tab. BTW these also timeout under USB connection, however USB seems to work with Setup, LAN doesn't!!

That is odd. Those are valid commands. Screenshot from here attached: https://www.hioki.com/e/products/lcr/application/IM3536/English/index.htm

I will email you.

Thanks,
Josh

[mawyatt]

LEV:CHEC:LIM
DCR:LEV
DCR:LEV:VOLT
DCR:LEV:CVOLT
DCR:LIM
DCR:LIM:VOLT
DCR:LIM:CURR

TC requires a ? after the command or it will not expect an answer.
The SCPIx driver has ways around that, with a couple of txrx commands to put in front of the actual command.
List of them are here: https://lygte-info.dk/project/TestControllerConfigDevice2%20UK.html#Commands_to_write_and_read_values

We didn't include the "?" in the list, but was used to get a return value from the command line.

Best

[mawyatt]

Here are some examples of timeout commands:

LEV:CHEC:LIM
DCR:LEV
DCR:LEV:VOLT
DCR:LEV:CVOLT
DCR:LIM
DCR:LIM:VOLT
DCR:LIM:CURR

These all timeout however the IM3536 is still connected and can return proper measurement values as shown in Current values tab. BTW these also timeout under USB connection, however USB seems to work with Setup, LAN doesn't!!

That is odd. Those are valid commands. Screenshot from here attached: https://www.hioki.com/e/products/lcr/application/IM3536/English/index.htm

I will email you.

Thanks,
Josh

Note these are DCR:LIM and DCR:LEV types that time out. The LEV and LIM commands work OK except the mentioned LEV:CHEC:LIM command.

Best

[KungFuJosh]

Note these are DCR:LIM and DCR:LEV types that time out. The LEV and LIM commands work OK except the mentioned LEV:CHEC:LIM command.

Oops- I overlooked that! I'll review the DCR commands with the manual. Is there anything else that failed to respond on your IM3536?

ETA:
From your logs it looks like only these commands:

Code: [Select]

:DCR:LEV?
:DCR:LEV:VOLT?
:DCR:LEV:CVOLT?
:DCR:LEV:CCURR?
:DCR:LIM?
:DCR:LIM:VOLT?
:DCR:LIM:CURR?

:LEV:CHEC?
:LEV:CHEC:LIM?

I will review them, and modify the definition appropriately.

Thanks,
Josh

[mawyatt]

SOLVED !!!!!!

Apparently the various DCR commands are not recognized by the IM3536. We deleted these commands from the Hioki 35XX file and now we have LAN connections and various functions working, and Setup behaves as expected

Still have some "cleaning up" to do, but things appear to be in order now and working with LAN

Thanks for all the help

Edit: Here's the updated IM35XX file.
Don't use this one, use the one Josh updated and added below, it's "cleaner"!!!

Best

[KungFuJosh]

SOLVED !!!!!!

Apparently the various DCR commands are not recognized by the IM3536. We deleted these commands from the Hioki 35XX file and now we have LAN connections and various functions working, and Setup behaves as expected

Still have some "cleaning up" to do, but things appear to be in order now and working with LAN

Thanks for all the help

Best

I will release an official version that has the corrections made for device specific limitations.

Thanks,
Josh

[KungFuJosh]

Here's an updated version of the Hioki IM series LCR meters. This should cover the compatibility issues Mike experienced.

Apparently, only the IM3570 had those extra features. 🤷

@mawyatt, please try this version instead.

ETA: Updated. I missed the other level check. Now this should be 100% compatible.

Thanks,
Josh

[KungFuJosh]

@mawyatt & @Martin72,

Please test the updated file on my previous post. I replaced it as it still had a level check that needed to be removed for your devices.

Thanks,
Josh