Program that can log from many multimeters.

[HKJ]

If Not :
How easy I can be added, I know Java so I can participate in this if needed

TC do not directly support RC chargers or their protocol, but has a lot of customizable drivers that can be adapted without any Java programming.

This one looks usable for the device:
https://lygte-info.dk/project/TestControllerConfigDevice2%20UK.html#Binary_with_fixed_communication_blocks_(Block)
You will have to use the configuration for streaming data

[Hexley]

V2.31 is up.
Fix of a some bugs and some additions.
   Added: Variable for control indicator & indicatorInt

I'm not having much luck with the indicator state variable.
A code snippet is below. While the indicator itself turns on and off as expected, the radio control below the indicator -- which should be enabled only when the indicator is off -- does not track the state of the indicator variable.
What am I missing?

Code: [Select]

#cmdSetup indicator Trigger Ch2Setup
:read: :FUNC?
:string:
Coupled_to_Channel_1 match(unQuote(value),"TINT") green
:updatemodechange:

#cmdSetup radio Trigger_Level Ch2Setup
:read: :EVEN2:LEV:ABS?
:write: :EVEN2:LEV:ABS #
Auto 1
Manual 0
:enable: Ch2Setup.Trigger!=1
:updatemodechange:


[HKJ]

I'm not having much luck with the indicator state variable.
A code snippet is below. While the indicator itself turns on and off as expected, the radio control below the indicator -- which should be enabled only when the indicator is off -- does not track the state of the indicator variable.
What am I missing?

Two points:
All :...: must be place before other parameters.
Use :enable: displayVar(split(getVarList(1),"\n"));" to see the actual value of the variables, it is not 1

[Hexley]

Two points:
All :...: must be place before other parameters.
Use :enable: displayVar(split(getVarList(1),"\n"));" to see the actual value of the variables, it is not 1

Thanks for the tip about the "::" statement placement. I fixed that.
But still no luck with the :enable: logic.
First, I added the displayVar snippet. That produced the list shown in the attachment.
Next, I tried using that exact sequence in the enable section, like this:

Code: [Select]

:enable: Ch2Setup.Trigger!={string}match(unQuote(value),\x22TINT\x22)But that triggered an error from Java, that looked like this:

Code: [Select]

Exception in thread "AWT-EventQueue-0" dk.hkj.script.ProgramExceptions$InvalidException: <{> is not a valid token
Ch2Setup.Trigger!={____<----____string}match(unQuote(value),\x22TINT\x22)
        at dk.hkj.script.Program.nextTokenWhiteSpace(Program.java:646)
        at dk.hkj.script.Program.nextToken(Program.java:673)
        at dk.hkj.script.Script.next(Script.java:102)
        at dk.hkj.script.Script.parseCompare(Script.java:531)
        at dk.hkj.script.Script.parseLogical(Script.java:561)
        at dk.hkj.script.Script.parseQuestionMark(Script.java:587)
        at dk.hkj.script.Script.parseExpression(Script.java:612)
        at dk.hkj.script.Script.expression(Script.java:1220)
        at dk.hkj.devices.SetupFormats.calcEnable(SetupFormats.java:344)
        at dk.hkj.devices.SetupFormats.enableItems(SetupFormats.java:332)
        at dk.hkj.main.PopupSetupSelection.initialSync(PopupSetupSelection.java:125)
        at dk.hkj.main.PopupSetupSelection.timerUpdate(PopupSetupSelection.java:131)
        at dk.hkj.main.PopupSetupSelection.access$3(PopupSetupSelection.java:129)
        at dk.hkj.main.PopupSetupSelection$3.actionPerformed(PopupSetupSelection.java:88)
        at javax.swing.Timer.fireActionPerformed(Unknown Source)
        at javax.swing.Timer$DoPostEvent.run(Unknown Source)
        at java.awt.event.InvocationEvent.dispatch(Unknown Source)
        at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
        at java.awt.EventQueue.access$500(Unknown Source)
        at java.awt.EventQueue$3.run(Unknown Source)
        at java.awt.EventQueue$3.run(Unknown Source)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source)
        at java.awt.EventQueue.dispatchEvent(Unknown Source)
        at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
        at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
        at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
        at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
        at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
        at java.awt.EventDispatchThread.run(Unknown Source)

So I removed the offending "{string}" token, changing the line to this:

Code: [Select]

:enable: Ch2Setup.Trigger!=match(unQuote(value),\x22TINT\x22)
That generated a new error:

Code: [Select]

Exception in thread "AWT-EventQueue-0" dk.hkj.script.ProgramExceptions$UnknownException: Variable not found value
Ch2Setup.Trigger!=match(unQuote(value)____<----____,\x22TINT\x22)
        at dk.hkj.script.Script.getVar(Script.java:73)
        at dk.hkj.script.Script.parseValue(Script.java:281)
        at dk.hkj.script.Script.parseBitOp(Script.java:316)
        at dk.hkj.script.Script.parseProduct(Script.java:388)
        at dk.hkj.script.Script.parseSum(Script.java:470)
        at dk.hkj.script.Script.parseCompare(Script.java:525)
        at dk.hkj.script.Script.parseLogical(Script.java:561)
        at dk.hkj.script.Script.parseQuestionMark(Script.java:587)
        at dk.hkj.script.Script.parseExpression(Script.java:612)
        at dk.hkj.script.Script.parseParamList(Script.java:123)
        at dk.hkj.script.Script.parseValue(Script.java:267)
        at dk.hkj.script.Script.parseBitOp(Script.java:316)
        at dk.hkj.script.Script.parseProduct(Script.java:388)
        at dk.hkj.script.Script.parseSum(Script.java:470)
        at dk.hkj.script.Script.parseCompare(Script.java:525)
        at dk.hkj.script.Script.parseLogical(Script.java:561)
        at dk.hkj.script.Script.parseQuestionMark(Script.java:587)
        at dk.hkj.script.Script.parseExpression(Script.java:612)
        at dk.hkj.script.Script.parseParamList(Script.java:123)
        at dk.hkj.script.Script.parseValue(Script.java:267)
        at dk.hkj.script.Script.parseBitOp(Script.java:316)
        at dk.hkj.script.Script.parseProduct(Script.java:388)
        at dk.hkj.script.Script.parseSum(Script.java:470)
        at dk.hkj.script.Script.parseCompare(Script.java:532)
        at dk.hkj.script.Script.parseLogical(Script.java:561)
        at dk.hkj.script.Script.parseQuestionMark(Script.java:587)
        at dk.hkj.script.Script.parseExpression(Script.java:612)
        at dk.hkj.script.Script.expression(Script.java:1220)
        at dk.hkj.devices.SetupFormats.calcEnable(SetupFormats.java:344)
        at dk.hkj.devices.SetupFormats.enableItems(SetupFormats.java:332)
        at dk.hkj.main.PopupSetupSelection.initialSync(PopupSetupSelection.java:125)
        at dk.hkj.main.PopupSetupSelection.timerUpdate(PopupSetupSelection.java:131)
        at dk.hkj.main.PopupSetupSelection.access$3(PopupSetupSelection.java:129)
        at dk.hkj.main.PopupSetupSelection$3.actionPerformed(PopupSetupSelection.java:88)
        at javax.swing.Timer.fireActionPerformed(Unknown Source)
        at javax.swing.Timer$DoPostEvent.run(Unknown Source)
        at java.awt.event.InvocationEvent.dispatch(Unknown Source)
        at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
        at java.awt.EventQueue.access$500(Unknown Source)
        at java.awt.EventQueue$3.run(Unknown Source)
        at java.awt.EventQueue$3.run(Unknown Source)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source)
        at java.awt.EventQueue.dispatchEvent(Unknown Source)
        at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
        at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
        at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
        at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
        at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
        at java.awt.EventDispatchThread.run(Unknown Source)

Any thoughts?

[Edit: I should also mention that I tried:

Code: [Select]

:enable: Ch2Setup.Trigger!="TINT"That gave no Java error, but the :enable: does not change states.]

[HKJ]

But still no luck with the :enable: logic.

I looked at bit more on it and that indicator is a bit tricky to handle, because there is no well defined field with its current value.

To get around that I went back to multiple fields for the variable in this new .jar file:
http://lygte-info.dk/pic/Projects/TestController/TestController.jar

There are four vars present:
.on for color turned on.
.color for actual color, see my initial post about format.
.value actual value, this is the same as now and is not exactly the best to match on in this case.
.name the name at the start of the line

name, value and color will contain the first line when no match is found and on will be 0
In all other cases they will contain the matching line and on will be 1.

In the var list "{string}" is the actual type of the variable, the rest of the line is the contents. For strings you must put quotes around the contents to match.

[Hexley]

.on for color turned on.

That works perfectly, thanks HKJ.

Except for one side issue with :enable: -- it does not seem to be responding when its associated control is updated by another control.

The code below shows that the indicator control sends an update to the radio button control. The radio control is enabled/disabled according to the state of the indicator, using your new ".on" variable in an "enable" statement. So this code should cause the radio button's enablement to track the state of the indicator.

What I see is slightly different. (1) The radio button's enable logic works when the Setup window is initially loaded. At that point the radio button is enabled or disabled according to the state of the indicator, as expected.

But (2) if the mode is then changed. the indicator responds correctly but the radio button stays in its initial state. It seems that its "enable" statement is not firing or something. It is necessary to close and re-open the setup window to get the radio button's "enable" logic to work.

Any suggestions to try?

Code: [Select]

#cmdSetup indicator Trigger Ch2Setup
:read: :FUNC?
:string:
:updatemodechange:
:update: Ch2Setup.Trigger_Level
Coupled_to_Channel_1 match(unQuote(value),"TINT") green

#cmdSetup radio Trigger_Level Ch2Setup
:read: :EVEN2:LEV:ABS?
:write: :EVEN2:LEV:ABS #
:enable: Ch2Setup.Trigger.on!=1
Auto 1
Manual 0

[HKJ]

Any suggestions to try?

Updates are done when a control writes a setting to a device and because the indicator newer writes a setting, it never calls update.

Maybe I need to change that for the indicator, i.e. it will send a update if the state changes and a :update: tag is present (This will also include itself, reading its own state again).

[Hexley]

Thanks, HKJ.Sounds like a good solution.
No hurry, so I'll just wait until you resume updating TC after the New Year.
Happy Holidays.
Hexley

[HKJ]

Thanks, HKJ.Sounds like a good solution.
No hurry, so I'll just wait until you resume updating TC after the New Year.

I will not make official releases, but test updates will still be made when needed.

I hope this updated jar file fixes your problem (It is V2.33):
http://lygte-info.dk/pic/Projects/TestController/TestController.jar

[Hexley]

I hope this updated jar file fixes your problem (It is V2.33):

That works perfectly. Thanks, HKJ.

One last question about the indicator control: is it possible to suppress the display of either the control label or the parameter text field?

Right now, it displays two text fields before the actual indicator, as shown in Pic 1.

Is there a work-around to make it show only one field before the indicator? Either the control parameter (Pic 2) or the control name (Pic 3) would be fine.

This is a "nice-to-have" not a "have-to-have" feature, of course. But I thought it could not hurt to ask...
     

[HKJ]

One last question about the indicator control: is it possible to suppress the display of either the control label or the parameter text field?

You can always define the label (second name) as _ (Underscore), it many places it will be replace with a space.

[Messtechniker]

May I recommend for the "Current values" display, user definable background colours.
Might help readability in the case shown below where it would be of advantage to highlight every third line.

[T3TRIS]

Hello everyone, first time posting here. This thread looks like it's the end-all-be-all reference for the Test Controller app.
I just purchased an East Tester ET5410A+ 400W Electronic Load to do some detailed capacity tests on custom built 12V lithium battery packs. The idea is to accelerate capacity testing (currently done at 150W) and chart the discharge so I can set better state of charge (SOC) estimate value within the battery's battery management system (BMS). Currently I can enter voltage values for every 10% of SOC from 0% to 100%. The tedious way to do this is by estimating how long the test would be, divide that by 10 and measure voltage at each time segment. That'd be a royal today as my battery test takes around 26hrs at 150W. Doing the same would be easier with the ET5410 though still a 10hr process, checking every hour.
That's when I learned about the Test Controller app. I'm working on a Mac platform. I've downloaded the app and Java. The app seems to open properly though I can't load any test device. I've also connected the ET5410 to the Mac using a USB cable but am failing at adding a device. I see that there is a folder full of devices in the Test Controller app folder, but I'm unsure what to do with these. I tried loading the ET5410A.txt file in the first page but that doesn't do much. In the "Load Devices" section, I tried following the instructions on the App's website but I can't seem to find out how to load the device. The Load Device page stay blank/empty and the little pull-down menu in the lower left corner never shows any option.
I've tried 2 different Macs, both with JAVA (a Mac mini M1 and a 2013 MacBook Pro), and I tried all the USB ports to no avail.
I've searched this thread for keywords relating to "Mac," "East Tester," "ET54**" and "Load Device" but can't find any information that I can utilize.
I'm obviously no expert in this field but I figured adding some simple automation and graph charting of discharge wouldn't be too difficult. Hopefully I'm just missing something simple and stupid as is often the case.
Any input would be appreciated!
Thanks!

[HKJ]

May I recommend for the "Current values" display, user definable background colours.
Might help readability in the case shown below where it would be of advantage to highlight every third line.

I do not really understand you. Every fourth line is a different color to make it easier when many lines are shown, I use that on most table displays.

[HKJ]

I'm working on a Mac platform. I've downloaded the app and Java. The app seems to open properly though I can't load any test device. I've also connected the ET5410 to the Mac using a USB cable but am failing at adding a device. I see that there is a folder full of devices in the Test Controller app folder, but I'm unsure what to do with these. I tried loading the ET5410A.txt file in the first page but that doesn't do much. In the "Load Devices" section, I tried following the instructions on the App's website but I can't seem to find out how to load the device. The Load Device page stay blank/empty and the little pull-down menu in the lower left corner never shows any option.

The device folder is the definitions used by TestController, they are loaded each time test controller is started and is supposed to be accessible on the pull-down menu on the "Load Devices" page.
As long as they are not, there is something wrong with your installation, I cannot help your with that (I do not have a Mac), but I hope some of the Mac users can.

To load devices you must find them in the pull-down menu and add them to the "Load Devices" page, set the correct serial port or ip-address and then checkmark them, pressing "Reconnect" or restarting TestController will then load them and connect to the device if it is connected and turned on.

[Messtechniker]

May I recommend for the "Current values" display, user definable background colours.
Might help readability in the case shown below where it would be of advantage to highlight every third line.

I do not really understand you. Every fourth line is a different color to make it easier when many lines are shown, I use that on most table displays.

To clarify: I mean in this case highlighting each line beginning with "Temperature".
That would be every third line in this particular case.

[T3TRIS]

Ok! made some progress, thanks!
Looks like the .JAR file I was using just wasn't fishing the .TXT files from the right folder. I copied the .TXT file for the ET5410A+ device in the device folder and it showed up in the pull down menu!
However, now I'm stuck at the serial port or IP address. I've done some research on pulling such info using Terminal (on Mac) and the closest I got to getting serial port information is something that resembles this:

Code: [Select]

tty.usbserial-1410When I connect the device to the other USB port, the terminal command returns

Code: [Select]

tty.usbserial-1420. So I imagine my USB serial port numbers are either 1410 or 1420 depending on the USB port I chose. Neither seem to work on the Test Controller App and I keep getting this message when trying to reconnect the device:

Code: [Select]

;; USB Serial (Dial-In) (tty.usbserial-1410) Device ET5420 do not match: ET5410A+,V1.00.2213.016,09702232111,V1.00.2213.016
;; Dummy Device ET5420 do not match: null,,,I'm going to keep digging and see if I can find out more on USB serial number or device IP addresses on Mac. Thanks again for the help!

[modz786]

Hi I was curious how you amassed so many supported meters?
Is there a central repository of specs that you scanned but not physically tested each one?

Thanks

[HKJ]

To clarify: I mean in this case highlighting each line beginning with "Temperature".
That would be every third line in this particular case.

When I made TC I played with highlighting every 2-3-4-5 line and I liked every fourth line best, every third is also a good option, but I do not believe it is significant enough for a configuration option.
I can see in your case it would be nice to have first line of every device highlighted and that is another proposal and I may thing about that.

[HKJ]

Ok! made some progress, thanks!
Looks like the .JAR file I was using just wasn't fishing the .TXT files from the right folder. I copied the .TXT file for the ET5410A+ device in the device folder and it showed up in the pull down menu!

TC looks for the device files in two locations:
1) A subfolder to Jave working directory (This is supposed to be the directory where the .jar file is placed), called "Devices"
2) A subfolder to your home folder called TestController/Devices

When you are finished with troubleshooting I would be thankful if you can write a short text I can add to my install page:
lygte-info.dk/project/TestControllerInstalling UK.html

However, now I'm stuck at the serial port or IP address. I've done some research on pulling such info using Terminal (on Mac) and the closest I got to getting serial port information is something that resembles this:

Code: [Select]

tty.usbserial-1410When I connect the device to the other USB port, the terminal command returns

Code: [Select]

tty.usbserial-1420. So I imagine my USB serial port numbers are either 1410 or 1420 depending on the USB port I chose. Neither seem to work on the Test Controller App and I keep getting this message when trying to reconnect the device:

Code: [Select]

;; USB Serial (Dial-In) (tty.usbserial-1410) Device ET5420 do not match: ET5410A+,V1.00.2213.016,09702232111,V1.00.2213.016
;; Dummy Device ET5420 do not match: null,,,I'm going to keep digging and see if I can find out more on USB serial number or device IP addresses on Mac. Thanks again for the help!

Try right clicking the mouse when you are editing the address field (You must be in edit mode, just selecting the field is not enough), this is supposed to show a list of serial ports.

[HKJ]

Hi I was curious how you amassed so many supported meters?
Is there a central repository of specs that you scanned but not physically tested each one?

A couple of ways.
I have many multimeter:
https://lygte-info.dk/info/DMMReviews.html
https://lygte-info.dk/info/DMMHigh-end%20UK.html

Users have made definitions and done testing, sometimes with help/programming from my end. If I get a couple of ascii hexdump of a protocol and what the display shows, I can often make the protocol and then the user checks it against the meter to verify it is working (This may go back and forth a couple of times to get all ranges/modes to work).

Meters that is supposed to use same protocol as a already supported meter is often listed. That is how I made the Keysight DMM's, I have the top models and the lesser models in each series generally use same protocol.
This also means there a some meters (and other devices) in the list that may not work, but hopeful not many.

[T3TRIS]

TC looks for the device files in two locations:
1) A subfolder to Jave working directory (This is supposed to be the directory where the .jar file is placed), called "Devices"
2) A subfolder to your home folder called TestController/Devices

When you are finished with troubleshooting I would be thankful if you can write a short text I can add to my install page:
lygte-info.dk/project/TestControllerInstalling UK.html

Will do! This helps

Try right clicking the mouse when you are editing the address field (You must be in edit mode, just selecting the field is not enough), this is supposed to show a list of serial ports.

This is also helpful and allowed for a little more progress! Sorry if I missed this trick somewhere in the information shared by the way. Anyhow, when in edit mode, the right-click indeed brings up different ports. It gave me 2 options for the USB port (Dial-in and non Dial-in). I would select one of the USB option, disable and re-enable the device and click reconnect. It still tells me it did not find a match.

I tried both USB options on both USB ports, I also checked and unchecked the "Scan serial port" just for the heck of it. Same issue...

[HKJ]

I tried both USB options on both USB ports, I also checked and unchecked the "Scan serial port" just for the heck of it. Same issue...

Looks like both ports work, but you have selected the wrong device. Select a "ET5410A+" and try again.
The "Scan serial ports" is mostly for Arduino stuff, it will only work for devices at 9600 baud or without baud (Like ATMega32U4).

[T3TRIS]

Looks like both ports work, but you have selected the wrong device. Select a "ET5410A+" and try again.
The "Scan serial ports" is mostly for Arduino stuff, it will only work for devices at 9600 baud or without baud (Like ATMega32U4).

The ET5410A+ is the only .TXT file I copied into the device folder... There is a "note" about it that mentions the ET5410A+ identifies itself as an ET5420 (see attached screenshot).

In any case, I copied the "East Tester ET5420.txt" and "East Tester ET5410.txt" files into the device folder and they now show up in the pull-down list (thanks again for that tip by the way). I tried the same approach with the 2 additional devices and am getting the same messages.

I don't know why it says ";; Dummy Device ET5420 do not match: null,,,"
I have never been able to load a virtual device either by the way.

[HKJ]

The ET5410A+ is the only .TXT file I copied into the device folder... There is a "note" about it that mentions the ET5410A+ identifies itself as an ET5420 (see attached screenshot).

In any case, I copied the "East Tester ET5420.txt" and "East Tester ET5410.txt" files into the device folder and they now show up in the pull-down list (thanks again for that tip by the way). I tried the same approach with the 2 additional devices and am getting the same messages.

I don't know why it says ";; Dummy Device ET5420 do not match: null,,,"
I have never been able to load a virtual device either by the way.

Now I remember, I got the ET5410A file from somebody where the ET5410A+ identified itself as ET5420. This bug has obvious been fixed in yours.

Try editing the ET5410A file and change:
#idString ET5420
to
#idString ET5410A+