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

[HKJ]

I will test that tomorrow for the Ascii driver definition. Thanks

Sorry for the confusion.
I made 2 different definitions one in Ascii and one 1 block.
In ascii the settings are limited, because of the limitations i made a new definition with #driver block.
Now i have al the source of the power supply and can read en reset status and alarm. And it works more native because i can use status information for update other settings.
But there is only a serial nummer what i can read and are not able to test for the different models.

Should a make 8 definition files for each model

I am pretty sure that you do not need to make a definition for each model.
As long as the definitions are nearly similar it can easily be done with #meta and #metadef

The ascii driver was not really fit for the protocol, the block matches much better. #metadef do not depend on protocol, all #metadef stuff is processed before the definition is passed to the protocol driver, i.e. #metadef do not even know what protocol (or driver) you have selected, it is pure text processing.

[HKJ]

I have changed the detection of the voltmeter to:

String m = di.getMode().toLowerCase();
if (m.contains("volt") || m.contains("vdc") || m.contains("v_dc")) {

I.e. volt, vdc and v_dc will match, both upper and lower case.

I hope this covers everything.

Thermometer is:

String m = di.getMode().toLowerCase();
if (m.contains("temp")) {

If anybody sees other names for temperature, please post it.

[flash2b]

In your SSR relay you have this:

#interface setRelay relay(value?"on":"off") (channel)
#interface getRelay relay? (channel)

So your scpi is "relay on 1"  and "relay off 1" ?

How can I have two parameters in a #scpiCmd ? and how do I split inputValue... do I need getElement ?

The actual command to the relay box is:
relayon channel
relayoff channel

relay(value?"on":"off")  simply modify the word to either relayon or relayoff, then channel put the channel number in as a parameter.
I do not remember it exactly now, but I believe multiple parameters may be passed as "1 2 3", i.e. you can split it on spaces (For some stuff it works that way, I do not remember if it is #scpiCmd).

My relay definition is working and has all required #interface commands. I also have relayon channel and relayoff channel implemented same way HKJ SSR Relay.



I am now going to make all my Eletechsup temperature definition compatible with the new format.

This also needs to be done for Temperature definitions from other authors like the Tasi TA612C, etc.

[flash2b]

Something like:
#interfaceType Thermometer Thermometer:2 Thermometer:3 Thermometer:4 Thermometer:5 Thermometer:6 Thermometer:7
#interface readTemperature 0 1 2 3 4 5 6

Would be more correct

The part about resistance is a issue, but I do not see that you can do anything about it. TC will not accept a readValue

Note that get/set will include a channel var in addition to the value var, for stuff that affect all channels you can ignore it.

Can I just add #interface readTemperature 0 and leave all other in place ?

Leaving the other #interface definitions is not nice, but I do not see any real issues with it.

I have made my Eletechsup NT18B07 definition to comply to the new standard and it is recognized by the battery test popup. 




I will now work on the other 4 definitions which require a little more work because of all the #meta stuff.


Conclusion for the battery test popup.

- PSU OK, 100%
- Relay OK, 100%
- Temperature, OK,  100% for the NT18B07 work to be done on all the others
- Voltmeter, NOK need a new test version of TestController to see if changes by HKJ fixed it for me

[HKJ]

My relay definition is working and has all required #interface commands. I also have relayon channel and relayoff channel implemented same way HKJ SSR Relay.

I am now going to make all my Eletechsup temperature definition compatible with the new format.

This is good.

This also needs to be done for Temperature definitions from other authors like the Tasi TA612C, etc.

There is no requirement for supporting #interface, but there will be some limitations if it is not supported.

I am thinking about adding other advanced test:
Maybe a DC-DC converter test with a power supply and load (Optional temperature and voltmeter) where TC can automatic do load sweep at different input voltages and do some long time (hours) test at full load.
Maybe a power supply test with a AC supply and a load and basically do the same tests as above.

This is only ideas and not something I will do just now, but if I do them they will use #interface to access the needed functions in devices.
I am also aware that the above can be done with existing functions in TC, but the idea is make it simple and automate it as much as possible.

[HKJ]

- Voltmeter, NOK need a new test version of TestController to see if changes by HKJ fixed it for me

Ok, ok, I have uploaded a new version, only change is the detection of a voltmeter.

[flash2b]

Dear HKJ,

I have made all my Eletechsup thermometer definitions compatible with the new #interfaceType Temperature standard.

These are Eletechsup NT18 NT28 NT38 NT48 PT21 modules, as found in the attachment.

Please delete Eletechsup NT48 series.txt from the Devices folder, since I renamed it to Eletechsup NT48xxx.txt for consistency.

Part of TC release 3.00

[ Attachment Invalid Or Does Not Exist ]

[flash2b]

- Voltmeter, NOK need a new test version of TestController to see if changes by HKJ fixed it for me

Ok, ok, I have uploaded a new version, only change is the detection of a voltmeter.

I did check with the new v2.99 version but none of my Hameg HM8112, Prema 4/5/6xxx, Analogic DP100 and Yokogawa 755x/756x seem to show up, so they are all not recognized.

I do see that the popup is polling values from the devices.

Do I need to set a mode first ?

These are the results from Voltage DC modes from my definitions:

getMode from my Yokogawa 7562 returns 1
getMode from my Hameg HM8112 returns Volt_DC (very common in other definitions)
getMode from my Analogic DP100 returns VDC

[HKJ]

Dear HKJ,

I have made all my Eletechsup thermometer definitions compatible with the new #interfaceType Temperature standard.

These are Eletechsup NT18 NT28 NT38 NT48 PT21 modules, as found in the attachment.

Please delete Eletechsup NT48 series.txt from the Devices folder, since I renamed it to Eletechsup NT48xxx.txt for consistency

Done, thanks

[HKJ]

I did check with the new v2.99 version but none of my Hameg HM8112, Prema 4/5/6xxx, Analogic DP100 and Yokogawa 755x/756x seem to show up, so they are all not recognized.

I do see that the popup is polling values from the devices.

Do I need to set a mode first ?

These are the results from Voltage DC modes from my definitions:

Yes, the meter need to be in a valid mode.

getMode from my Yokogawa 7562 returns 1

That sound silly, you mode button will show "1" instead of something more telling?

getMode from my Hameg HM8112 returns Volt_DC (very common in other definitions)

This is supposed to be caught on "Volt"

getMode from my Analogic DP100 returns VDC

This is supposed to be caught on "VDC"


I have put up a new test version (same version number), it will list meters and modes found when opening battery test to console output.
Like this:
Keysight 34465A   current mode in lower case: dc_voltage

To qualify to be checked for mode the meter must be type DMM and support readValue()

[flash2b]

For the Yokogawa 7562, the getMode I issued from the Test Interface popup, and then it reports 1

On de mode menu it is shown as  Volt DC

#value Volt_DC VDC SI 1

#cmdMode Volt_DC Volt_DC
voltDC;

I am confused, since you talked about the Column name at the beginning, but now we are talking about mode.

Well I am stuck now, since I cannot test the Battery Test popup since I do no have a compatible meter.

[HKJ]

For the Yokogawa 7562, the getMode I issued from the Test Interface popup, and then it reports 1

On de mode menu it is shown as  Volt DC

#value Volt_DC VDC SI 1

#cmdMode Volt_DC Volt_DC
voltDC;

I am confused, since you talked about the Column name at the beginning, but now we are talking about mode.

That was a mistake, I did/do check on the mode

Well I am stuck now, since I cannot test the Battery Test popup since I do no have a compatible meter.

A meter is not required to use it, but try opening it and see what modes are listed on the console.

Anyway I want to support your meters, but it will require you do some tests for me.

[HKJ]

For the Yokogawa 7562, the getMode I issued from the Test Interface popup, and then it reports 1

On de mode menu it is shown as  Volt DC

#value Volt_DC VDC SI 1

#cmdMode Volt_DC Volt_DC
voltDC;

I am confused, since you talked about the Column name at the beginning, but now we are talking about mode.

Well I am stuck now, since I cannot test the Battery Test popup since I do no have a compatible meter.

Looking in the Yokogawa definition I can see what is going wrong.

You define

#cmdMode Volt_DC Volt_DC

instead of

#cmdMode Volt_DC 1

The last one will take the 1 and change it to Volt_DC as mode for internal use in TC


Maybe I need to go for the columns instead of modes.

[HKJ]

Another version of TC (Same version number), this time I have switches to use the column name.
I hope this help, I do not want you to have issues with your meters.

[flash2b]

The latest version works for me, Yokogawa 7562 is recognized. 

Hameg HM8112 and Analogic DP100 are not.

[flash2b]

I have update my defintions for the Bside I8, eTommens eTM-MP and eTommens eTM-P series, to be compatible with #interfaceType PS and the Battery Test popup.

I had the Bside I8 finished last month but I did not release it.

HKJ, please update these in TestController.

[ Attachment Invalid Or Does Not Exist ]

[HKJ]

The latest version works for me, Yokogawa 7562 is recognized. 

Hameg HM8112 and Analogic DP100 are not.

They must be DMM types to be recognized, not DMM,
At leas that is the issue for Hameg, I did not check Analogic.

[HKJ]

I have update my defintions for the Bside I8, eTommens eTM-MP and eTommens eTM-P series, to be compatible with #interfaceType PS and the Battery Test popup.

I had the Bside I8 finished last month but I did not release it.

HKJ, please update these in TestController.

Updated, thanks.

[flash2b]

The latest version works for me, Yokogawa 7562 is recognized. 

Hameg HM8112 and Analogic DP100 are not.

They must be DMM types to be recognized, not DMM,
At leas that is the issue for Hameg, I did not check Analogic.

Analogic is working 

, removed and misssing a #interface readValue 0

Hameg is working as well 

, removed and misssing a #interface readValue 0

Well now all my equipment is working with the Battery Test popup.

Will send more definition updates soon.....

[flash2b]

I have updated my DMM BMM definitions with corrected #interfaceType DMM BMM to be compatible with Battery Test popup.

HKJ, please update these in TestController.

[ Attachment Invalid Or Does Not Exist ]

Thank you HKJ for making it possible to have my meters supported.

No I can start using/testing the Battery Test popup 

[HKJ]

No I can start using/testing the Battery Test popup 

It do not need all devices, but it is interesting to see the difference in result with/without DMM.
I uses a 4-terminal battery connector with the DMM connected to sense and both load and PS to the other part. There are significantly voltage differences.
It is not my battery test setup, that was optimized, but simple a setup at my bench with standard banana hookup wires.

[flash2b]

I meant Now instead of No ... sorry   

The only ingredient I did not check is my Siglent SDL1020X yet.

I did not write the Siglent SDL10xxXxx.txt definition, so I hope it is OK. Did you check ?

I will release the Relay definition once I know it is testing as it should. I also added the 8CH version to it.

(You updated my DMM BMM, did you?)

[HKJ]

I meant Now instead of No ... sorry   

That was fairly easy to guess.

The only ingredient I did not check is my Siglent SDL1020X yet.

I did not write the Siglent SDL10xxXxx.txt definition, so I hope it is OK. Did you check ?

No, I do not have a Siglent load. I checked with ITech. I do have a few other loads, but I have not checked with them.

If TC include it in the batteryTest popup it have the necessary definitions.

I will release the Relay definition once I know it is testing as it should. I also added the 8CH version to it.

Sounds good.

[flash2b]

Please overwrite my previous Yokogawa defintion that was included with 2 others.

New one attached...

[ Attachment Invalid Or Does Not Exist ]

Part of TestController v3.00

[Benleentje]

I am pretty sure that you do not need to make a definition for each model.
As long as the definitions are nearly similar it can easily be done with #meta and #metadef

The ascii driver was not really fit for the protocol,

Haha there i stil confusion.

The power supply supports 2 type of protocolls ascii and hex.
ascii works with #driver ascii
- There i a way to check voor modeltype by the query the maxpower
- There no status readback and checking for thing like  power = on or witch range the power supply is working in.
hex works with #driver block thanks for the help.
- There is no way to verify the device
- There is a status read back  and more values to read

For now i am back to ascii and put in your suggestion for replace text this is working great.
I am trying to make a readback for the range en output status.

Fot so far this is not working any suggestions?
I am trying somthin like this below

The power supply allways answer the command with the actual setting and that is the only thing i can use

Code: [Select]

#scpiCmd Range? txrx? (value?"SSHIFTH":"SSHIFTL") ;; this doesn't work but i don't kno a other way. how to turn the virtual led on or off
:readmath: ((value)=="SSHIFTH"?1:0)
#scpiCmd Range txrx (value?"SSHIFTH":"SSHIFTL")


#CMDSetup buttonsOn Range
:read: Range? (value)
:write: Range
:tip: turn range to low or high
:update: Set_Current Set_Voltage
On 1
OFF 0