FTDI Community

Please login or register.

Login with username, password and session length.
Advanced Search  

News:

Welcome to the FTDI Community!

Please read our Welcome Note

Technical Support enquires
please contact the team
@ FTDI Support


New Bridgetek Community is now open

Please note that we have created the Bridgetek Community to discuss all Bridgetek products e.g. EVE, MCU.

Please follow this link and create a new user account to get started.

Bridgetek Community

Pages: 1 ... 8 9 [10]
 91 
 on: September 21, 2021, 08:25:43 AM 
Started by ada - Last Post by ada
If IgnoreHWSerNum is set in the registers, COM port numbers are enumerated for each USB port.  ::)

 92 
 on: September 20, 2021, 08:08:44 PM 
Started by zyx - Last Post by zyx
Hi,

We are currently having some issues with the FT245RL chip which communicates with an FPGA. We have our own software to use that chip to send data to our computer, but our computer can't get any data. We saw Ft_SetFlowControl failed. Our computer is currently running macOS High Sierra 10.13.5, and the same computer with the same software worked well in the past when it was running Sierra 10.12.3. We've tried two versions of D2XX drivers (we're using direct drivers), 1.4.4 (old) and 1.4.24 (latest), getting the same problem.

We also tested the "simple" code under /Samples/Simple in the driver package (which just writes some data to the chip and then reads the data back), and even that code ran into errors. The number of bytes in D2XX receive-queue was always a zero or a bunch of zeros and the readings were just junk. We tried this piece of simple code on several different computers running macOS Sierra 10.12.6, High Sierra 10.13.5, and Catalina 10.15.7. All of them showed similar results. We also tried another board that has the same design and we still got the same result.

Does anyone have any idea on how to fix this? Thanks in advance!

 93 
 on: September 20, 2021, 04:55:42 PM 
Started by Siddharth Mishra - Last Post by FTDI Community
Hello,

You should try uninstalling the drivers using our CDM uninstaller utility. Then install our windows driver:

https://ftdichip.com/drivers/vcp-drivers/

However Device Descriptor Request Failed usually points to a hardware issue. Please contact your local support team and include your schematics:

https://ftdichip.com/technical-support/

Section 3.2.2 of the device datasheet describes the pin configuration to use the device asynchronous mode.

Best Regards,
FTDI Community

 94 
 on: September 20, 2021, 02:12:53 PM 
Started by kalle - Last Post by FTDI Community
Hello Scott,

Thank you for the details.
The Latency timer and buffer settings are the correct settings to alter in this case.

However as I'm sure you have noticed performance on different machines can vary, this is due to the inherent nature of USB.

USB products can’t reliably be used in real-time applications with time interval resolution guarantees.

Sometimes the behaviour of USB can be a problem and applications cannot be guaranteed throughput.
If there is more USB traffic then the OS and USB have to schedule the communication with each of the USB devices.
It’s highly dependent on the OS and USB Host and is out with our control.

You could take a look at the following App notes:

Data Throughput, Latency & Handshaking
Optimising D2XX Data Throughput

These apply to all of our USB products.

The latency timer can only be set to 1ms minimum for our High Speed USB products and nothing less, and 2ms for our Full Speed USB products (like FT232R inside the USB-RS485-WE cable).

Best Regards.
FTDI Community

 95 
 on: September 20, 2021, 02:08:50 PM 
Started by Siddharth Mishra - Last Post by Siddharth Mishra
Hi there,

We are working on a project which uses FT2232H, The MCU is of Kinetis 20/22 family by NXP. While using Linux as the OS we can see the Comm Ports being created on the Terminal but the same setup is not working on Windows and gets listed in the Device Manager as (Device Descriptor Request Failed).

We have tried almost every solution available on the Internet from Installation of drivers to other files that can be of use to implement, also tried using another board with the FT2232H mounted on it but all in vain.

Also, If someone can suggest if we need to make any extra configurations to use UART in Asynchronous Mode alongwith FT2232H which as far as we know is pretty straightforward to implement. Help and Suggestions would be much appreciated.

Thanks !

 96 
 on: September 17, 2021, 05:17:52 PM 
Started by kalle - Last Post by scotttmiller
Yes I am trying to modify the Info.plist to adjust the latency and buffer settings, because I am experiencing extreme jitter in the timestamp intervals.  The issue is so severe that unless I can correct it, I cannot use the FTDI chip for my experiments.

My teammate is using the same chip on his older, Intel-based MacBook Pro.  He is also running the latest version of Big Sur.  He tried the unmodified 1.4.7 driver, and a modified 2.4.4 driver.  The unmodified 1.4.7 provides smoother streaming with less jitter than the modified 2.4.4, but it's still not good enough for our experiments.

The following are the settings he added to the Info.plist of the 2.4.4 driver:

  <dict>
    <key>InBufferSize</key>
    <integer>128</integer>
    <key>LatencyTimer</key>
    <integer>24</integer>
  </dict>

Can you recommend a different driver or different modifications for him?

--Scott

 97 
 on: September 17, 2021, 02:50:05 PM 
Started by kalle - Last Post by FTDI Community
Hello Scott,

Thank you for your question.

I would like to apologise that you haven't be able to contact any via phone in the UK office, unfortunately we are still working form home currently.

We are currently investigating how to generate a codeless .dext wrapper for any Info.plist modifications which might be required by an end user.
Is this what you are trying to achieve?

Could you describe the latency issues you are seeing?

Hello.  My name is Scott Miller and I am a BCI researcher.  I too am experiencing severe latency issues with the VCP driver on macOS 11.  I am using a MacBook Pro M1 running the latest version of Big Sur.

I read this entire thread and several others blog threads across the internet.  I emailed and spoke with Cameron from FTDI tech support in Oregon.  Cameron was very helpful.  He let me know that the latest 1.4.7 driver runs on both x86_64 and arm64.  I tried modding the 1.4.7 driver on my M1 but ran into the same code signing issues described by others in this thread.

Cameron also reached out to the FTDI team in the UK on my behalf.  That team replied with some links which talk about how to build my own driver, but that's not very useful to me at this point in time.

I also tried calling tech support in Glasgow, during normal working hours in GMT, but was unable to reach anyone at all.  The voice mailboxes are all full, and not even an operator answered my calls.  I tried repeatedly.

I suspect that FTDI is for some reason unable to obtain a DriverKit entitlement from Apple.  Is that the case?  Has FTDI made any progress on this issue?

Best Regards,
FTDI Community.

 98 
 on: September 17, 2021, 11:58:11 AM 
Started by kalle - Last Post by scotttmiller
Hello.  My name is Scott Miller and I am a BCI researcher.  I too am experiencing severe latency issues with the VCP driver on macOS 11.  I am using a MacBook Pro M1 running the latest version of Big Sur.

I read this entire thread and several others blog threads across the internet.  I emailed and spoke with Cameron from FTDI tech support in Oregon.  Cameron was very helpful.  He let me know that the latest 1.4.7 driver runs on both x86_64 and arm64.  I tried modding the 1.4.7 driver on my M1 but ran into the same code signing issues described by others in this thread.

Cameron also reached out to the FTDI team in the UK on my behalf.  That team replied with some links which talk about how to build my own driver, but that's not very useful to me at this point in time.

I also tried calling tech support in Glasgow, during normal working hours in GMT, but was unable to reach anyone at all.  The voice mailboxes are all full, and not even an operator answered my calls.  I tried repeatedly.

I suspect that FTDI is for some reason unable to obtain a DriverKit entitlement from Apple.  Is that the case?  Has FTDI made any progress on this issue?

 99 
 on: September 03, 2021, 03:51:55 PM 
Started by KBridges - Last Post by FTDI Community
Hello,

Please work with your local support team on this issue and post any resolution here to help other community users.

Best Regards,
FTDI Community

 100 
 on: September 01, 2021, 02:42:54 PM 
Started by KBridges - Last Post by KBridges
Hello,

The VDIP1 module becomes unresponsive and fails to illuminate the LEDs. Re-programming the VDAP software onto the VDIP1 module rectifies the issue.

I've emailed the support team and I've yet to receive a response.

Could it be an issue with the power supply to the module?

Kind regards,

Kristian

Pages: 1 ... 8 9 [10]