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

[HKJ]

Much better. This is so much simpler now for metadefs.

Requires Test Controller V3.01 or higher.

Updated, thanks.

[HKJ]

:readmath: binConvString(value,0,24,"ISO-8859-1")

;; COM4: Rx: 01 03 18 45 49 44 30 35 31 2D 31 34 38 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 38
;; EID051_148: Rx <EID051-148              >

There is two ways to get rid of the trailing spaces:
:readmath: binConvString(value,0,24,"ISO-8859-1",0,0)
:readmath: trim(binConvString(value,0,24))

It is not necessary to specify code page when it is ISO-8859-1

[flash2b]

There was no need to remove the trailing spaces, since they were 00 so not a real space. TC removes them automatically no trim() required.

[testcalvin59]

Hi there,

I am new to this space - currently I have a Multicomp Pro 72-13360 (Aka Tenma and Korad KRW103) and I want to log the current, voltage measurements from the power supply. Does anyone have a configuration device txt file that you can share ?

Any help is very much appreciated.

Best regards

[homico]

Hi Dread. I'm using two ET5420A+  ET5410A+ electronic loads, bought in different years (...one by 2024). They work perfectly with TestController. However, they have one mandatory requirement: they must be locked, otherwise they won't work properly!
(Ignore the fan shut-off symbol—I do that myself to keep it from spinning when not needed.)

[HKJ]

I hate it when a harddisk dies, and a brand new (ok 1/2 year old) 4TB SSD with all my development on, luckily it was my hot-backup, i.e. a exact copy of my development computer and designed to take over from that computer sometime in the future. This means easy restoring of data (Getting it from my other backup is more work). Warrant replacement went smoothly (mostly) and I am restoring the data now (It may take up to a day, but I do not need to do anything).

[KungFuJosh]

Hi Dread. I'm using two ET5420A+ electronic loads, bought in different years (...one by 2024). They work perfectly with TestController. However, they have one mandatory requirement: they must be locked, otherwise they won't work properly!
(Ignore the fan shut-off symbol—I do that myself to keep it from spinning when not needed.)

I shared a new version compatible with the ET5420A+. It works fine with mine, can you try it out?

It's in this post: https://www.eevblog.com/forum/testgear/program-that-can-log-from-many-multimeters/msg6233797/#msg6233797

And you'll also need to download the V3.01 beta.

Thanks,
Josh

[homico]

Oh no! That's a typo, I'm using the ET5410A+.
And you have to remove the block for 5420, otherwise 5410A+ won’t connect.

[KungFuJosh]

Oh no! That's a typo, I'm using the ET5410A+.
And you have to remove the block for 5420, otherwise 5410A+ won’t connect.

It should still work with my definition, but you will need to remove whatever other definition you were using for it. It needs to be the only one that identifies the 5410A+.

[infino]

Are you planning to add support for the UT181A from UNI-T?

[HKJ]

Are you planning to add support for the UT181A from UNI-T?

I hit a snag, I need to incorporate JNI (Java native access) before I can do it. I have not gotten around to that yet.

[Grouwers]

And you'll also need to download the V3.01 beta.

Hello. Where can I download version 3.1 beta? Could you please provide a link? I couldn’t find any mention of this version on the developer’s website.

[HKJ]

And you'll also need to download the V3.01 beta.

Hello. Where can I download version 3.1 beta? Could you please provide a link? I couldn’t find any mention of this version on the developer’s website.

You can find it here: http://lygte-info.dk/pic/Projects/TestController/TestController.jar

The above link will always point to the newest test version, when one exist. I do sometimes post it in this thread.

[dreamer]

Good afternoon, colleagues.

I would like to thank you for the excellent and useful software.

I don’t use the DL24 electronic load very often, and now I’ve encountered a problem. After updating to version V3.0, two decimal digits after the decimal point are no longer displayed when measuring voltage. All other measurements are normal.

I rolled back to version 2.53, and here I still see only two decimal places (e.g., 5.00). Although the voltage also varies over the time period.

What could be the cause of this? Thank you.

[HKJ]

I don’t use the DL24 electronic load very often, and now I’ve encountered a problem. After updating to version V3.0, two decimal digits after the decimal point are no longer displayed when measuring voltage. All other measurements are normal.

I rolled back to version 2.53, and here I still see only two decimal places (e.g., 5.00). Although the voltage also varies over the time period.

What could be the cause of this? Thank you.

That the protocol only supplies two decimals.

[Fire Doger]

Hello,

I made the config for Rigol DM858 and DM858E. (E variant not tested)

[HKJ]

Hello,

I made the config for Rigol DM858 and DM858E. (E variant not tested)

I have added it, thanks.

[dreamer]

Thank you for your response.
I understand that the protocol supports 2 digits, but the problem is that in the case of voltage, the table displays zeros instead of the actual digits after the decimal point — X.00 regardless of the input voltage.

[jmurray]

Hi HKJ,

Attached are:

• Updated definition file for Giant Force GTH series thermal chambers
• New definition file for Sorensen DHP series power supplies

[HKJ]

Attached are:

• Updated definition file for Giant Force GTH series thermal chambers
• New definition file for Sorensen DHP series power supplies

Thanks, I have added/updated them.

[HKJ]

Thank you for your response.
I understand that the protocol supports 2 digits, but the problem is that in the case of voltage, the table displays zeros instead of the actual digits after the decimal point — X.00 regardless of the input voltage.

I have no idea why it is doing this, try running in debug mode.

[flash2b]

Dear HKJ,

I have made several new definitions for readout (new), relay and temperature devices to strengthen the supported equipment list of TestController.

Eletechsup DM18A01 1digit, DM18B02 2digit, DM18C04 4digit and DM18D06 6digit 7 segment display module
Eletechsup DM56A04 4digit and DM36B06 6digit 7 segment display module
Ebyte EID051 -133,-134,-135 and -138 3digit and EID051 -143,-144,-145 and -148 4digit 7 segment display module
LC Tech LCUS-1 1CH, LCUS-2 2CH, LCUS-4 4CH and LCUS-8 8CH USB relay module
XY MD02 (AHT20), MD02 (SHT20), SHTC3 (SHTC3) and MD02 (SHT40) 1CH Humidity & Temperature transmitter module
Ebyte EID041-G01 and EID041-G01S 1CH Humidity & Temperature transmitter module

The Eletechsup displays can show comma's and signs however they do not support showing floating  point numbers directly. I've written a floating point program in the definition, so that floating numbers are supported anyway. The firmware of the Eletechsup displays is very buggy so I needed a lot of code show floats correctly on the led displays.

The Ebyte display is much more advanced and easier to program, and is also bug-free. Floating point numbers are supported by hardware and in the setup menu you can choose to use firmware (=default) or definition based (like above Eletechsup equivalent) floating point support.

The LCUS-x USB relay modules were originally designed by Shenzhen LC Technology (originals have a PCB with LC on the silk screen), but the defintion should also work for clones (they are offered on many websites, eg. Banggood, Amazon, Aliexpress, Ebay, etc). These are USB relays, that plug straight into an USB port so without an additional adapter. They don't suport bitmask operations natively, but my defintion has code to support it anyway. They use RS232 internally and offer easier USB connection than the Eletechsup 10IOA0xx relay modules I released earlier. I hope now more people can enjoy the Battery Test popup. It is now a very cheap option to own TC controlled relay without any (RS485) additional adapter.

The Humidity & Temperature transmitter modules are all RS485 based and all look very similar but the internal sensor, connection order, and Modbus register and/or input assignment is different. There are more types, but the ones my definitions support are the most common and widely available ones. They are classified as temperature in TC but there main purpose is measure humidity (but there is no #interfaceType in TC for this). They also measure Temperature, which is a big bonus.


With the new readout #interfaceType it is possible to show values on a (small) display. I use it a lot to show temperatures with a little script. You can even make a clock with TC, with #RUNSCRIPTASYNC, very cool:

=var targetDevice="DM36B06"
=var a=1
#while  isLoaded(targetDevice)
=a=substring(date(),8,14)
=setReadoutFloat(targetDevice,a);
#delay 1
#WAITUI
#endwhile

I also added a secondary function to the #interfaceType readout:
#interface setReadoutSI, set readout to show value with SI prefix
#interface getReadoutSI, get the shown value with SI prefix of the readout

This allows the readout to show SI prefix values like 1.00K and 2.34G just like a (modern) DMM.

As a milestone for myself, I now also have used the #driver block for the new relay (LCUS-x) definitions. So now I should pass my "Official #driver license for TestController" ! 

Please add these definitions (and the additional secondary #interface functions in the documentation) to the next release of the wonderful world of TestController.

PS. I will release more definitions in May.

Part of TestController v3.03

[HKJ]

I have made several new definitions for readout (new), relay and temperature devices to strengthen the supported equipment list of TestController.

Eletechsup DM18A01 1digit, DM18B02 2digit, DM18C04 4digit and DM18D06 6digit 7 segment display module
Eletechsup DM56A04 4digit and DM36B06 6digit 7 segment display module
Ebyte EID051 -133,-134,-135 and -138 3digit and EID051 -143,-144,-145 and -148 4digit 7 segment display module
LC Tech LCUS-1 1CH, LCUS-2 2CH, LCUS-4 4CH and LCUS-8 8CH USB relay module
XY MD02 (AHT20), MD02 (SHT20), SHTC3 (SHTC3) and MD02 (SHT40) 1CH Humidity & Temperature transmitter module
Ebyte EID041-G01 and EID041-G01S 1CH Humidity & Temperature transmitter module

The Eletechsup displays can show comma's and signs however they do not support showing floating  point numbers directly. I've written a floating point program in the definition, so that floating numbers are supported anyway. The firmware of the Eletechsup displays is very buggy so I needed a lot of code show floats correctly on the led displays.

The Ebyte display is much more advanced and easier to program, and is also bug-free. Floating point numbers are supported by hardware and in the setup menu you can choose to use firmware (=default) or definition based (like above Eletechsup equivalent) floating point support.

The LCUS-x USB relay modules were originally designed by Shenzhen LC Technology (originals have a PCB with LC on the silk screen), but the defintion should also work for clones (they are offered on many websites, eg. Banggood, Amazon, Aliexpress, Ebay, etc). These are USB relays, that plug straight into an USB port so without an additional adapter. They don't suport bitmask operations natively, but my defintion has code to support it anyway. They use RS232 internally and offer easier USB connection than the Eletechsup 10IOA0xx relay modules I released earlier. I hope now more people can enjoy the Battery Test popup. It is now a very cheap option to own TC controlled relay without any (RS485) additional adapter.

The Humidity & Temperature transmitter modules are all RS485 based and all look very similar but the internal sensor, connection order, and Modbus register and/or input assignment is different. There are more types, but the ones my definitions support are the most common and widely available ones. They are classified as temperature in TC but there main purpose is measure humidity (but there is no #interfaceType in TC for this). They also measure Temperature, which is a big bonus.

More than 20 devices, that is nice, thanks.

With the new readout #interfaceType it is possible to show values on a (small) display. I use it a lot to show temperatures with a little script. You can even make a clock with TC, with #RUNSCRIPTASYNC, very cool:

=var targetDevice="DM36B06"
=var a=1
#while  isLoaded(targetDevice)
=a=substring(date(),8,14)
=setReadoutFloat(targetDevice,a);
#delay 1
#WAITUI
#endwhile

You can add a script in the "Other" menu, that would mean the readout can be used directly, without any scripting.

I also added a secondary function to the #interfaceType readout:
#interface setReadoutSI, set readout to show value with SI prefix
#interface getReadoutSI, get the shown value with SI prefix of the readout

This allows the readout to show SI prefix values like 1.00K and 2.34G just like a (modern) DMM.

Added.

As a milestone for myself, I now also have used the #driver block for the new relay (LCUS-x) definitions. So now I should pass my "Official #driver license for TestController" ! 

Congratulations.
But you get a minus for calling #pgm# definitions from #pgm# definitions, that is not really supported (It works more like a jump, than a call). A definition only has one contents for #pgm#'s, calling one from another will reset the contents for the new #pgm# block, not saving anything from the previous #pgm#

PS. I will release more definitions in May.

I look forward to it.

[flash2b]

With the new readout #interfaceType it is possible to show values on a (small) display. I use it a lot to show temperatures with a little script. You can even make a clock with TC, with #RUNSCRIPTASYNC, very cool:

=var targetDevice="DM36B06"
=var a=1
#while  isLoaded(targetDevice)
=a=substring(date(),8,14)
=setReadoutFloat(targetDevice,a);
#delay 1
#WAITUI
#endwhile

You can add a script in the "Other" menu, that would mean the readout can be used directly, without any scripting.

I find the "Other" menu very confusing. I managed to get it shown, but the programming around it is so different and (imho) not very user friendly. I was not successful in getting a script embedded in the definition file. 

Any timeline for the support in TC around multiple Modbus devices on one address using the slave ID ?

[HKJ]

I find the "Other" menu very confusing. I managed to get it shown, but the programming around it is so different and (imho) not very user friendly. I was not successful in getting a script embedded in the definition file. 

The Enova Gyrfalcon charges uses the other menu, but is very advanced.

For something more simple look in the KeysightU1461A.txt definition.

Very simple:
#otherList
   menuItem[0]="Manual.csv";
   menuItem[1]="Event.txt";

Defines the menu.

The .csv selects the section to process that menu entry, but if there are more entries for the same section, the section must contain if statements to split it out.

.csv calls #otherData
.txt calls #otherText and it will show the return value in a text window.

See more here https://lygte-info.dk/project/TestControllerConfigDevice%20UK.html#The_Other_popup

Any timeline for the support in TC around multiple Modbus devices on one address using the slave ID ?

I have no timeline.