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

[flash2b]

I'm facing another problem.

My device's temperature values live in input registers (function code 0x04). TC has the full holding-register set - holding?, holdingS?, holdingF? - but for input registers only the unsigned input? exists; there is no inputS? or inputF?.

The floating-point temperature block (0x01C2) would need an input-register float read (inputF?), which does not exist, so I fall back to the integer block (0x0190) with /10. But those integers are signed, and without an inputS? I cannot read
negative temperatures - and this device is specified from -200 degC (XEXX:-200~1350 degC @ 2%, XDXX: -200~850 degC @ 1%), so negatives are well within range, not an edge case.

I can add a per-channel readmath (((value+32768)%65536)-32768)/10 to fix the sign manually, but that forces one read per channel, so I lose polling all 6 values in a single transaction.

Could you add inputS? (and ideally inputF?) to mirror the existing holding commands? Either one solves it: inputF? lets me use the float block directly (signed by nature, no scaling), or inputS? lets the integer block handle negatives.

[flash2b]

Major problem in the TC test version v3.50

#verifyDevice does not work anymore for all my definitions that use identification like #verifyDevice DM36B06 model?

TC release version 3.48 still works.  (but does not work on Mobus TCP)

[HKJ]

Major problem in the TC test version v3.50

#verifyDevice does not work anymore for all my definitions that use identification like #verifyDevice DM36B06 model?

TC release version 3.48 still works.  (but does not work on Mobus TCP)

That do not make sense.
I connected my two DM36B06 and they work perfectly.

I did also compare the current modbus driver to the 3.48, there are two changes: #unitid and separate read/write for network folded into a combined read/write.

[HKJ]

I'm facing another problem.

My device's temperature values live in input registers (function code 0x04). TC has the full holding-register set - holding?, holdingS?, holdingF? - but for input registers only the unsigned input? exists; there is no inputS? or inputF?.

The floating-point temperature block (0x01C2) would need an input-register float read (inputF?), which does not exist, so I fall back to the integer block (0x0190) with /10. But those integers are signed, and without an inputS? I cannot read
negative temperatures - and this device is specified from -200 degC (XEXX:-200~1350 degC @ 2%, XDXX: -200~850 degC @ 1%), so negatives are well within range, not an edge case.

I can add a per-channel readmath (((value+32768)%65536)-32768)/10 to fix the sign manually, but that forces one read per channel, so I lose polling all 6 values in a single transaction.

Could you add inputS? (and ideally inputF?) to mirror the existing holding commands? Either one solves it: inputF? lets me use the float block directly (signed by nature, no scaling), or inputS? lets the integer block handle negatives.

Looks like I can fairly easy give you these commands, note F is a 32 bit value.

[flash2b]

Major problem in the TC test version v3.50

#verifyDevice does not work anymore for all my definitions that use identification like #verifyDevice DM36B06 model?

TC release version 3.48 still works.  (but does not work on Mobus TCP)

That do not make sense.
I connected my two DM36B06 and they work perfectly.

I did also compare the current modbus driver to the 3.48, there are two changes: #unitid and separate read/write for network folded into a combined read/write.

I emailed you the log, mine does not work in 3.50

[HKJ]

Major problem in the TC test version v3.50

#verifyDevice does not work anymore for all my definitions that use identification like #verifyDevice DM36B06 model?

TC release version 3.48 still works.  (but does not work on Mobus TCP)

That do not make sense.
I connected my two DM36B06 and they work perfectly.

I did also compare the current modbus driver to the 3.48, there are two changes: #unitid and separate read/write for network folded into a combined read/write.

I emailed you the log, mine does not work in 3.50

Are you using the exact same definition file in the two version?
When using #meta stuff, the files in documents\... do not take precedent.

[flash2b]

Yes.

v3.50:
Start thread for: Modbus Port1:1 - Eletechsup DM36B06
Modbus Port1:1: Tx <holding? 0xFE>
COM5: Tx: 01 03 00 FE 00 01 E5 FA
COM5: Rx: 01 03 02 00 03 F8 45
Modbus Port1:1: **Device do not match** <DM36B06>
Modbus Port1:1 Device "Eletechsup,DM36B06," do not match answer: "**Device do not match** <DM36B06>"
COM5: Close
Stopping thread for: Modbus Port1:1 - Eletechsup DM36B06
COM5: Close

v3.48 Connects fine:
Found Eletechsup DM36B06 on Modbus Port1:1

[HKJ]

Yes.

v3.50:
Start thread for: Modbus Port1:1 - Eletechsup DM36B06
Modbus Port1:1: Tx <holding? 0xFE>
COM5: Tx: 01 03 00 FE 00 01 E5 FA
COM5: Rx: 01 03 02 00 03 F8 45
Modbus Port1:1: **Device do not match** <DM36B06>
Modbus Port1:1 Device "Eletechsup,DM36B06," do not match answer: "**Device do not match** <DM36B06>"
COM5: Close
Stopping thread for: Modbus Port1:1 - Eletechsup DM36B06
COM5: Close

v3.48 Connects fine:
Found Eletechsup DM36B06 on Modbus Port1:1

I have put up a new test version 3.51, I have not done anything to fix your problem, because I do not have it. I use the last update you submitted of the definition, the same that is included in the release version.
But now input? exists in the same versions as holding? It is, of course, untested, but holding and input share code, only difference is a flag.

[flash2b]

3.51 tested:

- #subDriver TCP in #metadef now works
- inputS? works
- inputL? works
- inputSL? works
- inputF? works
- DM36B06 also works for me now... (forced to release version) will investigate why


So all works, and the first ever definition that uses Modbus TCP now also works !!

Thank you

[HKJ]

I have been working on a article that explain some of what TC can do, it is fairly shortform, but with links to relevant help pages:

https://lygte-info.dk/project/TestControllerHowToDo%20UK.html

Comments are welcome.

[Cyclotron]

I have been working on a article that explain some of what TC can do, it is fairly shortform, but with links to relevant help pages:

https://lygte-info.dk/project/TestControllerHowToDo%20UK.html

Comments are welcome.

Very nice, I have been over it briefly and think this is great. I will spend more time reviewing it to see if there's anything I can offer that might help.

[KungFuJosh]

I have been working on a article that explain some of what TC can do, it is fairly shortform, but with links to relevant help pages:

https://lygte-info.dk/project/TestControllerHowToDo%20UK.html

Comments are welcome.

That looks like a good start.

The thing I don't like about your website is that it doesn't have a functional menu system on every page. For example, for anything I might need to review separately, I have to bookmark separate pages.

A good menu structure would help people navigate the site, and find things faster for working in TC and adding devices. Something like (Bold = Parent; Indent = submenu items):

Home

Getting Started
   Install Guide
   How To Do (the new page)
   Docs for Main Pages
   Docs for Popups

Adding Devices
   New Device
   Configuration of SCPI Devices (and SCPIx)
   Configuration of Non-SCPI Devices

Scripting
   Script Commands
   Scripts for Device Configuration

Examples
   Scripting example
   Battery test with resistor
   Script for charging a USB charged battery and labeling the chart
   Using a Arduino with Test Controller
   User Scripts
   User Projects

I would use a simple horizontal menu bar at the top of the page.

Thanks,
Josh

[Cyclotron]

Bug or user error.

I've got a driver I'm about to pos that I've been working through. I was trying to use selectors/layout and found an issue where corruption would appear in the menus. The attached is a way to simply reproduce the issue

; TO RUN
;   1. Move the stock VirtualSinusGenerator.txt out of your Devices folder.
;      This file claims the same #idString, and only one can win the match.
;   2. Drop this file in Devices and restart TestController.
;   3. Add the VirtualSinusGenerator device and open its Setup dialog. It keeps
;      the stock name on purpose.

Now just let TC connect to to the virtual device and go to the "setup" menu. See Setup-Startup. Things look "ok".  When you select "1s" the menu changes dynamically and the first aberration appears in the bold of Sub-B, then go to the "3S" selection and you see the item corrupted.

The test driver has more doco in its header.  Let me now if you want more details.  I've worked around this by using another method to do the menu.

[Cyclotron]

New Driver, Chroma 63000 series electronic loads.  There are two in this series and I have tested the 63004-150-60.
Note that I developed this driver on TC connected to VMSG as my Chroma only has the USB interface and is on my VISA management system.  These Chroma models can have a GPIB interface, I just don't currently have one. I very much believe this driver will work directly with GPIB. I emulated the Prologix Ethernet Adapter on the TC side.

Driver attached and committed to this Github repo with further documentation and screenshots.

https://github.com/Cyclotronic/TC-Drivers/tree/main/drivers/Chroma_63000_Series

[flash2b]

Your UI, looked at the Github, look great. Nicely done.

You might consider changing #cmdSetup buttonsOn into #cmdSetup toggleButton, so more KungFuJosh style.

I use both in my defs, depending on it's use.

[HKJ]

New Driver, Chroma 63000 series electronic loads.  There are two in this series and I have tested the 63004-150-60.
Note that I developed this driver on TC connected to VMSG as my Chroma only has the USB interface and is on my VISA management system.  These Chroma models can have a GPIB interface, I just don't currently have one. I very much believe this driver will work directly with GPIB. I emulated the Prologix Ethernet Adapter on the TC side.

Driver attached and committed to this Github repo with further documentation and screenshots.

https://github.com/Cyclotronic/TC-Drivers/tree/main/drivers/Chroma_63000_Series

Added, thanks.

[HKJ]

Bug or user error.

Nested selectors is a issue.

[HKJ]

The thing I don't like about your website is that it doesn't have a functional menu system on every page. For example, for anything I might need to review separately, I have to bookmark separate pages.

A good menu structure would help people navigate the site, and find things faster for working in TC and adding devices. Something like (Bold = Parent; Indent = submenu items):

A menu requires a use a tool to generate the webpages or program in java script, I do not really like either option.


You menu structure is here, but in links:
https://lygte-info.dk/project/TestControllerIntro%20UK.html

You can also open relevant devlop pages from the filter menu on the load devices page.

And if you need help to a TC page, you just press F1.


I use the above and do not really see any issue with it (A menu would be nicer, but it is not really a obstacle).

[KungFuJosh]

I use the above and do not really see any issue with it (A menu would be nicer, but it is not really a obstacle).

I'll PM you about it.

[Salient666]

I am playing with TestController lately and I ran into an 'issue'.
Whenever I closed the program, all my meters would reset to their default state (which is good) except the Siglent SDM4065A.

I looked at the FinalCmd line and I copied the same line that is in the Keysight file there to see if that would help.

That line is:
#finalCmd ABOR;*CLS;*RST;INIT;SYST:LOC

And indeed, the meter now resets as it should (and turns off autoZero, which can't be activated by SCPI at the moment because... siglent....)

@KungFuJosh: I think this should be made default?

[KungFuJosh]

I am playing with TestController lately and I ran into an 'issue'.
Whenever I closed the program, all my meters would reset to their default state (which is good) except the Siglent SDM4065A.

I looked at the FinalCmd line and I copied the same line that is in the Keysight file there to see if that would help.

That line is:
#finalCmd ABOR;*CLS;*RST;INIT;SYST:LOC

And indeed, the meter now resets as it should (and turns off autoZero, which can't be activated by SCPI at the moment because... siglent....)

@KungFuJosh: I think this should be made default?

Maybe... I don't like the way it behaves with that full line right now. ABORT;*CLS is currently the finalCmd, but I can at least add the SYST:LOC if it works. I don't want to update the definition until after a firmware update. Siglent needs to fix the SCPI issues.

You can, of course, add that to your local file if that's what you prefer.

Thanks,
Josh

[Cyclotron]

Bug or user error.

Nested selectors is a issue.

Thanks! I didn't know if it was a known issue.  The modified driver for the internal virtual device helped me determine it was in TC, not in my driver. So I shared it in case you wanted to see it or test.

[Cyclotron]

I've tweaked the Chroma driver since I found a slight issue. I think the menus look nicer.

Screen shots and write up in the repo.
https://github.com/Cyclotronic/TC-Drivers


The other driver here is a duplicate and I had worked on it significantly before I realized it was a duplicate. The current HPe363xA bench power supply driver only seems to support serial which is why I didn't notice it before.  The one attached was developed on a HP E3633A attached to GPIB.

I don't know if you will want it since its a duplicate.  I'll take your advice on that.

[HKJ]

The other driver here is a duplicate and I had worked on it significantly before I realized it was a duplicate. The current HPe363xA bench power supply driver only seems to support serial which is why I didn't notice it before.  The one attached was developed on a HP E3633A attached to GPIB.

I don't know if you will want it since its a duplicate.  I'll take your advice on that.

I have updated the chroma driver.

I do not know what HP driver I want. I want the one that support most functions on the power supply, but your explanations do not say if your driver support more, the same or less. Obvious it supports GPIB, but that update may be as simple as add the word gpib to the already existing driver.
A screenshot of both configuration menus may also help.

[flash2b]

A suggestion on range for controls that support this.

Code: [Select]

#cmdSetup number CH1 Offset_CH1-6
:read: offsetShapeCH1?
:write: offsetShapeCH1
:tip: Temperature offset in °C (0.1 resolution; 0 = Default; positive value raises the reading, negative value lowers it)
°C -100.0 100.0

The range is °C -100.0 100.0 which is rendered like the screen shot.

What I do not like is that TC uses - sign to connect lower and upper side of the range. Normally this is ok, but if the range is negative to positive it does not look clear.

Can the control be modified that when it occurs a + sign is added to the upper side, or a :-command to add a + in the definition itself. The example is Temperature, many be not the most common use, but it is also for Voltage and Current.