[Ajay]

Hi David,

Please find that error code 5102 means Device Not Found.  More error code details here.

So 5102 could be caused due to inappropriate device reference that you provided at initialization.  I would recommend going through example VIs in the FTDI driver that can help you get started.  In one of the examples, you may find the device interface identifying example which can list possible device interfaces address.

Thanks,
Ajay

• This reply was modified 1 year, 8 months ago by Ajay.
• This reply was modified 1 year, 8 months ago by Ajay.

[Ajay]

Hi David,

In order to help better the error code is would be required in this case. Could you please share the error code that you find on the error screen?

Regards,
Ajay.

[Ajay]

Hi Jagdish Prasad,

Please review the FTDI link here regarding the change of your corporate identity in the FTDI INF file which affects the digital signature that Microsoft provided FTDI manufacturing.  Essentially when you change the digital signature, then you would need to get a separate digital signature from Microsoft.

It states that

How can I submit my driver for certification?
Microsoft® instituted a device driver certification process to ensure the drivers are functional with their products. Many FTDI customers are interested in changing the FTDI drivers to reflect their corporate identity. This can be done via editing FTDI’s INF files, however, once an INF file has been edited, its original digital signature is no longer valid and needs to be certified. Please see AN_101: Submitting Modified FTDI Drivers for Windows Hardware Certification for a guide on the certification. Please note that Microsoft may update their process and should be supported by Microsoft.

I hope it answers your issue.  Please feel free to reach out with any further questions.

Thanks,
Ajay.

[Ajay]

Hi Nguyen Le,

There is a FAQ section in the installation procedure document whiche explains specifically about WinError 10013.  Below is the excerpt

Why do I get the OSError: [WinError 10013] error?

Error 899404774 occurred at Error Detail: OSError: [WinError 10013] An attempt was made to access a socket in a way forbidden by its access permissions

Answer: This error occurs due to the usage of port 8080 by some other applications in the PC. To fix this, open flow.py under google python package and edit the ln:369 with different port. Any port like 8070 would work. Flow.py can be typically found under C:\Users\Win7VM\AppData\Local\Programs\Python\Python37-32\Lib\sitepackages\google_auth_oauthlib

Thanks,
AJ

[Ajay]

Hi Amit,

Indexing is different from using serial number.  Usually indexing counted in the order of the devices connected physically to the PC where as serial number of the FT4222 remains same.

There is a separate software and hardware device from FTDI to write the serial number to a fresh FTDI device.  I couldn’t recollect the device details off my head right away but you or your team may know that very well from hardware designer point of view. Using that external device and application from FTDI, you may write the serial number to each devices.  You serial number could be lengthy alpha numeric.

Once you have the separate serial number for each device, you will initialize it through the same APIs to get it connected with separate sessions.

The under hood of the library is password protected for secret of sauce.  However, since these initializations are taken care by original FTDI DLL libft422.dll , I can confirm you that under-the-hood will not give much of clue in this case.

I hope this can help you explore further.  Please feel free to get back to me of any more help.

Regards,
AJ

[Ajay]

Hi Prashant

Usually when you use multiple devices at same time, then you need to connect to them using independent serial numbers to allocate separate live sessions to each device.  This library supports connecting to different devices using a serial number when you have the serial number for different devices.
—
Thanks,
AJ

[Ajay]

Hi Prashant,

Please check on the FTDI error details in the link here if it makes sense.  Feel free to get back for any further support.

—
Thanks,
AJ

[Ajay]

Hi Evan,

Historically 64-bit LabVIEW is preferred only when there is an absolute benefit like high memory usage or real dependency on 64-bit drivers etc.  However, I can give a few suggestions like

• Have you used FTDI 64-bit drivers yourselves?
• A few things can go easily wrong in Call Library Function nodes like the pointer and its conversions, please ensure they are covered properly.
• If you have other dependencies in 32-bit support, I would say the quickest trick could, open your project/files in 32-bit LabVIEW and build them.  Since you don’t need a separate license for 32-bit or 64-bit LabVIEW.  However, if your project really needs 64-bit dependencies or 64-bit benefits then the obvious rough route is to build 64-bit dependencies.  FYI: The driver I have here is for the FT4222 device and doesn’t support MPSSE on FT2xx.

Thanks
Ajay

• This reply was modified 2 years, 8 months ago by Ajay.

[Ajay]

Good finding Nirmal..!  All the best & feel free to get in touch on any more struggle.  Now this thread can be closed.

Thanks
Ajay.

[Ajay]

Hi Nirmal/Infant,

As we discussed over the call, please try to install LabVIEW on the Error PC and confirm that it’s working as you assume in this problem statement.

If the error goes away, then it means some LabVIEW components are not packed as part of the installer.

If the error still persists after LabVIEW installation, then the root cause of the error would be different.  It could be a conflict with other drivers installed (like USB2ANY which we noticed in the project and executable build).

Also, you may compare the Dependency Walker logs between working PC and non-working PC (Erroring PC) to figure out any dependencies missing on non-working PC.  As we discussed you may not be able to directly copy over the missing DLLs in this case, but you would need to figure out an installer relevant to that (eg., VC++ Run time installer for missing C++ DLL)

Thanks,
AJ

[Ajay]

Hi Syed

From your statement, I assume LabVIEW is new to your team and so you’re looking for LabVIEW evaluation.   I recommend you to ensure you can go through the learning curve of LabVIEW as it seems to be a new tool to you.  By default LabVIEW installation from here will get you 7-days of the free trial (you may extend to 45 days free trial afterward.  So a maximum of around 52 days of free LabVIEW trial).  You can select which version of LabVIEW you want from the same link.  When you install FTDI Driver from here after LabVIEW installation, you can get a 30-days trial.  After that, you would need to get an FTDI driver’s license.

—
Thanks,
AJ

[Ajay]

Hi Nirmal,

I suspect some other driver could be conflicting as we noticed USB2ANY in yesterday’s meeting.  By clean PC, I’m not sure if you mean freshly installed Windows, maybe that could help you.

Since this discovery explains that the root cause of error-13 is not on the driver level (because the error occurs in one PC and doesn’t occur on another PC at the source code level), I would say it’s out of the scope of the FT4222 driver delivery.  I would recommend taking the consultation route if you would like me to support you further.

—
Thanks,
AJ

[Ajay]

Hi Syed

FT4222 driver can work from LabVIEW 2014 (32-bit) and beyond.  Notice currently this driver doesn’t support 64-bit LabVIEW

Regards
AJ

[Ajay]

Nirmal

Are the source code and built executable runs without error in the newly installed clean PC?

Thanks
AJ

[Ajay]

Hi Nirmal/Infant,

This looks strange to me as well, as this scenario has never been faced for over 3+ years this driver out to help various developers.  We would need to systematically analyze these.  By any chance would you be able to run the dependency walker on the target system as explained in this link?  Dependency Walker is software to figure out if all dependencies of the DLL are available on the system.  If you can send the screenshot of the dependency walker where warnings or missing dependencies are mentioned, we can figure out why we’re facing this issue and what is missing.

Since you’re telling that EXE works well if the PC has LabVIEW installed, &, not working in PC where LabVIEW is not yet installed, I presume that it’s most likely the built installer might be missing some necessary component that should be installed.

Thanks,
AJ

[Author]

Posts