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

[KungFuJosh]

I think you're probably using the wrong driver version, or it's not compatible with your firmware version.

Thanks,
Josh

What Driver are you using?
I am using the ch34 driver that they supply.

Sorry, I meant Definition in TC, not Driver in Windows.

Remove your device in the Load devices page, and readd it. Make sure you choose the ET5410A+ version, not the plain ET5410, which is what looks like the one you have loaded.

Also, uncheck the scan serial ports as HKJ mentioned above.

Thanks,
Josh

[Dread]

Also with all this tinkering I have also picked up some kind of device on Com5 that I cannot get rid of. it does not show up under devices. 

Check the "Load device"s page, you must have check marked more devices or "Scan serial ports".

Yes I have it ticked because if I don't tick it and just pick the ET5410A from the list, it does not connect.

If I rem out all the ET5420 lines the file still will not load but if I allow TC to scan ports it does load ET5410A.

[Dread]

Sorry, I meant Definition in TC, not Driver in Windows.

Remove your device in the Load devices page, and readd it. Make sure you choose the ET5410A+ version, not the plain ET5410, which is what looks like the one you have loaded.

Also, uncheck the scan serial ports as HKJ mentioned above.

Thanks,
Josh

Hi Josh
As you can in my post above to HKJ  i have tried it without the the Scan option and it loads nothing.
I am using the ET5410A+ file with the Scan is turned on it loads the file but with that error on the 5420.
I know the scan is picking up the right file because the ET5410A+ file is the only one that has some references in it to the ET5420.   The older ET5410 file has no lines in it that refer to the 5420.

At this point it seems like the SCPI command file for the ET5410A+ has some errors in it.
here is the TC Debug and what happens if I don't select Scan Ports.

[flash2b]

Your port Type = Dummy and should be Serial  or Serial fixed baudrate and Address should contain you COM + port no.

If your COM port is 13, you should put COM13 in address.

[HKJ]

At this point it seems like the SCPI command file for the ET5410A+ has some errors in it.
here is the TC Debug and what happens if I don't select Scan Ports.

As TC shows in one of the first screenshots you posted it is on com14 type that in the address field.

[Dread]

At this point it seems like the SCPI command file for the ET5410A+ has some errors in it.
here is the TC Debug and what happens if I don't select Scan Ports.

As TC shows in one of the first screenshots you posted it is on com14 type that in the address field.

I tried a different USB port, a USB-2 port just in case and it changed the Comm to 13.

[HKJ]

I tried a different USB port, a USB-2 port just in case and it changed the Comm to 13.

But you cannot just type 13, you must type com13 on windows.

[Dread]

Your port Type = Dummy and should be Serial  or Serial fixed baudrate and Address should contain you COM + port no.

If your COM port is 13, you should put COM13 in address.

YES 
That was the main issue.  Once I did that it still would not load but it was different because I was now seeing the Serial number of the Device showing up in the command window but the lines for the ET5420 were still causing issues.

I Rem out those lines and now it works perfectly 

Thank you Flash2b, HKJ and KungFuJosh for all the Help


HKJ you need to edit the ET5410A+ file that is included and Rem out those lines
For anyone else who has this issue, it needs to look like this.

;------------------------------------------------------------
; Devices
;------------------------------------------------------------

; Buggy FW which response with ET5420
;#metadef
;#idString ET5420
;#name     East Tester ET5410A+
;#handle   ET5410A
;#port     com

#metadef
#idString ET5410A+
#name     East Tester ET5410A+
#handle   ET5410A
#port     com

#meta
#idString ET5410A+
#name     East Tester ET5410A+
#handle   ET5410A
#port     com

#driver   SCPIx

[KungFuJosh]

At this point it seems like the SCPI command file for the ET5410A+ has some errors in it.
here is the TC Debug and what happens if I don't select Scan Ports.

Disable scan ports. It's detecting incorrectly, and applying the wrong definition file. Detecting the model incorrectly does nothing for you if the definition doesn't work.

I've attached a work-in-progress of the modified definition for newer ET5410A+ and ET5420A+ models. This is not ready for publication yet, but should probably work for you as it is.

You might need to delete, or comment out the non-functional metadef in the other files if you can't get this version to show up. The device handle will now be ET5410AP if it's working correctly.

Thanks,
Josh

[Dread]

At this point it seems like the SCPI command file for the ET5410A+ has some errors in it.
here is the TC Debug and what happens if I don't select Scan Ports.

Disable scan ports. It's detecting incorrectly, and applying the wrong definition file. Detecting the model incorrectly does nothing for you if the definition doesn't work.

I've attached a work-in-progress of the modified definition for newer ET5410A+ and ET5420A+ models. This is not ready for publication yet, but should probably work for you as it is.

You might need to delete, or comment out the non-functional metadef in the other files if you can't get this version to show up. The device handle will now be ET5410AP if it's working correctly.

Thanks,
Josh

Hi Josh
I would love to test it.
It might have other features I need.

[KungFuJosh]

Hi Josh
I would love to test it.
It might have other features I need.

I reuploaded it, and it's actually attached now. The board is weird with attachments sometimes. 

It doesn't have anything new yet; I only made it work and removed unneeded stuff. Let me know what features you need, and I'll see if I can implement them.

[Dread]

So here it is when it loads up properly.
The only issue I have left is that the logging does not start automatically when I do the battery discharge test.

Also the Mode button and access to changing the Loads Modes is always greyed out.
Is that normal?

[KungFuJosh]

So here it is when it loads up properly.
The only issue I have left is that the logging does not start automatically when I do the battery discharge test.

Also the Mode button and access to changing the Loads Modes is always greyed out.
Is that normal?

Try my version. But yes, the mode button will stay greyed out (for now).

Also, update your TC version. The newest version might have features you're missing out on.

[Dread]

Hi Josh
I would love to test it.
It might have other features I need.

I reuploaded it, and it's actually attached now. The board is weird with attachments sometimes. 

It doesn't have anything new yet; I only made it work and removed unneeded stuff. Let me know what features you need, and I'll see if I can implement them.

Thanks Josh I will give it a test tonight and let you know.

[Silent Runner]

I am trying to log measurement devices using TC (version dated 02/02/2026), but I have not been able to connect to the devices (Windows 10 Pro, connected via a USB cable to a USB 2.0 port on an X370 motherboard).

1. Atorch DL24 (new version with additional USB-C power socket):
When connecting the switched-on device, the sound for a new external device plays in Windows. In Device Manager, I can only find a new entry under ‘Human Interface Devices’ labelled ‘USB Input Device’. The location is ‘Port_#0016.Hub_#0001’. In the details, there is nothing to indicate the DL24.

In TC, I selected the Atorch DL24 in ‘Load devices’, entered “com16” (or com9) as the address and ticked ‘Enabled’. When I click on ‘Reconnect’, I end up in the “Commands” tab with the default entry ‘;; Use ’Load devices‘ page ...’
What am I doing wrong?

2. Agilent U1253A
Connection via an old U1177A on the same USB port. This gives me the entry ‘PL2303HXA PHASED OUT SINCE 2012....’ under ‘Ports (COM & LPT)’ in Device Manager. Due to known issues, I had installed an old driver (3.3.3.102) some time ago. This is apparently quickly replaced by Windows with driver version 3.8.40.0. After reselecting the old driver, no further errors are reported. Device Manager now shows Porlific USB-to-Serial Comm Port (COM9). However, the location is still ‘Port_#0016.Hub_#0001’.

When I select the Keysight U1253A in TC and enter the address com9 (or com16), I get the message ‘;; USB-Serial Controller (COM9) Did not find any match for: Agilent Technologies,U1253A,MY511xxxxx,V1.20’
Does TC only support the Keysight U1253A and not the Agilent U1253A? I believe the U1253A was only sold under the Agilent name. The U1253B was then marketed as Keysight. In the Devices folder of the TC installation, I can’t find a file named either Agilent 125XA or Keysight U125XA. Is something missing?

Edit: Found the file KeysightDMMs.txt in the Devices-Folder, edited the entry

#metadef Agilent U1272A
#idString Keysight Technologies,U1253A,
#name Keysight U1253A
#handle K1253
#sections U125xA

to
#metadef Agilent U1272A
#idString Agilent Technologies,U1253A,
#name Agilent U1253A
#handle K1253
#sections U125xA

Now there is a Agilent U1253A in the select-list, but it doesn't work.

[CaptainBucko]

Like to share my latest Batterytest scripts.

@HKJ This updated Battery test script from Pukker (Oct-2025) "Battery Test with IntResistance Check AutosaveTussen.txt" also needs an update to ATorchPX100Devices.txt with the following in order to operate:

; These functions will read the actual values
; These can either contain a number that will reference to a data column or they can contain a command to read the value
#interface readVoltage 0
#interface readCurrent 1
#interface readCapacity 2
#interface readEnergy 3
#interface readTemperature 4

Tnx
CptB

[HKJ]

Like to share my latest Batterytest scripts.

@HJK This updated Battery test script from Pukker (Oct-2025) "Battery Test with IntResistance Check AutosaveTussen.txt" also needs an update to ATorchPX100Devices.txt with the following in order to operate:

; These functions will read the actual values
; These can either contain a number that will reference to a data column or they can contain a command to read the value
#interface readVoltage 0
#interface readCurrent 1
#interface readCapacity 2
#interface readEnergy 3
#interface readTemperature 4

Tnx
CptB

I have added it, thanks.

[HKJ]

I am trying to log measurement devices using TC (version dated 02/02/2026), but I have not been able to connect to the devices (Windows 10 Pro, connected via a USB cable to a USB 2.0 port on an X370 motherboard).

1. Atorch DL24 (new version with additional USB-C power socket):
When connecting the switched-on device, the sound for a new external device plays in Windows. In Device Manager, I can only find a new entry under ‘Human Interface Devices’ labelled ‘USB Input Device’. The location is ‘Port_#0016.Hub_#0001’. In the details, there is nothing to indicate the DL24.

In TC, I selected the Atorch DL24 in ‘Load devices’, entered “com16” (or com9) as the address and ticked ‘Enabled’. When I click on ‘Reconnect’, I end up in the “Commands” tab with the default entry ‘;; Use ’Load devices‘ page ...’
What am I doing wrong?

Instead of type a command port, press F2 to enter edit mode in the address field, the right click to see what comport are defined.

2. Agilent U1253A
Connection via an old U1177A on the same USB port. This gives me the entry ‘PL2303HXA PHASED OUT SINCE 2012....’ under ‘Ports (COM & LPT)’ in Device Manager. Due to known issues, I had installed an old driver (3.3.3.102) some time ago. This is apparently quickly replaced by Windows with driver version 3.8.40.0. After reselecting the old driver, no further errors are reported. Device Manager now shows Porlific USB-to-Serial Comm Port (COM9). However, the location is still ‘Port_#0016.Hub_#0001’.

When I select the Keysight U1253A in TC and enter the address com9 (or com16), I get the message ‘;; USB-Serial Controller (COM9) Did not find any match for: Agilent Technologies,U1253A,MY511xxxxx,V1.20’
Does TC only support the Keysight U1253A and not the Agilent U1253A? I believe the U1253A was only sold under the Agilent name. The U1253B was then marketed as Keysight. In the Devices folder of the TC installation, I can’t find a file named either Agilent 125XA or Keysight U125XA. Is something missing?

Edit: Found the file KeysightDMMs.txt in the Devices-Folder, edited the entry

#metadef Agilent U1272A
#idString Keysight Technologies,U1253A,
#name Keysight U1253A
#handle K1253
#sections U125xA

to
#metadef Agilent U1272A
#idString Agilent Technologies,U1253A,
#name Agilent U1253A
#handle K1253
#sections U125xA

Now there is a Agilent U1253A in the select-list, but it doesn't work.

Try only changing the #name string, not the #idString and see if that makes it work.

[KungFuJosh]

Attached is an updated version of the Magnova definition which adds support for the hardware counters and DVM functions.

I have done basic testing, but if somebody finds a bug/issue, please let me know.

Thanks,
Josh

ETA: Found a bug, will update shortly.

[HKJ]

Attached is an updated version of the Magnova definition which adds support for the hardware counters and DVM functions.

Updated, thanks.

[KungFuJosh]

The attached new version appears to be happy.

As always, if somebody else finds a bug, please let me know.

Thanks,
Josh

[KungFuJosh]

Updated, thanks.

There was a bug in that one. Please grab the new one in my post above.

Thanks,
Josh

[HKJ]

There was a bug in that one. Please grab the new one in my post above.

Ok, updated again and thanks again.

[Silent Runner]

Instead of type a command port, press F2 to enter edit mode in the address field, the right click to see what comport are defined.

Nothing happens, when I right click while editing the address field. The Electronic Load Test Software by Atorch also doesn't see the DL24. Do I need a driver for the DL24? Under which entry is the DL24 usually listed in Device Manager?

Edit: A post by @1RandomUser led me to the BW150 software from Atorch  (http://en.atorch.cn/NewsDetail.aspx?ID=84). It runs smoothly on the BW150 even without a firmware update. Is this because the BW150 – and presumably the newer DL24 as well – cannot be accessed via a UART interface? Can the BW150 be supported by TC?

Try only changing the #name string, not the #idString and see if that makes it work.

Unfortunately, nothing has changed.

[Dread]

I reuploaded it, and it's actually attached now. The board is weird with attachments sometimes. 

It doesn't have anything new yet; I only made it work and removed unneeded stuff. Let me know what features you need, and I'll see if I can implement them.

Josh I still have not gotten to your file yet.  I had to test two batteries for a project and did not realize that it would take 16 hours to test each battery.

BTW when a battery load test is performed is the graphing and data capture supposed to start when I turn on Load and end when the load voltage gets to cutoff?
I have to be doing it manually.