Cannot transfer data between two labview based softwares in the same pc using two Waveshare USB Type A to UART FT232

[govindsankar]

Hello, 

I have a general question that is not exactly labview based. If anyone can help me, kindly let me know. 

I have two USB Type A to UARR FT232 hardware which I connect on the same pc so that i can transfer data from one software to another using the COM ports generated by this. I tried communicating with hterm, and they work perfectly even on different baudrates. But then when I tried to do this with two labview based software's, and it is not working. The baudrates for the softwares are all set correctly, but it is not working. I used to use these labview softwares with virtual com ports. And it was working. But the problem is my company changed my laptop to a newer version with new admin rules. So for the virtual com port to work, i need to make such changes in my old laptop, but it is not allowed in my old laptop because of admin rules. So i had to buy this hardware for doing this. The hardware is working fine, as i said it worked with hterm and those labview softwares also work fine with virtual comports. But the hardware is not working with these two labview softwares. And I dont know how to debugg this issue. Can you give me ideas on what I can do to solve this issue. Thank you. 

[GerdW]

Hi govindsankar,

---

@govindsankar wrote:

Can you give me ideas on what I can do to solve this issue. 

---

Talk with your company IT to give you the same admin rights as you had when your setup was still working…

[MECSO]

When working with virtual com ports in the past, I found that the driver was not always installed automatically PC. For some PC it worked, for some I had to install it manually. So maybe check for the drivers in device manager first.

[daveTW]

I can confirm this. The FTDI- Devices have very good developed drivers. Since a couple of years they are part of the Windows Update System, so the should be installed automatically. This, of course, requires an internet connection.

To manually install the driver, go to https://ftdichip.com/drivers/vcp-drivers/ , it is an all-in-one driver since it consists also the d2xx- driver. It should be mentioned, that a reboot of the machine after installation is often required, although it is not mentioned by the installer.

To Do so, you need Admin- permissions on the machine, as Gerd stated.

[LVNinja]

I faced issues with FTDI usb/com adapters before, some versions are not compatible with Win11. You may need to update to older drivers. 

[govindsankar]

So i dont have some drivers, thats why its not working. But then how is the HTerm working. I started two Hterms and connected to the com ports created by each of the UART FT232 and i send message from one Hterm and recieved it in the other and vice versa. Its the labview softwares that are not working. Does these require special kind of drivers?

[RTSLVU]

---

---

Well if it's not a driver issue as others have suggested we will need to see your LabVIEW code.

Also what is the error message the LabVIEW programs show? 

[govindsankar]

Sorry for the late reply. Have been sick and out. Unfortunately i cannot share the code. The 2 programs are a battery charging discharging test program and other is a battery simulator. So the program works like this, the test program sends a handshake request to the battery simulator and the battery simulator replies which will make them connected. There is no error showing. When battery test sends the request, battery simulator doesn't get the request, so they dont connect. But as i said in the past, they used to connect with virtual com ports in my old laptop, but i cannot use virtual com port in my new laptop. Virtual com port will need to disable standard bios, which my company it admin wont allow. So i need to use hardware. But as I said the hardware is not connecting because the handshake request send by battery test system is not recieved by battery simulator. 

[daveTW]

Hello,

I adapted the "Continuous serial Write and Read" from the Example Finder to establish a communication between two (almost identical) VIs.

1. Open the project
2. Open "Continuous Serial Write and Read (1).vi"
3. Select one COM- Port in the "VISA resource name" and start the VI
4. open "Continuous Serial Write and Read (2).vi"
5. Select another other COM- Port in the "VISA resource name" and start the VI

You should now see the sended commands with ascending counters in both of the response indicators.

[RTSLVU]

The "Continuous serial Write and Read" from the Example Finder is a very poorly written example and should NOT be used. 

VIWeek 2020/Proper way to communicate over serial