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

[HairyWombat]

I do not now if it causes the problems, but follow the instruction and put the line in the .bat file and use the .bat file to start TC.

This is depend on what Java is used and other types of Java will crash if I put that directive in, i.e. I cannot add it as standard.

Understood, adding native java selection removed the error however there was no change to the polling activity.
Starting to think it may well be something buried in Windows 11 com port control but would expect other devices to be affected.

Might just disregard the Protek as a viable solution with TC on Win11 or with my setup.
Thanks for trying to get it working HKJ and flash2b

[flash2b]

Instead of using the Current Values tab in TC you could also use Log instead. There you can set the polling interval, to 1sec or so. Then it will be much more likely that you do not have time outs from the Protek meter.

If it is temperature measuring that you are looking for solely, as an alternative buy a NT18B07 + RS485 adapter (purple version) and TC + my definition (all described in this topic). Then you will have 7 CH temp monitoring with 0.1C precision super stable.

[HKJ]

Instead of using the Current Values tab in TC you could also use Log instead. There you can set the polling interval, to 1sec or so. Then it will be much more likely that you do not have time outs from the Protek meter.

That is not true for this driver, it polls the device constantly in the background and answers with the latest result when polled from TC

[flash2b]

Is that specific to the singleValue driver then ? (I did not know this....  )

The Protek 506 is only 1200 baud (7-2-N) and no flow control supported. I know that TC is way much faster than that, bombarding the meter leading to a timeout. Can we add a delay in the definition ?

[HKJ]

Is that specific to the singleValue driver then ? (I did not know this....  )

The Protek 506 is only 1200 baud (7-2-N) and no flow control supported. I know that TC is way much faster than that, bombarding the meter leading to a timeout. Can we add a delay in the definition ?

I checked the code and it looks like I remembered wrong, SingleValue is not one of the drivers that communicate in the background (Some drivers do).
So logging will probably slow it down.

[HairyWombat]

I tried it but it didn't help.
While it did stop blasting the meter with bursts the same response was evident.
Instead of a request every second TC hangs for varying periods.
During this hang time no data changes in the debug window and TC is non responsive to commands.

Its not the speed of requests that is the problem its like TC gets something it really does not like.

[flash2b]

Sorry HKJ I made a typo in my last definition. Could you please update to the one attached ?

Thank you.
Now part of TestController V2.96

[ Attachment Invalid Or Does Not Exist ]

[HKJ]

Sorry HKJ I made a typo in my last definition. Could you please update to the one attached ?

Updated, thanks.

[HKJ]

Its not the speed of requests that is the problem its like TC gets something it really does not like.

I doubt TC gets anything it do not like, the driver is supposed to handle any character without issues.

But because it is synchronized to data collection, timeouts will affect TC.

[KungFuJosh]

I tried it but it didn't help.
While it did stop blasting the meter with bursts the same response was evident.
Instead of a request every second TC hangs for varying periods.
During this hang time no data changes in the debug window and TC is non responsive to commands.

Its not the speed of requests that is the problem its like TC gets something it really does not like.

Are you using JDK or JRE?

[flash2b]

In definition BrymenBM250.txt

#name ACT/6000 should be changed to #name ACT ACT/6000

Also found out that the column Device on the Load Devices tab is case sensitive. The "search socket" was changed recently to be case insensitive.

[HKJ]

In definition BrymenBM250.txt

#name ACT/6000 should be changed to #name ACT ACT/6000

You are sort of correct in that, but I do not believe anybody will be confused by the current name.

Also found out that the column Device on the Load Devices tab is case sensitive. The "search socket" was changed recently to be case insensitive.

The sorting for the search socket was changed to be case insensitive.

[HairyWombat]

Are you using JDK or JRE?

Java SE Dev Kit 24.0.2 64bit

[homico]

Dear HKJ, I have created 3 new definitions for temperature acquisition modules manufactured by Eletechsup.

These modules are Modbus_RTU controlled
..,.....
The definitions are:
- Eletechsup NT18B07 7CH temperature acquisition module
.......

This is excellent! Thank you, flash2B. I think I'll buy one.
Well, It would be nice to connect this one too: PTA9B01 PT100 RS485


You can scatter a dozen of these around the house on twisted pair cable...

[Tjuurko]

My first test version of creating a device description.
 East Tester ET35xx.txt

[HKJ]

My first test version of creating a device description.

I have added it, thanks.
You did not add a #author statement.

[flash2b]

Also found out that the column Device on the Load Devices tab is case sensitive. The "search socket" was changed recently to be case insensitive.

The sorting for the search socket was changed to be case insensitive.

True... but the sorting of Load Devices is not. It is not a big problem, I like consistency.

[HKJ]

True... but the sorting of Load Devices is not. It is not a big problem, I like consistency.

I may fix that 

[flash2b]

Dear HKJ, I have created 3 new definitions for temperature acquisition modules manufactured by Eletechsup.

These modules are Modbus_RTU controlled
..,.....
The definitions are:
- Eletechsup NT18B07 7CH temperature acquisition module
.......

This is excellent! Thank you, flash2B. I think I'll buy one.
Well, It would be nice to connect this one too: PTA9B01 PT100 RS485
(Attachment Link)
(Attachment Link)
You can scatter a dozen of these around the house on twisted pair cable...

You can however the RS485 slave address is not fully supported by TC. The relationship with a Serial Connection to Device is 1:1. If you want to used slave IDs you need to alter the definition and add them there. Then a definition controls multiple devices, which s far from ideal.

Hope you like the Eletechsup NT18B07 as much as I like them.

[HKJ]

You can however the RS485 slave address is not fully supported by TC. The relationship with a Serial Connection to Device is 1:1. If you want to used slave IDs you need to alter the definition and add them there. Then a definition controls multiple devices, which s far from ideal.

Hope you like the Eletechsup NT18B07 as much as I like them.

TC might at a later date.
I am thinking about getting a RS485 USB adapter and a couple of temperature sensors (Guess who is responsible for that  ) and see if I can make a modbus sharing.
It will be in the GPIB menu, but hopefully require another selection than GBIB, maybe modbus-
The syntax will be similar to GPIB, ie. a id, a colon and a number where the number will override the default modbus address from the definition.

Everything above is ideas and I do not promise anything!

[flash2b]

I can't wait and happy to test with you.

The CH340T based adapter (purple one) and the CH344 based adapter (Waveshare, 4CH) are my favorites, as mentioned before. The FT232RL adapter, I do no like so much so I not advise that one. It is not that the FT232RL is bad, it is the module itself.

I have already started to write definitions for 2 more modules.

[flash2b]

My first test version of creating a device description.
(Attachment Link)

Since I like LCR meters a lot, I am happy that your wrote a definition for another advanced LCR meter.

[KungFuJosh]

Are you using JDK or JRE?

Java SE Dev Kit 24.0.2 64bit

Yes, that's JDK. That might be related to the issue you're having. I had some issues with JDK and switched to JRE (Java Runtime Environment). You can see some more info around this post: https://www.eevblog.com/forum/testgear/program-that-can-log-from-many-multimeters/msg6057645/#msg6057645

Thanks,
Josh

[HairyWombat]

The CH340T based adapter (purple one) and the CH344 based adapter (Waveshare, 4CH) are my favorites, as mentioned before. The FT232RL adapter, I do no like so much so I not advise that one. It is not that the FT232RL is bad, it is the module itself.

Flash2B I have had really good results with these CH340 RS485 adapters off Ali
Amazingly cheap, about the price of 2 RS485 DIP transceivers which are so expensive now.

[HairyWombat]

Are you using JDK or JRE?

Java SE Dev Kit 24.0.2 64bit

Yes, that's JDK. That might be related to the issue you're having. I had some issues with JDK and switched to JRE (Java Runtime Environment). You can see some more info around this post: https://www.eevblog.com/forum/testgear/program-that-can-log-from-many-multimeters/msg6057645/#msg6057645
Thanks,
Josh

You sir are indeed a legend, thank you very much Josh

Installed the standard end user JRE, tried the modded debug TC but it crashed and same with non debug TC.
Uninstalled JDK 24.0.2, reran JRE installer as it only installed an update before and tried the non debug TC, SHE RAN CORRECTLY for the first time!!!
Removed enabled native access switch from debug TC and that was it TC is happily spewing out readings, wonderful.
So don't install that JDK at all and its good it seems, not sure about the latest JDK 25, I will test later but expect the same issue.
Does the JDK not contain the JRE components or is it more of a permissions issue?

The problem was always right there with the Java error however the resolution provided in the error does not resolve the issue.
So its a warning to fix your Java environment it seems 

Code: [Select]

Starting
;; jSerialComm version: 2.11.2
;; Start thread for: COM4 - Protek 506
;; Start thread for: COM3
;; COM3: Set params: 9600
;; COM4: Set params: 1200N72
;; Found Protek 506 on USB-Serial Controller D (COM4)
;; COM3: Tx: <*IDN?.> 2A 49 44 4E 3F 0A
;; COM3: Rx: timeout
;; COM3: Tx: <*IDN?.> 2A 49 44 4E 3F 0A
;; COM3: Rx: timeout
;; Stopping thread for: COM3
;; COM3: Close
;; Mode reported: <DCV>
;; P506: Tx <VALUE?>
;; P506: Rx Timeout
;; P506: Rx as numbers <No data (timeout?)>
;; P506: Tx <VALUE?>
;; P506: Rx Timeout
;; P506: Rx as numbers <No data (timeout?)>
;; P506: Tx <VALUE?>
;; P506: Rx Timeout
;; P506: Rx as numbers <No data (timeout?)>
;; P506: Tx <VALUE?>
;; P506: Rx <-0.001>
;; P506: Rx as numbers <-0.001>
;; P506: Tx <VALUE?>
;; P506: Rx <-0.001>
;; P506: Rx as numbers <-0.001>
;; P506: Tx <VALUE?>
;; P506: Rx <-0.001>
;; P506: Rx as numbers <-0.001>
;; P506: Tx <VALUE?>
;; P506: Rx <0.003>
;; P506: Rx as numbers <0.003>
;; P506: Tx <VALUE?>
;; P506: Rx <0.003>
;; P506: Rx as numbers <0.003>
;; P506: Tx <VALUE?>
;; P506: Rx <0.005>
;; P506: Rx as numbers <0.005>
;; P506: Tx <VALUE?>
;; P506: Rx <0.005>
;; P506: Rx as numbers <0.005>
;; P506: Tx <VALUE?>
;; P506: Rx <0.005>
;; P506: Rx as numbers <0.005>
;; P506: Tx <VALUE?>
;; P506: Rx <0.018>
;; P506: Rx as numbers <0.018>
;; P506: Tx <VALUE?>
;; P506: Rx <0.018>
;; P506: Rx as numbers <0.018>
;; P506: Tx <VALUE?>
;; P506: Rx <0.018>
;; P506: Rx as numbers <0.018>
;; P506: Tx <VALUE?>
;; P506: Rx <-0.001>
;; P506: Rx as numbers <-0.001>
;; P506: Tx <VALUE?>
;; P506: Rx <-0.001>
;; P506: Rx as numbers <-0.001>
;; P506: Tx <VALUE?>
;; P506: Rx <-0.006>
;; P506: Rx as numbers <-0.006>
;; P506: Tx <VALUE?>
;; P506: Rx <-0.006>
;; P506: Rx as numbers <-0.006>
;; P506: Tx <VALUE?>
;; P506: Rx <0.005>
;; P506: Rx as numbers <0.005>
;; P506: Tx <VALUE?>
;; P506: Rx <0.005>
;; P506: Rx as numbers <0.005>
;; P506: Tx <VALUE?>
;; P506: Rx <0.005>
;; P506: Rx as numbers <0.005>
;; P506: Tx <VALUE?>
;; P506: Rx <0.001>
;; P506: Rx as numbers <0.001>
;; P506: Tx <VALUE?>
;; P506: Rx <0.001>
;; P506: Rx as numbers <0.001>
;; Mode reported: <DIO>
;; P506: Tx <VALUE?>
;; P506: Rx <1>
;; P506: Rx as numbers <1.0>
;; P506: Tx <VALUE?>
;; P506: Rx <1>
;; P506: Rx as numbers <1.0>
;; P506: Tx <VALUE?>
;; P506: Rx <1>
;; P506: Rx as numbers <1.0>
;; P506: Tx <VALUE?>
;; P506: Rx <1>
;; P506: Rx as numbers <1.0>
;; P506: Tx <VALUE?>
;; P506: Rx <1>
;; P506: Rx as numbers <1.0>
;; P506: Tx <VALUE?>
;; P506: Rx <1>
;; P506: Rx as numbers <1.0>
;; Mode reported: <CAPF>
;; P506: Tx <VALUE?>
;; P506: Rx <00.00u>
;; P506: Rx as numbers <0.0>
;; P506: Tx <VALUE?>
;; P506: Rx <00.00u>
;; P506: Rx as numbers <0.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0026>
;; P506: Rx as numbers <26.0>
;; Mode reported: <TEMPC>
;; P506: Tx <VALUE?>
;; P506: Rx <0026>
;; P506: Rx as numbers <26.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0026>
;; P506: Rx as numbers <26.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0026>
;; P506: Rx as numbers <26.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0026>
;; P506: Rx as numbers <26.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0026>
;; P506: Rx as numbers <26.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0026>
;; P506: Rx as numbers <26.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0026>
;; P506: Rx as numbers <26.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0029>
;; P506: Rx as numbers <29.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0029>
;; P506: Rx as numbers <29.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0029>
;; P506: Rx as numbers <29.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0028>
;; P506: Rx as numbers <28.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0028>
;; P506: Rx as numbers <28.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0028>
;; P506: Rx as numbers <28.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0026>
;; P506: Rx as numbers <26.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0026>
;; P506: Rx as numbers <26.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0029>
;; P506: Rx as numbers <29.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0029>
;; P506: Rx as numbers <29.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0029>
;; P506: Rx as numbers <29.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0027>
;; P506: Rx as numbers <27.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0027>
;; P506: Rx as numbers <27.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0027>
;; P506: Rx as numbers <27.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0027>
;; P506: Rx as numbers <27.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0027>
;; P506: Rx as numbers <27.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0027>
;; P506: Rx as numbers <27.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0027>
;; P506: Rx as numbers <27.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0030>
;; P506: Rx as numbers <30.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0030>
;; P506: Rx as numbers <30.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0030>
;; P506: Rx as numbers <30.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0028>
;; P506: Rx as numbers <28.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0028>
;; P506: Rx as numbers <28.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0028>
;; P506: Rx as numbers <28.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0027>
;; P506: Rx as numbers <27.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0027>
;; P506: Rx as numbers <27.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0027>
;; P506: Rx as numbers <27.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0030>
;; P506: Rx as numbers <30.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0030>
;; P506: Rx as numbers <30.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0030>
;; P506: Rx as numbers <30.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0028>
;; P506: Rx as numbers <28.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0028>
;; P506: Rx as numbers <28.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0027>
;; P506: Rx as numbers <27.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0027>
;; P506: Rx as numbers <27.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0027>
;; P506: Rx as numbers <27.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0027>
;; P506: Rx as numbers <27.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0030>
;; P506: Rx as numbers <30.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0030>
;; P506: Rx as numbers <30.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0030>
;; P506: Rx as numbers <30.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0027>
;; P506: Rx as numbers <27.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0027>
;; P506: Rx as numbers <27.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0027>
;; P506: Rx as numbers <27.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0028>
;; P506: Rx as numbers <28.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0028>
;; P506: Rx as numbers <28.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0028>
;; P506: Rx as numbers <28.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0030>
;; P506: Rx as numbers <30.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0030>
;; P506: Rx as numbers <30.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0027>
;; P506: Rx as numbers <27.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0027>
;; P506: Rx as numbers <27.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0027>
;; P506: Rx as numbers <27.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0028>
;; P506: Rx as numbers <28.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0028>
;; P506: Rx as numbers <28.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0028>
;; P506: Rx as numbers <28.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0030>
;; P506: Rx as numbers <30.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0030>
;; P506: Rx as numbers <30.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0027>
;; P506: Rx as numbers <27.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0027>
;; P506: Rx as numbers <27.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0027>
;; P506: Rx as numbers <27.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0028>
;; P506: Rx as numbers <28.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0028>
;; P506: Rx as numbers <28.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0028>
;; P506: Rx as numbers <28.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0028>
;; P506: Rx as numbers <28.0>
;; P506: Tx <VALUE?>
;; P506: Rx <0028>
;; P506: Rx as numbers <28.0>
A huge thanks to everyone who commented, even tautech, to resolve my TC issue.
Hopefully this helps someone else.

HKJ Thank you so much for writing such a wonderful program thats open source configurable, truly brilliant.
The lack of locked executable and advertising bloatwear is refreshing and so wish others would follow this path.
I can only see great things for TC moving forward