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

[HKJ]

I believe I found the issue and has uploaded a new version of TC, but with same version number.
The ADC files are also removed from this upload.

Can you put my original definition back in it please?

Ok, even though I do not agree with you about the all uppercase name.

[KungFuJosh]

I believe I found the issue and has uploaded a new version of TC, but with same version number.
The ADC files are also removed from this upload.

Can you put my original definition back in it please?

Ok, even though I do not agree with you about the all uppercase name.

If you really like it better, put the edited version and I'll replace the device in TC and edit my scripts. I liked the name/IDN etc matching. But it's not that important now that I'm fully awake and calm. 

[HKJ]

If you really like it better, put the edited version and I'll replace the device in TC and edit my scripts. I liked the name/IDN etc matching. But it's not that important now that I'm fully awake and calm. 

Modern meters have two different id strings and they do not match, I am sort of using fuzzy comparison to get around that. It mostly works (The issue is when you do a #DISCOVER?, it returns device names, but not exactly the same as *idn?)

I don't want to do more replacements now and your scripts may work with the updated TC.
Please report where there are issues with upper/lower case names.

[KungFuJosh]

I believe I found the issue and has uploaded a new version of TC, but with same version number.
The ADC files are also removed from this upload.

Thanks, the new version did correct the case-sensitivity issue.

[Messtechniker]

You should also delete ADC10F103C.txt and ADC16F103R.txt from the release

Why?

[HKJ]

Thanks, the new version did correct the case-sensitivity issue.

Where TC is case sensitive is the programming language, i.e. anything with variables.
The device name do not get near that, it cannot because spaces are legal in device names, but not in variables.

[HKJ]

You should also delete ADC10F103C.txt and ADC16F103R.txt from the release

Why?

Because they now exist with a brand name (LC Tech), but you can easily find them by typing ADC in the filter on the load devices page.

[mawyatt]

Finally got around to downloading and installing Test Controller. We know what took so long

This is an impressive effort from HKJ

After stumbling thru a few things we were able to get our DMM6500, DAQ6510 installed by LAN. Then our GPP-4323 and a pair of SPD3303X.

However we've tried the Hioki IM3536 and can't seem to connect, we know we have a good LAN connection as we can "see" the IM3536 with terminal connection from our Mac:  "Connection to 192.168.001.119 port 3500 [tcp/rtmp-port] succeeded!".

Also tried with the TH2830 with a USB connection, also without success. We could "see" the USB connection with a terminal command ls /dev/tty.usbmodem* as "/dev/tty.usbmodem301" which was verified by plugging and unplugging the USB cable. Not sure how this should be entered into the serial address, so used com301 and get a "Dummy Device" response.

Anyone have any suggestions, we aren't up on this sort of stuff, and getting the IM3536 connected is more of a priority for starters.

Best

[HKJ]

Finally got around to downloading and installing Test Controller. We know what took so long

This is an impressive effort from HKJ

After stumbling thru a few things we were able to get our DMM6500, DAQ6510 installed by LAN. Then our GPP-4323 and a pair of SPD3303X.

However we've tried the Hioki IM3536 and can't seem to connect, we know we have a good LAN connection as we can "see" the IM3536 with terminal connection from our Mac:  "Connection to 192.168.001.119 port 3500 [tcp/rtmp-port] succeeded!".

Also tried with the TH2830 with a USB connection, also without success. We could "see" the USB connection with a terminal command ls /dev/tty.usbmodem* as "/dev/tty.usbmodem301" which was verified by plugging and unplugging the USB cable. Not sure how this should be entered into the serial address, so used com301 and get a "Dummy Device" response.

Anyone have any suggestions, we aren't up on this sort of stuff, and getting the IM3536 connected is more of a priority for starters.

If you have issue with a connection, configure to only try that device and then run TC in debug mode. That may get you some useful information. Sorry, but I do not know hos to do that on a Mac., can you open a console window and start it from there?

With serial ports: Right-click in the address field and TC will list serial ports, that usually makes it much easier to find the correct one.

[mawyatt]

If you have issue with a connection, configure to only try that device and then run TC in debug mode. That may get you some useful information. Sorry, but I do not know hos to do that on a Mac., can you open a console window and start it from there?

With serial ports: Right-click in the address field and TC will list serial ports, that usually makes it much easier to find the correct one.

Need to read up on how to run TC in debug mode, thanks.

Also on Mac, the right click doesn't work on Address to show com ports, nothing pops up with either a right or left click!!

Best

[KungFuJosh]

Finally got around to downloading and installing Test Controller. We know what took so long

This is an impressive effort from HKJ

After stumbling thru a few things we were able to get our DMM6500, DAQ6510 installed by LAN. Then our GPP-4323 and a pair of SPD3303X.

However we've tried the Hioki IM3536 and can't seem to connect, we know we have a good LAN connection as we can "see" the IM3536 with terminal connection from our Mac:  "Connection to 192.168.001.119 port 3500 [tcp/rtmp-port] succeeded!".

Also tried with the TH2830 with a USB connection, also without success. We could "see" the USB connection with a terminal command ls /dev/tty.usbmodem* as "/dev/tty.usbmodem301" which was verified by plugging and unplugging the USB cable. Not sure how this should be entered into the serial address, so used com301 and get a "Dummy Device" response.

Anyone have any suggestions, we aren't up on this sort of stuff, and getting the IM3536 connected is more of a priority for starters.

Best

Did you edit the port number / verify that it matches on the IM3536 and in the device definition file? The default port number in the file is 03536.

For the ST2832, you need to make sure the port selected in the ST2832 says USBCDC, not USBTMC. I've not tried with a Mac, so I don't know what headaches might occur with that. TestController is not currently compatibly with USBTMC.

Even when correctly setup, I sometimes have to hit "Reconnect" a few times with the ST2832. The serial communication with it can be a little tricky. Adjusting buffer sizes sometimes helps with that sort of thing.

There are some notes to help with both devices in the definition files. For my ST2832, I had to remove the USBTMC driver before Windows would work with and install the correct USBCDC driver. I know you're on a Mac, so again I don't know what headaches it will throw.

On a Mac, try long-clicking to see if options popup.

There's a batch file to run debug mode in the TestController app folder. I dunno if that does anything on Mac, but it will show you the normal command / options.

Thanks,
Josh

[HKJ]

Need to read up on how to run TC in debug mode, thanks.

There is not much to read about it, it requires that TC is start with a command line debug option, using a console window gives extra info.

Also on Mac, the right click doesn't work on Address to show com ports, nothing pops up with either a right or left click!!

Then there are no com ports, or you are not editing the address field (You must be editing the field).


I forgot: You can turn debug mode on from within TC with the #debug command, but you must do a reconnect for it to give any useful information about connecting.

[Cyclotron]

If you have issue with a connection, configure to only try that device and then run TC in debug mode. That may get you some useful information. Sorry, but I do not know hos to do that on a Mac., can you open a console window and start it from there?

With serial ports: Right-click in the address field and TC will list serial ports, that usually makes it much easier to find the correct one.

Need to read up on how to run TC in debug mode, thanks.

Also on Mac, the right click doesn't work on Address to show com ports, nothing pops up with either a right or left click!!

Best

As I don't do a lot of Java I had to look at this too. I now just open a command/terminal, run

Code: [Select]

java -jar testcontroller.jar debug
The debug content shows up in the Testcontroller window as well but since I often want to run a tee on the content and watch for strings in the debug I use the console methods. 

I'd don't know if there's a more efficient way and look for advice if folks have a better work flow. I worked on the k2002/2001(m) configs with Josh and while I checked and validated the config I would restart TC each time to recheck. I didn't look but there didn't seem to be an obvious way to reload the device config while TC is still running.

A device config build menu would be awesome (just wishing). Select a device config and it loads it and you see a debug console so you can make edits, reload, and so on testing and QA'ing till you're ready to push it out for publishing.

[KungFuJosh]

That's normal. The device definition files are loaded when TC starts. I would love a reload definitions button.

[HKJ]

As I don't do a lot of Java I had to look at this too. I now just open a command/terminal, run

Code: [Select]

java -jar testcontroller.jar debug
The debug content shows up in the Testcontroller window as well but since I often want to run a tee on the content and watch for strings in the debug I use the console methods. 

I'd don't know if there's a more efficient way and look for advice if folks have a better work flow. I worked on the k2002/2001(m) configs with Josh and while I checked and validated the config I would restart TC each time to recheck. I didn't look but there didn't seem to be an obvious way to reload the device config while TC is still running.

A device config build menu would be awesome (just wishing). Select a device config and it loads it and you see a debug console so you can make edits, reload, and so on testing and QA'ing till you're ready to push it out for publishing.

Reloading a definition would be nice, but there are some issues.
1) I would have to remove the old definition first (Not that hard, only issues is that the filename is not related to the definition name, i.e. I have to parse for #name first)
2) With #metadef I would have to remove all definitions and the original definition, I do not save information to do that, i.e. it is rather hard.

Because TC generally starts fairly fast, I do not really see this as a big issue. To start really fast, rename the devices directory in the TC folder so TC only has to load a few definitions. I do sometimes use this, it do not spoil the list on "Load devices" page and it is easy to restore the devices.

[Cyclotron]

As I don't do a lot of Java I had to look at this too. I now just open a command/terminal, run

Code: [Select]

java -jar testcontroller.jar debug
The debug content shows up in the Testcontroller window as well but since I often want to run a tee on the content and watch for strings in the debug I use the console methods. 

I'd don't know if there's a more efficient way and look for advice if folks have a better work flow. I worked on the k2002/2001(m) configs with Josh and while I checked and validated the config I would restart TC each time to recheck. I didn't look but there didn't seem to be an obvious way to reload the device config while TC is still running.

A device config build menu would be awesome (just wishing). Select a device config and it loads it and you see a debug console so you can make edits, reload, and so on testing and QA'ing till you're ready to push it out for publishing.

Reloading a definition would be nice, but there are some issues.
1) I would have to remove the old definition first (Not that hard, only issues is that the filename is not related to the definition name, i.e. I have to parse for #name first)
2) With #metadef I would have to remove all definitions and the original definition, I do not save information to do that, i.e. it is rather hard.

Because TC generally starts fairly fast, I do not really see this as a big issue. To start really fast, rename the devices directory in the TC folder so TC only has to load a few definitions. I do sometimes use this, it do not spoil the list on "Load devices" page and it is easy to restore the devices.

Yes, the current method isn't horrible. I was just "Wishing".  A quick reload of the devices dir? 

I appreciate you considering the thought.

It is far better to work on features for users than for device configuration build as the latter will eventually become much slower per my suspicion.

[KungFuJosh]

To start really fast, rename the devices directory in the TC folder so TC only has to load a few definitions. I do sometimes use this, it do not spoil the list on "Load devices" page and it is easy to restore the devices.

Oh, I like this idea. I'll get rid of all the definitions for devices I either don't have or don't have any interest in. 🤔

I'm putting everything I don't have in an "Unused" subfolder.

[Cyclotron]

To start really fast, rename the devices directory in the TC folder so TC only has to load a few definitions. I do sometimes use this, it do not spoil the list on "Load devices" page and it is easy to restore the devices.

Oh, I like this idea. I'll get rid of all the definitions for devices I either don't have or don't have any interest in. 🤔

I'm putting everything I don't have in an "Unused" subfolder.

Yeah, this is also something I'm going to do.  As the def numbers grow, that might be a worth while feature. Either a component gui to select the defs you want to enable or have it bult into TC to do so you can optimize the load.  Maybe its not interesting.

[KungFuJosh]

Yeah, this is also something I'm going to do.  As the def numbers grow, that might be a worth while feature. Either a component gui to select the defs you want to enable or have it bult into TC to do so you can optimize the load.  Maybe its not interesting.

TBH, TC always loads fast and I didn't notice a difference after making the change. However, it makes me feel better knowing it doesn't load anything to do with Rigol. 

[HKJ]

Yeah, this is also something I'm going to do.  As the def numbers grow, that might be a worth while feature. Either a component gui to select the defs you want to enable or have it bult into TC to do so you can optimize the load.  Maybe its not interesting.

TBH, TC always loads fast and I didn't notice a difference after making the change. However, it makes me feel better knowing it doesn't load anything to do with Rigol. 

I have been fairly careful with using multi threading to make TC look fast. It throws up the UI very fast, but the gray look may take some time to get rid of (At least on a old machine with spinning disks  ).

[KungFuJosh]

Is it possible to plot Allan deviation with TC? https://en.wikipedia.org/wiki/Allan_variance

Thanks,
Josh

[mawyatt]

Finally got around to downloading and installing Test Controller. We know what took so long

This is an impressive effort from HKJ

After stumbling thru a few things we were able to get our DMM6500, DAQ6510 installed by LAN. Then our GPP-4323 and a pair of SPD3303X.

However we've tried the Hioki IM3536 and can't seem to connect, we know we have a good LAN connection as we can "see" the IM3536 with terminal connection from our Mac:  "Connection to 192.168.001.119 port 3500 [tcp/rtmp-port] succeeded!".

Also tried with the TH2830 with a USB connection, also without success. We could "see" the USB connection with a terminal command ls /dev/tty.usbmodem* as "/dev/tty.usbmodem301" which was verified by plugging and unplugging the USB cable. Not sure how this should be entered into the serial address, so used com301 and get a "Dummy Device" response.

Anyone have any suggestions, we aren't up on this sort of stuff, and getting the IM3536 connected is more of a priority for starters.

Best

Did you edit the port number / verify that it matches on the IM3536 and in the device definition file? The default port number in the file is 03536.

For the ST2832, you need to make sure the port selected in the ST2832 says USBCDC, not USBTMC. I've not tried with a Mac, so I don't know what headaches might occur with that. TestController is not currently compatibly with USBTMC.

Even when correctly setup, I sometimes have to hit "Reconnect" a few times with the ST2832. The serial communication with it can be a little tricky. Adjusting buffer sizes sometimes helps with that sort of thing.

There are some notes to help with both devices in the definition files. For my ST2832, I had to remove the USBTMC driver before Windows would work with and install the correct USBCDC driver. I know you're on a Mac, so again I don't know what headaches it will throw.

On a Mac, try long-clicking to see if options popup.

There's a batch file to run debug mode in the TestController app folder. I dunno if that does anything on Mac, but it will show you the normal command / options.

Thanks,
Josh

Thanks Josh, that was it, we did not change the port in the device text file

Edit: just noted the M1,2,3,4 current values are shifted down and the actual Z is not displayed. IM3536 is set for Cp, Rs, D, Z from top to bottom?

Best

[KungFuJosh]

Thanks Josh, that was it, we did not change the port in the device text file

Nice, that's an easy fix.

Did you figure out your TH2830 yet?

I tried to get my old MacBook Pro going, but the battery died before I could do anything useful.

[mawyatt]

Thanks Josh, that was it, we did not change the port in the device text file

Nice, that's an easy fix.

Did you figure out your TH2830 yet?

I tried to get my old MacBook Pro going, but the battery died before I could do anything useful.

Just got back, so no attempts at anything other than IM3536. See Edit above about the Current Value Display?

Best

[KungFuJosh]

Just got back, so no attempts at anything other than IM3536. See Edit above about the Current Value Display?

Trying going to the Commands tab, and click Setup. Then manually select each of the 4 parameters and see if that corrects the issue for you.