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

[flash2b]

When logging is running and I clicking to get Column resize (last column) on Table view I do get sometimes Java errors:

Code: [Select]

;; HM8112_2: Tx <read?>
;; HM8112_2: Tx <txrx? L1
:readmath: substring(value,0,12)>
;; HM8112_2: Rx <+02.50044E+0>
;; HM8112_2: Rx as numbers <2.50044>
Exception in thread "AWT-EventQueue-0" java.lang.ArrayIndexOutOfBoundsException
;; HM8112_2: Tx <read?>
;; HM8112_2: Tx <txrx? L1
:readmath: substring(value,0,12)>
;; HM8112_2: Rx <+02.50044E+0>
;; HM8112_2: Rx as numbers <2.50044>
Sometimes there are multiple Exception in thread "AWT-EventQueue-0" java.lang.ArrayIndexOutOfBoundsException but logging does not crash.

What can cause this ?

AWT = Abstract Window Toolkit. I wish that TC would auto-size the output column(s) (the column next to dateTime) so I do not have to do it by hand. It has something to do with the resizing.

[Odd]

Itech IT8513C+
displays voltage with four real decimals ,  in Test Controller, the last voltage decimal is always zero.
it displays current with four decimals, in Test Controller the current is truncated to three digits.



Is this a protocol limit, or the implementation?

[KungFuJosh]

Itech IT8513C+
displays voltage with four real decimals ,  in Test Controller, the last voltage decimal is always zero.
it displays current with four decimals, in Test Controller the current is truncated to three digits.

(Attachment Link)

Is this a protocol limit, or the implementation?

Go to the Current Values tab, right click, and select more digits. See if that solves it. If so, you can edit the definition file and change the amount of decimal places to suit your needs.

[flash2b]

Dear HKJ,

I have added support of the Prema 5001 and Prema 6001 to my existing definition. Furthermore this definition also has some minor bug fixes of existing devices.

This was made possible with help the TC dummy interface pop-up, very useful addition (however I still have some questions  )

Please note the definition filename was changed into "Hameg HM8112.txt", so please delete the existing "Hameg HM8112 .txt" that had an extra space in the filename.

 Hameg HM8112 v1.03 Final.zip (4.1 kB - downloaded 22 times.)

[HKJ]

When logging is running and I clicking to get Column resize (last column) on Table view I do get sometimes Java errors:

Please use debug mode and post the error messages from the console.

[HKJ]

Is this a protocol limit, or the implementation?

I do not remember the details, but my guess is a protocol limit.

[HKJ]

I have added support of the Prema 5001 and Prema 6001 to my existing definition. Furthermore this definition also has some minor bug fixes of existing devices.

I have added it, thanks.

[flash2b]

When logging is running and I clicking to get Column resize (last column) on Table view I do get sometimes Java errors:

Please use debug mode and post the error messages from the console.

Here is some more log for you.

Code: [Select]

;; P6001: Tx <txrx? L1
:readmath: substring(value,0,12)>
;; P6001: Rx <+02.50044E+0>
;; P6001: Rx as numbers <2.50044>
Exception in thread "AWT-EventQueue-0" java.lang.ArrayIndexOutOfBoundsException: -1
        at java.util.Vector.elementData(Unknown Source)
        at java.util.Vector.elementAt(Unknown Source)
        at javax.swing.table.DefaultTableColumnModel.getColumn(Unknown Source)
        at dk.hkj.main.Support$WidthTableColumnModel.getColumn(Support.java:1003)
        at dk.hkj.main.PaneTable$3$1.getToolTipText(PaneTable.java:109)
        at javax.swing.ToolTipManager.checkForTipChange(Unknown Source)
        at javax.swing.ToolTipManager.mouseMoved(Unknown Source)
        at java.awt.AWTEventMulticaster.mouseMoved(Unknown Source)
        at java.awt.Component.processMouseMotionEvent(Unknown Source)
        at javax.swing.JComponent.processMouseMotionEvent(Unknown Source)
        at java.awt.Component.processEvent(Unknown Source)
        at java.awt.Container.processEvent(Unknown Source)
        at java.awt.Component.dispatchEventImpl(Unknown Source)
        at java.awt.Container.dispatchEventImpl(Unknown Source)
        at java.awt.Component.dispatchEvent(Unknown Source)
        at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
        at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
        at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
        at java.awt.Container.dispatchEventImpl(Unknown Source)
        at java.awt.Window.dispatchEventImpl(Unknown Source)
        at java.awt.Component.dispatchEvent(Unknown Source)
        at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
        at java.awt.EventQueue.access$500(Unknown Source)
        at java.awt.EventQueue$3.run(Unknown Source)
        at java.awt.EventQueue$3.run(Unknown Source)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source)
        at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source)
        at java.awt.EventQueue$4.run(Unknown Source)
        at java.awt.EventQueue$4.run(Unknown Source)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source)
        at java.awt.EventQueue.dispatchEvent(Unknown Source)
        at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
        at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
        at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
        at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
        at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
        at java.awt.EventDispatchThread.run(Unknown Source)
Exception in thread "AWT-EventQueue-0" java.lang.ArrayIndexOutOfBoundsException: -1
        at java.util.Vector.elementData(Unknown Source)
        at java.util.Vector.elementAt(Unknown Source)
        at javax.swing.table.DefaultTableColumnModel.getColumn(Unknown Source)
        at dk.hkj.main.Support$WidthTableColumnModel.getColumn(Support.java:1003)
        at dk.hkj.main.PaneTable$3$1.getToolTipText(PaneTable.java:109)
        at javax.swing.ToolTipManager.checkForTipChange(Unknown Source)
        at javax.swing.ToolTipManager.mouseMoved(Unknown Source)
        at java.awt.AWTEventMulticaster.mouseMoved(Unknown Source)
        at java.awt.Component.processMouseMotionEvent(Unknown Source)
        at javax.swing.JComponent.processMouseMotionEvent(Unknown Source)
        at java.awt.Component.processEvent(Unknown Source)
        at java.awt.Container.processEvent(Unknown Source)
        at java.awt.Component.dispatchEventImpl(Unknown Source)
        at java.awt.Container.dispatchEventImpl(Unknown Source)
        at java.awt.Component.dispatchEvent(Unknown Source)
        at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
        at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
        at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
        at java.awt.Container.dispatchEventImpl(Unknown Source)
        at java.awt.Window.dispatchEventImpl(Unknown Source)
        at java.awt.Component.dispatchEvent(Unknown Source)
        at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
        at java.awt.EventQueue.access$500(Unknown Source)
        at java.awt.EventQueue$3.run(Unknown Source)
        at java.awt.EventQueue$3.run(Unknown Source)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source)
        at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source)
        at java.awt.EventQueue$4.run(Unknown Source)
        at java.awt.EventQueue$4.run(Unknown Source)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source)
        at java.awt.EventQueue.dispatchEvent(Unknown Source)
        at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
        at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
        at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
        at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
        at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
        at java.awt.EventDispatchThread.run(Unknown Source)
;; P6001: Tx <read?>
;; P6001: Tx <txrx? L1
:readmath: substring(value,0,12)>
;; P6001: Rx <+02.50044E+0>
;; P6001: Rx as numbers <2.50044>


[Odd]

Itech IT8513C+
displays voltage with four real decimals ,  in Test Controller, the last voltage decimal is always zero.
it displays current with four decimals, in Test Controller the current is truncated to three digits.

(Attachment Link)

Is this a protocol limit, or the implementation?

You were right, Changing current to 4 decimals delivers the full precision, as on display.
however: voltage is already selected as 4 decimals, selecting 5 does not solve it.  But while the instruments can show 1.2345 volts . the test Controller shows 1.2340
I do not believe this is a protocol limitation (as they show all digits for current.)
I took a look inside Devices/Itech IT85xx.txt  ,and I see nothing that seems to do anything on that level.
Go to the Current Values tab, right click, and select more digits. See if that solves it. If so, you can edit the definition file and change the amount of decimal places to suit your needs.

[KungFuJosh]

You were right, Changing current to 4 decimals delivers the full precision, as on display.
however: voltage is already selected as 4 decimals, selecting 5 does not solve it.  But while the instruments can show 1.2345 volts . the test Controller shows 1.2340
I do not believe this is a protocol limitation (as they show all digits for current.)
I took a look inside Devices/Itech IT85xx.txt  ,and I see nothing that seems to do anything on that level.

Try SI6 and see if there's any difference. If not, then there's something about either the device communication, or the driver file that limits it.

One mode vs another mode doesn't guarantee anything, but I agree with the question: if it can do one, why not the other?

What values do you get if you enter voltage? or current? on the commands tab?

[Odd]

You were right, Changing current to 4 decimals delivers the full precision, as on display.
however: voltage is already selected as 4 decimals, selecting 5 does not solve it.  But while the instruments can show 1.2345 volts . the test Controller shows 1.2340
I do not believe this is a protocol limitation (as they show all digits for current.)
I took a look inside Devices/Itech IT85xx.txt  ,and I see nothing that seems to do anything on that level.

Try SI6 and see if there's any difference. If not, then there's something about either the device communication, or the driver file that limits it.

One mode vs another mode doesn't guarantee anything, but I agree with the question: if it can do one, why not the other?

What values do you get if you enter voltage? or current? on the commands tab?

That's odd:
current?
;; 0.1    << it is 0.0992A (99.2mA)
voltage?
;; 10    << the "10" is just bizarre,  it is 0.9256 V (according to instruments display)    and 0.9260 according to "current values" - which acts as if rounded. 

[KungFuJosh]

That's odd:
current?
;; 0.1    << it is 0.0992A (99.2mA)
voltage?
;; 10    << the "10" is just bizarre,  it is 0.9256 V (according to instruments display)    and 0.9260 according to "current values" - which acts as if rounded.

That is odd. I don't know anything about the device or the communication method setup in the driver. If I was interested in improving it, I'd try and find a manual with communication / command information. It seems you might need a different command or to set it up a different way to get more information.

[HKJ]

Here is some more log for you.

Code: [Select]

;; P6001: Tx <txrx? L1
Exception in thread "AWT-EventQueue-0" java.lang.ArrayIndexOutOfBoundsException: -1
        at java.util.Vector.elementData(Unknown Source)
        at java.util.Vector.elementAt(Unknown Source)
        at javax.swing.table.DefaultTableColumnModel.getColumn(Unknown Source)
        at dk.hkj.main.Support$WidthTableColumnModel.getColumn(Support.java:1003)
        at dk.hkj.main.PaneTable$3$1.getToolTipText(PaneTable.java:109)
        at javax.swing.ToolTipManager.checkForTipChange(Unknown Source)
        at javax.swing.ToolTipManager.mouseMoved(Unknown Source)
        at java.awt.AWTEventMulticaster.mouseMoved(Unknown Source)
        at java.awt.Component.processMouseMotionEvent(Unknown Source)
        at javax.swing.JComponent.processMouseMotionEvent(Unknown Source)


It is not something I really want to do a lot about, but I have trapped the error

[HKJ]

That's odd:
current?
;; 0.1    << it is 0.0992A (99.2mA)
voltage?
;; 10    << the "10" is just bizarre,  it is 0.9256 V (according to instruments display)    and 0.9260 according to "current values" - which acts as if rounded.

That is odd. I don't know anything about the device or the communication method setup in the driver. If I was interested in improving it, I'd try and find a manual with communication / command information. It seems you might need a different command or to set it up a different way to get more information.

There is no rounding or anything going on in the driver, it is a protocol limitation.
The device uses its own protocol and it has some limits.
Volt is support down to 1mV steps, current to 0.1mA steps and power to 1mW steps all transmitted as long integer (32 bit).
Capacity and energy is calculated in the driver, it is not part of the protocol.

I do also believe it can do SCPI, but the driver do not support that, it will have to be another driver (If anybody do write one, I will be happy to include it).

[flash2b]

Finally could reproduce the hanging LOG behavior in TC since version >2.77 with help of the Dummy interface.

Setup of the Dummy interface in settingsDummyDummy.txt

Code: [Select]

cmd:OS|init:|ex:"MDL7562\nF1R0\nM0IT5SI1000TD0\nNL0AZ1\nNS500RD0\nSM0AT100\nCO0CF1\nKA+0.000000E+00KB+1.000000E+00\nKC+0.200000E+02KD+1.000000E+00\nHI+0.000000E+00LO+0.000000E+00"
cmd:D|init:|ex:"NDCV+02.50006E+0"
cmd:OC|init:|ex:"@"
cmd:S|init:|ex:"A"
Definition:
Yokogawa 7562

Testcase:
Request setup menu for the device

Then start logging with pressing "Log"  in TC.

TC will hang......

Could you take a look at it HKJ? I never had this problem with v2.77 and before.

(..... BTW I like the dummy interface a lot !!)
 

[Hydron]

I have also seen TC hang when pressing Log, however I was not in a position to investigate or replicate it.

[Gertjan]

I have also seen TC hang when pressing Log, however I was not in a position to investigate or replicate it.

Hi HKJ,

I am also experiencing this problem with V2.88. I wanted to investigate further before reporting, but now the subject has come up.
My experiences so far:

- When starting logging TC will freeze. (readout in the Current Values tab works fine)
- The problem is only when the Setup Menu is open.
- When looking in debug mode, after pressing "Log", there is a askmode? or updatemodechange, with a series of refreshes of the Setup Menu.
  Halfway trough these refreshes TC freezes.
- With all :updatemodechange: removed from the Setup Menu, the problem is gone (But the menu is no longer updated )
- With all :updatemodechange: removed, and  #updateModeChange added, the problem is the same.
- The problem seems to be only with GPIB controlled devices. (Ethernet and COM controlled devices seems unaffected)
- I tried long delay timeouts (#readingDelay 10, #modeChangeDelay 10). Did not improve matters.
- When switching back to V2.77 all is fine.

I experienced the problem with the Keithley 199 and the Agilent 3458A drivers, using latest Java JRE, on Win7 and Win10.

Hope this helps....
regards, Gertjan.

[flash2b]

I retested it with that version, but does not help. 

Then the problem occurred again, no logging.
MAJOR breakthrough

I deleted all :updatemodechange: and now logging works again !, but of-course now there are other issues since the menu is not synchronized anymore.

Logging now also starts instantly after pressing the log, the button is red and logging starts without any delay.

------

If I put back :updatemodechange: to #cmdSetup info or #cmdSetup selector then logging does not work anymore !!! These both invoke askMode !!!

Thank you, I retested it with v2.81 and same issue as with v2.84/5.

So between 2.77 and 2.81 something changed with the handling of :updatemodechange: that affected the logging.

So same as reported a while back, for me both on com and GPIB in the ascii driver.

[Gertjan]

If I put back :updatemodechange: to #cmdSetup info or #cmdSetup selector then logging does not work anymore !!! These both invoke askMode !!!

Indeed I think this is the same issue as flash2b reported before....

Thank you, I retested it with v2.81 and same issue as with v2.84/5.
So between 2.77 and 2.81 something changed with the handling of :updatemodechange: that affected the logging.

So same as reported a while back, for me both on com and GPIB in the ascii driver.

I have tested with an Agilent 34401A. Logging with Setup menu open works OK connected with COM as wel as GPIB with TC v2.88.
Agilent 34401A has a very similar menu structure then the Keithley 199 etc. drivers. (These are more or less copies of / inspired by the 34401A menu's)

Difference is that 34401A is SCPIx. So the problem seems to be with ASCII driver definitions.

Hope this helps. For my measurements I am going back to v2.77....

regards, Gertjan.

[Mike99]

Hi, I've just started playing with TestController connected to my Racal 1991 counter via AR488.

I can set the counter resolution manually to 10 digits, but when I start logging with TestController it changes it to 9 digits.

I may be missing something obvious, but why does this happen?

Mike

[Gertjan]

Hi, I've just started playing with TestController connected to my Racal 1991 counter via AR488.

I can set the counter resolution manually to 10 digits, but when I start logging with TestController it changes it to 9 digits.

I may be missing something obvious, but why does this happen?

Hi Mike99,

Nice to see you over here, as a TestController user .

- In general: you can right-click on a column with values, and choose format. Here you can choose the number of digits or decimals. SI is digits using numkMG, D is number of decimals.
  (TestController is always recording the full resolution of an instrument. This is just about the presentation, all digits are always available in the underlying table)

- Racal-Dana 1991 specific: The number of digits depends on the Gate Time. Only with the longest Gate Time of ten seconds, the counter will return 10 digit values. 1sec Gate Time will return 9 digit values etc.

Maybe superfluous, but when logging, take care that you choose a  longer logging interval then the selected gate time....

regards, Gertjan.

[Mike99]

Hi Gertjan 

Yes I did find how to change the format but that doesn't help me. I can set the counter to 10 digits and 10 second gate time but TestController changes it to display 9 digits and 1 second gate time and it only returns the 9 digits. The popup has a gate time setting but it doesn't appear to do anything.

Mike

EDIT: OK it does appear to work, as in it returns the full 10 digits to TestController, but the counter display is odd. It shows 000.000018 when the frequency is 10.00000018MHz.

[Gertjan]

EDIT: OK it does appear to work, as in it returns the full 10 digits to TestController, but the counter display is odd. It shows 000.000018 when the frequency is 10.00000018MHz.

Hi Mike,

Did you notice the O/F LED on the left side of your counter? It means OverFlow. Your counter is now measuring 10MHz with 1mHz resolution. There are not enough digits on the display, so the most significant digits are pushed into overflow.
The small "3" on the right side indicates that the readout value is in kHz. So there is "10" (first 2 digits) in the overflow

regards, Gertjan.

[Mike99]

EDIT: OK it does appear to work, as in it returns the full 10 digits to TestController, but the counter display is odd. It shows 000.000018 when the frequency is 10.00000018MHz.

Hi Mike,

Did you notice the O/F LED on the left side of your counter? It means OverFlow. Your counter is now measuring 10MHz with 1mHz resolution. There are not enough digits on the display, so the most significant digits are pushed into overflow.
The small "3" on the right side indicates that the readout value is in kHz. So there is "10" (first 2 digits) in the overflow

regards, Gertjan.

Ah yes, got it now! You can tell I'm new to this but I'll get there eventually.

Thanks,

Mike

[HKJ]

Finally could reproduce the hanging LOG behavior in TC since version >2.77 with help of the Dummy interface.

That lead directly to the error, it was a deadlock (I already expected that, but they can be very hard to locate and fix).
This time it was a easy to locate and fix, because I could reproduce it.

There is a new test version up.