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

Show Posts

You can view here all posts made by this member. Note that you can only see posts made in areas to which you currently have access.

Messages - FTDI Community

Pages: 1 ... 58 59 [60]
886
Hi Anton,

Could you please check whether the board is connected to a USB2 or USB3 port when doing the programming?

The utility requires a USB3 port in order to program the device and the error from a USB2 port looks the same as the one you mentioned here.

The board can be recovered by connecting to a USB3 port and repeating the programming and should then show up correctly programmed with your new settings.

Best Regards
FTDI Community

887
Hi,

Thanks for your question.

When there is no bus transactions on the FT601 for 10 seconds the device will enter selective suspend mode and the driver will suspend the device. Upon entering selective suspend the device will turn off the clock. 
 
This USB selective suspend can be turned off, or the idle interval at which suspend should occur can be controlled by the FT_SetSuspendTimeout API (detailed info can be found in the D3XX Programmers Guide http://www.ftdichip.com/Support/Documents/ProgramGuides/AN_379%20D3xx%20Programmers%20Guide.pdf),but Ive put basic info on the Set and Get APIs below:-
 
FT_SetSuspendTimeout
-          Takes handle and a timeout value in seconds as input.
-          When the timeout is set to zero, driver will disable the suspend feature.
 
FT_GetSuspendTimeout
-          Take handle and pointer to ULONG as inputs.
 
Note: The value for the idle timeout configured using FT_SetSuspendTimeout is valid only for the current instance of the driver. An unplug and re-plug will cause the driver to set the timeout to a default 10 seconds.

Please may I ask you to contact support1@ftdichip.com where we can assist you further with the rest of your questions.

Best Regards,
FTDI Community

888
Discussion - Software / Re: FT51A output pad configuration
« on: October 11, 2017, 11:24:38 AM »
Hello,

All our software examples use the 8051 Digital I/O ports P1 and P3 or Analog I/O ports P0 and P2. The pull up/downs are only relevant to the pins when they are inputs, and like the 8051 the pins are open drain when set as outputs.

Also note that traditional 8051 Port 0 (P0) is open-collector, unlike the other ports (P1 to P3).
This means that an external pull-up is required when using P0 as GPIO for example.

Thanks,
FTDI Community

889
Discussion - Hardware / Re: USB-I2C converter - Cypress CY8C9560A
« on: October 06, 2017, 04:19:38 PM »
Hello Júlio,

We have not used these adapters ourselves unfortunately, but hopefully some of the other forum members can help.

One thing we did notice is that the 5 bytes of the command need to be sent together and so please check that your PC application does this without gaps between.

Best Regards,
FTDI Community


890
Hi,

Please follow the steps outlined in the Driver Uninstallation procedure which will remove and reinstall all FTDI drivers from your machine:
FTDI_Driver_Uninstall_with_2-12-28_Install.pdf

If you are still having problems after following these steps please can you contact support1@ftdichip.com with full details of your problem and a copy of your schematic so that we may review it, quoting this forum topic.

Thanks,
FTDI Community

891
Discussion - Hardware / Re: USB Printer emulator
« on: October 04, 2017, 05:06:50 PM »
Hello,

Welcome to the Forum,

I'm afraid our USB-serial bridging devices such as the FT232R don't support other USB classes and so could not be programmed to appear as a USB printer. A few applications may still support sending print data to a COM port as some printers (e.g. label printers) still connect over RS232.

If you are looking to send data (in a text file for example) from one PC to the other, you might also be able to re-direct that data to a COM port using an application such as a terminal program (send file option) or by writing a small program which parses the file and sends it out over the COM port. In this case, you could use a USB-COM232-PLUS-1 on the sending PC and another on the receiving PC and link them with a null-modem RS232 cable.

There is also a USB-NULL-MODEM cable with two FT232Rs inside which performs the same function provided that you only need a couple of meters of cabling.
http://www.ftdichip.com/Support/Documents/DataSheets/Cables/DS_USBNMC.pdf

Hope this helps,
FTDI Community





892
Discussion - Drivers / HLK Studio Error
« on: October 03, 2017, 02:16:34 PM »
Some of our customers are having problems with Driver Reseller Rights for our submission ID 1152921504627044695.
 
When they open the .hlkx files in HLK Studio, the following error appears:

"Package (Shell_1152921504627044695.hlkx) with a version (3.4.0.0) is not compatible with this instance of PackageManager.  This instance of Package Manager accepts versions 3.3.0.0, 2.0.0.0, 3.1.0.0, 3.2.0.0"

This appears to be a problem with the latest version of HLK Studio version 1703:

https://developer.microsoft.com/en-us/windows/hardware/windows-hardware-lab-kit

If you download 'Get the HLK Insider Preview' at the link above, the issue is resolved with this preview version.
Note: You need to be a member of the Windows Insider program to download this preview version.

Microsoft plan to release this updated version of HLK Studio.

Thanks,
FTDI Community

893
Discussion - Drivers / FTDI Driver Reseller Rights
« on: October 03, 2017, 02:03:49 PM »
Microsoft has moved to a new Hardware Dev Center for resell rights, replacing Sysdev:

https://developer.microsoft.com/dashboard/hardware

A resell submission is now called Shipping Label.

We have some reseller guidance on the process which was kindly shared by another customer:

Reseller Guidance.pdf

Note: You need a Microsoft Azure Domain Account.

More information can be found on Microsoft’s website since it’s their process.
If you need additional support, contact Microsoft.

Thanks,
FTDI Community

894
Discussion - Drivers / Create a Project Using the D2XX Drivers
« on: October 03, 2017, 11:27:30 AM »
The user can create 32bit or 64bit dynamic or statically linked projects using the D2XX drivers.

Read more in TN_153 Instructions on Including the D2XX Driver in a Visual Studio Express 2013 Project

The necessary driver files can be downloaded here:

D2XX Drivers

Note: The current free version of Visual Studio is Visual Studio Community 2017.
It allows you to use for 30 days without a Microsoft account. However, after this period it asks you to sign in. You can create a free Microsoft account which will allow you to continue to use Visual Studio for free.

The following simple code can be used as a test:

#include "stdafx.h"
#include <windows.h>
#include "ftd2xx.h"
int main()
{
FT_HANDLE ftHandle;
FT_STATUS ftStatus;
ftStatus = FT_Open(0, &ftHandle);
ftStatus |= FT_SetUSBParameters(ftHandle, 4096, 4096); // Set USB transfer sizes
ftStatus |= FT_SetChars(ftHandle, false, 0, false, 0); // Disable event characters
ftStatus |= FT_SetTimeouts(ftHandle, 5000, 5000); // Set read/write timeouts to 5 sec
ftStatus |= FT_SetLatencyTimer(ftHandle, 16); // Latency timer at default 16ms
ftStatus |= FT_SetFlowControl(ftHandle, FT_FLOW_NONE, 0x11, 0x13); // No flow control
ftStatus |= FT_SetBaudRate(ftHandle, 9600); // Baud rate = 9600
ftStatus |= FT_SetDataCharacteristics(ftHandle, FT_BITS_8, FT_STOP_BITS_1,
FT_PARITY_NONE);
if (ftStatus != FT_OK) printf("ftStatus not ok %d\n", ftStatus); //check for error
else
{
char data_out[12] = "Hello World";
DWORD w_data_len = 12;
DWORD data_written;
ftStatus = FT_Write(ftHandle, data_out, w_data_len, &data_written);
char data_in[12];
DWORD r_data_len = 12;
DWORD data_read;
ftStatus = FT_Read(ftHandle, data_in, r_data_len, &data_read);
if (ftStatus != FT_OK)
printf("ftStatus not ok %d\n", ftStatus);
else
printf("Data Read: %s\n", data_in);
}
ftStatus = FT_Close(ftHandle);
printf("Press Return To End Program");
getchar();
return 0;
}

895
Test and Review Area / libMPSSE Beta
« on: October 03, 2017, 11:25:29 AM »
Hi Everyone,

We have a new beta version of our libMPSSE library below:

libMPSSE__0_6_Beta.zip

This has several updates compared to the release currently on the website including:
- Resolves issue with multi-byte reads on I2C
- Resolves issue with opening device on some USB3 ports (opens by Description instead of location ID)
- Sends I2C Stop condition if the Master terminates a transaction
- Improved clock granularity in I2C_CLOCK_HIGH_SPEED_MODE
- Fix for clock resolution issue on FT2232D

We are currently testing the beta and hope to release it soon but if you have any feedback on the new beta then please let us know.

Thanks, FTDI Community

896
Window CDM WHQL Certified Driver v.2.12.28 is now available!
This applies to the following Windows OS versions:

Windows 10 (32/64)
Windows 8.1 (32/64)
Windows 8 (32/64)
Windows 7 (32/64)
Windows Server 2016
Windows Server 2012 R2 x64
Windows Server 2008 R2 x64

Download here:

2.12.28 driver files
Setup Executable

This driver version is also on Windows Update so should install automatically if you are connected to the internet.

You can also refer to the Installation Guides

If you have any feedback, please let us know.

Thanks,
FTDI Community

897
Shared Projects / USB Current and Voltage Monitor
« on: September 21, 2017, 04:53:20 PM »
Hi Everyone,

Here is a small project that our Applications engineers designed using a UM232H module in MPSSE mode. It acts as a USB to I2C Master bridge to take readings from a Texas Instruments INA219 current and voltage monitor. It also provides a couple of GPIO input lines and (most importantly of course) a flashing LED!

It connects in-line with a USB device and tracks how much current it is drawing from the host as well as the voltage on the VBus line. The 0.1" connector on the rear panel can be used instead if you want to connect it to measure other circuits via jumper wires. This can be really useful when debugging your own circuits and checking how much power they will require.

A program written in Visual Basic NET displays the results on a scrolling chart with different range settings. You can modify the code to talk to other I2C sensors as well though.

Here are some pictures showing the meter itself and a chart showing a USB flash drive which was connected and enumerated accessing a file on the disk.





We have written a document on the project as well as publishing the source code, and you can find these at the links below:

AN_355
Source Code

We hope this gives you some ideas for some projects of your own ...

Best Regards,
The FTDI Team





Pages: 1 ... 58 59 [60]