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

[flash2b]

The auto adjust popup is incorrectly formatted.

[flash2b]

On help system #SHOWPOPUPSYSTEM autoadjust

 #SHOWPOPUPSYSTEM name {x y {w h}}
   Show a system popup.
   Names supported: Calculator, Timer, LogTrigger, AdjustScale, Alarm, ParamAdjuster, AutoHold, ParamSweeper, VarDispay, Image, ScriptList, Main,  LogEvent, FFTView, TimerCounter, MPPT, BatteryTest, Steps
   Note: Main can be used to move the location of the main window, but will not show any popup
   The x and y is screen coordinates for the upper left corner and will override any other position.
   Can be used in scripts to configure screen layout


The help for #SHOWPOPUPSYSTEM does not list AutoAdjust, but #SHOWPOPUPSYSTEM autoadjust works. Also VarDispay is missing an L, and the help lists FFTView but not PSTest, while the web page lists PSTest but not FFTView.

[HKJ]

The auto adjust popup is incorrectly formatted.

Pull it wider, the issue is you have a very long name somewhere in the combobox.

[HKJ]

The help for #SHOWPOPUPSYSTEM does not list AutoAdjust, but #SHOWPOPUPSYSTEM autoadjust works. Also VarDispay is missing an L, and the help lists FFTView but not PSTest, while the web page lists PSTest but not FFTView.

I have fixed the issues and updated the website and the TC help file (It will be downloaded on next restart).

[flash2b]

Yes.. i did I can see it and it works also very nicely.

I never knew this existed, since no mention of the web or in the helpsystem. I was just looking for a tool I needed but I found it Adjust Scale.

I can use that to select components within a certain tolerance.

The alarm popup is also nice, but no percentage there.

[HKJ]

Yes.. i did I can see it and it works also very nicely.

I never knew this existed, since no mention of the web or in the helpsystem. I was just looking for a tool I needed but I found it Adjust Scale.

I can use that to select components within a certain tolerance.

The alarm popup is also nice, but no percentage there.

Now I believe #setAutoAdjust documentation is done.

What do you mean with percentage?

[flash2b]

#SHOWPOPUPSYSTEM scriptlist failed due to <ClassCastException> dk.hkj.main.PopupScriptList cannot be cast to dk.hkj.main.PopupImage

TC 3.58. It happens whether the Script list popup is open or closed. The same command opened the popup earlier today.

error:

#SHOWPOPUPSYSTEM scriptlist failed due to  <ClassCastException>  dk.hkj.main.PopupScriptList cannot be cast to dk.hkj.main.PopupImage

[flash2b]

Yes.. i did I can see it and it works also very nicely.

I never knew this existed, since no mention of the web or in the helpsystem. I was just looking for a tool I needed but I found it Adjust Scale.

I can use that to select components within a certain tolerance.

The alarm popup is also nice, but no percentage there.

Now I believe #setAutoAdjust documentation is done.

What do you mean with percentage?

In the Adjust Scale popup I enter a reference and a tolerance, for example 1000 and 1%. In the Alarm popup I have to work out the min and max myself, 990 and 1010. A reference plus a tolerance in percent, as an alternative to min and max, would make the Alarm handy for sorting components too.

[HKJ]

In the Adjust Scale popup I enter a reference and a tolerance, for example 1000 and 1%. In the Alarm popup I have to work out the min and max myself, 990 and 1010. A reference plus a tolerance in percent, as an alternative to min and max, would make the Alarm handy for sorting components too.

Try adjust scale for that.

[HKJ]

#SHOWPOPUPSYSTEM scriptlist failed due to <ClassCastException> dk.hkj.main.PopupScriptList cannot be cast to dk.hkj.main.PopupImage

TC 3.58. It happens whether the Script list popup is open or closed. The same command opened the popup earlier today.

error:

#SHOWPOPUPSYSTEM scriptlist failed due to  <ClassCastException>  dk.hkj.main.PopupScriptList cannot be cast to dk.hkj.main.PopupImage

Fixed, I could just remove the extra call, it was not needed.

[flash2b]

coil? over Modbus TCP returns 0 when the coil is 1.
coil? 0x0064
Tx: 00 06 00 00 00 06 01 01 00 64 00 01
Rx: 00 06 00 00 00 04 01 01 01 01
Result: 0
The same command over Modbus RTU returns 1 for the answer 01 01 01 01 90 48.

This is a blocking problem for my definition so I hope it can be fixed.

[flash2b]

coil? over Modbus TCP always returns 0.
coil? 0x00 6 with all six coils on:
Modbus RTU: Rx 01 01 01 3F 11 98, result 63
Modbus TCP: Rx ... 01 01 01 3F, result 0
Writing coils works over both.

[HKJ]

coil? over Modbus TCP always returns 0.
coil? 0x00 6 with all six coils on:
Modbus RTU: Rx 01 01 01 3F 11 98, result 63
Modbus TCP: Rx ... 01 01 01 3F, result 0
Writing coils works over both.

Found something that did not look correct, I have modified it and upload a new test version.
Please report back.

And all the other stuff I said I fixed is also fixed in this test version.

[flash2b]

You fixed it !! Thank you !!

Now the coil? gets the correct value and my relays are synced both on reboot TC and power-up after reboot the device.

I was getting crazy since I also made an error myself in the code. I fixed it and it worked, but I forgot that I retested it on RTU and not TCP. When I was working on TCP it was wrong again, but this time my code was not at fault. So probing the logs got me to the culprit, it was a faulty read from TC and not my device.

Glad it is working....

[HKJ]

You fixed it !! Thank you !!

Now the coil? gets the correct value and my relays are synced both on reboot TC and power-up after reboot the device.

I was getting crazy since I also made an error myself in the code. I fixed it and it worked, but I forgot that I retested it on RTU and not TCP. When I was working on TCP it was wrong again, but this time my code was not at fault. So probing the logs got me to the culprit, it was a faulty read from TC and not my device.

Glad it is working....

I had not change the offset of the data, from the RTU I used as base for it.
One bug found in TCP protocol, I wonder if there are mode 

[flash2b]

You know me, when I find them I will report it to you. Lots of fixes.

The resize of the Auto Adjust did not work for me, it shows the same on 3.59. Alarm is looking great now and scriptlist  the error is gone.

The button on the dialog popup i masked by moving the radio to the top...  so I cannot re-test....

[HKJ]

The resize of the Auto Adjust did not work for me, it shows the same on 3.59. Alarm is looking great now and scriptlist  the error is gone.

I did not adjust anything, you can just pull the window wider when you have the issue.

The button on the dialog popup i masked by moving the radio to the top...  so I cannot re-test....

It is fixed.

[flash2b]

Digital channel shows only the last bit in the chart (since 3.54 till 3.59)
A digital value with several bits, for example #value Output Logic DIGITAL(DO1,DO2,DO3,DO4), shows only its last bit on the chart in 3.54 till 3.59, also with all bits named:
#ChartCurves "LCUS4.Output DO1" "LCUS4.Output DO2" "LCUS4.Output DO3" "LCUS4.Output DO4"
All four bits exist as scales on the Scales for chart page, but the chart draws only DO4, and the Digital axis shows only DO4.

The same definitions and the same command draw all bits in the 3.53 release, as in my post of 26 August (reply #7356), with the Digital axis showing DO1 to DO4.

So 3.53 release was working ok then it stopped working.

It drew four traces before as can been seen on: https://www.eevblog.com/forum/testgear/program-that-can-log-from-many-multimeters/msg6343962/#msg6343962

[trobbins]

https://github.com/Cyclotronic/VMSG/issues/1
Looking for assistance on how to progress an instal.

[HKJ]

https://github.com/Cyclotronic/VMSG/issues/1
Looking for assistance on how to progress an instal.

I suppose it is the interface from Cyclotronic you are talking about, not TestController.

[HKJ]

v3.60 is up.
This is mostly because V3.57 had a serious bug, as explained by flash2b above. A collection of minor stuff has also been fixed, again with a lot of help from flash2b (Everything is discussed above over a couple of posts). Last there is also a couple of updated devices.
   Fixed: Digital channels did not work in v3.57 (I made a mistake in fixing memory leaks)
   Fixed: A bug in modbus TCP (Thanks flash2b)
   Update: Relay and AOutput modules (Thanks flash2b)
   Fixed/changed: Some small details with script/programming/definitions, mostly stuff that was not ideal (Thanks flash2b for pointing it out)
   Update: Lots of temperature modules (Thanks flash2b)
   Update: eTommens power supplies (Thanks flash2b)
   Updated: BSide I8xxx power supplies with wave output(Thanks Flash2b)
   Updated: Analogic DP100 & R&S UDL45 Multimeters (Thanks Flash2b)
   Updated: Owon LCR2020, LCR2100, LCR2200, LCR2300, Anbai AT3810A, AT3817A, AT3816A, AT3818, Applent AT3810A, AT3817A, AT3816A, AT3818 (Thanks Flash2b)

Looking at the device count it is now above 1000 devices supported by TestController. By device I mean different names a HP, Agilent, Keysight device count as 3. I have also updated the first post to list all supported devices as of this version.
The actual device count is 1031, but that includes virtual devices and some of my DIY projects.

Another area where flash2b has been busy is scripting, there are now 3 more scripts included with TC (Right click in log window to access). They will only be visible when the required devices are present, but can always be seen by selecting "Generate script, List and manage scripts" and checking "Include system".

[flash2b]

Thanks for v3.60 and for picking everything up so quickly. Within days, every report was looked at and fixed, and the scripts and definitions are in.

And congratulations on passing 1000 supported devices. That is quite a milestone for a program that started as a logger for a few multimeters.

Lets continue to grow the wonderful world of Test Controller !

[HKJ]

And congratulations on passing 1000 supported devices. That is quite a milestone for a program that started as a logger for a few multimeters.

From the start it was planned to support a wide variety of devices and also a lot of devices. My design was based on that and it still works well.

Lets continue to grow the wonderful world of Test Controller !

I hope so.

[HKJ]

A bit more about the start:

I had written a Java program to control different devices, it was written the classic way with basic device class and inheritance down each device type. It worked fine for my own purpose, but I did not see it as a program to publish.
For that I needed a way for other people to make definitions and the obvious way was a plain Ascii text file. That is also the reason I did not use a special extension for definitions, I wanted it to be obvious that it was plain text and that anybody could write them.

Because I wanted to log/control many device simultaneous, I looked at two ways:
1) Post request to all devices and then go around to collect responses.
2) Use a separate thread for each device.
The second way gave me more flexibility and I selected that.
I had already used my programming language for some years, it is written as a library and easy to include, so of course I included it to handle anything a bit more complex than a plain number.
I also wanted scripting, but the programming language was to cumbersome for that with () and "" around parameters and string, hence I did a plain scripting language where all commands started with #, making it possible to mix them with scpi stuff.

For configuration of devices I needed something easier than using SCPI commands, but I did not want a fully customizable config page for each device (It is way to hard to make a layout with that), I wanted something simpler, hence the #cmdSetup format . It is fairly simple to define the screen layout, it looks ok and has good functionality. It has been extended a bit over times from user suggestions, making it possible to handle more advanced setups and look a bit better.

One purpose of the program was automatic testing, where scripts could be done with the scripting language and because I do not believe people like to write in a new language without some example (I do not), TC got the ability to generate scripts of its setting, making it easy to do a lot scripts without really remembering the details. Over time TC has got build in tests it can do.

The different pages was basically a given, I wanted the different ways to present the data and do configuration. For stuff like table and chart I wanted as large screen area as possible, no small tables or chart for me!

The popups is the main way I add new functionality to TC and GridPanel is for people that want to customize a interface.

I hope some found the above story interesting.

[akapuma]

Hello,

I’d like to monitor my washing machine and tumble dryer. I have an ATORCH S1BWP smart plug that can connect via Bluetooth-SPP. As the range isn’t sufficient, I’m proceeding as follows:

On an Android mobile phone located near the washing machine, I have installed the BT/TCP-Bridge 12.2 app: https://play.google.com/store/apps/details?id=masar.bb
This app forwards the data as a TCP server via my home Wi-Fi to the PC.

On the Windows PC, I have installed a virtual COM port: https://www.hw-group.com/software/hw-vsp3-virtual-serial-port

In the Test Controller, I select the ATORCH S1BWP and connect it via the virtual COM port.

So far, this has worked quite well. However, I would now like to do away with the virtual COM port driver and connect the ATORCH S1BWP directly via TCP (the mobile app will, of course, remain in use).

Is there a way to do this? Unfortunately, my attempts so far have been unsuccessful.


Best regards

akapuma