Author Topic: 3458a logging via Windows app.....revisited  (Read 18516 times)

pwlps, Micke and 1 Guest are viewing this topic.

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
3458a logging via Windows app.....revisited
« on: November 18, 2018, 09:02:50 pm »
Hi all,

Some time ago I messed with an Excel spreadsheet and some VBA macros to enable my Win10 PC to gather GPIB data and present it on a graph........it worked, but I do find it a little unreliable. It'll just stop logging minutes or hours in......and the Excel VBA graphs are real slow even on a fast PC. Thread here:
https://www.eevblog.com/forum/metrology/3458a-logging-via-excel-macro/

So, I finally found some time to look into this subject again, I dug out the RaspPi 3 but gave up after a couple of hours.....I know nothing about linux!......I need a proper Windows solution!

I went hunting and stumbled on Pawel Wzietek's CodeProject thread and after downloading the VB source I finally got it to compile in Visual Studio 2015 (thanks for the tips Pawel) and after playing with it and my 3458A it looks extremely reliable......with his original code you can hammer the QUERY button and it simply queues the commands and gets the messages back. Not only that but it's also configurable for a number of different interfaces, such as VISA, GBIP:ADlink, GPIB-488 and COM port......and can run two devices at the same time.
https://www.codeproject.com/Articles/1166996/Multithreaded-communication-for-GPIB-Visa-Serial-i

Again, much thanks to Pawel for the great GPIB Device groundwork......

I/O DEVICE COMPATIBILITY (TESTED HARDWARE):
VISA (HP3458A – Using E5810A/82357B) (Keithley 2015THD - Using E5810A) (Fluke 8842A - Using E5810A) (Keysight 34461A - Using Lan)
GBIP:ADlink
GPIB-488
COM port

TEMPERATURE/HUMIDITY DEVICE COMPATIBILITY:
USB-TnH SHT10 V2.00 & USB-TnH SHT30 (Usb serial comms)

OS TESTED:
Win10

DOWNLOADS:
EXE’s - Release V1.49 attached below - IODeviceAppV1_49.zip (Source coming soon, I have been playing with PPM/DegC on Playback).
VB Source - Visual Studio Express 2015 exported template attached (V1.45 - 29/04/19) testIODeviceV1_45.zip.
Source install:
- Unzip the folder.
- Open "testIODevice.vbproj" in VS (folders will be created).
- From the EXE zip, copy "IODevice.dll" & "Microsoft.VisualBasic.PowerPacks.dll" to the new /bin/debug folder.

Note: I have tested the app with Win10 and briefly with Win7.

INSTRUCTIONS FOR INSTALLATION:

The zip file contains the following:
- main testIODevice.exe app
- additional .DLL's required (please replace these on any app updates).
- Empty Log.csv file
- GPIBchannels.txt file

Start the app by double clicking testIODevice.exe.


INSTRUCTIONS / NOTES FOR USE:

Assumes that you have loaded the current version of Keysight IO Libraries Suite and have it configured.
I have tested the app with an Agilent E5810A LAN-GPIB and an Agilent 82357B USB-GPIB clone. Both running in Visa mode.

DEVICES:
Set up your NAME and ADDRESS of the device(s) you want to connect to, and pick the INTERFACE type (I have tested Visa only).
The defaults shown when you install are my own as an example.
Hit the CREATE DEVICE button (you choose). An pop-up box will appear that lists the connected device. This box will remain visible at all times and will let you see the commands being sent and any queued commands.

You can effectively batch commands using the PRE RUN, AT RUN and AT STOP boxes and using the RUN/STOP button at the bottom.
PRE RUN commandsare used to set up your device.
AT RUN command is the command that is repeated at the SAMPLE RATE.
Command types are as follows:

SINGLE COMMANDS:
Enter single commands in the COMMAND boxes and hit QUERY and you'll get a RESPONSE back (if it's a command that returns a query).
Types of commands as follows:-
Blocking commands - Are immediately executed on the calling thread (usually GUI thread), this method waits until it gets response from the interface.
Query Asynchronous commands - Queries are queued and the queue is processed on a different thread (producer-consumer model). The call appends the query to the queue and returns immediately.

BATCH COMMANDS:
Send Asynchronous commands - Sent via AT RUN, and are sent similar to the Query Async commands except do not expect a reply, i.e. "fire and forget" manner.
Note: my GUI should really have a separate single command send for SendSync but I have not implemented this at the moment.....you can just use the QueryAsync single query send and the reply will just time-out gracefully.

IO DEVICES POP-UP:
When the CREATE DEVICE buttons are pressed a pop-up box will appear that lists the connected device(s).
This box will remain visible at all times and will let you see the commands being sent and any queued commands.
Note that you can close this window without any effect on the app. You can use the button "Show Device List" to show it again if needed.
Please note that there are some issues in this regard, i.e. you may see some errors appear and the queue grow, but in the case of my 3458A and Keithley 2015THD everything usually settles down until you just see one line for your devices as it communicates.

TEMPERATURE/HUMIDITY:
There is only a couple of Temperature/Humidity sensor I have tested and that are available from DOGRATIAN seller here:-
http://www.dogratian.com/products/index.php/menu-sensors/menu-usb-tnh-type-a-sht10
http://www.dogratian.com/products/index.php/menu-sensors/menu-usb-tnh-type-a-sht30
They are serial USB type sensor and does not require any drivers except what Win7/Win10 loads automatically as you insert it. You should see a COM port which you can pick from the list on the app.
The SHT30 gives 2dp's whereas the SHT10 1dp.

DATA LOG / CSV:
For CSV generation, per the defaults, set up your filename and path to where you want the CSV to be saved. At the moment there is not file generated if it doesn't exist so make sure you have an empty .CSV text file at the path specified.
The check box ENABLE CSV will start saving data to the .CSV file.
The EXPORT CSV file will copy the active .CSV file to the same folder and append the current date & time as the filename.
EXPLORER will launch Windows Explorer and pointing to the path folder.
You can clear the current CSV file with the RESET CSV button, there's a check box next to it which must be set before the reset will work.
ENABLE LOG check box will activate the log file display window.
E NOTATION TO DECIMAL check box will convert ########E-02 to the decimal equivalent. This is for the CSV and well as the log window.

CHART:
Enable either or both device charts via the check boxes.
With the boxes un-checked you can hit the CLEAR CHART to reset the chart windows and remove the data.
You can change the resolution of the chart with the X-AXIS SCALE POINTS entry. Once the chart display reaches the set number of data points on it the chart will start to scroll off to the left as new data appears at the right.
The range of the Y-axis is adjustable via the SCALE MIN AND SCALE MAX enries. You can manually set them or hit AUTO SCALE and the chart will look at the existing trace and from it's highest and lowest position will centre and scale the chart.
The UP and DN buttons allow the current set scale to be adjusted in 10% steps.

PLAYBACK CHART:
For offline display of the generated .CSV files. The user can select the Device to be displayed on the graph (since there are 2 devices available), and also zoom in/out and scroll back/forward through the graph.

SAVE SETTINGS:
Most of the entries are saved off so when you restart the app they will be there.

Have fun.

Ian.
« Last Edit: November 10, 2019, 11:24:48 am by IanJ »
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 
The following users thanked this post: Melt-O-Tronic, beanflying

Online Andreas

  • Super Contributor
  • ***
  • Posts: 2407
  • Country: de
Re: 3458a logging via Windows app.....revisited
« Reply #1 on: November 18, 2018, 10:11:21 pm »
but I do find it a little unreliable. It'll just stop logging minutes or hours in......
Hello,

your plans are really high sophisticated. (with the graphical display).
But how do you get W10 working reliable?
Every time I want to log one of my ADCs via RS232 in a W10 machine it tries to install some software and reboot over night.
I have found no way to stop this behaviour. So I usually use old XP or W7 machines for measurements.

Just one hint:
instead of trying to put all software into one application I use several  small programs.
E.g. one program for temperature sensing and one for sensing the reference voltage.
The easiest way is to log 1 minute averages and combine the results via spread sheet calculations.

Another interesting way is to use a virtual file for data exchange.
So the values of e.g. a NTC-sensor ADC can be used from other software applicatons
and logged together with the readings or could even be used for T.C. corrections.

with best regards

Andreas
 

Offline Conrad Hoffman

  • Super Contributor
  • ***
  • Posts: 1132
  • Country: us
    • The Messy Basement
Re: 3458a logging via Windows app.....revisited
« Reply #2 on: November 19, 2018, 12:38:40 am »
I do this with a small PowerBASIC program and an old Prologix adapter that uses an FTDI chip. I can easily call their drivers and have few reliability problems... but I haven't tried it on my Win10 machine. I don't expect any serious problems. The same program, with some minor changes reads my HP3478A, HP3455A and frequency counter (can't remember the model). I suspect similar code could be done with Visual Basic or most any language. I just happen to like Basic and FTDI chips.
 

Offline alanambrose

  • Frequent Contributor
  • **
  • Posts: 274
  • Country: gb
Re: 3458a logging via Windows app.....revisited
« Reply #3 on: November 19, 2018, 03:26:35 pm »
Another data point - I have quite a lot of C# GPIB code which runs fine. I have used both and USB<->GPIB adaptors and LAN<->GPIB and both work good. There's a bit of nonsense with the different manufacturers (NI, Keithley, Agilent etc) all trying to be the visa interface on your machine - I'm using the Agilent version right now but I think I've used others in the past. I've found that the different manufacturer's test equipment has its own GPIB idiosyncrasies, timing behaviour etc. A bit of care with good exception handling and dealing with corner cases will pay dividends. The good thing about the Microsoft environment (I'm sure others will list the negatives) is that visual studio is 'grown-up' and has a good built-in debugger. You can even make some code changes within the debugger and it'll do an incremental compile on-the-fly and continue running from where you hit the break point - i.e. without a full re-build, app re-start etc.

Alan
“A foolish consistency is the hobgoblin of little minds"
 

Offline alm

  • Super Contributor
  • ***
  • Posts: 1257
  • Country: 00
Re: 3458a logging via Windows app.....revisited
« Reply #4 on: November 19, 2018, 03:53:29 pm »
C# and before that C has been used for decades for instrument control. According to Wikipedia, LabWindows (the LabVIEW framework with G code replaced by C) started in 1987 (for DOS). So of course there is no reason you couldn't develop something that is at least as good as the Python + PyVISA solution you might use on a Raspberry PI (which should also work on Windows). The only disadvantage compared to the Raspberry PI solution I can see is price and power usage if you want to run it 24/7.

Like Andreas, I would reconsider the monolithic approach, and consider separating data acquisition and analysis / plotting. You can later create something that manages both (e.g. connect to acquisition using a socket and embed the plotting), but this makes it much easier to do unattended logging (e.g. start as service), offline analysis, combining data from multiple instruments, etc. I would also separate logging from the DMM (including its internal temperature if you care) and logging from the environment sensor(s), since the latter data may be used for multiple instruments that are in the same room.
 

Offline Conrad Hoffman

  • Super Contributor
  • ***
  • Posts: 1132
  • Country: us
    • The Messy Basement
Re: 3458a logging via Windows app.....revisited
« Reply #5 on: November 19, 2018, 04:09:04 pm »
As Alan says, different instruments have their own quirks. It took me forever to figure out how to get my HP 8903B back to local from program control. Long ago I interfaced to an HP network analyzer that had a very early version of HPIB. I did it with a big old Data Translation card that had a bunch of I/O lines. Quirky doesn't begin to describe it. Huge PITA, but the interface cards were quite expensive back then. I'd never think about using anything other than a National or Prologix interface now.
 

Offline alm

  • Super Contributor
  • ***
  • Posts: 1257
  • Country: 00
Re: 3458a logging via Windows app.....revisited
« Reply #6 on: November 19, 2018, 04:32:02 pm »
Instruments certainly have their quirks. Some in hardware: I think the designer of the Prologix interface had to spend a lot more time than he expected to get his GPIB interface to work with all kinds of instruments. In my experience, newer (e.g. post-IEE-488.2 / SCPI) instruments are better behaved than older ones: if you go back far enough, then they implemented GPIB entirely in discrete logic gates, and the programming might be "send a byte with the first bit set and the other seven bits the voltage you want to set" without having any feedback. In my experience HP/Agilent instruments are better behaved than Keithley or Philips instruments from the same era. I've had to write more "if garbage data, then ignore" code or "avoid this sequence, since the instrument may lock up" for the latter two than for HP equipment. But I'm sure that's not universal across instruments.
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #7 on: November 19, 2018, 07:29:11 pm »
Hi all,

New screenshot posted in message #1 above......

3458A connected via E5810A......and I've done a bit more coding, enough to see if the concept will work reliably.
I have a PDVS2 connected to the 3458A and set to ramp the voltage up & down between 0 - 10Vdc.

The procedure with the app is to manually send a few commands (will vary with instrument I guess), then trigger readings from then on, i.e.:

END ALWAYS - GPIB EOI mode, this is needed so the 3458A can respond correctly
NRDGS 1 - Number of readings
TARM SGL - Trigger readings (1)

PS. I haven't played with NPLC etc yet.....thats next to do.

Then with TARM SGL left in the COMMAND window, set the sample rate, in this case 1 second and hit "Run"
Over on the right on the DATA LOG the sample are being logged to screen along with Date, Time and Temperature. I've not processed the sampled reading so have left it as per sent by the 3458A for now.
The current Sample count is recorded in the Device 1 area.

At the moment "Stop" will cease the sampling, but will leave the 3458A connected. I will add another button to properly "disconnect" later.

No CSV file yet, I want to make sure, as a few have hinted, that Win10 is happy.

Noted alm post regarding Keithley instruments less well behaved.....I have a couple of 2015 THD DMM's so will hook them up at some point and give them a go. I also have some Fluke's, Racal-Dana gear also.

So far seems to be working fine, and much more reliable than my Excel spreadsheet/macros.

Ian.
« Last Edit: November 19, 2018, 07:36:29 pm by IanJ »
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #8 on: November 19, 2018, 10:44:04 pm »
Like Andreas, I would reconsider the monolithic approach, and consider separating data acquisition and analysis / plotting. You can later create something that manages both (e.g. connect to acquisition using a socket and embed the plotting), but this makes it much easier to do unattended logging (e.g. start as service), offline analysis, combining data from multiple instruments, etc. I would also separate logging from the DMM (including its internal temperature if you care) and logging from the environment sensor(s), since the latter data may be used for multiple instruments that are in the same room.

I hear ya.......however, at the moment I just want something operational that mostly fits my own needs.......and it's just easier for me to integrate everything into the one app. My forte is uC C++, this is my ummm 4th Visual Studio VB app....ever, so there's a lot I don't know.
The source code will be posted at some point (warts and all).....so anyone else can take it on after that if I don't look into it.

Update:
Have added a checkbox to format returned data in numerical data format with correct DP position. Useful for 3458A data. Screenshot above updated.
One issue I do have which I need to look at is manually terminating GPIB and not have the 3458A front panel controls locked out.......a job for tomorrow. Then I'll look at writing to CSV.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline Conrad Hoffman

  • Super Contributor
  • ***
  • Posts: 1132
  • Country: us
    • The Messy Basement
Re: 3458a logging via Windows app.....revisited
« Reply #9 on: November 20, 2018, 03:34:54 am »
My effort was much less ambitious, didn't even put a title on the title bar, but it does the job. It's reading 1.23456 VDC from the calibrator-
 
The following users thanked this post: IanJ

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #10 on: November 21, 2018, 11:04:59 am »
Hi all,

Hit upon a wee problem last night......all was working well, I could connect to the 3458A and I recorded some 60k+ samples at 1sec intervals no problem, I can connect to the 3458A via a series of commands every time without problem.

However, disconnection is another matter!.......LOCAL 7 or LOCAL 722, or any other combination of RESET, CLEAR etc etc etc will not release the meter from remote back to local.......and as a result some subsequent commands in an attempt to do so just time-out, almost like it is half way between remote and local.....and the funny thing is that it does accept SOME command but not all, i.e. BEEP and RESET work. I did read the GPIB manual, including Appendix B.....to no avail.

So, I fired up the Agilent E5810A's web inteface and sent some commands from it, the same commands I am sending from my VB app and it reacts in exactly the same way.

The only way I can get back to local mode on the 3458A after I have sent the commands is to press the LOCAL button on the 3458A itself.....or pull the GPIB connector from the back of the 3458A.

Tonight I will try the Agilent USB-GPIB adaptor (clone) I have and see if it does the same.

It's not a huge issue, but I would prefer that it all works as perfect as possible............any Ideas?

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline alm

  • Super Contributor
  • ***
  • Posts: 1257
  • Country: 00
Re: 3458a logging via Windows app.....revisited
« Reply #11 on: November 21, 2018, 02:21:46 pm »
So you are saying it does not just fail to release the keyboard, but also fails to respond to commands it would respond to before you send "LOCAL 722"?

If new commands were sent after "LOCAL 722", then I could understand the instrument going back to remote immediately.  Note that the "22" is the GPIB address, so if the instrument is at GPIB address 16, you should send "LOCAL 716". Did you also try to send the GTL GPIB command (ibloc), instead of sending the string "LOCAL ..." to the instrument?
 

Online pwlps

  • Regular Contributor
  • *
  • Posts: 163
  • Country: fr
Re: 3458a logging via Windows app.....revisited
« Reply #12 on: November 21, 2018, 02:46:26 pm »
Hi Ian,

As far as I remember the command for Agilent stuff should have been either "LOCAL:RESET" or "LOCAL OFF", did you try those?

Also, did you try to Dispose the class instance? Dispose calls the "viClose" Visa function, this might reset the instrument to local but I'm not sure.

Otherwise, if it doesn't work tell me and I could try to implement the GPIB "GTL" command in the library.  GTL is a GPIB bus message and Visa implements it e.g. with :
 
ViStatus viGpibControlREN(ViSession vi, ViUInt16 mode);

with this option: (from Visa manual):
mode                                                  Action Description
 
VI_GPIB_REN_ADDRESS_GTL                Send the Go To Local command (GTL) to this device.

But then check first in the manual if GTL is supported by your 3458A - not sure this belongs to the list of mandatory 488 functions (there are several levels of compatibility for GPIB but I don't remember them).

The call to this function could be added to Dispose just before the call to viClose.

Pawel
 


 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #13 on: November 21, 2018, 02:47:16 pm »
It fails to respond to LOCAL 7 or LOCAL 722, and yes my GPIB address is 22.

So, I send my preamble commands and ultimately TARM SGL every second and logging begins.....I then eventually stop sending TARM SGL and then send LOCAL 722 or CLEAR or RESET etc and those commands fail. This happens both with my VB and also at the command line on the E5810A web interface. And when those commands fail if I send BEEP or RESET instead then the 3458A responds......so not as if all comms has ceased. If I then try to start logging again (TARM SGL etc) then it fails, it's like the 3458A is half-ib and half-out of remote/local. I have to manually hit LOCAL on the front panel and manually RESET.......or pull the GPIB connector.
I will try your suggestions tonight when I get back to the workshop.

It would be nice to know what series of commands other folks are sending when they are finished with their GPIB session.....not much on the web about that, just plenty about initiating sessions.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline alm

  • Super Contributor
  • ***
  • Posts: 1257
  • Country: 00
Re: 3458a logging via Windows app.....revisited
« Reply #14 on: November 21, 2018, 02:56:54 pm »
For me, the instruments used for long-term logging are usually in remote mode. If I want to use them for local operation, I use the front panel to go to local, enable display and set triggering to auto. So I never bothered with sending the local command via GPIB. Will try it later today if I have time.
 
The following users thanked this post: TiN, denimdragon

Offline Conrad Hoffman

  • Super Contributor
  • ***
  • Posts: 1132
  • Country: us
    • The Messy Basement
Re: 3458a logging via Windows app.....revisited
« Reply #15 on: November 21, 2018, 03:29:51 pm »
Getting my instruments back to front panel operation remotely has always been a problem. I think I've got it licked, though I'm not a programmer and can't even play one on TV. The trick is to tell your controller not to look for data after every send. If it does that, communication can never stop, regardless of what else you send. Don't know if this will help, but here's the code called by my disconnect button (PowerBASIC for Prologix adapter)-

Code: [Select]
SUB GPIB_Close
    DIM lResult AS LONG
    DIM lpBuffer AS ASCIZ * %gpibWriteLen
    DIM B2W AS DWORD
    DIM BW AS DWORD
    ON ERROR GOTO GPIB_Error_Trap

    lpBuffer = "++auto0"+$LF                     'turn off controller automatic read after write so meter will release
    B2W = LEN(lpBuffer)
    lResult = FT_Write(InstHandle, lpBuffer, B2W, BW)
    IF lResult <> %FT_OK THEN ERROR 152

    lpBuffer = "D1F1R-2RAZ1N4T1"+$LF             'turn on internal trigger and reset other settings for manual operation
    B2W = LEN(lpBuffer)
    lResult = FT_Write(InstHandle, lpBuffer, B2W, BW)
    IF lResult <> %FT_OK THEN ERROR 152

    lpBuffer = "++loc"+$LF                       'return control to front panel- this releases instrument
    B2W = LEN(lpBuffer)
    lResult = FT_Write(InstHandle, lpBuffer, B2W, BW)
    IF lResult <> %FT_OK THEN ERROR 152

    lResult = FT_Close(InstHandle)               'close the GPIB connection
    IF lResult <> %FT_OK THEN ERROR 152

    gpibConnected = 0

GPIB_Close_Exit:
    EXIT SUB


« Last Edit: November 21, 2018, 06:33:07 pm by Conrad Hoffman »
 

Online pwlps

  • Regular Contributor
  • *
  • Posts: 163
  • Country: fr
Re: 3458a logging via Windows app.....revisited
« Reply #16 on: November 21, 2018, 06:01:48 pm »
I guess the VB code posted by Conrad Hoffman is for a Prologix GPIB adapter?

Quote
lpBuffer = "++loc"+$LF                       'return control to front panel- this releases instrument

In Prologix language the "++loc" command sends a GoToLocal message to the device, this should be equivalent to the Visa function I mentioned.

edit:
In fact as there is no device address in this code, I think the "++loc" simply releases the REN line, so that all devices on the bus return to local.  Prologix manual is not clear about this.
« Last Edit: November 21, 2018, 06:13:31 pm by pwlps »
 

Offline Conrad Hoffman

  • Super Contributor
  • ***
  • Posts: 1132
  • Country: us
    • The Messy Basement
Re: 3458a logging via Windows app.....revisited
« Reply #17 on: November 21, 2018, 06:37:40 pm »
For the above to work, that first command in my disconnect code is needed. You have to get the adapter out of auto mode. For the Prologix it's "++auto0". No idea for other adapters, but I tore my hair out until I  figured this out.  :palm:
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #18 on: November 21, 2018, 08:11:35 pm »
Hi all,

I'll get back to the 3458A disconnect issue later....I was starting to pull my hair out also!

Meantime I have done some more work and have got both devices working at the same time now.....HP3458A and a Keithley 2015THD......see screenshot in post#1 above.
There are now some extra text boxes:
Commands to send at run......and Commands to send at STOP......It's this 'stop' where I was trying to send LOCAL 722 to the 3458A......ahh well!

The way it works is: The preamble commands are sent, but the last command in the list is the one that is repeated over and over......hence my TARM SGL & :READ?

I also have the CSV file generation working and logging to there also.
Snapshot of CSV below.....note I have decoded the readings in it as well as the onscreen Data Log, this is optional via a checkbox.

PS. Keithley DMM has annoying 'beep' when GPIB command is sent....I am sure there's a command to disable this!.....actually I think it's an error being generated....need to fix this....UPDATE: Send ":INIT:CONT OFF" also, per page 2-55 of 2015THD manual.

PS. There's a wee bug in the data formatting below......
Code: [Select]
HP3458A,21/11/2018 8:00:37 PM,4.53913284,25.0 C,33.2 %RH
KEITHLEY,21/11/2018 8:00:37 PM,4.53913284,25.0 C,33.2 %RH
HP3458A,21/11/2018 8:00:40 PM,8.55030307,25.0 C,33.3 %RH
KEITHLEY,21/11/2018 8:00:40 PM,4.53913284,25.0 C,33.3 %RH
HP3458A,21/11/2018 8:00:42 PM,8.55030307,25.0 C,33.3 %RH
KEITHLEY,21/11/2018 8:00:42 PM,8.55030307,25.0 C,33.3 %RH
HP3458A,21/11/2018 8:00:45 PM,5.93175246,25.0 C,33.4 %RH
KEITHLEY,21/11/2018 8:00:45 PM,8.55030307,25.0 C,33.4 %RH
HP3458A,21/11/2018 8:00:47 PM,5.93175246,25.0 C,33.4 %RH
KEITHLEY,21/11/2018 8:00:47 PM,5.93175246,25.0 C,33.4 %RH
HP3458A,21/11/2018 8:00:50 PM,1.10277879,25.0 C,33.4 %RH
KEITHLEY,21/11/2018 8:00:50 PM,5.93175246,25.0 C,33.4 %RH
HP3458A,21/11/2018 8:00:52 PM,1.10277879,25.0 C,33.4 %RH
KEITHLEY,21/11/2018 8:00:52 PM,1.10277879,25.0 C,33.4 %RH
HP3458A,21/11/2018 8:00:55 PM,4.37050003,25.0 C,33.4 %RH
KEITHLEY,21/11/2018 8:00:55 PM,1.10277879,25.0 C,33.4 %RH
HP3458A,21/11/2018 8:00:57 PM,4.37050003,25.0 C,33.4 %RH
KEITHLEY,21/11/2018 8:00:57 PM,4.37050003,25.0 C,33.4 %RH
HP3458A,21/11/2018 8:01:00 PM,3.19072211,25.0 C,33.4 %RH
KEITHLEY,21/11/2018 8:01:00 PM,4.37050003,25.0 C,33.4 %RH
HP3458A,21/11/2018 8:01:02 PM,3.19072211,25.0 C,33.4 %RH
KEITHLEY,21/11/2018 8:01:02 PM,3.19072211,25.0 C,33.4 %RH
HP3458A,21/11/2018 8:01:05 PM,7.16935305,25.0 C,33.4 %RH
KEITHLEY,21/11/2018 8:01:05 PM,3.19072211,25.0 C,33.4 %RH
HP3458A,21/11/2018 8:01:07 PM,7.16935305,25.0 C,33.4 %RH
KEITHLEY,21/11/2018 8:01:07 PM,7.16935305,25.0 C,33.4 %RH
HP3458A,21/11/2018 8:01:10 PM,8.15781706,25.0 C,33.4 %RH
KEITHLEY,21/11/2018 8:01:10 PM,7.16935305,25.0 C,33.4 %RH
HP3458A,21/11/2018 8:01:12 PM,8.15781706,25.0 C,33.4 %RH
KEITHLEY,21/11/2018 8:01:12 PM,8.15781706,25.0 C,33.4 %RH
HP3458A,21/11/2018 8:01:15 PM,1.56956653,25.0 C,33.5 %RH
KEITHLEY,21/11/2018 8:01:15 PM,8.15781706,25.0 C,33.5 %RH
HP3458A,21/11/2018 8:01:17 PM,1.56956653,25.0 C,33.5 %RH
KEITHLEY,21/11/2018 8:01:17 PM,1.56956653,25.0 C,33.5 %RH
HP3458A,21/11/2018 8:01:20 PM,4.12928689,25.0 C,33.5 %RH
KEITHLEY,21/11/2018 8:01:20 PM,1.56956653,25.0 C,33.5 %RH
HP3458A,21/11/2018 8:01:22 PM,4.12928689,25.0 C,33.5 %RH
KEITHLEY,21/11/2018 8:01:22 PM,4.12928689,25.0 C,33.5 %RH
HP3458A,21/11/2018 8:01:25 PM,2.5474837,25.0 C,33.5 %RH
KEITHLEY,21/11/2018 8:01:25 PM,4.12928689,25.0 C,33.5 %RH

Ian.
« Last Edit: November 21, 2018, 08:42:34 pm by IanJ »
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 
The following users thanked this post: Conrad Hoffman, denimdragon

Offline alm

  • Super Contributor
  • ***
  • Posts: 1257
  • Country: 00
Re: 3458a logging via Windows app.....revisited
« Reply #19 on: November 21, 2018, 09:03:04 pm »
PS. Keithley DMM has annoying 'beep' when GPIB command is sent....I am sure there's a command to disable this!.....actually I think it's an error being generated....need to fix this....UPDATE: Send ":INIT:CONT OFF" also, per page 2-55 of 2015THD manual.
I remember the error beep and having to send ":INITIATE:CONTINUOUS OFF" as one of the Keithley quirks, indeed. Took quite a while until I figured out the solution.
 

Offline alm

  • Super Contributor
  • ***
  • Posts: 1257
  • Country: 00
Re: 3458a logging via Windows app.....revisited
« Reply #20 on: November 21, 2018, 10:49:53 pm »
A quick test on a HP 3458A connected to an Agilent E2050A (predecessor of the E5810A without all the new-fangled stuff like web interfaces :P). I used a Python shell with python-vxi11 to send commands through the E2050A. This instrument is on GPIB address 20.
Code: [Select]
# Initialize
>>> import vxi11
>>> instr = vxi11.Instrument("TCPIP::1x.x.x.x::gpib,20::INSTR")
 # Send a random command to make it go to remote mode
>>> instr.write('DISP ON')
 # At this point the REM annunciator is lit, and front panel keys other than local are disabled.
 # Send GTL
>>> instr.local()
 # The REM annunciator turns off, and front panel keys work again
I checked the manual again, and the LOCAL 7 commands are for HP 200/300 BASIC, so they're irrelevant for modern computers. Sending those to the 3458A produces an error, as expected. You just have to tell the GPIB controller to send the GTL command and / or release the REM line. In the NI 488 C bindings, this would be ibloc(), and pwlps describes a few posts earlier how to do it with VISA. In the VXI-11 bindings I was using for this test, it's Instrument.local(). Before this, I issue DISP ON and TRIG AUTO to get the DMM into a usable state for interactive use.
 
The following users thanked this post: IanJ

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #21 on: November 21, 2018, 11:15:39 pm »
I checked the manual again, and the LOCAL 7 commands are for HP 200/300 BASIC, so they're irrelevant for modern computers. Sending those to the 3458A produces an error, as expected. You just have to tell the GPIB controller to send the GTL command and / or release the REM line. In the NI 488 C bindings, this would be ibloc(), and pwlps describes a few posts earlier how to do it with VISA. In the VXI-11 bindings I was using for this test, it's Instrument.local(). Before this, I issue DISP ON and TRIG AUTO to get the DMM into a usable state for interactive use.

Aha!......this prompted me to do more testing because pwlps had sent me an updated DLL to do just this (there are two applications, I am just modifying one of them right now)......but I think it was written to call GTL on shutdown of the app, which indeed does work and it releases the 3458A back to local mode. A good step forward though.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline Conrad Hoffman

  • Super Contributor
  • ***
  • Posts: 1132
  • Country: us
    • The Messy Basement
Re: 3458a logging via Windows app.....revisited
« Reply #22 on: November 22, 2018, 01:02:28 am »
Wow, that reminds me of the HP 85 I used to use. We've come a ways.
 

Offline acts238willy

  • Regular Contributor
  • *
  • Posts: 68
  • Country: us
Re: 3458a logging via Windows app.....revisited
« Reply #23 on: November 22, 2018, 02:48:30 am »
+Sadly, the old gear is still very good, ppm-wise.
The Datron, HP, etc., GPIB stuff that all calls for
the HP85 needs a modern solution for data collection.
I get some help from Digelent's program called
'Labview Home'... it's a student copy of Labview,
dated 2014, for less than $60. It has good tools
for my 3458s.
 

Offline Conrad Hoffman

  • Super Contributor
  • ***
  • Posts: 1132
  • Country: us
    • The Messy Basement
Re: 3458a logging via Windows app.....revisited
« Reply #24 on: November 22, 2018, 04:03:29 am »
With the right meter setup, say "F1R0Z0N3T3D3" to blank the display and fix the range, I can read at about 60 ms intervals. OK for what I tend to do, but not record breaking speed. How fast is your program?
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #25 on: November 22, 2018, 08:31:13 pm »
Hi all,

Some updates, see screenshot in post#1 above.

Added a RESET to close the devices......this is in tandem with the STOP buttons and I felt necessary because GPIB on different brands of devices etc is a fickle thing!
The 3458A has it's issues on shutting down GPIB.....whilst the Keithley has it's issues on starting up GPIB!
However, the most important thing I came across is the retry feature of Pawel's code......simply stunning to see the Keithley GPIB having trouble at startup but the app continuing to retry and controlling the GPIB traffic and after 10secs or so it's all stable and working.

Got the Chart working, screenshot shows device 1 active, but it will display both devices 1 & 2. PS. screenshot is a bit misleading as I screen-captured it with only 140 datapoints loaded out of the 500 it is set with.
Scales are adjustable as is the number of x-axis datapoints.
The chart is a rolling type based on the datapoints.
I may add an auto-centre and window adjust feature (I did that on my excel vba chart) as it makes it easier/quicker to narrow right down on a voltage signal for example.
Temperature/Humidity is not logged at the moment......I am thinking that can be for the external graph analysys based on the CSV.

Added an export to CSV. This is so that you can basically copy the current CSV being written to, to another file (date & time stamped) without distrurbing it.

By the end of the week I will publish the EXE's so that others can play with it..........for me it will be invaluable with my 3458A during my PDVS2 production testing.

To do: Play with NPLC on the 3458A and see what effect this has on the app. Also need to add functionality to save-all settings.

PS. My next VB app will be to automate calibration of my PDVS2's without human intervention......i.e.: VB reads output voltage of PDVS2 via GPIB, VB sends instruction to PDVS2 to adjust up/down, VB instructs PDVS2 to save cal (zero & span DAC adjustment)............this will save me hours and hours of calibrating batches pf PDVS2's!!!

Ian.
« Last Edit: November 22, 2018, 08:45:24 pm by IanJ »
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #26 on: November 22, 2018, 11:11:13 pm »
Quick screenshot attached.

3458A in yellow, Keithley 2015THD in aqua........two PDVS2 reference sources........amazing difference in stability of DMM.
Keithley has a filter enabled running at 100. 3458A has an NPLC set at 20 only.

Ian.

Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 
The following users thanked this post: Conrad Hoffman

Offline alm

  • Super Contributor
  • ***
  • Posts: 1257
  • Country: 00
Re: 3458a logging via Windows app.....revisited
« Reply #27 on: November 23, 2018, 06:24:38 am »
The Keithley 2015 trace appears to have periodic noise in it. Could this be environment temperature changes due to the heating / AC switching on / off?
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #28 on: November 23, 2018, 07:07:55 am »
The Keithley 2015 trace appears to have periodic noise in it. Could this be environment temperature changes due to the heating / AC switching on / off?

Not sure....I'll look into it. I also have a 2nd 2015THD so will try that.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #29 on: November 23, 2018, 11:45:25 pm »
Hi all,

Screenshot in post #1 updated.

Some more work done on the chart/graph:-
Auto-Scale button will look at the data on the chart and set a max and min scale around those values. You can of course still set your own values.
Add Max-Difference-Recorded which is basically the highest minus the lowest on the chart.
Clear-Chart button wipes everything.
PS. See the screenshot and notice the big dip near the end.......thats my air-con switching on in the workshop so looks like I need to add a mains filter there........!

Other stuff:-
Save-Settings button added so now all user adjustable data/values is saved off.
Enable-Log checkbox added.
Added Repeat-Command value to the Devices config area so you can see what command will ultimately be repeated to the device (last on the list), a bit clearer.

Keithley
Regarding the wild oscillating values from my Keithley 2015THD......the other one I have is just the same.....but thats as far as I have looked into this. It's not the PDVS2's, because I swapped them over and the problem stayed with the Keithley.

This weekend I will be going back to look at the GPIB startup etc.....I got some more good info from Pawel so will be looking at that......if my VB skills allow!

By Sunday I will release the first EXE's for the apps (the two dialog boxes in the screenshots are two separate installs).

Thanks,

Ian.
« Last Edit: November 23, 2018, 11:54:26 pm by IanJ »
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Online Andreas

  • Super Contributor
  • ***
  • Posts: 2407
  • Country: de
Re: 3458a logging via Windows app.....revisited
« Reply #30 on: November 24, 2018, 04:36:52 am »
Keithley has a filter enabled running at 100. 3458A has an NPLC set at 20 only.
Hello,

0.7 seconds device response time for 100 NPLC ?
I guess there is something wrong with aquisition time.
I would expect around 6 seconds with auto zero active.

I usually have around 4-6 uVpp on a K2000 (which is similar) with 10 NPLC in 10V range on my references.
 (0.6 sec / reading on K2000 with 50 Hz mains frequency)
So with 100 NPLC you should not get 50 uVpp.

with best regards

Andreas

 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #31 on: November 24, 2018, 12:18:17 pm »
V1.0 released. See post #1.

I am now working on the query/send startup issue and also the 'Playback Chart'.

Have fun!

Ian.
« Last Edit: November 24, 2018, 01:01:08 pm by IanJ »
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Online Grandchuck

  • Regular Contributor
  • *
  • Posts: 69
  • Country: us
Re: 3458a logging via Windows app.....revisited
« Reply #32 on: November 24, 2018, 05:49:46 pm »
Thanks Ian! :)
 
The following users thanked this post: IanJ

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #33 on: November 25, 2018, 03:42:20 pm »
Hi all,

V1.1 is available for download in post #1.
New screenshot posted also.

This new version transforms the GPIB device startup. There are several ways to communicate with any device, some commands are sent expecting a reply and when that reply doesn't come then the app can generate an error. So, I found out from Pawel an alternate command to use in these conditions and which cuts back on many of the errors and resends.

Have fun.

Ian.

UPDATE:
 bug in the GUI of V1.1......I'll update a new V1.2 asap - Done!

Ian.
« Last Edit: November 25, 2018, 05:27:10 pm by IanJ »
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Online Grandchuck

  • Regular Contributor
  • *
  • Posts: 69
  • Country: us
Re: 3458a logging via Windows app.....revisited
« Reply #34 on: November 26, 2018, 05:59:50 pm »
Many thanks Ian.  Version 1.2 is running here.  A very nice contribution to the metrology group.
 
The following users thanked this post: IanJ

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #35 on: November 26, 2018, 08:32:14 pm »
V1.3 now available in post #1

Changes:-

V1.3 - Added Send Async command to Dev1 and Dev2. Useful when all you want to do is send your device a blind command.
V1.3 - Added a HELP button with some info about the different command types.
V1.3 - Added some defaults for the CSV path. If it's left blank then it will pick up the folder where the main EXE is being run from and where the Log.csv is.
V1.3 - Made the installation of the app portable (easier)......just unzip to a folder of your choice and run the EXE file there. No setup.exe required. If you have an existing version installed you may need to uninstall it first. Note: Any problems with running the portable version then let me know and I will go back to the full install.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline branadic

  • Super Contributor
  • ***
  • Posts: 1484
  • Country: de
Re: 3458a logging via Windows app.....revisited
« Reply #36 on: November 26, 2018, 10:32:58 pm »
Just my two cents... have you thought about putting all settings in a seperate tab and only have the necessary things like the diagram and some start/stop buttons on the main tab? Would make things much more clearly. By now the program is somewhat overcharged. Please understand it just as a suggestion with an eye on user experience. The engineer tends to put everthing possible into one window, with the result of bad usablility.

-branadic-
Fluke 8050A | Prema 5000 | Prema 5017 SC | Advantest R6581D | GenRad 1434-G | Datron 4000A | Tek 2465A | VNWA2.x with TCXO upgrade and access to: Keysight 3458A, Keithley 2002, Prema 5017 SC, 34401A, 34410A, Keithley 2182A, HDO6054, Keysight 53230A and other goodies at work
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #37 on: November 27, 2018, 12:24:41 am »
Just my two cents... have you thought about putting all settings in a seperate tab and only have the necessary things like the diagram and some start/stop buttons on the main tab? Would make things much more clearly. By now the program is somewhat overcharged. Please understand it just as a suggestion with an eye on user experience. The engineer tends to put everthing possible into one window, with the result of bad usablility.

-branadic-

I hear you.....and I agree......but to develop the app just for fun, for free and with limited time it's just easier and quicker to throw it all on one form. VB isn't my preferred language, I've only ever developed a few VB apps......so there's obstacles there also.
But yes, you are right, I do like it, as an engineer, to have it all right there especially during development.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Online pwlps

  • Regular Contributor
  • *
  • Posts: 163
  • Country: fr
Re: 3458a logging via Windows app.....revisited
« Reply #38 on: November 27, 2018, 10:26:01 am »
Hi Ian,

Below is a screenshot of my test of V1.3 with an Agilent 34410A (I'm not a metrology guy and this one is enough for me) via USB.

A few observations:

- the reset button works correctly: the 344140A goes back to local
- after pressing "stop" the control panel with query buttons remains disabled (it only gets enabled again after "reset" and "create dev"), it might be more practical if it were enabled again after stopping the automatic run
- when I pressed "autoscale" the chart tripped an exception, I could continue the acquisition but without chart (see screenshot).   

Pawel
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #39 on: November 27, 2018, 11:35:22 am »
Hi Ian,

Below is a screenshot of my test of V1.3 with an Agilent 34410A (I'm not a metrology guy and this one is enough for me) via USB.

A few observations:

- the reset button works correctly: the 344140A goes back to local
- after pressing "stop" the control panel with query buttons remains disabled (it only gets enabled again after "reset" and "create dev"), it might be more practical if it were enabled again after stopping the automatic run
- when I pressed "autoscale" the chart tripped an exception, I could continue the acquisition but without chart (see screenshot).   

Pawel

Hi,

I'll look at the STOP button tonight.

The Auto-Scale crashed the app on your PC due to the negative values you are pulling from your 34410A...….I'll have to add some code so it deals with negative numbers correctly. Might be fun!

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #40 on: November 27, 2018, 08:58:25 pm »
Hi all,

V1.4 available in post #1.

V1.4 - Fixed bug when reading negative values from devices which was causing the AUTO SCALE to crash. Only positive values are allowed....for now.
V1.4 - Added a warning pop-up dialog box. This will be used more and more for displaying warnings/errors etc, for now doesn't appear much.
V1.4 - I have started to develop a PLAYBACK CHART, see the button under MISC. This is very, very preliminary just to get the ball rolling. It should be used to load a CSV with only ONE deviced logged only.
V1.4 - When STOP is pressed on the devices it now re-enables the command input areas.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #41 on: November 28, 2018, 12:53:06 pm »
Hi all,

V1.5 available in post #1.

V1.5 - Fixed bug in Index No. creation in CSV file when running 2 devices. Whilst at it, added error trapping around CSV file, including creating file if it doesn't exist.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline pelule

  • Frequent Contributor
  • **
  • Posts: 509
  • Country: de
  • What is business? It’s other people’s money
Re: 3458a logging via Windows app.....revisited
« Reply #42 on: November 28, 2018, 01:01:23 pm »
Hi Ian
tere seems a issue downloding the file.
Got message "You are not allowed to access this section"
/PeLuLe
You will learn something new every single day
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #43 on: November 28, 2018, 01:14:10 pm »
Hi Ian
tere seems a issue downloding the file.
Got message "You are not allowed to access this section"
/PeLuLe

You mean from the EEVBlog server?........just tried it and it works for me.

Alternative download from my own server:-
https://www.ianjohnston.com/images/stories/IanJ/GPIB/IODeviceAppV1_5.zip

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Online Grandchuck

  • Regular Contributor
  • *
  • Posts: 69
  • Country: us
Re: 3458a logging via Windows app.....revisited
« Reply #44 on: November 28, 2018, 03:13:30 pm »
Hello Ian,

With version 1.5, autoscale is not working?
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #45 on: November 28, 2018, 06:18:40 pm »
Hello Ian,

With version 1.5, autoscale is not working?

Fixed......a wee typo. New version uploaded.

V1.6 - Fixed bug in AUTO SCALE function. Added more controls and functionality to the Playback Chart (zoom in/out and up/down control over Y-axis scale), also added more error trapping and some grid colours to both the charts/graphs.


Ian.
« Last Edit: November 28, 2018, 06:51:51 pm by IanJ »
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Online Grandchuck

  • Regular Contributor
  • *
  • Posts: 69
  • Country: us
Re: 3458a logging via Windows app.....revisited
« Reply #46 on: November 28, 2018, 08:01:59 pm »
 :)1.6 fixed it!  Thanks Ian.
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #47 on: November 28, 2018, 09:07:27 pm »
Hi all,

V1.7 available in post #1.

V1.7 - Changed the way the Playback .CSV file is selected

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Online Grandchuck

  • Regular Contributor
  • *
  • Posts: 69
  • Country: us
Re: 3458a logging via Windows app.....revisited
« Reply #48 on: November 28, 2018, 09:42:28 pm »
Ian, I used Photoshop to make the grid brighter.  On my screen, it is hard to see. 
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #49 on: November 28, 2018, 11:41:17 pm »
Ian, I used Photoshop to make the grid brighter.  On my screen, it is hard to see.

Ok, I'll notch it up a bit tomorrow night.

I will be tackling the parsing of dual logs, temp/ humidity and displaying both on the playback chart also. Not looking forward to this one.....it gets messy with dual scales I think.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #50 on: November 29, 2018, 07:34:20 pm »
Hi all,

V1.8 available in post #1.

V1.8 - Added Temperature to the main chart. Increased brightness of grey grid on chart a little bit.

New screenshots added to post #1 also.

Note: Have decided to defer the Playback chart mods at least until Friday if not the weekend.

Ian.

Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #51 on: November 30, 2018, 01:57:02 pm »
Hi all,

V1.9 available in post #1.

V1.9 - Added RESET buttons to the Recorded Maximum's below the chart. Fixed a couple of bugs around the chart control Device 1/Device2/Temperature check boxes.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Online Grandchuck

  • Regular Contributor
  • *
  • Posts: 69
  • Country: us
Re: 3458a logging via Windows app.....revisited
« Reply #52 on: November 30, 2018, 02:44:15 pm »
Ian, version 1.9 does not work here?
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #53 on: November 30, 2018, 02:44:57 pm »
Hi all,

V1.10 available in post #1.

V1.10 - Added RESET button to Auto Scale function. This saves having to stop the chart and restart it again if your values have changed.......necessary because Auto Scale remembers it max/min since the chart had started.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #54 on: November 30, 2018, 02:45:50 pm »
Ian, version 1.9 does not work here?

Fixed an issue. There is now an additional .DLL file in the ZIP file which must reside alongside the others. Not sure why it's required now, I never added any PowerPack toolbox items as far as I know.....not recently anyways. Hopefully all will be ok.

Update: Ahhh yes, the coloured rectangles to signify the chart colours are from the PowerPack .DLL.

Ian.
« Last Edit: November 30, 2018, 03:20:59 pm by IanJ »
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Online Grandchuck

  • Regular Contributor
  • *
  • Posts: 69
  • Country: us
Re: 3458a logging via Windows app.....revisited
« Reply #55 on: November 30, 2018, 03:25:47 pm »
Version 1.10 running here.  Like good Scotch ... just keeps getting better! ;)
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #56 on: November 30, 2018, 09:15:19 pm »
Hi all,

V1.11 available in post #1.

V1.11 - Playback Chart - Able to parse .CSV by entering device name before loading .CSV

So if you have two devices configured and log to .CSV then there are actually two graphs embedded in the .CSV......so now on the PlayBack chart you can select which one you want to view.
Ideally, both graphs could be displayed at once but the current .CSV format won't allow that.......I'd need to have a single sample rate for both devices.......Nahhhh!

Ian.
« Last Edit: November 30, 2018, 09:48:13 pm by IanJ »
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Online pigrew

  • Frequent Contributor
  • **
  • Posts: 515
  • Country: us
Re: 3458a logging via Windows app.....revisited
« Reply #57 on: December 01, 2018, 08:58:09 pm »
Is there a possibility to log many devices at once?  Since seeing this code, I've wanted to implement modular support for different DMM models, similar to BenchVue, and also real-time enabling and disabling of meters, to allow for autocal cycles. In my code, I usually request a sample from all instruments, then wait for a response from all instruments, then delay until the requested sample period is reached. This way, I get synchronous datapoints which are more easily comparable.

Otherwise, points can be left blank in some columns, or have a meter ID column and exactly one measurement per row (making the output have many more rows).  Maybe write to a SQLite DB or intermediate use, and then convert to CSV for viewing?
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #58 on: December 01, 2018, 09:38:41 pm »
Is there a possibility to log many devices at once?  Since seeing this code, I've wanted to implement modular support for different DMM models, similar to BenchVue, and also real-time enabling and disabling of meters, to allow for autocal cycles. In my code, I usually request a sample from all instruments, then wait for a response from all instruments, then delay until the requested sample period is reached. This way, I get synchronous datapoints which are more easily comparable.

Otherwise, points can be left blank in some columns, or have a meter ID column and exactly one measurement per row (making the output have many more rows).  Maybe write to a SQLite DB or intermediate use, and then convert to CSV for viewing?

My code logs to the same CSV for both devices and even if both devices have a different sample rate. This does make things tough when wanting to compare results......however, a half-way house answer is to set the time base of both to the same and the entry in the CSV looks like as follows, i.e. alternating writes to the CSV:-

Index, Device, Date/Time, Value, Temperature, Humidity

Code: [Select]
1,HP3458A,28/11/2018 1:00:16 PM,1.00003333,24.9,37.9
2,2015THD,28/11/2018 1:00:16 PM,9.99990603,24.9,37.9
3,HP3458A,28/11/2018 1:00:17 PM,2.00003333,24.9,37.9
4,2015THD,28/11/2018 1:00:17 PM,8.99994451,24.9,37.9
5,HP3458A,28/11/2018 1:00:20 PM,3.00003467,24.9,37.9
6,2015THD,28/11/2018 1:00:20 PM,7.99994451,24.9,37.9
7,HP3458A,28/11/2018 1:00:22 PM,4.00003467,24.9,37.9
8,2015THD,28/11/2018 1:00:22 PM,6.99991115,24.9,37.9
9,HP3458A,28/11/2018 1:00:24 PM,5.00003156,24.9,37.9
10,2015THD,28/11/2018 1:00:24 PM,5.99991115,24.9,37.9

I have been gathering some thoughts on where to go from here and with the Playback Chart in mind.
First off I think I'll add a header to the CSV that will record things like the sample rates(s), single/dual logs etc as it will help the Playback Chart work out what it can and can't do with the data.

Nice idea about specifying time-out periods in order to run ACAL from the app also........it had crossed my mind before, and I just need to work out a way to do it thats can be made generic/adjustable to different device types, and also a way to log that data in the CSV so that any spikes from such are made clear in the charts/graphs.

I don't use a SQL DB, I just use a Datatable within VS.

So much I can do with this.....problem is file handling is not my forte and it takes me a wee while to get it right!

Ian.
« Last Edit: December 01, 2018, 09:40:40 pm by IanJ »
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #59 on: December 01, 2018, 09:40:09 pm »
were you able to investigate repeating average vs moving average @ NPLC100?

Not yet......a quick look and my 2015THD's and they are both set for moving average.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #60 on: December 03, 2018, 07:41:33 pm »
Hi all,

V1.12 available in post #1.

I have changed the way that dual devices are run by adding a separate RUN button and it's own sample rate. I have also added an extra display parameter "CSV File No. Lines".

Also, the Playback Chart function now supports reading dual logged CSV files......very preliminary but does appear to work. Tha caveat here is that it's only really useful if you have logged running both devices using the same sample rate. The entries in the log assume that each log for device 1 & device 2 were taken at the same time.

The screenshot below is missing some info on the yellow trace as it's just a text......both should be the same length. Out of interest, yellow=3458A, aqua=2015THD.

PS. I have left V1.11 available to download due to changes made to V1.12 are virtually untested.

Note: Next thing to do is get the temperature & humidity details on the chart.

UPDATE: Yep, there's quite a few bugs with the playback chart in this version.....might want to wait until the next one. Problem zooming etc.

Ian.
« Last Edit: December 03, 2018, 08:42:29 pm by IanJ »
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #61 on: December 03, 2018, 09:10:48 pm »
Hi all,

V1.13 available in post #1.

I have made some mods to the zoom & scroll controls in the Playback Chart and fixed the issues with dual log display etc.

I have also included in the .zip a couple of sample log files. Device names are in the filename.

LogSampleDual_HP3458A_2015THD.csv
LogSampleSingle_HP3458A.csv

PS. If you have dual logged to .CSV (two devices) but just want to playback one of them then just leave the other one empty and the chart will only pull the one named into the chart wondow.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #62 on: December 04, 2018, 06:50:11 pm »
Hi all,

V1.14 available in post #1.

Mods made to the Playback Chart:
- Ability to display logged temperature & humidity, so now 4 graphs on the 1 chart.
- Temp & Humidity share the same right hand scale which is user adjustable.
- Settings on the Playback Chart can now be saved.

I have included another sample CSV file......which is the one shown on the Playback screenshot. You may notice the humidity slowly decreasing over time from the start.......that's because I set up the test, started logging then shortly after left the workshop for the night. The temperature rolls of a little also but my VB controlled air-con/heater kept it within a degree or so....:-)

Note:-
There is an apparent issue with the Zoom Out control which shows up when you zoom in and then try to zoom out again. Sometimes you do not get all the way out again, and this is because the zoom facility actually zooms around the centreline of the chart (see CL on screenshot), so if you have scrolled too far to one end of the graph it cannot zoom out and retaining  the same centreline.
I may do something about this, but the workaround is just to press DISPLAY ALL.

Thanks,

Ian.
« Last Edit: December 04, 2018, 07:11:16 pm by IanJ »
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #63 on: December 04, 2018, 10:16:45 pm »
Hi all,

V1.15 available in post #1.

I have added SHIFT UP and SHIFT DOWN buttons to the Playback Chart.
This moves the chart up and down by 10% of the current range of the displayed chart. Effects Device1 & Device 2 only.

To do: Work out how to auto-repeat the various buttons.......

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #64 on: December 07, 2018, 04:08:38 pm »
Hi all,

V1.16 available in post #1.

I have added TOOLTIP values to the Playback chart, so hover your mouse over the traces on the chart and read the value at that point. There's a checkbox at top right corner to enable/disable this since on the very odd occasion it was crashing the program when floating the mouse over the left side scale.....wierd!

I have added an AUTO-DETECT MIN/MAX checkbox for the Playback chart. Select this before loading the .CSV file and the min/max values for Device1 & 2 are detected and use to scale the chart automatically.
On loading the auto-detected values 10% padding is added top/bottom.
See screenshot in post #1.

TO DO: I want to add in a PPM graph (calculated) on the Playback chart but am struggling to get more Y-axis scales other than the one on the left and one on the right to display.....it seems a limitation of MS Chart object.......however, I may go ahead anyway and just display in text format the scale.

Ian.
« Last Edit: December 07, 2018, 04:19:54 pm by IanJ »
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline blackdog

  • Frequent Contributor
  • **
  • Posts: 580
  • Country: nl
  • Please stop pushing bullshit...
Re: 3458a logging via Windows app.....revisited
« Reply #65 on: December 08, 2018, 07:22:13 pm »
Hi Ian  :)

First this, Thank You!

I have your software now working but after quite a bit of headache...
That was largely due to the Keysight Connection Expert 2018.
This software lies right in your face!

My GPIB cable had fallen out of one of my measuring instruments and when I asked if there was a connection with this command "Check Connecion Status"
the software indicated that everything was OK for the relevant GPIB instrument.
I had the connector in my hand and the cable only went to my measuring computer... Wireless GPIB!

If I have emptied the "Keysight Connection Expert 2018", i.e. removed all measuring instruments, then the scan function cannot find any measuring instruments!
I then have to use the "+Add" key and enter the address for the GPIB group and the measuring instrument will be displayed.

If I have emptied the "Keysight Connection Expert 2018" and in the LAN group I have to enter the IP address of my measuring instruments, sarcastic mode => well coded! "Developers" (hobby coders, mini brains)

Your software
I do have a few comments about your software.
Is it possible to use a ";" instead of a "," in the csv file? 
In the Dutch language gives "," problems when importing into Excel.

Two picturen so you can see its working.
This is only your version V1.16 software measuring my Agilent 3458A



And this is proof that your software works at the same time with the Keysight "horror" BenchVue module also measuring my 10V LAB reference after zeroing the 34461A instrument on the 10V range.


Keep op the good work!

Kind regards,
Bram
“Two things are infinite, the universe and human stupidity, and I am not yet completely sure about the universe.”
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #66 on: December 08, 2018, 07:22:40 pm »
Hi all,

V1.17 available in post #1.
(V1.16 remains available as this new version has some tentative new functions)

Playback Chart:-
I have added the ability to plot PPM deviation on the chart for Device 1 or 2. See the screenshot in post #1.
This is calculated and plotted on the chart dynamically from the imported CSV data and is not saved back to the .CSV file.
When selected, the zoom & shift button are disabled, it's a Display All function only.

There is no way that I know to enable more than 1 secondary scale to an MS Chart, so I have had to 'make my own' which involved a lot of extra work.....hence the tentative V1.17.

Please note that large CSV files take time to process PPM Deviation, so the GUI may lock for a few seconds.

I have also fixed a small bug in the Auto-detect Min/Max values.

PS. The noisy aqua coloured plot in the screenshot is my noisy Keithley 2015THD.......I must have a look at them (2off) and find out what settings I can tweak.
PPS. Tooltips are not enabled for the PPM plot due to the hard-coding nature of the PPM scale.


Ian.
« Last Edit: December 08, 2018, 07:49:22 pm by IanJ »
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #67 on: December 08, 2018, 07:45:39 pm »
Hi Ian  :)

First this, Thank You!

I have your software now working but after quite a bit of headache...
That was largely due to the Keysight Connection Expert 2018.
This software lies right in your face!

My GPIB cable had fallen out of one of my measuring instruments and when I asked if there was a connection with this command "Check Connecion Status"
the software indicated that everything was OK for the relevant GPIB instrument.
I had the connector in my hand and the cable only went to my measuring computer... Wireless GPIB!

If I have emptied the "Keysight Connection Expert 2018", i.e. removed all measuring instruments, then the scan function cannot find any measuring instruments!
I then have to use the "+Add" key and enter the address for the GPIB group and the measuring instrument will be displayed.

If I have emptied the "Keysight Connection Expert 2018" and in the LAN group I have to enter the IP address of my measuring instruments, sarcastic mode => well coded! "Developers" (hobby coders, mini brains)

Your software
I do have a few comments about your software.
Is it possible to use a ";" instead of a "," in the csv file? 
In the Dutch language gives "," problems when importing into Excel.

Two picturen so you can see its working.
This is only your version V1.16 software measuring my Agilent 3458A

And this is proof that your software works at the same time with the Keysight "horror" BenchVue module also measuring my 10V LAB reference after zeroing the 34461A instrument on the 10V range.

Keep op the good work!

Kind regards,
Bram

Hi,

Nice screenshots.

This project has been great fun........and to tell you the truth I'd never have started it if I didn't have a motive!.......Which is, I have come up with an idea to self-calibrate my PDVS2's on my wee production line, i.e. PDVS2 sends voltage to 3458A via GPIB, Windows app reads the voltage via GPIB and then communicates back to the PDVS2 via USB in calibration mode........I just have to press a button and the calibration is all automatic instead of sitting at a PDVS2 pressing buttons. The idea was to get this app working to a satisfactory level then modify it for the PDVS2 cal............but I keep on making mods to the code!!!!

I must admit, I am using Keysight IO libraries version 18.1 and yes it's a bit non-intuitive.......but once I got my devices added it's no problem. I only had to clear them once.

Regarding semi-colon's versus comma's, unfortunately I just went with commas per Comma-Separated-Values which is the standard.
If I get time I will add in a selection for it........but it does mean adjusting quite a lot of code, i.e. for the Playback chart etc.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline TiN

  • Super Contributor
  • ***
  • Posts: 4045
  • Country: tw
  • xDevs.com/live - 24/7 lab feed
    • xDevs.com
Re: 3458a logging via Windows app.....revisited
« Reply #68 on: December 08, 2018, 08:14:29 pm »
I'd also get rid of all those meaningless digits after 7th in graphs/charts so it looks more clean and tidy.  :-DMM
Perhaps consider to switch into engineering notation (e.g. 9.9999532e+0 for VDC , or 100.00532E-6 for 100uamps).
YouTube | Chat room | Live-cam | Have documentation to share? Upload here! No size limit, firmware dumps, photos.
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #69 on: December 08, 2018, 08:49:30 pm »
I'd also get rid of all those meaningless digits after 7th in graphs/charts so it looks more clean and tidy.  :-DMM
Perhaps consider to switch into engineering notation (e.g. 9.9999532e+0 for VDC , or 100.00532E-6 for 100uamps).

Part of the tidy up later on when the basics are done........albeit V1.17 PlayBack chart has it limited to 7 already (part of the PPM Deviation mods).
During coding the extra digits helped me narrow down a rounding issue with the auto-detect main/max Playback.

Cheers.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 
The following users thanked this post: TiN

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #70 on: December 08, 2018, 09:02:47 pm »
Regarding semi-colon's versus comma's, unfortunately I just went with commas per Comma-Separated-Values which is the standard.
If I get time I will add in a selection for it........but it does mean adjusting quite a lot of code, i.e. for the Playback chart etc.

Hi,

V1.18 has been uploaded.
(V1.16 remains available as this new version has some tentative new functions)

I have added the functionality to select COMMA or SEMI-COLON as the delimiter for the CSV file generation. The settings is a couple of radio buttons on the main screen.
Please note that this affects the Playback Chart reading of the CSV's. so make sure you have the setting correct for the CSV file you want to read.

Ian.
« Last Edit: December 08, 2018, 09:48:36 pm by IanJ »
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #71 on: December 08, 2018, 10:53:58 pm »
Hi all,

Just a wee note to remind folks that this app can be used to connect to newer equipment as well.

Example:
Keysight 34461A (without optional GPIB interface).

So, connect the 34461A via ethernet to Lan and open Keysight IO Libraries Suite (Windows App) and ADD the device.
Once added, right click on the device in the IO Libraries suite and select COPY VISA ADDRESS.

Open the GPIB app and on Device 1 or 2 paste the address to the ADDRESS entry., select VISA as the interface type.

In my case the address for my 34461A = TCPIP0::192.168.1.139::inst0::INSTR

The AT RUN command for the 34461A =  :READ?

Ian.
« Last Edit: December 08, 2018, 11:18:16 pm by IanJ »
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline blackdog

  • Frequent Contributor
  • **
  • Posts: 580
  • Country: nl
  • Please stop pushing bullshit...
Re: 3458a logging via Windows app.....revisited
« Reply #72 on: December 09, 2018, 10:49:01 am »
Hi Ian,  :)

Thanks for the Comma/Semi-Colon option!

Here a screenshot on one of my 34461A DMM controled by your software.
The grafics and "auto scale" still can use some work, only sometimes it works.

In the display of my 34461A i always get a error when i use the "run" button, but the sofware starts logging anyway.
The picture shows my 10V LAB reference logt bij the 34461A.



Keep up the good work!

Kind regards,
Bram
“Two things are infinite, the universe and human stupidity, and I am not yet completely sure about the universe.”
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #73 on: December 09, 2018, 10:58:54 am »
Hi,

V1.19 has been uploaded.
(V1.16 remains available as this new version has some tentative new functions)

Fixed a bug in the Playback Chart where the PPM chart was not always loading, it seemed to take two attempts each time which was a clue to an issue with a later subroutine setting something that the proceeding one needed.

Added a NOTEPAD button on main screen linked to GPIBchannels.txt. I found I have to keep a text file to store all my handy notes, so this keeps them even handier. File is in .zip.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #74 on: December 09, 2018, 11:05:03 am »
Hi Ian,  :)

Thanks for the Comma/Semi-Colon option!

Here a screenshot on one of my 34461A DMM controled by your software.
The grafics and "auto scale" still can use some work, only sometimes it works.

In the display of my 34461A i always get a error when i use the "run" button, but the sofware starts logging anyway.
The picture shows my 10V LAB reference logt bij the 34461A.

Keep up the good work!

Kind regards,
Bram

Your 34461A DMM will error because it doesn't understand the PRE-RUN commands as they are for a Keithley 2015THD.
Change to the following (or erase all). The 34461A user manual explains all the commands and it really just depends on what you are looking to do.

*RST
CALC:SMO:RESP MED

Yes, the auto-scale does need a bit of work......I need to disable the button till enough data is gathered, and also fix the problem where when you hit the button it does nothing until the next data arrives......which can be a while if your sample rate is set long.
Don't forget to hit RESET on the auto-scale so that previously recorded data is not used to calculate the new max/min.

Ian.
« Last Edit: December 09, 2018, 11:42:43 am by IanJ »
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #75 on: December 09, 2018, 01:05:28 pm »
Hi all,

V1.20 available in post #1.
Screenshots update.

Tidied up the GUI and limited the number of digits shown after the D.P. across the board.
Added an ABOUT section on the main screen.
Tidied up the Playback screen.

NB. Have still got to test & validate the PPM Dev. graph properly on the Playback Chart etc.

Ian.
« Last Edit: December 09, 2018, 01:33:46 pm by IanJ »
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #76 on: December 09, 2018, 04:16:36 pm »
Hi all,

V1.21 available in post #1.

Slight tweak to PPM Dev. scale in Playback Chart.

NB. Have still got to test & validate the PPM Dev. graph properly on the Playback Chart etc. I am playing with PPM Deviation and also Tempco calcs (ppm/degC)

Ian.
« Last Edit: December 10, 2018, 07:00:31 am by IanJ »
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline blackdog

  • Frequent Contributor
  • **
  • Posts: 580
  • Country: nl
  • Please stop pushing bullshit...
Re: 3458a logging via Windows app.....revisited
« Reply #77 on: December 09, 2018, 04:29:34 pm »
Hi Ian,  :)

This is a picture of software V1.18 afther four after four hours of logging, blue is the 34461A DMM and yellow is the 3458A DMM both set to 10plc.


And this is a test with the 1.20 version of the software,  again the settings are such that I use 10PLC for both instruments and both instruments measure my LAB reference.


Is it not possible to create a configuration file for an instrument, a simple text file
In which you enter the settings you want to use for a 34461A or a Racal Dana 1991.
And that you choose the configuration file in your software via a load button?

The order for a LM399 testboard is from me, for your hard work  :D

Kind Regards,
Bram

PS,
The Chart is working better now.
“Two things are infinite, the universe and human stupidity, and I am not yet completely sure about the universe.”
 
The following users thanked this post: IanJ

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #78 on: December 10, 2018, 05:57:19 pm »
Hi all,

V1.22 available in post #1.

A slight GUI change to the Devices selection on the main app.

I have done a bit more work to the PPM Deviation functions on the Playback Chart, work on the calculations and work on the PPM scale (tough to code outside of the VB Chart object!).
Now able to select between PPM Deviation and PPM Tempco (ppm/degC) plotting.

Still not finished and still not working properly, I have still got some work to do and then to test & validate the PPM data properly.

Ian.
« Last Edit: December 10, 2018, 07:17:01 pm by IanJ »
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Online Grandchuck

  • Regular Contributor
  • *
  • Posts: 69
  • Country: us
Re: 3458a logging via Windows app.....revisited
« Reply #79 on: December 10, 2018, 07:11:51 pm »
Hello all,

A screenshot of two instruments running.  It was straightforward to get a 34465A added as instrument #2.

Thanks again Ian.  This is a valuable asset to my home lab.

I have ordered the temperature/humidity sensor.
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #80 on: December 10, 2018, 09:22:39 pm »
Hi all,

V1.23 available in post #1.

I have identified a problem reading the .CSV into the Playback Chart.........i.e. it does work, but some CSV's are dual device logs, some are single devices logs.......and it can trip up the code if you don't select properly.....so I need to re-write the sub that loads in the CSV so that it always gets it right.

I have started to do this but it's not finished so for now just select careful.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #81 on: December 10, 2018, 09:23:38 pm »
Hello all,

A screenshot of two instruments running.  It was straightforward to get a 34465A added as instrument #2.

Thanks again Ian.  This is a valuable asset to my home lab.

I have ordered the temperature/humidity sensor.

You'll not regret the temp/hum probe.......probably the most reliable thing of the whole project......:-)

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #82 on: December 11, 2018, 07:51:49 pm »
Hi all,

V1.24 available in post #1.

The problem with the Playback Chart CSV file loading is fixed.
The way the CSV is loaded is now slightly different. The DEVICE NAMES are automatically pulled from the CSV and the entry boxes on the Playback chart populated.
If it's a dual device recorded CSV then both are pulled in (yellow and blue), if it's a single device CSV then it just loads the one accordingly (yellow).

Ian.


Hi all,

V1.23 available in post #1.

I have identified a problem reading the .CSV into the Playback Chart.........i.e. it does work, but some CSV's are dual device logs, some are single devices logs.......and it can trip up the code if you don't select properly.....so I need to re-write the sub that loads in the CSV so that it always gets it right.

I have started to do this but it's not finished so for now just select careful.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #83 on: December 12, 2018, 04:43:48 pm »
Hi all,

V1.25 available in post #1.

Fixed issue where RESET button remained hidden when STOP pressed on main app.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #84 on: December 13, 2018, 09:25:20 pm »
Hi all,

V1.26 available in post #1.

I have made an attempt add adding an x-axis scale to the Playback Chart, units are Minutes.
It's not perfect, but it's a start. Also, it's only compatible with log files made in the past 7 or 8 versions (when I made a change to teh time stamp in the CSV).

I have left V1.25 available for download as there are quite a few mods to make this new version work.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #85 on: December 14, 2018, 03:08:57 pm »
Hi all,

V1.27 available in post #1.
V1.28 available in post #1.

I have tidied up the x-axis scale functionality on the Playback Chart.

I have left V1.25 available for download as there are quite a few mods to make this new version work.

Ian.
« Last Edit: December 14, 2018, 03:35:00 pm by IanJ »
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline blackdog

  • Frequent Contributor
  • **
  • Posts: 580
  • Country: nl
  • Please stop pushing bullshit...
Re: 3458a logging via Windows app.....revisited
« Reply #86 on: December 14, 2018, 05:56:06 pm »
Hi Ian,  :)

The Autoscale is still troublesome in the main program.
If i configure my 34461A as device-2 alone, it wil never work...

And is it posible to load the settings for device-1 and device-2 via a config file like your notepad button but then for 1 instrument.
so i wil have in de directory where your program is, say 10 different cdevice files, like this: 34461a-DC10V-100PLC.conf, 3458A-1V-10PLC, etc.
Than you can quickly chose device settings for a instrument.

Have a nice weekend, and i do not mean a coding weekend :-DD

Kind regards,
Bram
“Two things are infinite, the universe and human stupidity, and I am not yet completely sure about the universe.”
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #87 on: December 14, 2018, 07:35:08 pm »
Hi Ian,  :)

The Autoscale is still troublesome in the main program.
If i configure my 34461A as device-2 alone, it wil never work...

And is it posible to load the settings for device-1 and device-2 via a config file like your notepad button but then for 1 instrument.
so i wil have in de directory where your program is, say 10 different cdevice files, like this: 34461a-DC10V-100PLC.conf, 3458A-1V-10PLC, etc.
Than you can quickly chose device settings for a instrument.

Have a nice weekend, and i do not mean a coding weekend :-DD

Kind regards,
Bram

Yes, I found a bug in the AutoScale sub which meant values from Dev1 were being carried to the Dev2 routine. Fixed.

Note: There's a small problem with the Zoom In & Zoom Out controls on the main app. If there is very little noise on the source signal and the min/max recorded is extremely small then those two buttons don't appear to do anything. I can see what's going on and will fix it in a later version if I can.

V1.29 available in post #1.

PS. I hear what you are saying about the config file, but I doubt I will implement anything further there.......file handling is a pain to do (for me) as it means parsing the data, making sure it's all formatted correctly, and what to do if it isn't etc.

Ian.
« Last Edit: December 14, 2018, 07:44:38 pm by IanJ »
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline blackdog

  • Frequent Contributor
  • **
  • Posts: 580
  • Country: nl
  • Please stop pushing bullshit...
Re: 3458a logging via Windows app.....revisited
« Reply #88 on: December 14, 2018, 08:30:02 pm »
Hi Ian,

I understand, coding for me is very difficult, because I have dyslexia.
So coding it for myself wil not happen, its a hell for me.

It is very difficult for me to struggle through the HP3458A and the KeySight GPIB code.
There are so many differences between the different instruments and so few simple examples of how to apply the code.
I find analogue electronics much simpler...

I have searched myself crazy for my 34461A to put it on 100PLC mode via GPIB and I can't find it...

The way I do it now for this measuring instrument is to enter this string in your software: CONF:VOLT:DC 10,0.000003
This gives a 10V DC range with a 100 PLC value, not really clear to me.
I know the last part of the string: 0.000003 sets the resolution, but why not something like *PLC100,
Maybe I haven't searched well or it's in my blind spot...  :-DD

Kind regards,
Bram
“Two things are infinite, the universe and human stupidity, and I am not yet completely sure about the universe.”
 

Offline alm

  • Super Contributor
  • ***
  • Posts: 1257
  • Country: 00
Re: 3458a logging via Windows app.....revisited
« Reply #89 on: December 14, 2018, 09:01:42 pm »
I have searched myself crazy for my 34461A to put it on 100PLC mode via GPIB and I can't find it...
Try VOLT:DC:NPLC 100 in DCV mode. You'll need to set range and function via separate commands.
 

Offline blackdog

  • Frequent Contributor
  • **
  • Posts: 580
  • Country: nl
  • Please stop pushing bullshit...
Re: 3458a logging via Windows app.....revisited
« Reply #90 on: December 14, 2018, 09:36:22 pm »
Hi Alm  :)

Thanks, i will try it tomorrow, at the moment version 1.29 is running to see if it is stable.
I also upgraded my measuring computer, is is a Windows-7 machine, DELL Precision T1500 with a early I7 processor, 860 at 2.8GHz and 12 GB work memory.

The system load is verry low, below 5%, nice.



Kind regards,
Bram
« Last Edit: December 14, 2018, 09:38:12 pm by blackdog »
“Two things are infinite, the universe and human stupidity, and I am not yet completely sure about the universe.”
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #91 on: December 15, 2018, 10:24:23 am »
Hi all,

V1.30 available in post #1.

Playback Chart updates:
- Bug fix to the SHIFT UP / SHIFT DOWN buttons where the operation was a little slow and the calculated new max/min scale positions were beyond 7 dp's.
- Added "warning" pop-up when an old format CSV file is loaded and as a result the x-axis "mins" scale doesn't render (all zeros).

Ian.
« Last Edit: December 15, 2018, 10:52:36 am by IanJ »
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline alm

  • Super Contributor
  • ***
  • Posts: 1257
  • Country: 00
Re: 3458a logging via Windows app.....revisited
« Reply #92 on: December 15, 2018, 11:11:55 am »
Bram,

The full commands to set an SCPI-compatible meter to measure 10 V DC at 100 NPLC will be something like:
Code: [Select]
FUNCTION 'VOLT:DC'
VOLT:DC:RANGE 10
VOLT:DC:NPLC 100
 

Offline noname4me

  • Regular Contributor
  • *
  • Posts: 85
Re: 3458a logging via Windows app.....revisited
« Reply #93 on: December 15, 2018, 11:47:00 am »
Nice thread...quick question...why not use labview? 

Might it not be an easier solution?

Sent from my SM-N960F using Tapatalk

 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #94 on: December 15, 2018, 12:17:22 pm »
Nice thread...quick question...why not use labview? 

Might it not be an easier solution?

Sent from my SM-N960F using Tapatalk

I have never used Labview......plus doesn't it cost a minimum of £320 per year?
I would suspect also that Labview would not offer the complete and utter flexibility (and hardships!) of writing in VB (Visual Studio).

Ian.
« Last Edit: December 15, 2018, 01:24:47 pm by IanJ »
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #95 on: December 15, 2018, 04:52:33 pm »
Hi all,

V1.31 available in post #1.

Playback Chart updates:
- PPM Deviation - Added the optional ability to pull the Median Values from the 1st entry in the CSV instead of typing it it manually. In the case of Dual Device CSV's, it will pull from the relevant device line as selected.

TO-DO:
Need to add tooltips on all the various buttons etc.....the app is getting quite complicated without a manual!

Ian.
« Last Edit: December 15, 2018, 04:54:05 pm by IanJ »
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline blackdog

  • Frequent Contributor
  • **
  • Posts: 580
  • Country: nl
  • Please stop pushing bullshit...
Re: 3458a logging via Windows app.....revisited
« Reply #96 on: December 15, 2018, 05:13:20 pm »
Hi Ian,

I can do what i want, but it is not posible for me to get any useful information out of the playback chart.
It doesn't matter if I use one of your .csv or one I made myself...
This is a picture where you can see something at the bottom, I can't make anything else with it.
I have tried many settings but none of them provides a useful piece of software.
What am I doing wrong?



Kind regards,
Bram
“Two things are infinite, the universe and human stupidity, and I am not yet completely sure about the universe.”
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #97 on: December 15, 2018, 05:20:38 pm »
Hi Ian,

I can do what i want, but it is not posible for me to get any useful information out of the playback chart.
It doesn't matter if I use one of your .csv or one I made myself...
This is a picture where you can see something at the bottom, I can't make anything else with it.
I have tried many settings but none of them provides a useful piece of software.
What am I doing wrong?
Kind regards,
Bram

Manually edit your CSV and delete the first entry or so......you seem to have a rising voltage right at the start of the log......which is effectively giving your min and max a huge range.....thus the Playback chart resolution ends up quite low as a result (9.9 to 10.1 Vdc).
Don't worry about losing the first index numbers of the CSV, they aren't used for anything really.

To avoid this in the future, when you start logging the LAST thing you should do is hit ENABLE CSV and when the Data Log is showing good data.

Example of a CSV which need the first line deleted:
Code: [Select]
1,HP3458A,2018-12-05_21:31:49,0.00000000,24.9,30.8
2,HP3458A,2018-12-05_21:31:49,9.999999730,24.9,30.8
3,HP3458A,2018-12-05_21:32:49,9.999999735,24.9,30.6
4,HP3458A,2018-12-05_21:33:49,9.999998419,25.0,30.6
5,HP3458A,2018-12-05_21:34:49,9.99999779,25.0,30.6
6,HP3458A,2018-12-05_21:35:49,9.999996985,25.1,30.7
7,HP3458A,2018-12-05_21:36:49,9.999997014,25.1,30.8
8,HP3458A,2018-12-05_21:37:49,9.999996883,25.1,30.3
9,HP3458A,2018-12-05_21:38:49,9.999996546,25.0,30.3
10,HP3458A,2018-12-05_21:39:49,9.999995932,25.0,31.0

Ian.
« Last Edit: December 15, 2018, 05:28:30 pm by IanJ »
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline blackdog

  • Frequent Contributor
  • **
  • Posts: 580
  • Country: nl
  • Please stop pushing bullshit...
Re: 3458a logging via Windows app.....revisited
« Reply #98 on: December 15, 2018, 07:01:08 pm »
Hi Ian,

Friday night I had your software work on the 34461A and the 3458a.
And it was the second night that the software got stuck.

The software runs here on a 64 bit Windows -7 computer without unnecessary software.
Meanwhile I have also been able to solve all the remarks and errors from the windows logs.
Only the WMI 10 eror that is in almost every Windows-7 computer i cant kill, but this is not important.
The following screenshots contain some Dutch text, but the important information consists of English text.

I hope these pictures helps to find erors in your software.








Kind regards,
Bram

PS

Your remarks workt, see the picture below.
The wave is the temperature dependency of the instruments and a little of my 10V LAB reference. (draf and switching on and off of the heater in my lab)
The LAB reference will come in a second oven of about 40C and the inner oven is about 43C, but that is a job of the beginning of 2019.


“Two things are infinite, the universe and human stupidity, and I am not yet completely sure about the universe.”
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #99 on: December 15, 2018, 07:27:13 pm »
Hi Ian,

Friday night I had your software work on the 34461A and the 3458a.
And it was the second night that the software got stuck.

The software runs here on a 64 bit Windows -7 computer without unnecessary software.
Meanwhile I have also been able to solve all the remarks and errors from the windows logs.
Only the WMI 10 eror that is in almost every Windows-7 computer i cant kill, but this is not important.
The following screenshots contain some Dutch text, but the important information consists of English text.

I hope these pictures helps to find erors in your software.

Kind regards,
Bram

PS

Your remarks workt, see the picture below.
The wave is the temperature dependency of the instruments and a little of my 10V LAB reference. (draf and switching on and off of the heater in my lab)
The LAB reference will come in a second oven of about 40C and the inner oven is about 43C, but that is a job of the beginning of 2019.


I will look into the warning error....but if you can click on the DETAILS tab so I can see more.

Your PPM graph is offscreen (almost).....so change your PPM SCALE to say 6 or 7 instead of 5 and you should be fine.
Also, see the latest version to make it easier to set the MEDIAN VALUE for PPM Deviation.......if it's of interest to you.

I am adding Tooltips to all the buttons for the next version which will help usability.
Also, I am adding another button to the Playback Screen....."SAVE SCREENSHOT" which generates a PNG file of the Playback screen and the filename will be the log file name etc.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline blackdog

  • Frequent Contributor
  • **
  • Posts: 580
  • Country: nl
  • Please stop pushing bullshit...
Re: 3458a logging via Windows app.....revisited
« Reply #100 on: December 15, 2018, 09:21:59 pm »
Hi ian,  :)


I have two screenshots for you, maybe they help.




And number two.


Kind regards,
Bram
“Two things are infinite, the universe and human stupidity, and I am not yet completely sure about the universe.”
 

Offline blackdog

  • Frequent Contributor
  • **
  • Posts: 580
  • Country: nl
  • Please stop pushing bullshit...
Re: 3458a logging via Windows app.....revisited
« Reply #101 on: December 16, 2018, 10:20:56 am »
Morning Ian,  :)

This morning at 5:47 the program stopt working.



In the event data i found this string: System.OutOfMemoryException bij System.Array.Resize[[System.Byte, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](Byte[] ByRef, Int32.

This is a picture of the error log from ".net"



And this picture of the error "testIODevice.exe"



This is a screenshot of the directory your software is in, the file at the bottom "Zaterdag-01.csv" also stopped at 5:47 which is logical.



Here is nothing special visible, there is also plenty of memory left, more than 6GB free.



This is the beginning of the logfile.



And the end of the logfile.



This time around 15 o'clock the software has been logging and the file size is just over 1MB.
I have no idea if these two things have anything to do with the error, except the one:  System.OutOfMemoryException remark in the log files.

The computer works normally after your software has crashed.

I hope this helps.

Kind regards,
Bram
“Two things are infinite, the universe and human stupidity, and I am not yet completely sure about the universe.”
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #102 on: December 16, 2018, 11:42:04 am »
Morning Ian,  :)

This morning at 5:47 the program stopt working.

In the event data i found this string: System.OutOfMemoryException bij System.Array.Resize[[System.Byte, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](Byte[] ByRef, Int32.

This is a picture of the error log from ".net"

And this picture of the error "testIODevice.exe"



This is a screenshot of the directory your software is in, the file at the bottom "Zaterdag-01.csv" also stopped at 5:47 which is logical.



Here is nothing special visible, there is also plenty of memory left, more than 6GB free.



This is the beginning of the logfile.


And the end of the logfile.


This time around 15 o'clock the software has been logging and the file size is just over 1MB.
I have no idea if these two things have anything to do with the error, except the one:  System.OutOfMemoryException remark in the log files.

The computer works normally after your software has crashed.

I hope this helps.

Kind regards,
Bram

Can you try logging your 3458A only, and if it still crashes use the following additional command in the PRE-RUN

ARANGE 0

This will turn off auto-ranging on the 3458A. I notice that if my battery driven 10v voltage source goes dead then my app will start queueing some errors (doesn't crash though). ARANGE 0 stops the 3458A changing ranges as the voltage drops to zero. Make sure you manually set up the range on your 3458A before you start. Worth a try!

Also, if the 3458A is ok overnight then try the 34461A on it's own also.

Also, on the main app there is an ABORT ERRORS checkbox, you can try un-checking them both.....just to see.

Also, try running without enabling the Chart Devices.

Also, can you expand Task Manager in Windows AFTER it's crashed and tell me what you get in there.....here's mine after I have CREATE BOTH DEVICES, so I want to see if your IO Devices DLL is still running.


PS. So far I have no crashes even running for a few days.......I will test further though.

Ian.
« Last Edit: December 16, 2018, 12:23:33 pm by IanJ »
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #103 on: December 16, 2018, 05:49:56 pm »
Hi all,

V1.32 available in post #1.

- Tootips added to many of the Main app and Playback app buttons and entries. Just hover your mouse over. Note: Still have some to do.
- Have added a SCREENSHOT button to the Playback screen. This takes a screenshot of the Playback app only and saves a .PNG to the app folder. Date and Time in the filename i.e. "2018-12-16_10-50-44_Log.png"
  Note: There is a small bug in the screenshot as it doesn't capture everything for some reason (some details missing off-graph).

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline Messtechniker

  • Frequent Contributor
  • **
  • Posts: 333
  • Country: de
  • Old analog audio hand - No voodoo.
Re: 3458a logging via Windows app.....revisited
« Reply #104 on: December 17, 2018, 01:11:20 pm »
Just joined the club with my 34465A. :-+
Works so far on W7 32 Bit. Logging and .CSV are OK, but no curves. :--
Playback crashes even upon loading LOG_sample.csv. :-//
Will look into this tomorrow possibly on another PC. :scared:

Agilent 34465A, Hameg HMO1022, R&S HMC 8043, Voltcraft VC 940 and M-Audio Audiophile 192
 
The following users thanked this post: volvo_nut_v70

Offline blackdog

  • Frequent Contributor
  • **
  • Posts: 580
  • Country: nl
  • Please stop pushing bullshit...
Re: 3458a logging via Windows app.....revisited
« Reply #105 on: December 17, 2018, 01:42:54 pm »
Hi Ian,  :)

Your software now runs for about 25 hours with only the 3458a.
It is not yet crashing and the logfile is afther 25 hour around 850KB.
If it does go wrong, I will go to your proposed taskmanager settings, and yes I am lagging behind with the software version, that's because your software is still working.  :-DD


This morning a parcel was delivered, and what do you think it contained, TADA.... An Inan LM399 test print!
It is a nicely made print, now save for the parts, the 2ppm resistors are on the expensive side in small amounts.



Kind regards,
Bram
“Two things are infinite, the universe and human stupidity, and I am not yet completely sure about the universe.”
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #106 on: December 17, 2018, 02:28:25 pm »
Hi Ian,  :)

Your software now runs for about 25 hours with only the 3458a.
It is not yet crashing and the logfile is afther 25 hour around 850KB.
If it does go wrong, I will go to your proposed taskmanager settings, and yes I am lagging behind with the software version, that's because your software is still working.  :-DD

This morning a parcel was delivered, and what do you think it contained, TADA.... An Inan LM399 test print!
It is a nicely made print, now save for the parts, the 2ppm resistors are on the expensive side in small amounts.

Kind regards,
Bram

You can use whatever resistors you want, depends on your purpose for the board.
If it's just for soak test / ageing then you don't need 2ppm.
5ppm works well also, and is a lot cheaper.
Also, you don't need to populate the whole board, a channel at a time may suffice your needs.

I am running a long term test also, running the app in debug mode so any problems will hopefully be revealed.

Ian.
« Last Edit: December 17, 2018, 04:30:22 pm by IanJ »
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #107 on: December 17, 2018, 02:30:06 pm »
Just joined the club with my 34465A. :-+
Works so far on W7 32 Bit. Logging and .CSV are OK, but no curves. :--
Playback crashes even upon loading LOG_sample.csv. :-//
Will look into this tomorrow possibly on another PC. :scared:

New user so I have my ideas, I will reply again later today once I get back to the workshop. Tweaks may be required.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Online pwlps

  • Regular Contributor
  • *
  • Posts: 163
  • Country: fr
Re: 3458a logging via Windows app.....revisited
« Reply #108 on: December 17, 2018, 02:37:01 pm »
Hi Ian and blackdog,

As the error is triggered from my library it seems it's my job to answer this one.

This is weird:  the "AccessViolationException" should never be thrown by a managed code but here it looks like it came from an internal NET routine (the WaitHandle.WaitOne method).  Does it mean a bug in NET or it was just by accident that the error appearing elsewhere has been trapped just there?  I found other threads reporting such errors on stackoverflow and msdn forums but with no clear indications on the possible reasons.

Several options to explore:

1) I see that the NET version is 4.03..something, and I know that there were a lot of changes in the way threading is handled between the version 3.5 and 4 so maybe there is a problem in this early version.
I have been using the library under v3.5 in a heavy-duty environment (acquisition with many instruments  scanned in parallel, running 24h/24h for months, also under Win7 64bit), but did not make such tests under 4.0. Maybe it would be a good test to try the app under 3.5 : Ian, could you make a "downgraded" version of the exe compiled with v3.5 ? ("Target Framework" in compiler options). 

2) Ian, you could also add a checkbox to select between async and blocking querying mode. Of course in blocking mode the acquisition with more than one device will be slower (especially at higher NPLC) but this could provide a sort of fall-back option where any bugs are much easier to trace because everything is done on the main thread.

3) I will send Ian a slightly patched version of the main file, with the error being catched (only for NET 4.0 and higher)  - but I'm not sure it can help.

I have no idea about the "out of memory" error (this might possibly also be triggered by an "access violation" error somewhere else), the only way to get more information would be to run the program under the debugger.

keep me updated
Pawel
 
The following users thanked this post: blackdog

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #109 on: December 17, 2018, 07:02:42 pm »
Hi Ian and blackdog,

As the error is triggered from my library it seems it's my job to answer this one.

This is weird:  the "AccessViolationException" should never be thrown by a managed code but here it looks like it came from an internal NET routine (the WaitHandle.WaitOne method).  Does it mean a bug in NET or it was just by accident that the error appearing elsewhere has been trapped just there?  I found other threads reporting such errors on stackoverflow and msdn forums but with no clear indications on the possible reasons.

Several options to explore:

1) I see that the NET version is 4.03..something, and I know that there were a lot of changes in the way threading is handled between the version 3.5 and 4 so maybe there is a problem in this early version.
I have been using the library under v3.5 in a heavy-duty environment (acquisition with many instruments  scanned in parallel, running 24h/24h for months, also under Win7 64bit), but did not make such tests under 4.0. Maybe it would be a good test to try the app under 3.5 : Ian, could you make a "downgraded" version of the exe compiled with v3.5 ? ("Target Framework" in compiler options). 

2) Ian, you could also add a checkbox to select between async and blocking querying mode. Of course in blocking mode the acquisition with more than one device will be slower (especially at higher NPLC) but this could provide a sort of fall-back option where any bugs are much easier to trace because everything is done on the main thread.

3) I will send Ian a slightly patched version of the main file, with the error being catched (only for NET 4.0 and higher)  - but I'm not sure it can help.

I have no idea about the "out of memory" error (this might possibly also be triggered by an "access violation" error somewhere else), the only way to get more information would be to run the program under the debugger.

keep me updated
Pawel


Hi all,

I ran dual device logging (3458A & 34461A) for 24hrs and never had any problem, so it's indeed a curious issue that blackdog is experiencing.
It was running for 24hrs in the debug mode of Visual Studio and no issues were reported, or any resources dropping etc.

blackdog,
I have taken Pawel's new .DLL an included it in V1.33 (see Post # 1).
I have also added a checkbox per Pawel above that gives an alternative way to send the query to Device 1 & 2. See check box "Send Blocking" to enable this mode after you have Created Dev1/Dev2.
When you hit RUN you should see this mode in operation in the Device List pop-up as each device is queried.

Messtechniker,
If you are not seeing any charts/graphs, i.e. just a black box with NOTHING inside it, and no scales down the sides per the screenshots then I think your .NET Framework is probably old.....thats the only reason I can see for this.
You may need to update it via .NET Framework 4.0 installer from Microsoft:-
https://www.microsoft.com/en-gb/download/details.aspx?id=17851
However, this would affect other software on your PC so please make sure it's really what you are able to do.
PS. Win 7 comes with .NET 3.5.1 by default I believe.
Regarding the Playback screen crashing immediately you load the sample log, I think this is exactly the same problem.

I have left version V1.32 in Post #1 until we can see if V1.33 is working ok.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 
The following users thanked this post: blackdog

Online pwlps

  • Regular Contributor
  • *
  • Posts: 163
  • Country: fr
Re: 3458a logging via Windows app.....revisited
« Reply #110 on: December 17, 2018, 07:12:29 pm »
Hi Ian,

Here is another suggestion.

From last Bram's posts I see that the error occurs when he connects two devices, one via gpib and another via hislip, but it seems to disappear when there is only one device.  This points to a possible problem with simultaneous calls to Visa.  My library tries to optimize the speed following the official Visa specs saying that it is thread-safe, i.e. the default configuration allows concurrent Visa calls. However this behavior is entirely configurable as I explan in the article, section about lock levels.  The concurrency is governed by the field "interfacelockid" set by the class constructor and you can easily change it in the code. In the file VisaDevice.vb you will find (method "create" called by the constructor) the following piece of code which sets this field :

           If addr.ToUpper().Contains("GPIB") Then
                 Dim gpibboard As Integer
                 Dim gpibaddr As Byte
                 IODevice.ParseGpibAddr(addr, gpibboard, gpibaddr)
                  interfacelockid = gpibboard + 10
             Else
                 interfacelockid = -1 'no interface lock for non-gpib interfaces
              End If

The reasons to do it this way are explained in the article.

But you can replace this piece of code by e.g.

        interfacelockid = 25

With this setting all Visa devices will share the same lock whatever the physical interface  so that it won't be possible anymore to transfer data via hislip and gpib at the same time: the thread will always wait until the other transfer is complete, hence some loss in efficiency is expected.  However if you only transfer short strings this might not be a problem.
If you try it I will be interested to know if it helps.  Visa is said to be thread-safe but I haven't seen many apps using it extensively in multithreaded environments, on the other hand I saw several reports about Labview crashes when using concurrent Visa calls.

Pawel

 
The following users thanked this post: blackdog

Offline blackdog

  • Frequent Contributor
  • **
  • Posts: 580
  • Country: nl
  • Please stop pushing bullshit...
Re: 3458a logging via Windows app.....revisited
« Reply #111 on: December 17, 2018, 08:26:27 pm »
Hi!  :)

Program is running now for 32H and the logfile at the moment is 1.079MB.
We wil see tomorrow how it going.
I get a better filing about it now  :)

Thanks again for al your work Ian and Pawel, your work is really appreciated by me.

Kind regards,
Bram
“Two things are infinite, the universe and human stupidity, and I am not yet completely sure about the universe.”
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #112 on: December 17, 2018, 08:47:24 pm »
Hi Ian,

Here is another suggestion.

From last Bram's posts I see that the error occurs when he connects two devices, one via gpib and another via hislip, but it seems to disappear when there is only one device.  This points to a possible problem with simultaneous calls to Visa.  My library tries to optimize the speed following the official Visa specs saying that it is thread-safe, i.e. the default configuration allows concurrent Visa calls. However this behavior is entirely configurable as I explan in the article, section about lock levels.  The concurrency is governed by the field "interfacelockid" set by the class constructor and you can easily change it in the code. In the file VisaDevice.vb you will find (method "create" called by the constructor) the following piece of code which sets this field :

           If addr.ToUpper().Contains("GPIB") Then
                 Dim gpibboard As Integer
                 Dim gpibaddr As Byte
                 IODevice.ParseGpibAddr(addr, gpibboard, gpibaddr)
                  interfacelockid = gpibboard + 10
             Else
                 interfacelockid = -1 'no interface lock for non-gpib interfaces
              End If

The reasons to do it this way are explained in the article.

But you can replace this piece of code by e.g.

        interfacelockid = 25

With this setting all Visa devices will share the same lock whatever the physical interface  so that it won't be possible anymore to transfer data via hislip and gpib at the same time: the thread will always wait until the other transfer is complete, hence some loss in efficiency is expected.  However if you only transfer short strings this might not be a problem.
If you try it I will be interested to know if it helps.  Visa is said to be thread-safe but I haven't seen many apps using it extensively in multithreaded environments, on the other hand I saw several reports about Labview crashes when using concurrent Visa calls.

Pawel

Ok, I have uploaded a new V1.34 in Post #1 which includes a checkbox on the Device List pop-up (IO Devices).
"Dev1/Dev2 Interlock" which will give the above functionality that Pawel describes, but it's optional.

Default when unchecked is as normal, checked will disallow concurrent calls.

I am leaving the previous version available to download.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #113 on: December 17, 2018, 09:05:44 pm »
Hi!  :)

Program is running now for 32H and the logfile at the moment is 1.079MB.
We wil see tomorrow how it going.
I get a better filing about it now  :)

Thanks again for al your work Ian and Pawel, your work is really appreciated by me.

Kind regards,
Bram

Which version are you running?
Are you still logging two devices HP3458A and 34461A...?
Any other changes like a slower sample rate, different PRE RUN & ON RUN commands etc?

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline blackdog

  • Frequent Contributor
  • **
  • Posts: 580
  • Country: nl
  • Please stop pushing bullshit...
Re: 3458a logging via Windows app.....revisited
« Reply #114 on: December 17, 2018, 09:12:02 pm »
Hi Ian,

Iam still logging with version V1.29, i cant keep up with al your versions  :-DD

Do you want me to stop logging with this version?
It is only doing my 3458A.

Look still running


You can tell me what you want and i will start it before i go to bed.

Kind regards,
Bram

PS
Range set on 10V and 100PLC.
« Last Edit: December 17, 2018, 09:15:20 pm by blackdog »
“Two things are infinite, the universe and human stupidity, and I am not yet completely sure about the universe.”
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #115 on: December 17, 2018, 09:24:40 pm »
Hi Ian,

Iam still logging with version V1.29, i cant keep up with al your versions  :-DD

Do you want me to stop logging with this version?
It is only doing my 3458A.

Look still running

You can tell me what you want and i will start it before i go to bed.

Kind regards,
Bram

PS
Range set on 10V and 100PLC.

Download V1.34 and log both devices at the same sample rate etc that made it crash before.

When you hit CREATE BOTH DEVICES the pop-up will appear, and on it a new checkbox.........so please check it "Dev1/Dev2 Interlock" before you hit RUN.

On the main app, just leave both "Send Blocking" unchecked.

PS. This new version has changes to the .testIODevice.exe and also IODevice.dll

Ian.
« Last Edit: December 17, 2018, 09:27:42 pm by IanJ »
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline blackdog

  • Frequent Contributor
  • **
  • Posts: 580
  • Country: nl
  • Please stop pushing bullshit...
Re: 3458a logging via Windows app.....revisited
« Reply #116 on: December 17, 2018, 09:34:11 pm »
Hi Ian,

Is is running, we shall se, off to bed :-)



Kind regards,
Bram
“Two things are infinite, the universe and human stupidity, and I am not yet completely sure about the universe.”
 

Online pwlps

  • Regular Contributor
  • *
  • Posts: 163
  • Country: fr
Re: 3458a logging via Windows app.....revisited
« Reply #117 on: December 18, 2018, 02:35:20 pm »
Hi,
and here a very old version - still running in the background on my office PC  :)
Look at the sample count - you can't beat me  ;D

 

Offline Messtechniker

  • Frequent Contributor
  • **
  • Posts: 333
  • Country: de
  • Old analog audio hand - No voodoo.
Re: 3458a logging via Windows app.....revisited
« Reply #118 on: December 18, 2018, 03:40:25 pm »
When graphing throws errors it might help to change in Windows
the language from in my case DE to EN. Now properly displaying
5100 samples at a sample rate of 5. Nice :-+

Next I'd like to log temp and humi. Are the recommended sensors available in the EU?
Would save me customs trouble and cost. 
« Last Edit: December 18, 2018, 03:42:59 pm by Messtechniker »
Agilent 34465A, Hameg HMO1022, R&S HMC 8043, Voltcraft VC 940 and M-Audio Audiophile 192
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #119 on: December 18, 2018, 04:46:55 pm »
When graphing throws errors it might help to change in Windows
the language from in my case DE to EN. Now properly displaying
5100 samples at a sample rate of 5. Nice :-+

Next I'd like to log temp and humi. Are the recommended sensors available in the EU?
Would save me customs trouble and cost.

The USB-TnH SHT10 V2 sensor that I use is available via the manufacturers webpage, or sometimes he advertises on Ebay.
http://www.dogratian.com/products/index.php/menu-sensors/menu-usb-tnh-type-a-sht10

I have purchased several times from the guy without problem.

I could probably implement other serial USB sensors but would need one in my hand and with details of the protocol or example code.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Online Grandchuck

  • Regular Contributor
  • *
  • Posts: 69
  • Country: us
Re: 3458a logging via Windows app.....revisited
« Reply #120 on: December 18, 2018, 04:58:10 pm »
Just received the sensor Ian has mentioned and it started working immediately with no hassles.

Strangely, though, am now not able to playback my .csv log file.  The one included in the zip package is fine.  Has nothing to do with the sensor.  The error message is "conversion from string """" to type 'Double is not valid.

Looking at Ian's file and my own does not reveal any differences?  I know Playback used to work (some versions back).
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #121 on: December 18, 2018, 05:07:48 pm »
Just received the sensor Ian has mentioned and it started working immediately with no hassles.

Strangely, though, am now not able to playback my .csv log file.  The one included in the zip package is fine.  Has nothing to do with the sensor.  The error message is "conversion from string """" to type 'Double is not valid.

Looking at Ian's file and my own does not reveal any differences?  I know Playback used to work (some versions back).

Can you email me your log file?....or attach here. Playback is working ok with V1.34.

Ian.
« Last Edit: December 18, 2018, 05:45:32 pm by IanJ »
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #122 on: December 18, 2018, 05:43:46 pm »
Hi all,

V1.35 available in post #1.

- Got new code from Pawel (new .DLL file)
- I have added some error checking to the CSV file loading into the Playback Chart.
  Detects for an invalid/empty file and offers a pop-up as a result.
  Auto-detects the delimiter (comma or semi-colon) and sets it accordingly and loads the file. If none found then there's a problem and offers a pop-up as a result.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #123 on: December 18, 2018, 08:32:09 pm »
Hi all,

V1.36 available in post #1.

- Added checks to make sure the necessary data being written to the CSV is ready available to do so.
  I found that if the CSV is enabled before the logging has started, before the temp/humidity sensor is delivering data etc then the CSV can contain bad data which crashes the Playback Chart.
  Now the controls & checkboxes can be made in any order and the CSV file is always correctly written to.
- I have also added more checks to CSV when loading it into the Playback Chart. Pop-ups will advise of any bad data/lines in the CSV on loading.

Thanks to Chuck for sending me his test CSV file which prompted these fixes.

Ian.
« Last Edit: December 18, 2018, 08:36:43 pm by IanJ »
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #124 on: December 18, 2018, 09:31:12 pm »
Hi all,

V1.37 available in post #1.

- With all the CSV checks I added......the blank Log.csv I enclose in the ZIP isn't compatible with teh Playback Chart.......it has an extra blank line!....aarrgghh!
   So enclosed with V1.37 is a new blank Log.csv that will work.

I knew that when I started to add checks and balances all over the place that things would break as a result......:-)

Thanks again Chuck!

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #125 on: December 18, 2018, 10:11:49 pm »
Hi all,

V1.38 available in post #1.

- Interlocks added so that Temp/Hum cannot be enabled until the Temp?Hum sensor is started.
- Interlock added so that you cannot RESET teh CSV file without first checking the box next to it (saves inadvertent resets!)

Any issues with the CSV loading into the Plabck Chart please let me know......there's lots of interlocks in teh code now so I'd be interested to hear any issues.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline Messtechniker

  • Frequent Contributor
  • **
  • Posts: 333
  • Country: de
  • Old analog audio hand - No voodoo.
Re: 3458a logging via Windows app.....revisited
« Reply #126 on: December 19, 2018, 06:18:05 am »
V 1.38:
Logging and curves are OK with Windows EN enabled.
However, playing back the recorded log.csv results in:

Conversion from sting "" to type 'Double' is not valid
 :-//

Both sample .csv files play back correctly

Here an excerpt from the log file in question:

1,34465A,2018-12-19_07:02:15,10.0052315
2,34465A,2018-12-19_07:02:20,10.0051795
3,34465A,2018-12-19_07:02:25,10.0051923
4,34465A,2018-12-19_07:02:30,10.0052188
5,34465A,2018-12-19_07:02:35,10.0050439
6,34465A,2018-12-19_07:02:40,10.004845
7,34465A,2018-12-19_07:02:45,10.0049304
8,34465A,2018-12-19_07:02:50,10.0049489
9,34465A,2018-12-19_07:02:55,10.0049471

All lines are like that. No blank line.
Agilent 34465A, Hameg HMO1022, R&S HMC 8043, Voltcraft VC 940 and M-Audio Audiophile 192
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #127 on: December 19, 2018, 07:23:53 am »
V 1.38:
Logging and curves are OK with Windows EN enabled.
However, playing back the recorded log.csv results in:

Conversion from sting "" to type 'Double' is not valid
 :-//

Both sample .csv files play back correctly

Here an excerpt from the log file in question:

1,34465A,2018-12-19_07:02:15,10.0052315
2,34465A,2018-12-19_07:02:20,10.0051795
3,34465A,2018-12-19_07:02:25,10.0051923
4,34465A,2018-12-19_07:02:30,10.0052188
5,34465A,2018-12-19_07:02:35,10.0050439
6,34465A,2018-12-19_07:02:40,10.004845
7,34465A,2018-12-19_07:02:45,10.0049304
8,34465A,2018-12-19_07:02:50,10.0049489
9,34465A,2018-12-19_07:02:55,10.0049471

All lines are like that. No blank line.

Hi,

The CSV looks fine (no temp/hum sensor connected or active).
When you get the error can you copy n paste the detail from the error box and send to me.
Near the top of the error report it will mention (more than once possibly) which lines in the .vb code the error occurred…...that's the detail I need.

Ian.
« Last Edit: December 19, 2018, 07:26:04 am by IanJ »
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #128 on: December 19, 2018, 05:16:32 pm »
Hi all,

V1.39 available in post #1.

In order to fix the Playback CSV load error that some of you are getting I have made a modification to the data that is written to the CSV.
So now instead of writing nothing to the CSV if there is no Temp/Hum sensor connected I am writing 0.0 for both......I am hoping this is the source of the error.
It looks like that some non-English Windows configurations have a problem loading the CSV which results in a String conversion to Double error.

Please note that this fix will only work for new CSV files created with this version 1.39. If you try to load older CSV files they will likely still error.

Feedback appreciated.

Ian.
« Last Edit: December 19, 2018, 05:31:13 pm by IanJ »
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline Messtechniker

  • Frequent Contributor
  • **
  • Posts: 333
  • Country: de
  • Old analog audio hand - No voodoo.
Re: 3458a logging via Windows app.....revisited
« Reply #129 on: December 19, 2018, 06:17:33 pm »
Did a quick check on V 1.39. Seems to work well!
Playback loads demo files and files created with V 1.39. :-+
Long logging in progress now.
More testing tomorrow to see if it works with
language set to German. Is EN at the moment .
Agilent 34465A, Hameg HMO1022, R&S HMC 8043, Voltcraft VC 940 and M-Audio Audiophile 192
 

Offline blackdog

  • Frequent Contributor
  • **
  • Posts: 580
  • Country: nl
  • Please stop pushing bullshit...
Re: 3458a logging via Windows app.....revisited
« Reply #130 on: December 19, 2018, 08:35:27 pm »
Hi,

I had onother crash of the program, afther 19 hour and almost 1.3MB of collected data.

I wil place nouw a lot of pictures of screenshot i made, maybe it helps...

Crashd but stil in memory.



Screen space wil nog be updated before i close the program



Taskmanager pictures in three parts, part-1



Taskmanager pictures in three parts, part-2



Taskmanager pictures in three parts, part-4


The computer has no high processor load if the program is crashd en the computer is still running fine.

Latest version problems
Crash...
I started version 1.39 of the program en created both devices, the 3458A and the 34461A.
And put this in for configuration afther power cycling of the 34461A:
*RST
FUNCTION 'VOLT:DC'
VOLT:DC:RANGE 10
VOLT:DC:NPLC 100



An a second try and no 34461A reboot, and it works... :-//

Kind regards,
Bram












“Two things are infinite, the universe and human stupidity, and I am not yet completely sure about the universe.”
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #131 on: December 19, 2018, 09:22:32 pm »
Hi,
I had onother crash of the program, afther 19 hour and almost 1.3MB of collected data.
I wil place nouw a lot of pictures of screenshot i made, maybe it helps...
Crashd but stil in memory.
Screen space wil nog be updated before i close the program
Taskmanager pictures in three parts, part-1
Taskmanager pictures in three parts, part-2
Taskmanager pictures in three parts, part-4
The computer has no high processor load if the program is crashd en the computer is still running fine.
Latest version problems
Crash...
I started version 1.39 of the program en created both devices, the 3458A and the 34461A.
And put this in for configuration afther power cycling of the 34461A:
*RST
FUNCTION 'VOLT:DC'
VOLT:DC:RANGE 10
VOLT:DC:NPLC 100
An a second try and no 34461A reboot, and it works... :-//
Kind regards,
Bram

The pop-up displays an error code = BFFF00A6, and looking this up the description is:-
"The connection for the given session has been lost - VI_ERROR_CONN_LOST"
http://literature.cdn.keysight.com/litweb/pdf/E2090-90040.pdf

The next time in crashes can you open the Keysight Connection Expert and see if the 34461A is still connected there.......in fact leave the connection expert running on-screen.
You could also try sending commands to it via the Connection Expert to see if it reacts when it crashes.

You can also use th Keysight IO Monitor and capture all messages.

I have set up V1.39 with my own 3458A & 34461A exactly like yours so will let it run. I should manage 20hrs straight.

If it's a Keysight issue then maybe we need to play with the PRE RUN ans AT RUN commands to help it.

Other ideas:
1. 34461A firmware version?....I am running A.02.14-02.40-02.14-00.49-01-01
2. Is your 34461A on the same sub-net as your PC......could your Lan be dropping packets, or something interfering with the TCP/IP connection?
3. Windows OS?
4. I am using Keysight Connection Expert 2018
5. Is your 34461A displaying an "error" at top right corner of the LCD when it happens, or any other message?

I have never had a 34461A crash problem......so something is different between your and my setup. The only thing I notice is that sometimes READ? can take a few seconds to get a reply, but it usually settles down.

Ian.
« Last Edit: December 19, 2018, 10:01:51 pm by IanJ »
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Online pwlps

  • Regular Contributor
  • *
  • Posts: 163
  • Country: fr
Re: 3458a logging via Windows app.....revisited
« Reply #132 on: December 20, 2018, 12:11:07 pm »
Hi Ian and Bram,

ah yes, "werkt niet meer", it is obvious: it doesn't work  :-DD

VI_ERROR_CONN_LOST  means a lost TCP connection but it shouldn't blow off the whole thing.
Now that the error message window is enabled it looks like the code handled the problem at least once without crashing, does it mean the crash went from inside a Visa function when the command was sent next time?  Even with all those taskmanager windows we can't know it without a debugger trace.

Another question (for Ian): how was the dev1/dev2 Visa interlock option configured in this version? If it was disabled it might be interesting to repeat  the test with interlock on.   

Pawel 
 

Offline blackdog

  • Frequent Contributor
  • **
  • Posts: 580
  • Country: nl
  • Please stop pushing bullshit...
Re: 3458a logging via Windows app.....revisited
« Reply #133 on: December 20, 2018, 12:36:08 pm »
Pawel,

This is not funny! => ah yes, "werkt niet meer", it is obvious: it doesn't work  :-DD

Got you  :-DD

Maybe comming weekend i have some time left to play again with the software.

Ian
A have the latest firmware in my two 34461A DMM's from the beginning of this month.
The OS of my measuring computer is W7 Prof, up to date.
The IO package is the latest of KeySight.
The IP address of the meters are in the same range as the measuring computer and my main workstation conected to my workbench switch and short good quality patch cables.
I use fixt IP adresses for my measuring gear.
Last crash no error messages on the display of the 34461A that was in use.

Kind regards,
Bram
“Two things are infinite, the universe and human stupidity, and I am not yet completely sure about the universe.”
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #134 on: December 20, 2018, 01:33:28 pm »
Hi Ian and Bram,

ah yes, "werkt niet meer", it is obvious: it doesn't work  :-DD

VI_ERROR_CONN_LOST  means a lost TCP connection but it shouldn't blow off the whole thing.
Now that the error message window is enabled it looks like the code handled the problem at least once without crashing, does it mean the crash went from inside a Visa function when the command was sent next time?  Even with all those taskmanager windows we can't know it without a debugger trace.

Another question (for Ian): how was the dev1/dev2 Visa interlock option configured in this version? If it was disabled it might be interesting to repeat  the test with interlock on.   

Pawel

Pawel,

Interlock in this version is per your last email passing me the .vb file. I inserted it 'as-is' and took the checkbox off the form.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Online pwlps

  • Regular Contributor
  • *
  • Posts: 163
  • Country: fr
Re: 3458a logging via Windows app.....revisited
« Reply #135 on: December 20, 2018, 01:50:58 pm »
Ian,

Quote
Interlock in this version is per your last email passing me the .vb file. I inserted it 'as-is' and took the checkbox off the form.

Then it is not activated by default.  To activate it (in a simple way - hardwired in the code) replace, in the main form (in CreateDevice) :
dev = New VisaDevice(name, address)
by
dev = New VisaDevice(name, address, true)

(see explanations in my email on Dec 12th)

As I said somewhere in my mails  the performance loss due to interlock will not be perceptible as long as you only transfer short strings (this would be different with e.g. long scope traces).  Therefore in this app you can probably leave it like this for the moment. (Later you can add a checkbox (in the main form) which would select the desired behavior if you want to be perfectionist).

Pawel
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #136 on: December 20, 2018, 03:20:33 pm »
Ian,

Quote
Interlock in this version is per your last email passing me the .vb file. I inserted it 'as-is' and took the checkbox off the form.

Then it is not activated by default.  To activate it (in a simple way - hardwired in the code) replace, in the main form (in CreateDevice) :
dev = New VisaDevice(name, address)
by
dev = New VisaDevice(name, address, true)

(see explanations in my email on Dec 12th)

As I said somewhere in my mails  the performance loss due to interlock will not be perceptible as long as you only transfer short strings (this would be different with e.g. long scope traces).  Therefore in this app you can probably leave it like this for the moment. (Later you can add a checkbox (in the main form) which would select the desired behavior if you want to be perfectionist).

Pawel

Ok, I agree......the voltnuts can easily live with it so I will amend tonight.

Ian
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #137 on: December 20, 2018, 04:56:19 pm »
Hi all,

V1.40 available in post #1.

This version activates an interlock in order to try and stop an issue where some user(s) have experienced the app crashing when a connected device appears to go offline, i.e a VI_ERROR_CONN_LOST error reported. This also only seems to happen when dual devices are connected and running.

Feedback appreciated.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline blackdog

  • Frequent Contributor
  • **
  • Posts: 580
  • Country: nl
  • Please stop pushing bullshit...
Re: 3458a logging via Windows app.....revisited
« Reply #138 on: December 21, 2018, 09:05:00 am »
Good morning Ian,  :)

Since last night your version 1.40 runs here with the 3458A and the 34461A, which is currently about 10 hours log time.
I used again the same setting.

Yesterday I also played with the new web interface of the 34461A.
I think there are some big bug's in it, I will test it later today with my second 34461A DMM.

All you have to do is go to the IP address of the 34461A and then choose the Interactive IO,
Then the measuring instrument gives even if you only type 1 character, directly an error!
So giving an enter is not necessary, just enter a character and ERROR...

If you choose a command from the "Execute" drop down menu, the instrument performs this command without error.

I used three different browsers from my main workstation to see if the browser influenced this.
These were the latest versions of Firefox, Opera and Internet explorer (No Edge and also no Google, which are not appreciated here)
I also tested a virtual, latest version of MINT Linux with Firefox, same result.

Later today I will test this with two computers on the 34461A I currently have available for this purpose.
Why am I telling this here, because I thought it would be useful to test the commados I would like to use via GPIB.
Before i put them in Ians software.
I will keep my comment short about this so as not to pollute this topic.

Kind Regards,
Bram
“Two things are infinite, the universe and human stupidity, and I am not yet completely sure about the universe.”
 
The following users thanked this post: IanJ

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #139 on: December 21, 2018, 03:41:30 pm »
Hi all,

V1.41 available in post #1.

Relatively minor updates:-
- Data Log & Event Log window data formatted so that it is more aligned/readable (small text, but it's readable).
- Further checks that the temp/hum sensor data is valid before writing to Data Log and CSV. This is necessary since if the sensor/data is lost it was creating CSV entries that the Playback chart couldn't handle.

Ian.
« Last Edit: December 21, 2018, 03:53:04 pm by IanJ »
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #140 on: December 22, 2018, 03:06:38 pm »
Hi all,

V1.42 available in post #1.

- Added a TEMPERATURE MAX DIFF RECORDED display and RESET button below the chart on the main display.
  This complements the Device 1&2 Max Diff Recorded displays already there.
  I also increased the responsivness of the RESET button there.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #141 on: December 22, 2018, 07:38:05 pm »
Hi all,

V1.43 available in post #1.

- Bug fix - Device 2 AT STOP commands were not being sent.
- I have changed the way the AT STOP commands are sent, i.e. changed to blind commands that don't expect a reply.
- Bug Fix - If you hit STOP on any device and then hit RUN again then the software would not return to a working RUN mode again.
  The idea is that you can hit STOP, then adjust some PRE-RUN or AT RUN parameters then continue on again as it will re-send the PRE-RUN commands.

Ian.
« Last Edit: December 22, 2018, 07:39:55 pm by IanJ »
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #142 on: December 29, 2018, 08:05:03 pm »
Hi all,

V1.44 available in post #1.

- Log scale functionality added to the PlayBack Chart

Please note that the Log scale functionality won't work with negative data......I have taken some precautions, but if there is negative data anywhere in the CSV then it may cause the app to crash.
A checkbox on the PlayBack Chart enables Log scale.

I have left 1.43 available for download as there's quite a bit of mods done to make 1.44......a bit of a tidy up, and adding the Log scale functionality.

Ian.
« Last Edit: December 29, 2018, 08:22:03 pm by IanJ »
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Online Grandchuck

  • Regular Contributor
  • *
  • Posts: 69
  • Country: us
Re: 3458a logging via Windows app.....revisited
« Reply #143 on: December 30, 2018, 09:22:57 pm »
Returned from a holiday trip and found nice upgrades to the logging app!  Thanks much Ian and a happy new year to you and yours.

PPM scale is not showing on the saved screen so I also attached a screen capture.

Happy new year to all here.
 
The following users thanked this post: IanJ

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #144 on: December 31, 2018, 12:15:29 am »
Returned from a holiday trip and found nice upgrades to the logging app!  Thanks much Ian and a happy new year to you and yours.

PPM scale is not showing on the saved screen so I also attached a screen capture.

Happy new year to all here.

Yep, it's a quirk/bug in the way vb saves a bitmap......and not much I can do about it except replace 1 line of code with a whole routine......which I will get around to eventually. You'll notice it's not just the PPM scale, other random stuff is missing.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline deepskyridge

  • Regular Contributor
  • *
  • Posts: 81
  • Country: us
Re: 3458a logging via Windows app.....revisited
« Reply #145 on: January 21, 2019, 03:05:28 pm »
Ian, I have your windows app running with my HP 3457A and seems to be working well. Will run it for a couple of days next to check reliability.

Is there a way to make the instrument id and gipb address retain between restarts.

Never Mind, I figured it out.

Thanks for the nifty software.

Gary
« Last Edit: January 21, 2019, 05:26:24 pm by deepskyridge »
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #146 on: January 22, 2019, 11:36:45 am »
Ian, I have your windows app running with my HP 3457A and seems to be working well. Will run it for a couple of days next to check reliability.

Is there a way to make the instrument id and gipb address retain between restarts.

Never Mind, I figured it out.

Thanks for the nifty software.

Gary


I hope the software is of good use to you...…...and thanks for the donation, very much appreciated.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline deepskyridge

  • Regular Contributor
  • *
  • Posts: 81
  • Country: us
Re: 3458a logging via Windows app.....revisited
« Reply #147 on: January 22, 2019, 05:37:51 pm »
Two Things that would be nice to add.

1. Ability to convert temp from Celsius to Fahrenheit.

2. Add support for the scanning card on the 3457A, I have the 44491A card in mine.

Thanks
Gary
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #148 on: January 23, 2019, 03:18:18 pm »
Two Things that would be nice to add.

1. Ability to convert temp from Celsius to Fahrenheit.

2. Add support for the scanning card on the 3457A, I have the 44491A card in mine.

Thanks
Gary

The reason I chose DegC, apart from that what we use mostly here, is that since it shares the same scale as Humidity the numbers are closer together when set to DegC. Thats said, probably a good idea to have a selection option.

I don't have a 44491A card in my 3457A.....but if I pick one up I will look at integrating it.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline Svgeesus

  • Contributor
  • Posts: 37
  • Country: us
Re: 3458a logging via Windows app.....revisited
« Reply #149 on: January 25, 2019, 04:55:30 pm »
On a Keysight 34465A, I'm looking for some way to automate testing and logging. I would preferably like to be able to control a PDVS2 at the same time. Details below of what exactly led me to the need to automate, for those interested, but basically I want to generate control voltages and log voltage, frequency, temperature and time for later analysis (mean, median, regression) and charting.

Compared to my old handheld meter (UT-71C) besides the greatly improved accuracy and precision I certainly appreciate being able to get a min, max, mean, standard deviation plus a visual time series/trend chart and histogram. But the limitations of that approach are becoming irksome - the output is raster screenshots saved, somewhat laboriously, to a USB stick. I want to be able to capture the individual readings, log them with timestamp, and then be able to calculate mean, sd, also median and so on. I want more flexibility in graphing and analysis (like charts with error bars).

This moved up in urgency when I was measuring some analog audio oscillators (Eurorack modular oscillators, for electronic music synthesis). These are controlled by an analog input voltage, where an increase in one volt results in a doubling of output frequency (one octave pitch change). I was using a PDVS2 to create the control voltages, covering 20V in 100mV steps (10V positive and 10V negative). This voltage went to the oscillator, and the voltage at the oscillator control voltage input went to the front panel of the 34465A (100PLC, HiZ). The triangle wave produced by the oscillator went to the rear panel of the 34465A, where the frequency was measured. So each measurement required a series of manual steps:

  • Set the new voltage on the PDVS2, with the rotary encoder
  • Change to front panel inputs, reset the readings, monitor the voltage for 10 seconds to get a mean and sd (the PDVS2 is very stable, so this was quick)
  • Write the voltage values in a CSV file
  • Note the temperature inside the synthesizer case
  • Write the temperature value in a CSV file
  • Switch to rear panel inputs, reset the frequency reading, monitor the frequency for 1000 readings to get the mean and sd
  • Write the frequency values in a CSV file

This had the disadvantage that the voltage measurements were all taken together and then the frequency measurements all together, rather than taking interleaved measurements over the recording of each data point. The PDVS2 is very stable, the temperature was fairly stable but climbing gradually. Because the 20V range was done in two stages (with the leads being reversed to get the negative voltages)  I think this explains the fact that the two halves of the voltage vs. log frequency plot did not fully line up. It also had the disadvantage of switching manually between front and rear via the pushbutton, a lot of times. This would be better done with software control.

My next VB app will be to automate calibration of my PDVS2's without human intervention......i.e.: VB reads output voltage of PDVS2 via GPIB, VB sends instruction to PDVS2 to adjust up/down, VB instructs PDVS2 to save cal (zero & span DAC adjustment)............this will save me hours and hours of calibrating batches pf PDVS2's!!!

Because Ian wrote a Windows program to control the PDVS2, I'm first looking at his program to control my meter (and hopefully, to also log temperatures and to control the PDVS2 at the same time). Only if that doesn't work out will I bite the bullet and do the whole Raspberry Pi Linux logging station thing, which looks a lot more complicated to set up.

Questions:

  • Does this require purchasing the GPIB option for my meter, or can I use the USB or ethernet connections?
  • Would this be compatible with my meter or is it 3458a only (I saw mention of other meters but not my specific one)
  • Could one program run both devices or would I need to run two programs with a timed series and hpe they don't drift apart?
  • Also, what are my options for expanding beyond two channels (front and rear) on the meter/ I see other Keysight meters that take multi-channel scanner cards, but these don't seem to turn op on searches on this forum. And there doesn't seem to be an add-on scanner card for this meter. I can see this being my next requirement. Or do people just buy multiple similar meters?
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #150 on: January 25, 2019, 05:58:38 pm »
Hi,

Assuming you are looking for answers in regard to my logging app, as follows:-

Quote
Does this require purchasing the GPIB option for my meter, or can I use the USB or ethernet connections?

When you install it hit the NOTEPAD button and it will bring up a text file containing some sample GPIB configs....including a 34461A by way of it's ethernet Lan connection. All you need is to install the free Keysight IO Libraries and config your meter there. The IO suite acts as a bridge to allow direct control from my logging app.

Quote
Would this be compatible with my meter or is it 3458a only (I saw mention of other meters but not my specific one)

It's GPIB compatible, so unless there's some 'quirk' with any particular device it should work with any GPIB device (to take readings).....you just need to configure the right GPIB command for your device.......i.e. the commands for a 3458A are different to a Keithley 2015THD are different to a Fluke 8842A.

Quote
Could one program run both devices or would I need to run two programs with a timed series and hpe they don't drift apart?

You can run two devices from the one program......it's just that the CSV file is shared. In saying that you can open as many instances of the program as you like......I've never tried it, but I am guessing you can therefore run as many devices as you like. Just make sure you configure separate CSV files.

I have thought about designing a generic scanner/relay board that would be GPIB controlled and thus could theoretically open up say 8 separate channels into a 3458A. I'd modify the logging app to control it......but like I said, it's just a thought at the moment.

PS. If it helps, the PDVS2 serial protocol is available (if you contact me via email) thus allowing anyone to write their own app to control it remotely.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 
The following users thanked this post: Svgeesus

Offline zed65

  • Contributor
  • Posts: 25
  • Country: se
Re: 3458a logging via Windows app.....revisited
« Reply #151 on: January 25, 2019, 07:29:59 pm »
Hi Ian, really nice app you have made!
I have a small question/bug report, say that you are trying to connect to a COM-port device but forgot to switch from VISA to COM and hit create device.
As I can see there are no way back after that (you got to close and restart the app).
Or is it only me doing something wrong :-\
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #152 on: January 25, 2019, 09:17:34 pm »
Hi Ian, really nice app you have made!
I have a small question/bug report, say that you are trying to connect to a COM-port device but forgot to switch from VISA to COM and hit create device.
As I can see there are no way back after that (you got to close and restart the app).
Or is it only me doing something wrong :-\

It is a small GUI issue.......but the way around it is to hit RUN then immediately hit STOP then hit RESET and you are back at the start again.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 
The following users thanked this post: zed65

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #153 on: February 16, 2019, 11:14:28 am »
Hi all,

VB source code attached to post #1.

Visual Studio Express 2015 exported template V1.44.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline deepskyridge

  • Regular Contributor
  • *
  • Posts: 81
  • Country: us
Re: 3458a logging via Windows app.....revisited
« Reply #154 on: February 16, 2019, 09:41:05 pm »
Ian, thanks for posting the source code, I have it loaded in VS 2015. Is there anything I need to install. It is generating errors.

It's complaining about IODevices.

Thanks
Gary
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #155 on: February 18, 2019, 11:46:08 am »
Ian, thanks for posting the source code, I have it loaded in VS 2015. Is there anything I need to install. It is generating errors.

It's complaining about IODevices.

Thanks
Gary


The entire app is basically two VS projects, the IODevices one I never touched and it compiles to a DLL (which is included in the exe download).
The source is available at the codeproject link (see post #1).
I'm away from the workshop right now, but I'll check tonight what I had to do to get my app to compile.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #156 on: February 18, 2019, 05:19:51 pm »
Hi all,

To compile my VS app first add a reference to the IODevice.dll, i.e.:-





Your path will vary.

Ian.

Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 
The following users thanked this post: wolfy007

Offline zed65

  • Contributor
  • Posts: 25
  • Country: se
Re: 3458a logging via Windows app.....revisited
« Reply #157 on: February 19, 2019, 06:59:48 pm »
I can't compile it. It throws some errors about "$safeprojectname$" on different locations in the solution.
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #158 on: February 20, 2019, 07:19:25 am »
Hi all,

Has anyone managed to compile my program now?...….just wondering if my exported template still has an issue at my end.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline zed65

  • Contributor
  • Posts: 25
  • Country: se
Re: 3458a logging via Windows app.....revisited
« Reply #159 on: February 20, 2019, 04:52:51 pm »
I finally got it to compile in both VS2015 and VS2017 :-+

 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #160 on: February 20, 2019, 05:20:38 pm »
I finally got it to compile in both VS2015 and VS2017 :-+

3 devices!!......I wondered how long it would take before that was done.......:-)

I am planning some mods of my own eventually.......I'd like to add multiplexer board control, i.e. several DUT's (possibly 8-way) and one 3458A.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 
The following users thanked this post: zed65, Svgeesus

Online pwlps

  • Regular Contributor
  • *
  • Posts: 163
  • Country: fr
Re: 3458a logging via Windows app.....revisited
« Reply #161 on: February 21, 2019, 02:47:48 pm »

The entire app is basically two VS projects, the IODevices one I never touched and it compiles to a DLL (which is included in the exe download).
The source is available at the codeproject link (see post #1).
I'm away from the workshop right now, but I'll check tonight what I had to do to get my app to compile.

Ian.

Just to precise that the IODevices dll included in the exe (and required to compile your source) is a bit different from the CodeProject version because it uses a slightly downgraded VisaDevice class with a global Visa interlock (i.e. considering Visa as non-thread-safe even it it claims the opposite). I suggested to try it after some problems reported by blackdog, we didn't hear from him since so maybe it did help finally, I don't know.
 

Offline zed65

  • Contributor
  • Posts: 25
  • Country: se
Re: 3458a logging via Windows app.....revisited
« Reply #162 on: February 21, 2019, 10:04:00 pm »
Ian, did you get the HiRes mode of your 3457A to work? I've fiddled some with that experimental code for it but no luck.
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #163 on: February 22, 2019, 05:42:21 am »
Ian, did you get the HiRes mode of your 3457A to work? I've fiddled some with that experimental code for it but no luck.

No, that code is about as far as I got. I wasnt sure in the end I had the idea of how the 3457A works for achieving that mode correct so just left it.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline deepskyridge

  • Regular Contributor
  • *
  • Posts: 81
  • Country: us
Re: 3458a logging via Windows app.....revisited
« Reply #164 on: February 23, 2019, 10:10:09 pm »
I can't compile it. It throws some errors about "$safeprojectname$" on different locations in the solution.
[/quhttps://www.eevblog.com/forum/metrology/3458a-logging-via-windows-app-revisited/150/?action=post;num_replies=163ote]

How did you solve this ?

Thanks
 

Offline zed65

  • Contributor
  • Posts: 25
  • Country: se
Re: 3458a logging via Windows app.....revisited
« Reply #165 on: February 24, 2019, 10:26:49 pm »
Ok here are the steps I did to make it compile.

1. Unzip the folder.
2. Open the "testIODevice.vbproj" in VS2015.
3. Now VS2015 have created some folders, move/copy the "IODevice.dll" and "Microsoft.VisualBasic.PowerPacks.dll" to the /bin/debug folder.
4. Delete "IODevices" and "app.config" from the solutions tree.
5. Open the My Project settings and type in "test" or something as Assembly name and Root namespace.
6. Change "Startup form" from "Formtest" to "Dialog2".
7. Build the project once then change back the "Startup form" to "Formtest".
8. Now it should compile/build.
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #166 on: February 25, 2019, 10:43:51 am »
Hi all,

I have tidied up the source zip in post #1 so should not need to delete IODevices/app.config from the solutions tree.
No idea if the other actions still need to be performed as I only have one install of VS (except copy over the DLL's).

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline deepskyridge

  • Regular Contributor
  • *
  • Posts: 81
  • Country: us
Re: 3458a logging via Windows app.....revisited
« Reply #167 on: February 27, 2019, 04:26:40 pm »
Thanks for the info, I have it building and have made the changes for Fahrenheit temp. Works great.

Next I would like to include the ability to use the scanner card in my 3457A.

Thanks
Gary
 
The following users thanked this post: zed65

Offline branadic

  • Super Contributor
  • ***
  • Posts: 1484
  • Country: de
Re: 3458a logging via Windows app.....revisited
« Reply #168 on: March 18, 2019, 07:49:36 pm »
Hi Ian,

I have downloaded the latest version of Keysight IO Libraries Suite, with its Interactive IO able to send and receive commands to and from my meter. It shows up as GPIB0::22::INSTR.
But when using your program, I'm not able to connect to my meter. The software aborts with the message:

Quote
cannot create device R6581D
could not open Visa device at address GPIB0::22::INSTR
error code BFFF00A5

I'm using an Agilent 82357A and choosed VISA for the interface. Am I'm missing something?

-branadic-
Fluke 8050A | Prema 5000 | Prema 5017 SC | Advantest R6581D | GenRad 1434-G | Datron 4000A | Tek 2465A | VNWA2.x with TCXO upgrade and access to: Keysight 3458A, Keithley 2002, Prema 5017 SC, 34401A, 34410A, Keithley 2182A, HDO6054, Keysight 53230A and other goodies at work
 

Online pwlps

  • Regular Contributor
  • *
  • Posts: 163
  • Country: fr
Re: 3458a logging via Windows app.....revisited
« Reply #169 on: March 19, 2019, 08:34:51 am »
BFFF00A5 or "VI_ERROR_INTF_NUM_NCONFIG" means VISA doesn't have a resource "GPIB0".  So it is strange if you can see it via their interactive utility. Apparently the error can happen if you have both Agilent and NI interfaces installed:
https://forums.ni.com/t5/Instrument-Control-GPIB-Serial/VISA-error-bfff00a5/td-p/529294
otherwise I don't know.
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #170 on: March 19, 2019, 11:49:30 am »
Hi Ian,

I have downloaded the latest version of Keysight IO Libraries Suite, with its Interactive IO able to send and receive commands to and from my meter. It shows up as GPIB0::22::INSTR.
But when using your program, I'm not able to connect to my meter. The software aborts with the message:

Quote
cannot create device R6581D
could not open Visa device at address GPIB0::22::INSTR
error code BFFF00A5

I'm using an Agilent 82357A and choosed VISA for the interface. Am I'm missing something?

-branadic-


Early on I had a weird issue whereby I could communicate to my 3458A/34461A using GPIB0 with the Keysight IO Libraries Suite but elsewhere had to use GPIB1......or something like that, it was a while ago so can't remember...….so it might be worth playing with the resource ID's.

Ian.

EDIT:

Screenshot attached, my 3458A in the connection expert, and the GPIB app.

« Last Edit: March 19, 2019, 09:54:06 pm by IanJ »
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline branadic

  • Super Contributor
  • ***
  • Posts: 1484
  • Country: de
Re: 3458a logging via Windows app.....revisited
« Reply #171 on: March 20, 2019, 12:58:03 pm »
Tried that but didn't work for me  :'(

-branadic-
Fluke 8050A | Prema 5000 | Prema 5017 SC | Advantest R6581D | GenRad 1434-G | Datron 4000A | Tek 2465A | VNWA2.x with TCXO upgrade and access to: Keysight 3458A, Keithley 2002, Prema 5017 SC, 34401A, 34410A, Keithley 2182A, HDO6054, Keysight 53230A and other goodies at work
 

Online pwlps

  • Regular Contributor
  • *
  • Posts: 163
  • Country: fr
Re: 3458a logging via Windows app.....revisited
« Reply #172 on: March 20, 2019, 05:01:27 pm »
What is the brand/model of your gpib adapter? If it uses a gpib32.dll interface then you can bypass Visa and directly talk to this dll: select "ADLink" as interface (initially it was using some ADLink-specific dll functions hence the name, but now it is in principle compatible with other gpib32.dll's even though the interface name remained the same). 
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #173 on: March 20, 2019, 06:32:14 pm »
What is the brand/model of your gpib adapter? If it uses a gpib32.dll interface then you can bypass Visa and directly talk to this dll: select "ADLink" as interface (initially it was using some ADLink-specific dll functions hence the name, but now it is in principle compatible with other gpib32.dll's even though the interface name remained the same).

Per earlier post an Agilent 82357A which does work as I have a rip-off version and have tried it also.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline wolfy007

  • Contributor
  • Posts: 37
  • Country: au
  • Back into electronics again, as a hobby this time.
Re: 3458a logging via Windows app.....revisited
« Reply #174 on: March 28, 2019, 07:50:48 am »
I was using Ian's program last night to log the output from a 3245A, my settings were the same (3458A, GPIB0::22::INSTR, VISA on 82357A). It didnt work first couple times, same error as branadic. Noticed I had NI-VISA installed as primary, changed to the Keysight VISA as primary (didnt notice it had installed as a secondary VISA) and it started working fine. Logged 4hours of data out of the 3458A without further issues.
« Last Edit: March 28, 2019, 08:02:20 am by wolfy007 »
Tek: 222A, 212, TAS465, TDS460A, 2465, 2465B, 2467, TM504, TM506, SG504, SG503, PG506, TG501, SC504, PS503a, FG501a, DM504a, PG501, 7603+7L12
BWD: 835, 539d, 521, 504, 141, 160a  Fluke: 8060A, 8024B, 8025A, 27/FM, 87, 87III   HP: 5315A, 3478a, 3468A, 3457a  Keithley: 196, 228a  Solartron: 7081 7151
 
The following users thanked this post: IanJ

Offline wolfy007

  • Contributor
  • Posts: 37
  • Country: au
  • Back into electronics again, as a hobby this time.
Re: 3458a logging via Windows app.....revisited
« Reply #175 on: March 29, 2019, 06:05:23 am »
Just a quick update on changing the VISA version used, I did it manually on Windows8.1pro (because Windows10 sux  >:D ) as follows;

I had installed some National Instruments software to control a couple oscilloscopes last year, so I checked the details of the visa32.dll library(right click on file and select properties) in the \Windows\sysWOW64 directory. The  file details of the one already in there indicates the author as National Instruments. So I renamed it visa32.dll.NIbak, and since there was another visa32.dll.bak file in there, I checked its details and found it was a Keysight file and renamed it visa32.dll.

If there isnt another visa32 file in sysWOW64, rerun the Keysight IO installer again to repair the install (after renaming if needed) and it should put the Keysight visa32.dll in there.

Hope that helps.

PS: You could use 'C:\Program Files\Keysight\IO Libraries Suite' to check whats installed regarding VISA (and other software). You could also use the KeysightConnectionExpert to choose VISA version. Once open, click on the 'gear' icon in the top right of the ConnectionExpert window and select 'Tools', then select 'Visa Conflict Manager'. From this you should be able to choose your VISA preference.
« Last Edit: March 29, 2019, 06:24:50 am by wolfy007 »
Tek: 222A, 212, TAS465, TDS460A, 2465, 2465B, 2467, TM504, TM506, SG504, SG503, PG506, TG501, SC504, PS503a, FG501a, DM504a, PG501, 7603+7L12
BWD: 835, 539d, 521, 504, 141, 160a  Fluke: 8060A, 8024B, 8025A, 27/FM, 87, 87III   HP: 5315A, 3478a, 3468A, 3457a  Keithley: 196, 228a  Solartron: 7081 7151
 
The following users thanked this post: IanJ

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #176 on: March 29, 2019, 09:16:47 pm »
Hi all,

FWIW......on my Win10 PC.....

C:\windows\SysWOW64 = Keysight DLL
C:\windows\Systm32 = IVI Foundation DLL

Can confirm the copy in SysWOW64 is the one used by the GPIB app.....the other doesn't work.

Also, if you copy the Keysight DLL to the GPIB app folder then no matter what DLL is in the SysWOW64 folder doesn't matter......so I guess protects the app from further issues.

Note: Found the following in my SysWOW64 folder........Hmmmm!
VISA_Shared_CleanupUtility.exe

Ian.

Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Online pwlps

  • Regular Contributor
  • *
  • Posts: 163
  • Country: fr
Re: 3458a logging via Windows app.....revisited
« Reply #177 on: March 31, 2019, 12:48:19 pm »
Ian,

Can confirm the copy in SysWOW64 is the one used by the GPIB app.....the other doesn't work.

SysWOW64 is for 32-bit dlls and C:\windows\System32 for 64-bit dlls (no error here, I don't know how MS came up with this sort of inverted naming), therefore if you compile your app in 32 bit (compiler target CPU set to x86) then it will only search for dlls in the SysWOW64 folder.
For Visa dll names it is confusing too. So there is a Visa32.dll (32 bit) in SysWOW64 and Visa64.dll (64 bit) in system32, but there is also a "Visa32.dll" in the system32 folder and this one appears to contain a 64 bit version...  :-//  (so the latter seems to be there just to avoid changing the dll names in the code when switching your app from 32 bit to 64 bit ?).   

Pawel
 

Online pwlps

  • Regular Contributor
  • *
  • Posts: 163
  • Country: fr
Re: 3458a logging via Windows app.....revisited
« Reply #178 on: April 08, 2019, 12:06:11 pm »
With the correct meter setup, state "F1R0Z0N3T3D3" to clear the presentation and fix the range, I can peruse at around 60 ms interims. Alright for what I will in general do, yet not record breaking speed. How quick is your program?

I think the speed is more limited by 1) the response time of your meter, 2) my IODevice library, than Ian's code.
As for the library, by default it uses polling every few tens of ms hence the minimum delay. But the library can handle  asynchronous callbacks on SRQ therefore you can go as fast as your device permits (if your device is able to set SRQ on the "data ready" status), in Ian's source code handling SRQ can be activated with the call to "setnotify",  in Formtest.vb you can uncomment lines like:
            'uncomment this to use SRQ notifying on device1 :
            'setnotify(dev1)

With this and using HiSLIP I could sometimes get a response within 1-2 ms.  VXI11 is much slower, as for gpib it greatly depends on the gpib board but I did not study it in detail.
 
 

Offline branadic

  • Super Contributor
  • ***
  • Posts: 1484
  • Country: de
Re: 3458a logging via Windows app.....revisited
« Reply #179 on: April 23, 2019, 06:48:33 pm »
Hi Ian,

a feedback from me. I today received one of those 82357B clones and without touching the driver this one is working with your software without problems. I again checked with original Agilent 82357A but this resulted in the same error as before. Hopefully that helps somewhat.

-branadic-
Fluke 8050A | Prema 5000 | Prema 5017 SC | Advantest R6581D | GenRad 1434-G | Datron 4000A | Tek 2465A | VNWA2.x with TCXO upgrade and access to: Keysight 3458A, Keithley 2002, Prema 5017 SC, 34401A, 34410A, Keithley 2182A, HDO6054, Keysight 53230A and other goodies at work
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #180 on: April 24, 2019, 05:16:22 pm »
Hi all,

An update to V1.45, download in post #1 (I will update the source code soon).

Dogratian the manufacturer of the Temp/Humidity sensor I have used in this project has released a higher spec model (I begged him!) and which has 0.01 digit resolution on the temperature & humidity. It's called the USB-TnH (SHT30) and so I have now included this in the code.
There was also a wee bug in the existing temp/humidty interface which would only have been apparent if you has tried to select anything other than the USB-TnH SHT10 V2.00 model.

Dogratian's webpage here for the SHT30:-
http://www.dogratian.com/products/index.php/menu-sensors/menu-usb-tnh-type-a-sht30

Thanks,

Ian.




Branadic, not really sure whats going on there with the 82357A.......maybe because it's an old device!

Ian.
« Last Edit: April 24, 2019, 05:27:07 pm by IanJ »
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline maginnovision

  • Super Contributor
  • ***
  • Posts: 1182
  • Country: us
Re: 3458a logging via Windows app.....revisited
« Reply #181 on: May 04, 2019, 07:19:20 am »
I'm not sure if I'm missing something. I'm trying to use this with my Datron 1082. How would I set this up to just read the response for a sample? Using Keysight Interactive IO if I just hammer the read response button I get a sample every time.
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #182 on: May 05, 2019, 07:11:30 pm »
I'm not sure if I'm missing something. I'm trying to use this with my Datron 1082. How would I set this up to just read the response for a sample? Using Keysight Interactive IO if I just hammer the read response button I get a sample every time.

Hi,

If you mean how do you config this app to grap data from your 1082 then you'll first need to to set an interface and address of your 1082 then formulate the, as a bare minimum, then AT RUN entry to grap the actual sample.
If you click on NOTEPAD on the app you'll get a few examples for various devices.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Online pwlps

  • Regular Contributor
  • *
  • Posts: 163
  • Country: fr
Re: 3458a logging via Windows app.....revisited
« Reply #183 on: May 05, 2019, 10:45:59 pm »
Using Keysight Interactive IO if I just hammer the read response button I get a sample every time.

This is not clear: do you mean there is no command to send, i.e. it is configured as "talk only" device?
 

Offline maginnovision

  • Super Contributor
  • ***
  • Posts: 1182
  • Country: us
Re: 3458a logging via Windows app.....revisited
« Reply #184 on: May 05, 2019, 11:00:21 pm »
Well it does work in sending data as I can config the meter just fine but the program seems to be trying to read a flag which may or may not be valid and throws an error. I can not get any response from any command. Using the Keysight interactive IO works as expected be it returning data from a command or just doing a raw read(which is how it shows up in the Keysight logging program).  Actually, if it tries to run through more than 2 or 3 "AT RUN"s the meter resets. If you're interested I can get the actual reported error, if not I'll write a program for it later.

Using Keysight Interactive IO if I just hammer the read response button I get a sample every time.

This is not clear: do you mean there is no command to send, i.e. it is configured as "talk only" device?

I have tried as talker only and not. Talker only is not as useful though since I can't remotely set it up. I don't have the 1081 manual but the 1071 says it should trigger SRQ for each sample. Keysight interactive IO seems to be issuing a raw read for the VISA interface and that works but send and receive also works.

Quick edit: from memory the error had to do with MAV. Possible bit not set? Again I can verify later if either of you would like me to.
« Last Edit: May 05, 2019, 11:06:15 pm by maginnovision »
 

Online pwlps

  • Regular Contributor
  • *
  • Posts: 163
  • Country: fr
Re: 3458a logging via Windows app.....revisited
« Reply #185 on: May 06, 2019, 08:30:25 am »
Quick edit: from memory the error had to do with MAV. Possible bit not set? Again I can verify later if either of you would like me to.

If the message is "MAV bit not set" then it is clear: your meter is not quite compliant with the 488.2 specification on the meaning of status byte bits. I explain. Polling the status byte is used here to check if the device is ready to send response, according to 488.2 this information is coded in the "Message Available" bit of the status byte, the bit 5 (so the default mask used is 16). Keysight interactive IO works because it does not use any information from the status byte: when you hit "read" it calls the raw low-level read function which waits until it gets response.  But then once a "read" is issued the whole gpib bus will remain blocked until your meter is done with the measurement - very annoying if you have more than one devices connected, especially with high NPLC where it can take seconds to respond.  This software uses periodic polls to check if the data is available, before calling "read", in this way the bus remains available and the program is able to query two (or more) devices simultaneously.  This is the default configuration but it can be easily disabled on per-device basis (you may do it yourself or ask Ian to add checkboxes controlling the "enablepoll" flag for each device).  For a more elaborate version, the MAV masks can also be set individually for each device.   
« Last Edit: May 06, 2019, 08:33:46 am by pwlps »
 

Offline maginnovision

  • Super Contributor
  • ***
  • Posts: 1182
  • Country: us
Re: 3458a logging via Windows app.....revisited
« Reply #186 on: May 06, 2019, 08:47:34 am »
Quick edit: from memory the error had to do with MAV. Possible bit not set? Again I can verify later if either of you would like me to.

If the message is "MAV bit not set" then it is clear: your meter is not quite compliant with the 488.2 specification on the meaning of status byte bits. I explain. Polling the status byte is used here to check if the device is ready to send response, according to 488.2 this information is coded in the "Message Available" bit of the status byte, the bit 5 (so the default mask used is 16). Keysight interactive IO works because it does not use any information from the status byte: when you hit "read" it calls the raw low-level read function which waits until it gets response.  But then once a "read" is issued the whole gpib bus will remain blocked until your meter is done with the measurement - very annoying if you have more than one devices connected, especially with high NPLC where it can take seconds to respond.  This software uses periodic polls to check if the data is available, before calling "read", in this way the bus remains available and the program is able to query two (or more) devices simultaneously.  This is the default configuration but it can be easily disabled on per-device basis (you may do it yourself or ask Ian to add checkboxes controlling the "enablepoll" flag for each device).  For a more elaborate version, the MAV masks can also be set individually for each device.

No it's much too old to conform to 488.2. It uses bit 6(7:0) of status byte to indicate SRQ. I haven't used visual basic since VB6 but maybe I'll look into it or just write something in C++. Thanks for responding.
 

Online pwlps

  • Regular Contributor
  • *
  • Posts: 163
  • Country: fr
Re: 3458a logging via Windows app.....revisited
« Reply #187 on: May 06, 2019, 09:20:25 am »
I haven't used visual basic since VB6 but maybe I'll look into it or just write something in C++.

It is very easy to modify it in Ian's source code. In Formtest.vb, in the "create device 1" button handler sub "btncreate1_Click" you will find some hints:
Code: [Select]
            'dev1.enablepoll = False  'uncomment this if a device does not support polling ("poll timeout" is signalled)
            'dev1.MAVmask = ...  'set a different mask if your device supports polling but its status flags do not comply with 488.2

If you just uncomment "dev1.enablepoll = False" it will work exactly like Keysight interactive IO.
« Last Edit: May 06, 2019, 09:23:54 am by pwlps »
 

Offline maginnovision

  • Super Contributor
  • ***
  • Posts: 1182
  • Country: us
Re: 3458a logging via Windows app.....revisited
« Reply #188 on: May 06, 2019, 09:41:40 am »
I haven't used visual basic since VB6 but maybe I'll look into it or just write something in C++.

It is very easy to modify it in Ian's source code. In Formtest.vb, in the "create device 1" button handler sub "btncreate1_Click" you will find some hints:
Code: [Select]
            'dev1.enablepoll = False  'uncomment this if a device does not support polling ("poll timeout" is signalled)
            'dev1.MAVmask = ...  'set a different mask if your device supports polling but its status flags do not comply with 488.2

If you just uncomment "dev1.enablepoll = False" it will work exactly like Keysight interactive IO.

Thanks for the hint. I'll probably have to do a little more to implement the checking of SRQ byte and I also have 5 devices to connect to. Nothing too major. I already have a C++/OpenGL framework I wrote for my autonomous car though that would work well for this, just need to build a small UI and modify graphing for multimeters instead of maps.
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #189 on: May 06, 2019, 10:23:42 pm »
I haven't used visual basic since VB6 but maybe I'll look into it or just write something in C++.

It is very easy to modify it in Ian's source code. In Formtest.vb, in the "create device 1" button handler sub "btncreate1_Click" you will find some hints:
Code: [Select]
            'dev1.enablepoll = False  'uncomment this if a device does not support polling ("poll timeout" is signalled)
            'dev1.MAVmask = ...  'set a different mask if your device supports polling but its status flags do not comply with 488.2

If you just uncomment "dev1.enablepoll = False" it will work exactly like Keysight interactive IO.

If this something that is likely to come up again I could always update my app and add a check box for this......Thinking about it I have a Racal-Dana Freq Counter that I can't get to work, I wonder if this is the same problem?

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Online pwlps

  • Regular Contributor
  • *
  • Posts: 163
  • Country: fr
Re: 3458a logging via Windows app.....revisited
« Reply #190 on: May 07, 2019, 06:07:57 am »
I already have a C++/OpenGL framework I wrote for my autonomous car ...

Wow, would be nice to see this project too :)
 

Online pwlps

  • Regular Contributor
  • *
  • Posts: 163
  • Country: fr
Re: 3458a logging via Windows app.....revisited
« Reply #191 on: May 07, 2019, 06:18:26 am »
If this something that is likely to come up again I could always update my app and add a check box for this......Thinking about it I have a Racal-Dana Freq Counter that I can't get to work, I wonder if this is the same problem?

As far as I remember I didn't have any problems with Racal-Dana (model 1998).

More generally, disabling the polling function is only necessary when you see a message "poll timeout".

 

Offline HighVoltage

  • Super Contributor
  • ***
  • Posts: 4259
  • Country: de
Re: 3458a logging via Windows app.....revisited
« Reply #192 on: June 03, 2019, 04:13:57 pm »
I am starting on a freshly installed Win7 Pro laptop, to use this software for the first time.
What version of Visual Studio should I install?
Is there a link to an offline installer, since that laptop will not go online?
Thanks
There are 3 kinds of people in this world, those who can count and those who can not.
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #193 on: June 05, 2019, 03:52:25 pm »
I am starting on a freshly installed Win7 Pro laptop, to use this software for the first time.
What version of Visual Studio should I install?
Is there a link to an offline installer, since that laptop will not go online?
Thanks

Hi,

If you just want to run/use the software then you don't need to install VS, just download the binary in post #1 and install.

If you want to work on the source code then it was developed on VS Express 2015, but later versions should be ok also.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline branadic

  • Super Contributor
  • ***
  • Posts: 1484
  • Country: de
Re: 3458a logging via Windows app.....revisited
« Reply #194 on: June 15, 2019, 10:58:46 am »
Hi Ian,

got the app running on a Samsung Netbook, that I had laying around. What is annoying is the static window. Would have been better programming it dynamic so that it fit's the resolution of the system. Even with an external monitor I can't see everything (1024 x 800).

-branadic-
Fluke 8050A | Prema 5000 | Prema 5017 SC | Advantest R6581D | GenRad 1434-G | Datron 4000A | Tek 2465A | VNWA2.x with TCXO upgrade and access to: Keysight 3458A, Keithley 2002, Prema 5017 SC, 34401A, 34410A, Keithley 2182A, HDO6054, Keysight 53230A and other goodies at work
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #195 on: July 10, 2019, 07:23:58 pm »
Hi,

Small update to the EXE (see version 1.46), I have been playing with Temco graph )PPM/DegC) on Playback.
The formula I have coded in I think is still not perfect but it is better than the last one.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #196 on: July 10, 2019, 07:26:35 pm »
Hi Ian,

got the app running on a Samsung Netbook, that I had laying around. What is annoying is the static window. Would have been better programming it dynamic so that it fit's the resolution of the system. Even with an external monitor I can't see everything (1024 x 800).

-branadic-

Hi,

I'm not a programmer, I just hack my way around VB really......so thats why it's all fixed on one form for the most part. I just concentrated on getting it working rather than bells n whistles.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline niner_007

  • Regular Contributor
  • *
  • Posts: 115
  • Country: us
Re: 3458a logging via Windows app.....revisited
« Reply #197 on: July 20, 2019, 05:57:48 am »
IanJ, Hi! :) I respect your work, and you got really cool projects going, I have the PDVS, really great device!

I'm a software engineer, devs tools (IDEs, libraries, compilers etc.), and I do quite a bit of UI. I understand that this app works for you, but I have a few recommendations, below. If you ever need help with coding, send me a message I'll be happy to help. If not done already, I recommend putting your app on github, so others can fork/contribute.

- cleanup the UI, remove everything from the main UI, and only keep the graph/chart with data, and any other statistics. don't keep anything else on the main GUI
- pick a really good font, for data visualization involving text, the font is everything
- have a separate modal dialog for configuring the chart, with a button to get to it, make it easy to get to it from near the chart itself
- don't keep any of the device coniguration on the main menu; it causes information overload and it's unnecessary to be there all the time
it also doesn't scale, what if you have 5 x 3458A? what if you have 15 x temp sensors?
- have a main menu, from which you can get the device list, and a device configuration
- have a device list, as a modal dialog, a List Box or List View, where you'd keep an entry for each device
- you can have it as a small list (icons) on the main menu at the bottom as well, like the Keysight Bench etc.
- from the device list get to the setting of any of the devices in the list
- for a device, store the commands etc. as a script, on disk, and persist it across sessions

« Last Edit: July 21, 2019, 07:42:53 am by niner_007 »
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #198 on: July 21, 2019, 06:54:28 pm »
IanJ, Hi! :) I respect your work, and you got really cool projects going, I have the PDVS, really great device!

I'm a software engineer, devs tools (IDEs, libraries, compilers etc.), and I do quite a bit of UI. I understand that this app works for you, but I have a few recommendations, below. If you ever need help with coding, send me a message I'll be happy to help. If not done already, I recommend putting your app on github, so others can fork/contribute.

- cleanup the UI, remove everything from the main UI, and only keep the graph/chart with data, and any other statistics. don't keep anything else on the main GUI
- pick a really good font, for data visualization involving text, the font is everything
- have a separate modal dialog for configuring the chart, with a button to get to it, make it easy to get to it from near the chart itself
- don't keep any of the device coniguration on the main menu; it causes information overload and it's unnecessary to be there all the time
it also doesn't scale, what if you have 5 x 3458A? what if you have 15 x temp sensors?
- have a main menu, from which you can get the device list, and a device configuration
- have a device list, as a modal dialog, a List Box or List View, where you'd keep an entry for each device
- you can have it as a small list (icons) on the main menu at the bottom as well, like the Keysight Bench etc.
- from the device list get to the setting of any of the devices in the list
- for a device, store the commands etc. as a script, on disk, and persist it across sessions

Hi,

Thanks for your input.......and I agree the UI could be a lot better.....but here's the thing....I am not a software engineer  :palm: I basically just hacked it together in a way that got it working in the fastest/simplest way for myself and based on Pawel initial GPIB code. I then released the EXE's and source code into the wild (see post #1).

The app does everything I need it to do for me so I probably won't be doing many more mods (except just the PPM Tempco calc needs a little work when I get time). I use the app all the time at the moment, both 3458A logging and generating Playback graphs......see the graphs at the foot of this page (my new PDVS2mini):
https://www.ianjohnston.com/index.php/onlineshop/handheld-precision-digital-voltage-source-2-mini-detail

The best thing about the app is Pawel's GPIB code......it is quite simply utterly reliable (usually an issue in Wondows). It would be great for somebody else to take the source code and develop it further......I know there is one person who modified it for 6 device logging if I remember correctly.

PS...the best thing is that there is no Excel req'd (my pet hate!).

Thanks again,

Ian.
« Last Edit: July 21, 2019, 06:56:32 pm by IanJ »
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline niner_007

  • Regular Contributor
  • *
  • Posts: 115
  • Country: us
Re: 3458a logging via Windows app.....revisited
« Reply #199 on: July 21, 2019, 08:17:43 pm »
IanJ, completely understandable
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #200 on: July 25, 2019, 04:14:10 pm »
Hi,

Small update to the EXE (see version 1.47 in post #1), somebody asked to be able to set sample rates in fractions of seconds i.e. X.Xsecs.
Minimum is now 0.1 secs.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline Wintel

  • Contributor
  • Posts: 12
  • Country: us
Re: 3458a logging via Windows app.....revisited
« Reply #201 on: September 30, 2019, 11:45:52 pm »
Good program, very helpful.
 

Offline Frex

  • Contributor
  • Posts: 22
Re: 3458a logging via Windows app.....revisited
« Reply #202 on: October 27, 2019, 08:17:43 am »
Hello,

I purchased some time ago a used HP34401 DVM, and this software seem to do exactly
what i would. So the question is does it work on 34401 with only serial interface (with USB adapter) on Win7 (or win 10) ?
I first looked on BenchVue, but that really overpriced for what i need to do !
Best regards, and many thanks to all contributor of this tool.

Frex
 

Online imo

  • Super Contributor
  • ***
  • Posts: 1875
  • Country: 00
Re: 3458a logging via Windows app.....revisited
« Reply #203 on: October 27, 2019, 08:32:19 am »
Nope, the 34401A cannot work with a ttl/cmos USB dongle on its RS232.

Mind its rx/tx/dtr/dsr signals have got the rs232 levels (around +/- 9V, log1=-9V).

You need to convert the rs232 levels to ttl/cmos levels (ie. MAX232, or 2 transistors, etc).

Another issue to solve could be the handshaking. I've been using the serial, while I force the 34401's DTR input to +5V (a pullup 4k7 resistor) telling to the 34401 my side is always ready. Otherwise you most probably have to elaborate the DTR/DSR signals as well.

I was using the Agilent DMM Utility under Win7 and it worked till 10NPLC "reliably" (sometimes it had problem with initiation of the measurement, but the measurement itself was runnung for days fine). The lower NPLCs do not work reliably without handshaking. Today I use my own stm32 as an interface, fusing the 34401A data with two 16bit adcs (temperature) and an RTC, sending the data via Bluetooth to my PCs.
« Last Edit: October 27, 2019, 08:51:30 am by imo »
 

Offline Frex

  • Contributor
  • Posts: 22
Re: 3458a logging via Windows app.....revisited
« Reply #204 on: October 27, 2019, 08:49:44 am »
Hello,

Thanks for the answer.
So, even with the right level interface, it couldn't work fine, is that ?
What others solutions exist to record data with 34401 on modern PC ?
Does you own solution is available ?
Regards

Frex
 

Online imo

  • Super Contributor
  • ***
  • Posts: 1875
  • Country: 00
Re: 3458a logging via Windows app.....revisited
« Reply #205 on: October 27, 2019, 08:55:08 am »
With right interface and handshaking it works fine under Win7.
The 34401A rs232 interface speed is limited to 9600baud  >:( therefore you cannot expect it will work with all sampling rates.

Other way to get the data off the 34401A is the GPIB interface - it is fast enough for any sampling rates 34401A supports..
 

Offline Frex

  • Contributor
  • Posts: 22
Re: 3458a logging via Windows app.....revisited
« Reply #206 on: October 27, 2019, 09:27:17 am »
Hello,

Ok fine.
You would recommend to  get a GPIB-USB adapter and that's it ?
It will work out of the box with the software ?
Do you know a "low cost" model that work fine and you would recommend ?
Thanks again.

Frex
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #207 on: October 27, 2019, 02:18:14 pm »
Hello,

Ok fine.
You would recommend to  get a GPIB-USB adapter and that's it ?
It will work out of the box with the software ?
Do you know a "low cost" model that work fine and you would recommend ?
Thanks again.

Frex

82357B via Ebay (knock off version) is probably what you are looking for. I have one and it works fine with my 3458A & Win10.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline Frex

  • Contributor
  • Posts: 22
Re: 3458a logging via Windows app.....revisited
« Reply #208 on: October 27, 2019, 07:27:40 pm »
Hello,

Ok, i ordered one 82357B on Aliexpress here  https://fr.aliexpress.com/item/32905508446.html?spm=a2g0s.9042311.0.0.1ecd6c373NtPPK .
I hope that will do the job. I will post my experience as soon received.
Thank !

Frex
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #209 on: November 08, 2019, 04:51:28 pm »
Hi,

Small update to the EXE (see version 1.48 in post #1), I have been playing with the PPM/DegC option in the Playback chart.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #210 on: November 09, 2019, 12:40:18 pm »
Hi,

Small update to the EXE (see version 1.49 in post #1), I have added a REFRESH CHART button in the Playback chart......much easier/quicker to refresh the graph if you make any changes to the graph settings etc.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Offline Frex

  • Contributor
  • Posts: 22
Re: 3458a logging via Windows app.....revisited
« Reply #211 on: Yesterday at 02:38:48 pm »
Hello,

I received the 82357A adapter these days.
After spending some time to understanding what  need to be installed, i finally  get it working.
I tried first the BenchVue  multimeter software (DMM), but i won't pay for that...
So i installed your IODeviceapp software and i must say that's a great job !
Thank you for sharing your job with us.

I use it with my HP34401 DMM, and it is connected to my Win7-64 computer.
I don't know if you already had this issue, but data graph display doesn't work.
Anyway, data logging work ok.
(When i enable data display, the error box message say that autoscale can't work
with negative data, but they are only positive ! There is the same issue when
 using post-process data display utility).

I would also have one question (i'm noob on SCPI commands) about data to be logged :
Does it is possible to record two differents measurements with the same device when data logging ?
For example, i would like to record with the DMM, the frequency of the incoming signal,
and  then record the AC RMS values. (Maybe by using alternate SCPI commands
for each measurements ?) Does it is possible ?
 Thank you for your help.

Best regards,

Frex
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1004
  • Country: scotland
  • Pro EE guy many years ago, now a hobby/home biz.
    • IanJohnston.com
Re: 3458a logging via Windows app.....revisited
« Reply #212 on: Yesterday at 06:53:19 pm »
Hello,

I received the 82357A adapter these days.
After spending some time to understanding what  need to be installed, i finally  get it working.
I tried first the BenchVue  multimeter software (DMM), but i won't pay for that...
So i installed your IODeviceapp software and i must say that's a great job !
Thank you for sharing your job with us.

I use it with my HP34401 DMM, and it is connected to my Win7-64 computer.
I don't know if you already had this issue, but data graph display doesn't work.
Anyway, data logging work ok.
(When i enable data display, the error box message say that autoscale can't work
with negative data, but they are only positive ! There is the same issue when
 using post-process data display utility).

I would also have one question (i'm noob on SCPI commands) about data to be logged :
Does it is possible to record two differents measurements with the same device when data logging ?
For example, i would like to record with the DMM, the frequency of the incoming signal,
and  then record the AC RMS values. (Maybe by using alternate SCPI commands
for each measurements ?) Does it is possible ?
 Thank you for your help.

Best regards,

Frex

I think logging from the same device would depend on the commands you want to use.......I just did a quick test and set up both channels to log from my 3458A and it appears to be doing so just fine.
You could run into problems if ch.1 sends a command that is due to take some time to respond and in the meantime ch.2 has sent it's command to the same device. You could find you get a queue of commands building up (the small pop up will show you queued commands).

Could you post your CSV log file here and maybe a screenshot of the app so I can see your setup and I will take a look at it. I seem to remember a similar issue during development but thought it was all fixed.

Ian.
Ian Johnston
www.ianjohnston.com
Manufacturer of the PDVS2 & PDVS2mini
 

Online pwlps

  • Regular Contributor
  • *
  • Posts: 163
  • Country: fr
Re: 3458a logging via Windows app.....revisited
« Reply #213 on: Today at 01:02:25 pm »

I think logging from the same device would depend on the commands you want to use.......I just did a quick test and set up both channels to log from my 3458A and it appears to be doing so just fine.
You could run into problems if ch.1 sends a command that is due to take some time to respond and in the meantime ch.2 has sent it's command to the same device. You could find you get a queue of commands building up (the small pop up will show you queued commands).


Yes, the commands can mix up if both devices point to the same physical address. Using only blocking commands might work but then you loose some of the advantages of asynchronous commands.  But there is one very simple solution to this. Add, on the device2 upper panel, a new button "set device2 same as device1" as an alternative to the "create device 2" button. The code of this button would be the same except for the first line:
dev2 = CreateDevice(... etc.
should be replaced by
dev2=dev1

This is quite different from setting the same address for both: as there is only one object - i.e. a single queue and a single device lock  -  commands cannot mix up.
I did not try but I don't see any reason this wouldn't work.
« Last Edit: Today at 01:04:01 pm by pwlps »
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf