Electronics > Metrology

WinGPIB - Windows GPIB App (multi-purpose)

<< < (164/166) > >>

IanJ:

--- Quote from: yuhar on June 17, 2024, 06:50:24 am ---I write a little shell to Your software that realizes my ideas... (controller for 34465A/34470A) read measurement and temperature one after the other... (maybe later tempereture controlled autocal)

And it is not the best, when the previous measurement value is still visible in the field - Please.

Istvan

--- End quote ---

Unfortunately, if I understand you, I think there are too many issues with alternating readings based on one reading completing before allowing the other......related to response time for each device.
At the moment I have a simple timer running Device 1&2. It already sends alternate commands to each device (added to each device queue), and although theoretically they should alternate responses perfectly it depends, as I said, on the response timing from each.
You can see in the Data Log that sometimes a device will respond before the other one in Device 1 & 2 mode.
I don't really want to mess with the existing code for this.

Ian.

IanJ:
New version in Post #1 available for download. - PLEASE READ THE INFO IN POST #766 BEFORE UPGRADING TO THIS VERSION IF YOU ARE COMING FROM V3.177 OR EARLIER.
WinGPIB_V3_195.zip
[Virus scanned using BitDefender AntiVirus]
Need help installing, upgrading or moving to a new PC, then see instructions in Post #1

Bug Fix = PDVS2mini tab. COM Port selection had a bug whereby it wouldn't always CONNECT to the COM Port selected on the pull-down.

Ian.

IanJ:
New version in Post #1 available for download. - PLEASE READ THE INFO IN POST #766 BEFORE UPGRADING TO THIS VERSION IF YOU ARE COMING FROM V3.177 OR EARLIER.
WinGPIB_V3_196.zip
[Virus scanned using BitDefender AntiVirus]
Need help installing, upgrading or moving to a new PC, then see instructions in Post #1

Bug Fix = PDVS2mini tab, if trying to SET OUTPUT back to PDVS2mini when Device 1 is not connected program will crash. Have changed this so that you can still communicate with a PDVS2mini even though Device 1 is not connected.

IanJ:
New version in Post #1 available for download. - PLEASE READ THE INFO IN POST #766 BEFORE UPGRADING TO THIS VERSION IF YOU ARE COMING FROM V3.177 OR EARLIER.
WinGPIB_V3_197.zip WinGPIB_V3_198.zip
[Virus scanned using BitDefender AntiVirus]
Need help installing, upgrading or moving to a new PC, then see instructions in Post #1

Added Tx & Rx LEDs to the PDVS2mini tab so the serial comms with the PDVS2mini is more visible.

UPDATE: V3.198 - LEDs moved position.

Ian.

IanJ:
So I was playing around with a new USB to RS232 (TTL) device, the Waveshare USB TO RS232/485/TTL. I chose this model because it has an isolated USB port meaning that the any mains born noise on the earth will not make it's way to the PDVS2mini when connected using WinGPIB.
However, I came across an issue and thought I'd post here concerning a common issue of getting an FTDI based USB-Serial (TTL) adaptor working on Windows.

If you are lucky, you plug in your cheap FTDI based adaptor, drivers automatically load, and it just works! If not, then you sometimes have to jump through hoops, the symptoms being you can see a COM Port in Device Manager but it doesn't work properly with your Comms app, i.e. WinGPIB or any other serial app, or worse still you don't see a COM Port at all.

The quick fix is to dump the FTDI based adaptor and buy a CH340G, CH343G, CP2102 etc. based adaptor as they 'just work'. But, if you are stuck with FTDI, then here's some tips based on my experience:

If you install the FTDI driver software then it may appear in Device Manager under PORTS as "FTDI......", but this may not work properly.
It has to appear in Device Manager as "USB Serial Port (ComX)" where X is your port number.

Zadig is a great wee app ( https://zadig.akeo.ie ) that allows you to change drivers for a device on the fly, quickly and easily, however, I found that Zadig doesn't support changing to the FTDI driver.
If it could, you'd want Zadig to change out the driver for one listed as "FTDIBUS (v2.12.6.0)" but the selection available to do so is not listed and none of the ones that are will work.

So, going back to Device Manager the answer lies there.

First, download the FTDI VCP driver from https://ftdichip.com/drivers/vcp-drivers/
(At time of writing I installed CDM-v2.12.36.4-WHQL-Certified)
Unzip and right click on both the .INF files and select INSTALL. You should get confirmation each time that the driver is installed......but of course it won't actually be active!

Next, open Device Manager, right click on the COM Port and select UPDATE DRIVER and select BROWSE FOR DRIVERS ON MY COMPUTER
Then at the bottom select LET ME PICK FROM A LIST OF AVAILABLE DRIVERS ON MY COMPUTER, and select "USB Serial Port Version........".
PS. HAVE DISK is an option but I didn't need to do that.

Once you do this (you may need to re-boot), Device Manager should now list your COM Port as "USB Serial Port (ComX)", and if you did open Zadig just for a look then it should list as "FTDIBUS (v2.12.6.0)"

Hope that helps somebody!

Ian.

Some screenshots (configured & working COM Port):

Device Manager:


Device Manager:


Device Manager:


Zadig:


Waveshare USB to RS232/485/TTL adaptor (FTDI version):
Note: There is an alternative version of this called the (B) that uses the CH343G chipset.


WinGPIB PDVS2mini comms:


Some of my, now redundant, cheap Chinese USB TTL adaptors!:

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod