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

[HKJ]

Fully functional definition file for this PS except sequention featature, which is fully covered by Testcontroller. May be in the future :-)

Added, but I changed its name to:
#name GOSSEN-METRAWATT SSP 32 N 32 RU 18 P
That is much better than just GOSSEN-METRAWATT and match the number on the Gossen website. The name/number on the front plate would be even better, but I am not sure what it is, (Maybe SSP 320-32 like your filename)

As you are also using it as handle, I have changed name again:
#name Gossen-Metrawatt SSP 320-32

[flash2b]

What is the difference between printLog() and print() ?

Print() outputs to the internal return buffer, printLog() outputs to the log window.
Commands run on the command line or in the log window will output the internal return buffer to the log window when finished.

Why is print() not in the doc as a function ?

[HKJ]

Why is print() not in the doc as a function ?

It is not a regular function, but more part of the language.
There is some documentation here: https://lygte-info.dk/project/Calculator%20UK.html#Return_values

[pivous]

It looks like Test controller_V3.53 does not support AR-488. The version Test controller_V3.48 wors still well. Am I wrong?

[HKJ]

It looks like Test controller_V3.53 does not support AR-488. The version Test controller_V3.48 wors still well. Am I wrong?

I hope you are wrong, but I do not know it.

[flash2b]

Tried AR488 on TC v3.53 and it still connects fine for me to my Yokogawa's.

Be sure to have you devices powered on before AR488 gets power, or unplug/replug USB.

[KungFuJosh]

I'm on V3.54 and AR488 still works fine.

Code: [Select]

;; Found Keithley 2010 on AR488 A:9

[pivous]

Yes, I was wrong - missing definition file in new version. Many thanks to all!

[HKJ]

Yes, I was wrong - missing definition file in new version. Many thanks to all!

Added, thanks.
This is a bit strange, the supply called GPD-3303S exist in 3 version: GPD-3303S, GPD-3303S II and GPD-3303S III

Another detail:
When making your own definitions, put them in the subfolder in the document folder, that way they will be valid for any installed TC.

[flash2b]

Adding to Cyclotron's report about short commands not being sent — there is a second symptom just above his threshold.

A command body of exactly 4 characters throws instead of failing silently:

    #scpiCmd trigExecute tx E

    java.lang.StringIndexOutOfBoundsException: String index out of range: 5
        at java.lang.String.substring(Unknown Source)
        at dk.hkj.devices.DeviceAscii$TranslatingCommInterface.write(DeviceAscii.java:216)
        at dk.hkj.main.SCPICommand.writeReadInternal(SCPICommand.java:385)
        at dk.hkj.main.SCPICommand.writeRead(SCPICommand.java:408)
        at dk.hkj.main.DeviceInterface.doCommand(DeviceInterface.java:86)

So as far as I can see:

    <= 3 chars   not sent at all, silently   (Cyclotron)
       4 chars   StringIndexOutOfBounds
    >= 5 chars   works

Looks like the write path indexes a fixed offset of 5 without checking the length first.

In my case the command reached the device as nothing, so the instrument did what it was told - nothing - and then reported an error several steps later when the result of that step was needed. Took a while to trace back.

Workaround is easy once you know: make it longer.

    #scpiCmd trigExecute tx E(value)

value is empty when the command is called without one, so the instrument still receives just E.

[HKJ]

Adding to Cyclotron's report about short commands not being sent — there is a second symptom just above his threshold.

A command body of exactly 4 characters throws instead of failing silently:

    #scpiCmd trigExecute tx E

    java.lang.StringIndexOutOfBoundsException: String index out of range: 5
        at java.lang.String.substring(Unknown Source)
        at dk.hkj.devices.DeviceAscii$TranslatingCommInterface.write(DeviceAscii.java:216)
        at dk.hkj.main.SCPICommand.writeReadInternal(SCPICommand.java:385)
        at dk.hkj.main.SCPICommand.writeRead(SCPICommand.java:408)
        at dk.hkj.main.DeviceInterface.doCommand(DeviceInterface.java:86)

Found and fixed, the dump pointed directly to the problem.
I checked for #pgm#, but forgot to check if the string was long enough before doing it.

I had repeated the mistake in 5 drivers and they are all fixed.

[pivous]

Yes, I was wrong - missing definition file in new version. Many thanks to all!

Added, thanks.
This is a bit strange, the supply called GPD-3303S exist in 3 version: GPD-3303S, GPD-3303S II and GPD-3303S III

Another detail:
When making your own definitions, put them in the subfolder in the document folder, that way they will be valid for any installed TC.

The version GPD-3303S III is just upgrade of old versions. It works better with scripts. You can rename it to GPD-3303S and delete the old versions. Sorry for this mess of naming.

[disago]

Hi Hendrik,

Klaus' (kw1) post on TinyGTC groups.io forum motivated me to put together (AI-assisted) the Tiny Devices TinyGTC (https://www.tinydevices.org/wiki/pmwiki.php?n=TinyGTC.Homepage)  driver for TestController.  Find attached the driver to this post.

It has the following features:

- Includes a dummy, so you can try it without the device.
- Setup popup for both inputs, the OUT and REF outputs (including OUT PPS on firmware V1.0-255 or newer), the timebase (lock target, events) and the system (presets, reset, battery, clock).
- Logs both counters at full precision. Each channel logs into a column for its function (frequency, time, phase, ratio, count) with the matching unit (changing the function from TestController rebuilds the columns).
- Loads a counter's whole data buffer into the table from the "Other" menu. So that's the preferred way to get every result (up to 9999 per counter, about 2 s for a full buffer) instead of one value per log interval.
- Logs the GPSDO lock state and the two DACs that steer the reference oscillator, plus their combined value, so you can follow the lock over a long log. In testing, losing the antenna didn't change the lock state (checked on V1.0-104), but the DACs showed the holdover.
- Switches the command port to SCPI mode itself.
- Works around some firmware I stumbled upon: it waits out slow commands so they don't hang the command port, it re-sends an output's frequency when the output is switched on (the firmware can otherwise run it at the wrong frequency), among other details. OUT PPS can still occasionally reset the device.
- Tested with firmware V1.0-104 and V1.0-255 (V1.0-255 or newer recommended, and needed for OUT PPS).

Let me know if you find something that needs adjustment or fixing, happy to do it.

Best,

Diego

[HKJ]

Hi Hendrik,

Klaus' (kw1) post on TinyGTC groups.io forum motivated me to put together (AI-assisted) the Tiny Devices TinyGTC (https://www.tinydevices.org/wiki/pmwiki.php?n=TinyGTC.Homepage)  driver for TestController.  Find attached the driver to this post.

Added, thanks.
I also changed the #name in the stream definition, so they use the same name, except for the stream postfix.

[pivous]

Added only metadef for KORAD KEL103. You can find it in Load devices menu as KORAD KEL103v2. It is more complex alternative to original KORAD KEL103.

[HKJ]

Added only metadef for KORAD KEL103. You can find it in Load devices menu as KORAD KEL103v2. It is more complex alternative to original KORAD KEL103.

Updated, thanks.

[Benleentje]

I am busy with an Zera VCS320 en de setup needs to setup it al at once.
For that i am using the set control and that is not working as i expected.
I see in in de TX data that de end of a line de value's are merged together like 00, 040 24040.

I thought that i could work around it but 240 can be in de range of 0.0 to 359.9 and 40 can be in de range of 40.000 to 319.999

I can not use de individual writes i need to calculate value from all these settings write it back to variables and at last write 6 commands tot de VCS320

Code: [Select]

VCS320: Tx <Program 050 00 1 1 040 1 10 120 24040 40 4030 150 2701 1 1 AA A A AA A AA A A>
VCS320: Script start
VCS320: Script end <>

[HKJ]

I am busy with an Zera VCS320 en de setup needs to setup it al at once.
For that i am using the set control and that is not working as i expected.
I see in in de TX data that de end of a line de value's are merged together like 00, 040 24040.

I thought that i could work around it but 240 can be in de range of 0.0 to 359.9 and 40 can be in de range of 40.000 to 319.999

Code: [Select]

VCS320: Tx <Program 050 00 1 1 040 1 10 120 24040 40 4030 150 2701 1 1 AA A A AA A AA A A>
VCS320: Script start
VCS320: Script end <>

In the documentation I recommend using \x20 for space, other options may be _ or a expression (" ")
A expression can be done line :write: (value+" ")

[Benleentje]

sorry for that i had found it one your website

Code: [Select]

#cmdSetup set Update
:write: cmd
control1 control2 page.control3
delimiter
Know have used \x20 and ik works perfect.

[7tronics]

[rewrite as my feeble mind was thinking about battery charging mode not discharge mode, edited my poorly thought out comments...]

Oh my, was shipped an Owon OEL1515 instead of OEL1515T, so no built-in battery test mode as the ET54A+ series has. We have used testController (tC) with ET54A+ series and just set the Battery Test mode on, set the parameters and go.

For the OEL1515 it looks like we need to setup checking in tC while in CC mode so the test doesnt go beyond a low cutoff voltage. But the OEL1515 seems to only stop when the battery pack reaches BMS cutoff voltage or if monitored externally.

Anyone usjng the OEL series with tC to comment?

[HKJ]

For the OEL1515 it looks like we need to setup checking in tC while in CC mode so the test doesnt go beyond a low cutoff voltage. But the OEL1515 seems to only stop when the battery pack reaches BMS cutoff voltage or if monitored externally.

TC has build-in battery test that will turn off at a specified voltage.

With battery test you do not use CV mode, usually it is CC more, it is also possible to argue for CP mode (TC do not support that in its battery test).

It do not look like TC support OEL15 series devices, only OEL85 series devices. If the 15 series is similar to the 85 series, it is fairly simple to add support for them.

[Benleentje]

I wonder if it possible to add indicator types?
There is only one type and don't like it so much.
I would like plane round cirkels or plane rectangle with a small border.

[HKJ]

I wonder if it possible to add indicator types?
There is only one type and don't like it so much.
I would like plane round cirkels or plane rectangle with a small border.

I will put it on the list of good ideas.

[flash2b]

I have created a large definition to support all ME31 modules (9 in total) from Ebyte. This definition is my 31st and the largest to date 105kb with 282 created scpiCmd's. It was fun writing it and it has been tested on all meta's using a simulator device.

It is the first definition that uses the #cmdSetup advcomboboxHot control !

This is my first definition with an Other Menu and also using my color scheme for the channels and graphs !

The models that are covered:

- ME31-Model       DI   AI   DO  AO
- ------------------  ---  ---  ---  ---
- ME31-XAXA0404    -    4    -    4
- ME31-XXXA0006    -    -    -    6
- ME31-XAXX0600    -    6    -    -
- ME31-XXAX0060    -    -    6    -
- ME31-XAAX0440    -    4    4    -
- ME31-AXXX8000    8    -    -    -
- ME31-AXAX4040    4    -    4    -
- ME31-AAAX2240    2    2    4    -
- ME31-AAAX4220    4    2    2    -

The modules support a combination of DI (digital input), AI (analog input), DO (digital output) and AO (analog Output) that map to TC's Input, AInput, Relay and AOutput #interfaceType.

The modules can also be used stand alone since they have an OLED display and communication with TC can be RS485 or Ethernet.

Please add them to the next release of TestController.

[ Attachment Invalid Or Does Not Exist ]

Part of TC v3.57

[flash2b]

I have updated my definition for the XEXX0600 / XEXX0800 K-type and XDXX0400 / XDXX0800 PT100/PT1000 Temperature Acquisition modules from Ebyte.

The XDXX now also supports PT1000 sensors.

Also included is my one click graph setup and coloring using the Other Menu which saves a lot of time !

Please add them to the next release of TestController.
[ Attachment Invalid Or Does Not Exist ]

Part of TC v3.57